Systems and methods for negotiating ticket transfers

Abstract

A method and system for enabling users of a ticketing market to exchange tickets in order to acquire groups of adjacent seats for an event. The method may include the steps of acquiring data associated with a first transaction for acquiring a first ticket by a first user, acquiring a first indication of intent by the first user to negotiate the exchange of the first ticket, and determining a set of exchange conditions. A second user may then acquire a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket acquired by the first user and request the first user to exchange the first ticket for a third ticket. When it is determined that the third ticket satisfies the set of exchange conditions, the first ticket acquired by the first user is automatically transferred to the second user, and the third ticket is automatically transferred to the first user.

Description

Technology Field

[0001] The present disclosure generally relates to e-commerce, electronic ticketing, and more specifically, to facilitating the negotiation, exchange, and purchase of event tickets. Background Technology

[0002] Computer systems and networks have facilitated the buying, selling, and transferring of goods. For example, global computer networks, such as the Internet, have enabled buyers to find and purchase goods online relatively quickly and efficiently. Similarly, global computer networks provide sellers with an efficient and cost-effective medium to advertise, offer, provide, and sell their products. E-commerce companies provide buyers and sellers with online services and infrastructure that receive orders from remote buyers, perform the financial transactions necessary to confirm and complete sales, ship or distribute goods to remote buyers, and carry out other related logistics.

[0003] One example of a market for goods within the realm of e-commerce is the online ticket market. Various online ticket sellers provide websites where parties buy and sell tickets online. These tickets are typically acquired by users to reserve seats and / or admission to various live events, such as sports events, concerts, theater events, and other entertainment events. Generally, a buyer browses for available tickets on a ticket market website or other online listings, and if available, determines which tickets are of interest to the buyer.

[0004] The technical essence claimed herein is not limited to embodiments that address any disadvantages or operate only in environments such as those described above. Instead, this background is provided merely to illustrate an exemplary technical area in which some of the embodiments described herein may be practiced.

[0005] An exemplary method may include the step of obtaining data associated with a first transaction for acquiring a first ticket by a first user in a ticketing market system. Additionally, the method includes the step of obtaining a first indication of intent by a first user to negotiate an exchange of the first ticket from a device associated with the first user in a ticketing market system, and the step of determining a set of exchange conditions by the ticketing market system. The method further includes the step of obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket acquired by the first user in a ticketing market system, and obtaining a request by the first user and a second user to exchange the first ticket acquired by the first user for a third ticket. Additionally, the method includes the step of determining by the ticketing market system that the third ticket satisfies a set of exchange conditions. In response to the satisfaction of the set of exchange conditions: the method also includes the step of automatically transferring the first ticket acquired by the first user to a second user and automatically transferring the third ticket to the first user by the ticketing market system. Brief explanation of the drawing

[0006] FIG. 1 is a block diagram of an exemplary computing system adapted to implement the selection, purchase, and exchange of tickets for issued events according to one embodiment. FIG. 2 is a block diagram of an exemplary computer system suitable for implementation on one or more devices of the computing system of FIG. 1, according to one embodiment. FIG. 3 is a block diagram of an exemplary system that facilitates the exchange of tickets for issued events according to one embodiment. Figure 4 is a diagram of an exemplary user device showing how a user can purchase tickets using a ticketing system currently available in the relevant technology field. FIG. 5 is a diagram of an exemplary user device illustrating a method in which a negotiable transfer can be initiated by a first user using the user device according to one embodiment. FIG. 6 is a diagram of an exemplary user device illustrating a method in which exchange conditions for a negotiable transfer according to one embodiment can be selected by a first user using the user device. FIG. 7 is a diagram of an exemplary user device illustrating a method in which a second user can use a negotiable transfer to acquire tickets, including tickets previously acquired by a first user, according to one embodiment. FIG. 8 is a diagram of an exemplary user device illustrating a method for a second user to select seats for a negotiable transfer to satisfy exchange conditions for a ticket previously acquired by a first user, according to one embodiment. FIG. 9 is a diagram of an exemplary user device illustrating a method for a second user to check the selection of seats for a negotiable transfer in order to satisfy exchange conditions for a ticket previously acquired by a first user, according to one embodiment. FIG. 10 is a diagram of an exemplary user device representing a request to approve a negotiable exchange of seats between a first user and a second user, which may be presented to a first user according to one embodiment. FIG. 11 is a diagram of an exemplary user device showing the resulting tickets of a second user following a successful negotiable transfer of tickets according to one embodiment. FIG. 12 is a diagram of an exemplary user device showing the resulting tickets of a first user following a successful negotiable transfer of tickets according to one embodiment. FIG. 13 is a flowchart illustrating an exemplary process that can be performed for a negotiable exchange of tickets according to one embodiment. Specific details for implementing the invention

[0007] Various applications of the devices and methods are described in this section. These examples are provided solely to add context and to aid in understanding the concepts covered by the present invention. Accordingly, it will be apparent to those skilled in the art that the present invention may be practiced without some or all of these specific details. In other cases, to avoid unnecessarily obscuring the present invention, widely known process steps have not been described in detail. Other applications are possible for which the following examples should not be considered limiting.

[0008] In the following detailed description, reference is made to the accompanying drawings, which form part of the description and illustrate specific embodiments of the present invention. Although these embodiments are described in sufficient detail to enable a person skilled in the art to practice the present invention, it is not considered that these examples are limiting, so other embodiments may be used and modifications may be made without departing from the spirit and scope of the present invention.

[0009] Devices, systems, and methods are provided for performing activities related to the online sale, purchase, resale, flipping, and swapping of tickets for issued events. In various specific embodiments, the devices, systems, or methods may include one or more devices communicating over a network. These devices, systems, and methods may facilitate the selection, negotiation, and exchange of tickets for various issued events, transfer, and purchase, as well as the exchange of goods or activities associated with the purchased tickets.

[0010] One difficulty in purchasing tickets for issued events is that as tickets are sold, a number of single or small groups of tickets tend to remain available in more desirable seating sections. As a result, it is difficult to acquire larger groups of tickets in the desired sections. Often, potential buyers are forced to choose between splitting their groups into smaller ones to correspond with the smaller groups of available tickets, which would require them to sit separately at the event, or acquiring tickets in less desirable seating sections to ensure that, where possible, the larger groups can secure seats and sit together. This scenario is also disadvantageous for ticket sellers, as they may be left with single tickets that are difficult to sell or are sold only at significant discounts.

[0011] The devices, systems, and methods described in this disclosure relate to ticket exchange activities (often referred to herein as ticket swapping, ticket flipping, or ticket swapping activities) which, according to some embodiments, may include pre-event ticket negotiation and exchange activities in which a ticket holder indicates an intention to participate in negotiations to exchange one or more tickets for a ticketed event for one or more other tickets for that event or another event. In some cases, negotiations to perform the exchange may include providing additional incentives to the ticket holder who intends to participate in the exchange. These incentives may be settled by other parties to the exchange.

[0012] In various situations, a user of the ticket exchange system may indicate an intention to exchange (swap or flip) at least one ticket for another ticket, such as a low-cost ticket in the same area or another ticket. To compensate a ticket holder who exchanges previously purchased ticket(s), an incentive may also be provided to the ticket holder, and in some cases, the ticket holder may decide whether to proceed with the ticket exchange after review. In some cases, this compensation may include a high-cost ticket for multiple low-cost tickets, a low-cost ticket for a high-cost ticket with additional costs, multiple low-cost tickets for a high-cost ticket, a ticket for another ticket in an equal swap or flip, or one or more other tickets, money, credits, goods, and / or services.

[0013] Although many examples described herein are described in the context of the exchange of tickets (often referred to herein as swapping or flipping), a person skilled in the art will understand that the systems and methods described herein may be applied to the exchange of any goods and / or services. For example, a user of an exchange system may be provided with the ability to exchange goods or services for goods or services other than tickets, in addition to or in addition to tickets (e.g., credit or gift cards to affiliates of the ticketing market, credit / coupons for discounts at the venue, credit / coupons for parking passes at the venue, vouchers for experiences at the venue, credits for future purchases in the ticketing market). The system and / or swap-available users of the system may generate exchange offers that may be offered to users of the system. In these and other embodiments, the system may generate exchange offers to users of the system based on the preferences of swap-available users and / or users of the system.

