111111
`
`1111111111111111111111111111111111111111111111111111111111111
`US007327258B2
`
`c12) United States Patent
`Fast et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,327,258 B2
`Feb.5,2008
`
`(54) SYSTEM FOR, AND METHOD OF,
`MONITORING THE MOVEMENTS OF
`MOBILE ITEMS
`
`(75)
`
`Inventors: Raymond D. Fast, Surrey (CA);
`Robert R. Goehring, Vancouver (CA);
`Kai Loon Ng, Vancouver (CA)
`
`5,519,403 A *
`6,661,372 B1
`6,720,888 B2 *
`6,958,677 B1 *
`7,139,820 B1 *
`7,152,020 B2 *
`7,176,797 B2 *
`
`. ............ 342/352
`
`5/1996 Bickley et al.
`12/2003 Girerd et a!.
`4/2004 Eagleson eta!. ........ 340/572.1
`10/2005 Carter ....................... 340/10.1
`11/2006 O'Toole eta!. ............. 701/213
`12/2006 Michiwaki eta!. .... 340/539.11
`2/2007 Zai eta!. ................. 340/572.1
`
`(73) Assignee: Guardian Mobile Monitoring
`Systems, Vancouver, B.C. (CA)
`
`FOREIGN PATENT DOCUMENTS
`
`wo
`
`WO 02/23922 A2
`
`3/2002
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 384 days.
`
`(21) Appl. No.: 111048,555
`
`(22) Filed:
`
`Jan. 31, 2005
`
`(65)
`
`Prior Publication Data
`
`US 2006/0181411 Al
`
`Aug. 17, 2006
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/542,208, filed on Feb.
`4, 2004.
`
`(51)
`
`Int. Cl.
`G08B 13114
`(2006.01)
`(52) U.S. Cl. .................................... 340/572.1; 701/213
`(58) Field of Classification Search ............. 340/572.1,
`340/825.36, 825.49, 825.72, 539.11; 7011213,
`701/214; 342/357.01, 357.02
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`5,317,309 A * 5/1994 Vercellotti eta!. ......... 340/10.5
`
`* cited by examiner
`Primary Examiner-John Tweel, Jr.
`(74) Attorney, Agent, or Firm-Fulwider Patton LLP
`
`(57)
`
`ABSTRACT
`
`A system monitors parameters (e.g., speed, position, thresh(cid:173)
`old boundaries) of mobile items attached to beacons and
`produces signals indicating these parameters. The system
`also monitors non-mobile parameters (e.g., battery life, door
`locks, windows) in the items. Different technologies (e.g.,
`wireless) are provided for communicating between the bea(cid:173)
`cons and a beacon controller interface. Different technolo(cid:173)
`gies are provided for locating and indicating item positions.
`The beacons and the interface provide for new beacons to be
`added to the system with different characteristics than the
`existing beacons for monitoring the operation of new bea(cid:173)
`cons without affecting the operation of existing beacons. The
`system includes resellers, retailers, users and subscribers in
`a flexible relationship to enhance the ease in the system
`operation. Beacons can perform more than one function (e.g.
`tracking, threshold monitoring) simultaneously. Scenarios
`for the beacons can be created and monitored. Recovery
`personnel can intervene to resolve crises.
`
`122 Claims, 30 Drawing Sheets
`
`TELETRAC Ex. 1003
`
`1
`
`

`
`U.S. Patent
`U.S. Patent
`
`Feb. 5,2008
`Feb.5,2008
`
`Sheet 1 of 30
`Sheet 1 of 30
`
`US 7,327,258 B2
`US 7,327,258 B2
`
`FIG. 1
`
`2
`
`

`
`31""'
`
`_........- 'v -
`
`'
`
`\_[Mapping J
`
`5
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`( Network r
`~ _._.r
`'-r
`I Secure GMMS Servers in Data Center
`
`Webservices
`Back up secure dialup connection
`14-
`30- 12
`
`26
`
`Application Server
`
`6
`
`J
`
`CTI
`
`·27
`
`~ ~
`Backup
`Database
`Server
`
`User's
`Handheld Devices
`lU
`-~
`Subscriber' PCs
`~22
`
`·--==-.. -
`
`Subscriber' PCs
`
`24
`Hot Stand by
`2~6~Balanrer
`
`System Health
`Monitor
`
`WebServer
`Farm
`
`Application Server
`
`Application Server
`
`Map/Aerial Image Server
`
`Application
`Server Cluster
`
`FIG. 2
`
`'"rj
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`N
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`3
`
`

`
`GMMS Administration Module (GAM)
`
`I User Manager I Retail Service
`I Partner/Dealer
`
`Plan Manager
`Wholesale Service
`Plan Manager
`
`Manager
`
`Beacon Type
`Manager
`
`1-
`Beacon Inventory I
`
`Manager
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`Incident Manager
`
`Partner/Dealer Portal
`I Account Manager
`I Beacon Manager I Wholesale Service
`I Recovery Interface
`
`Plan Manager
`Service Plan
`Manager
`
`Subscriber Portal
`ResidenuaiSubscriber
`Dependent Manager I Asset Manager
`I Beacon Manager I Scenario Manager
`
`Account Activity
`Manager
`
`Location Tracking
`Manager
`
`Commercial Subscriber
`
`I Personnel
`I Beacon Manager
`Account Activity
`Manager
`
`Asset Manager
`
`Scenario Manager
`
`Profile Manager
`
`User
`Administration
`c.:ustomer
`Relationship Manaqer
`
`I Activity Logger I
`...
`I Guardian Manager
`r
`
`Profile Manager
`
`/
`
`I Supervisor Manager
`I Location Tracking
`
`Organization User
`Manager
`
`Manager
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`rFJ =(cid:173)
`.....
`
`('D
`('D
`
`(.H
`
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w
`N
`-....l
`'N
`u.
`
`00 = N
`
`4
`
`

`
`Alarm Queue Integration
`Integration Networks
`
`[Telephony (Wireline)) [Telephony (Wireless))
`)
`[
`
`l I
`
`Other
`
`TCP/IP
`
`Automation Systems
`) (
`( MAS
`(
`1 [
`IBS
`( Other ... )
`
`Bold
`
`Dice
`
`)
`)
`
`'6
`
`7a
`
`68
`
`b/D
`l
`-
`) Beacon Controller Interface
`I
`~
`~) [BeaaJn Manager 1) [Wireless Network 1)
`(Beacon Manager 2) [wireless Network 2)
`;
`(Beacon Manager N) (Wireless Network N)
`ct
`-
`
`Mapping Interface
`( Street Map Data )
`
`~ 11.1
`~ .!::;
`)(-.I ~
`~t:::
`I.Ci
`(b:g
`I:])
`·5:
`::::,u
`ii5~ ~
`lg ~
`~ ....____
`
`(Aerial Image Data )
`)
`(
`
`Other. ..
`
`FIG. 3-2
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`rFJ =(cid:173)
`.....
`
`('D
`('D
`
`.j;o.
`
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`5
`
`

`
`GMMS
`Web Applications
`
`Beacon Controller
`Interface
`
`I
`
`Subscriber
`Portal
`
`Monitoring
`Station
`Portal
`
`Recovery
`Interface
`
`Q:j
`t:::
`~
`6
`::....
`~
`Cl..: -g
`Ill
`~
`i:i:
`
`Feature
`Request
`
`¢:::J
`
`Response
`
`Subiber ~
`~ ;:::>
`~ ~ Recovery
`61
`
`Operator
`
`ctton
`
`Personnel
`
`Automated
`Event
`
`Wireless
`Network 1
`(DC:~~~~~~ (CDMA)
`
`~ Beacon A
`
`D
`
`Wireless ~~
`Network 2
`QseaconB
`(GSM)
`
`(Beacon~r Wirete~ ~~~Bearonc
`Networ, n
`( ... )
`
`Mnr
`
`.
`
`ft
`
`ff
`
`FIG. 4
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`Ul
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`6
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 6 of 30
`
`US 7,327,258 B2
`
`92
`
`Function
`request from
`application
`
`93
`
`94
`
`95
`
`Beacon Controller
`passes request to Plug
`and Play Channel
`(Beacon ID=xyz)
`
`PPC looks up Beacon ID
`in database for Model
`type.
`
`Based on Beacon ID, PPC
`dispatches function
`request to appropriate
`Beacon Manager
`
`96
`
`Send
`request to
`BM
`
`/90
`
`97
`
`Request data
`returned
`from BM
`
`98
`
`PPC dispatches
`data to originating
`client application
`
`FIG. 5
`
`7
`
`

`
`102
`
`Beacon Start
`
`103
`
`104
`
`111
`
`Beacon Manager reads current
`Beacon's State of Operation.
`
`Beacon session
`data retrieved from
`database
`
`Remove record for Session
`request of current feature
`
`100
`
`7
`
`Enable real-time
`inspection on all incoming
`beacon data.
`
`108
`
`109
`
`Beacon Manager formats command and
`sends command via appropriate
`wireless network interface
`
`Beacon Manager waits for returned data
`from Beacon
`
`110
`
`116
`
`Send Command to
`activate Buffering
`in Beacon
`
`Retrieve Beacon
`Session
`
`119
`
`Send Command to
`activate feature in
`Beacon
`
`FIG. 6
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`"'f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`-....l
`0 ......
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`8
`
`

`
`122
`
`Request sent from
`PPC for Beacon
`
`Set Current Tracking Expiry =
`Current Time X seconds
`
`Beacon Manager formats command and
`sends command to Beacon to track via
`appropriate wireless network interface
`
`Records Current Beacon State. Set
`Current Beacon State to Tracking.
`
`133
`
`Send data from
`beacon to the
`requesting
`application via
`the BCI
`
`Request sent from
`PPC to stop Beacon
`Tracking Session
`
`120
`
`j
`
`142
`
`Updates Current Tracking
`Expiry = Current Time + X
`Seconds
`
`Records Session Tracking
`ID and Session Tracking
`Expiry
`
`Set Timer to expire in Y
`seconds. Y= Current Time
`+ Max (Session Expiry)
`
`Send Command to activate Threshold
`Monitoring in Beacon via appropriate
`wireless network interface
`
`166.-----------------.
`Send Command to activate Buffering
`in Beacon via appropriate wireless
`network interface
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`QO
`
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`9
`
`

`
`182
`
`Beacon Threshold
`Monitoring
`Request from PPC
`
`FIG. 8
`
`Stop Beacon
`Threshold
`
`180 ?
`
`214
`
`Remove record for Session
`request of Threshold
`Monitoring.
`
`194
`Record Session request for
`Threshold Monitoring.
`
`No
`
`Set current Beacon State to
`Threshold Monitoring.
`
`Send command to Beacon to
`activate Threshold Monitoring.
`
`190
`
`196
`
`Set State of Beacon to
`Buffering and send
`command to Buffer
`the Beacon
`
`Disable real-time
`Threshold inspection of
`all incoming
`Tracking Data.
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`"'f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`\0
`0 ......
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`10
`
`

`
`Zone
`Zone
`S~'!_ _______ _____ ~~-::\__!_one Request
`Stop
`i
`Tracking
`Tracking-Request----! __ -Tra&/iig--------- - l
`Starn- - - - - -- - - - - - - - -- - ---, Stop
`:
`
`_ J_2
`
`1
`
`1
`
`l.Zone requestinterrupted
`by Tracking request
`
`I) Zone Monitoring State=>
`
`II) Tracking state=>
`
`238.....J.~=======~
`yr-------J'r------------------------~'~-------,
`234~
`Beacon in Zone Monitoring
`Beacon in Zone Monitoring
`!
`Threshold state
`Threshold state
`
`1
`1
`
`\.
`
`236
`
`Beacon in Tracking State (real-time
`inspection of tracking data used to
`satisfy zone feature request)
`
`FJ G. 9
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`....
`0
`0 ....
`
`(.H
`0
`
`Tracking
`
`240
`
`(~'! _______ zooe--~~~~;Z?u!P~E--~-zooe--------~~~
`Startr _______________ f_---, Stop
`
`Tracking
`
`1
`
`2.Zone request interrupted
`by Zone request
`I) Tracking state=>
`
`1
`
`I
`
`I
`I
`
`Beacon Remains in Tracking State
`(real-time inspection of tracking data
`used to satisfy zone feature request)
`
`FIG. 10
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`11
`
`

`
`.
`3. Trackmg request interrupted
`by Zone Speed request
`
`1
`
`I
`
`I
`
`Tracking
`241\
`.
`start
`Tracking
`r - - - - - - - - - _____ l_ !!.B_Ekmg Request
`Stop
`Zone Request [0i2--ZOne- ""Speed---- -iiJl
`~~;~
`:
`r-------- - ___ }top Start ___ ["_
`I Speed Request
`1
`1
`---+
`
`I
`
`I
`
`1
`
`/)Tracking state=>
`
`I
`
`II) Speed state=>
`
`Beacon in Tracking State (real-time
`inspection of tracking data used to
`satisfy zone feature request)
`
`\.
`I
`y
`Beacon in Tracking State (real-time
`inspection of tracking data used to
`satisfy speed feature request)
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`244 5
`peed
`J
`1
`Stop
`..C-
`
`I
`1
`
`FIG. lOa
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`....
`....
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`12
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 12 of 30
`
`US 7,327,258 B2
`
`FIG. 11-1
`
`250
`
`~
`
`261
`
`Select a
`Scenario
`
`252
`
`Select an
`Item with
`an assigned
`Beacon
`
`256
`
`Vehicle 1,2,N
`Asset 1,2,N
`Dependant 1,2,N
`Personnel 1,2,N
`
`TRIGGERS:
`Panic Button
`Speed
`Zone
`Door Open
`Motion
`Alarm
`etc ...
`
`Use scheduler
`to define a
`Schedule
`during which
`scenario is
`active
`
`Name and
`save
`Schedules
`
`294
`
`Select a
`trigger
`mechanism
`
`278
`
`Select a
`t-------1 Notification ._..,r-<
`Scheme
`
`E
`
`13
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 13 of 30
`
`US 7,327,258 B2
`
`r-=-'-==-:-----7-t NOTIFICATION
`METHODS:
`Text
`Email
`SMS
`MMS
`IM
`Pager
`Voice
`Fax
`etc ...
`
`MESSAGES:
`System message 1
`System message 2
`System message n
`Subscriber message 1
`Subscriber message 2
`Subscriber message n
`
`and save
`Notification
`Scheme
`
`Define
`Notification
`Schemes
`
`292
`
`296
`
`Name and save
`Scenario
`
`Activate Schedule
`in Scheduling
`Engine
`
`Trigger Beacon
`command at
`scheduled time
`
`Outgoing
`settings to BCI
`
`FIG. 11-2
`
`14
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 14 of 30
`
`US 7,327,258 B2
`
`302
`
`Incoming
`Trigger from
`BCI for Beacon
`1
`
`300~
`
`304
`
`Incoming
`Trigger from
`BCI for Beacon
`2
`
`306
`
`Incoming
`Trigger from
`BCI for Beacon
`N
`
`308
`
`315
`
`.-------r-------.1 Listen for incoming .,__----1
`Trigger reports
`
`Send error
`message to
`system
`administrator
`
`314
`
`298
`
`Scheduling
`Engine
`
`Notification
`Scheme
`
`Send Notification
`,__~ messages
`
`326
`
`FIG. 12
`
`15
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 15 of 30
`
`US 7,327,258 B2
`
`352
`
`350
`
`""
`
`Set Presentation
`style based
`on access
`device type
`
`354
`
`Login with User ID
`and Password
`
`FIG. 13
`
`360
`
`Prevent Log in
`
`User Types:
`-Super Administrator
`-Manager
`-Administrator
`-Clerk
`-Assistant
`-etc ...
`
`362
`
`366
`
`Manage Partners
`Dealers
`
`369
`
`Manage Beacon
`Inventory
`
`Manage
`Manage Retail
`Wholesale
`Service Plans Services Plans
`
`Assign
`Subscriber
`
`Assign Beacons
`to Partners/
`Dealers
`
`374
`
`376
`
`Assign
`Wholesale
`Service Plans
`to Partners'/
`Dealers'
`Beacons
`
`382
`
`Set Feature
`Defaults for
`Beacon Type
`
`16
`
`

`
`402
`
`400
`
`403
`Set Presentation style based
`
`404
`
`j
`on access device type ~ and Password
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`408
`
`Yesl Determine level of
`authorized access 1 ..
`based on user type
`
`1
`
`USER TYPES:
`Administrator
`Operator
`Reseller
`Accounts Payable
`Accounts Receivable
`Sales
`Etc ...
`
`444
`
`410
`
`Manage
`system users
`
`Manage residential/
`commercial
`subscriber accounts
`
`Manage
`reports
`
`Manage beacons
`
`Manage
`customer
`relationships
`
`Manage incidents
`
`FIG. 14-1
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`......
`0\
`0 ......
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`17
`
`

`
`Add/update/
`delete system
`users
`
`Assign access
`levels to
`system users
`
`c
`
`434
`
`Add/update/ delete
`subscribers
`
`Access subscriber
`portal
`
`View Inventory 1 •I• 1 Manually initiate
`1
`incident
`
`413
`
`420
`
`432
`
`428
`
`446
`
`' 1
`
`Operator
`authenticates
`with keyword or
`override
`
`422
`
`433
`
`Assign beacon 1 .. 1 ... 1 Initialize beacon
`to subscriber
`
`View incident
`history
`
`430
`
`Assign/ modify
`service plan
`
`Test beacon
`
`FIG. 14-2
`
`438
`
`440
`
`445
`
`Request
`beacon
`function from
`BCI
`
`Go to incident
`handling
`
`Incident alert
`from BCI
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`....
`-....l
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`18
`
`

`
`453
`
`452
`
`Search for
`Subscriber's
`Beacon
`
`454
`
`Incident
`
`457
`Operator authenticates
`with Subscriber/
`Guardian/ Supervisor's
`keyword, or overrides
`
`automatically
`accepted by
`operator
`
`450
`
`t;
`
`490
`
`Interface Network:
`-Telephony (wireline)
`-Telephony (Wireless)
`-TCP/IP
`-Other
`
`494
`
`496
`
`498
`
`Determines
`alarm Queue
`Interface
`Network
`
`Configure Protocol
`based on Automation
`System type and
`Interface Network
`495
`Automation System:
`-MAS
`-Bold
`-IBS
`-Dice
`-Other
`
`499
`
`Automation
`System
`Interface
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`....
`0 .....
`(.H
`0
`
`QO
`
`Enable
`Recovery
`Interface
`
`Operator
`accepts incident 1 466
`
`FIG. 15-1
`
`8
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`19
`
`

`
`468
`
`Operator manages I
`
`incident
`
`.---------t
`
`480
`
`•I Operator ~ho?ses I
`
`to resolve mc1dent
`
`483
`
`•I incident resolution
`
`Operator chooses
`
`type
`
`470
`
`Incident
`handler
`requests
`tracking
`feature
`
`476
`
`472
`
`474
`
`482
`
`BCI returns
`data from
`beacon
`
`Manually
`request
`functions from
`BCI
`
`Request
`beacon tracking!
`START from
`from BCI
`
`Request beaconl
`tracking STOP
`from BCI
`
`Operators enters
`resolution
`comments
`
`484
`
`485
`
`FIG. 15-2
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`
`rFJ =-('D
`.....
`....
`\0
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`20
`
`

`
`Presentation
`style based
`on access
`device
`
`503
`
`504
`
`Login with User ID
`and Password
`
`505a
`
`506
`
`Authenticated
`access from
`Partner/Dealer
`Portal
`
`500 )
`
`FIG. 16-1
`
`Determine level of
`authorized access
`based on User Type
`
`User Types:
`-Subscriber
`-Guardian
`-Organization Manager
`-Supervisor
`-Operator
`-Dealer
`-etc ...
`
`Prevent Log in
`
`A
`
`8
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`"'f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`N
`0
`0 ......
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`21
`
`

`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`516
`
`Manage Profile
`
`Manage
`Beacons
`
`Manage
`Dependents/
`Personnel
`
`Manage
`Assets
`
`Manage
`Supervisors/
`Guardians
`
`Manage
`Scenarios
`
`Manage User
`Types
`
`View Account
`Activity
`
`Manage Manual
`Beacon Features
`(Locate/ Track, Door
`Unlock, etc ... )
`
`527
`
`Assign
`Guardians to
`Dependents/
`Assets
`
`532
`
`534
`
`476
`
`474
`
`BCI returns
`beacon
`function data
`
`Request
`Beacon
`function from
`BCI
`
`Request
`stop Beacon
`function
`from BCI
`
`520
`
`Go to Scenario
`Manager
`
`Add/Update/
`Delete
`system users
`
`Assign access
`levels to
`system users
`
`FIG. 16-2
`
`"'f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`......
`N ......
`0 ......
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`22
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 22 of 30
`
`US 7,327,258 B2
`
`System generates
`unique Incident ID
`and Recovery
`password
`
`556
`
`Recovery
`Interface
`Enabled
`
`Operator provides
`URL, login and
`password to
`Recovery User(s)
`
`Recovery User(s)
`logs in
`
`560
`
`550 J
`
`FIG. 17-1
`
`No
`
`No
`
`566
`
`Prevent log in
`
`Provides access to
`Recovery Interface
`
`574
`
`Send Recovery
`571
`>-'------r--~ User's location
`to Beacon
`Manager
`
`A
`
`8
`
`23
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 23 of 30
`
`US 7,327,258 B2
`
`A
`
`572
`
`576
`
`Set map
`display
`application to
`display User's
`location on
`same map
`
`Recovery User works
`with application
`
`.-..---.--------'
`
`Manager
`
`Session Manager
`returns incident
`Status
`
`586
`
`Warn user
`terminate
`session
`
`Manually log out of
`Recovery Interface
`
`~----------------------~
`
`FIG. 17-2
`
`24
`
`

`
`0 Distributor Portal-Recovery View Incident- Microsoft Internet Explorer
`
`Locating: $4
`
`GJ~~
`Incident ID: 76 Start: 12/05/2003 4:42PM PSTI
`
`'• .. ·-"'··-~-~
`r.:=~=;~~~~~~~~~mn==~~==~~==~~~~ilrooM
`I
`o:
`"•
`! Nil! IA I
`;;
`IN
`~
`..
`"
`r:::l+
`
`Asset Details:
`
`Type:
`Make:
`Model:
`
`Color:
`License:
`
`Year:
`VIN:
`
`Vehicle
`Audi
`
`Silver
`DSK303
`
`2000
`
`D
`D
`D
`D
`D
`D
`D
`D
`D
`
`D D
`rooM our
`MAP D
`m El
`
`CErfTER
`
`BEST
`
`Center
`last
`Locate
`611
`
`Clicking on map will (!)recenter Qview address Qzoom to recta11gle
`
`Displaylocates: @all
`
`Qlast3points Qlastpointonly
`
`FIG. 18
`
`Location Details:
`[6]
`12/05/2203 04:42 :40PM PST
`[5]
`12/05/2203 04:42:07PM PST
`[4]
`12/0S/2203 04:41:47PM PST
`[3]
`12/0S/2203 04:41:14PM PST
`[2]
`12/0S/2203 04:40:32PM PST
`
`1075 HomerSt, ,V6B
`1075 HomerSt, ,V6B
`1077 HomerSt, ,V6B
`1077 HomerSt, ,V6B
`1076 HomerSt, ,V6B
`
`149.27684
`149.27678
`149.27680
`149.27683
`149.27687
`
`l-123.12071
`l-123.12063
`l-123.1206.5
`1-123.12069
`1-123.12075
`
`0.5km/h
`0.4km/h
`0.6km/h
`O.Bkm/h
`0.2km/h
`
`I Om
`I Om
`I Om
`Om
`I Om
`
`/1,
`
`I LV r
`I c
`I ~v
`I LV
`
`jv
`
`Incident Operator: Winston Ng
`
`(c) Guardian Mobile Monitoring Systems
`
`0
`
`o=o
`
`@Internet
`
`e •
`
`7J)_
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`rFJ =(cid:173)
`
`('D
`('D
`.......
`N
`.j;o.
`
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w
`N
`-....l
`'N
`U'l
`
`00 = N
`
`25
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 25 of 30
`
`US 7,327,258 B2
`
`GMMS
`Administration
`Module
`
`Wholesaler/
`Retailer
`Porta I
`
`f---
`
`600 l
`
`Incident Handing -- 610)
`....----'--------.
`r- Beacon controller
`Interface
`
`612,
`
`Beacon Manager
`.._..~ (request/reply)
`
`Recovery Interface --
`
`6~
`
`Beacon Manager
`(tracking features)
`
`(618
`
`Subscriber's
`Portal
`(commercial/residential)
`
`----
`
`Scenario Builder
`
`1)2
`
`----
`
`Scenario Monitor
`
`Beacon Manager
`(threshold monitoring
`features)
`
`FIG. 19
`
`26
`
`

`
`702
`
`GUARDIAN SYSTEM
`
`703
`
`I Locate
`Beacon
`
`712
`
`'
`
`704
`
`Track
`Beacon
`
`J
`705
`
`Aux
`Control r
`706
`
`Aux ~Buffer
`Reports
`Beacon
`707
`
`1
`708
`
`Threshold
`Monitoring
`709
`
`BEACON CONTROLLER INTERFACE
`
`BeaconManager
`
`BeaconManager
`
`BeaconManager
`
`BeaconManager
`
`BeaconManager
`
`BEACON A I I BEACON B I I BEACON c I I BEACON D I I BEACON E I I BEACON F
`
`BeaconManager
`
`720
`
`721
`
`700 1
`
`FIG. 20
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`N
`0\
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w
`N
`-....l
`'N
`u.
`
`00 = N
`
`27
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 27 of 30
`
`US 7,327,258 B2
`
`750
`
`7
`
`751
`
`7520
`
`Process
`
`Decision
`
`753\
`r--r>---"""T"""''
`
`Predefined or automatic process
`
`Reference to another system (outgoing)
`
`Reference to another system (incoming)
`
`Stored Data
`
`Looped Operation (Start)
`
`Looped Operation (Stop)
`
`Termination Point (Start/Stop)
`
`FIG. 21
`
`28
`
`

`
`802 1
`
`I
`t
`Retailer
`1-1
`
`Wholesaler 1
`
`Retailer
`1-2
`
`I
`t
`Retailer
`1-N
`
`GMMS
`
`Wholesaler 2
`
`Retailer
`2-2
`
`I
`t
`Retailer
`2-N
`
`I
`t
`Retailer
`2-1
`
`I
`t
`Retailer
`N-1
`
`t
`
`Subscriber!
`!Subscriber!
`lSubscriber
`
`t
`
`ISubscriberl
`ISubscriberl
`lSubscriberl
`
`Subscriber!
`!Subscriber!
`lSubscriberl
`
`t
`I Subscriber!
`!Subscriber!
`lSubscriber
`
`Subscriber!
`!Subscriber!
`lSubscriber
`
`t
`
`Subscriber
`ISubscriberl
`lSubscriberl
`
`t
`I Subscriber
`!Subscriber!
`lSubscriber
`
`1 8o4
`
`I /
`I
`t
`Retailer
`N-N
`
`t
`
`Wholesaler N
`
`r8o6
`
`Retailer
`N-2
`
`( 808
`
`Subscriber
`!Subscriber!
`lSubscriber
`
`Subscriber1
`ISubscriberl
`lSubscriberl
`
`r-7'-
`
`..,..,
`
`814""'
`I Direct Subscriber I
`1 Direct Subscriber 1
`I Direct Subscriber I
`
`t
`809-._.
`I Subscriber!
`!Subscriber!
`!Subscriber
`
`810~ '
`
`Direct
`Reseller
`2
`
`Direct
`Reseller
`1
`
`Direct
`Reseller
`3
`
`812"""
`I Subscriber!
`lSubscriberl
`!Subscriber!
`
`Subscriber!
`lSubscriberl
`!Subscriber!
`
`!Subscriber
`lSubscriberl
`!Subscriber!
`
`e •
`
`00
`•
`~
`~
`~
`
`~ = ~
`
`""f'j
`('D
`?'
`~Ul
`N
`0
`0
`QO
`
`('D
`('D
`
`rFJ =(cid:173)
`.....
`N
`QO
`
`0 .....
`(.H
`0
`
`d
`rJl
`-....l w N
`-....l
`'N
`u.
`
`00 = N
`
`29
`
`

`
`U.S. Patent
`U.S. Patent
`
`Feb.5,2008
`Feb 5,2008
`
`Sheet 29 of 30
`Sheet 29 of 30
`
`US 7,327,258 B2
`US 7,327,258 B2
`
`zszra
`
`Rm
`
`"E
`
`Emm.b.\.....
`
`,.‘--.
`
`
`
`.§\§=8Eummm
`
`.8m»:$E
`
`“Wma
`
`Em
`
`30
`
`Q aj E
`
`.—
`E5.
`:\:|:I
`
`$3:mam
`
`Sm
`
`“an\Em
`
`30
`
`
`
`
`
`
`
`

`
`U.S. Patent
`
`Feb.5,2008
`
`Sheet 30 of 30
`
`US 7,327,258 B2
`
`950 f
`
`Caller identifies
`subscriber's account
`
`956
`
`FIG. 24
`
`Operator finds and selects subscriber's
`account in subscriber management
`module of operator's portal
`
`Security screen prevents unsecured
`access to subscriber's account by asking
`for passcode or override
`
`958
`
`962
`
`964
`
`Yes
`
`Operator enters
`subscriber's
`passcode
`
`Prevent login
`
`Operator enters
`subscriber's portal
`and manages
`subscriber's account
`
`968
`
`Authorized entry,
`including time stamp and
`operator's ID, recorded in
`Subscriber's portal
`
`976
`
`980
`
`Operator required
`to enter override
`justification
`
`Operator enters subscriber's
`portal and manages
`subscriber's account
`
`Operator selects
`"Override" function
`
`978
`
`Override entry including
`time stamp and
`operator's ID, recorded in
`Subscriber's portal
`
`982
`
`31
`
`

`
`US 7,327,258 B2
`
`1
`SYSTEM FOR, AND METHOD OF,
`MONITORING THE MOVEMENTS OF
`MOBILE ITEMS
`
`CROSS-REFERENCES TO RELATED
`APPLICATIONS
`
`This is a non-provisional application 11/048,555 relating
`to a SYSTEM FOR AND METHOD OF MONITORING
`THE MOVEMENTS OF MOBILE ITEMS and lists Ray(cid:173)
`mond D. Fast, Robert R. Goehring and Kai Loon Ng as joint
`inventors. This non-provisional application corresponds to
`provisional application 60/542,208 filed on Feb. 4, 2004 in
`the United States Patent Office.
`
`FIELD OF THE INVENTION
`
`2
`nologies are provided for locating and indicating item posi(cid:173)
`tions. The beacons and the interface provide for new bea(cid:173)
`cons to be added to the system with different characteristics
`than the existing beacons for monitoring the operation of
`new beacons without affecting the operation of existing
`beacons.
`The system includes resellers, retailers, users and sub(cid:173)
`scribers in a flexible relationship to enhance the ease in the
`system operation. Beacons can perform more than one
`10 function (e.g.
`tracking, threshold monitoring) simulta(cid:173)
`neously. Scenarios for the beacons can be created and
`monitored. Recovery personnel can intervene to resolve
`cnses
`
`15
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`This invention relates to a system for, and a method of,
`monitoring beacons attached to mobile items to monitor the
`position and movement of the mobile items. The invention 20
`additionally relates to a system for, and method of, moni(cid:173)
`toring the beacons with respect to non-mobile aspects (e.g.
`battery life, door locks, window openings) of the items. The
`system and methods provide advantages in monitoring such
`that additional beacons can be added to the system with 25
`characteristics different from those of existing beacons in the
`system and such that the addition of the new beacons will
`not affect the operation of the existing beacons in the system.
`
`BACKGROUND OF THE INVENTION
`
`FIG. 1 is a schematic diagram of hardware in a system
`constituting this invention for monitoring the movement
`items under the control of beacons coupled to the items;
`FIG. 2 is another schematic diagram of the hardware
`shown in FIG. 1;
`FIG. 3 is a schematic diagram of software architecture in
`the system;
`FIG. 4 is a flow chart on an overview basis of a beacon
`controller interface included in the system;
`FIG. 5-8 are flow charts showing the operation of the
`beacon controller interface in additional detail;
`FIGS. 9, 10 and lOa are graphs showing the operation of
`30 the beacon controller interface in the system;
`FIGS. 11 and 12 are flow charts showing the operation of
`a scenario manager in the system;
`FIG. 13 is a logic flow chart showing the operation of a
`guardian administration module in the system;
`FIG. 14 is a logic flow chart showing the operation of a
`wholesaler, retailer portal in the system;
`FIG. 15 is a logic flow chart showing the operation of an
`incident handling in the system;
`FIG. 16 is a logic flow chart showing the operation of an
`40 incident handling in the system;
`FIG. 17 is a flow chart showing the operation of a
`recovery interface in the system;
`FIG. 18 is an illustrative map of an area where the
`recovery interface is operating to recover an item (e.g.,
`45 child) who may have wandered outside of a prescribed zone;
`FIG. 19 is a flow chart showing the interrelationship
`between the various flow charts shown in the previous
`Figures;
`FIG. 20 is a schematic diagram showing the operation of
`the beacon controller interface under the control of the
`Guardian Monitoring System in controlling the operation of
`a number of different beacons;
`FIG. 21 is a chart indicating a plurality of individual
`symbols for providing different operations in the system,
`these individual symbols being provided in the flow charts
`specified above; and
`FIG. 22 is a schematic diagram showing the interrelation(cid:173)
`ship between the Guardian Mobile Monitoring System
`60 (GMMS), individual wholesalers, individual retailers and
`individual subscribers in monitoring mobile items in accor(cid:173)
`dance with the flow charts shown in the previous Figures.
`FIG. 23 is a schematic diagram showing how the beacon
`controller interface, a component of the Guardian Mobile
`65 Monitoring System (GMMS), provides the same user inter(cid:173)
`face regardless of the wireless network, wireless location
`technology, or functionality of the beacon.
`
`Systems have been provided for determining the move(cid:173)
`ments of mobile items. For example, tags have been dis(cid:173)
`posed on articles in department stores to signal when mer(cid:173)
`chandise is being removed from the stores without payment 35
`for the items. Tags have also been disposed on articles in
`railroad cars to indicate the movement of the items in the
`railroad cars along the tracks. In the systems now in use, the
`tags have a single design and a single construction. This has
`limited the utility of the systems.
`In recent years, different systems have been provided for
`communicating on a wireless basis between a pair of spaced
`positions. Each of the systems employs a different technol(cid:173)
`ogy of wireless communication. Different systems have also
`been provided in recent years for locating the positions of
`mobile items. Each of these systems employs a different
`location technology. It would be desirable to provide a
`universal system which would be responsive to all of the
`different types of wireless communications between a pair of
`spaced positions and would be responsive to all of the
`different technologies for locating the positions of mobile
`items. It would also be desirable to make these systems so
`flexible in their concept and operation that they could also
`incorporate new wireless communication technologies and
`new location technologies in the future without affecting the 55
`operation of the existing wireless communication technolo(cid:173)
`gies and the existing location technologies n the system.
`
`50
`
`SUMMARY OF THE INVENTION
`
`A system monitors parameters (e.g., speed, posJtJOn,
`threshold boundaries) of mobile items attached to beacons
`and produces signals indicating these parameters. The sys(cid:173)
`tem also monitors non-mobile parameters (e.g., battery life,
`door locks, windows) in the items. Different technologies
`(e.g., wireless) are provided for communicating between the
`beacons and a beacon controller interface. Different tech-
`
`32
`
`

`
`US 7,327,258 B2
`
`3
`FIG. 24 is a schematic diagram showing how an operator
`at a monitoring station can access a subscriber's portal to
`provide services while still protecting the security and
`privacy of the subscriber.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`
`GMMS and Software Architecture
`
`4
`For a monitored security system for mobile objects the
`monitoring station operators are alerted if a panic button is
`activated, if an object is not where it was specified to be at
`a given time, if an object is moving at a velocity greater than
`it was specified to be moving, if triggering of any sensor
`attached to the mobile monitoring device is detected, or if
`tampering with the mobile monitoring device itself is
`detected. In all cases the mobile device, a component of the
`10 GMMS called a beacon, provides the operator with its
`present location.
`A key component to enabling the security company to
`provide the required assistance for these mobile security
`situations is for the system to provide the location of the
`mobile object. Another key component is the means to notifY
`the appropriate personnel with the appropriate information,
`either automatically or manually. The GMMS provides
`several methods of enabling these for mobile applications.
`
`15
`
`Overview
`There has never before been a system that performs the
`functions of the GMMS. It is a machine consisting of many
`components and the system's unique functionality is pro(cid:173)
`vided by the combination of the interconnected components
`and the software that ties them together.
`The combination of components is referred to as the
`Guardian Mobile Monitoring System, or simply the GMMS.
`The GMMS actually includes the integration of several
`separate networks such as wireless communications net- 20
`works, the Internet, the Global Positioning system (GPS),
`and the Public Switched Telephone Network (PSTN).
`The GMMS software can best be understood by describ(cid:173)
`ing two different aspects, the architecture and the applica(cid:173)
`tions. The architecture is the design of the structure of the 25
`software, which allows it to tie together the various com(cid:173)
`ponents and networks of the GMMS and allow the various
`functions, or applications, that control those components to
`be created.
`This document first discusses the unique interconnection 30
`of components and networks that create the GMMS. It then
`describes the unique software architecture, and finally it
`describes some the functionality of the applications provided
`by the system.
`
`GMMS
`
`Mobile
`Monitoring
`
`Definitions:
`
`The Guardian Mobile Monitoring System - not the company
`called Guardian Mobile Monitoring Systems, Inc.
`A service similar to the monitored security services
`pro