PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection ofinformation unless it contains a valid OMB control number.
`
` .
`
`
`. Attorney Docket Number|10001-04293 US
`
`Application Data Sheet 37 CFR 1.76
`
`
`
`Application Number
`
`
`
`
`
`Title of Invention
`
`Hybrid Device Having a Personal Digital Key and Receiver-DecocerCircuit and Methods of Use
`
`The application data sheetis part of the provisional or nonprovisional application for whichit is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paper filed application.
`
`Secrecy Order 37 CFR 5.2
`Oo Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuantto
`37 CFR 5.2 (Paperfilers only. Applications that fall under Secrecy Order may notbe filed electronically.}
`
`Inventor Information:
`
`
`Inventor
`Legal Name
`
`
`1
`
`Prefix) Given Name
`
`Middle Name
`
`Family Name
`
`Suffix
`
`
`Residence Information (Select One)
`(e) US Residency
`©) NonUS Residency
`() Active US Military Service
`
`Mailing Addressof Inventor:
`
`Address 1
`
`Address 2
`
`c/o Proxense, LLC
`
`689 NW Stonepine Drive
`
`Postal Code
`
`97701
`
`US
`
`Inventor Information blocks may be
`Inventors Must Be Listed - Additional
`All
`generated within this form by selecting the Add button.
`
`Add
`
`CorrespondenceInformation:
`Enter either Customer Number or complete the CorrespondenceInformation section below.
`Forfurther information see 37 CFR 1.33({a).
`
`[|An Addressis being provided for the correspondence Information of this application.
`
` Customer Number
`
`Email Address
`
`docketing@patentlawworks.net
`
`Add Ema
`
`
`
`Application Information:
`
`Title of the Invention
`Hybrid Device Having a Personal Digital Key and Receiver-Decoder Circuit and Methods of Use
`Attorney Docket Number] 10001-04293US_ Small Entity Status Claimed
`Application Type
`Nonprovisional
`
`Subject Matter
`
`Utility
`
`Total Numberof Drawing Sheets (if any)
`
`Suggested Figure for Publication {if any)
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 1
`
`
`
`
`
`
`
`Petitioner’s Ex. 1002, Page 1
`
`

`

`PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
` Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number|10001-04293 US
`
`
`
`Title of Invention
`Hybrid Device Having a Personal Digital Key and Receiver-Decoder Circuit and Methods of Use
`
`
`Application Number
`
`
`
`Publication Information:
`
`[_] Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`
`Request Not to Publish. | hereby requestthat the attached application not be published under
`35 U.S.C. 122(b} and certify that the invention disclosed in the attached application has not and will not be the
`subject of an application filed in another country, or under a multilateral international agreement, that requires
`publication at eighteen monthsafterfiling.
`
`
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`Either enter Customer Number or complete the Representative Name section below.
`If both sections are completed the customer
`Numberwill be used for the Representative Information during processing.
`
`
`
`©) Limited Recognition (37 CFR 11.9)
`
`Please Select One:
`Customer Number
`
`(#) Customer Number
`89194
`
`(©) US PatentPractitioner
`
`Domestic Benefit/National Stage Information:
`This section allowsfor the applicant to either claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c) or indicate National Stage
`entry from a PCT application. Providing this information in the application data sheet constitutes the specific reference required
`by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78.
`Whenreferring to the current application, please leave the application numberblank.
`
`Prior Application Status
`
`Application Number
`
`Filing Date (YYYY-MM-DD)
`
`Prior Application Status
`Application
`Number
`13445825
`
`a
`Continuity Type
`Continuation of
`
`Prior Application
`Number
`12329329
`
`Filing Date
`(YYYY-MM-DD)
`2008-12-05
`
`
`
`
`
`
`
`
`
`Patent Number
`8171528
`
`Issue Date
`(YYYY-MM-DD)
`2012-05-01
`
`Prior Application Status|Expired
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`12329329
`Claims benefit of provisional
`60992953
`Additional Domestic Benefit/National Stage Data may be generated within this form
`by selecting the Add button.
`
`Filing Date (YYYY-MM-DD}
`
`2007-12-06
`Add
`
`Foreign Priority Information:
`
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 2
`
`Petitioner’s Ex. 1002, Page 2
`
`

`