[0014] While the various examples disclosed herein focus on specific aspects of the online sale, purchase, and / or transaction of tickets (often referred to herein as swapping or flipping), it will be understood that the various principles of the invention and the embodiments disclosed herein may also be applied to other types of ticketing applications and arrangements. For example, a ticket exchange performed on a closed or proprietary computing system may utilize one or more of the aspects and features found in the various systems and methods provided in which a transaction is initiated, communicated, messaged, alerted, notified, tracked, recorded, arranged, or facilitated by the system or method.

[0015] Throughout the specification, references to “various embodiments,” “some embodiments,” “one embodiment,” “one embodiment,” “various examples,” “one example,” “example,” or “some examples” mean that a specific feature, structure, or characteristic or example described in relation to that embodiment is included in at least one embodiment. Accordingly, the appearance of these does not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0016] According to one embodiment, a computer program product may include a non-transient machine-readable medium. The non-transient machine-readable medium may have computer-readable and executable code that commands one or more processors to perform any of the methods disclosed herein.

[0017] Starting with FIG. 1, some embodiments of the computing system are adapted to implement the selection and purchase of tickets for ticketed events and / or the exchange of tickets for ticketed events, which are illustrated in a block diagram format. As indicated, the computing system (100) may include or implement a plurality of servers and / or software components that operate to perform various methodologies according to the described embodiments. Exemplary servers may include standalone and enterprise-grade servers running a server OS, such as MICROSOFT® OS, UNIX® OS, LINUX® OS, or any other suitable server-based OS. It may be seen that the servers illustrated in FIG. 1 may be deployed in other ways, and that the operations performed and / or services provided by these servers may be combined or separated for a given implementation and may be performed by a greater or smaller number of servers. One or more servers may be operated and / or maintained by the same or different entities.

[0018] The computing system (100) may include or include a client (102) capable of utilizing one or more client devices (104), such as a laptop, a mobile computing device, a PC, and / or any other computing device having computing and / or communication capabilities according to the described embodiments, among various devices, servers, databases, and other elements. In particular, the client devices (104) are considered to include a cellular phone, such as a smartphone capable of performing various computing and communication functions or other similar mobile devices that a user can carry and easily access.

[0019] Client devices (104) may generally provide one or more client programs (106), such as system programs and application programs, to perform various computing and / or communication operations. Exemplary system programs may include, without limitation, operating systems (e.g., MICROSOFT® OS, UNIX® OS, LINUX® OS, Symbian OS™, Embedix OS, BREW (Binary Run-time Environment for Wireless) OS, Java OS, Wireless Application Protocol (WAP) OS, iOS, etc.), device drivers, programming tools, utility programs, software libraries, application programming interfaces (APIs), and others. Exemplary application programs may include, without limitation, web browser applications, messaging applications (e.g., email, IM, SMS, MMS, telephone, voicemail, VoIP, video messaging), contact applications, calendar applications, electronic document applications, database applications, media applications (e.g., music, video, television), location-based services (LBS) applications (e.g., GPS, mapping, directions, points of interest, locators), proprietary ticketing applications specifically designed to support the purchase, transfer, and sale of event tickets, and others. One or more of the client programs (106) may display various graphical user interfaces (GUIs) to present information to one or more of the client devices (104) and / or receive information from the client devices (104).

[0020] In the present invention, the user interfaces (502 and 702) shown in FIGS. 5 through 12 are examples of graphical user interfaces that can be presented to a first and second user through mobile devices (500 and 700), which are examples of client devices (104) that can be used by users to communicate with a network-based system (110). Also, the network-based system (110) may be collectively referred to in the present invention as a ticketing market capable of communicating with the client device(s) (104).

[0021] As indicated, a client (102) may be coupled to a network-based system (110) communicably through one or more networks (108). The network-based system (110) may be structured, arranged, and / or configured to enable the client (102) to establish one or more communication sessions with the network-based system (110) using various client devices (104) and / or client programs (106). Accordingly, a communication session between the client (102) and the network-based system (110) (e.g., a communication session negotiating the exchange, sale, and / or purchase of tickets for a ticketed event) may involve a unidirectional and / or bidirectional exchange of information and may occur through one or more types of networks (108) depending on the mode of communication. In some cases, this communication may include facilitating communication between one or more clients (102) through the networks (108). Although the embodiment of FIG. 1 illustrates a computing system (100) deployed in a client-server operating environment, it should be understood that other suitable operating environments and / or architectures may be used according to the described embodiments.

[0022] Data and / or voice communications between the client (102) and the network-based system (110) may be transmitted and received through one or more networks (108), such as the Internet, WAN, WWAN, WLAN, mobile phone network, wired phone network, VoIP network, as well as other suitable networks. For example, the client (102) may communicate with the network-based system (110) through the Internet or other suitable WAN by transmitting and / or receiving information through interactions with websites, email, IM sessions, and / or video messaging sessions. As can be easily seen, any very wide variety of suitable communication types may occur between the client (102) and the network-based system (110). In particular, any suitable form of wireless communication may occur between the client (102) and the network-based system (110), which often occurs, for example, in the case of mobile phones or other personal mobile devices.

[0023] In various embodiments, the computing system (100) may include, among other elements, a third party server (114) that hosts a third party application (116) or a third party (112) that can be utilized. In various embodiments, the third party server (114) and / or the third party application (116) may host a website associated with or utilized by the third party (112). For example, the third party server (114) and / or the third party application (116) may enable the network-based system (110) to provide additional services and / or information, such as an additional ticket inventory, to the client (102). A third-party server (114) and / or a third-party application (116) can provide email services and / or information, social networking services and / or information, travel services and / or information, purchasing services and / or information, or other online services and / or information to a network-based system (110) and / or a client (102).

[0024] In one embodiment, the third-party server (114) may include a social networking server that hosts the user's social network account. In another embodiment, the third-party server (114) may include an email server that hosts the user's email account. In some embodiments, one or more of the client programs (106) may be used to access the network-based system (110) through the third party (112). For example, the client (102) may access and / or receive content from the network-based system (110) using a web client after initially communicating with a third-party website hosted by the third-party server (114).

[0025] A network-based system (110) may include one or more communication servers (120) that provide suitable interfaces enabling communication using various modes of communication and / or through one or more networks (108). The communication servers (120) may include a web server (122), an API server (124), and / or a messaging server (126) that provide interfaces to one or more application servers (130). The application servers (130) of the network-based system (110) may be structured, arranged, and / or configured to provide various online marketplaces and / or ticket execution services to users accessing the network-based system (110). In various embodiments, the client (102) may communicate with the application servers (130) of the network-based system (110) through one or more of the web interface provided by the web server (122), the programming interface provided by the API server (124), and / or the messaging interface provided by the messaging server (126). It may be seen that the web server (122), the API server (124), and the messaging server (126) may be structured, arranged, and / or configured to communicate with various types of client devices (104) and / or client programs (106), and may be interoperable with each other in some embodiments.

[0026] A web server (122) may be arranged to communicate with web clients and / or applications, such as web browsers, web browser toolbars, desktop widgets, mobile widgets, web-based applications, web-based resolvers, virtual machines, and others. An API server (124) may be arranged to communicate with various client programs (106) and / or third-party applications (116) including implementations of APIs for network-based systems (110). A messaging server (126) may be arranged to communicate with various messaging clients and / or applications such as email, IM, SMS, MMS, telephone, VoIP, video messaging, and others, and the messaging server (126) may provide a messaging interface that enables access by the client (102) and / or third party (112) to various services and functions provided by the application servers (130).

[0027] When implemented as an online ticketing market, the application servers (130) of the network-based system (110) may provide various online market and ticket execution services, including, for example, account services, purchase services, sales services, catalog services, exchange services, swapping services, delivery services, payment services, collection services, fraud services, intelligent decision-making services, collection services, and notification services. The application servers (130) may include an account server (132), a sales server (134), a purchase server (136), a catalog server (138), a dynamic content management server (140), a payment server (142), a notification server (144), and / or a delivery server (146), which are structured and arranged to provide these online market and ticket execution and / or exchange services.

[0028] Accordingly, application servers (130) may be coupled to and accessible to one or more databases (150), including a subscriber database (152), an active events database (154), and / or a transaction database (156). The databases (150) may generally store and maintain various types of information for use by the application servers (130) and, according to the described embodiments, may include or be implemented by various types of computer storage devices (e.g., servers, memory) and / or database structures (e.g., relational, object-oriented, hierarchical, dimensional, network).

