US008810392B1
`
`(12) United States Patent
`Teller et al.
`
`(10) Patent No.:
`
`(45) Date of Patent:
`
`US 8,810,392 B1
`Aug. 19, 2014
`
`(54) DEVICE AND METHOD FOR MONITORING
`THE PRESENCE OF ITEMS AND ISSUING AN
`ALERT IF AN ITEM IS NOT DETECTED
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`8/1999 Renney .................. .. 340/539.32
`5,939,981 A *
`7/2000 Rabanne et al.
`......... .. 340/573.4
`6,084,517 A *
`11/2007 Drzaic et al.
`7,295,114 B1
`2/2011 Maeng
`7,880,613 B1
`6/2005 Glick et al.
`2005/0134459 A1*
`2005/0285739 A1* 12/2005 Velhalet al.
`2006/0202840 A1*
`9/2006 Korbonski
`2007/0210930 A1*
`9/2007 Pyo et al.
`2008/0174425 A1*
`7/2008 Torning
`2008/0204233 A1*
`8/2008
`2009/0077675 A1
`3/2009
`340/572.4
`2010/0039266 A1*
`2/2010
`340/572.1
`2010/0188226 A1*
`7/2010
`340/572.1
`2010/0289646 A1* 11/2010
`2010/0302032 A1* 12/2010 Abed ..................... .. 340/539.32
`
`
`
`.............. .. 340/572.1
`.
`340/572.1
`. 340/539.32
`.. 340/573.1
`.. 340/540
`340/572.1
`
`.
`
`* cited by examiner
`
`Primary Examiner — Thomas Mullen
`(74) Attorney, Agent, or Firm — Fish & Richardson P.C.
`
`ABSTRACT
`(57)
`Disclosed herein are methods and systems that involve moni-
`toring presence of items based on context. An exemplary
`method involves: (i) determining a context for a given user;
`(ii) determining a proximity framework between a monitor-
`ing device and one or more items, based on the determined
`context, wherein the proximity framework comprises (a) one
`or more proximity requirements, each proximity requirement
`indicating a required proximity between the monitoring
`device and at least one of the items and (b) a notification
`process corresponding to each proximity requirement; (iii)
`monitoring proximity of each of the items relative to the
`monitoring device, based on a presence signal from each of
`the items, in order to determine when one of the proximity
`requirements is not met; and (iv) responsive to determining
`that one of the proximity requirements is not met, initiating
`the corresponding notification process.
`
`35 Claims, 22 Drawing Sheets
`
`(75)
`
`Inventors: Eric Teller, San Francisco, CA (US);
`Martin T. King, Vashon Island, WA
`(US); Cheryl Grunbeck, legal
`representative, Vashon Island, WA (US);
`Claes-Fredrik Mannby, Mercer Island,
`WA (US); Michael J. Smith, Seattle,
`WA (US)
`
`(73) Assignee: Google Inc., Mountain View, CA (US)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 450 days.
`
`(21) Appl.No.: 13/019,701
`
`(22)
`
`Filed:
`
`Feb. 2, 2011
`
`Related U.S. Application Data
`
`(60) Provisional application No. 61/301,560, filed on Feb.
`4, 2010, provisional application No. 61/301,544, filed
`on Feb. 4, 2010.
`
`(51)
`
`Int. Cl.
`G08B 1/08
`(52) U.S.Cl.
`USPC ............... .. 340/539.32, 235/385; 340/539.11,
`340/572.1
`
`(2006.01)
`
`(58) Field of Classification Search
`USPC ............. .. 340/539.32, 572.1, 539.23, 539.11;
`235/385; 705/28
`See application file for complete search history.
`
`HIMPP 1008
`
`HIMPP 1008
`
`100
`
`130
`
`
`
`K 1
`
`50
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 1 of 22
`
`US 8,810,392 B1
`
`130
`
`FIGURE 1
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 2 of 22
`
`US 8,810,392 B1
`
`200
`‘
`
`MONITORING DEVICE
`
`COMMUNICATION
`RFID
`
`READER
`
`201
`
`202
`
`203
`
`204
`
`205
`
`206
`
`220
`
`ACTIVE SENSORS 221
`
`RFID
`
`BLUETOOTH
`
`224
`
`223
`
`222
`
`221
`
`224
`
` 23°
`
`PASSIVE
`
`SENSORS
`
`RFID
`
`
`
`’;’IIll:.-_‘:‘\‘\1,1:——
`
`
`
`246
`
`248 %
`
`25°
`
`FIGURE 2A
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 3 of 22
`
`US 8,810,392 B1
`
`200
`
`MONITORING DEV!CE
`
`270
`
`265
`
`275
`
`280
`
`M‘BANgg%’E:E"‘G
`
`PAIRING
`MANAGEMENT
`MODULE
`
`ALERTS MODULE
`
`DATABASE
`
`FIGURE 2B
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 4 of 22
`
`US 8,810,392 B1
`
`IS SEPARATED FROM YOU.
`
`WOULD YOU LIKE TO PAIR IT
`
`AN ITEM HAS BEEN IDENTIFIED
`
`THAT CAN BE PAIRED WITH
`THIS DEVICE SO THAT YOU
`WILL BE ALERTED IF THE ITEM
`
`TO THIS DEVICE?
`
`330
`
`HGURE3A
`
`300
`
`320
`
`350
`
`370
`
`380
`
`355
`
`KDISTANCE
`
`360
`kTYPE OF WARNING
`365
`
`VIBRATE V
`
`DEFAULT
`
`KDETECTION FREQUENCY
`
`375
`
`HGUREBB
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 5 of 22
`
`US 8,810,392 B1
`
`“:2
`
`FIGURE4
`
`CHECKOFITEM
`
`415
`
`
`
`DETECT ITEM’S
`PRESENCE?
`
`DELAY
`
`NO
`
`DELAY
`
`420
`
`425
`
`PERFORM PRESENCE
`CHECK OF ITEM
`
`430
`
`
`
`RESPONSE
`RECEIVED
`
`
`
`
`
`NO
`
`PERFORM PRESENCE
`CHECK OF ITEM
`
`YES
`
`435
`
`
`
`440
`
`RETURN
`
`
`
`
`REMOVE ITEM
`FROM
`MONITORING
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 6 of 22
`
`US 8,810,392 B1
`
`500
`
`YOUR READING
`GLASSES CANNOT
`BE DETECTED.
`THE GLASSES WERE
`LAST IDENTIFIED AT 5:45 PM.
`
`AT THIS TIME, YOUR LAPTOP,
`COMPUTER, WALLET AND CAR
`KEYS WERE ALSO IDENTIFIED.
`MORE INFORMATION
`
`PREFERENCES
`
`520
`
`CLEAR WARNING
`
`530
`
`FIGURE 5
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 7 of 22
`
`US 8,810,392 B1
`
`602
`
`MONITORING DEVICE
`
`TEMPERATURE
`
`ELECTRODE
`
`ACCELEROMETER
`
`SHOCK
`
`GYROSCOPE
`
`CHEMICAL
`
`COMPASS
`
`BIOLOGICAL
`
`BAROMETER
`
`LIGHT
`
`MOISTURE
`
`MICROPHONE
`
`DIGITAL CAMERA
`
`COMMUNICATION
`
`WEATHER
`MODULE
`
`RFID
`READER
`
`SYSTEM CLOCK
`
`LOCATON SYSTEM
`
`FM RECEIVER
`
`604
`
`606
`
`608
`
`610
`
`612
`
`614
`
`628
`
`630
`
`632
`
`634
`
`635
`
`FIGURE 6
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 3 of 22
`
`US 8,810,392 B1
`
`700
`
`7042
`
`70412
`
`704c
`
`704d
`
`7046
`
`702a
`
`7021;
`
`702a
`
`702d
`
`7o2e
`
`(VIBRATE(P), LOCK(L))
`
`(VlBRATE_RlNG(P))
`
`PROXIMITY FRAMEWORK (P, L, W, K)
`
`(LOCK(L))
`
`(V|BRATE_RlNG(P), LOCK(L))
`
`(VlBRATE(P))
`
`FIGURE 7
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 9 of 22
`
`US 8,810,392 B1
`
`FIGURE 8
`
`DETERMINE A CONTEXT
`
`START
`
`800
`
`
`
`DETERMINE A PROXIMITY
`FRAMEWORK FOR ONE OR
`MORE ITEMS, BASED ON
`THE DETERMINED CONTEXT
`
`MONITOR THE PROXIMITY OF
`EACH OF THE ITEMS, BASED
`ON A PRESENCE SIGNAL
`FROM EACH ITEM
`
`YES
`
`RE—DETERI\/IINE THE
`CONTEXT
`
`812
`
`RETURN
`
`ALL PROXIMITY
`REQUIREMENTS
`
`808
`
`NO
`
`
`
`
`MET 810
`
`INITIATE THE NOTIFICATION
`PROCESS CORRESPONDING
`TO THE PROXIMITY
`REQUIREMENT THAT IS NOT
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 10 of 22
`
`US 8,810,392 B1
`
`soc
`
`FIGURE 9
`
`RECEIVE USER—lNPUT DATA THAT
`IDENTIFIES A GROUP OF ITEMS AND
`DEFINES, AT LEAST IN PART, THE
`PROXIMITY FRAMEWORK FOR THE
`GROUP OF |TEMS
`
`992
`
`RETURN
`
`
`
`INITIATE THE
`NOTIFICATION PROCESS
`CORRESPONDING T0
`THE PROXIMITY
`REQUIREMENT THAT IS
`NOT MET
`
`904
`
`906
`
`RECEIVE USER-INPUT DATA THAT
`SPECIFIES, AT LEAST IN PART, A
`USER-CONTEXT IN WHICH THE
`PROXIMITY FRAMEWORK SHOULD BE
`AppL[ED
`
`
`ALL PROXIMITY
`REQUIREMENTS
`
`STORE RECORD ASSOCIATING THE
`
`SPECIFIED USER—CONTEXT WITH THE
`IDENTIFIED GROUP OF ITEMS
`
`MONITOR THE CURRENT
`USER-CONTEXT
`
`MOMTOR THE PROX,Mm, OF
`EACH OF THE ,TEMS BASED
`ON A PRESENCE SIGNAL
`FROM EACH ITEM
`
`
`
`
`
`
`
`CURRENT UsER_CQNTEXT
`SUBSTANTIALLY THE SAME
`AS THE SPECIFIED USER-
`
`CONTEXT?
`
`CURRENT USER-CONTEXT
`
`DETERMINE, FROM THE
`STORED DATA, THE
`PROXIMITY FRAMEWORK
`THAT THE USER
`ASSOCIATED WITH THE
`
`910
`
` ACCESS THE STORED DATA
`
`TO DETERMINE THE GROUP
`OF ITEMS THAT IS
`ASSOCIATED WITH THE
`CURRENT USER-CONTEXT
`
`912
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 11 of 22
`
`US 8,810,392 B1
`
`FIGURE 10
`
`1000
`
`
`
`DETERMINE A USER-CONTEXT FOR A GIVEN USER
`
`DETERMINE A PROXIMITY FRAMEWORK BASED AT LEAST IN
`PART ON THE DETERMINED USER CONTEXT, WHERE THE
`PROXIMITY FRAMEWORK INCLUDES:
`
`(A) A PROXIMITY REQUIREMENT BETWEEN A
`MONITORING DEVICE AND AN ITEM-CATEGORY, AND
`(B) AT LEAST ONE NOTIFICATION PROCESS
`CORRESPONDING TO THE PROXIMITY REQUIREMENT
`
`\
`1002
`
`
`
`MONITOR THE PRESENCE SIGNALS FROM
`THE ITEMS IN THE ITEM-CATEGORY
`
`
`
`PROXIMITY REQUIREMENT
`MET FOR AT LEAST ONE ITEM
`IN ITEM-CATEGORY?
`
`1006
`
`
`RETURN
`
`INITIATE THE NOTIFICATION PROCESS THAT
`CORRESPONDS TO THE PROXIMITY REQUIREMENT
`
`1008
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 12 of 22
`
`US 8,810,392 B1
`
`START
`
`1100
`\
`
`1102
`
`1104
`
`1106
`
`1108
`
`1110
`
`IDENTIFY A USER-CONTEXT IN WHICH AT LEAST A
`PREDETERMINED QUANTITY OF A GIVEN TYPE OF ITEM
`SHOULD BE DETECTED BY THE MONITORING DEVICE
`
`IDENTIFIED USER-CONTEXT
`
`GENERATE AND STORE DATA THAT ASSOCIATES THE
`IDENTIFIED USER-CONTEXT WITH A PROXIMITY
`FRAMEWORK THAT INCLUDES:
`(A) A PROXIMITY REQUIREMENT FOR AT LEAST THE
`PREDETERMINED QUANTITY OF THE GIVEN TYPE OF
`ITEM TO BE DETECTABLE IN THE IDENTIFIED USER-
`
`CONTEXT, AND
`(B) AT LEAST ONE NOTIFICATION PROCESS
`CORRESPONDING TO THE PROXIMITY REQUIREMENT
`
`DETERMINE THAT A CURRENT USER-CONTEXT IS
`SUBSTANTIALLY THE SAME AS THE PREVIOUSLY-
`
`SEARCH FOR ANY PRESENCE SIGNALS THAT ARE
`AVAILABLE TO THE MONITORING DEVICE FROM ITEMS OF
`THE GIVEN TYPE
`
`DETERMINE A TOTAL ITEM COUNT FOR THE GIVEN TYPE OF
`ITEM BASED ON THE SEARCH FOR PRESENCE SIGNALS
`
`
`
`TOTAL ITEM COUNT >
`PREDETERMINED QUANTITY?
`
`
`
`INITIATE THE
`coRREsPoND|NG
`NoT||=|(3,/.\T|oN
`PROCESS
`
`
`
`
`
`1112
`
`FIGURE 11
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 13 of 22
`
`US 8,810,392 B1
`
`START
`
`1200
`/
`
`OBSERVING (A) ANY CONTEXT SIGNALS AVAILABLE TO
`THE MONITORING DEVICE, AND (B) PROXIMITY RELATIVE
`TO THE MONITORING DEVICE OF ANY ITEMS FROM WHICH
`PRESENCE SIGNALS CAN BE DETECTED
`
`1202
`
`GENERATE HISTORICAL USER-CONTEXT DATA THAT
`
`INDICATES WHICH CONTEXT SIGNALS AND WHICH ITEMS \
`WERE OBSERVED AT SUBSTANTIALLY THE SAME TIME
`1204
`
`USE THE HISTORICAL USER-CONTEXT DATA AS A BASIS
`
`TO LEARN CERTAIN USER-CONTEXTS IN WHICH CERTAIN \
`PROXIMITY FRAMEWORKS SHOULD BE APPLIED
`1206
`
`
`
`RETU RN
`
`FIGURE 12A
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 14 of 22
`
`US 8,810,392 B1
`
`1210
`
`/
`
`MONITOR CONTEXT SIGNALS
`THAT ARE AVAILABLE TO THE
`MONITORING DEVICE
`
`MONITOR PRESENCE SIGNALS
`FROM ITEMS THAT ARE
`DETECTABLE AT THE
`MONITORING DEVICE
`
`CHANGE IN DETECTED
`
`GENERATE AND STORE A DATA ENTRY THAT INCLUDES:
`
`(A) DATA INDICATING THE ONE OR MORE CONTEXT
`SIGNALS DETERMINED AT THE TIME, AND
`(B) DATA THAT IDENTIFIES EACH NEARBY ITEM FROM
`WHICH A PRESENCE SIGNAL IS RECEIVED
`
`FIGURE 12B
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 15 of 22
`
`US 8,810,392 B1
`
`1 220
`
`DETERMINE ANY AVAILABLE
`CONTEXT SIGNALS
`
`DETECTS ANY AVAILABLE
`PRESENCE SIGNALS
`
`IDENTIFY THE SOURCE ITEM
`FOR EACH DETECTED
`PRESENCE SIGNAL
`
`DETERMINE THE DISTANCE TO
`EACH OF THE DETECTED ITEMS
`
`GENERATE AND STORE A DATA ENTRY THAT INCLUDES:
`
`(A) CONTEXT DATA INDICATING THE ONE OR MORE CONTEXT
`SIGNALS DETERMINED AT THE TIME, AND
`(B) PROXIMITY DATA THAT IDENTIFIES EACH DETECTED ITEM AS
`BEING PRESENT AT THE TIME, AND INDICATES THE DISTANCE TO
`THAT ITEM (IF CALCULABLE)
`
`FIGURE 12C
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 16 of 22
`
`US 8,810,392 B1
`
`.22
`
`<9‘manor.
`
`oocmwoi
`
`Em_,
`
`
`
`m.m:m_wuxficoo
`
`8.2
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 17 of 22
`
`US 8,810,392 B1
`
`fimfl
`
`
`
`mm.manor.
`
`
`
`oucflmfimo:omo..n_
`
`
`
`m_a:m_m«X3200
`
`82
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 18 of 22
`
`US 8,810,392 B1
`
`
`
`mEB_ufloflmm
`
`ND.Em:
`
`MD.Em:
`
`.o.._wQm:w.o§<
`
`...............................~21.
`
`
`
`mE2_._o::os_L_\
`
`83
`
`mmmuumtc
`
`=_eo¢F
`
`33
`
`
`
`E0:oEmz
`
`3.3.
`
`E.mm_:w_u_
`
`xom>>no>3S92:.
`
`:o:mn..o..SMamawm;
`
`
`
`§.§_oo05¢.”
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 19 of 22
`
`US 8,810,392 B1
`
`START
`
`GENERATE AND STORE THE
`HISTORICAL USER-CONTEXT
`
`1500
`
`
`
`DATA
`
`1502
`
`DETERMINE A CURRENT USER-
`CONTEXT FOR A GIVEN USER
`
`COMPARES THE CURRENT
`USER-CONTEXT TO HISTORICAL
`USER-CONTEXT DATA
`
`
`
`BASED AT LEAST IN PART ON THE
`COMPARISON, DETERMINE A PROXIMITY
`FRAMEWORK BETWEEN THE MONITORING
`DEVICE AND ONE OR MORE ITEMS
`
`1508
`
`MONITORS THE PROXIMITY OF
`EACH OF THE ITEMS
`
`YES
`
`ALL PROXIMITY
`REQUIREMENTS
`
`
`
`FIGURE 15
`
`NO
`
`15”
`
`
`THAT IS NOT MET 1514
`
`INITIATE THE NOTIFICATION
`PROCESS CORRESPONDING TO
`THE PROXIMITY REQUIREMENT
`
`RETURN
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 20 of 22
`
`US 8,810,392 B1
`
`4Fmmm..3w£3
`
`
`
`m..ommmuEn_.205..00:0
`
`o3:,
`
`
`
`m:oumuE=EEoofozamz
`
`
`
`2:305.wom.c3:_
`
`
`
`|ooo_.E£m>w:8_%mm:_._o::o_>_
`
`
`
`
`
`
`
`
`
`|3eu_mo._m:a=o5-E2_ow|_.womt3:_E02502
`
`
`
`
`
`
`
`
`
`mom:momt3:_fefiwz
`
`
`
`29..:o=mN_.om3mo-E2_
`
`29
`
`
`
`
`
`|«marm_3Uo_2=o_.8o._
`
`flan§2:oo.._mm:
`
`
`
`u_mo._EoEwmn:m_>_
`
`99.
`
`x.5>3oz
`
`.vNo_.
`
`
`
`pxflcoo_o:m>:E_x9_m
`
`
`
`u_mo.._m:_.:mv._
`
`32
`
`Q>:w_mum
`
`83
`
`2.mm:o_u_
`
`
`
`Low:.mo_._3m__._
`
`
`
`mmmnfima33300
`
`_.Nw_.
`
`
`
`
`
`29..mc_xom..r.>,_2:o>:_:o=moo._
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 21 of 22
`
`US 8,810,392 B1
`
`FIGURE 17
`
`MONITORS THE PRESENCE
`SIGNAL FROM AN ITEM
`
`NO
`
`1702
`
`
`
`1700
`
`\
`I
`
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`
`1708
`
`
`
`
`
`
`PRESENCE SIGNAL
`UNAVAILABLE FOR
`PREDETERMINED PERIOD OF
`TIME?
`
`
`
`YES
`
`//NOTIFICATION
`I PROCESS
`1
`1
`1
`1
`1
`1
`I
`I
`I
`I
`I
`1
`1
`1
`1
`1
`1
`
`SEND A LOST-ITEM MESSAGE
`TO A MONITORING-SUPPORT
`SYSTEM
`
`RECEIVE A MESSAGE FROM THE
`MONITORING SUPPORT SYSTEM THAT
`INDICATES WHETHER OR NOT THE
`PRESENCE SIGNAL FROM THE ITEM HAS
`BEEN DETECTED BY ANOTHER
`MONITORING DEVICE
`
`GENERATE AN ALERT THAT
`INDICATES WHETHER OR NOT
`THE ITEM HAS BEEN DETECTED 1710
`
`RETURN
`
`

`

