Systems and methods for electronic ticket management
First Claim
1. A computer system, comprising:
- a data store holding;
a plurality of profiles, each of a respective entity and stored in association with past ticket usage data indicating a probability that the respective entity would personally use a ticket issued to them based on a history of past ticket usage;
a computer interface configured to receive a ticket request from a requesting device via a computer network, the ticket request identifying a profile of a requesting entity;
one or more processors configured to execute code for managing tickets, the code configured when executed to implement;
a ticket controller configured to;
in response to the ticket request, determine whether a ticket should be issued to the requesting entity based on the past ticket usage data associated with the requesting entity'"'"'s profile, and if so issue a ticket to the requesting entity in electronic form via the network,a receiving module configured to receive a ticket use notification from a validating device via the network, the ticket use notification indicating;
identity data of the requesting entity and identity data of a presenting entity that has presented the issued ticket to the validating device, anda profile manager configured to;
update the past ticket usage data associated with the requesting entity'"'"'s profile based on the ticket use notification, wherein the updated past ticket usage data conveys whether the requesting entity presented the ticket themselves,wherein the identity data of the requesting entity and the identity data of the presenting entity comprise a hash of at least part of a payment account number issued to the requesting entity and a hash of at least part of a payment account number issued to the presenting entity respectively.
2 Assignments
0 Petitions
Accused Products
Abstract
A computer system according to certain aspects uses past ticket usage data indicating a probability that a respective entity would personally use a ticket issued to them based on a history of past ticket usage. A ticket controller can respond to ticket requests by determining whether a ticket should be issued to a requesting entity based on the past ticket usage data associated with the requesting entity'"'"'s profile, and if so issue a ticket to the requesting entity in electronic form. The system can receive a ticket use notification and update the past ticket usage data associated with the requesting entity'"'"'s profile based on the ticket use notification, where the updated past ticket usage data conveys whether the requesting entity presented the ticket themselves.
4 Citations
19 Claims
-
1. A computer system, comprising:
-
a data store holding;
a plurality of profiles, each of a respective entity and stored in association with past ticket usage data indicating a probability that the respective entity would personally use a ticket issued to them based on a history of past ticket usage;a computer interface configured to receive a ticket request from a requesting device via a computer network, the ticket request identifying a profile of a requesting entity; one or more processors configured to execute code for managing tickets, the code configured when executed to implement; a ticket controller configured to;
in response to the ticket request, determine whether a ticket should be issued to the requesting entity based on the past ticket usage data associated with the requesting entity'"'"'s profile, and if so issue a ticket to the requesting entity in electronic form via the network,a receiving module configured to receive a ticket use notification from a validating device via the network, the ticket use notification indicating;
identity data of the requesting entity and identity data of a presenting entity that has presented the issued ticket to the validating device, anda profile manager configured to;
update the past ticket usage data associated with the requesting entity'"'"'s profile based on the ticket use notification, wherein the updated past ticket usage data conveys whether the requesting entity presented the ticket themselves,wherein the identity data of the requesting entity and the identity data of the presenting entity comprise a hash of at least part of a payment account number issued to the requesting entity and a hash of at least part of a payment account number issued to the presenting entity respectively. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A method implemented by a computer system comprising a data store holding a plurality of profiles, each of a respective entity and stored in association with past ticket usage data indicating a probability that the respective entity would personally use a ticket issued to them based on a history of past ticket usage, the method comprising:
-
receiving a ticket request from a requesting device via a computer network, the ticket request identifying a profile of a requesting entity; in response to the ticket request, determining whether a ticket should be issued to the requesting entity based on the past ticket usage data associated with the requesting entity'"'"'s profile, and if so issue a ticket to the requesting entity in electronic form via the network; receiving a ticket use notification from a validating device via the network, the ticket use notification indicating;
identity data of the requesting entity and identity data of a presenting entity that has presented the issued ticket to the validating device; andupdating the past ticket usage data associated with the requesting entity'"'"'s profile based on the ticket use notification, wherein the updated past ticket usage data conveys whether the requesting entity presented the ticket themselves, wherein the identity data of the requesting entity and the identity data of the presenting entity comprise a hash of at least part of a payment account number issued to the requesting entity and a hash of at least part of a payment account number issued to the presenting entity respectively.
-
-
19. A computer program product comprising computer readable instructions stored on a non-transitory computer readable storage medium and which, when executed, configured to implement a method comprising:
-
receiving a ticket request from a requesting device via a computer network, the ticket request identifying a profile of a requesting entity; in response to the ticket request, determining whether a ticket should be issued to the requesting entity based on past ticket usage data associated with the requesting entity'"'"'s profile, and if so issue a ticket to the requesting entity in electronic form via the network; receiving a ticket use notification from a validating device via the network, the ticket use notification indicating;
identity data of the requesting entity and identity data of a presenting entity that has presented the issued ticket to the validating device; andupdating the past ticket usage data associated with the requesting entity'"'"'s profile based on the ticket use notification, wherein the updated past ticket usage data conveys whether the requesting entity presented the ticket themselves, wherein the identity data of the requesting entity and the identity data of the presenting entity comprise a hash of at least part of a payment account number issued to the requesting entity and a hash of at least part of a payment account number issued to the presenting entity respectively.
-
Specification