[0029] Referring further to FIG. 2, an example of a computer system (200) suitable for implementation on one or more devices of the computing system of FIG. 1 is illustrated in block diagram format. In various embodiments, the device comprising the computer system (200) may include a personal computing device capable of communicating with a network (e.g., a smart or mobile phone, a computing tablet, a personal computer, a laptop, a PDA, a Bluetooth device, a key FOB, a badge, wearable computing devices such as smartwatches and glasses, etc.). A ticket provider and / or a payment provider may use a network computing device capable of communicating with a network (e.g., a network server). It should be understood that each of the devices used by users, ticket providers, and payment providers may be implemented as a computer system (200) in the following manner.

[0030] The computer system (200) may include a bus (202) or other communication mechanism for communicating information data, signals, and information between various components of the computer system (200). The components include an input / output (I / O) component (204) that processes user actions, such as selecting keys on a keypad / keyboard, selecting one or more buttons or links, and transmits the corresponding signal to the bus (202). The I / O component (204) may also include output components, such as a display (211) and a cursor control (213) (e.g., keyboard, keypad, mouse, etc.). An optional audio input / output component (205) may also be included to enable the user to use voice to input information by converting audio signals. The audio I / O component (205) may allow the user to listen to audio. A transceiver or network interface (206) transmits and receives signals over a network between the computer system (200) and other devices, such as other user devices, merchant servers, place servers, email servers, social networking servers, other third-party servers, and / or payment provider servers. In various embodiments, such as multiple cellular phones and other mobile device embodiments, this transmission may be wireless, but other transmission media and methods may also be suitable. A processor (212), which may be a microcontroller, a digital signal processor (DSP), or other processing component, processes these various signals for transmission to other devices on the network (260) via a display on the computer system (200), for example, or via a communication link (218). Also, in some embodiments, the communication link (218) may simply be a form of wireless communication. The processor (212) may also control the transmission of information, such as cookies or IP addresses, to other devices.

[0031] Components of the computer system (200) also include a system memory component (214) (e.g., RAM), a static storage component (216) (e.g., ROM), and / or a disk drive (217). The computer system (200) performs specific operations by executing one or more sequences of instructions contained in the system memory component (214) by the processor (212) and other components. The logic may be coded on a computer-readable medium that may refer to any medium participating in providing instructions to the processor (212) for execution. Such media may take a number of forms including, but not limited to, non-volatile media, volatile media, and transmission media. In various embodiments, non-volatile media include optical or magnetic disks, volatile media include dynamic memory such as the system memory component (214), and transmission media include coaxial cables, copper wires, and optical fibers, including wires including a bus (202). In one embodiment, the logic is encoded on a non-transient machine-readable medium. In one example, the transmitting media may take the form of acoustic or light waves, such as those occurring during radio, optical, and infrared data communications.

[0032] Some common forms of computer-readable media may include, for example, floppy disks, flexible disks, hard disks, magnetic tapes, any other magnetic media, CD-ROMs, any other optical media, punch cards, paper tapes, any other physical media having patterns of holes, RAM, PROM, EPROM, flash-EPROM, any other memory chip or cartridge, or any other media adapted for computer reading.

[0033] In various embodiments of the present disclosure, the execution of instruction sequences for implementing the present disclosure may be performed by a computer system (200). In various other embodiments of the present disclosure, a plurality of computer systems (200) coupled by a communication link (218) to a network (e.g., various other wired or wireless networks including LAN, WLAN, PTSN, and / or remote communications, mobile, and cellular phone networks) may cooperate with each other to perform instruction sequences for implementing the present disclosure. The modules described herein may be implemented in one or more computer-readable media or may communicate with one or more processors to execute or process the steps described herein.

[0034] A computer system may transmit and receive messages, data, information, and instructions, including one or more programs (i.e., application code), through communication links and communication interfaces. The received program code may be executed by a processor as received and / or stored in a disk drive component or any other non-volatile storage component for execution.

[0035] Where applicable, the various embodiments provided by this disclosure may be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and / or software components disclosed herein may be combined into composite components including software, hardware, and / or both without departing from the spirit of this disclosure. Where applicable, the various hardware components and / or software components disclosed herein may be separated into sub-components including software, hardware, or both without departing from the scope of this disclosure. Furthermore, where applicable, software components may be implemented as hardware components and vice versa.

[0036] Software according to the present disclosure, such as program code and / or data, may be stored on one or more computer-readable media. Additionally, software identified herein is considered to be implementable using one or more general-purpose or specific-purpose computers and / or computer systems, networks and / or others. Such software may be stored and / or utilized at one or more locations along or throughout the system on a client (102), a network-based system (110), or both. Where applicable, the order of the various steps described herein may be changed, combined into composite steps, and / or separated into sub-steps to provide the features described herein.

[0037] The aforementioned networks, systems, devices, and many variations thereof may be used to implement a mechanism that enables negotiation between a ticket holder and a potential ticket holder for an exchange or swapping operation for goods such as tickets and / or services and / or forms of additional rewards.

[0038] FIG. 3 is a block diagram illustrating a ticket selection and purchase system that can be used to facilitate exchange operations, such as ticket exchange, and negotiation operations, according to one embodiment. As shown in FIG. 3, the ticket server (330) can communicate with one or more user devices, such as a user device (320), one or more place devices, such as a place device (310), and one or more third-party servers, such as a third-party server (350).

[0039] In some embodiments, a location device, such as a location device (310), may be present at each of a plurality of different event locations (e.g., stadiums, theaters, arenas, amphitheaters, or other locations where ticketed events are held). The location device (310) may provide information regarding events scheduled to take place at a specific location and information regarding seats at that location. In some embodiments, the location device (310) may provide information to a ticket server (330). The ticket server (330) may obtain information regarding events scheduled to take place at various locations and information regarding seats at various locations from one or more location devices (310) or from other sources, or the ticket server (330) may have a database of event information and location information independently of any interaction with the location device. The ticket server (330) may be, for example, an embodiment of the network-based system (110) of FIG. 1.

[0040] The location device (310) may be, for example, a computer, a server, a computing tablet, or a mobile device. The location device (310) may have a processing circuit such as a processor (312) and storage such as memory (311). The processor (312) may execute a software program stored in memory (311) to provide information regarding events scheduled at the location and information regarding the seats at the location for each scheduled event. The location device (310) may provide information to a ticket server and / or a user device such as a user device (320).

[0041] The location device (310) may be placed in a location. However, this is merely exemplary. If desired, the location device (310) may be placed in a location other than a location. Each location may have a dedicated location device (310), or multiple different locations may share a common location device (310). For example, jointly owned locations may share a common location device (310).

[0042] In some embodiments, the location device (310) may be omitted if the ticket server (330) has information necessary for the purchase, sale, and exchange of tickets. For example, the ticket server (330) may have a database of information regarding tickets and locations and available tickets that enables the ticket server (330) to provide the user with information necessary for the purchase and / or exchange of tickets for events at the locations.

[0043] Third-party servers (350) may include, for example, a social media server hosting one or more social networking accounts (e.g., a social networking account for a user of the user device (320)), an email server hosting email services (e.g., an email account for a user), and / or other servers. A user may access the access ticket server (330) using the user device (320) to select and purchase tickets for issued events from the ticket server (330) (e.g.), sell tickets for issued events, purchase tickets for events at a venue and / or exchange (swap) tickets or other goods and / or services.

[0044] The third-party server (350) may be, for example, a computer, a server, a computing tablet, or a mobile device. The third-party server (350) may have a processing circuit such as a processor (354) and storage such as memory (352).

[0045] In one embodiment, the third-party server(s) (350) may be omitted if the ticket server (330) has information necessary for exchanging tickets. For example, the ticket server (330) may have a database of purchases and / or user device information collected from a user device (320) that displays other information related to the user, such as the user's social media interactions, the user's location, and the user's web interactions, among other information related to the user, such as tickets purchased by the user, user interests, the user's calendar information, the user's travel information, the user's purchase history information, or other information related to other users or tickets, events, venues, artists, teams, or situations where tickets were purchased and / or sold, and / or other information related to the user.

