Sign In to Follow Application
View All Documents & Correspondence

Area Tracking Systems And Methods Of Tracking Electronic Devices

Abstract: Area tracking systems (100) including a plurality of short range sensors (150) that are communicatively connected to a server (110) and methods of tracking electronic devices (160). The electronic devices (160) are tracked by polling for the electronic devices (S500 S600) the polling including transmission of electronic addresses corresponding to the electronic devices and determining whether a reply to the poling is received (S510 S610). The electronic addresses are each stored on one of a plurality of lists. Each of the lists may be polled at a different frequency and may include a different number of electronic device addresses.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
10 July 2013
Publication Number
50/2014
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2022-03-24
Renewal Date

Applicants

ALCATEL LUCENT
3 avenue Octave Gréard F 75007 Paris

Inventors

1. WENGROVITZ Michael
1315 Old Marlboro Road Concord MA 01742
2. JANISZEWSKI Tom
11 Spring Hunter Court Andover NJ 07821
3. ZHOU Qiru
558 Pine Street Scotch Plains NJ 07076

Specification

AREA TRACKING SYSTEMS
AND METHODS OF TRACKING ELECTRONIC DEVICES
BACKGROUND OF THE INVENTION
Field
Example embodiments relate t o area tracking systems and
methods of tracking electronic devices, and more particularly t o a n
area tracking system including a distributed network of short range
sensors and methods of detecting the location of electronic devices
using the short range sensors.
Description o f the related Art
Short range wireless connectivity for exchanging data between
electronic devices is widely used. For example, Bluetooth radios are
resident in a wide range of electronic devices and in almost all mobile
phones and smart phones. Bluetooth is a n open wireless technology
standard for exchanging data over a range from about l m t o about
100m using frequency-hopping spread spectrum which divides data
over a s many a s 7 9 bands ( 1 MHz each) in the range 2402-2480 MHz.
A multitude of services may b e offered t o a user using a
Bluetooth radio t o connect a foreign electronic device t o a user's
device. Many of the services can expose private data or allow the
foreign party t o control the user's device. Accordingly, it is in the
interest of the user t o b e able t o screen which devices are allowed t o
connect t o their device. However, for convenience, it is also in the
interest of the user t o allow foreign Bluetooth devices t o automatically
establish a connection without user intervention when they come into
range.
To accommodate both interests, Bluetooth uses a process called
pairing t o establish a connection between electronic devices. A user
generally initiates pairing manually by exposing their device's
Bluetooth link t o other devices. The pairing process is typically
triggered automatically the first time a device receives a connection
request from a device with which it is not yet paired. Once a pairing
has been established each device retains a record of the pairing and
the devices may subsequently reconnect t o each other without user
intervention.
Bluetooth is a packet-based protocol with a master-slave
relationship. The master device is responsible for timing and access
control in a Bluetooth network (e.g., a "piconet") and may b e
connected t o a s many a s 7 slave devices.
Each Bluetooth enabled device includes a Bluetooth radio that
is identified by a unique permanent 48-bit Bluetooth Device Address
(BD_ADDR). I n general, electronic devices including Bluetooth radios
are personal t o a specific user and the detection of a specific
BD_ADDR in most cases is the same a s detection of the specific user.
In certain cases, for example a s with a security supervisor in a n
airport, the user carries multiple Bluetooth enabled devices and the
detection of more the one of the devices increases the probability that
the user is present.
The detectability of a Bluetooth device is dependent on a mode
setting of the device. In a discovery/ inquiry mode, a discovering
device sends identification (ID) packets including a n access code such
a s a General Inquiry Access code (GIAC), a Dedicated Inquiry Access
Code (DIAC) or a Limited Inquiry Access Code t o every device in
proximity of the discovering device. Any device in the discoverable
mode that is within range responds t o the ID packets by sending a
Frequency Hop Synchronization (FHS) packet that discloses the
BD_ADDR and native clock (CLKN) of the discovered device.
However, many electronic devices in widespread usage are
configured t o b e in a non-discoverable mode. For example, certain
phones d o not promiscuously respond t o a general discovery inquiry
due t o security and privacy concerns. Allowing promiscuous
discovery may result in the user being sent messages they are not
intended t o receive, thereby allowing phone spamming. The setting
for discoverability is typically not exposed t o a user and is often fixed
by the manufacturer of the electronic device.
Electronic devices that are not in the discoverable mode but are
set t o b e connectable can still b e detected in the page and page scan
states. In paging, the master device will transmit a n ID packet
including a Device Access Code (DAC) that is based on the Lower
Address part (LAP) of the user's BD_ADDR. When the electronic
device of the user detects the ID packet including the user device's
DAC, it will reply by transmitting the user device's DAC back t o the
discovering device. A typical response time t o paging is 1 sec or less.
In complex and/ or cluttered radio environments, a response time may
b e 2-3 seconds.
Although a user device is discoverable in the page and page
scan states, the detecting device must have possession of, for
example, the user's DAC.
SUMMARY OF THE INVENTION
Example embodiments include a n area tracking system having
a server connected t o a network and a plurality of sensors connected
t o the server. The sensors are configured t o poll for a t least one
electronic device using a n identification packet including a n address
of the electronic device.
Other example embodiments include methods of tracking a
plurality of electronic devices using a plurality of sensors connected t o
a server. The methods include polling, by a sensor, for a first
electronic device using a n identification packet that includes a n
address of the first electronic device, and determining whether the
first electronic device is within range of the sensor based on whether
or not the first electronic device replies t o the polling within a period of
time. A server transmits data relating t o a position of the first
electronic device.
Still other example embodiments include methods of tracking a
plurality of electronic devices using a plurality of sensors connected t o
a server. The methods include maintaining, by a first sensor, first and
second lists including a plurality of electronic device addresses
corresponding t o a plurality of electronic devices and sequentially
polling, by the first sensor, for the plurality of electronic devices. The
sequential polling is performed by sequentially transmitting
identification packets including the electronic device addresses of the
first and second lists and determining, by the first sensor, whether
one of the plurality of electronic devices is in range of the first sensor.
The first sensor determines if one of the plurality of electronic devices
is in range of the first sensor based on whether or not a reply t o the
sequential poll corresponding t o the one of the plurality of electronic
devices is received by the first sensor within a first period of time. A
server transmits data relating t o a position of the one of the electronic
devices.
BRIEF DESCRIPTION OF THE DRAWINGS
The present invention will become more fully understood from
the detailed description given herein below and the accompanying
drawings, wherein like elements are represented by like reference
numerals, which are given by way of illustration only and thus are not
limiting of the present invention and wherein:
FIG. 1 is a diagram illustrating area tracking systems according
t o a n example embodiment;
FIG. 2 is a schematic diagram illustrating area tracking servers
according t o a n example embodiment;
FIG. 3 is a perspective diagram illustrating kiosks according t o
a n example embodiment;
FIG. 4 is a flow diagram illustrating methods of tracking
electronic devices using short range scanners/ sensors according t o a
single list example embodiment;
FIG. 5 is a flow diagram illustrating methods of tracking
electronic devices using short range scanners/ sensors according t o a
first list of a dual list example embodiment;
FIG. 6 is a flow diagram illustrating methods of tracking
electronic devices using short range scanners/ sensors according t o a
second list of a dual list example embodiment; and
FIG. 7 is a flow diagram illustrating methods of administering
the tracking of electronic devices a t a server according t o a n example
embodiment.
It should be noted that these Figures are intended t o illustrate
the general characteristics of methods, structure and/ or materials
utilized in certain example embodiments and t o supplement the
written description provided below. These drawings are not, however,
t o scale and may not precisely reflect the precise structural or
performance characteristics of any given embodiment, and should not
be interpreted a s defining or limiting the range of values or properties
encompassed by example embodiments. For example, the relative
thicknesses and positioning of molecules, layers, regions and/ or
structural elements may be reduced or exaggerated for clarity. The use
of similar or identical reference numbers in the various drawings is
intended t o indicate the presence of a similar or identical element or
feature.
DETAILED DESCRIPTION
While example embodiments are capable of various
modifications and alternative forms, embodiments thereof are shown
by way of example in the drawings and will herein be described in
detail. It should be understood, however, that there is n o intent t o
limit example embodiments t o the particular forms disclosed, but on
the contrary, example embodiments are t o cover all modifications,
equivalents, and alternatives falling within the scope of the claims.
Like numbers refer t o like elements throughout the description of the
figures.
Before discussing example embodiments in more detail, it is
noted that some example embodiments are described a s processes or
methods depicted a s flowcharts. Although the flowcharts describe the
operations a s sequential processes, many of the operations may be
performed in parallel, concurrently or simultaneously. I n addition,
the order of operations may be re-arranged. The processes may be
terminated when their operations are completed, but may also have
additional steps not included in the figure. The processes may
correspond t o methods, functions, procedures, subroutines,
subprograms, etc.
Methods discussed below, some of which are illustrated by the
flow charts, may be implemented by hardware, software, firmware,
middleware, microcode, hardware description languages, or any
combination thereof. When implemented in software, firmware,
middleware or microcode, the program code or code segments t o
perform the necessary tasks may be stored in a machine or computer
readable medium such a s a storage medium. A processor(s) may
perform the necessary tasks.
Specific structural and functional details disclosed herein are
merely representative for purposes of describing example
embodiments of the present invention. This invention may, however,
be embodied in many alternate forms and should not be construed a s
limited t o only the embodiments set forth herein.
It will be understood that, although the terms first, second, etc.
may be used herein t o describe various elements, these elements
should not be limited by these terms. These terms are only used t o
distinguish one element from another. For example, a first element
could be termed a second element, and, similarly, a second element
could be termed a first element, without departing from the scope of
example embodiments. As used herein, the term "and/or" includes
any and all combinations of one or more of the associated listed items.
It will be understood that when a n element is referred t o a s
being "connected" or "coupled" t o another element, it can be directly
connected or coupled t o the other element or intervening elements
may be present. I n contrast, when a n element is referred t o a s being
"directly connected" or "directly coupled" t o another element, there are
n o intervening elements present. Other words used t o describe the
relationship between elements should be interpreted in a like fashion
{e.g., "between" versus "directly between," "adjacent" versus "directly
adjacent," etc.).
The terminology used herein is for the purpose of describing
particular embodiments only and is not intended t o be limiting of
example embodiments. As used herein, the singular forms "a," "an"
and "the" are intended t o include the plural forms a s well, unless the
context clearly indicates otherwise. It will be further understood that
the terms "comprises," "comprising," "includes" and/ or "including,"
when used herein, specify the presence of stated features, integers,
steps, operations, elements and/or components, but d o not preclude
the presence or addition of one or more other features, integers, steps,
operations, elements, components and/ or groups thereof.
It should also be noted that in some alternative
implementations, the functions/ acts noted may occur out of the order
noted in the figures. For example, two figures shown in succession
may in fact be executed concurrently or may sometimes be executed
in the reverse order, depending upon the functionality/ acts involved.
Unless otherwise defined, all terms (including technical and
scientific terms) used herein have the same meaning a s commonly
understood by one of ordinary skill in the art t o which example
embodiments belong. I t will be further understood that terms, e.g.,
those defined in commonly used dictionaries, should be interpreted a s
having a meaning that is consistent with their meaning in the context
of the relevant art and will not be interpreted in a n idealized or overly
formal sense unless expressly s o defined herein.
Portions of the example embodiments and corresponding
detailed description are presented in terms of software, or algorithms
and symbolic representations of operation on data bits within a
computer memory. These descriptions and representations are the
ones by which those of ordinary skill in the art effectively convey the
substance of their work t o others of ordinary skill in the art. An
algorithm, a s the term is used here, and a s it is used generally, is
conceived t o be a self-consistent sequence of steps leading t o a desired
result. The steps are those requiring physical manipulations of
physical quantities. Usually, though not necessarily, these quantities
take the form of optical, electrical, or magnetic signals capable of
being stored, transferred, combined, compared, and otherwise
manipulated. It has proven convenient a t times, principally for
reasons of common usage, t o refer t o these signals a s bits, values,
elements, symbols, characters, terms, numbers, or the like.
I n the following description, illustrative embodiments will be
described with reference t o acts and symbolic representations of
operations (e.g., in the form of flowcharts) that may be implemented a s
program modules or functional processes include routines, programs,
objects, components, data structures, etc., that perform particular
tasks or implement particular abstract data types and may be
implemented using existing hardware a t existing network elements.
Such existing hardware may include one or more Central Processing
Units (CPUs), digital signal processors (DSPs), application-specificintegrated-circuits, field programmable gate arrays (FPGAs) computers
or the like.
It should b e borne in mind, however, that all of these and
similar terms are t o b e associated with the appropriate physical
quantities and are merely convenient labels applied t o these
quantities. Unless specifically stated otherwise, or a s is apparent
from the discussion, terms such a s "processing" or "computing" or
"calculating" or "determining" of "displaying" or the like, refer t o the
action and processes of a computer system, or similar electronic
computing device, that manipulates and transforms data represented
a s physical, electronic quantities within the computer system's
registers and memories into other data similarly represented a s
physical quantities within the computer system memories or registers
or other such information storage, transmission or display devices.
Note also that the software implemented aspects of the example
embodiments are typically encoded on some form of program storage
medium or implemented over some type of transmission medium. The
program storage medium may b e magnetic (e.g., a floppy disk or a
hard drive) or optical (e.g., a compact disk read only memory, or "CD
ROM"), and may b e read only or random access. Similarly, the
transmission medium may b e twisted wire pairs, coaxial cable, optical
fiber, or some other suitable transmission medium known t o the art.
The example embodiments not limited by these aspects of any given
implementation .
FIG. 1 is a diagram illustrating a n area tracking system 100
according t o a n example embodiment. Referring t o FIG. 1 , a n area
tracking system 100 may include a n area tracking server (ATS) 1 10, a
location-based services (LBS) server 120, a network 130, access points
140 and sensors 150.
The ATS 110 may track electronic devices 160, such a s laptops,
netbooks and/or mobile phones, using the sensors 150. The sensors
150 may b e distributed across a defined area in order for the ATS 1 10
t o track the electronic devices 160. According t o a n example
embodiment, the sensors 150 may b e distributed across a large indoor
and/ or outdoor facility (not shown) such a s a n airport, a shopping
mall and/or a college campus. For example, the sensors may b e
distributed across an airport t o track electronic devices a t each airline
gate, retail store, cafe, restaurant, parking lot and hallway.
According t o a n example embodiment, the sensors 150 are
configured t o poll for a t least one electronic device using a n
identification packet including a n address of the electronic device. For
example, the address of the electronic device may b e a BT-MAC-ID
and/or other address that, when broadcast, causes the electronic
device t o reply.
Addresses of electronic devices may b e included in one or more
lists that may b e used by a t least one of the sensors 150 and/ or the
ATS 110. The lists may b e compiled a t the ATS 1 10 and/or sent t o
the ATS 110. The lists may b e maintained by the sensors 150, the
ATS 1 10, or both of the sensors 150 and the ATS 1 10.
According t o a n example embodiment in which each sensor 150
maintains one or more lists of electronic device addresses, a sensor
150 may poll for electronic devices within range of the sensor 150.
For example, the sensor 150 may b e configured t o sequentially
broadcast the addresses of the one or more lists. An electronic device
160 in range of the sensor 150 will reply when receiving a packet
including the address of the electronic device 160. A sensor 150
receiving a reply may notify the ATS 1 10 that a n electronic device 160
has been detected.
Coverage of the sensors 150 may b e overlapping or nonoverlapping. According t o a n example embodiment in which 2 or more
sensors 150 overlap in coverage, a location of a n electronic device may
b e determined with greater accuracy. For example, by using received
signal strength indications (RSSIs) it may b e determined if the
electronic device 160 is closer t o one or the other of the sensors 150.
Tracking, averaging and other methods may also b e used.
The sensors 150 may b e connected t o the ATS 1 10 through the
access points 140 and the network 130. The access points 140 may
b e WiFi access points and the sensors 150 may b e Bluetooth
measurement sensors/ scanners wirelessly connected t o the access
points 140. The network 130 may be, for example, a n internet
protocol (IP) local-are-network (LAN). The sensors 150 may b e
configured in a n access-point-client mode s o that each sensor 150
establishes a client into a n existing WiFi/ LAN infrastructure.
Measurement results collected by the sensors 150 may b e backhauled
t o the network 130 across a WiFi radio link t o the access points 140.
Accordingly, the sensors 150 may only require connection t o a power
source (not shown). The ATS 1 10 may b e connected t o and receive the
measurement results from the network 130.
The sensors 150 may b e connected t o the ATS 1 10 through the
network 130 in a wired configuration not including the access points
140. The sensors 150 may include, for example, WiFi subsystems
configured t o act a s a WiFi access points and provide WiFi-based
network connectivity between electronic devices 160 and the network
130. Although Bluetooth and WiFi occupy the same unlicensed
frequency band a t 2.4 GHz, both types of systems may co-exist,
operate simultaneously and co-reside within the same appliance
without interference due t o adaptive frequency-hopping RF
capabilities resident in all Bluetooth radios. According t o a n example
embodiment not including access points 140, the sensors 150 may
require both a power connection and a wired network connection (not
shown) .
The sensors 150 may b e configured t o operate in mesh network
configurations, and/or in various combinations where a t least one
sensor 150 is a WiFi access point and a t least one sensor 150 is a n
access point client. There are many such examples, combinations
and possibilities known t o those skilled in the art of WiFi network
design and deployment.
A sensor 150 may b e a short range scanner/ sensor transmitting
and receiving data in a range that is less than a range of a base
station connected t o mobile terminals. For example, a range of the
scanner/ sensor may be from about l m t o about 100m. A sensor 150
may include a universal serial bus (USB) Bluetooth dongle attached t o
a WiFi router with suitably modified internal firmware.
According t o other example embodiments, a sensor 150 may b e
a scanner/ sensor with built-in short range transmission capability.
For example, a sensor 150 may b e a scanner/ sensor with built-in
Bluetooth capability and/or may have one or more wired ports. It is
noted that although example embodiments are described herein with
reference t o Bluetooth and WiFi connectivity technologies, example
embodiments are not s o limited and other communication
technologies are contemplated. For example, the sensor 150 may
comply with WiFi/3G/4G and/or other types of network connectivity
standards.
FIG. 2 is a schematic diagram illustrating a n area tracking
server (ATS) 1 10 according t o a n example embodiment. Referring t o
FIG. 2 , a n ATS 1 10 may include a bus 250 connecting a processor
2 10, a memory 220, mass storage 230 and input/output device 240.
The processor 2 10, the input/output device 240, the mass storage
230 and the memory 220 may perform data communication with each
other by using the bus 250. For example, according t o commands of
the processor 2 10, the memory 220 and the processor 2 10 may
exchange data. Accordingly, the memory 220 may store data i n the
memory 220 and/or output data from the memory 220. Similarly,
the mass storage 230 may exchange data with the processor 2 10
and/or a memory controller of the memory 220. The mass storage
230 may store data in the mass storage 230 and/or output data from
the mass storage 230. The memory 220 and/or the mass storage 230
may store codes and/ or programs for operations of the processor 2 10.
The processor 2 10 may execute a program and control the ATS
110. The input/ output device 240 may be used t o input/ output data
to/ from the ATS 110. The ATS 110 may be connected t o a n external
device. For example, the ATS 110 may be connected t o the access
points 140, the sensors 150 and/or the LBS 120 by using the
input/output device 240, and may exchange command and control
information with the sensors 150.
The ATS 110 may be a single controlling server that controls the
sensors 150. The ATS 110 may be resident in a n area including a
distributed network of sensors 150 and/ or may be located remotely
from the sensors 150 across the network 130. For example, the ATS
110 may be in a hosted services deployment. The ATS 110 may
operate in a high-availability and redundant mode for reliability
purposes, s o a s t o eliminate a single point of failure.
Electronic device addresses may be provided t o the ATS 110
and/ or the sensors 150 through, for example, enrollment or
registration by end users of the electronic devices. For example, each
end-user might be required t o provide the BT-MAC-ID, typically
viewable within the About-Menu of his/her mobile phone, a s part of
a n enrollment process. A person might visibly see the BT-MAC-ID in
his/her mobile phone and then, for example, manually enter and
submit this ID t o a n area tracking system 100 by filling out a form,
sending a n email, and/or using a Web or other computer-based
interface.
FIG. 3 is a perspective diagram illustrating a registration kiosk
300 according t o a n example embodiment. Referring t o FIG. 3 , a
registration kiosk 300 may be, for example, a freestanding, self-service
device used t o provide a service and/or sell merchandise t o a user. A
registration kiosk 300 may include a terminal 3 10 mounted on a n
enclosure 320. A user may access services, purchase merchandise
and/or register electronic device addresses using the terminal 3 10.
The kiosk 300 may send registered electronic device addresses t o a n
ATS 110 for distribution t o sensors 150, compile electronic device
address lists for subsequent distribution t o the sensors 150 and/ or
send electronic device addresses directly t o the sensors 150.
According t o a n example embodiment, a registration kiosk 300
may be used t o automatically measure a n electronic device address.
For example, a registration kiosk 300 may emulate the operation of a
Bluetooth headset. A registrant seeking t o register a n electronic
device 160 may enter personal information such a s the registrant's
name and a mobile phone telephone number using the terminal 3 10.
The registrant may be provided with instructions on how t o pair a n
electronic device 160 t o the terminal 3 10 of the registration kiosk 300.
During a pairing process with the registration kiosk 300, a radio
(e.g., a Bluetooth radio) in the terminal 3 10 may determine a n
electronic address of the electronic device 160 which is fully exposed
over-the-air during the pairing process. The address measured by the
terminal during the pairing process may be sent t o the ATS 110. The
ATS 110 may associate the electronic device address with the personal
information entered during the registration process. The electronic
device address may be obtained regardless of whether the electronic
device 160 completes pairing t o the terminal 300 and/or whether the
electronic device 160 is subsequently paired t o a different device than
the terminal 3 10. The ATS 1 10 may retain the electronic device
address along with a n association t o the registrant's personal
information.
According t o other example embodiments, the kiosk 300 may
automatically sniff a n electronic device address of a n electronic device
160 from a n existing connection. For example, a registrant with a n
electronic device 160 paired t o another electronic device (e.g., a
Bluetooth headset) may enter personal information a s described
above, and the existing communication link between the paired
devices may b e automatically sniffed.
As one example, the electronic device 160 may b e a mobile
phone connected t o a headset. The terminal 3 10, upon entry of the
personal information, may sniff a n existing connection and/or place a
telephone call t o the mobile phone in order for communication t o
occur between the phone and headset. Once communication is
established, a n associated electronic device address may b e sniffed.
Signal level and received signal strength indication (RSSI) of the
connection may b e measured by the terminal 3 10 t o establish that the
sniffed electronic device address corresponds t o a particular registrant
and not t o a nearby user of a different electronic device.
A registration kiosk 300 may provide services and/or sell
merchandise t o a user. For example, a registration kiosk 300 may
provide check-in services a t a n airport, provide general information,
and/or provide banking services. A registration kiosk 300 may b e a
dedicated registration kiosk 300 that does not provide a service
and/or sell merchandise t o a user. For example, incentives (e.g.,
coupons, rebates, and/or discounts) may b e provided t o a user
volunteering t o register a n electronic device 160 a t a terminal 3 10.
Although generation of electronic device address lists are
described with respect t o registration and enrollment using a kiosk,
example embodiments are not s o limited. Lists may b e generated
using a variety of sources and may include a priori information. For
example, area tracking may be used by employers t o track electronic
devices associated with employees. Lists of electronic addresses may
be compiled based on employee work schedules. Other examples may
include tracking cargo and/or electronic devices of customers. Lists
of electronic addresses may be compiled from a priori sources such a s
cargo manifests where cargo includes one or more electronic devices
and/or passenger lists maintained by common carriers (e.g., airlines).
FIG. 4 is a flow diagram illustrating methods of tracking
electronic devices using a sensor 150 of FIG. 1 according t o a single
list example embodiment. Referring t o FIG. 4 , a sensor 150 may
sequentially poll for a plurality of electronic devices corresponding t o
electronic device addresses in order t o determine if any of the
electronic devices are within range of the sensor 150. Hereinafter, the
electronic device address of the electronic device currently being polled
for is termed the 'active' electronic device address.
I n step S400, a sensor 150 may poll for a n electronic device by
broadcasting the active electronic device address (e.g., a BT-MAC-ID).
At step S4 10, the sensor 150 may wait for a reply for u p t o a time
period T (e.g., 5 seconds) or until a reply is received from the
corresponding electronic device. If a reply is received a t step S4 10,
the sensor 150 may send the active electronic device address t o a n
ATS 110 a t step S430 and, a t step S440, the sensor 150 may select a
different electronic device address a s the active electronic device
address. At step S400, the sensor 150 may poll for the active
electronic device address. If n o reply is received within T seconds a t
step S4 10, the sensor 150 may select a different electronic device
address a s the active electronic device address a t step S440. At step
S400, the sensor 150 may poll for the new active electronic device
address.
FIGS. 5 and 6 are flow diagrams illustrating methods of tracking
electronic devices using a sensor 150 of FIG. 1 according t o a dual list
example embodiment.
According t o a dual list example embodiment, each sensor 150
may store two lists of electronic device addresses. A sensor 150 may
poll for the electronic devices corresponding t o each list a t different
frequencies. For example, a first list may b e a 'slow-list' and a second
list may b e a 'fast-list.' Electronic devices corresponding t o a slow list
may b e polled for a t a lower frequency than and electronic device
corresponding t o the fast-list.
Electronic device addresses of electronic devices may b e
assigned t o a slow list or a fast list (or both) based on one or more
factors. For example, if a n electronic device is known t o b e within
range of a sensor 150, the electronic device may b e added t o the fastlist of the sensor 150 in order t o increase the reliability of location
based data with respect t o the in-range electronic device. As another
example, if a user of a n area tracking system 100 desires t o obtain
location based data of a particular electronic device with a higher
priority than other electronic devices, sensors 150 may b e instructed
t o move a n electronic device address t o the fast list. For example, in
order t o locate a missing child in possession of a n electronic device
during a n amber alert in a shopping mall, every sensor 150 may b e
instructed by a n ATS 1 10 t o add the electronic address of the child's
electronic device t o their fast lists. One having ordinary skill in the art
will understand that many configurations are possible in light of the
present disclosure. For example, a n ATS 1 10 may instruct sensors
150 t o disregard the slow and fast lists, and constantly poll for a
single electronic device, or for several multiple electronic devices.
Referring t o FIG. 5 , a sensor 150 may poll for a n electronic
device by broadcasting a n active electronic device address (e.g., a BTMAC-ID) from a first list (e.g., slow-list) a s shown in step S500. The
sensor 150 may wait for a reply for u p t o a time period T l (e.g., 5
seconds) or until a reply is received from the corresponding electronic
device.
If a reply is received a t step S5 10, the sensor 150 may send the
active electronic device address t o a n ATS 110 and move the active
electronic device address from the first list t o a second list a t step
S560. For example, because a n electronic device corresponding t o the
active electronic device address is determined t o be inside the range of
the sensor 150, the active electronic device address may be moved t o
the second list (e.g., fast-list). The sensor may send other data in
addition t o the electronic device address t o the ATS 110. For example,
the sensor may send a n identification (ID) of the sensor 150 along
with the active electronic device address t o the ATS 110.
At step S530, the sensor 150 may determine if a time period T2
has elapsed. If the time period T2 has not elapsed the sensor 150
may select a new electronic device address from the first list a s the
active electronic device address a t step S550. For example, the sensor
150 may switch the active electronic device address t o a next
electronic device address on the first list. At step S500, the sensor
150 may poll for the active electronic device address.
If the time period T2 is determined t o have elapsed a t step S530,
the sensor 150 may select a n electronic device address from the
second list a s the active electronic device address a t step S540. For
example, the sensor 150 may switch the active electronic device
address t o a next electronic device address on the second list and
begin cycling through the second list (as described below with respect
t o FIG. 6).
If a reply is not received a t step S5 10 within T l seconds, the
sensor 150 may determine if the time period T2 has elapsed. If the
time period T2 has not elapsed the sensor 150 may select a different
electronic device address from the first list a s the active electronic
device address a t step S550. For example, the sensor 150 may switch
the active electronic device address t o a next electronic device address
on the first list. At step S600, the sensor 150 may poll for the active
electronic device address.
If the time period T2 is determined t o have elapsed by the
sensor 150 a t step S530, the sensor 150 may select a n electronic
device address from the second list a s the active electronic device
address a t step S540. For example, the sensor 150 may switch the
active electronic device address t o a next electronic device address on
the second list and begin cycling through the second list (as described
below with respect t o FIG. 6).
Referring t o FIG. 6 , a sensor 150 may poll for a n electronic
device by broadcasting a n active electronic device address (e.g., a BTMAC-ID) from a second list (e.g., fast-list) a s shown in step S600. The
sensor 150 may wait for a reply t o the poll for u p t o a time period T3
(e.g., 5 seconds) or until a reply is received from the corresponding
electronic device. If a reply is received a t step S6 10, the sensor 150
may determine if the time period T4 has elapsed a t step S660. If the
time period T4 has not elapsed the sensor 150 may select a different
electronic device address from the second list a s the active electronic
device address a t step S670. For example, the sensor 150 may switch
the active electronic device address t o a next electronic device address
on the second list. At step S600, the sensor 150 may poll for the
active electronic device address.
If the time period T4 is determined t o have elapsed by the
sensor 150 a t step S660, the sensor 150 may select a n electronic
device address from the first list a s the active electronic device
address a t step S650. For example, the sensor 150 may switch the
active electronic device address t o a next electronic device address on
the first list and begin cycling through the first list (as described above
with respect t o FIG. 5).
If a reply is not received by the sensor 150 within the time
period T3 a t step S6 10, a t step S630, the sensor 150 may send the
active electronic device address t o a n ATS 110 and move the active
electronic device address from the second list t o the first list. For
example, because a n electronic device corresponding t o the active
electronic device address is determined t o be outside the range of the
sensor 150, the active electronic device address may be moved t o the
first list (e.g., slow-list). The sensor may send other data in addition
t o the electronic device address t o the ATS 110. For example, the
sensor may send an identification (ID) of the sensor 150 that detects
the electronic device t o the ATS 110.
At step S640, the sensor 150 may determine if the time period
T4 has elapsed. If the time period T4 has not elapsed the sensor 150
may select a different electronic device address from the second list a s
the active electronic device address a t step S670. For example, the
sensor 150 may switch the active electronic device address t o a next
electronic device address on the second list. At step S600, the sensor
150 may poll for the active electronic device address.
If the time period T4 is determined t o have elapsed by the
sensor 150 a t step S640, the sensor 150 may select a n electronic
device address from the first list a s the active electronic device
address a t step S650. For example, the sensor 150 may switch the
active electronic device address t o a next electronic device address on
the first list and begin cycling through the first list (as described above
with respect t o FIG. 5).
Example embodiments with respect t o FIGS. 5 and 6 describe
the use of two lists. However, any number of lists of electronic device
addresses are contemplated by example embodiments. For example,
additional lists may be used t o provide cycling of lists a t more than
two frequencies. Further, different lists may be used a t different times
of day (e.g., day shift, night shift) or different days (staggered shifts).
Example embodiments are described with respect t o two lists in FIGS.
5 and 6 for ease of explanation and not t o limit the inventive concepts
disclosed herein. Similarly, the exact determinations and
consequences of those determinations a s described with respect t o
FIGS. 5 and 6 are not limiting of the scope of example embodiments
but only illustrative of the inventive concepts.
FIG. 7 is a flow diagram illustrating methods of administering
the tracking of electronic devices a t the ATS 110 of FIG. 1 according t o
a n example embodiment. Referring t o FIG. 7 , a n ATS 110 may receive
a message from a sensor 150 a t step S700. For example, the ATS 110
may receive a n electronic device address (e.g., BT-MAC-ID) from the
sensor 150. According t o a n example embodiment the ATS 110 may
receive a n electronic device address and the ID of the sensor 150
sending the electronic device address.
At step S7 10, the ATS 110 may determine whether or not the
electronic device 160 corresponding t o the received electronic device
address is in range or out of range of the sending sensor 150 based on
a current state of one or more lists maintained a t the ATS 110 for the
sending sensor 150. According t o other example embodiments, the
message received by the ATS 110 may indicate whether or not the
electronic device 160 corresponding t o the received electronic device
address is in range or out of range of the sending sensor 150 and a
determination may not be necessary.
If the electronic device 160 corresponding t o the received
electronic address is detected by the sending sensor 150, a t step S740
the ATS 110 may remove the received electronic address from first and
second lists of sensors 150 other than the sending sensor 150 and
send a n update t o one or more LBS servers 120. The ATS 110 may
remove the received electronic address from first and second lists of
the sensors 150 maintained a t the ATS 110 and/or send instructions
t o the sensors 150 t o remove the received electronic address from first
and second lists maintained a t the sensors 150.
If the electronic device 160 is not detected by the sending sensor
150, a t step S720 the ATS 110 may determine if any other sensor 150
of the area tracking system 100 detects the electronic device 160. For
example, receipt of the electronic device address from a sensor 150
may indicate that the corresponding electronic device recently left a
coverage area of the sending sensor 150. The ATS 110 may then
determine whether the electronic device 160 has moved into range of
any other sensor 150. If the ATS 110 determines that the electronic
device 160 is detected by a different sensor 150 from the sending
sensor 150 a t step S720, a t step S740, the ATS 110 may remove the
received electronic address from first and second lists of sensors 150
other than the detecting sensor 150 and send a n update t o one or
more LBS servers 120.
If the ATS 110 determines that the electronic device 160 is not
detected by a different sensor 150 from the sending sensor 150 a t step
S720, the ATS 110 may add the received electronic address t o first
lists of sensors 150 other than the sending sensor 150. Although not
shown, the ATS 110 may send a n update t o one or more LBS servers
120. According t o a n example embodiment, the received electronic
device address may be added a s a next device t o be polled for on first
lists of the sensors 150 other than the sending sensor 150 s o that
each sensor next attempts t o detect the electronic device 160. The
ATS 110 may add the received electronic address t o first lists of the
sensors 150 maintained a t the ATS 110 and/ or send instructions t o
the sensors 150 t o add the received electronic address t o first lists
maintained a t the sensors 150.
Although example embodiments described with respect t o FIG. 7
provide for a specific set of responses including adding or removing
electronic device addresses from specific lists, example embodiments
are not s o limited. Responses t o information that a n electronic device
has come into range or gone out of range of a sensor may be tailored
t o the particular configuration of a n area tracking system 100 and the
goals of a user. For example, upon determining that a n electronic
device 160 has gone out of range of a detecting sensor 150, a n ATS
110 may add a n electronic device address corresponding t o the
electronic device t o second lists (e.g., fast-lists) of sensors 150 with
adjacent or overlapping scanner coverage t o the detecting sensor 150
and add the electronic device address t o first lists (e.g., slow-lists) of
sensors 150 that are farther away. Various implementations within
the scope of example embodiments will be understood by one of
ordinary skill in the art in light of the present disclosure.
While example embodiments have been particularly shown and
described, it will be understood by one of ordinary skill in the art that
variations in form and detail may be made therein without departing
from the spirit and scope of the claims.
WE CLAIM:
1. An area tracking system, comprising:
a server ( 1 10) connected t o a network (130); and
a plurality of sensors (150) connected t o the server ( 1 10), the
sensors (160) configured t o poll for a t least one electronic device (160)
using a n identification packet including a n address of the electronic
device.
2 . The area tracking system of claim 1 , wherein
the sensors (150) are configured t o maintain first and second
lists including addresses of a plurality of electronic devices (160), and
t o poll for electronic devices (160) corresponding t o addresses of the
first list a t a greater frequency than for electronic devices
corresponding t o addresses of the second list,
the sensors (150) are configured t o detect any of the plurality
of electronic devices (160) in range of the sensors (150) that respond
t o the polling, and t o communicate the detection, or a change in the
detection, t o the server ( 1 10), and
the server ( 1 10) is configured t o update the first and second
lists by instructing the sensors (150) t o add or remove electronic
addresses from the first and second lists based on the communication
of detection, or the change of the detection, of any of the plurality of
electronic devices (160).
3 . The area tracking system of claim 1 , further comprising:
a plurality of wireless access points (140) connected t o the
network (130); and
a Location-Based Services (LBS) server (120) connected t o
the server ( 1 10) though the network (130),
wherein a t least one of the sensors (150) is a wireless sensor
connected t o the server ( 1 10) through a t least one of the wireless
access points (140), and
the wireless sensor (150) is configured in a n access-pointclient mode t o establish a client into the wireless access point (140).
4 . The area tracking system of claim 1 , wherein
the sensors (150) poll for the a t least one electronic device
(160) using a short range transmitter,
the short range transmitter broadcasts a signal detectable by
a n electronic device (160) in a range from about 1 t o about 100
meters, and
the address is a Bluetooth Media Access Control (MAC)
address.
5 . A method of tracking a plurality of electronic devices
using a plurality of sensors connected t o a server, the method
comprising:
maintaining, by a first sensor (150), first and second lists
including a plurality of electronic device addresses corresponding t o a
plurality of electronic devices (160);
sequentially polling (S500, S600), by the first sensor (150),
for the plurality of electronic devices (160) by transmitting
identification packets including the electronic device addresses;
determining (S5 10, S610) whether one of the plurality of
electronic devices (160) is in range of the first sensor (150) based on
whether or not a reply t o the sequential poll corresponding t o the one
of the plurality of electronic devices (160) is received by the first
sensor within a first period of time; and
transmitting, t o a server ( 1 10, S560, S630)), data relating t o
a position of the one of the electronic devices (160).
6 . The method of claim 5 , wherein the sequential polling
by the first sensor (150) includes sequentially polling for electronic
devices (160) corresponding t o the first list until a second period of
time elapses (S530), and then sequentially polling for electronic
devices (160) corresponding t o the second list until a third period of
time elapses (S660).
7 . The method of claim 6 , wherein, during the sequential
polling of the electronic devices (160, S500) corresponding t o the first
list, upon determining that one of the electronic devices (160)
corresponding t o the first list is in range (S5 10, S5 10), a n electronic
device address of the in range electronic device (160) is moved t o the
second list (S560), and upon determining that one of the electronic
devices (160) corresponding t o the first list is out of range (S5 10), a
next one of the electronic devices (160) corresponding t o the first list is
polled (S550), and
the transmitting of the data relating t o the position of the one
of the electronic devices (160, S630) includes transmitting sensor
identification information of the first sensor (150) and a n electronic
device address (S560).
8 . The method of claim 6 , wherein, during the sequential
polling of the electronic devices (160, S600) corresponding t o the
second list, upon determining that one of the electronic devices (160)
corresponding t o the second list is in range (S6 10), a next one of the
electronic devices (160) corresponding t o the second list is polled
(S670), and upon determining that one of the electronic devices (160)
of the second list is out of range (S6 10), a n electronic device address
of the out of range electronic device (160) is one of moved t o the first
list and removed from the second list (S630), and
the transmitting of the data relating t o the position of the one
of the electronic devices (160, S630) includes transmitting sensor
identification information of the first sensor (150) and a n electronic
device address.
9 . The method of claim 5 , further comprising:
generating the first and second lists by a t least one of
enrollment, registration, and use of a priori information,
wherein enrollment includes extracting a t least one electronic
device address from a t least one of a form, a n electronic mail (email)
and a web interface entry, and
registration includes detecting a t least one electronic address
a t a kiosk (300).
10. The method of claim 5 , further comprising:
publishing presence information t o a Location-Based
Services (LBS) server (120, S740)) based on the data relating t o the
position of the one of the electronic devices (160).

