IP Library Granted Patent US 12,256,282
Granted Patent B2
US 12,256,282 · App. 17/139,114 · Granted Mar 18, 2025

System and method for using a mobile device as an input device for surveys at a live event

Inventor: Jovan Hutton Pulitzer (Frisco, TX)
Assignee: Tesla Laboratories, LLC
H04W4/021G06F16/9554G06Q10/02G06Q30/0201G06Q30/0241H04W4/21H04W4/33H04L67/306H04L67/52H04M3/42357
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 12,256,282
App. No.
17/139,114
Granted
Mar 18, 2025
Kind
B2
Abstract

A method is provided for interacting with audience members in an event, each of the potential attendees having available thereto a unique identifier. The method comprises creating, for an attendee, a unique ID (UID) on a mobile wireless device (MWD) by the steps of inputting to the MWD one of the unique identifiers, combining the obtained unique identifier with a UID time stamp at the time of creation of the UID; receiving with a server on a first wireless channel communications from the MWD; registering the UID at the physical location of the event; generating a visual query; displaying on the MWD response indicators; receiving at the server from the registered attendee a response, to the query over the first wireless channel; and storing in a database on the server the received response in association with the displayed query.

Claims (47)

1. A method for interacting with audience members in an event, wherein the event has a finite number of participating attendees selected from attendees of the event, comprising the steps of:

for each participating attendee, creating a unique combined ID (UID) on a mobile wireless device (MWD) by the steps of:

detecting a presence of the MWD by a beacon device;

generating by the beacon device a signal configured for detection by the MWD;

launching an application stored on the MWD in response to a detection of the signal;

inputting to the MWD an identifier;

creating the combined UID by combining the input identifier with a UID timestamp corresponding to a time of creation of the UID, wherein the UID comprises an identifier portion that includes the input identifier and a UID timestamp portion so as to distinguish two different UIDs having a duplicate identifier portion; and

accepting and storing the combined UID in a database;

receiving with a server, on a wireless channel, communications from the MWD of each participating attendee; and

registering the combined UID of each participating attendee at a venue of the event.

2. The method of claim 1 , wherein the identifier is a fixed location associated with the venue.

3. The method of claim 2 , wherein the fixed location is a defined seat in the venue having a seat identifier as the fixed location.

4. The method of claim 2 , wherein registering each respective combined UID comprises recognizing each respective MWD at the respective fixed location within the venue.

5. The method of claim 4 , wherein recognizing each respective MWD comprises a scan of the MWD in a vicinity of the respective fixed location.

6. The method of claim 1 , wherein registering each respective combined UID comprises responding to a request for registration by transmitting the respective combined UID to the server over the wireless channel.

7. The method of claim 1 , further comprising:

generating at the server a visual query;

displaying on a physical display at the event the visual query, wherein the visual query relates to a plurality of visual messages;

displaying on the MWD of each participating attendee response indicators;

receiving at the server from each participating attendee a response, each response resulting from one of the participating attendees selecting one of the response indicators, to the visual query over the wireless channel;

storing in the database on the server the received responses in association with the displayed visual query;

associating the respective received responses with the respective combined UIDs;

creating a query ID (QID) associated with the displayed visual query; and

creating respective response time stamps indicating respective times at which the respective received responses were received by the server.

8. The method of claim 7 , further comprising:

creating a combined UID data record for each combined UID, each combined UID data record including:

the respective UID,

the QID,

the respective received response, and

the respective response time stamp.

9. The method of claim 8 , further comprising:

creating a QID data record for the QID, the QID data record including:

the QID;

each of the respective received responses,

each respective UID, and

each respective response time stamp;

performing statistical analysis on the QID data record;

selecting, based on the statistical analysis of the QID record, one of the visual messages from the plurality of visual messages; and

displaying on the physical display at the event the selected visual message.

10. The method of claim 9 , further comprising associating each respective received response with statistical information related to an attendee classification.

11. The method of claim 9 , further comprising assigning each respective combined UID to a statistical category based on the respective received response and the displayed query.

12. The method of claim 9 , wherein the combined UID data record also includes statistical information that is related to an attendee classification and that is based on the received response.

13. The method of claim 7 , wherein the response indicators comprise at least one of:

alphabetic symbols;

numeric symbols; and