[0046] A user (e.g., a potential ticket swapper) can use a device such as a user device (320) to shop online for available tickets and / or exchange purchased tickets for one or more events. The user device (320) may be a mobile device, such as a cellular phone, a tablet computer, a laptop computer, a smart device, or other portable computing device. The user device (320) may be a non-mobile device, such as a home (landline) telephone, a desktop computer, an interactive set-top box, or others. The user device (320) may be any device or combination of devices that facilitate online ticket purchasing and / or exchange. The user device (320) may be, for example, an embodiment of the client device (104) of FIG. 1.

[0047] The user device (320) may have a processor (321), memory (322), a satellite positioning system component (GPS) (323), and / or other suitable device components. The processor (321) may run an application, such as an app (325), that facilitates the ticket selection, purchase, and / or exchange methods disclosed herein. The app (325) may be stored in memory (322). The app (325) may provide a graphical user interface (GUI) to the user when the user selects, purchases, and / or exchanges tickets or other goods and / or services online. If desired, the app (325) may be a dedicated ticket purchase app. However, this is merely exemplary. In some configurations, the app (325) may be part of another app, such as a payment app, or may be associated with another app.

[0048] The user device (320) can communicate with the location device (310), third-party server (350), and / or ticket server (330) through a network, such as the Internet (340). The user device (320) can communicate with the Internet via a wired or wireless connection. The app (325) can be configured to transmit location information of the user device (320) to the ticket server (330). For example, the ticket server (330) can access location information about the user based on location data from the GPS (323).

[0049] The ticket server (330) may be operated by an online ticket seller such as StubHub, Inc. The ticket server (330) may facilitate online ticket sales and / or online ticket exchanges (often referred to herein as ticket swaps). The ticket server (330) may include a processing circuit, such as a processor (331), that communicates with storage, such as memory (332). The processor (331) may include one or more processors. The processor (331) may access accounts, such as user accounts (333) and / or venue accounts (334), stored in memory (332). The user account (333) may include information about the user (e.g., identification information, preferences, account numbers, purchase history, social network contacts, email contacts, email account permissions, social media account permissions, purchased-ticket event information, event attendance information, etc.). A location account (334) may contain information about a location (e.g., information about events, seats, location, and other location features). Memory (332) may be separated from the ticket server and may be used to store any number of user accounts (333) and location accounts (334). Memory (332) may be distributed and may have parts placed in multiple different locations, for example. Other accounts, such as accounts of users selling or exchanging tickets, which include ticket details such as price, quantity, location, and event information, and financial information that enables funds to be deposited into or withdrawn from seller accounts when their tickets are sold or exchanged, may also be accessible by the processor (331).

[0050] The ticket server (330) may include one or more servers located at one or more locations. Thus, the ticket server (330) may be geographically and operablely distributed if desired. The ticket server (330) may be part of another system, such as a payment provider system. The location device (310) and / or third-party server (350) may communicate with the ticket server (330) via wired or wireless connections, for example, through a network such as the Internet (340). The location device (310) and / or third-party server (350) may communicate with a plurality of different ticket servers (330). The ticket server (330) may communicate with a plurality of different location devices (310) and / or third-party servers (350). A plurality of different ticket servers (330) may communicate among themselves and may be considered herein as identical to a single ticket server (330). The user can interact with the ticket server (330) by operating the user device (320) so that the user can select, buy, sell, and / or swap tickets online.

[0051] The ticket server (330) can obtain information about a place by communicating with the place device (310). For example, the ticket server (330) can obtain information about the scheduling of events at the place and information about the characteristics of the place by communicating with the place device (310). The characteristics of the place may depend on the events at the place, and for example, the characteristics of the place may differ from event to event. Generally, the place device (310), the user device (320), the third-party server (350), and the ticket server (330) can perform the functions described herein. That is, at least to some extent, the functions described herein as being performed through a specific one of these devices may be performed by another of these devices, by a combination of these devices, and / or by other devices.

[0052] The ticket server (330) and / or the venue device (310) may be configured to include real-time information. For example, the venue device (310) may include real-time information regarding the venue and the configuration of seats at that venue. In these and other embodiments, the venue device (310) may provide information to the ticket server (330) in real time. As another example, the ticket server (330) may include real-time information regarding the status of tickets for a venue, such as which tickets are available for purchase at the venue.

[0053] The location device (310), user device (320), third-party server (350), other mobile devices, and ticket server (330) may communicate with each other through a network such as the Internet (340), or through one or more networks such as local area networks (LANs), wide area networks (WANs), cellular phone networks, etc. Mobile devices such as the location device (310), user device (320), third-party server (350), ticket server (330), and other devices may communicate with each other at least partially through one or more near-field communication (NFC) methods or other short-range communication methods such as infrared (IR), Bluetooth, Wi-Fi, and WiMAX.

[0054] (For example) if a user wishes to shop for tickets online, resell tickets online, check in to an event venue online, access electronic tickets online, or exchange tickets online, the user may open the online ticket seller's website or access the ticket seller using an application such as an app (325). The user may open the ticket seller's website using, for example, a user device (320). The ticket seller's website may be hosted on a ticket server (330), a venue device (310), or any other server or device.

[0055] FIG. 4 is a diagram of a mobile device (400) including a seat selection user interface (402) that can be presented to a potential ticket buyer according to a ticketing platform currently known in the relevant technical field. As shown in FIG. 4, the user interface (400) includes a diagram that generally corresponds to the seats available at a place for a specific event. In the example shown in FIG. 4, it should be noted that only a subset or a small selection of the total number of seats at a specific place may be shown so that only a specific section or area of ​​the seats at the place is shown at a specific time in order to facilitate the display and selection of purchaseable seats.

[0056] In the user interface (400) shown in FIG. 4, a diagram of seats within a venue is displayed as being "available" or "unavailable" for purchase by the user. In some cases, the term "unavailable" is used to indicate tickets that have been previously purchased, temporarily or permanently reserved, or that have not been authorized for sale by the ticketing platform. Conversely, the term "available" may be used to describe tickets that are available for sale or resale by the ticketing platform. As shown in FIG. 4, seats (405a, 405b, 410a, and 410b) are "available" for purchase, while each of the remaining seats (415) is "unavailable" for purchase using the purchase tickets button (414).

[0057] In some cases, a user may want to purchase a group of seats together to ensure that a group of friends or family can sit together and enjoy an event. However, one difficulty that such a user may face while using the user interface (400) shown in FIG. 4 is that there are no remaining groups of "available" tickets for groups larger than two. To be more specific, a user may want to purchase a group of four adjacent seats, but such a group of four adjacent seats cannot be purchased using the user interface (400). In this case, the user must obtain the desired group of tickets by a) locating the group of four adjacent tickets in a different, less desirable section of the venue (if available), b) taking a different, more tedious route to find another ticket seller who has additional tickets for sale in the desired group size, or c) purchasing two separate groups of available seats (405a, 405b, 410a, and 410b) and splitting the party into two smaller groups. As can be seen, each of these options may not be desirable for a potential ticket buyer who wishes to experience the event with a group of their friends or family. Another disadvantage is that the ticketing platform operating the user interface (400) may have an excess of single or small groups of seats, and since most potential ticket buyers are interested in attending the event with at least one other person, it may be difficult to sell in many cases. If the ticketing platform lacks the ability to provide potential ticket buyers with a mechanism to acquire larger groups of adjacent tickets, it may lose potential sales and customers.

[0058] FIGS. 5 through 12 illustrate diagrams of a method in which mobile devices (500 and 700) of a first user A and a second user B (including user devices) according to one embodiment may each be used to perform a negotiable transfer of seats between the first user A and the second user B. More specifically, FIG. 5 is a diagram of an exemplary mobile device (500) illustrating a method in which a negotiable transfer may be initiated by the first user A through a user interface (502) which may be part of a ticketing market app (325) (e.g., the app shown in FIG. 3) or a website. For example, the user interface (502) may be displayed on a ticketing market application that is displayed to the first user A as part of a ticketing purchase performed through an application via the user device (500). In another embodiment, the user interface (502) may be part of a ticket seller website to which the first user A has logged in, or it may occur on a display of the mobile device (500) or another device.

