(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2009/0055322 A1
`Bykov et al.
`(43) Pub. Date:
`Feb. 26, 2009
`
`US 20090055322A1
`
`(54) REMOVABLE MODULE IN PERSONAL
`HAND HELD DEVICES FOR PERSONAL
`INFORMATION EXCHANGE
`
`(75) Inventors:
`
`Sergey I. Bykov, Redmond, WA
`(US); Charles J. Williams,
`Redmond, WA (US)
`Correspondence Address:
`MERCHANT & GOULD (MICROSOFT)
`P.O. BOX 2903
`MINNEAPOLIS, MN 55402-0903 (US)
`(73) Assignee:
`Microsoft Corporation, Redmond,
`WA (US)
`11/844,078
`
`(21) Appl. No.:
`
`(22) Filed:
`
`Aug. 23, 2007
`
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`G06F 7700
`(2006.01)
`G06O 40/00
`(2006.01)
`H04L 9/00
`(52) U.S. Cl. .................... 705/64; 705/1705/16; 705/42
`
`ABSTRACT
`(57)
`A personal information exchange module in a standardized
`form is used as a plug-in to a personal handheld device for
`information exchange Such as financial transactions, facility
`access, medical information exchange, and the like while
`protecting sensitive code and data associated with the module
`by separating those from the operating environment of the
`personal handheld device. Functional capabilities of the mod
`ule may also be adjusted based on available power from the
`personal handheld device.
`
`7OO
`1.
`
`7O2
`
`Y
`
`(
`
`Start
`
`w
`Activate Personal Info
`Exchange Application
`
`Provide User Interaction
`Options Within Device GUI
`
`Communicate With Terminal k
`
`
`
`
`
`Transaction
`Complete?
`
`
`
`712
`
`s
`
`-
`
`-
`-
`r
`N - -
`-3C Device Power Low?
`
`No
`
`is
`
`Reconfigure Functional
`Capabilities of Personal
`
`APPL-1013
`APPLE INC. / Page 1 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 1 of 7
`
`US 2009/0055322 A1
`
`FIG. 1B
`
`
`
`APPL-1013
`APPLE INC. / Page 2 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 2 of 7
`
`US 2009/0055322 A1
`
`
`
`FIG. 2
`
`APPL-1013
`APPLE INC. / Page 3 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 3 of 7
`
`US 2009/0055322 A1
`
`
`
`1. 2OO
`
`FIG. 3
`
`APPL-1013
`APPLE INC. / Page 4 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 4 of 7
`
`US 2009/0055322 A1
`
`468
`
`1
`
`V
`N
`
`Main Application
`465
`
`1.
`
`
`
`
`
`V
`N
`N
`
`Payment
`Application
`463
`
`
`
`
`
`464
`
`w N
`
`1
`\
`M
`
`-
`
`FIG. 4
`
`APPL-1013
`APPLE INC. / Page 5 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 5 of 7
`
`US 2009/0055322 A1
`
`
`
`FIG. 5
`
`APPL-1013
`APPLE INC. / Page 6 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 6 of 7
`
`US 2009/0055322 A1
`
`ROM/RAM
`
`- - - -
`Operating
`System
`
`Personal Info
`Exchange
`(Payment) App.
`
`Removable
`Module
`
`
`
`
`
`Communication
`Connection(s)
`
`FIG. 6
`
`APPL-1013
`APPLE INC. / Page 7 of 14
`
`

`

`Patent Application Publication
`
`Feb. 26, 2009 Sheet 7 of 7
`
`US 2009/0055322 A1
`
`7OO
`
`1
`
`Activate Personal Info
`Exchange Application
`
`
`
`---- ---
`Provide User Interaction
`; Options Within Device GUI
`
`
`
`
`
`Transaction
`Complete?
`
`as as a
`
`as a
`
`- as
`
`712
`
`CY
`- a
`
`N.
`- 1
`Device Power Low?
`
`.
`
`Reconfigure Functional
`Capabilities of Personal
`| Information Exchange Module
`
`- - - - - - - - - - -
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`APPL-1013
`APPLE INC. / Page 8 of 14
`
`

`

`US 2009/0055322 A1
`
`Feb. 26, 2009
`
`REMOVABLE MODULE IN PERSONAL
`HAND HELD DEVICES FOR PERSONAL
`INFORMATION EXCHANGE
`
`BACKGROUND
`
`0001. With the proliferation of personal handheld devices
`Such as Smart mobile phones, there is increased interest in
`mobile wallet solutions that enable consumers to pay for their
`purchases with their mobile phones and perform similar
`actions. A mobile wallet is a program that runs on the phone,
`stores payment instrument information Such as credit card
`data, and enables a user to make purchases. At the time of a
`payment transaction, the program sends the payment instru
`ment information to the receiver that can be a Point of Sale
`(POS) terminal, payment terminal, and Automated Teller
`Machine (ATM), etc.
`0002 One of the challenges with mobile wallets is storing
`payment instrument data securely so that it cannot be easily
`extracted from a stolen phone. Another challenge is protec
`tion of the software code that handles sensitive information. If
`the code runs on the same processor and in the same environ
`ment as other software components of the phone, it may be
`difficult or impossible to ensure isolation of the sensitive code
`and data as it can be compromised by other software running
`on the phone. Compatibility may also present difficulties for
`Such a combination system since different phone models
`typically have different and often incompatible software
`execution environments that may hinderportability of mobile
`wallet between different phone models.
`
`SUMMARY
`
`0003. This summary is provided to introduce a selection of
`concepts in a simplified form that are further described below
`in the Detailed Description. This summary is not intended to
`identify key features or essential features of the claimed sub
`ject matter, nor is it intended as an aid in determining the
`Scope of the claimed Subject matter.
`0004 Embodiments are directed to enabling use of per
`Sonal handheld devices for personal information exchange
`requiring services such as payment applications, access
`applications, and the like. According to embodiments, a per
`Sonal information exchange application may be executed in a
`hardware software combination module that fits into a stan
`dardized connection in the personal handheld device Such as
`a Subscriber Identity Module (SIM) card. According to other
`embodiments, the hardware software combination may be
`enabled with additional capabilities such as passive commu
`nication independent of the personal handheld device's com
`munication system, control of personal information exchange
`application's capabilities based on available power, and so on.
`0005. These and other features and advantages will be
`apparent from a reading of the following detailed description
`and a review of the associated drawings. It is to be understood
`that both the foregoing general description and the following
`detailed description are explanatory only and are not restric
`tive of aspects as claimed.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`0006 FIG. 1A-1C illustrate example usage scenarios of a
`personal handheld device with personal information
`exchange application according to embodiments;
`
`0007 FIG. 2 illustrates the front view of an example per
`sonal handheld device which may include a module for per
`Sonal information exchange;
`0008 FIG. 3 illustrates the rear view of an example per
`sonal handheld device which may include a module for per
`Sonal information exchange;
`0009 FIG. 4 is a conceptual diagram illustrating relation
`ships of a payment application incorporated into a Smart
`phone device and the main phone application(s):
`0010 FIG. 5 is an example networked environment, where
`embodiments may be implemented;
`0011
`FIG. 6 is a block diagram of an example computing
`operating environment, where embodiments may be imple
`mented; and
`0012 FIG. 7 illustrates a logic flow diagram for a process
`of facilitating a personal information exchange application
`within a personal handheld device environment.
`
`DETAILED DESCRIPTION
`0013 As briefly described above, a hardware software
`combination module may be employed to incorporate a per
`Sonal information exchange application into a personal hand
`held device. In the following detailed description, references
`are made to the accompanying drawings that form a part
`hereof, and in which are shown by way of illustrations spe
`cific embodiments or examples. These aspects may be com
`bined, other aspects may be utilized, and structural changes
`may be made without departing from the spirit or scope of the
`present disclosure. The following detailed description is
`therefore not to be taken in a limiting sense, and the scope of
`the present invention is defined by the appended claims and
`their equivalents.
`0014 While the embodiments will be described in the
`general context of program modules that execute in conjunc
`tion with an application program that runs on an operating
`system on a personal computer, those skilled in the art will
`recognize that aspects may also be implemented in combina
`tion with other program modules.
`00.15
`Generally, program modules include routines, pro
`grams, components, data structures, and other types of struc
`tures that perform particular tasks or implement particular
`abstract data types. Moreover, those skilled in the art will
`appreciate that embodiments may be practiced with other
`computer system configurations, including hand-held
`devices, multiprocessor systems, microprocessor-based or
`programmable consumer electronics, minicomputers, main
`frame computers, and the like. Embodiments may also be
`practiced in distributed computing environments where tasks
`are performed by remote processing devices that are linked
`through a communications network. In a distributed comput
`ing environment, program modules may be located in both
`local and remote memory storage devices.
`0016 Embodiments may be implemented as a computer
`process (method), a computing system, or as an article of
`manufacture. Such as a computer program product or com
`puter readable media. The computer program product may be
`a computer storage media readable by a computer system and
`encoding a computer program of instructions for executing a
`computer process. The computer program product may also
`be a propagated signal on a carrier readable by a computing
`system and encoding a computer program of instructions for
`executing a computer process.
`0017 Referring to FIG. 1A-1C, example usage scenarios
`of a personal handheld device with personal information
`
`APPL-1013
`APPLE INC. / Page 9 of 14
`
`

`

`US 2009/0055322 A1
`
`Feb. 26, 2009
`
`exchange application according to embodiments are illus
`trated. A personal handheld device as used herein is any
`portable computing device that is capable of performing tasks
`Such as communication, scheduling, audio/video/image pro
`cessing and presentation, and the like. A Smart phone, a
`portable music player, a portable audio/video player, a remote
`control device, and a personal digital assistant (PDA) are
`examples of personal handheld devices. Embodiments are not
`limited to these example devices, however. Other types of
`portable devices may also be used to incorporate a personal
`information exchange module. For example, even a medical
`monitoring device may be used with a personal information
`exchange module as described herein.
`0018 Personal information exchange is part of almost
`every aspect of today's life. People make payments providing
`personal information Such as credit card data, provide identity
`information at medical offices and similar places, and even
`use identity information for accessing facilities Such as at
`electronically controlled gates.
`0019 FIG. 1A shows a consumer (102) making payment
`using a smartphone (104) at a Point Of Sale (POS) terminal
`106. FIG. 1B shows a patient 102 providing personal infor
`mation to a receptionist110 at a doctor's office using his PDA
`(108). FIG. 1C shows a person (102) opening a gate 114 to
`access a facility 116 using his Smartphone 112.
`0020 AS mentioned previously, incorporating a personal
`information exchange application directly into a personal
`handheld device has its challenges such as protection of sen
`sitive software code, compatibility between different hand
`held device operating systems and the application program
`(s), and so on. Another challenge in the specific example of
`incorporating payment instruments into Smartphones is that
`provisioning of mobile wallets as it takes physical or over the
`air (OTA) access to the phone to initialize or update the phone
`with the payment instrument information and other related
`data.
`0021. Furthermore, some mobile wallet solutions may be
`blocked by the conflict of interests, ownership, and business
`models between mobile service providers and financial insti
`tutions. Both parties have their own relations with the cus
`tomer: for the service providers, the customer is a mobile
`phone Subscriber, for the financial institution, the same cus
`tomer is an accountholder. The service providers may refuse
`to give access to the phone software by any external applica
`tion considering it their asset. The financial institutions may
`be reluctant to have the service providers involved in their
`transactions and fees.
`0022. According to some embodiments, a hardware soft
`ware combination module may be attached to the personal
`handheld device through a standardized connection and be
`capable of executing its own application without having to
`share sensitive code or data with the handheld device's own
`software.
`0023 FIG. 2 illustrates the front view of an example per
`sonal handheld device which may include a module for per
`sonal information exchange. While personal handheld
`devices according to embodiments may take many forms, a
`smart phone/PDA device is illustrated in the figure as an
`example.
`0024 Personal handheld device 200 is shown with many
`features. However, embodiments may be implemented with
`fewer or additional components. Example personal handheld
`device 200 includes typical components of a mobile commu
`nication device Such as a hard keypad 222, specialized but
`
`tons (“function keys”) 224 and 226, display 228, and one or
`more indicators (e.g. LED) 234. Personal handheld device
`200 may also include a camera 238 for video communications
`and microphone 236 for voice communications. Display 228
`may be an interactive display (e.g. touch sensitive) and pro
`vide soft keys (e.g. 230) as well.
`0025. In addition to providing a Graphical User Interface
`(GUI) for the main application(s) such as communication
`application, scheduling application, and the like, of the per
`sonal handheld device 200, the display 228 may also present
`a GUI for the personal information exchange application to
`the user. For example, an application user interface may dis
`play options to a user to make payment from an account, the
`amount, account balance, and so on. For an identity verifica
`tion application, the GUI may again provide options for the
`user to select as to which personal information should be
`provided (e.g. social security number, address, etc.). Some or
`all of the information exchange may also be automated and
`the user simply provided a confirmation that the transaction
`has taken place. Some of the specialized buttons and/or soft
`keys may be used by the personal information exchange
`application GUI.
`0026 FIG. 3 illustrates the rear view of an example per
`sonal handheld device which may include a module for per
`Sonal information exchange. A personal handheld device may
`typically include a battery 344, power connection 342, and
`one or more standardized modules (e.g. modules 346 and 352
`and their connectors 348 and 354).
`0027. A personal information exchange module according
`to embodiments may be implemented as a standardized mod
`ule that can be easily plugged into any personal handheld
`device. For example, the personal information exchange
`module may be in SIM form, which is accepted by a majority
`of cellular phones today. Many personal handheld devices,
`such as PDAs, also include memory module slots where
`memory or similar modules may be plugged in.
`0028. In the example of a payment module, a module
`provided by a financial institution may execute sensitive code
`and store sensitive financial data with its appropriate security
`measures. A user may obtain this module from their financial
`institution and plug into a SIM card slot (if the module is in
`SIM form) of their cellular phone and use the phone for
`financial transactions transparent to the main functionality of
`the phone. Since the sensitive code and data is not transferred
`to the control of the phone's operating system, the module's
`integrity is protected and compatibility issues may be mini
`mized by using standard APIs.
`0029. The personal information exchange module may be
`configured to operate in various modes. For example, the
`module may be configured to use the host device (personal
`handheld device) only as a power Source by connecting to the
`battery of the host device without interacting with the device
`operating system. The interaction between the host device
`and the module may be arranged in varying degrees. Accord
`ing to another example, the keypad of the personal handheld
`device may be used for basic interaction with the module such
`as PIN entry without further interaction with the operating
`system. According to a further example, the module may
`interact directly with the screen and the keyboard bypassing
`the local operating system all together.
`0030. On the other end of the spectrum, the module may be
`designed for fully compatible operation with the host device's
`operating system enabling the personal handheld device to
`display a GUI for the module's software application and the
`
`APPL-1013
`APPLE INC. / Page 10 of 14
`
`

`

`US 2009/0055322 A1
`
`Feb. 26, 2009
`
`user's interaction with the module's application beyond
`simple PIN entry. Such interactions may include account
`selection, balance check, transaction history review, personal
`information selection, and the like.
`0031. As described above, the personal information
`exchange application may be configured to be executed par
`tially in the module and partially in the personal handheld
`device Such that sensitive code and data are protected physi
`cally within the module, while the application takes advan
`tage of power management and user interface capabilities of
`the host device's operating system.
`0032 A personal information exchange module according
`to embodiments may be an active device that requires external
`power from the host device to operate or a passive device that
`is powered by electromagnetic waves transmitted from a ter
`minal device (e.g. a passive card). The power use of the
`personal information exchange module may be configured
`based on the available power from the host device. This can be
`managed in a variety of ways.
`0033. The power management can vary from a simple
`turning off the module when Sufficient power is no longer
`available to adjusting capabilities of the module based on
`available power. For example, a payment module with an
`interactive GUI (mobile banking functions) may have its
`mobile banking capabilities (e.g. checking transaction his
`tory, balance, etc.) limited if available power is insufficient. A
`module that is capable of operating as an active module and a
`passive module may be Switched to a passive operation mode,
`when the host device has insufficient power allowing the user
`to continue making payments even when their cellular phone
`has run out of battery, for example. Similarly, a facility access
`module may still be used even when the personal handheld
`device is turned off, if the module is set to passive operation
`mode (e.g. Near Field Communications).
`0034. As discussed above, the personal information
`exchange module may be implemented in a standardized
`form such as a SIM card. These standardized forms may be
`employed across different types of personal handheld
`devices. For example, SIM card slots may be designed into
`portable audio/video players, PDAs, or even remote control
`devices allowing a user to move their module from one por
`table device to another.
`0035 Moreover, a personal handheld device such as those
`described in conjunction with FIG. 2 and FIG. 3 may be
`equipped with additional authentication mechanisms such as
`fingerprint recognition, Voice recognition, and the like. A
`module according to embodiments may be configured to
`authenticate the user through one of these mechanisms before
`executing the transaction(s).
`0036 FIG. 4 is a conceptual diagram illustrating relation
`ships of an example payment application incorporated into a
`Smartphone device and the main phone application(s). While
`a variety of personal handheld devices may be used as a host
`device for a module according to embodiments and the host
`devices may or may not include communication capability, an
`expected area of use for such a module is a mobile wallet
`application as part of a Smartphone device. Moreover, Smart
`phones utilizing cellular technology are common today, but
`with the development of newer network communication tech
`nologies and increased bandwidth and processing power,
`handheld devices using other communication technologies
`and providing additional services are not in the too distant
`future. A mobile wallet module according to embodiments
`
`would be just as applicable with the personal handheld
`devices of the future as those available today.
`0037. In the figure, smartphone 402 is illustrated as hav
`ing a main application 465, which manages communication
`capabilities of the phone as part of a network 466 that may be
`managed by a central server or group of servers (468). The
`mobile wallet module of the phone enables payment applica
`tion 463 to be executed in conjunction with the main appli
`cation 465 of the phone.
`0038. When a transaction is performed, payment applica
`tion 463 may communicate with a terminal device 462, which
`is part of a network 464 managed by one or more servers (469)
`of the financial institution issuing (or authorizing) the mod
`ule.
`0039 FIG. 5 is an example networked environment, where
`embodiments may be implemented. A personal information
`exchange module is configured to communicate with another
`device, such as a POS terminal, for exchange of personal
`information. The other device is commonly part of a larger
`network of devices managed by one or more servers. Such a
`system may be implemented in a distributed manner over a
`number of physical and virtual clients and servers. It may also
`be implemented in un-clustered systems or clustered systems
`employing a number of nodes communicating over one or
`more networks (e.g. network(s) 570).
`0040. The system may comprise any topology of servers,
`clients, Internet service providers, and communication
`media. Also, the system may have a static or dynamic topol
`ogy. The term "client may refer to a client application or a
`client device. While a networked system implementing com
`munication with a personal information exchange module
`may involve many more components, relevant ones are dis
`cussed in conjunction with this figure.
`0041. A module according to embodiments is typically
`plugged into a personal handheld device Such as cellular
`phone 588 or PDA 586. The module communicates, again
`commonly through near field communications, but not lim
`ited to that communication form, with other devices such as
`terminal 582. Terminal 582 is connected to a larger network
`managed by server 572 for performing the transactions asso
`ciated with the module.
`0042 Data stores associated with personal information
`exchange may be embodied in a single data store Such as data
`store 576 or distributed over a number of data stores associ
`ated with individual client devices, servers, and the like.
`Dedicated database servers (e.g. database server 574) may be
`used to coordinate data retrieval and storage in one or more of
`Such data stores. The data store(s) may store information
`associated with the modules and/or users such as identifying
`information, security information, access information, and
`the like.
`0043 Network(s) 570 may include a secure network such
`as an enterprise network, an unsecure network Such as a
`wireless open network, or the Internet. Network(s) 570 pro
`vide communication between the nodes described herein. By
`way of example, and not limitation, network(s) 570 may
`include wired media such as a wired network or direct-wired
`connection, and wireless media Such as acoustic, RF, infrared
`and other wireless media.
`0044) Many other configurations of computing devices,
`applications, data sources, data distribution systems may be
`employed to implement personal information exchange using
`a plug-in module in a personal handheld device. Furthermore,
`the networked environments discussed in FIG.5 are for illus
`
`APPL-1013
`APPLE INC. / Page 11 of 14
`
`

`

