NETWORKED BARCODE VERIFICATION SYSTEM

• US 20100228576A1
• Filed: 03/03/2010
• Published: 09/09/2010
• Est. Priority Date: 03/06/2009
• Status: Active Grant

• Current Assignee: Live Nation Entertainment Incorporated
• Original Assignee: Ticketmaster LLC (Live Nation Entertainment Incorporated)
• Inventors: Marti, Benjamin J., Levin, Samuel, Denker, Dennis A.
• Granted Patent: US 8,510,138 B2
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06K 5/00 Methods or arrangements for verifying the correctness of markings on a record carrier; Column detection devices
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events

Abstract

Systems and methods are described for barcode verification. Optionally, a barcode scanner/imager is coupled to a verification system over a network. The verification system receives over the network barcode data associated with an item, such as a ticket, and associated information. The verification system uses the barcode data and associated information to determine if the barcode is valid and corresponds to an identified event. The verification system transmits a verification result.

Claims

1. A barcode verification system comprising:

a barcode interface configured to receive barcode data associated with a ticket barcode associated with a ticketed event, wherein the barcode data was obtained via a barcode imaging device at a first location or was manually entered;

an interface configured to receive seating and event data manually provided by a first user offering the ticket and/or by a second user seeking to acquire the ticket;

a data store that stores;

barcode data for issued tickets associated for the ticketed event;

event data associated with the issued tickets;

seating data associated with the issued tickets;

transfer permission data associated with the issued tickets;

code stored in non-transitory memory, that when executed by a computing device is configured to;

determine if the received barcode data is in accordance with a first specified format;

determine if the received barcode data corresponds to barcode data stored in the data store;

when the received barcode data corresponds to barcode data stored in the data store, determine if the received event data corresponds to the event data associated with the issued tickets for the event;

determine if the received seating data corresponds to barcode data stored in the data store;

determine if the received barcode data is associated with a ticket that is not to be transferred via at least a first transaction type;

transmit a positive verification and transfer right indication based at least in part on the determination that;

the received barcode data is in accordance with a first specified format;

the received barcode data corresponds to barcode data stored in the data store;

the received event data corresponds to the event data associated with the issued tickets for the event; and

the received seating data corresponds to barcode data stored in the data store.

2. The barcode verification system as defined in claim 1, further comprising a barcode reader system.

3. The barcode verification system as defined in claim 1, wherein the barcode verification system is associated with a first website that enables a user to acquire and transfer tickets and provides a ticket management user interface via which a user can access ticket data related to tickets acquired by the first user, the ticket data including at least:

an event name associated with at least one ticket previously acquired by the first user;

an indication as to whether the first user had transferred at least one ticket via a service offered by the first website; and

an indication as to whether the first user had transferred at least one ticket via a service offered by a different website.

4. The barcode verification system as defined in claim 1, wherein the code is configured to:

receive a locator associated with a posting of the ticket from the first user and/or the second user; and

access a web resource hosted by a web server associated with the locator;

access from the web resource the seating and event data manually provided by the first user and/or the second user via the web server.

5. The barcode verification system as defined in claim 1, wherein the code is configured to determine if the ticket is transferable based at least in part on an indication that the event date has passed or that there is insufficient time before event to process ticket transfer.

6. The barcode verification system as defined in claim 1, wherein the code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the event is cancelled.

7. The barcode verification system as defined in claim 1, wherein the code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory readable memory that ticket is being offered by the first user with a second ticket wherein the seat associated with the ticket is not adjacent to a seat associated with the second ticket.

8. The barcode verification system as defined in claim 1, wherein the code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket has already been transferred by the first user.

9. The barcode verification system as defined in claim 1, wherein the code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket is a complementary ticket.

10. A method of verifying a barcode, comprising:

receiving at a ticket posting system, the ticket posting system including at least one computing device, a ticket posting request by a first user, the ticket posting request including barcode data, event data, and seating data associated with a ticket offer;

transmitting a verification request over a network to a verification system, the verification request including the barcode data and the seat data;

receiving at the ticket posting system an indication as to whether;

the barcode data corresponds to a valid ticket,

for an event corresponding to the event data,

the ticket is associated with a seat corresponding to the seat data, and

is transferable by the first user;

if the verification indicates that;

the barcode data does not correspond to a valid ticket,

or if the verification indicates that;

that the barcode data corresponds to a ticket for an event different than that corresponding to the event data,

is associated with a seat that does not correspond to the seat data, and/or

is not transferable by the first user,

inhibiting the posting of the ticket;

if the verification indicates that;

the barcode data does correspond to a valid ticket,

for an event corresponding to the event data,

that the ticket is associated with a seat corresponding to the seat data, and

is transferable by the first user;

enabling the first user to post the ticket for transfer;

