US010073960B1
`
`US 10,073,960 B1
`(10) Patent No.:
`a2) United States Patent
`Brown
`(45) Date of Patent:
`*Sep. 11, 2018
`
`
`(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)
`
`HO4L 63/0861 (2013.01); HO4L 63/10
`(2013.01); HO4L 67/10 (2013.01); Ho4aw
`4/029 (2018.02); HO4AW 4/80 (2018.02);
`HOW 12/06(2013.01); HO4W 12/08
`(2013.01)
`(58) Field of Classification Search
`USPC iececescsseecesessssescnesensssescenssanscneeesensensees 726/3
`
`(73) Assignee: Proxense, LLC, Bend, OR (US)
`
`See application file for complete search history.
`
`(*) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`This patent is subject to a terminal dis-
`claimer.
`
`5,623,552 A
`6,325,285 B1
`
`4/1997 Lane
`12/2001 Baratelli
`(Continued)
`Primary Examiner — David J Pearson
`(21) Appl. No.: 15/595,739
`(74) Attorney, Agent, or Firm — Patent Law Works LLP
`(22)
`Filed:
`May15, 2017
`(57)
`ABSTRACT
`Related U.S. Application Data
`—_A hybrid device includes a personal digital key (PDK) and
`(63) Continuation of application No. 14/961,645,filed on
`a receiver-decodercircuit (RDC). The PDK and RDCofthe
`Dec. 7, 2015, now Pat. No. 9,679,289, which is a
`hybrid device are coupled for communication with each
`continuation of application No. 14/677,893, filed on
`other. In one embodiment, the hybrid device also provides a
`Apr. 2, 2015, now Pat. No. 9,235,700, which is a
`continuation of application No. 14/171,705, filed on—_physical interconnect for connectingto other devices to send
`(Continued)
`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-
`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-
`rization inheritance.
`
`(51)
`
`Int. Cl.
`HO4L 29/06
`GO6F 21/32
`GO6F 21/35
`HO4W 12/06
`HO4W 12/08
`HO4L 29/08
`HO4W 4/029
`HO4W 4/80
`(52) U.S. Cl.
`CPC vices G06F 21/32 (2013.01); GO6F 21/35
`(2013.01); HO4E 63/0492 (2013.01); HO4L
`63/08 (2013.01); HO4E 63/0853 (2013.01);
`
`(2006.01)
`(2013.01)
`(2013.01)
`(2009.01)
`(2009.01)
`(2006.01)
`(2018.01)
`(2018.01)
`
`1200
`
`\
`
`
`SIM Card
` 1206
`
`
`PDK 1026
`
`
`20 Claims, 15 Drawing Sheets
`
`
`
`Cell Phone 1202
`
`Cell Phone
`nNS&
`
`
`
`
`
`Components & Battery
`
`
`PDK 1024
`
`4102
`
`Page 1 of 29
`
`GOOGLE EXHIBIT1001
`
`GOOGLE EXHIBIT 1001
`
`Page 1 of 29
`
`

`

`US 10,073,960 B1
`Page 2
`
`Related U.S. Application Data
`
`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.
`
`(60) Provisional application No. 60/992,953, filed on Dec.
`6, 2007.
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`6,728,397 B2
`6,879,966 Bl
`7,159,765 B2
`7,231,068 B2
`
`4/2004 McNeal
`4/2005 Lapsley etal.
`1/2007 Frerking
`6/2007 Tibor
`
`7,314,164
`7,349,557
`7,565,329
`8,171,528
`8,646,042
`8,678,273
`8,856,539
`9,049,188
`9,235,700
`2004/0254837
`2005/0116020
`2006/0113381
`
`Al*
`
`1/2008
`3/2008
`7/2009
`5/2012
`2/2014
`3/2014
`10/2014
`6/2015
`1/2016
`12/2004
`6/2005
`6/2006
`
`2006/0208066
`
`Al*
`
`9/2006
`
`2007/027 1194
`
`Al*
`
`11/2007
`
`Bonalle et al.
`Tibor
`Lapsley et al.
`Brown
`Brown
`McNeal
`Weiss
`Brown
`Brown
`Roshkoff
`Smoluchaet al.
`Hochstein .......... G06K 19/0718
`235/382
`FINN oe ceeeeeeeeeees G06K 7/0004
`235/380
`Walker voces G06Q 30/02
`705/80
`
`* cited by examiner
`
`Page 2 of 29
`
`Page 2 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 1 of 15
`
`US 10,073,960 B1
`
`|Sls
`
`
`
`yOZ|uoneoiddy
`
`90}Josuas
`
`SOU}aWOlg
`
`vOl
`
`
`
`cOldd
`
`90S
`
`YVelbud
`
`debt
`
`cht
`
`Page 3 of 29
`
`Page 3 of 29
`
`
`
`

`