`U.S. Patent
`
`Aug. 19, 2014
`
`Sheet 22 of 22
`
`US 8,810,392 B1
`
`START
`
`1800
`
`RECEIVE ONE OR MORE FOUND-ITEM MESSAGES,
`WHERE EACH FOUND-ITEM MESSAGE IDENTIFIES AN
`ITEM THAT HAS BEEN DETECTED BY A FIRST
`MONITORING DEVICE THAT DOES NOT HOLD RIGHTS
`
`TO THE IDENTIFIED ITEM 1302
`
`RECEIVES A LOST-ITEM MESSAGE THAT IDENTIFIES A
`LOST ITEM THAT A SECOND MONITORING DEVICE,
`WHICH HAS RIGHTS TO THE LOST ITEM, DID NOT
`DETECT AS EXPECTED
`
`1804
`
`LOST ITEM IDENTIFIED IN A
`FOUND-ITEM MESSAGE?
`
`Sggggg ’m)",S,5‘+SC')fiS(3TgET\::EE
`THAT INDICATES THAT THE
`LOST ITEM HAS BEEN FOUND
`
`SENDS A MESSAGE TO THE
`SECOND MONITORING DEVICE
`THAT INDICATES THAT THE
`LOST ITEM HAS NOT BEEN
`FOUND
`
`1810
`
`RETURN
`
`FIGURE 18
`
`