if, after the ticket is posted for transfer a successful transfer operation is performed with respect to a second user,

transmitting a request for a new barcode over the network to a barcode issuing system, the barcode request including an indication that the ticket is being transferred;

receiving over the network a new barcode associated by the barcode issuing system with the ticket;

enabling the ticket to be provided to the second user with the new barcode.

11. The method as defined in claim 10, wherein the barcode data is received via a camera or barcode scanner.

12. The method as defined in claim 10, wherein the barcode verification causes a lock to be placed on the ticket at least partly in response to receiving an indication that a ticket transfer process has been initiated.

13. The method as defined in claim 10, wherein the barcode verification system is operated by a different entity than the posting system.

14. The method as defined in claim 10, wherein the indication as to whether:

the barcode data corresponds to a valid ticket,

for an event corresponding to the event data,

the ticket is associated with a seat corresponding to the seat data, and

is transferable by the first user;

is provided via a verification pass or verification fail indication.

15. The method as defined in claim 10, wherein the indication as to whether the ticket is transferable by the first user indicates that the event date has passed or that there is insufficient time before event to process ticket transfer.

16. The method as defined in claim 10, wherein the indication as to whether the ticket is transferable by the first user indicates that that ticket is being offered by the first user with a second ticket wherein the seat associated with the ticket is not adjacent to a seat associated with the second ticket.

17. The method as defined in claim 10, wherein the indication as to whether the ticket is transferable by the first user indicates that that the ticket has already been transferred by the first user.

18. Program code stored in non-transitory, tangible computer readable memory that when executed by a computing device is configured to perform verification operations comprising:

receive barcode data associated with a ticket barcode associated with a ticketed event;

receive seating and event data manually provided by a first user offering the ticket and/or by a second user seeking to acquire the ticket;

store in a data store;

barcode data for issued tickets associated for the ticketed event;

event data associated with the issued tickets;

seating data associated with the issued tickets;

transfer permission data associated with the issued tickets;

determine if the received barcode data is in accordance with a first specified format;

determine if the received barcode data corresponds to barcode data stored in the data store;

when the received barcode data corresponds to barcode data stored in the data store, determine if the received event data corresponds to the event data associated with the issued tickets for the event;

determine if the received seating data corresponds to barcode data stored in the data store;

determine if the received barcode data is associated with a ticket that is not to be transferred via at least a first transaction type;

transmit a positive verification and transfer right indication based at least in part on the determination that;

the received barcode data is in accordance with a first specified format;

the received barcode data corresponds to barcode data stored in the data store;

the received event data corresponds to the event data associated with the issued tickets for the event; and

the received seating data corresponds to barcode data stored in the data store.

19. The program code as defined in claim 18, wherein the program code is configured to receive the barcode data via a barcode reader system and/or via manual entry.

20. The program code as defined in claim 18, wherein the program code is further configured to access and provide to the first user with:

an event name associated with at least one ticket previously acquired by the first user;

an indication as to whether the first user had transferred at least one ticket via a service offered by the first website; and

an indication as to whether the first user had transferred at least one ticket via a service offered by a different website that a website that hosts the program code.

21. The program code as defined in claim 18, wherein the program code is further configured to:

receive a locator associated with a posting of the ticket from the first user and/or the second user; and

access a web resource hosted by a web server associated with the locator;

access from the web resource the seating and event data manually provided by the first user and/or the second user via the web server.

22. The program code as defined in claim 18, wherein the program code is further configured to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the event date has passed or that there is insufficient time before event to process ticket transfer.

23. The program code as defined in claim 18, wherein the program code is further configured to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the event is cancelled.

24. The program code as defined in claim 18, wherein the program code is further configured to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that ticket is being offered by the first user with a second ticket wherein the seat associated with the ticket is not adjacent to a seat associated with the second ticket.

25. The program code as defined in claim 18, wherein the program code is further configured to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the ticket has already been transferred by the first user.

26. The program code as defined in claim 18, wherein the program code is further configured to determine if the ticket is transferable based at least in part on an indication stored in computer readable memory that the ticket is a complementary ticket.

27. A verification system comprising:

an interface configured to receive coded data associated with a ticket for a ticketed event;

a data store stored that stores;

coded data for issued tickets associated for the ticketed event;

event data associated with the issued tickets;

seating data associated with the issued tickets;

program code stored in non-transitory memory, that when executed by a computing device is configured to;

determine if the received coded data is in accordance with a first specified format;

determine if the received coded data corresponds to coded data stored in the data store;

determine if event data received in association with the coded data corresponds to the event data associated with the issued tickets for the event;

transmit a positive verification based at least in part on the determination that;

the received coded data is in accordance with a first specified format;

the received coded data corresponds to coded data stored in the data store; and