`01ZAiowayy
`
`:
`pz }dAsaqadAioug
`
`ZS J0}99|8S
`
`¢Old
`
`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 2 of 15
`
`US 10,073,960 B1
`
`JOAIQOSUL|
`
`0L¢
`
`uogeoyddy
`
`09¢
`
`SSOIOIIMA
`i9¢
`
`E98SaS
`
`cOLdd
`
`0IN8S
`
`Page 4 of 29
`
`Page 4 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 3 of 15
`
`US 10,073,960 B1
`
`JOMIONOMEN
`
` (SNESOdO/||80€OlSOPL9}U|
`
`
`JO.UODZLE
`|old|
`
`
`
`90]Josues
`
`Page 5 of 29
`
`OUJaWOIg
`
`(s)sapeay
`
`COE
`
`JOSS90014
`
`90€
`
`Page 5 of 29
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 4 of 15
`
`US 10,073,960 B1
`
`uoneoiddy
`
`Oc
`
`Kaysseooy
`
`dsb
`
`Ssa00y
`
`VELLAey
`
`vols
`
`cOl4dd
`
`
`
`OLSBdIN9qSUOJEPUEIS/Od
`
`
`
`QQ)Josues
`
`9919S
`
`Vell4d
`
`acl}
`
`Och
`
`Page 6 of 29
`
`Page 6 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 5 of 15
`
`US 10,073,960 B1
`
`
`
`SOASJBUIA]XYZG801INO]POYOMJON/DdQQ}Josuag
`
`
`
`
`
`Auojeayddy
`
`uoneoyddy
`
`Kayssaooy
`
`agit
`
`GOld
`
`COLMd
`
`B01
`
`YcoLbWd
`
`geht
`
`ell
`
`Page 7 of 29
`
`Page 7 of 29
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 6 of 15
`
`US 10,073,960 B1
`
`LZ0Z1ddy
`
`V8LLAay
`
`éZ01S
`
`2Z02}ddy
`
`agL1Aey
`
`€ZO0LS
`
`€ZOZ)ddy
`
`agit.Aey
`
`ddy
`
`LAOZL
`
`9Old
`
`cOL4d
`
`B0IM8S
`
`Velbod
`
`gebh
`
`Och
`
`XOZbddy
`
`O8t|Aey
`
`MOLS
`
`Moz!ddy
`
`O81)Aey
`
`AQLS
`
`Adz)ddy
`
`O81}Aey
`
`Page 8 of 29
`
`Page 8 of 29
`
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 7 of 15
`
`US 10,073,960 B1
`
`:eees
`mH7
`Unit a FIG.7
`
`
`od=
`2[a3]oS
`
`= £a
`
`=z
`RemoteApps
`Zz a5)Cc—
`
`we—
`Oo
`2®
`
`£S
`ea)
`
`°e
`
` >
`
`<2=o
`
`oO
`CoSo
`NS
`Si
`=
`om
`MM
`720E
`S9°
`SS}|ia
`wa
`oS
`qm
`rc
`°—
`|
`®
`o
`<<
`=
`
`Page 9 of 29
`
`
`
`8 =
`=O
`Su
`Sr
`oO
`
` =
`
`=
`a
`Cc
`—
`
`Page 9 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 8 of 15
`
`US 10,073,960 B1
`
`
`
`
`FIG. 8
`
`FIG. 9
`
`Page 10 of 29
`
`Page 10 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 9 of 15
`
`US 10,073,960 B1
`
`JOSOLOL
`
`
`
`|uoyngsasseud
`
`|uoyNq
`
`OP0L pededsip
`sie919Wd0901(sualOu)WHO.
`[IOSUdS|JOJEUIPIOOWS}!§=—[_uoqeorddy]
`|Ob'Ols
`|Leerht|LvOe0hY0S0|
`
`gJe9}9JoyeJadQ
`
`jsenbeu
`
`
`
`BIIMESOCOL
`
`
`
`(|uoyng)yee
`
`Page 11 of 29
`
`Page 11 of 29
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 10 of 15
`
`US 10,073,960 B1
`
`lu
`
`i ©_Ei
`
`on
`
`FIG.11
`
`Page 12 of 29
`
`Page 12 of 29
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 11 of 15
`
`US 10,073,960 B1
`
`BOLNd
`
`cLOld
`
`Bp0eO0Yq201¥dd
`
`Asayyeg9sjuauodwoy
`
`
`
`auoud[18D
`
`
`
`
`
`COC)SU0UdI|8D
`
`pledWIS
`
`9021
`
`00z1
`
`Page 13 of 29
`
`Page 13 of 29
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 12 of 15
`
`US 10,073,960 B1
`
`qvoeOdd
`
`eZOLWdd
`
`ev0€OGY
`
`elOld
`
`OOEL
`
`Page 14 of 29
`
`Page 14 of 29
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 13 of 15
`
`US 10,073,960 B1
`
`qv0€Ody
`
`e201Ndd
`
`
`
`WNOISATEVNA
`
`vlOld
`
`eVOEOY
`
`42014dd
`
`OOrL
`
`Page 15 of 29
`
`Page 15 of 29
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 14 of 15
`
`US 10,073,960 B1
`
`OSL
`
`
`
`WNOISF1EVNA
`
`GbOld
`
`
`
`e201Wd2051
`
`/i\
`
`G20lWad
`
`ep0eOGYUZOL4Qd
`AXf40aEa
`
`vost
`
`Page 16 of 29
`
`Page 16 of 29
`
`
`
`

`

