(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`
`(19) World Intellectual Property Organization
`International Bureau
`
`(43) International Publication Date
`4 March 2010 (04.03.2010)
`
`(10) International Publication Number
`WO 2010/023506 Al
`
`(51) International Patent Classification:
`H04L 9/08 (2006.01)
`
`(21) International Application Number:
`
`(22) International Filing Date:
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`PCT/IB2008/053436
`
`26 August 2008 (26.08.2008)
`
`English
`
`English
`
`(71) Applicant (for all designated States except US): NOKIA
`CORPORATION [FIZFI]; Keilalahdentie 4, FIN-02150
`Espoo (FI).
`
`(71) Applicant (for LC only): NOKIA INC. [US/US]; 6021
`Connection Drive, Irving, Texas 75039 (US).
`
`(72) Inventor; and
`(for US only): NYBERG, Kaisa
`(75) Inventor/Applicant
`Tellervo [FIZFI]; Temppelikatu 3-5 A 12, FIN-00100
`Helsinki (FI).
`
`(81) Designated States (unless otherwise indicated, for every
`kind of national protection available): AE, AG, AL, AM,
`AO, AT, AU, AZ, BA, BB, BG, BH, BR, BW, BY, BZ,
`CA, CH, CN, CO, CR, CU, CZ, DE, DK, DM, DO, DZ,
`EC, EE, EG, ES, FI, GB, GD, GE, GH, GM, GT, HN,
`HR, HU, ID, IL, IN, IS, JP, KE, KG, KM, KN, KP, KR,
`KZ, LA, LC, LK, LR, LS, LT, LU, LY, MA, MD, ME,
`MG, MK, MN, MW, MX, MY, MZ, NA, NG, NI, NO,
`NZ, OM, PG, PH, PL, PT, RO, RS, RU, SC, SD, SE, SG,
`SK, SL, SM, ST, SV, SY, TJ, TM, TN, TR, TT, TZ, UA,
`UG, US, UZ, VC, VN, ZA, ZM, ZW.
`
`(84) Designated States (unless otherwise indicated, for every
`kind of regional protection available): ARIPO (BW, GH,
`GM, KE, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG, ZM,
`ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU, TJ,
`TM), European (AT, BE, BG, CH, CY, CZ, DE, DK, EE,
`ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, LT, LU, LV,
`MC, MT, NL, NO, PL, PT, RO, SE, SI, SK, TR), OAPI
`(BF, BJ, CF, CG, CI, CM, GA, GN, GQ, GW, ML, MR,
`NE, SN, TD, TG).
`
`Declarations under Rule 4.17:
`(74) Agents: LEYES, Charles Andrew et al; Bank of Ameri
`ca Plaza, 101 South Tryon Street, Suite 4000, Charlotte, — of inventorship (Rule 4L 7(iv))
`North Carolina 28280-4000 (US).
`
`(54) Title: METHODS, APPARATUSES, COMPUTER PROGRAM PRODUCTS, AND SYSTEMS FOR PROVIDING SE
`CURE PAIRING AND ASSOCIATION FOR WIRELESS DEVICES
`
`[Continued on next page]
`
`(57) Abstract: A method, apparatus, computer program product, and
`system are provided, which may enable use of a fixed secret value and
`fixed public key in a first device for use in pairing and association of the
`first device with a second device without compromising forward secre
`cy. In this regard,
`the first and second devices may establish a first
`shared secret key in accordance with a public key agreement protocol
`based at least in part upon the fixed public key of the first device and a
`public key associated with the second device. The first shared secret key
`may be used for verification of a second shared secret key. The second
`shared secret key may be established based at least in part upon the pub
`lic key associated with the second device and a fresh public key generat
`ed by the first device and may be used to facilitate encrypted communi
`cations between the devices.
`
`312
`
`FIG. 3.
`
`Canon Exhibit 1045, Page 1
`
`

`

`WO 2010/023506 A1 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
`
`Published:
`
`— with international search report (Art. 21(3))
`
`Canon Exhibit 1045, Page 2
`
`Published:
`
`Canon Exhibit 1045, Page 2
`
`

`

`METHODS, APPARATUSES, COMPUTER PROGRAM PRODUCTS, AND
`
`SYSTEMS FOR PROVIDING SECURE PAIRING AND ASSOCIATION FOR
`
`WIRELESS DEVICES
`
`TECHNOLOGICAL FIELD
`Embodiments of the present invention relate generally to mobile
`
`communication technology and, more particularly, relate to methods, apparatuses,
`
`computer program products, and systems for providing secure pairing and
`
`association for wireless devices.
`
`BACKGROUND
`The modern communications era has brought about a tremendous
`
`expansion of wireline and wireless networks. Computer networks, television
`
`networks, and telephony networks are experiencing an unprecedented
`
`technological expansion, fueled by consumer demand. Wireless and mobile
`
`networking technologies have addressed related consumer demands, while
`
`providing more flexibility and immediacy of information transfer.
`
`Current and future networking technologies continue to facilitate ease of
`
`information transfer and convenience to users. One area in which there is a
`
`demand to further improve the convenience to users is pairing and association for
`
`wireless devices. In the past few years, there have been several advancements in
`
`the development of wireless interfaces and protocols that allow multiple devices to
`
`communicate wirelessly.
`
`Recently new secure pairing and association models have been specified
`
`for Bluetooth, Wireless USB, Wimedia and Wi-Fi Alliance. These new
`
`mechanisms require that the devices have user interfaces for handling variable
`
`verification data and passkeys, or that they can be connected using fixed cable or
`
`Canon Exhibit 1045, Page 3
`
`

`

`secure out-of-band (OOB) connection. This requirement may present a problem in
`
`that not all devices have sufficient interfaces for handling the necessary
`
`authentication data. In this regard, some vendors are reluctant to provide such
`
`interfaces due to added cost. Further, from a user perspective, usability of such
`
`online interfaces is not always easy.
`
`There is a demand for an association model using a fixed secret, which
`
`comes with one of the devices. This association model is in use in many
`
`applications, including being the traditional one also for the Bluetooth devices.
`
`However, these fixed secret applications may not be secure in that the protocols
`
`currently in use do not protect the secrecy of the fixed secret. In this regard,
`
`existing pairing and association models utilizing a fixed secret may be vulnerable
`
`to passive eavesdropping and man-in-the-middle attacks.
`
`Further, if a fixed secret is hard coded into a first device, then it may be that
`
`the public key and the private key of the device must also be fixed. Fixing of the
`
`private key may present a problem when a public key agreement protocol, such as
`
`the Diffie-Hellman key agreement protocol, is used to establish a shared secret key
`
`between the first device and a second device for use to encrypt further
`
`communications between the first and second devices. A malicious party may
`
`record communications traffic between the first and second devices and may later
`
`acquire the first device. The malicious party may then extract the fixed private key
`
`and use the fixed private key to recalculate the shared secret key and use it to
`
`decrypt the recorded traffic. Thus, communications between the first and second
`
`devices may lack perfect forward secrecy.
`
`Accordingly, it may be advantageous to provide computing device users
`
`with methods, apparatuses, computer program products, and systems for providing
`
`secure pairing and association for wireless devices. These methods, apparatuses,
`
`computer program products, and systems may advantageously provide perfect
`
`forward secrecy such that devices do not contain any secrets that may be used to
`
`decrypt messages from previous communications sessions in spite of the use of a
`
`fixed secret value and fixed private key associated with a first device to initiate
`
`pairing with the second device.
`
`Canon Exhibit 1045, Page 4
`
`

`

`BRIEF SUMMARY OF SOME EXAMPLES OF THE INVENTION
`
`A method, apparatus, computer program product, and system are therefore
`
`provided, which may provide secure pairing and association for wireless devices.
`
`In particular, a method, apparatus, and computer program product may be provided
`
`to enable, for example, the use of a fixed secret value and fixed public key in a first
`
`device, wherein the fixed secret value and fixed public key are used to initiate
`
`pairing of the first device with a second device without compromising forward
`
`secrecy. In this regard, the first and second devices may establish a first shared
`
`secret key in accordance with a public key agreement protocol based at least in part
`
`upon the fixed public key of the first device and a public key associated with the
`
`second device. The first shared secret key, however, may only be used for
`
`verification of a second shared secret key. The second shared secret key may be
`
`established based at least in part upon the public key associated with the second
`
`device and a fresh public key generated by the first device. Accordingly,
`
`communications between the first and second devices may be encrypted based
`
`upon the second shared key and not the first shared key. Thus, neither the first nor
`
`the second device contains any secrets that can be used to decrypt messages from
`
`previous communications sessions in spite of the use of a fixed secret value and
`
`fixed public key associated with the first device to initiate pairing with the second
`
`device.
`
`In one exemplary embodiment, a method is provided which may include
`
`receiving a fixed shared secret value associated with a remote device. The method
`
`may further include receiving a fixed public key from the remote device. The
`
`fixed public key may be associated with the remote device. The method may also
`
`include verifying authenticity of the fixed public key as being associated with the
`
`remote device based at least in part upon the fixed shared secret. The method may
`
`additionally include generating a public key associated with a local device and
`
`sending the generated public key to the remote device. The method may further
`
`include establishing, with the remote device, a first shared secret key in accordance
`
`with a public key agreement protocol based at least in part upon the received fixed
`
`Canon Exhibit 1045, Page 5
`
`

`

`public key and the generated public key. The method may also include receiving a
`
`fresh public key associated with the remote device from the remote device. The
`
`fresh public key may be generated by the remote device for establishing a
`
`communications session with the local device. The method may additionally
`
`include establishing, with the remote device, a second shared secret key in
`
`accordance with the public key agreement protocol for use in communications
`
`between the local device and the remote device. The establishment of the second
`
`shared key may be based at least in part upon the received fresh public key and the
`
`generated public key.
`
`In another exemplary embodiment, a computer program product is
`
`provided. The computer program product includes at least one computer-readable
`
`storage medium having computer-readable program instructions stored therein.
`
`The computer-readable program instructions may include first, second, third,
`
`fourth, fifth, sixth, seventh, and eighth program instructions. The first program
`
`instruction is for receiving a fixed shared secret value associated with a remote
`
`device. The second program instruction is for receiving a fixed public key from
`
`the remote device. The fixed public key may be associated with the remote device.
`
`The third program instruction is for verifying authenticity of the fixed public key
`
`as being associated with the remote device based at least in part upon the fixed
`
`shared secret. The fourth program instruction is for generating a public key
`
`associated with a local device. The fifth program instruction is for sending the
`
`generated public key to the remote device. The sixth program instruction is for
`
`establishing, with the remote device, a first shared secret key in accordance with a
`
`public key agreement protocol based at least in part upon the received fixed public
`
`key and the generated public key. The seventh program instruction is for receiving
`
`a fresh public key associated with the remote device from the remote device. The
`
`fresh public key may be generated by the remote device for establishing a
`
`communications session with the local device. The eighth program instruction is
`
`for establishing, with the remote device, a second shared secret key in accordance
`
`with the public key agreement protocol for use in communications between the
`
`local device and the remote device. The establishment of the second shared key
`
`Canon Exhibit 1045, Page 6
`
`

`

`may be based at least in part upon the received fresh public key and the generated
`
`public key.
`
`In another exemplary embodiment, an apparatus is provided, which may
`
`include a processor. The processor may be configured to receive a fixed shared
`
`secret value associated with a remote device. The processor may be further
`
`configured to receive a fixed public key from the remote device. The fixed public
`
`key may be associated with the remote device. The processor may also be
`
`configured to verify authenticity of the fixed public key as being associated with
`
`the remote device based at least in part upon the fixed shared secret. The processor
`
`may additionally be configured to generate a public key associated with a local
`
`device and sending the generated public key to the remote device. The processor
`
`may further be configured to establish, with the remote device, a first shared secret
`
`key in accordance with a public key agreement protocol based at least in part upon
`
`the received fixed public key and the generated public key. The processor may
`
`also be configured to receive a fresh public key associated with the remote device
`
`from the remote device. The fresh public key may be generated by the remote
`
`device for establishing a communications session with the local device. The
`
`processor may additionally be configured to establish, with the remote device, a
`
`second shared secret key in accordance with the public key agreement protocol for
`
`use in communications between the local device and the remote device. The
`
`establishment of the second shared key may be based at least in part upon the
`
`received fresh public key and the generated public key.
`
`In another exemplary embodiment, an apparatus is provided that may
`
`include means for receiving a fixed shared secret value associated with a remote
`
`device. The apparatus may further include means for receiving a fixed public key
`
`from the remote device. The fixed public key may be associated with the remote
`
`device. The apparatus may also include means for verifying authenticity of the
`
`fixed public key as being associated with the remote device based at least in part
`
`upon the fixed shared secret. The apparatus may additionally include means for
`
`generating a public key associated with a local device and sending the generated
`
`public key to the remote device. The apparatus may further include means for
`
`establishing, with the remote device, a first shared secret key in accordance with a
`
`Canon Exhibit 1045, Page 7
`
`

`

`public key agreement protocol based at least in part upon the received fixed public
`
`key and the generated public key. The apparatus may also include means for
`
`receiving a fresh public key associated with the remote device from the remote
`
`device. The fresh public key may be generated by the remote device for
`
`establishing a communications session with the local device. The apparatus may
`
`additionally include means for establishing, with the remote device, a second
`
`shared secret key in accordance with the public key agreement protocol for use in
`
`communications between the local device and the remote device. The
`
`establishment of the second shared key may be based at least in part upon the
`
`received fresh public key and the generated public key.
`
`In another exemplary embodiment, a system is provided which may include
`
`a first communications device and a second communications device. The first
`
`communications device may have a hard coded fixed shared secret value and a
`
`hard coded fixed public key and may be configured to generate a fresh public key,
`
`send the fixed public key to the second communications device, receive a public
`
`key associated with the second communications device from the second
`
`communications device, and send the fresh public key to the second
`
`communications device. The second communications device may be configured to
`
`receive the fixed shared secret value and the fixed public key, generate a public
`
`key, send the generated public key to the first communications device, and receive
`
`the fresh public key from the first communications device. The first and second
`
`communications devices may be configured to establish a first shared secret key in
`
`accordance with a public key agreement protocol based at least in part upon the
`
`received fixed public key and the public key generated by the second
`
`communications device. The first and second communications devices may also
`
`be configured to establish a second shared secret key in accordance with the public
`
`key agreement protocol based at least in part upon the fresh public key and the
`
`public key generated by the second communications device.
`
`The above summary is provided merely for purposes of summarizing some
`
`example embodiments of the invention so as to provide a basic understanding of
`
`some aspects of the invention. Accordingly, it will be appreciated that the above
`
`described example embodiments are merely examples and should not be construed
`
`Canon Exhibit 1045, Page 8
`
`

`

`to narrow the scope or spirit of the invention in any way. It will be appreciated
`
`that the scope of the invention encompasses many potential embodiments, some of
`
`which will be further described below, in addition to those here summarized.
`
`BRIEF DESCRIPTION OF THE DRAWING(S)
`
`Having thus described embodiments of the invention in general terms,
`
`reference will now be made to the accompanying drawings, which are not
`
`necessarily drawn to scale, and wherein:
`
`FIG. 1 illustrates a block diagram of a system for providing secure pairing
`
`and association for wireless devices according to an exemplary embodiment of the
`
`present invention;
`
`FIG. 2 is a schematic block diagram of a mobile terminal according to an
`
`exemplary embodiment of the present invention;
`
`FIG. 3 is a control flow diagram of communications signals passed between
`
`entities of the system of FIG. 1 according to an exemplary embodiment of the
`
`present invention; and
`
`FIG. 4 is a flowchart according to an exemplary method for providing
`
`secure pairing and association for wireless devices according to an exemplary
`
`embodiment of the present invention.
`
`DETAILED DESCRIPTION
`
`Some embodiments of the present invention will now be described more
`
`fully hereinafter with reference to the accompanying drawings, in which some, but
`
`not all embodiments of the invention are shown. Indeed, the invention may be
`
`embodied in many different forms and should not be construed as limited to the
`
`embodiments set forth herein; rather, these embodiments are provided so that this
`
`disclosure will satisfy applicable legal requirements. Like reference numerals refer
`
`to like elements throughout.
`
`FIG. 1 illustrates a block diagram of a system 100 for providing secure
`
`pairing and association for wireless devices according to an exemplary
`
`embodiment of the present invention. As used herein, "exemplary" merely means
`
`an example and as such represents one example embodiment for the invention and
`
`Canon Exhibit 1045, Page 9
`
`

`

`should not be construed to narrow the scope or spirit of the invention in any way.
`
`It will be appreciated that the scope of the invention encompasses many potential
`
`embodiments in addition to those illustrated and described herein. As such, while
`
`FIG. 1 illustrates one example of a configuration of a system for providing secure
`
`pairing and association for wireless devices, numerous other configurations may
`
`also be used to implement embodiments of the present invention.
`
`As used herein, "public key agreement protocol" refers to any number of
`
`cryptographic protocols wherein two parties may jointly establish a shared secret
`
`key over an insecure communications channel. Such a shared secret key and/or
`
`keys derived therefrom may be used to encrypt subsequent communications
`
`between the parties over the communications channel. The Diffie-Hellman key
`
`agreement protocol may be referred to herein from time to time as an example of a
`
`public key agreement protocol that may be used in conjunction with embodiments
`
`of the present invention. However, it will be appreciated that embodiments of the
`
`present invention are not limited to the use of only the Diffie-Hellman key
`
`agreement protocol.
`
`As used herein, "fixed" as used in conjunction with, for example, a "fixed
`
`shared secret value" or a "fixed public key" refers to any value that is permanently
`
`hard coded into a device. In this regard, "hard coded" refers to the permanent
`
`coding of a value into a device. In this regard, hard coded values may be coded
`
`and/or stored in a device in hardware, software, firmware, and/or some
`
`combination thereof. In contrast, a "fresh key," such as, for example, a "fresh
`
`public key" refers to a value that is generated by a first device specifically for the
`
`purpose of establishing communications with a second device and which will be
`
`discarded by the end of the resulting communications session established with the
`
`second device.
`
`Further, the terms "association" and "pairing" are used interchangeably
`
`herein and refer to the establishment of a wireless communications session
`
`between two devices. In this regard, "associated" or "paired" devices are
`
`wirelessly coupled, having formed a trusted pair and may engage in
`
`communications over a wireless communications link.
`
`Canon Exhibit 1045, Page 10
`
`

`

`Referring now to FIG. 1, the system 100 may include a host device 102 and
`
`client device 104 configured to communicate over a wireless communications link
`
`106. It will be appreciated that the terms "host" and "client" with reference to the
`
`host device 102 and client device 104 are merely for purposes of distinguishing the
`
`devices in discussion of embodiments of the invention. Embodiments of the
`
`invention are not limited to embodiments wherein the host device 102 and client
`
`device 104 interface in a client-host relationship or to communications protocols
`
`which explicitly refer to a "host" and a "client." Instead, as used herein, a client
`
`device 104 is a device having a fixed secret value and a fixed public key hard
`
`coded into the device. A host device 102 is a device that securely receives a fixed
`
`shared secret associated with a client device 104. In some embodiments, one or
`
`both of the host device 102 and client device 104 may be embodied as a mobile
`
`computing device, such as, for example a mobile terminal 10 depicted in FIG. 2 .
`
`In this regard, FIG. 2 illustrates a block diagram of a mobile terminal 10
`
`representative of one embodiment of a host device 102 and/or client device 104 in
`
`accordance with embodiments of the present invention. It should be understood,
`
`however, that the mobile terminal illustrated and hereinafter described is merely
`
`illustrative of one type of host device 102 and/or client device 104 that may benefit
`
`from embodiments of the present invention and, therefore, should not be taken to
`
`limit the scope of the present invention. While several embodiments of the
`
`electronic device are illustrated and will be hereinafter described for purposes of
`
`example, other types of electronic devices, such as mobile telephones, mobile
`
`computers, portable digital assistants (PDAs), pagers, laptop computers, desktop
`
`computers, gaming devices, televisions, and other types of electronic systems, may
`
`employ embodiments of the present invention.
`
`As shown, the mobile terminal 10 may include an antenna 12 (or multiple
`
`antennas 12) in communication with a transmitter 14 and a receiver 16. The
`
`mobile terminal may also include a controller 20 or other processor(s) that
`
`provides signals to and receives signals from the transmitter and receiver,
`
`respectively. These signals may include signaling information in accordance with
`
`an air interface standard of an applicable cellular system, and/or any number of
`
`different wireless networking techniques, comprising but not limited to Wireless-
`
`Canon Exhibit 1045, Page 11
`
`

`

`Fidelity (Wi-Fi), wireless local access network (WLAN) techniques such as
`
`Institute of Electrical and Electronics Engineers (IEEE) 802.1 1, and/or the like. In
`
`addition, these signals may include speech data, user generated data, user requested
`
`data, and/or the like. In this regard, the mobile terminal may be capable of
`
`operating with one or more air interface standards, communication protocols,
`
`modulation types, access types, and/or the like. More particularly, the mobile
`
`terminal may be capable of operating in accordance with various first generation
`
`(IG), second generation (2G), 2.5G, third-generation (3G) communication
`
`protocols, fourth-generation (4G) communication protocols, and/or the like. For
`
`example, the mobile terminal may be capable of operating in accordance with 2G
`
`wireless communication protocols IS-136 (Time Division Multiple Access
`
`(TDMA)), Global System for Mobile communications (GSM), IS-95 (Code
`
`Division Multiple Access (CDMA)), and/or the like. Also, for example, the
`
`mobile terminal may be capable of operating in accordance with 2.5G wireless
`
`communication protocols General Packet Radio Service (GPRS), Enhanced Data
`
`GSM Environment (EDGE), and/or the like. Further, for example, the mobile
`
`terminal may be capable of operating in accordance with 3G wireless
`
`communication protocols such as Universal Mobile Telecommunications System
`
`(UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code
`
`Division Multiple Access (WCDMA), Time Division-Synchronous Code Division
`
`Multiple Access (TD-SCDMA), and/or the like. The mobile terminal may be
`
`additionally capable of operating in accordance with 3.9G wireless communication
`
`protocols such as Long Term Evolution (LTE) or Evolved Universal Terrestrial
`
`Radio Access Network (E-UTRAN) and/or the like. Additionally, for example, the
`
`mobile terminal may be capable of operating in accordance with fourth-generation
`
`(4G) wireless communication protocols and/or the like as well as similar wireless
`
`communication protocols that may be developed in the future.
`
`Some Narrow-band Advanced Mobile Phone System (NAMPS), as well as
`
`Total Access Communication System (TACS), mobile terminals may also benefit
`
`from embodiments of this invention, as should dual or higher mode phones (e.g.,
`
`digital/analog or TDMA/CDMA/analog phones). Additionally, the mobile
`
`Canon Exhibit 1045, Page 12
`
`

`

`terminal 10 may be capable of operating according to Wireless Fidelity (Wi-Fi)
`
`protocols.
`
`It is understood that the controller 20 may comprise circuitry for
`
`implementing audio/video and logic functions of the mobile terminal 10. For
`
`example, the controller 20 may comprise a digital signal processor device, a
`
`microprocessor device, an analog-to-digital converter, a digital-to-analog
`
`converter, and/or the like. Control and signal processing functions of the mobile
`
`terminal may be allocated between these devices according to their respective
`
`capabilities. The controller may additionally comprise an internal voice coder
`
`(VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the
`
`controller may comprise functionality to operate one or more software programs,
`
`which may be stored in memory. For example, the controller 20 may be capable of
`
`operating a connectivity program, such as a web browser. The connectivity
`
`program may allow the mobile terminal 10 to transmit and receive web content,
`
`such as location-based content, according to a protocol, such as Wireless
`
`Application Protocol (WAP), hypertext transfer protocol (HTTP), and/or the like.
`
`The mobile terminal 10 may be capable of using a Transmission Control
`
`Protocol/Internet Protocol (TCP/IP) to transmit and receive web content across the
`
`internet or other networks.
`
`The mobile terminal 10 may also comprise a user interface including, for
`
`example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a
`
`user input interface, and/or the like, which may be operationally coupled to the
`
`controller 20. As used herein, "operationally coupled" may include any number or
`
`combination of intervening elements (including no intervening elements) such that
`
`operationally coupled connections may be direct or indirect and in some instances
`
`may merely encompass a functional relationship between components. Although
`
`not shown, the mobile terminal may comprise a battery for powering various
`
`circuits related to the mobile terminal, for example, a circuit to provide mechanical
`
`vibration as a detectable output. The user input interface may comprise devices
`
`allowing the mobile terminal to receive data, such as a keypad 30, a touch display
`
`(not shown), a joystick (not shown), and/or other input device. In embodiments
`
`Canon Exhibit 1045, Page 13
`
`

`

`including a keypad, the keypad may comprise numeric (0-9) and related keys (#,
`
`*), and/or other keys for operating the mobile terminal.
`
`As shown in Figure 2, the mobile terminal 10 may also include one or more
`
`means for sharing and/or obtaining data. For example, the mobile terminal may
`
`comprise a short-range radio frequency (RF) transceiver and/or interrogator 64 so
`
`data may be shared with and/or obtained from electronic devices in accordance
`
`with RP techniques. The mobile terminal may comprise other short-range
`
`transceivers, such as, for example, an infrared (IR) transceiver 66, a Bluetooth™
`
`(BT) transceiver 68 operating using Bluetooth™ brand wireless technology
`
`developed by the Bluetooth™ Special Interest Group, a wireless universal serial
`
`bus (USB) 70 and/or the like. The Bluetooth transceiver 68 may be capable of
`
`operating according to ultra-low power Bluetooth technology (e.g., Wibree™)
`
`radio standards. In this regard, the mobile terminal 10 and, in particular, the short-
`
`range transceiver may be capable of transmitting data to and/or receiving data from
`
`electronic devices within a proximity of the mobile terminal, such as within 10
`
`meters, for example. Although not shown, the mobile terminal may be capable of
`
`transmitting and/or receiving data from electronic devices according to various
`
`wireless networking techniques, including Wireless Fidelity (Wi-Fi), WLAN
`
`techniques such as IEEE 802.1 1 techniques, and/or the like.
`
`The mobile terminal 10 may comprise memory, such as a subscriber
`
`identity module (SIM) 38, a removable user identity module (R-UIM), and/or the
`
`like, which may store information elements related to a mobile subscriber. In
`
`addition to the SIM, the mobile terminal may comprise other removable and/or
`
`fixed memory. The mobile terminal 10 may include volatile memory 40 and/or
`
`non-volatile memory 42. For example, volatile memory 40 may include Random
`
`Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip
`
`cache memory, and/or the like. Non-volatile memory 42, which may be embedded
`
`and/or removable, may include, for example, read-only memory, flash memory,
`
`magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, etc.),
`
`optical disc drives and/or media, non-volatile random access memory (NVRAM),
`
`and/or the like. Like volatile memory 40 non-volatile memory 42 may include a
`
`cache area for temporary storage of data. The memories may store one or more
`
`Canon Exhibit 1045, Page 14
`
`

`

`software programs, instructions, pieces of information, data, and/or the like which
`
`may be used by the mobile terminal for performing functions of the mobile
`
`terminal. For example, the memories may comprise an identifier, such as an
`
`international mobile equipment identification (IMEI) code, capable of uniquely
`
`identifying the mobile terminal 10.
`
`Returning to FIG. 1, the host device 102 and client device 104 are not
`
`limited to being embodied as a mobile terminal 10 and may be embodied as any
`
`computing device, mobile or fixed, and may be embodied as a server, desktop
`
`computer, laptop computer, mobile terminal 10, and/or the like. The wireless
`
`communications link 106 may comprise any wireless link in accordance with any
`
`wireless communications protocol over which the host device 102 and client
`
`device 104 are configured to communicate. Example protocols that may be
`
`implemented for communication over the wireless communications link 106
`
`include, but are not limited to, Bluetooth™, wireless USB, and/or the like.
`
`The host device 102 may include various means, such as a processor 110,
`
`memory 112, communication interface 114, user interface 116, and host
`
`cryptography unit 118 for performing the various functions herein described.
`
`These means of the host device 102 as described herein may be embodied as, for
`
`example, hardwa