I 1111111111111111 11111 1111111111 111111111111111 11111 11111 1111111111 11111111
`US009679289B 1
`
`c12) United States Patent
`Brown
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,679,289 Bl
`*Jun. 13, 2017
`
`(52) U.S. Cl.
`CPC ........... G06Q 201363 (2013.01); G06F 21132
`(2013.01); G06F 21135 (2013.01); G06Q
`20/40145 (2013.01); H04L 63/0492 (2013.01);
`H04L 63/0861 (2013.01); H04L 63/10
`(2013.01); H04W 12104 (2013.01); H04W
`12108 (2013.01); H04W 88102 (2013.01)
`(58) Field of Classification Search
`USPC .............................................................. 726/3
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,623,552 A
`6,728,397 B2
`
`4/1997 Lane
`4/2004 McNeal
`(Continued)
`Jason Lee
`Primary Examiner -
`(74) Attorney, Agent, or Firm - Patent Law Works LLP
`
`ABSTRACT
`(57)
`A hybrid device includes a personal digital key (PDK) and
`a receiver-decoder circuit (RDC). The PDK and RDC of the
`hybrid device are coupled for communication with each
`other. In one embodiment, the hybrid device also provides a
`physical interconnect for connecting to other devices to send
`and receive control signals and data, and receive power. The
`hybrid device operates in one of several modes including,
`PDK only, RDC only, or PDK and RDC. This allows a
`variety of system configurations for mixed operation includ(cid:173)
`ing: PDK/RDC, RDC/RDC or PDK/PDK. The present
`invention also includes a number of system configurations
`for use of the hybrid device including: use of the hybrid
`device in a cell phone; simultaneous use of the PDK and the
`RDC functionality of hybrid device; use of multiple links of
`hybrid device to generate an authorization signal, use of
`multiple PDK links to the hybrid device to generate an
`authorization signal; and use of the hybrid device for autho(cid:173)
`rization inheritance.
`20 Claims, 15 Drawing Sheets
`
`120C
`
`Application 120A
`
`(54) HYBRID DEVICE HAVING A PERSONAL
`DIGITAL KEY AND RECEIVER-DECODER
`CIRCUIT AND METHODS OF USE
`
`(71) Applicant: Proxense, LLC, Bend, OR (US)
`
`(72)
`
`Inventor: David L. Brown, Jupiter, FL (US)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by O days.
`
`This patent is subject to a terminal dis(cid:173)
`claimer.
`
`(21) Appl. No.: 14/961,645
`
`(22) Filed:
`
`Dec. 7, 2015
`
`(63)
`
`(51)
`
`Related U.S. Application Data
`
`Continuation of application No. 14/677,893, filed on
`Apr. 2, 2015, now Pat. No. 9,235,700, which is a
`continuation of application No. 14/171,705, filed on
`Feb. 3, 2014, now Pat. No. 9,049,188, which is a
`continuation of application No. 13/445,825, filed on
`Apr. 12, 2012, now Pat. No. 8,646,042, which is a
`continuation of application No. 12/329,329, filed on
`Dec. 5, 2008, now Pat. No. 8,171,528.
`(Continued)
`
`Int. Cl.
`H04L 29106
`G06Q 20136
`H04W 12104
`H04W 12108
`G06F 21132
`G06F 21135
`G06Q 20140
`H04W88/02
`
`(2006.01)
`(2012.01)
`(2009.01)
`(2009.01)
`(2013.01)
`(2013.01)
`(2012.01)
`(2009.01)
`
`100
`
`POK 102
`
`Service
`Blk 112A
`112B
`112C
`
`112N
`
`106
`
`---=zb--
`
`Sensor 108
`
`Access
`Kev 118A
`118D
`118F
`
`Biometrics
`104
`
`Page 1 of 29
`
`GOOGLE EXHIBIT 1001
`
`

`

`US 9,679,289 Bl
`Page 2
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/992,953, filed on Dec.
`6, 2007.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,879,966 Bl
`7,159,765 B2
`7,231,068 B2
`7,349,557 B2
`7,565,329 B2
`8,678,273 B2
`2005/0116020 Al
`2007 /0271194 Al*
`
`4/2005 Lapsley et al.
`1/2007 Frerking
`6/2007 Tibor
`3/2008 Tibor
`7/2009 Lapsley et al.
`3/2014 McNeal
`6/2005 Smolucha et al.
`11/2007 Walker .
`
`* cited by examiner
`
`G06Q 30/02
`705/80
`
`Page 2 of 29
`
`

`

`U.S. Patent
`
`Jun.13,2017
`
`Sheet 1 of 15
`
`US 9,679,289 Bl
`
`<(
`0
`N
`
`u
`
`0
`N
`
`sir-
`
`CJ
`LL
`
`00
`0
`
`I....
`
`0 en
`C
`Q.)
`Cf)
`
`en <(
`en oo
`Q.) ..-
`(.) ..-
`(.) >-
`<( Q.)
`:::.::::
`
`0 LL
`00 00
`..- ..-
`..- ..-
`
`en
`(.) :s -.;:J(cid:173)
`Q.) 0 E ..(cid:173)
`a
`a5
`
`(0
`0
`
`N
`0
`
`:::.::::
`0 a..
`
`Q.) <(
`.!:! ~ co
`2:: ..- N ..-
`Q.) ~ ..-
`Cf) -co
`
`u
`N ..-
`..-
`
`Page 3 of 29
`
`

`

