Method of live event ticketing with prioritized link for seating rearrangement
A system and method for reassignment of tickets in a live event via network communications for scheduling data transfers between systems. One or more data requesting systems may request access to particular data for one or more tickets to a venue for the live event causing a task to be performed to exchange the particular data between a data accessing system having access to the particular data and a data requesting system requesting access to the particular data. In some embodiments, the communication exchange may be initiated based on a parameter included in the request that the task be performed.
1 . A computer-implemented method for reassignment of tickets to a live event, comprising:
receiving a first communication from a mobile device associated with a user, wherein:
the first communication corresponds to a request for one or more tickets to a venue for the live event, and
the request includes a ticketing constraint;
querying, in response to the request, a data store for a first set of tickets of a plurality of tickets that satisfy the ticketing constraint, wherein the first set of tickets includes an assigned ticket that was previously assigned to a plurality of ticketholders;
identifying, based on cached ticket data stored in the data store, availability and status of the first set of tickets, wherein the cached ticket data is updated based on periodic communications with a data management server farm;
accessing a user profile of the user retained in one or more repositories, wherein the user profile includes historical purchase data of the user;
determining buying parameters of the user based on the historical purchase data of the user, wherein the buying parameters of the user includes value range of one or more tickets;
altering parameters of the first set of tickets based on the buying parameters of the user;
selecting a ticketholder of the plurality of ticketholders based on the buying parameters for the user;
determining a second set of tickets from the first set of tickets for reassignment to the user, wherein:
the second set of tickets is associated with the selected ticketholder, and
the second set of tickets is determined based on the buying parameters of the user;
verifying, prior to reassignment, that the second set of tickets remain available for reassignment based on updated ticket information retrieved from the data management server farm; and
transmitting a second communication to the mobile device of the user comprising a notification that indicates the reassignment of the second set of tickets to the user.
2 . The method of claim 1 , wherein the assigned ticket is represented by a unique identifier code.
3 . The method of claim 1 , wherein each ticket of the first set of tickets enables access to a spatial area associated with the venue during a defined time period of the live event.
4 . The method of claim 1 , wherein the buying parameters includes one or more of: a type of the one or more tickets requested by the user, a number of the one or more tickets requested by the user, and a price of the one or more tickets requested by the user.
5 . The method of claim 1 , further comprising:
determining a price for the second set of tickets, wherein the price is determined based on time remaining before the live event.
6 . The method of claim 5 , wherein the price for the second set of tickets is further determined based on the user profile.
7 . The method of claim 1 , wherein each of the second set of tickets are associated with a first identification reference.
8 . The method of claim 7 , further comprising:
invalidating the first identification reference for each of the second set of tickets after the reassignment; and
assigning a second identification reference to each of the second set of tickets.
9 . A system for reassignment of tickets to a live event, comprising:
one or more processors; and
a non-transitory computer-readable storage medium containing instructions which, when executed on the one or more processors, cause the one or more processors to perform operations including:
receive a first communication from a mobile device associated with a user, wherein:
the first communication corresponds to a request for one or more tickets to a venue for the live event, and
the request includes a ticketing constraint;
query, in response to the request, a data store for a first set of tickets of a plurality of tickets that satisfy the ticketing constraint, wherein the first set of tickets includes an assigned ticket that was previously assigned to a plurality of ticketholders;
identify, based on cached ticket data stored in the data store, availability and status of the first set of tickets, wherein the cached ticket data is updated based on periodic communications with a data management server farm;
access a user profile of the user retained in one or more repositories, wherein the user profile includes historical purchase data of the user;
determining buying parameters of the user based on the historical purchase data of the user, wherein the buying parameters of the user includes value range of one or more tickets;
alter parameters of the first set of tickets based on the buying parameters of the user;
select a ticketholder of the plurality of ticketholders based on the buying parameters for the user;
determine a second set of tickets from the first set of tickets for reassignment to the user, wherein:
the second set of tickets is associated with the selected ticketholder, and
the second set of tickets is determined based on the buying parameters of the user;
verify, prior to reassignment, that the second set of tickets remain available for reassignment based on updated ticket information retrieved from the data management server farm; and
transmit a second communication to the mobile device of the user comprising a notification that indicates the reassignment of the second set of tickets to the user.
10 . The system of claim 9 , wherein the assigned ticket is represented by a unique identifier code.
11 . The system of claim 9 , wherein each ticket of the first set of tickets enables access to a spatial area associated with the venue during a defined time period of the live event.
12 . The system of claim 9 , wherein the buying parameters includes one or more of: a type of the one or more tickets requested by the user, a number of the one or more tickets requested by the user, and a price of the one or more tickets requested by the user.
13 . The system of claim 9 , wherein the processors are further configured to:
determine a price for the second set of tickets, wherein the price is determined based on time remaining before the live event.
14 . The system of claim 13 , wherein the price for the second set of tickets is further determined based on the user profile.
15 . The system of claim 9 , wherein each of the second set of tickets is associated with a first identification reference.
16 . The system of claim 15 , further configured to:
invalidate the first identification reference for each of the second set of tickets after the reassignment; and
assign a second identification reference to each of the second set of tickets.
17 . A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause a processing apparatus to perform operations for reassignment of tickets to a live event, including:
receiving a first communication from a mobile device associated with a user, wherein:
the first communication corresponds to a request for one or more tickets to a venue for the live event, and
the request includes a ticketing constraint;
querying, in response to the request, a data store for a first set of tickets of a plurality of tickets that satisfy the ticketing constraint, wherein the first set of tickets includes an assigned ticket that was previously assigned to a plurality of ticketholders;
identifying, based on cached ticket data stored in the data store, availability and status of the first set of tickets, wherein the cached ticket data is updated based on periodic communications with a data management server farm;
accessing a user profile of the user retained in one or more repositories, wherein the user profile includes historical purchase data of the user;
determining buying parameters of the user based on the historical purchase data of the user, wherein the buying parameters of the user includes value range of one or more tickets;
altering parameters of the first set of tickets based on the buying parameters of the user;
selecting a ticketholder of the plurality of ticketholders based on the buying parameters for the user;
determining a second set of tickets from the first set of tickets for reassignment to the user, wherein:
the second set of tickets is associated with the selected ticketholder, and
the second set of tickets is determined based on the buying parameters of the user;
verifying, prior to reassignment, that the second set of tickets remain available for reassignment based on updated ticket information retrieved from the data management server farm; and
transmitting a second communication to the mobile device of the user comprising a notification that indicates the reassignment of the second set of tickets to the user.
18 . The computer-program product of claim 17 , wherein the assigned ticket is represented by a unique identifier code.
19 . The computer-program product of claim 17 , wherein each ticket of the first set of tickets enables access to a spatial area associated with the venue during a defined time period of the live event.
20 . The computer-program product of claim 17 , wherein the buying parameters includes one or more of: a type of the one or more tickets requested by the user, a number of the one or more tickets requested by the user, and a price of the one or more tickets requested by the user.