[0059] As illustrated in FIG. 5, a first user A interacts with the user interface (502) and indicates a desire to purchase tickets A4 and A5 corresponding to seats "4" and "5" of row A in a specific section of the venue for the event. As can be seen, the user interface (502) may initially display seats A4 and A5 as "available" for purchase by using a designated graphic or image designed to notify the user of seat availability. For example, in FIG. 5, seats A2 and A3 are also exemplified as "available," but seat A1 is indicated as "unavailable." As illustrated in FIG. 5, upon selection and / or purchase of seats A4 and A5, the user interface (502) may make seats A4 and A5 of the user interface (502) have a modified appearance indicating the selection and / or purchase of these seats. It should be understood that any number of means for selecting seats A4 and A5 may be used, including but not limited to the user selecting seats by clicking a corresponding part of a touch-screen display or entering text indicating the desired seats.

[0060] According to one embodiment, during the purchase process, a first user A is presented with an option to receive their purchased seats A4 and A5 for a negotiable transfer to another user. This can be accomplished by various methods including various graphic control elements such as selectable buttons (512), which enable the first user A to select selectable features through the user interface (502). It should be understood that other selection means, including checkboxes, radio dial buttons, or others, may be used. In another embodiment, as shown in FIG. 5, the first user A can select seats A4 and A5 for a negotiable transfer by selecting the button (512) when purchasing tickets. When the first user A completes their selection and decides whether to make the selected tickets into a negotiable transfer, the first user A can complete their ticket selection by pressing the purchase tickets button (514).

[0061] FIG. 6 is a diagram of an exemplary user device illustrating how exchange conditions for a negotiable transfer can be selected by a first user A using a user interface (502). More specifically, after selecting tickets A4 and A5 as targets for a negotiable transfer, the user interface (502) may prompt the first user A to select transfer or exchange conditions by providing a list or a series of selectable buttons (612, 614, and 616) corresponding to a set of exchange conditions for which the first user A is willing to trade or exchange seats A4 and A5.

[0062] In the example shown in FIG. 6, the first user A can choose from three distinct options, including a selectable button (612) corresponding to the exchange condition for two tickets in Section XX with an additional reward of $50, a selectable button (614) corresponding to the exchange condition for two tickets in Section YY with an additional reward of $50, and a selectable button (616) corresponding to the exchange condition for two tickets in Section ZZ without additional financial reward. As can be seen, in this example, tickets in Section ZZ may be assumed to be slightly more valuable. In some cases, this may be because tickets in Section ZZ have a better view and are closer to the stage, stadium, or etc. In this example, the first user A can select any of the selectable exchange conditions using the selectable buttons (612, 614, and 616). Also, in this example, the selectable exchange conditions may be generated or identified by the ticket server (330).

[0063] Exchange conditions may be generated or identified by the ticket server (330) based on a comparison between tickets A4 and A5 and tickets for other available seats. The comparison may be based on one or more factors, such as quality, quantity, price, user preferences, market demand, location, and other factors that may be considered when purchasing tickets for an event. In some embodiments, the machine learning model may be generated by a machine learning algorithm such as a neural network, a random forest, or a decision tree machine learning algorithm. The machine learning model may be provided with tickets A4 and A5 that are subject to negotiation transfer. The machine learning model may indicate other tickets and / or other tickets and financial rewards that are comparable to tickets A4 and A5. In these and other embodiments, the machine learning model may output a range of other tickets. The ticket server (330) may review the tickets available for purchase from the range of tickets and select tickets for exchange. In these and other embodiments, a machine learning model may be generated by providing a machine learning algorithm with a number of different scenarios of exchange conditions to learn how to select exchange conditions for a given set of tickets. For example, information regarding exchange tickets, such as quality, quantity, location, costs, market demand, and other information may be provided to the machine learning algorithm and one or more different exchange conditions. Based on this information, the machine learning algorithm may generate a machine learning model. After the generation of the machine learning model, similar information regarding tickets to be exchanged may be provided to the machine learning model, and the machine learning model may provide exchange conditions for a range of seats. The ticket server (330) may select seats from a range of currently available seats and provide exchange conditions for the selected seats to the first user A.

[0064] If more than a certain number of exchange conditions are available, the ticket server (330) may select exchange conditions to be provided to the first user A based on the exchange history of the first user A. For example, if more than three exchange conditions are available to be provided to the first user A, the ticket server (330) selects from among exchange conditions similar to previous selections by the first user A. For example, if the first user A has previously selected exchange conditions with additional rewards rather than exchange conditions without additional rewards, the ticket server (330) may select exchange conditions with additional rewards to be provided to the first user A. In some embodiments, the machine learning model may also be generated based on user preferences. In these and other embodiments, user preferences for exchange conditions may be provided to the machine learning model so that they are used in the generation of exchange conditions by the machine learning model. As an example, tickets A4 and A5 may have a combined value of $200 and may be located near the aisle, bathroom, and home team as preferred by the first user A. Values, locations for aisles and bathrooms, and preferences of the first user A may be provided to the ticker server (330). The ticket server (330) may select two sets of tickets for exchange. Each set of tickets may include a home team, an aisle, and a bathroom nearby. The first set of tickets may have a value of $175. The second set of tickets may have a value of $200. Consequently, the exchange conditions for the first set of tickets may include a reward of $25. The exchange conditions for the second set of tickets may not include a reward.

[0065] FIG. 6 illustrates a user interface (502) comprising selectable buttons (612, 614, and 616) corresponding to exchange conditions generated or identified by the ticket server (330), but it should be understood that other mechanisms may be used to set exchange conditions. In some cases, a first user A may generate his or her own exchange conditions by selecting other seats and / or seat sections considered suitable for acceptable exchange conditions, using any number of user input mechanisms including a text input field and a user interface that allows the first user A to view a graphic interface depicting various seat sections of the venue. Also, in the example shown in FIG. 6, it is assumed that the first user A requires exchange conditions that generate the same number of seats for the event, but in some cases, through exchange conditions, the first user A may swap or trade their previously purchased seat(s) for more or fewer seats.

[0066] Returning to the user interface (502), it should also be understood that the first user A may be able to select a set of more than one exchange conditions. In this example, it is assumed that the first user A can use both selectable buttons (612 and 616) to indicate that the first user A considers two tickets in Section XX and $50, or two tickets in Section ZZ, as acceptable exchange conditions. Once the first user A has completed their selection, the first user A can submit the exchange conditions using the selectable button (620).

[0067] FIG. 7 is a diagram of an exemplary mobile device (700) illustrating a method by which a negotiable transfer may subsequently be performed by a second user through a user interface (702), which may be part of a ticketing market app (325) (e.g., the app shown in FIG. 3) or a website. In this disclosure, the second user is referred to as "second user B". For example, the user interface (702) may be displayed in a ticketing market application that is displayed to the second user B through the user device (700) as part of a ticketing purchase performed through the application. In another embodiment, the user interface (702) may be part of a ticket seller website to which the second user B is logged in, or it may occur on a display of the second user B's mobile device (700) or another device.

[0068] As shown in FIG. 7, a second user B interacts with the user interface (702) and indicates a desire to purchase tickets A2-A5 corresponding to seats "2", "3", "4", and "5" in row A of a specific section at the venue for the event. As can be seen, the user interface (702) may indicate that seats A2 and A3 are "available" for purchase directly from the ticket server (330) using designated graphics or images designed to notify the user of seat availability. The user interface (702) may indicate that seats A4 and A5 are available for purchase via a negotiable transfer. As illustrated in FIG. 7, after the selection and / or purchase of seats A4 and A5, the user interface (702) may display an indication exemplifying acceptable exchange conditions associated with the selected seats A4 and A5 and corresponding selectable buttons (712 and 714) that may be selected by a second user B, and an indication of the second user B’s intent to exchange for a negotiable transfer of the selected seats A4 and A5 according to the selected exchange conditions. Thus, the acceptable exchange conditions associated with the selected seats A4 and A5 and the corresponding selectable buttons (712 and 714) may not be displayed on the user interface (702) when the second user B first sees them. Instead, in some embodiments, the acceptable exchange conditions associated with the selected seats A4 and A5 and the corresponding selectable buttons (712 and 714) may be displayed only after an indication of interest in one or more of tickets A2-A5 has been provided.

[0069] When the second user B selects the "2 tickets of Section XX and $50" exchange condition button (712) shown in FIG. 7, the user interface (702) may be updated to the display shown in FIG. 8. As shown in FIG. 8, the user interface (702) indicates that the second user B has selected to transfer the 2 tickets to the first user A in exchange for $50 and the 2 tickets of Section XX, and displays a prompt to the second user B instructing the second user B to select the 2 tickets of Section XX to be subsequently transferred to the first user A with $50 in exchange for tickets A4 and A5 previously purchased by the first user A for purchase by the second user B. The user interface (702) may include a display exemplifying the selection of "available," "unavailable," and "negotiable" seats. In this example, a second user B can use a user interface to select tickets B5 and B6, which are exemplified as "available" and are available for sale or resale by the ticketing platform through the ticket server (330). As can be seen, the ticketing selection process may include various different embodiments, including the display of various prices for various seats.

