IP Library Granted Patent US 9,881,433
Granted Patent B2
US 9,881,433 · App. 14/638,411 · Granted Jan 30, 2018

Systems and methods for electronic ticket validation using proximity detection

Inventors: Micah Bergdale (New York, NY); Matthew Grasser (New York, NY); Nicholas Ihm (New York, NY); Gregory Valyer (Highland Park, IL)
G07C9/00111G07C9/00103G07B15/00G07C9/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,881,433
App. No.
14/638,411
Granted
Jan 30, 2018
Kind
B2
Abstract

Systems and methods for monitoring permission to be in a location comprising: a secured area having at least one entry point with a mechanical gate having an open and closed position; at least two wireless proximity sensors attached to a portion of (or the area adjacent to) the mechanical gate; a token device in communication with the wireless proximity sensors that determine a location of the token device relative to one of the wireless proximity sensors to provide a detection data point and a set of detection data points for the group of detection data points; and a system computing device that calculates the shared proximity of the token device. If the token device contains a valid ticket and the shared proximity of the token device is within a predetermined area the system computing device will cause the mechanical gate to go to the open position.

Claims (54)

1. A system for monitoring permission for persons to be in a location, said system comprising:

a secured area having at least one entry point, wherein each of the entry points have a mechanical gate with an open position and a closed position;

at least two bluetooth low energy wireless proximity sensors attached to at least one of a portion of the mechanical gate and an area adjacent to a portion of the mechanical gate;

a token device in communication with the at least two bluetooth low energy wireless proximity sensors and a system computing device, wherein each of the at least two bluetooth low energy wireless proximity sensors are used by the system computing device to determine a relative location of the token device relative to one of the at least two bluetooth low energy wireless proximity sensors according to signal strength to provide a detection data point for each of the at least two bluetooth low energy wireless proximity sensors and a set of detection data points for the group of detection data points;

wherein the system computing device calculates the shared proximity of the token device according to the set of detection data points and determines that the token device contains a valid ticket or does not contain a valid ticket, wherein the token device contains a valid ticket and the system computing device determines the shared proximity of the token device is within a predetermined area the system computing device will cause the mechanical gate to go to the open position.

2. A system as in claim 1 , wherein the system computing device causes the mechanical gate to go to a closed position upon determining that the shared proximity of the token device is outside a predetermined area.

3. A system as in claim 1 , wherein the system computing device calculates the shared proximity of the token device according to triangulation of the set of detection data points.

4. A system as in claim 1 , wherein the system computing device calculates the shared proximity of the token device according to geometric calculations of the set of detection data points.

5. A system as in claim 1 , wherein the system computing device calculates the shared proximity of the token device according to a sensor sensitivity profile.

6. A system as in claim 1 , wherein the system computing device calculates the shared proximity of the token device according to a sensor sensitivity profile that has a predetermined range of shapes from a signal of a predetermined set of strengths at each of the at least two bluetooth low energy wireless proximity sensors and determines that the shared proximity of the token device is within the predetermined area to cause the mechanical gate to go to the open position only when the sensor sensitivity profile is in the predetermined range of shapes.

7. A system as in claim 1 , further comprising at least one light beam in the mechanical gate, wherein the at least one light beam must be tripped, the token device must contain a valid ticket and the system computing device must determine the shared proximity of the token device to be within a predetermined area for mechanical gate to go to the open position.

8. The system as in claim 1 , further comprising an additional ticket validation, wherein there must be the additional ticket validation, the token device must contain a valid ticket and the system computing device must determine the shared proximity of the token device to be within a predetermined area for mechanical gate to go to the open position.

9. The system as in claim 8 , wherein the additional ticket validation is selected from the group consisting of visual validation, fingerprint scanning, sound sampling, facial recognition, a light beam, Bluetooth LE, wireless proximity analysis, GPS, geo-fencing, automated license plate reading, fingerprint scanning, facial recognition, unique alphanumeric ID entry via a keyboard, numeric keypad.

10. A system as in claim 7 , wherein the shared proximity of the token device is determined according to one detection data point in the set of detection data points and the at least one light beam.

11. A system as in claim 1 , wherein the token device is determined to contain a valid ticket by having a stored ticket token that is transmitted to the system computing device.

12. A system as in claim 11 , wherein the stored ticket token is transmitted to the system computing device over a secure data channel.

13. A system as in claim 11 , wherein the stored ticket token is generated by the system computing device using at least one of the token device International Mobile Equipment Identity (IMEI) number, token device Unique Device identifier (UDID) and the token device serial number.

14. A system as in claim 1 , further comprising an activated ticket indicator for valid tickets that activated.

15. A system as in claim 1 , wherein the token device is selected from the group consisting of a mobile phone, smartphone, computing device, luggage tag, lanyard, card, physical ticket, shipping label with barcode, NFC, RFID, UDID, Bluetooth ID.

16. A system as in claim 1 , further comprising a secure data channel between the token device and the computing device, wherein the computing device determines that the token device contains a valid ticket or does not contain a valid ticket by fetching a stored ticket token on the token device and transmitting the stored ticket token from the token device to the computing device over the secure data channel.

17. A system as in claim 1 , further comprising a ticketing verification system in communication with the token device, wherein the ticketing verification system provides the token device with a valid ticket and wherein the system computing device determines that the token device contains a valid ticket from the ticketing verification system to cause the mechanical gate to go to the open position.

18. A method of validating a ticket and monitoring permission for persons to be in a location, the method comprising:

providing a secured area having at least one entry point, wherein each of the entry points have a mechanical gate with an open position and a closed position;