`

`US 8,810,392 B1
`
`1
`DEVICE AND METHOD FOR MONITORING
`THE PRESENCE OF ITEMS AND ISSUING AN
`ALERT IF AN ITEM IS NOT DETECTED
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`This application claims priority to U.S. Provisional Appli-
`cation No. 61/301,560, entitled “Device and Method for
`Monitoring the Presence of Items and Issuing an Alert if an
`Item is Not Detected”, filed on Feb. 4, 2010, and to U.S.
`Provisional Application No. 61/301,544, entitled “System
`and Method for Real-Time Based Interaction of a Mobile
`
`Phone with a User in Response to Location Detection,” filed
`on Feb. 4, 2010, which are herein incorporated by reference
`for all purposes.
`
`BACKGROUND
`
`A person typically needs various portable items near him
`throughout the day. For example, a person may use his read-
`ing glasses and laptop at both his house and ofiice, and he may
`need his wallet and keys wherever he goes. In the absence of
`such items, a person may become frustrated, inefficient, or
`even endangered. Such items therefore must not be forgotten,
`misplaced, or lost.
`Despite a person’s best intentions and attempts, however, it
`is almost inevitable that he will eventually forget or misplace
`something that is necessary or important for him to have near.
`A wallet, for example, may be forgotten at a restaurant, or
`keys may fall out of a pocket and slip between couch cush-
`ions. In either situation, a person may not realize that his
`personal item has disappeared from his presence until a later
`time when it is too late or too inconvenient to retrieve the
`
`missing item.
`
`SUMMARY
`
`The present application discloses systems and methods
`that generally involve monitoring of items based on context.
`In a first aspect, an example computer-implemented
`method involves: (i) determining a context; (ii) determining a
`proximity framework between a monitoring device and one
`or more items, based on the determined context, wherein the
`proximity framework comprises (a) one or more proximity
`requirements, each proximity requirement
`indicating a
`required proximity between the monitoring device and at
`least one of the items and (b) a notification process corre-
`sponding to each proximity requirement; (iii) monitoring
`proximity of each of the items relative to the monitoring
`device, based on a presence signal fro1n each of the items, in
`order to determine when one ofthe proximity requirements is
`not met; and (iv) responsive to determining that one of the
`proximity requirements is not met, initiating the correspond-
`ing notification process.
`In a second aspect, an example computer-implemented
`method involves: (i) receiving, via a user-interface of a moni-
`toring device, user input that comprises one or more user-
`provided context signals; (ii) determining, based at least in
`part on the one or more user-provided context signals, a
`context in which to apply a proximity framework for one or
`more items and wherein the proximity framework comprises
`(a) one or more proximity requirements, each proximity
`requirement indicating a required proximity between the
`monitoring device and at least one of the items and (b) a
`notification process corresponding to each proximity require-
`ment; (iii) monitoring context via the monitoring device; and
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`(iv) detecting when the context substantially matches the
`identified context and responsively: (a) determining whether
`any one of the proximity requirements is not met based on a
`presence signal from each item; and (b) responsive to deter-
`mining that one of the proximity requirements is not met,
`initiating the corresponding notification process.
`In a third aspect, an example computer-implemented
`method involves: (i) determining a context for a given user;
`(ii) determining a group of one or more items that is associ-
`ated with the current user context; (iii) determining a prox-
`imity framework for the group of items based at least in part
`on the current user context, wherein the proximity framework
`comprises (a) one or more proximity requirements and (b) at
`least one notification process corresponding to each proxim-
`ity requirement, and wherein each proximity requirement
`indicates a required proximity between a monitoring device
`and at least one of the items; (iv) monitoring a proximity of
`each item from the group relative to the monitoring device,
`based on a presence signal from each item, in order to detect
`when any one of the proximity requirements is not met; and
`(v) responsive to detecting that one of the proximity require-
`ments is not met, initiating the corresponding notification
`process.
`In a fourth aspect, an example computer-implemented
`method involves: (i) determining a context for a given user;
`(ii) determining a proximity framework based at least in part
`on the current user context, wherein the proximity framework
`comprises (a) a proximity requirement between a monitoring
`device and an item-category comprising a plurality of items,
`and (b) at least one notification process corresponding to the
`proximity requirement; (iii) monitoring, based on a presence
`signal from each item, whether or not the proximity require-
`ment between the monitoring device and the item-category is
`met for at least one of the items in the item category; and (iv)
`responsive to a determination that the proximity requirement
`between the monitoring device and the item-category is not
`met for at least one ofthe items in the item-category, initiating
`the corresponding notification process.
`In a fifth aspect, an example computer-implemented
`method involves:
`(i) determining a proximity framework
`between a monitoring device and an item, and wherein the
`proximity framework comprises (a) a proximity requirement
`between the item and the monitoring device, and (b) at least
`one notification process corresponding to the proximity
`requirement; (ii) monitoring a presence signal from the item
`and detecting when the presence signal is unavailable for a
`predetermined period of time; and (iii) responsive to detect-
`ing that the presence signal is unavailable for a predetermined
`period of time, initiating the corresponding notification pro-
`cess, wherein the notification process comprises: (a) sending
`a location-query message to a monitoring-support system that
`determines whether another monitoring device has detected
`the presence signal from the item; (b) receiving, from the
`monitoring-support system, a message indicating whether or
`not the presence signal from the item has been detected by
`another monitoring device; and (c) providing an indication of
`whether or not the item has been detected by another moni-
`toring device.
`In a sixth aspect, an example computer-implemented
`method involves: (i) identifying a context in which at least a
`predetermined quantity of the given type of item should be
`detected by the monitoring device, wherein each item of the
`given type is detectable via a presence signal transmitted from
`the item, and wherein a proximity framework between the
`monitoring device and the given type of item comprises (a) a
`proximity requirement for at least the predetermined quantity
`of the given type of item to be detectable in the identified
`
`