[0070] Subsequently, the second user B may complete the selection of two seats B5 and B6 in Section XX by selecting a button (812) that indicates the second user B’s commitment to participate in the purchase of seats B5 and B6 for the purpose of transferring or exchanging tickets as part of a negotiable exchange condition for seats A4 and A5 purchased by the first user A. In some cases, the user interface (702) may be updated to display a summary of the exchange to the second user B. More specifically, the user interface (702) may exemplify that the second user B has chosen to purchase seats A2 and A3 to be transferred to the second user B as described below for purchase from the ticketing platform. Additionally, the user interface (702) may exemplify that although the second user B has selected to purchase seats B5 and B6 from the ticketing platform, as described below, instead of being transferred or delivered to the second user B, they are automatically transferred to the first user A in exchange for seats A4 and A5, and subsequently delivered to the second user B. Subsequently, when reviewing the conditions for the exchange, the second user B can complete their selection using the button (912).

[0071] Upon completion of their selection according to the user interface (702) shown in FIG. 9, the second user B may be guided to another user interface to perform the purchase of tickets A2, A3, B5, and B6 with an additional $50 according to negotiated exchange conditions. It should be understood that any number of payment interfaces, including the ability to perform payments using a credit card, bank transfer, financial account, or the like, may be used in connection with the user interface (702).

[0072] In some embodiments, when the second user B completes the purchase and the funds are deemed transferred, the terms of a negotiable exchange between the first user A and the second user B may be deemed satisfied, and tickets A2, A3, A4, and A5 may be automatically transferred to the second user B, while tickets B5 and B6 and a $50 credit or gift card are transferred to the first user A. The transfer may simply involve the other user notifying the first user A that they have accepted and satisfied the terms of their negotiable transfer, and thus the first user A is deemed no longer to have ownership of the tickets corresponding to seats A4 and A5, and instead receives ownership of tickets B5 and B6 along with a $50 credit or gift card. In some cases where User 1 A has already received electronic or physical tickets corresponding to seats A4 and A5, User 1 A may be notified that the scannable barcode or other ticketing data on the electronic or physical tickets previously corresponding to seats A4 and A5 has been invalidated and no longer permits access to the venue for the event, and instead, new tickets B5 and B6 have been issued.

[0073] In other cases, the first user A may receive a notification that the second user B has requested to participate in a negotiable transfer of tickets corresponding to seats A4 and A5 according to the exchange conditions previously submitted by the first user A. In these embodiments, the first user A may receive a notification displayed on a user interface (502) that displays the locations of seats B5 and B6 to be received in exchange for the previously purchased seats A4 and A5, so that the first user A may explicitly accept the terms of the transfer. In the user interface (502), the first user A may accept the terms of the transfer through a selectable button (1012). In some cases, the first user A may be given a certain period of time to accept the terms of the negotiable exchange before the offer for the exchange is deemed invalid and expires. Additionally, upon the acceptance of the terms of the negotiable exchange by the first user A, the second user B may be granted a specific time period to complete the purchase of tickets A2, A3, B5, and B6, along with payment for an additional reward of $50. If the second user B fails to complete the purchase within the allocated time period, the exchange shall be deemed void and expire. Conversely, if the second user B completes the purchase within the prescribed period, the terms of the negotiation shall be deemed satisfied.

[0074] Upon completion of the purchase of tickets by the second user B and the negotiable exchange between the second user B and the first user A, FIG. 11 illustrates a user interface (702) that provides the second user B with a summary illustrating ownership of the group of adjacent seats A2-A5. It should be noted that in the user interface (702) shown for the second user B, seats B5 and B6 are displayed as "unavailable" because they have been transferred to the first user A in exchange for the received tickets A4 and A5.

[0075] Similarly, FIG. 12 illustrates a user interface (502) that may be displayed to the first user A upon completion of a negotiable transfer of tickets A4 and A5 to the second user B in exchange for tickets B5 and B6 and an additional $50 reward. As shown in FIG. 12, upon completion of the negotiable transfer, the seats A4 and A5 previously owned by the first user A are now marked as "unavailable" because they have subsequently been transferred to the second user B, and the first user A is now marked as owning tickets B5 and B6. Additionally, the user interface (502) now includes a selectable button (1212) that enables the first user A to use or redeem the $50 credit received as part of the exchange conditions.

[0076] While the embodiments described herein exemplify exchange conditions including exchanges for seats, credits, and / or financial compensation, it should be understood that other exchange conditions may be used. For example, exchange conditions may include credits or vouchers for various goods and services, such as food service items, merchandise items, parking vouchers, or other amenities available at the venue. As can be seen, such exchanges may involve providing one party involved in a negotiable transfer with a voucher, gift card, or coupon that enables the user to receive the goods or services, and in return, requesting payment or compensation from the other negotiating party for the corresponding value of the goods or services. Additionally, exchange conditions may include exchanges for gift cards or credits for merchants affiliated with the ticketing platform, or further, exchanges for tickets to other events and / or shows available through the ticketing platform.

[0077] As can be seen, the embodiments described herein enable a second user B to participate in the negotiable transfer of seats A4 and A5 from a first user A, thereby providing the second user B with a mechanism to acquire a larger group of adjacent tickets than could otherwise be purchased from a ticketing platform currently known in the relevant art. More specifically, by providing a mechanism that facilitates the direct purchase of tickets from a ticketing platform along with the negotiable transfer of seats between the first user A and the second user B, the embodiments described herein enable users to identify and acquire larger groupings of seats than could otherwise be possible, and more specifically, enable users to perform these transactions using a convenient user interface that communicates with the ticketing platform described herein. In some cases, the mechanism that facilitates the direct purchase of tickets from a ticketing platform along with the negotiable transfer of seats may be performed via a display on a mobile device such as a smartphone or another client device (104).

[0078] Also, although the negotiable transfer of FIGS. 4 through 12 is shown to be performed on mobile device(s), it should be understood that the types of exchanges described herein may be presented to users or other types of computing devices, such as non-mobile computing devices, laptop devices, tablet devices, desktop devices, or others.

[0079] Exemplary steps 1300 used to initiate and / or provide negotiations for transferring tickets are illustrated in FIG. 13. As described above, as the connectivity of devices expands, there will be various methods for notifications, offers, messaging, prompting, and other actions that initiate and facilitate exchange transactions.

[0080] In step 1310, for example, a system of the type shown in FIG. 1 and / or FIG. 3 may obtain data associated with a first transaction corresponding to a first ticket acquired by a first user A of the system. Step 1310 may include a step of participating in and facilitating the purchase of the first ticket with the first user A. In other embodiments, step 1310 may include the first user A notifying the system that the first user A is the owner of the first ticket, and in some cases, providing the system with verification information that the first ticket is valid and / or that the first user A is the rightful owner.

[0081] At step 1320, the system may obtain from the first user A an intention to negotiate the exchange of the first ticket. At step 1330, the system may determine a set of exchange conditions. In some embodiments, determining the set of exchange conditions may include the system determining a suitable value for the first ticket and providing the first user A with a list of proposed or available exchange conditions. In other embodiments, the system may receive exchange conditions generated by the first user A and provided to the system. The exchange conditions may include a proposal for the first user A to exchange the first ticket for a ticket of a different value, and in some circumstances, additional compensation or, for example, additional costs as described herein in connection with FIGS. 4 through 12.

[0082] At step 1340, the system may obtain a request by second user B to obtain a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket, in addition to a request to exchange the first ticket for a third ticket obtained by second user B. At step 1350, the system may determine whether the third ticket satisfies a set of exchange conditions. If the system determines that the third ticket satisfies a set of exchange conditions, at step 1360, the system may automatically transfer the first ticket and the second ticket to second user B, and at step 1370, the system may automatically transfer the third ticket to first user A.

[0083] The system may transfer funds and / or additional tickets between the first and second users according to exchange conditions to compensate the first user A who participated in the negotiable transfer. The system may also enable the first user A to accept the transfer of a third ticket prior to transferring the funds and / or tickets.