the received event data corresponds to the event data associated with the issued tickets for the event.

28. The verification system as defined in claim 27, wherein the program code is further configured to:

provide an interface configured to receive seating and event data manually provided by a first user offering the ticket and/or by a second user seeking to acquire the ticket;

determine if the received seating data corresponds to seating data stored in the data store; and

transmit a positive verification based, in part on the determination that the received seating data corresponds to coded data stored in the data store.

29. The verification system as defined in claim 28, wherein the program code is configured to:

receive a locator associated with a posting of the ticket from the first user and/or the second user; and

access a web resource hosted by a web server associated with the locator;

access from the web resource the seating and event data manually provided by the first user and/or the second user via the web server.

30. The verification system as defined in claim 27, wherein the program code is further configured to:

determine if the received coded data is associated with a ticket that is not to be transferred via at least a first transaction type; and

transmit a transfer right indication based at least in part on the determination that received coded data is associated with a ticket that may be transferred via at least a first transaction type.

31. The verification system as defined in claim 27, wherein the coded data is barcode data.

32. The verification system as defined in claim 27, wherein the verification system is associated with a first website that enables a user to acquire and transfer tickets and provides a ticket management user interface via which a user can access ticket data related to tickets acquired by the user, the ticket data including at least:

an event name associated with at least one ticket previously acquired by the user;

an indication as to whether the user had transferred at least one ticket via a service offered by the first website; and

an indication as to whether the user had transferred at least one ticket via a service offered by a different website.

33. The verification system as defined in claim 27, wherein the program code is configured to determine if the ticket is transferable based at least in part on an indication that the event date has passed or that there is insufficient time before event to process ticket transfer.

34. The verification system as defined in claim 27, wherein the program code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the event is cancelled.

35. The verification system as defined in claim 27, wherein the program code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that ticket is being offered by the a user with a second ticket wherein the seat associated with the ticket is not adjacent to a seat associated with the second ticket.

36. The verification system as defined in claim 27, wherein the program code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket has already been transferred by a user.

37. The verification system as defined in claim 27, wherein the program code is configured to determine if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket is a complementary ticket.

38. A method of verifying a ticket, comprising:

receiving coded data associated with a ticket for a ticketed event;

determining, using a computing device, if the received coded data is in accordance with a first specified format;

determining, via the computing device, if the received coded data corresponds to coded data stored in a data store;

determining, via the computing device, if event data received in association with the coded data corresponds to event data associated with an issued ticket for the event; and

transmitting, via the computing device, a positive verification based at least in part on the determination that;

the received coded data is in accordance with a first specified format;

the received coded data corresponds to coded data stored in the data store; and

the received event data corresponds to the event data associated with the issued ticket for the event.

39. The method as defined in claim 38, the method further comprising:

providing an interface configured to receive seating and event data manually provided by a first user offering the ticket and/or by a second user seeking to acquire the ticket;

determining if the received seating data corresponds to coded data stored in the data store; and

transmitting a positive verification based, in part, on the determination that the received seating data corresponds to coded data stored in the data store.

40. The method as defined in claim 38, the method further comprising:

receiving a locator associated with a posting of the ticket from the first user and/or the second user; and

accessing a web resource hosted by a web server associated with the locator;

accessing from the web resource the seating and event data manually provided by the first user and the second user via the web server.

41. The method as defined in claim 38, the method further comprising:

determining if the received coded data is associated with a ticket that is not to be transferred via at least a first transaction type; and

transmitting a transfer right indication based at least in part on the determination that received coded data is associated with a ticket that may be transferred via at least a first transaction type.

42. The method as defined in claim 38, wherein the coded data is barcode data.

43. The method as defined in claim 38, the method further comprising:

providing a user interface via which a user can access ticket data related to tickets acquired by the user, the ticket data including at least;

an event name associated with at least one ticket previously acquired by the user;

an indication as to whether the user had transferred at least one ticket via a service offered by the first website; and

an indication as to whether the user had transferred at least one ticket via a service offered by a different website.

44. The method as defined in claim 38, the method further comprising determining if the ticket is transferable based at least in part on an indication that the event date has passed or that there is insufficient time before event to process ticket transfer.

45. The method as defined in claim 38, the method further comprising determining if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the event is cancelled.

46. The method as defined in claim 38, the method further comprising determining if the ticket is transferable based at least in part on an indication stored in non-transitory memory that ticket is being offered by the a user with a second ticket wherein the seat associated with the ticket is not adjacent to a seat associated with the second ticket.

47. The method as defined in claim 38, the method further comprising determining if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket has already been transferred by a user.

48. The method as defined in claim 38, the method further comprising determining if the ticket is transferable based at least in part on an indication stored in non-transitory memory that the ticket is a complementary ticket.