`

`US 8,810,392 B1
`
`3
`context, and (b) at least one notification process correspond-
`ing to the proximity requirement; (ii) determining that a con-
`text is the identified context and responsively: (a) searching
`for and receiving any presence signals that are transmitted by
`the given type of item; (b) based at least in part on a number
`of presence signals received at the monitoring device from
`items of the given type, determining a total item count for the
`given type of item; (c) determining wl1ether or not the prox-
`imity requirement for at least the predetermined quantity of
`the given type of item is met by the total item count; (e) if it is
`determined that the proximity requirement is not met, then
`initiating the corresponding notification process; and (f) oth-
`erwise, refraining from initiating the corresponding notifica-
`tion process.
`In a seventh aspect, an example computer-implemented
`method involves: (i) determining a context for a given user;
`(ii) determining a proximity framework between a plurality of
`items based on the determined context, wherein the proximity
`framework comprises (a) one or more proximity require-
`ments, each proximity requirement indicating a required
`proximity between at least two of the plurality of items and
`(b) a notification process corresponding to each proximity
`requirement; (iii) for each of the proximity requirements,
`monitoring proximity between the at least two items for
`which the proximity requirement indicates the required prox-
`imity in order to determine whether or not the proximity
`requirement is not met; (iv) responsive to determining that
`one of the proximity requirements is not met, initiating the
`notification process corresponding to the proximity require-
`ment that is not met.
`
`In an eighth aspect, an example system for a monitoring
`device includes: a wireless interface configured to wirelessly
`detect presence signals transmitted from nearby items; a non-
`transitory computer-readable medium; and program instruc-
`tions stored on the non-transitory computer-readable medium
`and executable by at least one processor to: (i) determine a
`context for a user associated with the monitoring-device sys-
`tem; (ii) use the determined context as a basis to determine a
`proximity framework between the monitoring device and one
`or more items, wherein a presence signal is transmitted from
`each item, wherein the proximity framework comprises: (a)
`one or more proximity requirements, each proximity require-
`ment indicating a required proximity between the monitoring
`device and one of the items, and (b) a notification process
`corresponding to each proximity requirement; (iii) monitor-
`ing, via the presence signals detected at the at least one
`wireless interface, proximity of each of the items relative to
`the monitoring device in order to determine when one of the
`proximity requirements is not met; and (iv) responsive to a
`determination that one of the proximity requirements is not
`met, cause the monitoring device to initiate the notification
`process corresponding to the proximity requirement that is
`not met.
`
`In a ninth aspect, an example computer-implemented
`method involves: (i) determining a current context for a given
`user; (ii) comparing the current context to historical context
`data; (iii) determining a proximity framework between a
`monitoring device and one or more items, based on the com-
`parison between the current context and the historical context
`data, wherein the proximity framework comprises (a) one or
`more proximity requirements, each proximity requirement
`indicating a required proximity between the monitoring
`device and at least one of the items and (b) a notification
`process corresponding to each proximity requirement; (iv)
`monitoring proximity of each of the items relative to the
`monitoring device, based on a presence signal from each of
`the items, in order to determine when one of the proximity
`
`4
`
`requirements is not met; and (v) responsive to determining
`that one of the proximity requirements is not met, initiating
`the corresponding notification process.
`In a tenth aspect, an example system for a monitoring-
`support system includes a non-transitory computer-readable
`medium and program instructions stored on the non-transi-
`tory computer-readable medium and executable by at least
`one processor to: (i) receive one or more found-item mes-
`sages at a monitoring-support system, wherein the found-
`iten1 messages identify items that have been detected by one
`or more first monitoring devices that do not hold rights to the
`identified items; (ii) receive a lost-item message at the moni-
`toring-support system, wherein lost-item message identifies a
`lost item that a second monitoring device did not detect as
`expected, wherein the second monitoring device has rights to
`the lost item; (iii) responsively determine whether or not the
`lo st item has been identified in one ofthe received found-item
`
`10
`
`15
`
`messages; and (iv) send a message to the second monitoring
`device that indicates whether or not the lost item has been
`
`20
`
`detected by one of the first monitoring devices.
`In an eleventh aspect, an example computer-implemented
`method involves: (i) receiving, in a monitoring-support sys-
`tem, one or more found-item messages, wherein the found-
`item messages identify items that have been detected by one
`or more first monitoring devices that do not hold rights to the
`identified items; (ii) receiving, in the monitoring-support sys-
`tem, a lost-item message that identifies a lost item that a
`second monitoring device did not detect as expected, wherein
`the second monitoring device has rights to the lost item; (iii)
`responsively determining whether or not the lost item has
`been identified in one of the received found-item messages;
`and (iv) sending a message to the second monitoring device
`that indicates whether or not the lost item has been detected
`
`by one of the first monitoring devices.
`These as well as other aspects, advantages, and altema-
`tives, will become apparent to those of ordinary skill in the art
`by reading the following detailed description, with reference
`where appropriate to the accompanying drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`25
`
`30
`
`35
`
`40
`
`FIG. 1 is depicts a representative scenario in which a moni-
`toring device is paired with multiple items and issues an alert
`if an item cannot be sensed.
`
`45
`
`FIG. 2A is a block diagram showing hardware components
`of a device for monitoring the presence of an item and for
`issuing an alert if the item is not sensed.
`FIG. 2B is a block diagram showing software modules of a
`device for monitoring the presence of an item and for issuing
`an alert if the item is not sensed.
`
`FIG. 3A is a representative interface that is displayed on a
`monitoring device to allow a user to pair an item to the
`monitoring device.
`FIG. 3B is a representative interface that is displayed on a
`monitoring device to allow a user to adjust pairing prefer-
`ences with respect to an item.
`FIG. 4 is a flow diagram showing steps performed by a
`monitoring device to monitor an item and to issue an alert.
`FIG. 5 is a representative interface that is displayed on a
`monitoring device to alert a user if a monitored item is no
`longer detected.
`FIG. 6 is a block diagram illustrating a monitoring device
`that includes sensors and program logic to determine context,
`according to an example embodiment.
`FIG. 7 is a table showing an example proximity framework
`for a set of items.
`
`50
`
`55
`
`60
`
`65
`
`