`
`
`This section allows for the applicant to claim priority to a foreign application. Providing this information in the application data sheet
`constitutes the claim for priority as required by 35 U.S.C. 119{b) and 37 CFR 1.55(d). Whenpriority is claimed to a foreign application
`thatis eligible for retrieval under the priority document exchange program (PDX) 'the information will be used by the Office to
`automatically attempt retrieval pursuant to 37 CFR 1.55(h){1) and (2). Under the PDX program, applicant bears the ultimate
`responsibility for ensuring that a copy of the foreign application is received by the Office from the participating foreign intellectual
`property office, or a certified copy of the foreign priority application is filed, within the time period specified in 37 CFR 1.55(g){1).
`
`[Remove|
`Application Number
`Country i
`Filing Date (YYYY-MM-DD)
`Access Code! (if applicable)
`
`
`
`
`
`
`
`PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`
`Attorney Docket Number|10001-04293 US
`
`Application Data Sheet 37 CFR 1.76
`
`Application Number
`
`
`Title of Invention
`Hybrid Device Having a Personal Digital Key and Receiver-Decoder Circuit and Methods of Use
`
`
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`
`Add
`
`Statement under 37 CFR 1.55 or 1.78 for AIA (First Inventor to File) Transition
`Applications
`
`
`This application (1) claims priority to or the benefit of an application filed before March 16, 2013 and (2) also
`contains, or contained at any time, a claim to a claimed invention that has an effective filing date on or after March
`[] 16, 2013.
`NOTE: By providing this statement under 37 CFR 1.55 or 1.78, this application, with a filing date on or after March
`16, 2013, will be examined underthefirst inventorto file provisions of the AIA.
`
`
`
`
`
`Authorization to Permit Access:
`
`[] Authorization to Permit Access to the Instant Application by the Participating Offices
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 3
`
`Petitioner’s Ex. 1002, Page 3
`
`

`

`PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
` Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number|10001-04293 US
`
`
`
`Title of Invention
`Hybrid Device Having a Personal Digital Key and Receiver-Decoder Circuit and Methods of Use
`
`
`Application Number
`
`If checked, the undersigned hereby grants the USPTO authority to provide the European Patent Office (EPO),
`the Japan Patent Office (JP©), the Korean Intellectual Property Office {(KIPO), the World Intellectual Property Office (WIPO),
`and any otherintellectual property offices in which a foreign application claiming priority to the instant patent application
`is filed access to the instant patent application. See 37 CFR 1.14(c) and (h). This box should not be checkedif the applicant
`does not wish the EPO, JPO, KIPO, WIPO, or otherintellectual property office in which a foreign application claiming priority
`to the instant patent application is filed to have accessto the instant patent application.
`
`In accordance with 37 CFR 1.14(h)(3), access will be provided to a copy of the instant patent application with respect
`to: 1) the instant patent application-as-filed; 2) any foreign application to which the instant patent application
`claims priority under 35 U.S.C. 119(a)-{c) if a copy of the foreign application that satisfies the certified copy requirement of
`37 CFR 1.55 has beenfiled in the instant patent application; and 3) any U.S. application-as-filed from which benefit is
`soughtin the instant patent application.
`
`In accordance with 37 CFR 1.14{c}, access may be provided to information concerning the date offiling this Authorization.
`
`Applicant Information:
`
`Providing assignment information in this section does not substitute for compliance with any requirement of part 3 of Title 37 of CFR
`to have an assignment recorded by the Office.
`
`1
`Applicant
`If the applicant is the inventor (or the remaining joint inventor or inventors under 37 CFR 1.45), this section should not be completed.
`The information to be provided in this section is the name and addressof the legal representative who is the applicant under 37 CFR
`1.43; or the name and addressof the assignee, person to whom theinventor is under an obligation to assign the invention, or person
`who otherwise showssufficient proprietary interest in the matter who is the applicant under 37 CFR 1.46. If the applicantis an
`applicant under 3? CFR 1.46 {assignee, person to whom the inventoris obligated to assign, or person who otherwise showssufficient
`proprietary interest) together with one or morejoint inventors, then the joint inventor or inventors who are also the applicant should be
`identified in this section.
`
`
`
`
`
`
`
`
`©)_Joint Inventor (e) Assignee
`OQ Legal Representative under 35 U.S.C. 117
`
`
`
` OC Person to whom theinventoris obligated to assign. Cc) Person who shows sufficient proprietary interest
`If applicant is the legal representative, indicate the authority to file the patent application, the inventor is:
`
`
`Nameof the Deceased or Legally Incapacitated Inventorfo
`
`
`If the Applicant is an Organization check here.
`OrganizationName|pbroxense, LLC
`
`Mailing Address Information:
`
`Address 1
`
`Address 2
`
`689 NW Stonepine Drive
`
`Phone Number
`
`Fax Number
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 4
`
`Petitioner’s Ex. 1002, Page 4
`
`

`

`PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
` Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number|10001-04293 US
`
`
`
`Title of Invention
`Hybrid Device Having a Personal Digital Key and Receiver-Decoder Circuit and Methods of Use
`
`Email Address
`
`Application Number
`
`
`
`
`
`Additional Applicant Data may be generated within this form by selecting the Add button.
`
`Add
`
`Assignee Information including Non-Applicant Assignee Information:
`
`Providing assignmentinformation in this section does not subsitute for compliance with any requirementof part 3 of Title 37 of CFR to
`have an assignmentrecordedby the Office.
`
`Assignee
`
`1
`
`Complete this section if assignee information, including non-applicant assignee information, is desired to be included on the patent
`application publication . An assignee-applicant identified in the "Applicant Information" section will appear on the patent application
`publication as an applicant. For an assignee-applicant, complete this section onlyif identification as an assigneeis also desired on the
`patent application publication.
`
`Remove
`
`
`
`
`
`
`
`
`If the Assignee or Non-Applicant Assignee is an Organization checkhere. [|
`
`
`
`Prefix
`
`Given Name
`
`Middle Name
`
`Family Name
`
`Suffix
`
`Mailing Address Information For Assignee including Non-Applicant Assignee:
`
`Address 1
`
`Address 2
`
`Phone Number
`
`Email Address
`
`
`
`
`
`
`
`
`
`
`Fax Number
`
`
`Additional Assignee or Non-Applicant Assignee Data may be generated within this form by
`selecting the Add button.
`
`Signature:
`NOTE: This form must be signed in accordance with 37 CFR 1.33. See 37 CFR 1.4 for signature requirements and
`certifications
`
`Signature First Name
`
`Date (YYYY-MM-DD)|
`
`/Kanda Ishihara/
`
`2014-02-03
`
`Additional Signature may be generated within this form by selecting the Add button.
`
`Add
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 5
`
`Petitioner’s Ex. 1002, Page 5
`
`

`

`PTOVAIA/14 (11-13)
`Approved for use through 01/31/2014. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Underthe Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`oo Attorney Docket Number|10001-04293 US
`
`Application Data Sheet 37 CFR 1.76
`
`— Title of Invention|Hybrid Device Having a Personal Digital Key and Receiver-DecocerCircuit and Methods of Use
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTOto process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amountof time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissionerfor Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 6
`
`Petitioner’s Ex. 1002, Page 6
`
`

`

`Privacy Act Statement
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552)
`and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine
`whether the Freedom cofInformation Act requires disclosure of these records.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or
`administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an
`individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of
`the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in
`order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as
`amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed,
`as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security
`review (35 U.S.C. 181} and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee,
`during an inspection of records conducted by GSA aspart of that agency's responsibility to recommend improvements in records
`management practices and programs, under authority of 44 U.S.C. 29804 and 2906. Such disclosure shall be made in accordance with the
`GSA regulations governing inspection of records for this purpose, and any other relevant(i.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations aboutindividuals.
`
`
`
`(1) the general authority for the collection
`a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that:
`of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information sclicited is voluntary; and (3) the principal purpose for which the information is
`used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent.
`If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonmentof the application or expiration of the patent.
`
` The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant
`to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37
`CFR 1.14, as a routine use, to the public if the record wasfiled in an application which became abandonedorin which the proceedings were
`terminated and which application is referenced by either a published application, an application open to public inspections or an issued
`patent.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency,if the
`USPTO becomes awareof a violation or potential violation of law or regulation.
`
`Petitioner’s Ex. 1002, Page 7
`
`EFS Web 2.2.9
`
`Petitioner’s Ex. 1002, Page 7
`
`

`

`HYBRID DEVICE HAVING A PERSONAL DIGITAL KEY AND RECEIVER-
`DECODER CIRCUIT AND METHODS OF USE
`
`INVENTOR:
`
`DAVID L. BROWN
`
`CROSS-REFERENCE TO RELATED APPLICATIONS
`
`[0001]
`
`The present application claimspriority under 35 U.S.C. § 120 to U.S. Patent
`
`Application 13/445,825 entitles “Hybrid Device Having a Personal Digital Key and Receiver
`
`Decoder Circuit and Method of Use,” filed April 12, 2012, which claimspriority under 35
`
`U.S.C. § 120 to U.S. Patent Application 12/329,329 entitled “Hybrid Device Having a Personal
`
`Digital Key and Receiver Decoder Circuit and Methodof Use,” filed December 5, 2008, now
`
`USS. Patent 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 December6, 2007 by
`
`David L. Brown, John J. Giobbi and Fred S. Hirt. The entire contents ofall of the foregoing are
`
`incorporated by reference herein.
`
`I.
`
`FIELD OF ART
`
`BACKGROUND
`
`[0002]
`
`The invention generally relates to personal digital keys and corresponding
`
`sensors, capable of proximity detection/location determination and auxiliary data
`
`services/application 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.
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 8
`
`Petitioner’s Ex. 1002, Page 8
`
`

`

`2.
`
`DESCRIPTION OF THE RELATED ART
`
`[0003]
`
`Proximity sensors and location tracking are technologies with many applications.
`
`For example, proximity sensors can be used to provide secure access to physical and/ordigital
`
`assets, based on biometrics, passwords, PINs, or other types of authentication. Proximity sensors
`
`typically have advantages of being less cumbersome,easier to use, and moreflexible in form
`
`factor and implementation. Proximity sensors can be used to control access to resources and/or
`
`to authenticate individuals, for example.
`
`[0004]
`
`Onepossible 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 ofthe tag.
`
`Regardless of how it is accomplished, location tracking (1.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 variouslocations. It can be used for time
`
`and motion studies. If tags are attached to people, then tracking of people can be usedto 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.
`
`[0005]
`
`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 hasthe 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 specific situation, thus preventing easy expandability to other situations or third
`
`party applications.
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 9
`
`Petitioner’s Ex. 1002, Page 9
`
`

`

`SUMMARY
`
`[0006]
`
`Various drawbacksof the prior art are overcomeby providing a hybrid device
`
`including a personal digital key (PDK) and a receiver-decoder circuit (RDC). The PDK and
`
`RDC ofthe 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 allowsa variety of
`
`system configurations for mixed operation including: PDK/RDC, RDC/RDC or PDK/PDK. The
`
`present invention also includes a numberof 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.
`
`[0007]
`
`Other aspects of the invention include systems and components corresponding to
`
`the above, and methods correspondingto all of the foregoing.
`
`BRIEF DESCRIPTION OF THE FIGURES
`
`[0008]
`
`FIG. 1 is a block diagram illustrating one embodiment of a system according to
`
`the invention.
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 10
`
`Petitioner’s Ex. 1002, Page 10
`
`

`

`[0009]
`
`FIG. 2 is a block diagram illustrating one embodiment of a Personal Digital Key
`
`(PDK).
`
`[0010]
`
`FIG. 3 is a block diagram illustrating one embodimentof a sensor.
`
`[0011]
`
`FIGS. 4-6 are block diagramsillustrating further embodiments of systems
`
`according to the invention.
`
`[0012]
`
`FIG. 7 is a block diagram illustrating one embodiment of a system with
`
`networked sensors.
`
`[0013]
`
`FIGS. 8-9 are block diagramsillustrating operation of the system in FIG. 7.
`
`[0014]
`
`FIG. 10 is a diagram illustrating operation of the system in FIG. 7.
`
`[0015]
`
`FIG. 11 is a block diagram of one embodiment of a hybrid device in accordance
`
`with the present invention.
`
`[0016]
`
`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.
`
`[0017]
`
`FIG. 13 is a block diagram of one embodiment of a system using the PDK and the
`
`RDCfunctionality of hybrid device in accordance with the present invention.
`
`[0018]
`
`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
`
`invention.
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 11
`
`Petitioner’s Ex. 1002, Page 11
`
`

`

`[0019]
`
`FIG. 15 is a block diagram of one embodimentof a system using the multiple
`
`PDKlinks to the hybrid device to generate an authorization signal in accordance with the present
`
`invention.
`
`[0020]
`
`FIG. 16 is a block diagram of one embodiment of a system using the hybrid
`
`device for authorization inheritance in accordance with the present invention.
`
`[0021]
`
`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
`
`alternative embodiments ofthe structures and methodsillustrated herein may be employed
`
`without departing from the principles of the invention described herein.
`
`DETAILED DESCRIPTION
`
`[0022]
`
`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 applications 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 andis
`
`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 variousregistrations of the user. In another
`
`embodiment, the sensor 108 operates as a standalone device without a connection to the network
`
`110.
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 12
`
`Petitioner’s Ex. 1002, Page 12
`
`

`

`[0023]
`
`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 informationis used as local secured information.
`
`[0024]
`
`In one example, a biometric is required in order to access specific service blocks
`
`112 inthe 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 usesthis 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 proper
`
`verification, various applications 120 are permitted to connect to the PDK 102 via the sensor 108
`
`and/or to gain access to other service blocks 112.
`
`[0025]
`
`The system 100 can be used to address applications 120 whereit 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 determinesif access to the application 120 should be
`
`granted. In this example, the system 100 provides authentication without the need for PINs or
`
`passwords(although PINs and passwords maybeused in other implementations). Moreover,
`
`personal biometric information need not be stored in any local or remote storage database andis
`
`only stored on the user’s own PDK(in one embodiment).
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 13
`
`Petitioner’s Ex. 1002, Page 13
`
`

`

`[0026]
`
`Thecredibility 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
`
`PDKsare described in more detail in U.S. Patent Application No. 11/292,330, entitled “Personal
`
`Digital Key And Receiver/Decoder Circuit System And Method” filed on November30, 2005;
`
`U.S. Patent Application No. 11/620,581 entitled “Wireless Network Synchronization Of Cells
`
`And Client Devices On A Network” filed on January 5, 2007; and U.S. Patent Application No.
`
`11/620,577 entitled “Dynamic Real-Time Tiered Client Access” filed on January 5, 2007, the
`
`entire contents of whichare all incorporated herein by reference.
`
`[0027]
`
`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 canbe,
`
`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 andinitiates 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 biometric input 104 to
`
`-7-
`
`10001-04293 US
`Petitioner’s Ex. 1002, Page 14
`
`Petitioner’s Ex. 1002, Page 14
`
`

`

`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, someorall of the
`
`authentication process can be performed by the PDK 102 instead of the sensor 108.
`
`[0028]
`
`In this example, the sensor 108 is further communicatively coupled to the network
`
`110 in order to receive and/or transmit information to remote databases for remote
`
`authentication. In an alternative embodiment, the sensor 108 includes a non-volatile data storage
`
`that can be synchronized with one or more remote databasesor 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 modeandfor the local data storage to be updated when a connectionis
`
`available. For example, a standalone sensor 108 can periodically download updated registry
`
`entries and perform authentication locally without any remote lookup.
`
`[0029]
`
`In yet another alternative, a standalone sensor 108 may havea 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 application 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.
`
`[0030]
`
`The network 110 provides communication between the sensor 108 and various
`
`validation databases and/orregistries, in addition to the applications 120. In one embodiment,
`
`the network 110