Digital securitization, obfuscation, policy and commerce of event tickets
AssigneeLive Nation Entertainment, Inc.
InventorSanzib KHAUND
Life of this patent
Estimating the term…
Abstract
The present disclosure provides systems and methods that may convert traditional tickets into secure digital assets protected by cryptographic public/private keys that deploy these tickets on a blockchain. By structuring these tickets as smart digital contracts, such system can act as a self-policing escrow while simultaneously allowing ticket issuers greater control over the tickets after the tickets leave the ticket issuers' possession. The system can incorporate specific capabilities into the digital assets to provide an increased level of multiple ownership, security granularity, and sales restrictions in ticket transactions.
Claims20
A computer-implemented method for creating a digital ticket for an event, the method comprising:
- creating a template for a ticket for the event, wherein:
- the ticket is a physical ticket, and
- the template for the ticket comprises a set of policies for:
- distribution, transfer, and redemption of the ticket,
- managing ownership of the ticket,
- managing access for the ticket, and
- restricting one or more parameters associated with the ticket,
- extracting data from the ticket, wherein the data includes the one or more parameters associated with the ticket;
- associating the data extracted from the ticket with a unique identifier of the event;
- verifying if a copy of the ticket exists;
- creating bytecodes and application binary interface (ABI) based on the template of the ticket, if the copy of the ticket does not exist;
- creating the digital ticket using the bytecodes and the ABI;
- deploying the digital ticket to a blockchain system;
- receiving a request to unlock the ticket along with a current location of the ticket and a time left for starting the event and passing the request to the ABI;
- and
- unlocking the ticket when the ticket is within a geofence of the event and a predetermined time is left for the event to begin.
A non-transitory computer-readable storage medium having stored thereon instructions for creating a digital ticket for an event, the instructions comprising:
- creating a template for a ticket for the event, wherein:
- the ticket is a physical ticket, and
- the template for the ticket comprises a set of policies for:
- distribution, transfer, and redemption of the ticket,
- managing ownership of the ticket,
- managing access for the ticket, and
- restricting one or more parameters associated with the ticket,
- extracting data from the ticket, wherein the data includes the one or more parameters associated with the ticket;
- associating the data extracted from the ticket with a unique identifier of the event;
- verifying if a copy of the ticket exists;
- creating bytecodes and application binary interface (ABI) based on the template of the ticket, if the copy of the ticket does not exist;
- creating the digital ticket using the bytecodes and the ABI;
- deploying the digital ticket to a blockchain system;
- receiving a request to unlock the ticket along with a current location of the ticket and a time left for starting the event and passing the request to the ABI;
- and
- unlocking the ticket when the ticket is within a geofence of the event and a predetermined time is left for the event to begin.
A system for creating a digital ticket for an event, the system comprising:
- one or more processors;
- and
- memory coupled with the one or more processors, the memory configured to store instructions that when executed by the one or more processors cause the one or more processors to:
- create a template for a ticket for the event, wherein:
- the ticket is a physical ticket, and
- the template for the ticket comprises a set of policies for:
- distribution, transfer, and redemption of the ticket,
- managing ownership of the ticket,
- managing access for the ticket, and
- restricting one or more parameters associated with the ticket,
- extract data from the ticket, wherein the data includes the one or more parameters associated with the ticket;
- associate the data extracted from the ticket with a unique identifier of the event;
- verify if a copy of the ticket exists;
- create bytecodes and application binary interface (ABI) based on the template of the ticket, if the copy of the ticket does not exist;
- create the digital ticket using the bytecodes and the ABI;
- deploy the digital ticket to a blockchain system;
- receive a request to unlock the ticket along with a current location of the ticket and a time left for starting the event and passing the request to the ABI;
- and
- unlock the ticket when the ticket is within a geofence of the event and a predetermined time is left for the event to begin.
Dependencies are inferred from the claim text.