[0084] It should be understood that one or more of the processes and steps described in relation to FIG. 13 may be performed in any suitable order, omitted / or repeated any suitable number of times to facilitate the purchase, sale, resale, and / or exchange of tickets and / or other goods and / or services.

[0085] Examples specification

[0086] The present disclosure may include any one of the following embodiments:

[0087] In Example I, the method comprises the step of obtaining data associated with a first transaction for obtaining a first ticket by a first user in a ticketing market system. Additionally, the method comprises the step of obtaining a first indication of intent by a first user to negotiate an exchange of the first ticket, as a device associated with the first user in a ticketing market system, and the step of determining a set of exchange conditions by the ticketing market system. Additionally, the method comprises the step of obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user in a ticketing market system, and obtaining a request by the first user and a second user to exchange the first ticket obtained by the first user for a third ticket. Additionally, the method comprises the step of determining by the ticketing market system that the third ticket satisfies a set of exchange conditions, and in response to the satisfaction of the set of exchange conditions: automatically transferring the first ticket obtained by the first user to the second user by the ticketing market system; and automatically transferring the third ticket to the first user.

[0088] In Example II, the system of the ticketing market includes a non-transient memory configured to store instructions. The system includes one or more processors configured to execute instructions from the non-transient memory to cause the system to perform operations, the operations include an operation of obtaining data associated with a first transaction for obtaining a first ticket by a first user, an operation of obtaining a first indication of intent by the first user to negotiate the exchange of the first ticket from a device associated with the first user, and an operation of determining a set of exchange conditions. The operations also include an operation of obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user, and an operation of obtaining a request from the first user and a second user to exchange the first ticket obtained by the first user for a third ticket. The operations also include an operation of determining that the third ticket satisfies a set of exchange conditions, and in response to the satisfaction of the set of exchange conditions: automatically transferring the first ticket obtained by the first user to the second user and transferring the third ticket to the first user.

[0089] In Example III, a non-transient computer-readable medium stores machine-readable instructions that, when executed by a server device, cause the server device to perform operations, said operations include, in a system of ticketing markets, an operation of obtaining data associated with a first transaction for obtaining a first ticket by a first user, and in a system of ticketing markets, an operation of obtaining a first indication of the first user's intent to negotiate the exchange of the first ticket from a device associated with the first user, and in a system of ticketing markets, an operation of determining a set of exchange conditions. The operations also include, in a system of ticketing markets, an operation of obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user, and obtaining a request from the first user and a second user to exchange the first ticket obtained by the first user for a third ticket. The operations also include, in a system of ticketing markets, an operation of determining that the third ticket satisfies a set of exchange conditions. In response to the satisfaction of a set of exchange conditions, the operations include the operation of automatically transferring a first ticket obtained by a first user to a second user and automatically transferring a third ticket to the first user by the system of the ticketing market.

[0090] Furthermore, embodiments consistent with the present disclosure may include any combination of the following elements in any order and number, in addition to embodiments I, II, and III:

[0091] Element 1, the step of determining that a set of exchange conditions is satisfied comprises: obtaining at least one user preference associated with the set of exchange conditions in a system of a ticketing market; and comparing a first value of a first ticket obtained by a first user with a second value of a third ticket. Element 2, the exchange for the third ticket and the first ticket further comprises additional items, and in response to determining that the third ticket and the additional items satisfy a set of exchange conditions, the additional items are transferred to the first user. Element 3, the additional items include financial incentives, credits for goods, or credits for services. Element 4, the step of determining that the third ticket satisfies a set of exchange conditions comprises: transmitting a notice requesting permission for exchange conditions to a device associated with the first user; and receiving approval from the first user through the device associated with the first user to perform the transfer of the first ticket from the first user to the second user and the transfer of the third ticket to the first user. Element 5, the step of determining a set of exchange conditions includes presenting a list of potential exchange conditions to the first user through a device associated with the first user. Element 6, the list of potential exchange conditions includes a list of alternative seat sections having available seats determined to be comparable in value to the seat corresponding to the first ticket, and the list of alternative seat sections is selectable by the first user as an indication of the first user's intention to exchange the seat corresponding to the first ticket for an available seat in the alternative seat sections.

[0092] Element 7, the step of determining that a set of exchange conditions is satisfied includes the step of obtaining at least one user preference associated with the set of exchange conditions; and the step of comparing a first value of a first ticket obtained by a first user with a second value of a third ticket. Element 8, the exchange for the third ticket and the first ticket further includes additional items, and in response to determining that the third ticket and the additional items satisfy a set of exchange conditions, the additional items are transferred to the first user. Element 9, the additional items include financial incentives, credits for goods, or credits for services. Element 10, the step of determining that the third ticket satisfies a set of exchange conditions includes the step of transmitting a notice requesting permission for exchange conditions to a device associated with the first user, and receiving approval from the first user through the device associated with the first user to perform the transfer of the first ticket from the first user to the second user and the transfer of the third ticket to the first user. Element 11, the step of determining a set of exchange conditions includes presenting a list of potential exchange conditions to the first user through a device associated with the first user. Element 12, the list of potential exchange conditions includes a list of alternative seat sections having available seats determined to be comparable in value to the seat corresponding to the first ticket, and the list of alternative seat sections is selectable by the first user as an indication of the first user's intention to exchange the seat corresponding to the first ticket for an available seat in the alternative seat sections. Element 13, the device associated with the first user includes a smart device capable of communicating with a ticketing market.

[0093] Element 14, the step of determining that a set of exchange conditions is satisfied comprises: obtaining at least one user preference associated with the set of exchange conditions in a system of a ticketing market; and comparing a first value of a first ticket obtained by a first user with a second value of a third ticket. Element 15, the exchange of a third ticket and a first ticket further comprises additional items, and in response to determining that the third ticket and additional items satisfy a set of exchange conditions, the additional items are transferred to the first user. Element 16, the additional items include financial incentives, credits for goods, or credits for services. Element 17, the step of determining a set of exchange conditions comprises presenting a list of potential exchange conditions to the first user through a device associated with the first user.

[0094] Terms used herein, in particular, in the appended claims (e.g., the text of the appended claims) are generally intended to be "open-ended" terms (e.g., the term "comprising" should be interpreted as "comprising but not limited thereto," the term "having" should be interpreted as "at least having," the term "comprising" should be interpreted as "comprising but not limited thereto," and so on).

[0095] Additionally, if a specific number of introduced claim citations is intended, such intent will be explicitly indicated in the claim, and in the absence of such citations, such intent does not exist. For example, for the aid of understanding, the following appended claims may include the use of the introductory phrases “at least one” and “one or more” to introduce claim citations. However, the use of such phrases should not be interpreted as implying that the introduction of a claim citation by the indefinite articles “one (a)” or “one (an)” limits any specific claim containing such introduced claim citations to embodiments containing only one such citation, and even if the same claim contains the introductory phrases “one or more” or “at least one” and the indefinite articles, e.g., “one (a)” or “one (an)” (e.g., “one (a)” and / or “one (an)” should be interpreted as meaning “at least one” or “one or more”), the same applies to the use of the definite article used to introduce the claim citations.

[0096] Furthermore, even if a specific number of introduced claim citations is explicitly cited, it is understood that such citations should be interpreted to mean at least the number cited (e.g., the most basic citation of “2 citations” without other modifiers means at least 2 citations, or 2 or more citations). Moreover, where conventions similar to “at least one of A, B, and C, etc.” or “one or more of A, B, and C, etc.” are used, such configurations are generally intended to include A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together, etc. For example, the use of the term “and / or” is intended to be interpreted in this way.

[0097] Additionally, any disjunctive word or phrase presenting two or more alternative terms in any of the detailed description, claims, or drawings or terms should be understood to include the possibility of including one of the terms, any one of the terms, or all of the terms. For example, the phrase “A or B” should be understood to include the possibility of “A” or “B” or “A and B”.