`U.S. Patent
`
`Sep. 11, 2018
`
`Sheet 15 of 15
`
`US 10,073,960 B1
`
`0091
`
`Q0EOGY
`
`
`
`BdIMOSI4-IMW/OdY
`
`9}Sls
`
`
`G20}1891A8qPLGAH
`SNES{sssooygduos
`
`[189ZyoyWepaoZO)SOURTTOUUTSSINIES
`Zyunoooy
`
`epoeDdY
`
`ez0bHdd
`
` PLOTSUESYUT
`
`JOOSSeo0yI-AA|juNosSY
`
`1199LpoyMeOWpeu9
`
`sseo0yyWdwo9
`
`AZOL4d
`
`Page 17 of 29
`
`Page 17 of 29
`
`
`
`

`

`US 10,073,960 B1
`
`1
`HYBRID DEVICE HAVING A PERSONAL
`DIGITAL KEY AND RECEIVER-DECODER
`CIRCUIT AND METHODS OF USE
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`The present application is a continuation and claims
`priority to U.S. application Ser. No. 14/961,645, entitled
`“Hybrid Device Having a Personal Digital Key and
`Receiver-Decoder Circuit and Methods of Use,” filed Dec.
`7, 2015, which claimspriority under 35 U.S.C. § 120 to US.
`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 claimspriority 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 Cir-
`cuit and Methodof Use,”filed Feb. 3, 2014, now U.S. Pat.
`No. 9,049,188, which claimspriority 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
`US.C. § 120 to US. patent application Ser. No. 12/329,329
`entitled “Hybrid Device Having a Personal Digital Key and
`Receiver Decoder Circuit and Methodof 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) 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 thatthe claimsof the
`present application are different from those of the aforemen-
`tioned related applications. Therefore, Applicant rescinds
`any disclaimer of claim scope made in the parent applica-
`tion, grandparent application or any other predecessor appli-
`cation in relation to the present application. The Examineris
`therefore advised that any such disclaimer and the cited
`reference that it was made to avoid may needto berevisited
`at this time. Furthermore, the Examineris also remindedthat
`any disclaimer madein the present application should not be
`read into or against the parent application, the grandparent
`application or any other related application.
`
`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-
`tion services. Still more particularly, the present invention
`relates to a hybrid device including a personal digital key
`(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 manyapplications. For example, proximity sensors can
`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-
`tages of being less cumbersome, easier to use, and more
`flexible in form factor and implementation. Proximity sen-
`Page 18 of 29
`
`2
`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
`tracked. RFID readers then interact with the RFID tags to
`determine the location of the tag. Regardless of how it is
`accomplished, location tracking (i.e., knowledge about the
`location of an object or person) is generally useful. For
`example, location tracking information can be usedto 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
`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
`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
`systemstypically are proprietary and narrowlytailored for a
`specific situation,
`thus preventing easy expandability to
`other situations or third party applications.
`
`SUMMARY
`
`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
`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
`modesincluding, PDK only, RDC only, or PDK and RDC.
`This allows a variety of system configurations for mixed
`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
`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
`automatically disabling a service or feature.
`Other aspects of the invention include systems and com-
`ponents corresponding to the above, and methods corre-
`sponding to all of the foregoing.
`
`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 diagramsillustrating further embodi-
`ments of systems according to the invention.
`FIG.7 is a block diagram illustrating one embodiment of
`a system with networked sensors.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Page 18 of 29
`
`

`

`US 10,073,960 B1
`
`3
`FIGS. 8-9 are block diagramsillustrating 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 embodimentof a hybrid
`device in accordance with the present invention.
`FIG.12 is a block diagram of one embodimentof 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 embodimentof 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 embodimentof a system
`using the multiple links of hybrid device to generate an
`authorization signal in accordance with the present inven-
`tion.
`
`FIG.15 is a block diagram of one embodimentof 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 embodimentof a system
`using the hybrid device for authorization inheritance in
`accordance with the present invention.
`The figures depict various embodiments of the present
`invention for purposesofillustration only. One skilled in the
`art will readily recognize from the following discussion that
`alternative embodiments of the structures and methodsillus-
`
`10
`
`20
`
`trated herein may be employed without departing from the
`principles of the invention described herein.
`
`30
`
`DETAILED DESCRIPTION
`
`40
`
`45
`
`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-
`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
`from a user and is capable of displaying status to a user. In
`alternative embodiments, different or additional resources
`and databases may be coupledto the network 110, including
`for example registries and databases used for validation or to
`check various registrations of the user. In another embodi-
`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-
`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 anduses this key to unlock the biometric service block
`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 properverification, various applications 120 are per-
`Page 19 of 29
`
`4
`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
`also receive a biometric input 104 from the individual.
`Based on the received information, the sensor 108 deter-
`minesif access to the application 120 should be granted. In
`this example, the system 100 provides authentication with-
`out the need for PINs or passwords (although PINs and
`passwords may be used in other implementations). More-
`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 102is
`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 PDKsare 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
`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
`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, RNAortheir derivatives that can uniquely
`identify the individual. The sensor 108 compares the bio-
`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
`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-
`tively coupled to the network 110 in order to receive and/or
`transmit information to remote databases for remote authen-
`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
`embodimentalleviates the need for a continuous connection
`
`to the network 110 and allows the sensor 108 to operate in
`
`Page 19 of 29
`
`

`

`US 10,073,960 B1
`
`5
`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
`any remote lookup.
`In yet another alternative, a standalone sensor 108 may
`have a pre-configured secure access key 118 and encryption
`algorithm, or a variable access key 118 that changes, for
`example based on time and sensor ID. One example appli-
`cation would be a sensor 108 located in a hotel room door,
`wherethe 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-
`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-
`grated services digital network (ISDN), digital subscriber
`line (DSL), asynchronous transfer mode (ATM), etc. Simi-
`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-
`tion technologies such as the secure sockets layer (SSL),
`Secure HTTP and/or virtual private networks (VPNs). In
`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 connectto 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-
`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-
`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
`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
`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
`Page 20 of 29
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`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
`112B, and a separate service 120C will not be able to access
`that information without the corresponding access key 118B.
`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 nowto FIG. 2, an example embodiment of a PDK
`102 is illustrated. The PDK 102 comprises a memory 210,
`control logic 250, wireless application 260 and a transceiver
`270. The PDK 102 can be standaloneas a portable, physical
`device or can be integrated into commonlycarried items. For
`example, a PDK 102 can be integrated into a portable
`electronic device such as a cell phone, Personal Digital
`Assistant (PDA), or GPS unit, an employee identification
`tag, clothing, or jewelry items such as watches, rings,
`necklacesor bracelets. In one embodiment, the PDK 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
`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-
`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
`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
`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
`PDKID 212 andthe different ID in conjunction. The PDK
`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. Whethera 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 PDKdefines how the internal memory 210 may be used
`for service blocks 112. In some cases, the issuer may choose
`to only allow their service blocks to be stored, in which case
`third party applications will not be able to store service
`blocks in memory 210. In other cases, the issuer may allow
`any third party service 120 to use available service blocks
`112. Ifa new service block is created, then memory for that
`service block is allocated. The specific location of the
`service block and generation of the corresponding service
`block access key can be handled by the PDK 102, or can be
`handled via an external service.
`
`Regardless of how created, once created, external appli-
`cations (such as applications 120 in FIG. 1) can gain access
`to a specific service block 112 by proving the corresponding
`access key 118. In FIG. 2, this is shown conceptually by
`
`Page 20 of 29
`
`

`

`US 10,073,960 B1
`
`7
`control logic 250. The wireless application 260 on the PDK
`102 communicates to the sensor (not shown in FIG. 2) via
`transceiver 270. The wireless application provides a service
`block select 226 and a service block access key 118 in order
`to store, retrieve and/or modify data in a service block 112.
`The selector 252 selects a service block 112 based on the
`select signal 226 and the access key 118. The encryption
`engine 254 encrypts/decrypts data 228 flowing to/from the
`service block 112 based on the access key 118 (or some other
`key generated based on the access key, for example a session
`key). In an alternate method, the service block 112 may be
`selected based on the service block access key 118, elimi-
`nating the need for a separate select signal 226.
`The PDK 102 may also include other data and applica-
`tions. For example,
`the PDK 102 typically will
`include
`various profiles. Many different types of profiles are pos-
`sible. A biometric profile, for example, includes profile data
`representing physical and/or behavioral information that can
`uniquely identify the PDK owner. A PDK 102 can store
`multiple biometric profiles, each comprising a different type
`of biometric information. The same biometric information
`
`can also be stored multiple times in a PDK 102. For
`example, two different applications may use the right index
`fingerprint, and that biometric information may be stored in
`two different service blocks, one for each application. In
`addition, the PDK 102 mayalso store one or more biometric
`profile “samples” associated with each biometric profile.
`Profiles may also store one or more PINs or passwords
`associated with the PDK owner, or one or more pictures of
`the PDK owner. A profile can further include personal
`identification information such as name, address, phone
`number, etc., bank information, credit/debit card informa-
`tion, or membership information. This information can be
`useful for transactions.
`The transceiver 270 is a wireless transmitter and receiver
`
`for wirelessly communicating with a sensor 108 or other
`wireless device. The transceiver 270 can send and receive
`data as modulated electromagnetic signals. Moreover, the
`data can be encrypted by the transceiver 270 and transmitted
`over a secure link. Further, the transceiver 270 can actively
`send connection requests, or can passively detect connection
`requests from another wireless source. In one embodiment,
`the transceiver 270 is adapted to communicate over a range
`of up to around 5 meters.
`In another embodiment,
`the
`transceiver 270 range can be varied.
`Turing now to FIG. 3, an example embodiment of a
`sensor 108 is illustrated. The embodiment includes one or
`more biometric readers 302, a receiver-decoder circuit
`(RDC) 304, a processor 306, a network interface 308 and an
`I/O port 312. In alternative embodiments, different or addi-
`tional modules can be included in the sensor 108.
`The RDC 304 provides the wireless interface to the PDK
`102. Generally, the RDC 304 wirelessly receives data from
`the PDK 102 in an encrypted format and decodes the
`encrypted data for processing by the processor 306. An
`example embodiment of an RDCis described in U.S. patent
`application Ser. No. 11/292,330 entitled “Personal Digital
`Key And Receiver/Decoder Circuit System And Method,”
`the entire contents of which are incorporated herein by
`reference. Encrypting data transmitted between the PDK
`102 and sensor 108 minimizes the possibility of eavesdrop-
`ping or other fraudulent activity. In one embodiment, the
`RDC 304is also configured to transmit and receive certain
`types of information in an unencrypted, or public, format.
`The biometric reader 302 receives and processes the
`biometric input 104 from an individual. In one embodiment,
`the biometric reader 302 is a fingerprint scanner. Other
`Page 21 of 29
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`embodiments of biometric readers 302 include retinal scan-
`ners,
`iris scanners, facial scanner, palm scanners, DNA/
`RNAanalyzers, signature analyzers, cameras, microphones,
`and voice analyzers. Furthermore,
`the sensor 108 can
`include multipl