providing at least two bluetooth low energy wireless proximity sensors attached to at least one of a portion of the mechanical gate and an area adjacent to a portion of the mechanical gate;

providing a token device in communication with the at least two bluetooth low energy wireless proximity sensors and a system computing device;

determining a relative location of the token device relative to one of the at least two bluetooth low energy wireless proximity sensors according to signal strength to provide a detection data point for each of the at least two wireless proximity sensors and a set of detection data points for the group of detection data points;

calculating, by the system computing device, the shared proximity of the token device according to the set of detection data points;

determining whether the token device contains a valid ticket or does not contain a valid ticket;

directing, by the system computing device, the mechanical gate to go to open position upon determination that the token device contains a valid ticket and the shared proximity of the token device is within a predetermined area.

19. A method as in claim 18 , further comprising the step of:

determining that the shared proximity of the token device is outside a predetermined area and directing, by the system computing device, the mechanical gate to go to closed position.

20. A method as in claim 18 , wherein the step of calculating, by system computing device, the shared proximity of the token device is according to triangulation of the set of detection data points.

21. A method as in claim 18 , wherein the step of calculating, by system computing device, the shared proximity of the token device is according to geometric calculations of the set of detection data points.

22. A method as in claim 18 , wherein the step of calculating, by system computing device, the shared proximity of the token device is according to a sensor sensitivity profile.

23. A method as in claim 18 , wherein the step of calculating, by system computing device, the shared proximity of the token device is according to a sensor sensitivity profile that has a predetermined range of shapes from a signal of a predetermined set of strengths at each of the at least two wireless proximity sensors and the system computing device determines that the shared proximity of the token device is within the predetermined area to cause the mechanical gate to go to the open position only when the sensor sensitivity profile is in the predetermined range of shapes.

24. A method as in claim 18 , further comprising at least one light beam in the mechanical gate, wherein the at least one light beam must be tripped, the token device must contain a valid ticket and the system computing device must determine the shared proximity of the token device to be within a predetermined area for mechanical gate to go to the open position.

25. The method as in claim 18 , further comprising the step of:

determining an additional ticket validation, wherein there must be the additional ticket validation, the token device must contain a valid ticket and the system computing device must determine the shared proximity of the token device to be within a predetermined area for mechanical gate to go to the open position.

26. The method as in claim 25 , wherein the additional ticket validation is selected from the group consisting of visual validation, fingerprint scanning, sound sampling, facial recognition, a light beam, Bluetooth LE, wireless proximity analysis, GPS, geo-fencing, automated license plate reading, fingerprint scanning, facial recognition, unique alphanumeric ID entry via a keyboard, numeric keypad.

27. A method as in claim 24 , wherein the shared proximity of the token device is determined according to one detection data point in the set of detection data points and the at least one light beam.

28. A method as in claim 18 , wherein the token device is determined to contain a valid ticket by having a stored ticket token that is transmitted to the system computing device.

29. A method as in claim 28 , further comprising the step of:

transmitting the stored ticket token to the system computing device over a secure data channel.

30. A method as in claim 28 , wherein the stored ticket token is generated by the system computing device using at least one of the token device International Mobile Equipment Identity (IMEI) number, token device Unique Device Identifier (UDID) and the token device serial number.

31. A method as in claim 18 , further comprising the step of:

requiring a ticket to be activated to be a valid ticket; and

causing an activated ticket indicator to be displayed for a valid ticket.

32. A method as in claim 18 , wherein the token device is selected from the group consisting of a mobile phone, smartphone, computing device, luggage tag, lanyard, card, physical ticket, shipping label with barcode, NFC, RFID, UDID, Bluetooth ID.

33. A method as in claim 18 , further comprising the steps of:

establishing a secure data channel between the token device and the computing device;

determining, by the computing device, that the token device contains a valid ticket or does not contain a valid ticket by fetching a stored ticket token on the token device; and

transmitting the stored ticket token from the token device to the computing device over the secure data channel.

34. A method as in claim 18 , further comprising the steps of:

providing a ticketing verification system in communication with the token device, wherein the ticketing verification system provides the token device with a valid ticket and wherein the system computing device determines that the token device contains a valid ticket from the ticketing verification system to cause the mechanical gate to go to the open position.

Assignments (5)
MERGER AND CHANGE OF NAME Recorded Aug 29, 2023
From: BYTEMARK, INC.; SIEMENS MOBILITY, INC.
To: SIEMENS MOBILITY, INC.
Reel/Frame 064739/0634 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 22, 2020
From: GRASSER, MATTHEW
To: BYTEMARK, INC.
Reel/Frame 053276/0650 →
RELEASE OF SECURITY INTEREST Recorded Nov 8, 2017
From: BILLYBEY HOLDING COMPANY LLC
To: BYTEMARK INC.
Reel/Frame 044412/0991 →
SECURITY INTEREST Recorded Aug 4, 2017
From: BYTEMARK INC.
To: BILLYBEY HOLDING COMPANY LLC
Reel/Frame 043204/0865 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 14, 2015
From: BERGDALE, MICAH; GRASSER, MATTHEW; IHM, NICHOLAS; VALYER, GREGORY
To: BYTEMARK, INC.
Reel/Frame 035404/0364 →
Continuity (7)
Continuation 14496645 · Sep 25, 2014
Continuation In Part 13901243 · May 23, 2013
Continuation 14538008 · Nov 11, 2014
Provisional Application 61948187 · Mar 5, 2014
Provisional Application 61883097 · Sep 26, 2013
Provisional Application 61902469 · Nov 11, 2013
Related Publication 20150213660A1 · Jul 30, 2015