[0098] Additionally, the use of terms “first,” “second,” “third,” etc. is not necessarily used herein to mean a specific order or number of elements. Generally, terms “first,” “second,” “third,” etc. are used as general identifiers to identify different elements. Unless the terms “first,” “second,” “third,” etc. are indicated to mean a specific order, these terms should not be understood to mean a specific order. Furthermore, unless the terms “first,” “second,” “third,” etc. are indicated to mean a specific number of elements, these terms should not be understood to mean a specific number of elements. For example, the first widget may be described as having a first face, and the second widget may be described as having a second face. With respect to the second widget, the use of the term "second surface" is intended to distinguish this surface of the second widget from the "first surface" of the first widget and does not imply that the second widget has two surfaces. Although the foregoing invention has been described in detail as examples and illustrations for the purposes of clarity and understanding, it will be understood that the foregoing invention may be embodied in numerous other specific variations and embodiments without departing from the spirit or essential characteristics of the invention. Various changes and modifications may be made, and it will be understood that the invention is not limited by the foregoing details but rather should be defined by the scope of the claims.

Claims

Claim 1 As a method, the method comprises: a step of obtaining data associated with a first transaction for acquiring a first ticket by a first user by a ticketing market system; a step of notifying the first user by the ticketing market system that the first user is the owner of the first ticket; a step of causing a device associated with the first user by the ticketing market system to display a graphical control element for the first user to select an option for a negotiable transfer of the first ticket to a second user; and, after notifying the first user that the first user is the owner of the first ticket, a step of obtaining a first indication of the first user's intention to negotiate an exchange of the first ticket from the graphical control element by the ticketing market system. After notifying the first user that the first user is the owner of the first ticket and obtaining the first indication of the first user's intent to negotiate the exchange of the first ticket: determining a set of exchange conditions by the ticketing market system and based on a comparison between the first ticket and tickets for available seats; obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user by the ticketing market system, and obtaining a request from the first user and the second user to exchange the first ticket obtained by the first user for a third ticket; determining by the ticketing market system that the third ticket satisfies the set of exchange conditions determined based on a comparison between the first ticket and tickets for available seats;and in response to the satisfaction of the set of exchange conditions above: a method comprising the step of automatically transferring the first ticket obtained by the first user to the second user by the system of the ticketing market, and the step of automatically transferring the third ticket to the first user.; Claim 2 A method according to claim 1, wherein the step of determining that the set of exchange conditions is satisfied comprises: obtaining at least one user preference associated with the set of exchange conditions by the system of the ticketing market; and comparing the first value of the first ticket obtained by the first user with the second value of the third ticket. Claim 3 A method according to claim 1, wherein the exchange for the third ticket and the first ticket further comprises an additional item, and in response to determining that the third ticket and the additional item satisfy the set of exchange conditions, the additional item is transferred to the first user. Claim 4 In paragraph 3, the method wherein the additional item includes financial incentives, credits for goods, or credits for services. Claim 5 A method according to claim 1, wherein the step of determining that the third ticket satisfies the set of exchange conditions comprises: transmitting a notice requesting permission for the set of exchange conditions to the device associated with the first user; and receiving approval from the first user through the device associated with the first user to perform the transfer of the first ticket from the first user to the second user and the transfer of the third ticket to the first user. Claim 6 A method according to claim 1, wherein the step of determining the set of exchange conditions comprises presenting a list of potential exchange conditions to the first user through the device associated with the first user. Claim 7 In paragraph 6, the list of potential exchange conditions comprises a list of multiple alternative seat sections having available seats determined to be comparable in value to the seat corresponding to the first ticket, wherein the alternative seat sections are selectable by the first user as an indication of the first user's intention to exchange the seat corresponding to the first ticket for an available seat in one of the alternative seat sections. Claim 8 A system for a ticketing market comprises: a non-transient memory configured to store instructions; and one or more processors configured to execute the instructions from the non-transient memory to cause the system to perform operations, wherein the operations include: an operation of obtaining data associated with a first transaction for obtaining a first ticket by a first user; an operation of notifying the first user that the first user is the owner of the first ticket; an operation by which the system for the ticketing market causes a device associated with the first user to display a graphic control element for the first user to select an option for a negotiable transfer of the first ticket to a second user; and, after notifying the first user that the first user is the owner of the first ticket, an operation of obtaining a first indication of the first user's intent to negotiate an exchange of the first ticket from the graphic control element. A system comprising: after notifying the first user that the first user is the owner of the first ticket and after obtaining the first indication of the first user's intent to negotiate the exchange of the first ticket: determining a set of exchange conditions based on a comparison between the first ticket and tickets for available seats; obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user, and obtaining a request from the first user and the second user to exchange the first ticket obtained by the first user for a third ticket; determining that the third ticket satisfies the set of exchange conditions determined based on a comparison between the first ticket and tickets for available seats; and in response to the satisfaction of the set of exchange conditions: automatically transferring the first ticket obtained by the first user to the second user, and automatically transferring the third ticket to the first user. Claim 9 A system according to claim 8, wherein the operation of determining that a set of exchange conditions is satisfied comprises: an operation of obtaining at least one user preference associated with the set of exchange conditions; and an operation of comparing a first value of a first ticket obtained by the first user with a second value of a third ticket. Claim 10 A system in which, in paragraph 8, the exchange for the third ticket and the first ticket further includes an additional item, and in response to determining that the third ticket and the additional item satisfy the set of exchange conditions, the additional item is transferred to the first user. Claim 11 In paragraph 10, the above additional item is a system including financial incentives, credits for goods, or credits for services. Claim 12 A system according to claim 8, wherein the operation of determining that the third ticket satisfies the set of exchange conditions comprises: transmitting a notice requesting permission for the set of exchange conditions to the device associated with the first user; and receiving approval from the first user through the device associated with the first user to perform the transfer of the first ticket from the first user to the second user and the transfer of the third ticket to the first user. Claim 13 A system according to claim 8, wherein the operation of determining the set of exchange conditions includes the operation of presenting a list of potential exchange conditions to the first user through the device associated with the first user. Claim 14 In paragraph 13, the list of potential exchange conditions comprises a list of multiple alternative seat sections having available seats determined to be comparable in value to the seat corresponding to the first ticket, wherein the alternative seat sections are selectable by the first user as an indication of the first user's intent to exchange the seat corresponding to the first ticket for an available seat in one of the alternative seat sections. Claim 15 In paragraph 8, the system comprises a smart device capable of communicating with the ticketing market, wherein the device associated with the first user is a smart device. Claim 16 A non-transient computer-readable medium storing machine-readable instructions that, when executed by a server device, cause the server device to perform operations, wherein the operations include: an operation by which a ticketing market system obtains data associated with a first transaction for acquiring a first ticket by a first user; an operation by which a ticketing market system notifies the first user that the first user is the owner of the first ticket; an operation by which a device associated with the first user displays a graphic control element for the first user to select an option for a negotiable transfer of the first ticket to a second user; and, after notifying the first user that the first user is the owner of the first ticket, an operation by which a ticketing market system obtains from the graphic control element a first indication of the first user's intent to negotiate an exchange of the first ticket. After notifying the first user that the first user is the owner of the first ticket and obtaining the first indication of the first user's intent to negotiate the exchange of the first ticket: an action of determining a set of exchange conditions by the ticketing market system and based on a comparison between the first ticket and tickets for available seats; an action of obtaining a second ticket corresponding to a seat adjacent to the seat corresponding to the first ticket obtained by the first user by the ticketing market system, and obtaining a request from the first user and the second user to exchange the first ticket obtained by the first user for a third ticket; an action of determining by the ticketing market system that the third ticket satisfies the set of exchange conditions determined based on a comparison between the first ticket and tickets for available seats;and in response to the satisfaction of the set of the above exchange conditions: an operation by the system of the ticketing market to automatically transfer the first ticket obtained by the first user to the second user, and an operation to automatically transfer the third ticket to the first user. A non-transient computer-readable medium comprising: Claim 17 A non-transient computer-readable medium, wherein, in paragraph 16, the operation of determining that the set of exchange conditions is satisfied comprises: the operation of obtaining at least one user preference associated with the set of exchange conditions by the system of the ticketing market; and the operation of comparing the first value of the first ticket obtained by the first user with the second value of the third ticket. Claim 18 A non-transient computer-readable medium in which, in response to determining that the third ticket and the first ticket exchange further include additional items, and that the additional items are transferred to the first user, the exchange for the third ticket and the additional items satisfy the set of exchange conditions. Claim 19 In paragraph 18, the additional item is a non-transient computer-readable medium comprising financial incentives, credits for goods, or credits for services. Claim 20 In paragraph 16, the operation of determining the set of exchange conditions comprises presenting a list of potential exchange conditions to the first user through the device associated with the first user, in a non-transient computer-readable medium.

Images