`

`US 8,810,392 B1
`
`5
`FIG. 8 is a flow chart illustrating a method in which a
`proximity framework for monitoring one or more items is
`selected according to determined context.
`FIG. 9 is a flow chart illustrating a method according to an
`example embodiment in which a group of items and its asso-
`ciated proximity framework are determined based upon a
`determined context.
`
`FIG. 10 is a flow chart illustrating a method that accounts
`for item-category proximity requirements, according to an
`example embodiment.
`FIG. 11 is flow chart illustrating a method that is applicable
`to monitor an inventory of an item, according to an example
`embodiment.
`
`FIG. 12A is a flow chart illustrating a method for dynami-
`cally learning relationships between contexts and proximity
`frameworks, according to an example embodiment.
`FIG. 12B is a flow chart illustrating a method carried out by
`a monitoring device to automatically populate a historical
`context database, according to an example embodiment.
`FIG. 12C is another flow chart illustrating a method carried
`out by a monitoring device to automatically populate a his-
`torical context database, according to an example embodi-
`ment.
`
`FIG. 13A is an illustration of snapshots in a historical
`context database, according to an example embodiment.
`FIG. 13B is another illustration of snapshots in a historical
`context database, according to an example embodiment.
`FIG. 14 is an illustration of a user-interface that may be
`provided by a monitoring device, according to an example
`embodiment.
`
`FIG. 15 is a flow chart illustrating a method for determining
`a proximity framework based on a comparison of a current
`context to a historical context, according to an example
`embodiment.
`
`FIG. 16 is block diagram illustrating a monitoring-support
`system according to an example embodiment.
`FIG. 17 is a flow chart illustrating a method carried out by
`monitoring device with lost-and-found functionality, accord-
`ing to an example embodiment.
`FIG. 18 is flow chart illustrating a method that may be
`carried out by a monitoring-support system to facilitate a
`lost-and-found service, according to an example embodi-
`ment.
`
`DETAILED DESCRIPTION
`
`The following detailed description describes various fea-
`tures and functions of the disclosed systems and methods
`with reference to the accompanying figures. In the figures,
`similar symbols typically identify similar components, unless
`context dictates otherwise. The illustrative system and
`method embodiments described herein are not meant to be
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`limiting. It will be readily understood that certain aspects of
`the disclosed systems and methods can be arranged and com-
`bined in a wide variety of different configurations, all of 55
`which are contemplated herein.
`A method and monitoring device are described that alert a
`user who has or is about to misplace, forget, lose, or otherwise
`have an item removed from the user’s presence. The moni-
`toring device monitors the presence of items in its vicinity,
`using a short-range wireless communication or sensing tech-
`nology, such as Near Field Communication (NFC), Blue-
`tooth, RuBee, radio-frequency identification (RFID), or any
`other method of wireless communication or sensing. If the
`monitoring device is no longer able to detect the presence of 65
`the item, thereby implying that the item has been lost, forgot-
`ten, stolen, or otherwise missing, the device issues a visual,
`
`60
`
`6
`audible, and/or physical alert to the user. The alert indicates to
`the user that they may want to search for or retrieve the
`missing item.
`Herein, a “monitoring device” should be Lmderstood to be
`any device or item capable of sensing or detecting the pres-
`ence of another device or item. Further, an “item” should be
`understood to be anything that is detectable by a monitoring
`device. As such, an item that is configured to detect other
`items may also be considered a monitoring device, and a
`monitoring device that is detectable may be considered an
`item.
`
`In some embodiments, an item is paired with a monitoring
`device and the monitoring device issues an alert if the item
`can no longer be detected by the monitoring device (e.g., the
`monitoring device can no longer sense or communicate with
`the item). For example, a mobile phone may be equipped with
`an RFID reader, and it may monitor an RFID tag attached to
`and associated with a car key. If the mobile phone attempts to
`read the RFID tag associated with the key and is unable to, the
`mobile phone issues an alert.
`In some embodiments, an item is paired with a monitoring
`device and the monitoring device issues an alert if the moni-
`toring device detects that the item is more than a predeter-
`mined distance away from the monitoring device and there-
`fore potentially about to go missing. For example, a mobile
`phone may be equipped with a Bluetooth device, and it may
`monitor another Bluetooth device attached to and associated
`
`with a laptop computer. The mobile phone may monitor both
`the presence of the laptop computer and the distance that the
`laptop computer is away from the