`U.S. Patent
`
`Jun.13,2017
`
`Sheet 2 of 15
`
`US 9,679,289 Bl
`
`~
`
`~
`
`I....
`Q.)
`>
`·cvo
`(.) r--
`~N
`ro
`I-
`
`I....
`
`C
`en o
`en :;::;
`ro o
`a.>
`~ .!:!~
`~ §:
`<(
`
`<D
`..
`N
`......
`
`(.)
`Q.)
`Q.)
`Cf)
`co
`Cf)
`
`..,._,
`00
`..-
`N
`..-
`N
`m
`...::.
`ro
`:::.::::
`0
`v9c ldAl::iaofldAJ:lU:J
`I
`c9c Jopa1as
`
`:;:::;-
`(.)
`Q.)
`Q.)
`Cf)
`co
`~
`
`N
`CJ
`LL
`
`Q.) <(
`co
`U N
`-- ..-
`2:: ..-
`N
`..-
`Q.) ~ ..-
`Cf) co
`
`u
`N
`..-
`..-
`
`I
`
`I
`
`I
`
`z
`N
`..-
`..-
`
`~
`
`.)
`
`r
`
`N
`0 ...---
`~
`0
`0....
`
`0
`L.C)
`N
`
`0
`..-
`N
`c:-
`0
`E
`Q.)
`~
`
`\...
`
`Page 4 of 29
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 3 of 15
`Sheet 3 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`~
`I....
`O o
`:s ..-
`ID ..-
`z
`
`~ I.
`
`OLL80€
`
`
`
`OMAN908COE}J0}U|
`
`(Sn}e}g
`
`U) 0
`::::,~
`CU C
`Cf) u
`...... 0
`
`jo.UO.)
`
`~ I.
`
`t
`ON
`a....-
`
`QC"")
`
`CV')
`
`€Old
`
`CJ
`LL
`
`I....
`
`JOSS8901q
`
`0 en
`en co
`90€
`Q.) 0
`(.) C"") e
`a..
`
`I
`
`u -.;:J-
`00
`0::: C"")
`
`,,
`
`~N
`00
`a.. ...--
`
`
`
`
`HOMISN(s)iapeoy
`
`(.) ..........
`-;::~
`ID ID N
`E -o o
`o
`ro M
`- - Q.)
`co 0:::
`
`~ Q.)
`I....
`(.)
`o
`ro oo
`~ ' t :o
`Q.) 2 C"")
`Z
`C
`
`
`
`90]JosueS
`
`00
`0 ...-
`I.....
`0
`Cf)
`C:
`Q)
`CJ)
`
`ouOWolg
`
`'I.
`
`Page 5 of 29
`
`Page 5 of 29
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 4 of 15
`Sheet 4 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`
`
`Cf) u a..
`
`I....
`
`00
`0 ..-
`0 en
`C
`Q.)
`Cf)
`
`01¢a0Inaqauojepuels/oq80},Josuag
`
`COLAdd
`
`0 ..-
`
`L.C)
`Q.)
`(.)
`·5
`Q.)
`0
`Q.)
`C
`0
`ro
`"O
`C ro
`......
`
`
`
`
`
`>-
`C
`Q.)
`0
`:::.:::: co
`:;:::;
`ast
`ro o
`Oc
`en oo
`·a.~ ~ ......
`U N
`en ..-
`
`uoneoiddy
`
`c..
`<(
`
`Kaysseooy
`
`(.)
`<(
`
`- o
`0.... N
`<( L.C)
`
`en <(
`en oo 0 LL
`Q.) ..- 00 00
`(.) ..- ..- ..-
`(.) >- ..- ..-
`<( Q.)
`:::.::::
`
`yOla
`
`~
`CJ
`LL
`
`(0
`0
`
`N
`0
`
`:::.::::
`0 a..
`
`Page 6 of 29
`
`VellAIG
`
`9019S
`
`co u
`Chl
`deb
`N N
`..- ..-
`..- ..-
`Q.) ~
`
`Q.) <(
`U N
`·2: ;:::
`Cf) -co
`
`Page 6 of 29
`
`

`

`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 5 of 15
`Sheet 5 of 15
`
`Q) u -~
`
`Q)
`(./)
`
`
`
`BIIAIGS|BUIS]X4
`
`C'O
`,._
`c::
`Q)
`
`>< w
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`LC')
`
`GOld
`
`(9
`LL
`
`uogeoddy
`
`>,
`c::
`Q)
`0
`~o ~ (Cl
`ash
`0c}
`en oo
`UN
`·a_ -r-
`en ..-
`~ ......
`u
`Cl.
`<(
`<(
`
`Keysseooy
`
`)
`I
`
`0 ..-
`..-
`-c:
`0
`~ I
`Q) z
`
`uoneoddy
`
`c::
`0
`~
`.S:2
`Cl.
`Cl.
`<(
`
`-o
`0... N
`<( L.O
`
`N u=;
`u ">
`
`Q)
`
`
`
`Josuas Iebh
`
`CLGBIABPOHOMPN/Od
`
`Q)
`0
`"'C
`Q)
`,._
`.:,,::
`0
`~
`z
`u
`
`Q)
`
`0...
`
`VELLAey
`
`ssa00y
`
`en <(
`en oo 0 LL
`Q) ..- 00 00
`u..- ..- ..-
`u >- ..- ..-
`<( Q)
`~
`
`9Q|
`
`00
`0 ..-
`0
`en
`c::
`Q)
`(./)
`
`<D
`0
`
`N
`0
`
`cOl¥dd
`
`~
`0
`0...
`
`S0IMOS
`
`Q)
`
`Q) <(
`(Cl u
`gcbh
`.S:2 ~
`2'.: ..-
`N N
`..- ..-
`..- ..-
`(./) -(Cl
`
`Welt4d
`
`.:,,::
`
`U.S. Patent
`U.S. Patent
`
`Page 7 of 29
`
`Page 7 of 29
`
`

`

`Ul
`
`....
`0 ....
`O'I
`.....
`=- ('D
`
`('D
`
`rJJ
`
`....
`~ = ? ....
`
`-....J
`0
`N
`~~
`
`= ~
`
`~
`~
`~
`~
`
`00 .
`e .
`
`'\.11 App 120Z3
`
`I
`
`510Z3
`
`I
`
`"
`
`11 Key 118B 11
`
`I App 120Z2
`I 510Z2 I I
`
`~'\
`
`108Z
`
`/
`
`11
`
`11 Key 118A
`
`/
`
`I
`
`I App 120Z1 I
`
`510Z1
`
`Key 11 SF
`
`Key 118C
`
`120Y2
`App
`
`App
`
`510Y
`
`\0 = """'
`
`00
`'N
`\0
`-....l
`O'I
`\0
`d r.,;_
`
`1 1 Key 118B 11
`
`FIG. 6
`
`j
`I I
`
`112N
`
`■
`
`l
`I
`
`Key 118C
`
`App 120V I
`I
`
`510V
`
`I I 112B I I
`App 120W 11 ~ I I Service I
`POK 102 µ
`
`Key 118C 11
`
`I
`
`510W
`
`112C
`
`Blk 112A
`
`~ 120Y1
`....
`
`I
`
`I
`
`Key 118C 11
`App 120X 11 ~
`
`I
`
`510X
`
`Page 8 of 29
`
`

`

`U.S. Patent
`
`Jun.13,2017
`
`Sheet 7 of 15
`
`US 9,679,289 Bl
`
`C: Q.)
`
`0 cu =
`·- u
`~ LL 8 0:::
`u
`
`Q.)
`C:
`
`~:!=
`"O C:
`C: :::J
`.m
`
`(./")
`
`r-(cid:173)
`C)
`LL
`
`0£L 1/\ll/\JS
`
`Ovl sng
`
`~
`C: N
`r--= 0)
`0
`ro c:
`c:.., · -
`0 ~
`c:.., ro
`_J
`~
`
`0)
`C:
`·a, co
`ro o
`U> N
`:g r--
`2
`
`u
`0
`N r--
`~
`Q.)
`<(
`
`~o
`ro o
`o....~
`"O U)
`.!:::: 0..
`..s:::: 0..
`I- <(
`
`U)
`0..
`0..
`<( w
`Q.) 0
`+-'N Or--
`E
`Q.)
`0:::
`
`ro
`,..._
`,..._
`C: ~
`Q.) 0 x~
`w Q.)
`oZ
`I-
`
`Page 9 of 29
`
`

`

`U.S. Patent
`
`Jun.13,2017
`
`Sheet 8 of 15
`
`US 9,679,289 Bl
`
`830~
`
`830~
`
`FIG. 8
`
`FIG. 9
`
`Page 10 of 29
`
`

`

`\0 = "'"'
`
`00
`'N
`\0
`-....l
`O'I
`\0
`d r.,;_
`
`FIG. 10
`
`N
`~~
`
`0 ....
`? ....
`2'
`
`-....J
`
`~ = ~
`
`~
`~
`~
`
`00 .
`e .
`
`presses button 1
`
`1010 User
`
`I
`
`PD!tj
`
`Beacon (no Aux. Data
`
`I Sensor I
`
`oordinator
`
`AQQlication
`
`button 1
`
`1060 POK clears
`
`ALOHA (no Alerts
`
`Beacon(Button
`
`I• I ALOHA ,Button 1 Alertl I I
`
`I
`
`1050B
`
`I•
`
`B
`
`I 1 0S0A I
`1040 Operator clears 11 • .........,...~-
`
`alert (button 1)
`
`request displayed
`
`1 030 Service
`
`Ul
`
`....
`0 ....
`.....
`rJJ =(cid:173)
`
`1,0
`
`('D
`('D
`
`Page 11 of 29
`
`

`

`U.S. Patent
`
`Jun.13,2017
`
`Sheet 10 of 15
`
`US 9,679,289 Bl
`
`a::: w
`wU
`I>
`I- w
`Oo
`
`<.D
`0 ...--(cid:173)
`...---
`
`-.;:I'"
`0
`...---
`...---
`
`rol
`0N
`::::s::::
`a..~
`
`rol
`u
`0
`0::: g
`
`-.;:J-
`
`sir-
`
`sir-.
`CJ
`LL
`
`N
`0
`...---
`...---
`Q) u
`">
`Q)
`0
`"O
`·c
`..0
`:r:
`
`Page 12 of 29
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 11 of 15
`Sheet 11 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`
`
`COC)9UOUdIl9D
`
`<D
`0 ..--
`..--
`
`C'il v
`
`C)
`CV)
`
`u
`0
`0:::
`
`Asayeg9sjuasuodwo)
`
`
`
`BU0Ud[9D
`
`c:-
`£:l
`C'il
`a> en
`5 od v
`..s:::: en o
`0... t: N
`Q) .,....
`a3
`C:
`u 0
`Cl.
`E
`0 u
`
`.._,.
`0 ..--
`
`..--(
`
`C'il
`N
`C)
`:::.:::
`0
`0...
`
`N
`0 ..--
`..--
`
`N
`
`~
`
`chOld
`
`■ CJ
`LL
`
`N
`0
`N
`
`
`
`~
`Q)
`C:
`0
`...c:
`0....
`
`Q)
`0
`
`BOLNdd EOEOdY42014d
`
`(X)
`0
`N ..--
`
`PIEDWIS
`
`9021
`
`.0
`N
`C)
`:::.:::
`0
`0...
`
`Page 13 of 29
`
`Page 13 of 29
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 12 of 15
`Sheet 12 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`.0
`
`("")
`
`qv0€OdY
`
`"'-'" 0
`u
`0
`0:::
`
` elOld
`
`"<:j'"
`
`0 ..--
`..--
`
`ec0ldd
`
`ro
`N
`0
`:::.:::
`0
`0..
`
`ey0eOdY
`
`ro
`"'-'"
`0
`("")
`u
`0
`0:::
`
`("')
`sir-
`.
`(9
`LL
`
`N
`0
`CV)
`..--
`
`"<:j'"
`0
`CV)
`..--
`
`N
`0
`
`~
`
`~
`Q)
`0
`">
`Q)
`0
`"'O
`·c
`..0
`:r:
`
`OOEL
`
`Page 14 of 29
`
`Page 14 of 29
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 13 of 15
`Sheet 13 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`....J
`
`<( z
`C,
`Cl)
`w
`....J
`l'.lJ
`
`
`
`TWNOISATEaVN3
`
`<( z
`w
`
`9071
`
`<.O
`0
`s;j""
`..--
`
`evOeOCH
`
`m
`-.::I"
`0
`("")
`u
`0
`0::::
`
`~
`~
`
`vbOls
`
`■
`
`(9
`LL
`
`qv0eOdy
`
`.0
`-.::I"
`0
`("")
`u
`0
`0::::
`
`EOLdd
`
`m
`N
`0
`::.:::
`0 a..
`
`s;j""
`
`0 ..--
`..--
`
`N
`0
`s;j""
`..--
`
`
`
`COLLS9lAeq
`
`N
`0 ...---
`...---
`Q)
`(..)
`">
`Q)
`0
`"'O
`·c
`..0
`:r:
`
`Oorl
`
`Page 15 of 29
`
`G20)4dd
`
`.0
`N
`0
`::.:::
`0 a..
`
`PHQAH
`
`Page 15 of 29
`
`

`

`U.S. Patent
`U.S. Patent
`
`Jun.13,2017
`Jun. 13, 2017
`
`Sheet 14 of 15
`Sheet 14 of 15
`
`US 9,679,289 Bl
`US 9,679,289 B1
`
`
`
`TWNOISAT8VNA
`
`....J
`<(
`z
`C,
`(f)
`w
`....J
`((l
`<(
`z
`w
`
`<D
`0
`I.()
`...----
`
`LO
`sir-
`
`SlSls
`
`■
`
`(9
`LL
`
`e2OlAdd UZOLdd
`
`OOS1
`
`N
`0 ...---
`...---
`Q)
`(.)
`">
`Q)
`0
`"O
`·c
`.0
`:r:
`
`s;:t
`0
`...----
`...----
`
`ro
`N
`0
`:::.:::
`0 n.
`
`("')
`
`ep0eOY
`
`ro
`""" 0
`u
`0 a:::
`
`G014dd
`
`.c
`N
`0
`:::.:::
`0 n.
`
`• • •
`
`C
`N
`0
`:::.:::
`0 n.
`
`Page 16 of 29
`
`Page 16 of 29
`
`

`

`\0 = """'
`
`00
`'N
`\0
`-....l
`O'I
`\0
`r.,;_
`d
`
`....
`....
`0
`Ul
`....
`.....
`rJJ =-
`
`('D
`('D
`
`Ul
`
`~
`
`~ = ~
`
`~
`~
`~
`
`.
`.
`e
`
`00
`
`0 ....
`....
`= ?
`
`--....J
`
`N
`~~
`
`1652
`
`I
`
`I ---
`
`RDC/Wi-Fi Service
`
`1600
`
`~ 7 ::: RDC 304b
`I
`
`__,___
`
`I
`
`I
`
`I ''t'
`
`1104
`
`POK 102a
`
`H~brid Device 1102b
`
`I
`
`'¥:
`
`I
`
`POK 102b
`
`FIG.16
`
`I I
`
`1616
`
`Personality Inheritance
`
`I
`
`I
`
`Feature Inheritance 1614
`
`/I
`
`I
`
`I
`
`'\.I
`
`Cell Account 2
`Credit Cart Acct. 2
`
`Service Inheritance 1612
`
`l"'-..1 Comp. B Access _.,, I I
`I
`I ~ /
`
`I I
`
`I
`
`I
`
`1606
`
`Personality Inheritance
`
`\
`
`1650
`
`Feature Inheritance I I
`
`1604
`
`I I "
`
`Comp. A Access
`
`Wi-Fi Access Acct
`Cell Account 1
`Credit Cart Acct. 1
`
`16il2
`
`Service Inheritance
`
`Page 17 of 29
`
`

`

`US 9,679,289 Bl
`
`1
`HYBRID DEVICE HAVING A PERSONAL
`DIGITAL KEY AND RECEIVER-DECODER
`CIRCUIT AND METHODS OF USE
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`5
`
`2
`accomplished, location tracking (i.e., knowledge about the
`location of an object or person) is generally useful. For
`example, location tracking information can be used to track
`inventory and trace the route of objects through various
`locations. It can be used for time and motion studies. If tags
`are attached to people, then tracking of people can be used
`to better understand their behavior. Knowledge about a
`person's location (and/or their past locations and projected
`future locations) could be used to provide better services to
`10 that person.
`However, most proximity systems and location tracking
`systems have limited capabilities. Typically, the proximity
`sensor, RFID tag or similar device is a dumb device, in the
`15 sense that the device is designed and has the capability only
`to report its location. For example, such devices typically do
`not have the capabilities to run different applications or to
`even interact with different applications. Furthermore, these
`systems typically are proprietary and narrowly tailored for a
`20 specific situation, thus preventing easy expandability to
`other situations or third party applications.
`
`SUMMARY
`
`pnonty under
`claims
`application
`present
`The
`35 U.S.C. §120 to U.S. patent application Ser. No. 14/677,
`893 entitled "Hybrid Device Having a Personal Digital Key
`and Receiver Decoder Circuit and Method of Use," filed
`Apr. 2, 2015, which claims priority under 35 U.S.C. § 120 to
`U.S. patent application Ser. No. 14/171,705 entitled "Hybrid
`Device Having a Personal Digital Key and Receiver
`Decoder Circuit and Method of Use," filed Feb. 3, 2014,
`now U.S. Pat. No. 9,049,188, which claims priority under 35
`U.S.C. §120 to U.S. patent application Ser. No. 13/445,825
`entitled "Hybrid Device Having a Personal Digital Key and
`Receiver Decoder Circuit and Method of Use," filed Apr. 12,
`2012, now U.S. Pat. No. 8,646,042, which claims priority
`under 35 U.S.C. §120 to U.S. patent application Ser. No.
`12/329,329 entitled "Hybrid Device Having a Personal
`Digital Key and Receiver Decoder Circuit and Method of
`Use," filed Dec. 5, 2008, now U.S. Pat. No. 8,171,528,
`which claims the benefit of priority under 35 U.S.C. § 119( e) 25
`of U.S. Provisional Application No. 60/992,953 entitled
`"Reverse Prox," filed on Dec. 6, 2007 by David L. Brown,
`John J. Giobbi and Fred S. Hirt. The entire contents of all of
`the foregoing are incorporated by reference herein.
`Applicants hereby notify the USPTO that the claims of the
`present application are different from those of the aforemen(cid:173)
`tioned related applications. Therefore, Applicant rescinds
`any disclaimer of claim scope made in the parent applica(cid:173)
`tion, grandparent application or any other predecessor appli(cid:173)
`cation in relation to the present application. The Examiner is
`therefore advised that any such disclaimer and the cited
`reference that it was made to avoid may need to be revisited
`at this time. Furthermore, the Examiner is also reminded that
`any disclaimer made in the present application should not be
`read into or against the parent application, the grandparent
`application or any other related application.
`
`Various drawbacks of the prior art are overcome by
`providing a hybrid device including a personal digital key
`(PDK) and a receiver-decoder circuit (RDC). The PDK and
`RDC of the hybrid device are coupled for communication
`with each other. In one embodiment, the hybrid device also
`30 provides a physical interconnect for connecting to other
`devices to send and receive control signals and data, and
`receive power. The hybrid device operates in one of several
`modes including, PDK only, RDC only, or PDK and RDC.
`This allows a variety of system configurations for mixed
`35 operation including: PDK/RDC, RDC/RDC or PDK/PDK.
`The present invention also includes a number of system
`configurations for use of the hybrid device including: use of
`the hybrid device in a cell phone; simultaneous use of the
`40 PDK and the RDC functionality of hybrid device; use of
`multiple links of hybrid device to generate an authorization
`signal, use of multiple PDK links to the hybrid device to
`generate an authorization signal; use of the hybrid device for
`authorization inheritance and use of the hybrid device for
`45 automatically disabling a service or feature.
`Other aspects of the invention include systems and com(cid:173)
`ponents corresponding to the above, and methods corre(cid:173)
`sponding to all of the foregoing.
`
`BACKGROUND
`
`1. Field of Art
`The invention generally relates to personal digital keys
`and corresponding sensors, capable of proximity detection/
`location determination and auxiliary data services/applica(cid:173)
`tion services. Still more particularly, the present invention
`relates to a hybrid device including a personal digital key 50
`(PDK) and a receiver-decoder circuit (RDC) and methods
`for using same.
`2. Description of the Related Art
`Proximity sensors and location tracking are technologies
`with many applications. For example, proximity sensors can 55
`be used to provide secure access to physical and/or digital
`assets, based on biometrics, passwords, PINs, or other types
`of authentication. Proximity sensors typically have advan(cid:173)
`tages of being less cumbersome, easier to use, and more
`flexible in form factor and implementation. Proximity sen- 60
`sors can be used to control access to resources and/or to
`authenticate individuals, for example.
`One possible application that can take advantage of
`proximity sensors is location tracking. RFID tracking is one
`example. In RFID, RFID tags are attached to objects to be 65
`tracked. RFID readers then interact with the RFID tags to
`determine the location of the tag. Regardless of how it is
`
`BRIEF DESCRIPTION OF THE FIGURES
`
`FIG. 1 is a block diagram illustrating one embodiment of
`a system according to the invention.
`FIG. 2 is a block diagram illustrating one embodiment of
`a Personal Digital Key (PDK).
`FIG. 3 is a block diagram illustrating one embodiment of
`a sensor.
`FIGS. 4-6 are block diagrams illustrating further embodi(cid:173)
`ments of systems according to the invention.
`FIG. 7 is a block diagram illustrating one embodiment of
`a system with networked sensors.
`FIGS. 8-9 are block diagrams illustrating operation of the
`system in FIG. 7.
`FIG. 10 is a diagram illustrating operation of the system
`in FIG. 7.
`FIG. 11 is a block diagram of one embodiment of a hybrid
`device in accordance with the present invention.
`
`Page 18 of 29
`
`

`

`US 9,679,289 Bl
`
`3
`FIG. 12 is a block diagram of one embodiment of a system
`in which the hybrid device is part of a cell phone in
`accordance with the present invention.
`FIG. 13 is a block diagram of one embodiment of a system
`using the PDK and the RDC functionality of hybrid device
`in accordance with the present invention.
`FIG. 14 is a block diagram of one embodiment of a system
`using the multiple links of hybrid device to generate an
`authorization signal in accordance with the present inven(cid:173)
`tion.
`FIG. 15 is a block diagram of one embodiment of a system
`using the multiple PDK links to the hybrid device to
`generate an authorization signal in accordance with the
`present invention.
`FIG. 16 is a block diagram of one embodiment of a system 15
`using the hybrid device for authorization inheritance in
`accordance with the present invention.
`The figures depict various embodiments of the present
`invention for purposes of illustration only. One skilled in the
`art will readily recognize from the following discussion that 20
`alternative embodiments of the structures and methods illus(cid:173)
`trated herein may be employed without departing from the
`principles of the invention described herein.
`
`10
`
`4
`also receive a biometric input 104 from the individual.
`Based on the received information, the sensor 108 deter(cid:173)
`mines if access to the application 120 should be granted. In
`this example, the system 100 provides authentication with(cid:173)
`out the need for PINs or passwords (although PINs and
`passwords may be used in other implementations). More(cid:173)
`over, personal biometric information need not be stored in
`any local or remote storage database and is only stored on
`the user's own PDK (in one embodiment).
`The credibility of the system 100 is ensured by the use of
`a PDK 102 that stores trusted information. The PDK 102 is
`a compact, portable uniquely identifiable wireless device
`typically carried by an individual. The PDK 102 stores
`digital information in a tamper-proof format that uniquely
`associates the PDK 102 with an individual. Example
`embodiments of PD Ks are described in more detail in U.S.
`patent application Ser. No. 11/292,330, entitled "Personal
`Digital Key And Receiver/Decoder Circuit System And
`Method" filed on Nov. 30, 2005; U.S. patent application Ser.
`No. 11/620,581 entitled "Wireless Network Synchronization
`Of Cells And Client Devices On A Network" filed on Jan. 5,
`2007; and U.S. patent application Ser. No. 11/620,577
`entitled "Dynamic Real-Time Tiered Client Access" filed on
`Jan. 5, 2007, the entire contents of which are all incorporated
`25 herein by reference.
`The sensor 108 wirelessly communicates with the PDK
`102 when the PDK 102 is within a proximity zone (i.e.,
`within a microcell) of the sensor 108. The proximity zone
`can be, for example, several meters in radius and preferably
`30 can be adjusted dynamically by the sensor 108. Thus, in
`contrast to many conventional RF ID devices, the sensor 108
`can detect and communicate with the PDK 102 without
`requiring the owner to remove the PDK 102 from his/her
`pocket, wallet, purse, etc. Generally, the sensor 108 receives
`uniquely identifying information from the PDK 102 and
`initiates an authentication process for the individual carrying
`the PDK 102. In one embodiment, the sensor 108 is adapted
`to receive a biometric input 104 from the individual. The
`biometric input 104 comprises a representation of physical
`or behavioral characteristics unique to the individual. For
`example, the biometric input 104 can include a fingerprint,
`a palm print, a retinal scan, an iris scan, a photograph, a
`signature, a voice sample or any other biometric information
`such as DNA, RNA or their derivatives that can uniquely
`45 identify the individual. The sensor 108 compares the bio(cid:173)
`metric input 104 to information received from the PDK 102
`to determine authentication. Alternatively, the biometric
`input 104 can be obtained by a biometric sensor on the PDK
`102 and transmitted to the sensor 108 for authentication. In
`50 additional alternative embodiment, some or all of the
`authentication process can be performed by the PDK 102
`instead of the sensor 108.
`In this example, the sensor 108 is further communica(cid:173)
`tively coupled to the network 110 in order to receive and/or
`transmit information to remote databases for remote authen(cid:173)
`tication. In an alternative embodiment, the sensor 108
`includes a non-volatile data storage that can be synchronized
`with one or more remote databases or registries. Such an
`embodiment alleviates the need for a continuous connection
`to the network 110 and allows the sensor 108 to operate in
`a standalone mode and for the local data storage to be
`updated when a connection is available. For example, a
`standalone sensor 108 can periodically download updated
`registry entries and perform authentication locally without
`65 any remote lookup.
`In yet another alternative, a standalone sensor 108 may
`have a pre-configured secure access key 118 and encryption
`
`DETAILED DESCRIPTION
`
`FIG. 1 is a high level block diagram illustrating a system
`for allowing access to multiple applications ( or services).
`The system 100 comprises a Personal Digital Key (PDK)
`102, a sensor 108, a network 110 and one or more applica(cid:173)
`tions 120 (including services). The sensor 108 is coupled to
`the PDK 102 by a wireless link 106 and coupled to a network
`110 by either a wired or wireless link. In this example, the
`applications 120 are also accessed over network 110. The
`sensor 108 is also adapted to receive a biometric input 104 35
`from a user and is capable of displaying status to a user. In
`alternative embodiments, different or additional resources
`and databases may be coupled to the network 110, including
`for example registries and databases used for validation or to
`check various registrations of the user. In another embodi- 40
`ment, the sensor 108 operates as a standalone device without
`a connection to the network 110.
`The PDK 102 includes multiple service blocks 112A-N as
`described in more detail in FIG. 2. Each service block 112
`is accessed using a corresponding service block access key
`118. In this example, the sensor 108 contains three of the
`service block access keys 118A, D, F. The service block
`access keys 118 allow the sensor 108 to unlock information
`stored in the corresponding service blocks 112, which infor(cid:173)
`mation is used as local secured information.
`In one example, a biometric is required in order to access
`specific service blocks 112 in the PDK 102. Verification of
`the biometric is achieved by using service block 112A. The
`sensor 108 stores the corresponding service block access key
`118A and uses this key to unlock the biometric service block 55
`112A, which stores a valid biometric. A current biometric is
`received using biometric input 104. The sensor 108 then
`verifies the stored biometric (from service block 112A)
`against the recently acquired biometric (from input 104).
`Upon proper verification, various applications 120 are per- 60
`mitted to connect to the PDK 102 via the sensor 108 and/or
`to gain access to other service blocks 112.
`The system 100 can be used to address applications 120
`where it is important to authenticate an individual for use.
`Generally, the sensor 108 wirelessly receives information
`stored in the PDK 102 that uniquely identifies the PDK 102
`and the individual carrying the PDK 102. The sensor 108 can
`
`Page 19 of 29
`
`

`

`US 9,679,289 Bl
`
`5
`algorithm, or a variable access key 118 that changes, for
`example based on time and sensor ID. One example appli(cid:173)
`cation would be a sensor 108 located in a hotel room door,
`where the sensor could constantly compute a different access
`key 118 based on time, and the PDK 102 could be associated
`with this key during the hotel registration process.
`The network 110 provides communication between the
`sensor 108 and various validation databases and/or regis(cid:173)
`tries, in addition to the applications 120. In one embodiment,
`the network 110 uses standard communications technologies
`and/or protocols. Thus, the network 110 can include links
`using technologies such as Ethernet, 802.11, 802.16, inte(cid:173)
`grated services digital network (ISDN), digital subscriber
`line (DSL), asynchronous transfer mode (ATM), etc. Simi(cid:173)
`larly, the networking protocols used on the network 110 can
`include the transmission control protocol/Internet protocol
`(TCP/IP), the hypertext transport protocol (HTTP), the
`simple mail transfer protocol (SMTP), the file transfer
`protocol (FTP), etc. The data exchanged over the network
`110 can be represented using technologies and/or formats
`including the hypertext markup language (HTML), the
`extensible markup language (XML), etc. In addition, all or
`some of links can be encrypted using conventional encryp(cid:173)
`tion technologies such as the secure sockets layer (SSL),
`Secure HTTP and/or virtual private networks (VPNs). In 25
`another embodiment, the entities can use custom and/or
`dedicated data communications technologies instead of, or
`in addition to, the ones described above.
`In one aspect, the sensor 108 may connect to a validation
`database that stores additional information that may be used
`for authorizing a transaction to be processed at the sensor.
`For example, in purchase transactions, the sensor 108 may
`interact with a credit card validation database that is separate
`from the merchant providing the sale. Alternatively, a dif(cid:173)
`ferent database may be used to validate different types of
`purchasing means such as a debit card, ATM card, or bank
`account number.
`In another aspect, the sensor 108 may connect to various
`registries that store, among other items, PDK, notary, and/or
`sensor information. In one embodiment, a registry stores
`biometric or other types of information in an encoded format
`that can only be recovered using an algorithm or encoding
`key stored in the PDK. Information stored in the registries
`can be accessed by the sensor 108 via the network 110 for
`use in the authentication process. Two basic types of regis- 45
`tries are private registries and a Central Registry. Private
`registries are generally established and administered by their
`controlling entities ( e.g., a merchant, business authority, or
`other entity administering authentication). Private registries
`can be custom configured to meet the specialized and 50
`independent needs of each controlling entity. A Central
`Registry is a highly-secured, centrally-located database
`administered by a trusted third-party organization. In one
`embodiment, all PDKs 102 are registered with the Central
`Registry and may be optionally registered with one or more 55
`selected private registries. In alternative embodiments, a
`different number or different types of registries may be
`coupled to the network 110.
`The service blocks 112 can be used for purposes other
`than user authentication. For example, information used or 60
`produced by an application 120 can be transferred back and
`forth to the corresponding service block 112. That is, each
`service block 112 can be used as a local secure memory for
`the corresponding application 120. Thus, a service 120B
`may store certain sensitive information in service block 65
`112B, and a separate service 120C will not be able to access
`that information without the corresponding access key 118B.
`
`6
`In this example, the sensor 108 only holds access keys 118A,
`D, F and does not hold access key 118B. The application
`120B may hold the access key 118B, thus allowing it to
`access service block 112B but preventing application 120C
`from accessing the service block 112B. Note that this
`implementation would also prevent the sensor 108 acting
`alone from accessing the service block 112B.
`Turning now to FIG. 2, an example embodiment of a PDK
`102 is illustrated. The PDK 102 comprises a memory 210,
`10 control logic 250, wireless application 260 and a transceiver
`270. The PDK 102 can be standalone as a portable, physical
`device or can be integrated into commonly carried items. For
`example, a PDK 102 can be integrated into a portable
`electronic device such as a cell phone, Personal Digital
`15 Assistant (PDA), or GPS unit, an employee identification
`tag, clothing, or jewelry items such as watches, rings,
`necklaces or bracelets. In one embodiment, the PD K 102 can
`be, for example, about the size of a Subscriber Identity
`Module (SIM) card and be as small as a square inch in area
`20 or less. In another embodiment, the PDK 102 can be easily
`contained in a pocket, on a keychain, or in a wallet. The
`PDK can also contain other components not shown, for
`example various other inputs, outputs and/or interfaces
`(serial or parallel).
`The memory 210 can be a read-only memory, a once-
`programmable memory, a read/write memory or any com(cid:173)
`bination of memory types, including physical access secured
`and tamperproof memories. The memory 210 typically
`stores a unique PDK ID 212. The PDK ID 212 comprises a
`30 public section and a private section of information, each of
`which can be used for identification and authentication. In
`one embodiment, the PDK ID 212 is stored in a read-only
`format that cannot be changed subsequent to manufacture.
`The PDK ID 212 is used as an identifying feature of a PDK
`35 102 and distinguishes between PDKs 102 in private or
`Central registry entries. In an alternative embodiment, the
`registries can identify a PDK 102 by a different ID than the
`PDK ID 212 stored in the PDK 102, or may use both the
`PDK ID 212 and the different ID in conjunction. The PDK
`40 ID 212 can also be used in basic PDK authentication to
`ensure that the PDK 102 is a valid device.
`The memory 210 also stores the various service blocks
`112A-N. Whether a particular service block 112 is stored in
`volatile or non-volatile memory may be determined by the
`specific application. In one approach, the original issuer of
`the PDK defines how the internal memory 210 may be used
`for service b