`US 2009/0055322 A1
`
`Feb. 26, 2009
`
`tration purposes only. Embodiments are not limited to the
`example applications, modules, or processes.
`004.5
`FIG. 6 and the associated discussion are intended to
`provide a brief, general description of a suitable computing
`environment in which embodiments may be implemented.
`With reference to FIG. 6, a block diagram of an example
`computing operating environment is illustrated. Such as com
`puting device 600. In a basic configuration, the computing
`device 600 may be any portable handheld device providing
`communication and other services to consumers in conjunc
`tion with a hosted service and typically include at least one
`processing unit 602 and system memory 604. Computing
`device 600 may also include a plurality of processing units
`that cooperate in executing programs. Depending on the exact
`configuration and type of computing device, the system
`memory 604 may be volatile (such as RAM), non-volatile
`(such as ROM, flash memory, etc.) or some combination of
`the two. System memory 604 typically includes an operating
`system 605 suitable for controlling the operation of a net
`worked personal computer, such as the WINDOWSR) oper
`ating systems from MICROSOFT CORPORATION of Red
`mond, Wash. The system memory 604 may also include one
`or more Software applications such as program modules 606.
`According to some embodiments, a personal information
`exchange application 620 associated with the module may be
`executed under the control of the operating system 606 but
`reside in removable module 609. According to other embodi
`ments, the module may operate completely independently
`from the operating system of computing device 600 and only
`receive power from the device.
`0046. The computing device 600 may have additional fea
`tures or functionality. For example, the computing device 600
`may also include additional data storage devices (removable
`and/or non-removable) Such as, for example, magnetic disks,
`optical disks, or tape. Such additional storage is illustrated in
`FIG. 6 by storage 610. Computer storage media may include
`volatile and nonvolatile, removable and non-removable
`media implemented in any method or technology for storage
`of information, such as computer readable instructions, data
`structures, program modules, or other data. System memory
`604, storage 610 are all examples of computer storage media.
`Computer storage media includes, but is not limited to, RAM,
`ROM, EEPROM, flash memory or other memory technology,
`CD-ROM, digital versatile disks (DVD) or other optical stor
`age, magnetic cassettes, magnetic tape, magnetic disk storage
`or other magnetic storage devices, or any other medium
`which can be used to store the desired information and which
`can be accessed by computing device 600. Any such com
`puter storage media may be part of device 600. Computing
`device 600 may also have input device(s) 612 such as key
`board, mouse, pen, Voice input device, touch input device, etc.
`Output device(s) 614 Such as a display, speakers, printer, etc.
`may also be included. These devices are well known in the art
`and need not be discussed at length here.
`0047. The computing device 600 may also contain com
`munication connections 616 that allow the device to commu
`nicate with other computing devices, such as over a wireless
`network in a distributed computing environment, for
`example, an intranet or the Internet. Communication connec
`tion 616 is one example of communication media. Commu
`nication media may typically be embodied by computer read
`able instructions, data structures, program modules, or other
`data in a modulated data signal. Such as a carrier wave or other
`transport mechanism, and includes any information delivery
`
`media. The term “modulated data signal” means a signal that
`has one or more of its characteristics set or changed in Such a
`manner as to encode information in the signal. By way of
`example, and not limitation, communication media includes
`wired media such as a wired network or direct-wired connec
`tion, and wireless media Such as acoustic, RF, infrared and
`other wireless media. The term computer readable media as
`used herein includes both storage media and communication
`media.
`0048. As discussed previously, removable module 609
`communicates with other devices through its own communi
`cation circuitry. Removable module 609 may communicate
`employing near field communications, longer range wireless
`communications, wired communications such as described
`above, or optical communications.
`0049. The claimed subject matter also includes methods.
`These methods can be implemented in any number of ways,
`including the structures described in this document. One Such
`way is by machine operations, of devices of the type
`described in this document.
`0050. Another optional way is for one or more of the
`individual operations of the methods to be performed in con
`junction with one or more human operators performing some.
`These human operators need not be collocated with each
`other, but each can be only with a machine that performs a
`portion of the program.
`0051
`FIG. 7 illustrates a logic flow diagram for process
`700 of facilitating a personal information exchange applica
`tion within a personal handheld device environment. Process
`700 may be implemented in a personal handheld device.
`0052 Process 700 begins with operation 702, where a
`personal information exchange application associated with a
`module according to embodiments is activated. The applica
`tion may be activated by the user or by the module itself, for
`example upon sensing a nearby terminal for communication.
`Processing advances from operation 702 to optional opera
`tion 704.
`0053 At optional operation 704, user interaction options
`are provided through a GUI controlled by the operating sys
`tem of the personal handheld device. According to some
`embodiments, the personal information exchange module
`may operate in an automated fashion without requiring user
`interaction. Processing moves from optional operation 704 to
`operation 706.
`0054. At operation 706, the module communicates with
`the terminal device to perform the intended transaction (e.g.
`make payment, access facilities, provide medical informa
`tion, provide identity information, etc.). Processing moves
`from operation 706 to decision operation 708.
`0055. At decision operation 708, a determination is made
`whether the transaction is complete. If the transaction is not
`completed yet, processing returns to operation 706. If the
`transaction is complete, processing advances to optional
`operation 710.
`0056. At optional operation 710, the user is provided a
`feedback Such as a GUI indication, an audio indication, or a
`graphical indication. Processing advances from optional
`operation 710 to optional decision operation 712.
`0057. At optional decision operation 712, a determination
`is made whether the personal handheld device power level is
`low. If there is still sufficient power available, processing
`returns to operation 702 for further transactions. If the power
`level is below a predefined threshold, processing moves to
`optional operation 714.
`
`APPL-1013
`APPLE INC. / Page 12 of 14
`
`

`

`US 2009/0055322 A1
`
`Feb. 26, 2009
`
`0058 At optional operation 714, functional capabilities of
`the personal information exchange module are reconfigured.
`The reconfiguration may include limitation of some of the
`functionalities or a change of operational mode such as from
`an active module to a passive module Such that the user can
`continue to perform the transactions even if the personal
`handheld device is turned off due to lack of power. After
`optional operation 714, processing moves to a calling process
`for further actions.
`0059. The operations included in process 700 are for illus
`tration purposes. Facilitating a personal information
`exchange application within a personal handheld device envi
`ronment may be implemented by similar processes with
`fewer or additional steps, as well as in different order of
`operations using the principles described herein.
`0060. The above specification, examples and data provide
`a complete description of the manufacture and use of the
`composition of the embodiments. Although the Subject mat
`ter has been described in language specific to str