symbols of differing colors.

14. The method of claim 7 , wherein receiving at the server the responses includes receiving the responses within a defined time window.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 31, 2020
From: PULITZER, JOVAN HUTTON
To: TESLA LABORATORIES, LLC
Reel/Frame 054784/0429 →
Continuity (14)
Continuation 16186293 · Nov 9, 2018
Continuation 15402738 · Jan 10, 2017
Continuation 15360697 · Nov 23, 2016
Continuation In Part 15146464 · May 4, 2016
Provisional Application 62258990 · Nov 23, 2015
Provisional Application 62258983 · Nov 23, 2015
Provisional Application 62258988 · Nov 23, 2015
Provisional Application 62258982 · Nov 23, 2015
Provisional Application 62258985 · Nov 23, 2015
Provisional Application 62258994 · Nov 23, 2015
Provisional Application 62258987 · Nov 23, 2015
Provisional Application 62258989 · Nov 23, 2015
Provisional Application 62258996 · Nov 23, 2015
Related Publication 20210235218A1 · Jul 29, 2021
References Cited (37)
US 6650903B2 · Inselberg · 2003 [cited by applicant]
US 8417221B2 · Shaw · 2013 [cited by applicant]
US 8520502B2 · Tenny · 2013 [cited by examiner]
US 9060039B2 · Walsh · 2015 [cited by examiner]
US 9226156B2 · O'Toole · 2015 [cited by examiner]
US 9646382B2 · Hawkins · 2017 [cited by applicant]
US 9817557B2 · Gresham et al. · 2017 [cited by applicant]
US 9836755B2 · Zamer · 2017 [cited by examiner]
US 10176486B2 · Pulitzer · 2019 [cited by applicant]
US 10178710B2 · Pulitzer · 2019 [cited by applicant]
US 10353982B1 · Kumar · 2019 [cited by examiner]
US 10524309B2 · Pulitzer · 2019 [cited by applicant]
US 10547742B2 · Pulitzer · 2020 [cited by applicant]
US 11012536B2 · Awad et al. · 2021 [cited by applicant]
US 11412575B2 · Pulitzer · 2022 [cited by applicant]
US 20040158865A1 · Kubler et al. · 2004 [cited by applicant]
US 20070294096A1 · Randall et al. · 2007 [cited by applicant]
US 20090271740A1 · Ryan-Hutton et al. · 2009 [cited by applicant]
US 20100262932A1 · Pan · 2010 [cited by examiner]
US 20100306064A1 · Inselburg · 2010 [cited by applicant]
US 20110271295A1 · Redmann et al. · 2011 [cited by applicant]
US 20120221962A1 · Lew et al. · 2012 [cited by applicant]
US 20130116044A1 · Schwartz · 2013 [cited by applicant]
US 20130157693A1 · Mercuri et al. · 2013 [cited by applicant]
US 20150012308A1 · Snyder · 2015 [cited by examiner]
US 20150149619A1 · Tsuji et al. · 2015 [cited by applicant]
US 20150281878A1 · Roundtree et al. · 2015 [cited by applicant]
US 20160110467A1 · Hern · 2016 [cited by applicant]
US 20160156638A1 · Somani et al. · 2016 [cited by applicant]
US 20160335564A1 · Downy et al. · 2016 [cited by applicant]
US 20170018004A1 · Walden · 2017 [cited by applicant]
US 20170155761A1 · Pulitzer · 2017 [cited by applicant]
US 20170280298A1 · Mycek et al. · 2017 [cited by applicant]
US 20190082049A1 · Pulitzer · 2019 [cited by applicant]
Anonymous: “Does an app exist to auto-launch an app when . . . | Android Development and Hacking”, Jun. 5, 2017 (Jun. 5, 2017), pp. 1-4, XP055652647, Retrieved from the Internet: URL: https://forum.xda-developers.com/sh… [cited by applicant]
Anonymous: “NFC Basics | Android Developers”, Feb. 19, 2014 (Feb. 19, 2014), XP055332687, Retrieved from the Internet: URL: http://web.archive.org/web/20140219150611/http://developer.android.com/guide/topics/connectivit… [cited by applicant]
EP: Article 94(3) Communication of 16869004.8 (related case); Jan. 2, 2020; 8 pages. [cited by applicant]