System and method for providing temporary access credentials for accessing a physical location - Patents.com
The digital access rights locker system addresses the challenge of managing temporary access to physical locations by securely transferring and tracking access rights through a network interface, ensuring authorized access and reducing the need for physical tokens.
Patent Information
- Application Number
- JP2023047794
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-11-07
- Filing Date
- 2023-03-24
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2043-03-24
AI Technical Summary
Existing systems lack efficient methods for providing dynamic and secure temporary access to physical locations, such as event venues, without the need for physical tickets or tokens, while ensuring security and preventing unauthorized access.
A digital access rights locker system that manages and tracks temporary access rights using a network interface, enabling secure transfer and loan of access rights through a distributed database, multi-factor authentication, and smart contracts to ensure authorized access for specified periods or events.
Enables secure, efficient, and flexible management of temporary access rights, reducing the risk of unauthorized use and enhancing security by eliminating the need for physical tokens, while allowing dynamic access control and tracking of access rights.
Smart Images

Figure 0007577780000001 
Figure 0007577780000002 
Figure 0007577780000003
Abstract
Description
[Technical field]
[0001] (Incorporation by reference of priority application) All applications for which a foreign or domestic priority claim is identified in the Application Data Sheet filed with this application are hereby incorporated by reference under 37 CFR 1.57.
[0002] (Copyright Notice) A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of this patent document and / or the patent disclosure as it appears in the U.S. Patent and Trademark Office patent files and / or records, but otherwise reserves all copyrights.
[0003] FIELD OF THE DISCLOSURE The present disclosure relates generally to systems and methods for providing access to physical locations. [Background technology]
[0004] Description of Related Art Electronic access control to physical locations is becoming increasingly important in providing efficient user access while at the same time securing the location by excluding unauthorized persons from the location. Summary of the Invention
[0005] The following presents a simplified summary in order to provide a basic understanding of one or more aspects. This summary is not an extensive overview of all contemplated aspects, and is not intended to identify key or critical elements of all aspects or to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0006] One aspect of the disclosure relates to a physical location access control system configured to receive, via a network interface, a request from a requester to provide a first user with temporary access to a first physical location, the request from the requester providing an indication regarding a first time period associated with the temporary access, and determine whether the requester has access to the first location for a second time period that includes the first time period. In response to determining that the requester has access to the first physical location for the second time period that includes the first time period, a temporary access token corresponding to the first time period is created and the requester's access to access the first physical location for the first time period is revoked. The temporary access token is transmitted to a device associated with the first user and enables the first user to access the first physical location for the first time period.
[0007] One aspect of the disclosure relates to a physical location access control system including a network interface and at least one processing device operable to receive, via the network interface, a request from an access controller to provide temporary access to a first user to a first physical location, the request from the access controller providing an indication regarding a first time period associated with the temporary access right, determine whether the access controller is authorized to provide temporary access to the first physical location to the first user for the first time period, and, in response at least in part to determining that the access controller is authorized to provide temporary access to the first physical location to the first user for the first time period, create a temporary access record corresponding to the first time period, revoke the access controller's access to access the first physical location for the first time period, send a message corresponding to the temporary access record to a destination associated with the first user, and enable access by the first user to the first physical location for the first time period, optionally without a token corresponding to the temporary access right.
[0008] One aspect of the present disclosure relates to a computer-implemented method, the method including the steps of: receiving, in a computer system, a request from an access rights controller having a set of access rights including a reclaimable first access right associated with a first physical location to provide a first access right reclaimable by the access rights controller for a first time period to the first user via a network interface; recording instructions in a database regarding providing the reclaimable first access right to the first user in response at least in part to the request from the access rights controller; disabling the ability of the access rights controller to utilize the reclaimable first access right associated with the first physical location; receiving a reclaim request for the first access from the access rights controller via a network; determining whether the reclaimable access right is currently reclaimable; in response at least in part to determining that the reclaimable access right is currently reclaimable, recording instructions in the database regarding reclaiming the reclaimable first access right and enabling the access rights controller to utilize the reclaimable first access right associated with the first physical location; and disabling the ability of the first user to utilize the reclaimable first access right associated with the first physical location.
[0009] One aspect of the disclosure relates to a non-transitory computer-readable memory storing instructions that, when executed by a computer system including one or more computing devices, cause the computer system to perform operations including receiving a request from a requester at a first time to provide a first user with retrievable access rights to a first physical location for a first event, determining whether the requester is authorized to provide the first user with retrievable access rights to the first physical location for the first event, and, in response at least in part to determining that the requester is authorized to provide the first user with retrievable access rights to the first physical location for the first event, creating an access provision record corresponding to providing the first user with retrievable access rights to the first event, revoking the requester's access rights to access the first physical location for the first event, sending a message corresponding to the access provision record to a destination associated with the first user, and optionally enabling the first user to access the first physical location for the first event in the absence of a token corresponding to the retrievable access rights. [Brief description of the drawings]
[0010] Embodiments will now be described with reference to the drawings summarized below. These drawings and the associated description are provided to illustrate exemplary aspects of the disclosure and are not intended to limit the scope of the invention. [Figure 1A] FIG. 1A illustrates an example of a network environment architecture. [Figure 1B] FIG. 1B illustrates an example of a system architecture. [Diagram 2] FIG. 2 shows an example of the process. [Diagram 3] FIG. 3 shows an example of the process. [Figure 4] FIG. 4 shows an example of the process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] One aspect of the present disclosure relates to methods and systems for providing dynamic and temporary access to resources, such as physical locations, for specified periods of time and / or for specified events. Digital access rights lockers can be utilized to store data indicative of users' access rights to physical locations, physical objects, and / or other rights, as well as the status of such rights.
[0012] A given access right may include subordinate access rights to physical locations, physical objects, and / or other rights. For example, a top-level access right may provide a user with access to multiple related events (e.g., multiple concerts or multiple sporting events, such as in the case of a season subscription to multiple events) at one or more physical locations / venues. A subordinate access right may be to a single event among multiple events at a single physical location (e.g., a single sporting event, such as in the case of a season ticket that includes tickets to a single sporting event), and / or a subordinate access right may include access to a specified time period (including start and / or stop dates and times) that may include one or more events at one or more physical locations. A subordinate access right may be to a portion of an event at a physical location, or to access to a special restricted area (e.g., a restaurant or VIP section) within a physical location to a given event.
[0013] A user (sometimes called an access control owner or access controller) may be able to loan / transfer one or more access rights (e.g., a top-level access right, a lower access right, a further lower access right, etc.) to another user (sometimes called a recipient or receiving user).
[0014] Thus, for example, the transfer or loan of access rights may be related to a start time (which may be a date and optionally a specific start time on that day) and an end time. Optionally, the transfer or loan of access rights may be related to a start time (which may be a date and optionally a specific start time on that day) and not an end time, but the access credential owner may revoke the transfer at any time or according to specified revocation rules. Optionally, the transfer or loan of access rights may be related to a start event (which may be a specific event in a season, such as a sports season) and an end event (which may be a specific subsequent event in that season), and may include all events in between. Optionally, the transfer or loan may include multiple access rights to a given event (e.g. multiple tickets that may be used by multiple attendees of the event). Thus, the transfer or loan of a specific access right may be temporary in nature and may be in the form of a loan of access rights. Optionally, the access control owner may be enabled to reclaim any loaned rights at any time. Optionally, the access control owner may be inhibited from reclaiming specific or any loaned rights. For example, optionally, an access right owner may be prevented from reclaiming access rights once loaned, but the recipient of the access rights may choose to return the loaned access rights (e.g., upon request from the access right owner, etc.).
[0015] As discussed above, a given access right may be to an event, such as a ticketed event (e.g., a musical performance, a sporting event, a movie, a play, an art exhibit, etc.), at a physical location, such as a venue (e.g., a stadium, a concert hall, a theater, a field, etc.). Additionally, the access right may be to a particular location within the venue, such as a particular seat (e.g., associated with a seat section, row, and seat number) and / or a VIP section. However, in addition or instead, the access right may be to a physical item, such as food or clothing.
[0016] Advantageously, such access rights can be optionally transferred or loaned without the need to transfer or loan an access credential or key to a receiving user device or electronic address (e.g., email address, messaging address, or other such address) or to print a physical ticket. Because a given access right is transferred or loaned without the need to transfer or loan an access credential or key to a receiving user device or electronic address, the security of the access right is greatly improved, as there is no opportunity for the access right to be intercepted or misused.
[0017] Instead, the transfer or loan is recorded in a digital access rights locker, which may optionally be in the form of a database record maintained by the access control system. As will be described, the access control system may optionally utilize a synchronous distributed database to store the record. The database record may include an identifier associated with the access rights owner (e.g., the user who originally purchased or owned the ticket) and any recipient of the transfer or loan of the access rights from the access rights owner. For example, a given access right may be associated with a logical toggle that indicates whether the access rights owner has retained use of the given access rights or whether the access rights owner has transferred or loaned the given access rights to a recipient. If the toggle indicates that the given access rights have been transferred or loaned, a corresponding recipient identifier may be stored in association with the toggle. In this way, the recipient of the access rights may be enabled to utilize the access rights (e.g., gain admission to an event) even in the absence of an access rights token such as a physical or electronic ticket. At the same time, the access rights owner's ability to utilize the access rights may be disabled.
[0018] As discussed above and elsewhere herein, optionally, the access rights holder may reclaim certain access rights that have been loaned to other users. Optionally, if the access rights holder has not reclaimed certain loaned or transferred access rights, the access rights holder may be inhibited from using the loaned or transferred access rights. For example, if the access rights holder presents a certificate or biometric to access an event to which the access rights holder has loaned the corresponding access rights, the disclosed system may utilize the access rights holder's records using the presented certificate or biometric. The system may then determine from the access rights holder's records that the access rights have been loaned and transmit instructions to an indicator (e.g., an indicator display and / or a sound emitting device) at the event venue to present an indication that the access rights holder is denied entry. Optionally, if the access rights holder reclaims the loaned access rights, a determination may be made as to whether the recipient of the loaned access rights has already used the access rights to access the venue. If a determination is made that the recipient of the loaned access rights has already used the access rights to access the venue, the access rights holder may be inhibited from reclaiming the access rights and entry to the event venue may be inhibited.
[0019] As an example, if it is determined that the recipient of the loaned access rights has not yet used the access rights to the event venue, the access rights owner may be allowed to reclaim the access rights and allowed to enter the event venue. If it is determined that the recipient of the loaned access rights has used the access rights to the event venue, the access rights owner may be restrained from reclaiming the access rights and restrained from entering the event venue. As a further example, if it is determined that the period before the event during which the loaned access rights allow access is greater than a predetermined threshold period, the access rights owner may be allowed to reclaim the loaned access rights. If it is determined that the period before the event during which the loaned access rights allow access is less than a predetermined threshold period, the access rights owner may be restrained from reclaiming the loaned access rights and restrained from entering the event venue.
[0020] The revocation of access rights may be recorded via a toggle in the corresponding database record. A notification may be sent to the recipient of the loaned (and now revoked) access rights indicating that the access rights have been revoked and are no longer available to the recipient. For example, the notification may be sent to an electronic address (e.g., email address, message service address) associated with the recipient and / or presented in an application configured to provide the access rights. Additionally, the recipient may be restrained from using the loaned access rights to enter the event venue. For example, the system may determine from the access rights owner's records that the access rights have been revoked, and the system may send instructions to an indicator at the event venue to present an indication that the recipient is denied entry.
[0021] To illustrate, an attendee and / or a device associated with an attendee may be identified by physical location. For example, an attendee may be identified using biometrics (e.g., a fingerprint, facial print data, iris print, etc.), optical indicia displayed on a user device (e.g., an optical code such as a QR code or other barcode, etc.), audible indicia generated by a speaker on the attendee device, radio frequency signals from the attendee device, and / or others. By way of example, an attendee device may be a smartphone, a wearable computing device (e.g., a smart watch, a smart badge, smart glasses, smart clothing, smart jewelry, etc.), a tablet computer, or other portable computing device or token.
[0022] Once an attendee is identified, the access rights, including corresponding access rights owned by the attendee or transferred or loaned to the attendee, may be retrieved and a determination may be made as to whether the owned, transferred, or loaned access rights (if any) entitle the attendee to gain access to the physical location at the current time (e.g., the current event). In response to determining that the owned, transferred, or loaned access rights (if any) entitle the attendee to gain access to the physical location at the current time (e.g., the current event), a signal may be generated to allow the attendee to access the physical location.
[0023] As described elsewhere herein, the signal may be used to provide a human-perceivable "access granted" indication in the form of a visible light indicator, an audible sound, and / or tactile feedback. Additionally or alternatively, the signal may cause a barrier to be unlocked and / or opened that provides attendees access to the physical location.
[0024] Optionally, multi-factor authentication consisting of multiple credentials and geographic location verification may be used to verify that a given attendee has gained a given access right at a given physical location. Multi-factor authentication enhances security by requiring two or more credentials of different types to access a resource (e.g., entry to a site such as an event venue). As described, optionally, the credentials may include a unique user identifier and a unique user device identifier, which may need to be presented at a particular geographic location (e.g., an entrance to a venue or a particular set of venue entrances, such as a seating area).
[0025] A user may obtain, transfer or lend, or be transferred or loaned, event access rights for one or more attendees. Optionally, rather than providing the user with a physical ticket, or a downloaded ticket or access token stored on the user device, as described above, the user's right to access a site (e.g., an event venue) may be enforced using multi-factor authentication, which advantageously does not require the user device to be connected to a network. For example, the user's right to access an event venue (or a portion thereof) may optionally be enforced by authenticating the user equipment and user to a particular location (e.g., a subset of the event venue or venue / seating area entrances).
[0026] For example, an application configured to allow a user to access an event at a venue may be downloaded from an application store (sometimes referred to as an app store) or other source and installed on a user device. Optionally, the same application may be used to manage electronic tokens. For example, the application may also include access to a wallet (sometimes referred to as a logical storage module) configured to store fungible tokens (sometimes referred to as non-unique digital elements herein, NDEs) and non-fungible tokens (sometimes referred to as unique digital elements herein, UDEs). A user may register an account with an access control system configured to manage and control event access. A user account may include authentication credentials, such as a unique identifier associated with the user and / or a unique identifier associated with the user device. The unique identifier associated with the user device may optionally be an identifier other than or in addition to a phone number associated with the user device, thereby making impersonation more difficult. A unique user device identifier, optionally used to perform multi-factor authentication, may or may not be assigned to the user device by the access control system.
[0027] For example, the user device identifier may include one or more of the following: a 14-digit International Mobile Equipment Identity (IMEI) number, a Unique Device ID (UDID) consisting of a 40-digit sequence of letters and numbers, a serial number, an ID for advertisers (IDFA), or a Google® Advertiser ID (GAID). Optionally, the access control system may embed a unique identifier in an application downloaded to the user device, which is then used as the unique device identifier.
[0028] A unique user identifier (optionally used for multi-factor authentication) may or may not be assigned to the user by the access control system. For example, the user may provide a user identifier and the system may search a database of user identifiers. If the system detects that the user identifier is associated with another user or user account, the user may be prompted by the system to select another user identifier. This process may be repeated until the user specifies what is determined to be a unique user identifier. Optionally, in addition or instead, the system may generate a unique user identifier and transmit the assigned unique user identifier to the user device. Applications hosted on the user device may utilize the unique device identifier and use it during the authentication / verification process described herein. Optionally, applications hosted on the user device may or may not present the unique user device identifier and / or user identifier to the user in a human readable form (using alphanumeric or ASCII characters). Thus, the user may be unaware of the actual value of the user device identifier and / or user identifier.
[0029] When a user arrives at a venue entrance (which may be an initial entrance to a venue building or area, or an internal entrance to a particular seat or other area within the venue, such as a VIP area), the user device may present a unique user device identifier and / or user identifier, optionally encoded (e.g., encrypted and converted from the digital domain to a light, radio frequency, and / or audio representation), to a venue scanner. For example, the user device may present (e.g., via an application provided on the user device) a unique user device identifier and / or user identifier and a timestamp of the current time encoded into a visual indicia (e.g., a barcode such as a QR code or linear barcode), encoded into an electronic signal (e.g., via Bluetooth, Wifi, NFC, etc.), and / or encoded in an audio signal. The timestamp may prevent other users from taking a screenshot or other record of the data presented by the user and transferring the screenshot or other record to other user devices and attempting to use the screenshot or other record to gain access to the event, since the timestamp of the screenshot or other record may no longer reflect the current time.
[0030] The user device application may periodically (e.g., every 5, 10, 15, or 30 seconds) update the presentation data and update the timestamp to approximately the current time. The unique user device identifier and / or user identifier, (and optionally the timestamp) may be encrypted using a hash code, using symmetric encryption, using asymmetric encryption, or in other ways.
[0031] For example, one may use the Advanced Encryption Standard (AES), which is a symmetric encryption algorithm that encrypts a fixed block of data (128 bits) at a time. AES utilizes a substitution network and may have a fixed block size (e.g., 128 bits) and a key size of 128, 192, or 256 bits.
[0032] As a further example, the Rivest-Shamir-Adleman (RSA) encryption / decryption technique may be used. RSA is a public key cryptosystem, where the encryption key is made public and the decryption key is kept private. RSA users may create and publish public keys (based on a large prime number and an auxiliary value, where the prime number is kept private / secret). Data may be encrypted by anyone with the public key, but only decrypted by someone who knows the private key (the prime number). Additionally, the Triple Data Encryption Standard (DES) encryption / decryption technique may be used (optionally in conjunction with AES). Triple DES applies a block cipher algorithm three times to each data block. Each block contains 64 bits of data. The three keys are used as a bundle key of 56 bits per key. In some forms of DES, all the keys are independent, two of the three keys are independent, or all three keys are identical (Triple DES). Triple DES key lengths include 168 bits, and key security can be 112 bits. As yet another example, a hash function may be used. Hashing changes the plaintext or key to a hashed value by applying a hash function. Optionally, the input length is of a larger size than the output hash value. Hashing provides a one-way encryption process such that the hash value cannot be reverse engineered to obtain the original plaintext or key.
[0033] Thus, the venue scanner may comprise a camera, a laser scanner, a radio frequency receiver, a palm scanner, a microphone device, and / or other device for receiving a unique user device identifier and / or a user identifier.
[0034] The timestamp may also be generated by the venue scanner and / or access control system (or other system) corresponding to the unique user device identifier and / or user identifier and timestamp received by the venue scanner and / or access control system. The venue scanner, either directly or via the access control system (or other system), may decrypt the encrypted unique user device user identifier and / or timestamp and compare the timestamp received from the user device with that generated by the venue scanner and / or system. If the timestamps do not match (e.g., exactly match or match within a certain time range, such as 1-15 seconds), the venue scanner or system may indicate an authentication failure.
[0035] If the timestamps are determined to match, the venue scanner, either directly or through an access control system, may compare the unique user device and / or user identifier (or a hash thereof) with those in a user database. If the unique user device and / or user identifier (or a hash thereof) matches that of a user account, a determination may be made as to whether the user account is associated with one or more access rights to the event. If a hash is used, the hash may be, by way of example, an MD5, SHA-1, SHA-256, or other hash. If a public key associated with the system is used to encrypt the user device and / or user identifier (if asymmetric encryption is employed), a private key may be used to decrypt the user device and / or user identifier. If a user device and / or user identifier is encrypted using symmetric encryption, the key used to perform the encryption may be used to perform the decryption.
[0036] The transferred or loaned access rights may be encoded in a token. The access rights token may include data identifying the access rights controller that is loaning the access rights, data identifying the transferred or loaned rights (e.g., access to an event, a location, an associated start time, an associated end time, and / or an associated time period), data indicating the status of the access rights (e.g., transferred, loaned, reclaimed, etc.), and / or data indicating the recipient user. The access rights data may be encrypted using a public key and decrypted using a private key, such as the keys discussed elsewhere herein.
[0037] As described elsewhere herein, by way of example, the transferred or loaned access rights may be for a particular event, all events within a specified time period, all events beginning at a specified start time until the access rights are revoked, or an initial event and a specified subsequent event and all events between the initial event and the subsequent event. Thus, once a user and / or user device is identified at a physical location, a determination may be made as to whether a current event at the physical location where the user and / or user device is identified corresponds to a transferred or loaned access right specifically for the current event, or falls within the time period in which the access rights were transferred or loaned to the user, or falls within the time period in which the access rights were transferred or loaned to the user after the time period in which the access rights were transferred or loaned to the user and before the revocation of the access rights occurs, or falls within the first specified event, a subsequent specified event, or an event between the first specified event and a subsequent specified event.
[0038] If the user account is determined to be associated with one or more access rights to the event (e.g., access rights transferred or loaned by other users as discussed herein), a corresponding authentication / verification indication may be provided via a venue entrance device (e.g., a display device, a sound generating device, an opening gate, etc.) to allow the user to access the event venue. For example, the authentication / verification success indication may include the illumination of a light of a particular color (e.g., green), text (e.g., "Authentication Approved"), a graphic (e.g., a thumbs up symbol), and / or a sound (e.g., a bell sound). Optionally, the number of access rights the user has may be presented via a venue display. For example, a user may have access rights for the user and for certain friends of the user. Optionally, in response to successful authentication / verification, a solenoid, stepper motor, or other electrical or electromechanical device may be actuated to unlock / open a barrier to allow the user (and one or more other users) to enter the venue.
[0039] If it is determined that a user account is not associated with one or more access rights to the event (e.g., purchased rights, transferred or loaned access rights), a corresponding authentication / verification failure indication may be provided via a device at the venue entrance (e.g., a display device, a sound emitting device, a gate that closes or remains closed, etc.). For example, the authentication / verification failure indication may include the illumination of a light of a particular color (e.g., red), text (e.g., "authentication failed"), a graphic (e.g., a prohibition symbol), and / or a sound (e.g., a boing sound).
[0040] Optionally, for a determination to be made that a user is authenticated / verified as having access to an event or a given venue entrance, an identifier associated with the event venue scanner (e.g., in conjunction with a user identifier and a user device identifier) must be received and verified. For example, the user's access rights stored by the system may indicate which venue entrances the user is entitled to pass through (and may explicitly or inferentially indicate which venue entrances the user is not entitled to pass through). Thus, even if the user identifier, user device identifier, and timestamp are verified, if the user does not have access to the venue entrance where the user device was scanned, a corresponding notification may be optionally provided to the venue operator and / or the user, and the user may be denied entry. Optionally, the notification may indicate which venue entrances the user is entitled to access. This optionally ensures that access is provided to certain seating areas of the event venue that the user is entitled to access, and that access is not granted to entrances that provide entry to seating areas to which the user does not have access.
[0041] Optionally, biometric authentication may be provided in addition to or in lieu of one or more of the authentication techniques discussed above (e.g., using a unique user identifier assigned to or provided by the user, a unique device identifier, and / or a venue authentication scanner identifier). For example, a camera may be utilized to capture an image of a user device that may be used to authenticate the user. As a further example, a fingerprint reader may be utilized to read a user's fingerprint for authentication purposes. As yet another example, an iris reader may be utilized to capture a user's iris for authentication. As yet another example, a palm scanner configured to emit infrared or near infrared light to capture a user's vein pattern may be utilized. The user's biometric readings may be compared to stored user readings (which may be associated with corresponding user and device identifiers), and if there is no match, a verification failure indication may be provided, similar to that described above.
[0042] Thus, a user can be authenticated using any multi-factor authentication and a user's right to access an event via a user device can be determined at the venue even if the user device does not have a ticket downloaded to the user device, etc., and the user device does not have Internet access at the venue. Multi-factor authentication can include, for example, two or more of a unique user identifier, a unique user identifier, a timestamp, a biometric reading, or a geographic location of the user (e.g., if the unique user identifier, the unique user identifier, the biometric reading, and / or the timestamp need to be verified at a specific location, i.e., at the event venue).
[0043] Optionally, the transfer or loan of access rights from one user to another can be recorded in a tamper-resistant or tamper-proof database. Optionally, the database can be publicly accessible. Optionally, a record of the transfer or loan of access rights may be stored on a distributed database (e.g., a distributed digital ledger such as a blockchain) that is synchronized and available across different sites and geographies by multiple attendees. The record can include the user identifier and the current state of the access rights (e.g., whether it was loaned, for how long, etc.).
[0044] Optionally, the transfer or lending of access rights can be stored on the distributed digital ledger (e.g., on a synchronous distributed database) in the form of a smart contract, which is a form of computer code executable on the synchronous distributed database. Thus, transactions occurring in the smart contract can be processed by the synchronous distributed database and can occur only if the conditions specified in the smart contract are met. For example, the smart contract can include "if / when...then..." statements that are written into the code on the blockchain. A network of computer systems can execute actions when the predefined conditions are met and verified. The corresponding transaction records can be encrypted, making it very difficult for hackers to exploit such transaction records.
[0045] For example, a synchronous distributed database may store blocks or references to blocks that contain some or all of the following data: data identifying the access rights administrator lending the access rights; data identifying the transferred or loaned rights (e.g., access rights to an event, a location, an associated start time, an associated end time, and / or an associated time period); data indicating the status of the access rights (e.g., transferred, loaned, reclaimed, etc.); and / or data indicating the recipient user. The access rights data may be encrypted using a public key and decrypted using a private key, such as the keys discussed elsewhere herein.
[0046] For example, the access control owner may be presented with a user interface (e.g., via a dedicated application such as a phone app or via a web page presented via a browser) that lists the access rights held by the access control owner (e.g., event tickets, rights to VIP locations, rights to food or merchandise, etc.) and their current status (e.g., loaned, reclaimed from loan, transferred, or in a default state (e.g., never loaned, reclaimed, or transferred)). In response to the access control owner selecting a given access right, various attributes related to the selected access right may be presented (e.g., available loan period, sub-rights available for loan, etc.). The user interface may allow the access right owner to specify parameters related to the loan of the access right (e.g., start time, end time, other parameters discussed herein, and / or the like). Fields may be provided in which the access right owner can specify to whom the access right should be loaned according to the specified parameters. For example, the recipient of the loaned access right may be specified via an electronic address (e.g., an email address, a message service address, or other electronic address) associated with the recipient.
[0047] Optionally, the system can be implemented with access rights lending rules that control which access rights may be loaned, when a given access right may be loaned, how long a given access right may be loaned, how many access rights may be loaned at a given time, how many access rights may be loaned for a given period (e.g., monthly, yearly, etc.), how often a given access right may be loaned, how many access rights loans may be reclaimed for a given period, etc. The user interface through which the access rights owner can select the access rights to loan and the corresponding loan parameters can be pre-configured by the system to indicate which access rights may currently be loaned, which access rights may not currently be loaned, which loan parameters may be selected for a given access right, and / or which loan parameters may not be selected for a given access right. For access rights that are not currently allowed to be loaned, the system can use the access rights owner's loan history and / or based on the access rights lending rules to determine when the access rights owner will be able to loan the access rights. The system can pre-configure the user interface with an indication of the date and / or other conditions that must be met before the access rights owner can loan the access rights.
[0048] Optionally, the access rights holder may be provided by the system with fungible and / or non-fungible tokens as a reminder or other benefit for the loaned access rights. For example, the token may include an image of a ticket for the event to which the loaned access rights correspond, an image of a performer at the event to which the loaned access rights allow access, a graphic, cryptocurrency, or other item. Optionally, the granting of the token may occur in response to the satisfaction of one or more conditions. For example, the token may be granted substantially immediately in response to the loaning of the access rights. As a further example, the token may be granted in response to the recipient of the access rights utilizing the access rights. Additionally, the token may be granted in response to the access rights holder determining that the access rights can no longer be retrieved.
[0049] Certain embodiments will now be described with reference to the figures.
[0050] 1A illustrates an example networked environment that may be utilized to implement the example processes herein. An access control system 102 may communicate via a network 100 (e.g., the Internet, an intranet, a cellular network, and / or other network) with one or more venue systems 104, 106, 108 that may be located (or have components located) at one or more respective venues.
[0051] For example, a given venue system often has a corresponding authentication scanner located at a venue entrance (which may be a venue building entrance or a building entrance to a restricted area). A given authentication scanner may include, by way of example, one or more of a camera configured to capture an image of a user and / or a barcode (e.g., a 1D or 2D barcode such as a QR code) for authentication purposes, a barcode scanner (e.g., a laser barcode scanner configured to scan a barcode), a radio frequency receiver configured to receive a wireless transmission including authentication data from a user device, a microphone configured to receive an audible signal including authentication data from a user device (e.g., user devices 110, 112, 114), a biometric reader (e.g., a fingerprint reader, an iris reader, a palm reader, etc.), and / or other devices for receiving a unique user device and / or user identifier. A given venue system may include a network interface configured to communicate with the multi-factor authentication system 102 and, optionally, other systems over the network 100.
[0052] The access control system 102 may be configured to store and provide access to two-dimensional and / or three-dimensional venue seating charts and event information. For example, the event information may include, for a given event, the event date, the event name (e.g., the name of the performer, the name of the tour, the team name for a sporting event), the event venue, the access token price for the event venue seats / sections, an indication of which seat access tokens have been sold and which are available. The access control system 102 may store user account information, which may include some or all of the following: That is, the user name, user email address, user phone number / SMS / text messaging address, user avatar (which the user may select from among content associated with the user's UDE), geographic information (e.g., physical address, zip code, city, etc.), a unique user identifier (e.g., alphanumeric identifier, fingerprint data, face print data, iris print data, etc.), a unique user device identifier, an event identifier corresponding to an event to which the user has access (including subordinate rights), access rights loaned by the user (optionally including loan date, identification of the event to which the access rights grant access, identification of the event venue for which the access rights were loaned, identification of the event date, and identification of the recipient), access rights loaned to the user (optionally including loan date, access rights loan date, event date, and recipient), the identity of the authorizer); loaned access rights that the user has retrieved (optionally including the date of the loan, the identity of the event to which the retrieved access rights allow access, the identity of the event venue for which the access rights were loaned, the identity of the event date, and the identity of the recipient); user preferences (e.g., favorite performers, favorite venues, favorite musical styles, etc.); UDEs that have been transferred to the user (including an identifier that enables the UDE to be located on a synchronous distributed database); UDEs that the user has re-transferred to another person; fees paid for the UDE; a unique UDE / cryptocurrency e-wallet identifier; and / or other user-related data as disclosed herein.
[0053] The access control system 102 may be configured to authenticate users using authentication data scanned by the venue authentication scanner, similar to that described elsewhere herein. For example, the access control system 102 may use multi-factor authentication in identifying and authenticating users.
[0054] The access control system 102 can also be configured to implement access right loaning rules that control which access rights may be loaned, when a given access right may be loaned, for how long a given access right may be loaned, how many access rights may be loaned at a given time, how many access rights may be loaned in a given period of time (e.g., monthly, yearly, etc.), how often a given access right may be loaned, how many access right loans may be reclaimed in a given period of time, etc. The access control system 102 can also be configured to pre-configure the user interfaces described herein.
[0055] The access control system 102 may also be configured to implement UDE allocation rules, rules controlling a user's right to sell, exchange, or otherwise transfer a UDE, and / or rules controlling the conversion of non-unique digital elements to unique digital elements. For example, the access control system 102 may be configured to implement the rules and allocation processes described elsewhere herein.
[0056] The access control system 102 can be configured to record UDEs on a distributed ledger 116 (e.g., a blockchain or other synchronous distributed database). The synchronous distributed database 116 can be a public or private synchronous distributed database. A UDE can represent access rights, images (e.g., photos, videos, graphics, digital artwork, etc.), sound files, and / or text. A UDE can be utilized to establish verified, public proof of ownership of any rights provided to a user over the content represented by the UDE (e.g., a license to use, copy, display the underlying content asset, the right to sell, transfer, or exchange the UDE, etc.).
[0057] 1B is a block diagram illustrating example components of an access control system 102. The example access control system 102 includes an arrangement of computer hardware and software components that can be used to implement aspects of the present disclosure. Those skilled in the art will appreciate that the example components may include more (or fewer) components than those depicted in FIG. 1B. The access control system 102 may include a cloud-based computer system.
[0058] With respect to cloud-based computer systems, a cloud-based computer system may include a hosted computing environment (sometimes referred to as a "cloud" computing environment) that includes a collection of physical computing resources that are remotely accessible, located in different facilities, and that can be rapidly provided on an as-needed basis. Certain data described herein may optionally be stored using a data store (sometimes referred to as "cloud" storage), which may include a hosted storage environment that includes a collection of physical data storage devices that are remotely accessible and that can be rapidly provided on-demand.
[0059] The access control system 102 includes one or more processing units 120B (e.g., general-purpose processors and / or high-speed graphics processors), one or more network interfaces 122B, a non-transitory computer-readable media drive 124B, and an input / output device interface 126B, all of which may communicate with each other via one or more communication buses. The network interface 122B may provide the services described herein with connectivity to one or more networks or computing systems (e.g., venue systems, user devices, distributed ledgers, event promoters, seating chart visualization systems, etc.). Thus, the processing unit 120B may receive information (e.g., purchase of access tokens, verification / authentication data, verification / authentication requests, etc.) and instructions from other computing devices, systems, or services via the network, and may provide data and / or execute instructions in response. The processing unit 120B may also communicate with the memory 124B and provide output information via the input / output device interface 126B. The input / output device interface 126B may accept input from one or more input devices, such as a keyboard, a mouse, a digital pen, a touch screen, a microphone, a camera, or the like.
[0060] The memory 128B may include computer program instructions that the processing unit 120B may execute to implement one or more aspects of the present disclosure. The memory 128B generally includes RAM, ROM (and variations thereof, such as EEPROM), and / or other permanent or non-transitory computer-readable storage media. The memory 128B may store an operating system 132B that provides computer program instructions for use by the processing unit 120B in the general management and operation of the authentication and electronic asset management module 134B and its included components.
[0061] Memory 128B may store user accounts including user name, user email address, user phone number / SMS / text messaging address, other electronic destination, geographic information (e.g., physical address, zip code, city, etc.), a unique user identifier (e.g., an alphanumeric identifier, fingerprint data, facial print data, iris print data, etc.), a unique user device identifier, event identifiers corresponding to events to which the user has access, a hash of the user device and / or user identifier, user preferences (e.g., favorite performers, favorite venues, favorite musical styles, other preferences described herein, etc.), payment device data, and / or other user data described herein.
[0062] The memory 128B may also store event, access token, and venue information, as discussed elsewhere herein. The memory 128B may store in the user record and / or elsewhere an identification of the access rights loaned by the user (optionally including the loan date, an identification of the event to which the access rights grant access, an identification of the event venue for which the access rights are loaned, an identification of the event date, and information of the recipient), the access rights loaned to the user (optionally including the loan date, an identification of the event to which the access rights grant access, an identification of the event venue for which the access rights are loaned, an identification of the event date, and an identification of the authorizer), and the loaned access rights reclaimed by the user (optionally including the loan date, an identification of the event to which the reclaimed access rights grant access, an identification of the event venue for which the access rights are loaned, an identification of the event date, and an identification of the recipient).
[0063] Some or all of the data and content discussed herein may optionally be stored in a relational database, a SQL database, a NOSQL database, or other database type. Because content elements may include binary large objects (BLOBs), such as large images (e.g., still images, video, multi-layered graphics) that are difficult for traditional databases to handle, some (e.g., BLOBs) or all of the content elements may be stored in files and corresponding references stored in a database. Optionally, memory 128B may include one or more third-party cloud-based storage systems.
[0064] The authentication and electronic asset management module 134B may include a GUI component that generates and / or pre-populates a graphical user interface and processes user input, and a search component (which may include a search engine used to search for ticketed events). The authentication and electronic asset management module 134B may also include a multi-factor authentication component configured to authenticate a user. As described above, authentication may be performed by comparing a hash of a unique user identifier and a unique device identifier with those generated by the event access system 102. As a further example, authentication may also be performed by decrypting data including the unique user identifier and the unique device identifier (e.g., using a private key or a key used to perform the encryption) and comparing the decrypted data with that stored by the event access system 102. As described elsewhere herein, the Advanced Encryption Standard (AES), a symmetric encryption algorithm that encrypts a fixed block (128 bits) of data at a time, may optionally be used. By way of further example, Rivest-Shamir-Adleman (RSA) encryption / decryption techniques may also be optionally utilized. As yet another example, a triple Data Encryption Standard (DES) encryption / decryption technique may optionally be used. As yet another example, a hash function may be used. Optionally, authentication may also be performed using biometric measurements of the user.
[0065] The access rights verification component can be configured to determine whether an authenticated user has the relevant rights to access an event at the venue (and / or part of the event venue), and the access rights rules engine (e.g., configured to determine which access rights may be loaned, when a given access right may be loaned, for how long a given access right may be loaned, how many access rights may be loaned at a given time, how many access rights may be loaned in a given period of time (e.g., monthly, yearly, etc.), how frequently a given access right may be loaned, how many access rights loans may be reclaimed in a given period of time, and / or the like).
[0066] The ticketing module 136B may be configured to enable a user to view information about a ticketed event, access a seating map for the event venue, view available and unavailable seats at the event venue, access an image of the view from a given seat, view access token prices, create a user account (optionally including some or all of the user account information discussed herein), purchase or otherwise obtain one or more access rights (e.g., access tokens) to the event, store a representation of the access rights that the user has obtained (e.g., purchased by the user, transferred to the user, loaned to the user), store a representation of the access rights that the user has transferred to others, and / or recommend events to the user (e.g., using the user's preferences, access token acquisition history, geographic location, event sponsors, etc.).
[0067] Image analysis and processing module 138B may be configured to perform image analysis (e.g., on optical indicia encoding encrypted authentication data), contrast enhancement, deblurring, and / or image rotation, thereby enhancing decoding and interpretation of images of optical indicia (e.g., barcodes captured using a camera device).
[0068] The memory 128B may include an interface module 130B that may be configured to facilitate generating one or more interfaces through which a compatible computing device may send and receive data and content to and from the authentication and electronic asset management module 134B and the ticketing module 136B.
[0069] Referring now to Figure 2, an example of an authentication / verification process is shown. This process may be performed using an access control system, a venue system, and / or other systems as described elsewhere herein. Although the example below discusses encryption of the authentication data by and presented to the user device, optionally the authentication data is not encrypted. Optionally, the user device presents the authentication data in unencrypted form (e.g., via a barcode) and a scanner reads the authentication data and encrypts the authentication (e.g., using key encryption or a hash). Optionally, the encryption may be performed by other systems described herein.
[0070] In block 202, the user device is scanned by a venue authentication scanner to access the encrypted authentication data. As described above, the user device may present a unique user identifier and / or a unique device identifier via an encrypted optical code, via an encrypted radio frequency signal, and / or via an encrypted audio signal. Thus, for example, the scanner may include a camera, a laser scanner, a radio frequency receiver, or a microphone.
[0071] The scanned authentication data may be compressed. For example, if a camera is used to capture an image of the authentication data, the image may be compressed to reduce the file image size, thereby reducing the memory required to store the image and the network bandwidth required to transmit the image. Compression may be lossless or lossy. By way of example, if lossy compression is used, transform coding (e.g., discrete cosine transform (DCT)) may be used to perform the compression. If lossless compression is used, run-length coding, entropy coding, predictive coding may be used. The image may optionally be decompressed using a decompression module corresponding to the form of encryption.
[0072] Optionally, a timestamp generated by an application provided on the user device is also received, which may or may not be encrypted. Optionally, the encryption may be performed using a key embedded in the application (e.g., the public key of an access control system or other system that performs the decryption). Optionally, a hash may be applied to the authentication data (e.g., a unique user ID and / or a unique device ID). Optionally, a biometric scanner may also or instead read a biometric feature of the user (e.g., a face print, fingerprint, iris image, etc.).
[0073] At block 204, the encrypted authentication data is decrypted (e.g., using a decryption key, such as a private key, associated with the system performing the decryption). Optionally, if the received authentication data is hashed authentication data, no decryption operation is performed. Additionally, the system may generate a unique timestamp. Optionally, the encrypted authentication data may be transmitted from the venue authentication scanner to a remote system performing the decryption.
[0074] Optionally, image analysis and processing is performed on the image of the optical indicium to enhance its readability and therefore decoding and accuracy in decoding. For example, if the optical indicium (e.g., a QR code or other barcode) is black and displayed against a dark background on the user device or on an image, contrast enhancement may be performed in response to detecting insufficient contrast (e.g., by not detecting clear edges). For example, a filter may be utilized that identifies edge boundaries in the image of the optical indicium, such as the edge between a barcode and a background of a contrasting color, and enhances the contrast of the image in areas immediately adjacent to the detected edges.
[0075] Also, if the optical code is blurred, it may be difficult to accurately decode and decode the optical code. Therefore, a deblurring and / or denoising process may be performed. The deblurring process may include applying a convolutional filter to the image of the optical code. The deblurring and denoising may be performed using a deep learning convolutional neural network. The convolutional neural network may optionally include a neural network input layer, one or more neural network hidden layers, a neural network pooling layer, and a neural network output layer. Other learning engines may be used. The convolutional neural network may also be utilized to perform image classification, recognition, localization, and / or object detection. Optionally, an autoencoder may be utilized to convert the low-resolution image to a high-resolution image.
[0076] Optionally, the optical indicium image can be rotated to match a desired orientation to further facilitate decoding and deciphering the encoded authentication data.
[0077] At block 206, a venue entrance identifier is received. The venue entrance identifier may correspond to a venue entrance where an authentication scanner is located and may be received specifically from the authentication scanner or from a venue system. The venue identifier may be an alphanumeric code and may include descriptive metadata (e.g., Entrance 1 on the east side of the venue).
[0078] At block 208, a determination is made as to whether the timestamp received from the user device matches the system generated timestamp. If it is determined that the timestamps do not match (e.g., an exact match or match within a certain time range, such as 1-15 seconds), an authentication / verification failed signal may be generated. This signal may be used to cause a light of a particular color (e.g., red), text to be presented on a display (e.g., "authentication failed"), a graphic to be presented on a display (e.g., a prohibition symbol), and / or a sound to be generated by a speaker (e.g., a boing sound).
[0079] If it is determined that the timestamps match, processing may proceed to block 210. A determination may be made as to whether the device ID value received from the user device matches a unique device ID (e.g., IMEI, UDID, serial number, IDFA, and / or GAID) in the user account record. If it is determined that the received device ID does not match, an authentication / verification failed signal may be generated. This signal may be used to cause a light of a particular color (e.g., red), text to be presented on a display (e.g., "authentication failed"), a graphic to be presented on a display (e.g., a prohibition symbol), and / or a sound to be generated by a speaker (e.g., a boing sound).
[0080] If it is determined that the device IDs match, processing proceeds to block 212. A determination is made as to whether the user ID matching the value received from the user device matches a unique user ID in a user account record that stores the matching unique device ID. If it is determined that the received user IDs do not match, an authentication / verification failure signal may be generated, similar to that described above.
[0081] If it is determined that the user ID matches, processing proceeds to block 214. In block 214, the user ID and / or device ID are used to determine whether the user has access to the event at the venue on the current day through the user account record. For example, the user may have purchased access, the access may have been transferred to the user, or the access may have been loaned to the user. In the example of access being loaned to the user, it may be determined whether the loaned access applies to the current event. For example, if the user has been loaned access to a series of events (e.g., a sports team's season or a musician's event series) and the loan is associated with a specified start and stop date, it may be determined whether the current event belongs to the series of events for which the access was loaned, whether the current date falls within the start and end times of the access loan, and whether the access loan has been reclaimed. In this example, if the current event belongs to the series of events for which the access was loaned, falls within the specified start and end dates, and the access loan has not been reclaimed, it may be determined that the user has access to the event at the event venue on the current day. Otherwise, it may be determined that the user does not have access to the event at the event venue on the current day.
[0082] If it is determined that the user has access to the event at the venue on the current day, then optionally, in block 216, a determination can be made as to whether the venue authentication scanner ID corresponds to a venue entrance to which the user has rights to access (e.g., by comparing the seats assigned to the user from the user account with a list of entrances corresponding to access to the assigned seats). If it is determined that the venue authentication scanner ID does not correspond to a venue entrance to which the user has rights to access, an authentication / verification failure signal can be generated, similar to that described above. Optionally, a notice can be presented that includes text indicating the venue entrances to which the user has rights to access. The user can then proceed to such authorized entrance and repeat the scanning verification process.
[0083] If it is determined that the venue authentication scanner ID corresponds to a venue entrance that the user has the right to access, an entry signal may be generated in block 218. The entry signal may cause a light to illuminate in a certain color (e.g., green), text (e.g., "Authentication Approved"), a graphic (e.g., a thumbs up symbol), and / or a sound (e.g., a bell). Optionally, it may indicate the number of access rights the user has. Optionally, the entry signal may cause an entry barrier to be unlocked or opened to allow the user to access the entrance. For example, the signal may activate a solenoid, a stepper motor, and / or a pneumatic actuator to unlock and / or open an entry door, retract a barrier, unlock and / or rotate a turnstile, etc. Additionally, the entry signal may be utilized in determining whether to assign an electronic element, such as a UDE, to the user. Additionally, if the access rights are loaned rights from another user, an indication may be stored in the database indicating that the loaned access rights have been used and are no longer available for reclaim.
[0084] Optionally, rather than comparing the user ID and device ID, a hash of the user ID and / or device ID received from the user device (e.g., via radio frequency signals, optical indicia, audio signals) may be compared to a hash of the user ID and / or device ID from the user account to determine if there is a match. If there is a match, and the timestamps match, processing may proceed to block 212. If not, an authentication / verification failure signal may be generated, similar to that described above.
[0085] Now referring to FIG. 3, an exemplary process for lending access rights is illustrated. By way of example, the process may be performed in whole or in part using the access control system 102, the user device, and / or other devices or systems disclosed herein. At block 302, the process detects that an access rights user interface has been requested. The access rights user interface may be configured to display access rights associated with the user and the status of such access rights. For example, the access rights user interface may be provided by a dedicated application related to ticketing provided on the user device (e.g., downloaded from an app store). In response to the user interface being utilized (e.g., in response to a request by the user), the application may transmit a corresponding message to the system over the network. As a further example, the access rights user interface may be utilized from the access control system 102 by a browser provided on the user device. The user device may transmit identification data associated with the user to the system. Such identification data may include a user identifier and password associated with the dedicated application provided on the user device, a unique code, a unique identifier associated with the user device, biometric data of the user, and / or other identification data.
[0086] At block 304, the identification data is utilized to access a database record corresponding to the user. The database record may include a record of access rights and corresponding context data associated with the user. For example, the database record may identify the events to which the user has access rights (e.g., a unique event identifier, event name, event date, event venue, event seat location, etc.), an indication of whether and when a given access right was loaned, an indication of loan parameters (e.g., start and / or stop dates, start and / or stop times, other parameters disclosed herein, etc.), an indication of to whom a given access right was loaned, an indication of which access rights were reclaimed (and associated reclaim dates), and / or other access rights data as disclosed herein.
[0087] In block 306, access right loan rules may be utilized from the data store. For example, the access right loan rules may include which access rights may be loaned, when a given access right may be loaned, for how long a given access right may be loaned, how many access rights may be loaned at a given time, how many access rights may be loaned in a given period of time (e.g., monthly, yearly, etc.), how frequently a given access right may be loaned, which access rights may be reclaimed, when access rights may be reclaimed (if any), how many access right loans may be reclaimed in a given period of time, etc.
[0088] In block 308, the rules engine utilizes the access rights rules and the access rights data to determine what access rights can be loaned, when (if at all) such access rights can be loaned if loaning a given access right is not permitted at the current time, and / or which access rights can or cannot be reclaimed.
[0089] In block 308, the retrieved access rights associated with the user, the access rights status, and an indication of which access rights can currently be loaned, when the access rights can be loaned (for access rights that cannot currently be loaned), which access rights can be reclaimed, and when the access rights can be reclaimed (for access rights that cannot currently be reclaimed) are transmitted to the user device and can be used to pre-configure the access rights user interface.
[0090] In block 310, an access rights specification may be received from a user via an access rights user interface. For example, the access rights specification may specify one or more access rights selected by the user and corresponding access rights loan and / or reclaim specifications. For example, the access rights loan specification may specify the access rights controlled by the user, the access rights loan recipient, the access rights loan start state, and / or the access rights loan end date. As a further example, the reclaim access rights specification may specify the access rights that the user wants to reclaim (e.g., so that the user can use the reclaimed access rights or loan or transfer the access rights to another recipient) and the timing of the reclaim (e.g., immediately or at a specified date or event).
[0091] In block 312, the access rights rules may be optionally re-run to determine whether a given access rights loan / recovery specification violates any rules and therefore whether the access rights loan / recovery specification is permitted. If the access rights loan / recovery specification is not permitted, in block 314, a denial notice may be generated and sent to the user device (e.g., for display by a dedicated application, browser, etc.) and / or to an electronic destination associated with the user (e.g., an email address, a short message service address, other electronic destination, etc.).
[0092] If the access loan / redeem specification is permitted, then in block 316 the corresponding database record may be updated to record the access loan and / or redeem, such as by setting a database toggle accordingly. In block 318, a notification may be sent for display to the designated recipient of the given access loan and to the recipient to whom the loan is being redeemable. For example, the notification may be sent to the recipient's device for display via a dedicated application, browser, etc., and / or to an electronic address associated with the recipient (e.g., email address, short message service address, etc.).
[0093] An exemplary redemption process is now illustrated with reference to FIG. 4. By way of example, the process may be performed in whole or in part using the access control system 102, the user device, and / or other devices or systems disclosed herein. At block 402, a redemption request for a specified access right is received from a user device associated with an access right control user via an access right user interface. As described elsewhere herein, the access right user interface may be configured to display access rights associated with the user and the status of such access rights. For example, the access right user interface may be provided by a dedicated application related to ticketing provided on the user device (e.g., downloaded from an app store). In response to the access right user interface being utilized (e.g., in response to a request by the user), the application may transmit a corresponding message to the system over the network. As a further example, the access right user interface may be utilized from the access control system 102 by a browser provided on the user device. The user device may transmit identification data associated with the user to the system. Such identification data may include a user identifier and password associated with a dedicated application provided on the user device, a unique code, a unique identifier associated with the user device, biometric related data of the user, and / or other identification data.
[0094] In block 404, access rights reclaim rules are executed. For example, the access rights reclaim rules may indicate which loaned access rights may be revoked / reclaimed, how many access rights loans may be reclaimed over a given period of time, whether there is an expiration date / time or period during which a given access right cannot be reclaimed, etc. In block 406, a determination is made as to whether the executed rules allow reclaiming of the specified loaned access rights. If the executed rules determine that the specified loaned access rights are not allowed to be reclaimed, in block 412, a denial notice may be generated and sent to the user device (e.g., for display by a dedicated application, browser, etc.) and / or to an electronic destination associated with the user (e.g., an email address, a short message service address, other electronic destination, etc.).
[0095] If the executed rules determine that the loaned access rights are permitted to be reclaimed, then in block 408 the access rights are reclaimed and the corresponding access rights record is updated to reflect the reclaim, such as by setting a database toggle accordingly. In block 410, a notification may be sent for display to the recipient of the loan of the loaned access rights and to the user controlling the access rights to indicate that the access rights have been reclaimed. For example, the notification may be sent to the recipient device and the access rights controller device for display by a dedicated application, browser, etc., and / or to an electronic address (e.g., email address, short message service address, etc.) associated with the recipient and an electronic address associated with the access rights controller.
[0096] Accordingly, one aspect of the present disclosure relates to methods and systems configured to provide dynamic, and optionally retrievable, access to resources, such as physical locations, for specified time periods and / or for a specified event or set of events. Digital access rights lockers can optionally be utilized to store data indicative of a user's access rights to physical locations, physical objects, and / or other rights, as well as the status of such rights.
[0097] The methods and processes described herein may have fewer or additional steps or states, and steps or states may be performed in a different order. Not all steps or states need to be reached. The methods and processes described herein may be embodied in and fully or partially automated through software code modules executed by one or more general-purpose computers. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all of the methods may alternatively be embodied in whole or in part in dedicated computer hardware. The systems described herein may optionally include a display, a user input device (e.g., touch screen, keyboard, mouse, voice recognition, etc.), a network interface, etc.
[0098] The results of the disclosed methods can be stored in any type of computer data repository, such as a relational database and a flat file system using volatile and / or non-volatile memory (e.g., magnetic disk storage, optical storage, EEPROM and / or solid-state RAM).
[0099] The various exemplary logic blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various exemplary components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. The described functionality can be implemented in various ways for each particular application, and such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0100] Furthermore, the various example logic blocks and modules described in connection with the embodiments disclosed herein may be implemented or performed by machines such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor device may be a microprocessor, but alternatively, the processor device may be a controller, a microcontroller, or a state machine, combinations thereof, and the like. A processor device may include electrical circuitry configured to process computer executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logical operations without processing computer executable instructions. A processor device may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. The computing environment may include any type of computer system, including, but not limited to, a microprocessor-based computer system, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within a consumer electronics device, to name a few.
[0101] Elements of the methods, processes, routines, or algorithms described in connection with the embodiments disclosed herein may be implemented directly in hardware, in a software module executed by a processor unit, or in a combination of both. The software modules may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer readable storage medium. An exemplary storage medium may be coupled to the processor unit such that the processor unit can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor unit. The processor unit and the storage medium may be incorporated in an ASIC. The ASIC may be incorporated in a user terminal. Alternatively, the processor unit and the storage medium may reside as discrete components in a user terminal.
[0102] Conditional language used herein, such as, among others, "can," "may," "might," "could," "could," "for example," and the like, is generally intended to convey that certain embodiments include certain features, elements, and / or steps and other embodiments do not, unless otherwise specified or understood within the context in which it is used. Thus, such conditional language is generally not intended to imply that features, elements, and / or steps are somehow required for one or more embodiments, or that one or more embodiments necessarily include logic that determines, with or without other input or prompting, whether those features, elements, and / or steps are included or should be performed in any particular embodiment. Terms such as "comprise," "have," and the like are synonymous and are used inclusively and expansively and do not exclude additional elements, features, acts, operations, etc. Additionally, the term "or" is used in an inclusive sense (and not an exclusive sense), e.g., when used to connect a list of elements, the term "or" may mean one, some, or all of the elements in the list.
[0103] Disjunctive language, such as the phrase "at least one of X, Y, Z," is understood in the context in which it is commonly used to indicate that an item, term, etc. can be either X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z), unless otherwise indicated. Thus, such disjunctive language is not generally intended, and should not be intended, to indicate that a particular embodiment requires that at least one of X, at least one of Y, or at least one of Z, respectively, be present.
[0104] The term "click" may be used in reference to a user selecting a control, menu selection, etc., although other user inputs may be used, such as voice commands, text input, gestures, etc. User input may be provided through an interface, such as, by way of example, through a text field in which the user enters text, and / or through a menu selection (e.g., a drop-down menu in which the user can check or otherwise select via a checkbox, a list or other arrangement, a group of individually selectable icons, etc.). When a user provides an input or activates a control, a corresponding computing system may perform a corresponding operation. Some or all of the data, inputs and instructions provided by the user may optionally be stored in a system data store (e.g., a database) from which the system may access and retrieve such data, inputs and instructions. The notifications / reminders and user interfaces described herein may be provided via web pages, dedicated or non-dedicated telephone applications, computer applications, short message service messages (e.g., SMS, MMS, etc.), instant messages, email, push notifications, voice, pop-up interfaces, and / or other methods.
[0105] A user terminal as described herein may be in the form of a mobile communications device (e.g., a mobile phone), a laptop, a tablet computer, an interactive television, a gaming console, a media streaming device, a head-wearable display, a network watch, other wearable computing devices, etc. A user terminal may optionally include a display, a user input device (e.g., a touch screen, a keyboard, a mouse, voice recognition, etc.), a network interface, etc.
[0106] While the above detailed description illustrates, describes, and points out novel features applicable to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the illustrated apparatus or algorithms may be made without departing from the spirit of the present disclosure. As will be appreciated, certain features may be used or practiced separately from other features, and therefore certain embodiments described herein may be embodied in a range of forms that do not provide all of the features and advantages set forth herein. The scope of certain embodiments disclosed herein is indicated by the appended claims, rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are intended to be embraced within their scope.
Claims
1. 1. A physical location access control system comprising: A network interface; At least one processing device, receiving, via the network interface, a request from an access controller to provide temporary access to a first user to a first physical location, the request from the access controller providing an indication of a first time period associated with the temporary access; determining whether the access controller is authorized to provide the first user with the temporary access right to the first physical location for the first time period; in response at least in part to the access controller determining that it is authorized to provide the first user with the temporary access right to the first physical location for the first time period; creating a temporary access record corresponding to said first time period; Revoke the access right of the access controller to access the first physical location during the first time period; sending a message corresponding to the temporary access record to a destination associated with the first user; enabling the first user to access the first physical location during the first time period without a token corresponding to the temporary access right; and at least one processing device operable to:
2. Determining whether the access controller is authorized to provide the first user with the temporary access right to the first physical location for the first time period includes: utilizing a history of temporary access rights provided by said access controller; determining a number of temporary access rights provided to users by the access controller over a second time period; in response at least in part to determining that a number of temporary access rights provided by the access controller over the second time period is less than a first threshold; determining that the access controller is authorized to provide the first user with the temporary access right to the first physical location for the first time period; The physical location access control system of claim 1 , further comprising:
3. Determining whether the access controller is authorized to provide the first user with the temporary access right to the first physical location for the first time period includes: utilizing a history of temporary access rights provision associated with said access controller; determining the number of temporary access rights currently provided to the user by the access controller; in response at least in part to determining that a number of temporary access rights currently being provided by the access controller is less than a first threshold; determining that the access controller is authorized to provide the first user with the temporary access right to the first physical location for the first time period; The physical location access control system of claim 1 , further comprising:
4. The system comprises: During the first period of time, receiving a first hash from a device at the first physical location, the first hash including a hash of an identifier identifying a user communication device associated with the first user and an identifier identifying the first user; comparing the first hash, which includes the hash of the identifier identifying the user communication device associated with the first user and the identifier identifying the first user, to a second hash generated using data stored in a database record associated with the first user; utilizing the temporary access record in response at least in part to determining that the first hash and the second hash match; 2. The physical location access control system of claim 1, configured to perform operations including: transmitting a command configured to cause an indicator of the first physical location to provide an access permission indication based at least in part on the utilized temporary access record.
5. The system comprises: During the first period of time, receiving, from a device at the first physical location, first biometric data of a given user acquired at the first physical location; comparing the received first biometric data with data stored in a database record associated with the first user; utilizing the temporary access record in response at least in part to determining that the first biometric data corresponds to data stored in a database record associated with the first user; 2. The physical location access control system of claim 1, configured to perform operations including: transmitting a command configured to cause an indicator of the first physical location to provide an access permission indication based at least in part on the utilized temporary access record.
6. receiving a request from the access controller to revoke the temporary access right to the first physical location; determining whether said temporary access right is currently retrievable; 2. The physical location access control system of claim 1, configured to perform operations including sending a reclaim failure notification to the access controller in response at least in part to determining that the temporary access rights are not currently reclaimable.
7. The physical location access control system of claim 1 , wherein the temporary access rights include access to a first event of a set of events.
8. The physical location access control system of claim 1 , wherein the temporary access rights include access to a designated area within the first physical location.
9. 2. The physical location access control system of claim 1, configured to perform operations including recording a token in a synchronous distributed database in response at least in part to providing the temporary access right to the first user.
10. 1. A computer-implemented method comprising: receiving, in the computer system, a request from an access rights controller via a network interface to provide a first user with a first access right retrievable by the access rights controller for a first time period, the first access right having a set of access rights including the retrievable first access right associated with a first physical location; in response, at least in part, to the request from the access rights controller; recording instructions in a database regarding providing the retrievable first access right to the first user; revoking the ability of the access rights controller to utilize the retrievable first access rights associated with the first physical location; receiving, via a network, a reclaim request for the reclaimable first access right from the access right controller; determining whether the revocable first access right is currently revocable; in response at least in part to determining that the retrievable first access right is currently retrievable; recording an indication in a database regarding the revocation of the reclaimable first access right and enabling the access rights controller's ability to utilize the reclaimable first access right associated with the first physical location; and revoking the first user's ability to utilize the retrievable first access right associated with the first physical location.
11. The step of determining whether the revocable first access right is currently revocable comprises:
11. The computer-implemented method of claim 10, further comprising determining whether the first user has utilized the retrievable first access right.
12. The step of determining whether the revocable first access right is currently revocable comprises: The computer-implemented method of claim 10 , further comprising determining whether a current time falls within the first time period.
13. based at least in part on a history of access rights provision associated with the access rights controller, the history including a number of access rights provided by the access rights controller to users over a second time period; 11. The computer-implemented method of claim 10, further comprising determining whether the access rights controller is authorized to provide the retrievable first access rights to the first physical location to the first user.
14. based at least in part on a number of access rights associated with the access rights controller that are currently provided to the user by the access rights controller; 11. The computer-implemented method of claim 10, further comprising determining whether the access rights controller is authorized to provide the retrievable first access rights to the first physical location to the first user.
15. 11. The computer-implemented method of claim 10, wherein the retrievable first access right comprises access to a first event of a set of events.
16. 11. The computer-implemented method of claim 10, wherein the retrievable first access rights include access rights to a specified area within the first physical location.
17. 11. The computer-implemented method of claim 10, further comprising recording a token in a synchronous distributed database at least in part in response to providing the retrievable first access right to the first user.
18. A non-transitory computer-readable memory storing instructions that, when executed by a computer system including one or more computing devices, cause the computer system to: receiving a request from a requestor at a first time to provide a first user with retrievable access rights to a first physical location for a first event; determining whether the requester is authorized to provide the first user with the retrievable access rights to the first physical location for the first event; in response at least in part to determining that the requester is authorized to provide the first user with the retrievable access rights to the first physical location for the first event; creating an access provision record corresponding to providing the retrievable access right to the first event to the first user; Revoke the requester's access to the first physical location for the first event; sending a message corresponding to the access provision record to a destination associated with the first user; enabling the first user to access the first physical location for the first event without a token corresponding to the retrievable access right; 23. A non-transitory computer-readable memory for causing a computer to perform operations including:
19. Determining whether the requester is authorized to provide the retrievable access right to the first physical location to the first user includes: utilizing a history of provision of the retrievable access rights associated with the requester; determining a number of retrievable access rights provided by the requester to users over a second time period; in response at least in part to determining that a number of retrievable access rights provided by the requester over the second time period is less than a first threshold; determining that the requester is authorized to provide the first user with the retrievable access rights to the first physical location for the first event; 20. The non-transitory computer readable memory of claim 18, further comprising:
20. Determining whether the requester is authorized to provide the first user with the retrievable access rights to the first physical location for the first event includes: utilizing a history of provision of retrievable access rights associated with said requester; determining the number of retrievable access rights currently provided to users by the requester; in response at least in part to determining that a number of the requester's currently provided retrievable access rights is less than a first threshold; determining that the requester is authorized to provide the first user with the retrievable access rights to the first physical location for the first event; 20. The non-transitory computer readable memory of claim 18, further comprising:
21. The operation includes: receiving a first hash from a device at the first physical location, the first hash including a hash of an identifier identifying a user communication device associated with the first user and an identifier identifying the first user; comparing a first hash including the hash of the identifier identifying the user communication device associated with the first user and the identifier identifying the first user to a second hash generated using data stored in a database record associated with the first user; utilizing the access provision record in response at least in part to determining that the first hash and the second hash correspond; 20. The non-transitory computer-readable memory of claim 18, further comprising an operation of: transmitting a command configured to cause an indicator of the first physical location to provide an access permission indication based at least in part on the utilized access provision record.
22. The operation includes: receiving, from a device at the first physical location, first biometric data of a given user acquired at the first physical location; comparing the received first biometric data with data stored in a database record associated with the first user; utilizing the access provision record in response at least in part to determining that the first biometric data corresponds to data stored in a database record associated with the first user; 20. The non-transitory computer-readable memory of claim 18, further comprising an operation of: transmitting a command configured to cause an indicator of the first physical location to provide an access permission indication based at least in part on the utilized access provision record.
23. The operation includes: receiving a request from the requestor to revoke the access right to the first physical location; determining whether the retrievable access rights are currently retrievable; 20. The non-transitory computer readable memory of claim 18, comprising an operation of: sending a reclaim failure notification to an access rights controller in response at least in part to determining that the reclaimable access rights are not currently reclaimable.
24. 20. The non-transitory computer-readable memory of claim 18, wherein the retrievable access rights include access rights to a first event of a set of events.
25. 20. The non-transitory computer-readable memory of claim 18, wherein the retrievable access rights include access rights to a specified area within the first physical location.
26. The operation includes:
20. The non-transitory computer readable memory of claim 18, further comprising: recording a token in a synchronous distributed database at least in part in response to providing the retrievable access rights to the first user.
Citation Information
Patent Citations
Program
WO2018074504A1