Documents

Application Documents

# Name Date
1 6184-DELNP-2013-RELEVANT DOCUMENTS [03-08-2023(online)].pdf 2023-08-03
1 6184-DELNP-2013.pdf 2013-07-18
2 6184-DELNP-2013-Form-13-(31-07-2013).pdf 2013-07-31
2 6184-DELNP-2013-IntimationOfGrant24-03-2022.pdf 2022-03-24
3 6184-DELNP-2013-PatentCertificate24-03-2022.pdf 2022-03-24
3 6184-delnp-2013-Correspondence Others-(31-07-2013).pdf 2013-07-31
4 6184-DELNP-2013-Correspondence-070819.pdf 2019-08-10
4 6184-delnp-2013-Claims-(31-07-2013).pdf 2013-07-31
5 6184-DELNP-2013-Power of Attorney-070819.pdf 2019-08-10
5 6184-delnp-2013-Form-3-(20-09-2013).pdf 2013-09-20
6 6184-delnp-2013-Correspondence Others-(20-09-2013).pdf 2013-09-20
6 6184-DELNP-2013-CLAIMS [29-07-2019(online)].pdf 2019-07-29
7 6184-delnp-2013-Correspondence-Others-(17-10-2013).pdf 2013-10-17
7 6184-DELNP-2013-COMPLETE SPECIFICATION [29-07-2019(online)].pdf 2019-07-29
8 6184-DELNP-2013-FER_SER_REPLY [29-07-2019(online)].pdf 2019-07-29
8 6184-delnp-2013-Assignment-(17-10-2013).pdf 2013-10-17
9 6184-delnp-2013-GPA.pdf 2014-02-07
9 6184-DELNP-2013-OTHERS [29-07-2019(online)].pdf 2019-07-29
10 6184-DELNP-2013-FER.pdf 2019-01-28
10 6184-delnp-2013-Form-5.pdf 2014-02-07
11 6184-DELNP-2013-FORM 3 [14-06-2018(online)].pdf 2018-06-14
11 6184-delnp-2013-Form-3.pdf 2014-02-07
12 6184-delnp-2013-Form-2.pdf 2014-02-07
12 Form 3 [01-06-2016(online)].pdf 2016-06-01
13 6184-delnp-2013-Correspondence Others-(23-10-2015).pdf 2015-10-23
13 6184-delnp-2013-Form-18.pdf 2014-02-07
14 6184-delnp-2013-Form-1.pdf 2014-02-07
14 6184-delnp-2013-Form-3-(23-10-2015).pdf 2015-10-23
15 6184-delnp-2013-Correspondence Others-(17-03-2015).pdf 2015-03-17
15 6184-delnp-2013-Correspondence-others.pdf 2014-02-07
16 6184-delnp-2013-Claims.pdf 2014-02-07
16 6184-delnp-2013-Form-3-(17-03-2015).pdf 2015-03-17
17 6184-delnp-2013-Form-3-(25-02-2014).pdf 2014-02-25
17 6184-DELNP-2013-Correspondence-131114.pdf 2014-12-04
18 6184-delnp-2013-Correspondence-Others-(25-02-2014).pdf 2014-02-25
18 6184-DELNP-2013-Form 3-131114.pdf 2014-12-04
19 6184-DELNP-2013-Correspondence-Others-(22-07-2014).pdf 2014-07-22
19 6184-DELNP-2013-Form-3-(22-07-2014).pdf 2014-07-22
20 6184-DELNP-2013-Correspondence-Others-(22-07-2014).pdf 2014-07-22
20 6184-DELNP-2013-Form-3-(22-07-2014).pdf 2014-07-22
21 6184-delnp-2013-Correspondence-Others-(25-02-2014).pdf 2014-02-25
21 6184-DELNP-2013-Form 3-131114.pdf 2014-12-04
22 6184-DELNP-2013-Correspondence-131114.pdf 2014-12-04
22 6184-delnp-2013-Form-3-(25-02-2014).pdf 2014-02-25
23 6184-delnp-2013-Claims.pdf 2014-02-07
23 6184-delnp-2013-Form-3-(17-03-2015).pdf 2015-03-17
24 6184-delnp-2013-Correspondence-others.pdf 2014-02-07
24 6184-delnp-2013-Correspondence Others-(17-03-2015).pdf 2015-03-17
25 6184-delnp-2013-Form-1.pdf 2014-02-07
25 6184-delnp-2013-Form-3-(23-10-2015).pdf 2015-10-23
26 6184-delnp-2013-Correspondence Others-(23-10-2015).pdf 2015-10-23
26 6184-delnp-2013-Form-18.pdf 2014-02-07
27 6184-delnp-2013-Form-2.pdf 2014-02-07
27 Form 3 [01-06-2016(online)].pdf 2016-06-01
28 6184-DELNP-2013-FORM 3 [14-06-2018(online)].pdf 2018-06-14
28 6184-delnp-2013-Form-3.pdf 2014-02-07
29 6184-DELNP-2013-FER.pdf 2019-01-28
29 6184-delnp-2013-Form-5.pdf 2014-02-07
30 6184-delnp-2013-GPA.pdf 2014-02-07
30 6184-DELNP-2013-OTHERS [29-07-2019(online)].pdf 2019-07-29
31 6184-DELNP-2013-FER_SER_REPLY [29-07-2019(online)].pdf 2019-07-29
31 6184-delnp-2013-Assignment-(17-10-2013).pdf 2013-10-17
32 6184-delnp-2013-Correspondence-Others-(17-10-2013).pdf 2013-10-17
32 6184-DELNP-2013-COMPLETE SPECIFICATION [29-07-2019(online)].pdf 2019-07-29
33 6184-delnp-2013-Correspondence Others-(20-09-2013).pdf 2013-09-20
33 6184-DELNP-2013-CLAIMS [29-07-2019(online)].pdf 2019-07-29
34 6184-DELNP-2013-Power of Attorney-070819.pdf 2019-08-10
34 6184-delnp-2013-Form-3-(20-09-2013).pdf 2013-09-20
35 6184-DELNP-2013-Correspondence-070819.pdf 2019-08-10
35 6184-delnp-2013-Claims-(31-07-2013).pdf 2013-07-31
36 6184-DELNP-2013-PatentCertificate24-03-2022.pdf 2022-03-24
36 6184-delnp-2013-Correspondence Others-(31-07-2013).pdf 2013-07-31
37 6184-DELNP-2013-Form-13-(31-07-2013).pdf 2013-07-31
37 6184-DELNP-2013-IntimationOfGrant24-03-2022.pdf 2022-03-24
38 6184-DELNP-2013-RELEVANT DOCUMENTS [03-08-2023(online)].pdf 2023-08-03
38 6184-DELNP-2013.pdf 2013-07-18

Search Strategy

1 SEARCHSTRATEGY_28-01-2019.pdf

ERegister / Renewals

3rd: 06 Apr 2022

From 09/01/2014 - To 09/01/2015

4th: 06 Apr 2022

From 09/01/2015 - To 09/01/2016

5th: 06 Apr 2022

From 09/01/2016 - To 09/01/2017

6th: 06 Apr 2022

From 09/01/2017 - To 09/01/2018

7th: 06 Apr 2022

From 09/01/2018 - To 09/01/2019

8th: 06 Apr 2022

From 09/01/2019 - To 09/01/2020

9th: 06 Apr 2022

From 09/01/2020 - To 09/01/2021

10th: 06 Apr 2022

From 09/01/2021 - To 09/01/2022

11th: 06 Apr 2022

From 09/01/2022 - To 09/01/2023

12th: 06 Dec 2022

From 09/01/2023 - To 09/01/2024

13th: 08 Dec 2023

From 09/01/2024 - To 09/01/2025

14th: 05 Dec 2024

From 09/01/2025 - To 09/01/2026