Decentralized virtual trustless ledger for access control

US9792742B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9792742-B2
Application numberUS-201715423452-A
CountryUS
Kind codeB2
Filing dateFeb 2, 2017
Priority dateFeb 2, 2016
Publication dateOct 17, 2017
Grant dateOct 17, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Described are systems and techniques for leveraging a virtual distributed trustless database using access-enabling codes. The computations use private codes. Each computation includes the information from all previous computations so that a chain of computations is maintained and controlled. A central system insures that dual computations do not occur.

First claim

Opening claim text (preview).

What is claimed: 1. A distributed virtual trustless database based access control system for controlling access to venue events comprising: a processor based ticket access coordinator that performs actions of: defining specifications for a ticket, wherein the ticket is related to a venue event; allocating access rights for the ticket based on the specifications; linking the access rights for the ticket to a trustless database computation; publishing the access rights for the ticket; using the trustless database computation to perform: assigning the access rights for the ticket to a requestor; and generating access-enabling codes for the ticket for the requestor using a private code; and granting access authorization to the venue event upon presentation of the access-enabling codes; one or more servers that perform the actions of: receiving a request for the access rights for the ticket from a requester device; receiving the private code from the requester device; receiving payment authorization for the access rights from an intermediate system, wherein the payment authorization is related to: a payment card account; and/or payment information associated with an account linked to the requester device; transmitting a confirmation of assignment for the access rights to the requester device; and transmitting the access-enabling codes to the requester device. 2. The distributed virtual trustless database based access control system for controlling access to venue events of claim 1 , wherein the private code is based in part on a requestor's signature or digital biometric information. 3. The distributed virtual trustless database based access control system for controlling access to venue events of claim 2 , wherein the digital biometric information includes facial image, fingerprint, voice print or, retina scan. 4. The distributed virtual trustless database based access control system for controlling access to venue events of claim 1 , wherein a centralized access-enabling code verification system limits access to the venue event to a single access-enabling codes holder for any period of time. 5. The distributed virtual trustless database based access control system for controlling access to venue events of claim 1 , wherein the processor based ticket access coordinator further performs actions of: using the trustless database computation, that performs: assigning the access rights for the ticket to a second requestor; and generating second access-enabling codes for the access rights for the second requestor using a second private code; and granting access to the venue event upon presentation of the second access-enabling codes. 6. The distributed virtual trustless database based access control system for controlling access to venue events of claim 5 , wherein the second private code is based in part on a second requestor's signature or digital biometric information. 7. The distributed virtual trustless database based access control system for controlling access to venue events of claim 1 , wherein a distributed virtual trustless database uses colored bitcoin, access tokens, or access token identifiers. 8. A processor based distributed virtual trustless database based access control method for controlling access to venue events comprising: defining specifications for a ticket, wherein the ticket is related to a venue event; allocating access rights for the ticket based on the specifications; linking the access rights for the ticket to a trustless database computation; publishing the access rights for the ticket; using the trustless database computation to perform the steps of: assigning the access rights for the ticket to a requestor; and generating access-enabling codes for the access rights for the requestor using a private code; and granting access authorization to the venue event upon presentation of the access-enabling codes; receiving a request for the access rights for the ticket from a requester device; receiving the private code from the requester device; receiving payment authorization for the access rights from an intermediate system, wherein the payment authorization is related to: a payment card account; and/or payment information associated with an account linked to the requester device; transmitting a confirmation of assignment for the access rights to the requester device; and transmitting the access-enabling codes to the requester device. 9. The processor based distributed virtual trustless database based access control method for controlling access to venue events of claim 8 , wherein the private code is based in part on a requestor's signature or digital biometric information. 10. The processor based distributed virtual trustless database based access control method for controlling access to venue events of claim 9 , wherein the digital biometric information includes facial image, fingerprint, voice print or, retina scan. 11. The processor based distributed virtual trustless database based access control method for controlling access to venue events of claim 8 , wherein a centralized access-enabling code verification system limits access to the event venue to a single access-enabling codes holder for any period of time. 12. The processor based distributed virtual trustless database based access control method for controlling access to venue events of claim 8 , further comprising: using the trustless database computation to perform the steps of: assigning the access rights for the ticket to a second requestor; and generating second access-enabling codes for the access rights for the second requestor using a second private code; and granting access to the venue event upon presentation of the second access-enabling codes. 13. The processor based distributed virtual trustless database based access control method for controlling access to venue events of claim 12 , wherein the second private code is based in part on a second requestor's signature or digital biometric information. 14. The processor based distributed virtual trustless database based access control method for controlling access to venue event s of claim 8 , wherein a distributed virtual trustless database uses colored bitcoin, access tokens, or access token identifiers. 15. A non-transitory computer-readable medium having sets of instructions stored thereon for a distributed virtual trustless database based access control for controlling access to venue events, that when executed by a computer, cause the computer to perform actions including: defining specifications for a ticket, wherein the ticket is related to a venue event; allocating access rights for the ticket based on the specifications; linking the access rights for the ticket to a trustless database computation; publishing the access rights for the ticket; using the trustless database computation to perform the steps of: assigning the access rights for the ticket to a requestor; and generating access-enabling codes for the access rights for the requestor using a private code; and granting access authorization to the venue event upon presentation of the access-enabling codes; receiving a request for the access rights for the ticket from a requester device; receiving the private code from the requester device; receiving payment authorization for the access rights from an intermediate system, wherein the payment authorization is related to: a payment card account; and/or payment information associated with an account linked to the requester device; transmitting a confirmation of assignment for the ac

Assignees

Inventors

Classifications

  • G07C9/257Primary

    electronically (G07C9/26 takes precedence) · CPC title

  • G06Q10/02Primary

    Reservations, e.g. for tickets, services or events · CPC title

  • using payment protocols involving tickets · CPC title

  • Location-sensitive, e.g. geographical location, GPS · CPC title

  • using e-cash · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9792742B2 cover?
Described are systems and techniques for leveraging a virtual distributed trustless database using access-enabling codes. The computations use private codes. Each computation includes the information from all previous computations so that a chain of computations is maintained and controlled. A central system insures that dual computations do not occur.
Who is the assignee on this patent?
Live Nation Entertainment Inc
What technology area does this patent fall under?
Primary CPC classification G07C9/257. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Oct 17 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).