Near Field Communication for Managing a Low Power Mode of an Electronic Device

Abstract

The present invention relates to managing near field communication in a low power mode of an electronic device. A system, method, and computer-readable medium for managing near field communication during a low power management mode of an electronic device are provided that enable the credentials of a near field communication (“NFC”) component to be appropriately secure and appropriately accessible while also limiting the power consumption of the NFC component and other components of the electronic device.

Description

[0001] This application is a divisional application of the patent application for invention titled "Near Field Communication for Managing Low Power Modes of an Electronic Device" with application date of June 19, 2014, application number of 201480044468.9.

[0002] Cross - reference to related applications

[0003] This patent application claims priority to the previously filed U.S. Provisional Patent Application 61 / 863,549 filed on August 8, 2013, and the U.S. Patent Application 14 / 063,433 filed on October 25, 2013, the entire disclosures of which are incorporated herein by reference. Technical Field

[0004] The present disclosure relates to managing near field communication, and more particularly to managing near field communication using a low power mode of an electronic device. Background Art

[0005] Portable electronic devices (e.g., cellular phones) may have near field communication ("NFC") components for enabling contactless proximity - based communication with another entity. These communications are often associated with currency transactions or other secure data transactions that users rely on daily, such as credit card payments and public transportation ticketing. However, due to the limited amount of available power in battery - operated devices, when the available power of such a device drops below a certain threshold, its NFC capabilities are often affected or rendered unusable. Summary of the Invention

[0006] The present invention describes a system, method, and computer - readable medium for managing power usage in a device capable of near field communication and / or other wireless communication technologies.

[0007] For example, a method for operating an electronic device may include receiving authentication information using an input component of the electronic device. The method may further include powering at least a portion of the near field communication component of the electronic device based on the received authentication information.

[0008] As another example, a method for operating an electronic device may include detecting a low - power - mode initiation event. In response to the detection, the method may further include disabling active components of the electronic device, where the active components include at least one of a communication component and an output component. The method also includes closing at least one active application running on the electronic device prior to the detection, and running a low - power - mode application on the electronic device. Running the low - power - mode application may include receiving authentication information from an input component of the electronic device, and enabling the near field communication component of the electronic device based on the received authentication information.

[0009] As yet another example, a method of operating an electronic device may include detecting a low power mode initiation event. In response to the detection, the method may further include disabling components of the electronic device and identifying an authentication initiation event. In response to the identification, the method may further include providing an output for requesting user interaction on an output component of the electronic device, the user interaction for enabling a near field communication component of the electronic device.

[0010] As yet another example, a non-transitory computer-readable medium may include computer-readable instructions recorded thereon for detecting a low power mode initiation event on an electronic device, and for disabling components of the electronic device in response to the detection to identify an authentication initiation event on the electronic device, and for providing an output on an output component of the electronic device in response to the identification for requesting enabling of a near field communication component of the electronic device.

[0011] As yet another example, an electronic device may include a near field communication component, an output component, and a processor. The processor may be configured to detect a low power mode initiation event, to ensure disabling of at least one function of the near field communication component in response to detecting the low power mode initiation event, to identify an authentication initiation event once ensuring disabling of at least one function of the near field communication component, and to provide an output on the output component for requesting user interaction with the electronic device in response to identifying the authentication initiation event, the user interaction for enabling at least one function of the near field communication component.

[0012] The present invention content is provided only to outline some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described in the present invention content are only exemplary and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The following discussion refers to the following drawings, in which like reference numerals refer to like components in all the drawings, and in which:

[0014] Figure 1 is a schematic diagram of an exemplary communication system including an electronic device for managing near field communication;

[0015] Figure 2 is Figure 1 a front view of the electronic device;

[0016] Figure 3 is Figure 1 and Figure 2 a schematic diagram of an exemplary portion of the electronic device;

[0017] Figures 4A - 4G Is Figures 1 - 3 a front view of a screen of a graphical user interface of an electronic device, which shows a process for managing near field communication; and

[0018] FIG. 5 - Figure 8 is a flowchart of an exemplary process for managing near field communication. DETAILED DESCRIPTION

[0019] According to different power management modes of the electronic device, near field communication can be managed in different ways. In some low power management modes, some components of the electronic device can be at least partially disabled or turned off to save power. When the electronic device is operating in these modes, it is possible to appropriately ensure the security of the credentials of the NFC component in the device and / or provide appropriate access to it, while restricting or reducing the power consumption of the NFC component. For example, when entering the low power management mode, the NFC component can be initially disabled and user authentication can be required to re - enable the NFC component for use during the low power management mode. When entering the low power management mode, output components such as a display can also be initially disabled, however, the output component can be re - enabled at a slightly later point during the low power management mode in order to prompt the user to authenticate themselves so as to re - enable the NFC component. One or more applications running on the device before entering the low power mode, such as non - native applications, can be disabled when entering the low power management mode, and a specific low power management mode application can be launched to control the NFC component and / or any other component of the electronic device during the low power management mode. The low power management mode can be initialized in response to a user request or in response to the remaining power of the power supply dropping below a specific threshold, and the user authentication of the NFC component can be initialized during the low power management mode in response to a user request or in response to detecting an NFC terminal in a specific neighborhood of the electronic device.

[0020] Figure 1 is a schematic diagram of an exemplary communication system 1 according to some embodiments, the exemplary communication system can include a terminal 10 and an electronic device 100 for managing near field communication 55 with the terminal 10. The electronic device 100 can include, but is not limited to, a music player (e.g., an iPod TM ) that can be purchased from Apple Inc. of Cupertino, California, a video player, a still image player, a game player, other media players, a music recorder, a movie or video camera or recorder, a still camera, other media recorders, a radio frequency device, a medical device, a household appliance, a transportation vehicle instrument, a musical instrument, a calculator, a cellular phone (e.g., an iPhone that can be purchased from Apple Inc. TM) and other wireless communication devices, personal digital assistants, remote controls, pagers, computers (e.g., desktop computers, laptop computers, tablet computers (e.g., iPad available from Apple Inc.), servers, etc.), monitors, televisions, stereo equipment, fixed boxes, set-top boxes, large portable recorders, modems, routers, printers, or any combination thereof. In some embodiments, the electronic device 100 may perform a single function (e.g., the device is dedicated to managing near-field communication), and in other embodiments, the electronic device 100 may perform multiple functions (e.g., the device manages near-field communication, plays music, and receives and transmits phone calls). TM The electronic device 100 can be any portable electronic device, mobile electronic device, handheld electronic device, or microelectronic device configured to manage near-field communication wherever the user goes. The form factor of some microelectronic devices can be smaller than that of handheld electronic devices such as the iPod

[0021] . Exemplary microelectronic devices can be integrated into various objects, which can include but are not limited to watches, rings, necklaces, straps, accessories for straps, headsets, accessories for shoes, virtual reality devices, glasses, other wearable electronic devices, accessories for sports equipment, accessories for fitness equipment, keychains, or any combination thereof. As an alternative, the electronic device 100 may not be portable at all and may be substantially stationary. TM As shown, for example, the electronic device 100 may include a processor 102, a memory 104, a communication component 106, a power supply 108, an input component 110, an output component 112, an antenna 116, and a near-field communication (“NFC”) component 120. The electronic device 100 may also include a bus 118, which may provide one or more wired or wireless communication links or paths for transmitting data and / or power to, from, or between the various other components of the device 100. In some embodiments, one or more components of the electronic device 100 may be combined or omitted. Additionally, the electronic device 100 may include other components not combined or

[0022] not included in Figure 1 . For example, the electronic device 100 may include motion sensing circuitry, a compass, any other suitable components, or Figure 1 several instances of the components shown in Figure 1 . For clarity, only one component of each component is shown in Figure 1 .

[0023] The memory 104 may include one or more storage media, such as including a hard disk drive, flash memory, persistent memory such as read-only memory (“ROM”), semi-persistent memory such as random access memory (“RAM”), any other suitable type of storage component, or any combination thereof. The memory 104 may include cache memory, which may be one or more different types of memory for temporarily storing data for electronic device applications. The memory 104 may be fixedly embedded within the electronic device 100 or may be incorporated onto one or more suitable types of cards (e.g., subscriber identity module (“SIM”) card or secure digital (“SD”) memory card) that can be repeatedly inserted into and removed from the electronic device 100. The memory 104 may store media data (e.g., music files and image files), software (e.g., for implementing functions on the device 100), firmware, preference information (e.g., media playback preferences), lifestyle information (e.g., food preferences), exercise information (e.g., information obtained through an exercise monitoring device), transaction information (e.g., information such as credit card information), wireless connection information (e.g., information that enables the device 100 to establish a wireless connection), subscription information (e.g., information tracking podcasts or TV shows or other media subscribed to by the user), contact information (e.g., phone numbers and email addresses), calendar information, any other suitable data, or any combination thereof.

[0024] A communication component 106 may be provided to allow the device 100 to communicate with one or more other electronic devices or servers using any suitable communication protocol. For example, the communication component 106 may support Wi-Fi (e.g., 802.11 protocol), ZigBee (e.g., 802.15.4 protocol), WiDi TM , Ethernet, Bluetooth TM , Bluetooth TM Low Energy (“BLE”), high-frequency systems (e.g., 900 MHz communication system, 2.4 GHz communication system, and 5.6 GHz communication system), infrared transmission control protocol / Internet protocol (“TCP / IP”) (e.g., any protocol used in each TCP / IP layer), stream control transmission protocol (“SCTP”), dynamic host configuration protocol (“DHCP”), hypertext transfer protocol (“HTTP”), BitTorrent TM , file transfer protocol (“FTP”), real-time transport protocol (“RTP”), real-time streaming protocol (“RTSP”), real-time control protocol (“RTCP”), remote audio output protocol (“RAOP”), actual data transfer protocol TM("RDTP"), User Datagram Protocol ("UDP"), Secure Shell Protocol ("SSH"), Wireless Distribution System ("WDS") bridging, any communication protocol that can be used by wireless phones, cellular phones, and personal email devices (e.g., Global System for Mobile Communications ("GSM"), GSM plus Enhanced Data Rates for GSM Evolution ("EDGE"), Code Division Multiple Access ("CDMA"), Orthogonal Frequency Division Multiple Access "OFDMA"), High-Speed Packet Access ("HSPA", multi-band, etc.), any communication protocol that can be used by low-power wireless personal area network ("6LoWPAN") modules, any other communication protocol, or any combination thereof. The communication component 106 may also include or be electrically coupled to any suitable transceiver circuit (e.g., a transceiver circuit or antenna 116 via bus 118), which may enable the device 100 to be communicatively coupled to another device (e.g., a host computer or accessory device) and communicate with that other device wirelessly or via a wired connection (e.g., using a connector port). The communication component 106 may be configured to determine the geographical location of the electronic device 100. For example, the communication component 106 may utilize the Global Positioning System ("GPS") or may utilize a positioning system that can use cell tower location technology or Wi-Fi technology for area or site range positioning.

[0025] Power supply 108 may include any suitable circuitry for receiving and / or generating electrical power and for providing such power to one or more other components of electronic device 100. For example, power supply 108 may be coupled to an electrical grid (e.g., when device 100 is not acting as a portable device or when charging the device's battery using power generated at a power plant at a power outlet). As another example, power supply 108 may be configured to generate electrical power from a natural source (e.g., using solar cells for solar power). As another example, power supply 108 may include one or more batteries for providing electrical power (e.g., when device 100 is acting as a portable device). For example, power supply 108 may include a battery (e.g., a gel, nickel metal hydride, nickel cadmium, nickel hydrogen, lead acid, or lithium ion battery), an uninterruptible or continuous power supply (“UPS” or “CPS”), and one or more of circuitry for processing electrical power received from a power source (e.g., electrical power generated by a power plant and delivered to a user via a power outlet or other means). Power supply 108 may provide electrical power as alternating current or direct current and may process the power to convert the power or limit the received power to have specific characteristics. For example, the power may be transformed into direct current or out of direct current and constrained to one or more values of average power, effective power, peak power, energy per pulse, voltage, current (e.g., measured in amperes), or any other characteristic of the received power. Power supply 108 may be used, for example, to request or provide a specific amount of electrical power at different times based on the needs or requirements of electronic device 100 or a peripheral device that may be coupled to electronic device 100 (e.g., when charging a battery, requesting more power than when the battery is charged).

[0026] One or more input components 110 may be provided to allow a user to interact with or connect to device 100. For example, input components 110 may take various forms, including but not limited to a touchpad, a dial, a click wheel, a scroll wheel, a touch screen, one or more buttons (e.g., a keyboard), a mouse, a joystick, a trackball, a microphone, a camera, a scanner (e.g., a barcode scanner or any other suitable scanner for obtaining product identification information from a code, such as a barcode, a QR code, etc.), a proximity sensor, a light detector, a motion sensor, a biometric sensor (e.g., a fingerprint reader or other feature recognition sensor, which may work in conjunction with a feature processing application that electronic device 100 may access for authenticating a user), and combinations thereof. Each input component 110 may be configured to provide one or more dedicated control functions for making selections or issuing commands associated with operating device 100.

[0027] The electronic device 100 may also include one or more output components 112 (e.g., graphical information, auditory information, and / or tactile information) that can present information to a user of the device 100. For example, the output components 112 of the electronic device 100 may take various forms, including but not limited to audio speakers, headphones, audio line outputs, visual displays, antennas, infrared ports, cleaning rollers, vibrators, or combinations thereof.

[0028] As a specific example, the electronic device 100 may include a display output component as the output component 112. Such a display output component may include any suitable type of display or interface for presenting visual data to the user. The display output component may include a display embedded in or coupled to the device 100 (e.g., a removable display). For example, the display output component may include a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a surface conduction electron emitter display (“SED”), a carbon nanotube display, a nanocrystal display, any other suitable type of display, or combinations thereof. As an alternative, the display output component may include a removable display or a projection system for providing content display on a surface remote from the surface of the electronic device 100, such as a video projector, a head-up display, or a three-dimensional (e.g., holographic) display. As another example, the display output component may include a digital viewfinder or a mechanical viewfinder such as the type found in a compact digital camera, a reflex camera, or any other suitable still camera or video camera. The display output component may include a display driver circuit, a circuit for driving the display driver, or both, and such a display output component may be used to display content (e.g., media playback information, an application screen for an application to be implemented on the electronic device 100, information about ongoing communication operations, information about incoming communication requests, a device operation screen, etc.) under the direction of the processor 102.

[0029] It should be noted that herein, one or more input components and one or more output components may sometimes be collectively referred to as input / output (“I / O”) components or an I / O interface (e.g., the input component 110 and the output component 112 as the I / O component or the I / O interface 114). For example, the input component 110 and the output component 112 may sometimes be a single I / O component 114 such as a touch screen, which can receive input information through user contact with the display screen and can also provide visual information to the user through the same display screen.

[0030] The processor 102 of the electronic device 100 may include any processing circuitry that can be used to control the operation and performance of one or more components of the electronic device 100. For example, the processor 102 may receive input from the input component 110 and / or drive output signals through the output component 112. AsFigure 1 As shown, the processor 102 can be used to run one or more applications such as application 103. Application 103 can include, but is not limited to, one or more operating system applications, firmware applications, media playback applications, media editing applications, NFC low-power mode applications, biometric processing applications, or any other suitable applications. For example, the processor 102 can load application 103 as a user interface program to determine how instructions or data received via the input component 110 or other components of the device 100 can manipulate the way information can be stored and / or provided to the user via the output component 112. Application 103 can be accessed by the processor 102 from any suitable source, such as from the memory 104 (e.g., via the bus 118) or from another device or server (e.g., via the communication component 106). The processor 102 can include a single processor or multiple processors. For example, the processor 102 can include at least one "general-purpose" microprocessor, a combination of general-purpose and special-purpose microprocessors, an instruction set processor, a graphics processor, a video processor, and / or associated chip sets and / or special-purpose microprocessors. The processor 102 can also include on-board memory for caching purposes.

[0031] The electronic device 100 can also include a near field communication ("NFC") component 120. The NFC component 120 can be any suitable proximity-based communication mechanism that can enable contactless transactions or communication 55 between the electronic device 100 and the terminal 10 (e.g., a payment terminal). The NFC component 120 can allow for short-range communication at a lower data rate (e.g., 424 kbps) and can comply with any suitable standards, such as ISO / IEC 7816, ISO / IEC 18092, ECMA-340, ISO / IEC 21481, ECMA-352, ISO 14443, and / or ISO 15693. As an alternative or in addition, the NFC component 120 can allow for short-range communication at a higher data rate (e.g., 560 Mbps) and can comply with any suitable standard such as TransferJet TM protocol. Communication between the NFC component 120 and the terminal 10 can occur within any suitable short-range distance between the device 100 and the terminal 10, such as in the range of approximately 2 centimeters to 4 centimeters, and can operate at any suitable frequency (e.g., 13.56 MHz). For example, such short-range communication of the NFC component 120 can occur via magnetic field induction, which can allow the NFC component 120 to communicate with other NFC devices and / or retrieve information from tags having radio frequency identification ("RFID") circuitry. The NFC component 120 can provide a way to collect merchant information, transmit payment information, and communicate with external devices (e.g., the terminal 10) in other ways.

[0032] The NFC component 120 may include any suitable module for implementing contactless proximity-based communication 55 between the electronic device 100 and the terminal 10. For example, as Figure 1 shown, the NFC component 120 may include an NFC device module 130, an NFC controller module 140, and an NFC memory module 150.

[0033] The NFC device module 130 may include an NFC data module 132, an NFC antenna 134, and an NFC booster 136. The NFC data module 132 may be configured to contain, route, or otherwise provide any suitable data that can be transmitted from the NFC component 120 to the terminal 10 as part of contactless proximity-based communication or NFC communication 55. In addition or alternatively, the NFC data module 132 is configured to contain, route, or otherwise receive any suitable data that can be received by the NFC component 120 from the terminal 10 as part of contactless proximity-based communication 55.

[0034] The NFC transceiver or NFC antenna 134 can be any suitable antenna or other suitable transceiver circuit that generally enables communication 55 from the NFC data module 132 to the terminal 10 and / or from the terminal 10 to the NFC data module 132. Thus, an NFC antenna 134 (e.g., a loop antenna) may be specifically provided to implement the contactless proximity-based communication capability of the NFC component 120.

[0035] Alternatively or in addition, the NFC component 120 may utilize the same transceiver circuit or antenna (e.g., antenna 116) as another communication component (e.g., communication component 106) of the electronic device 100 that can be used. For example, the communication component 106 may utilize the antenna 116 to implement Wi-Fi communication, Bluetooth between the electronic device 100 and another remote entity TMeither communication or GPS communication, while the NFC component 120 can utilize the antenna 116 to implement contactless proximity-based communication or NFC communication 55 between the NFC data module 132 of the NFC device module 130 and another entity (e.g., the terminal 10). In such embodiments, the NFC device module 130 can include an NFC booster 136 that can be configured to provide appropriate signal amplification for the data of the NFC component 120 (e.g., the data within the NFC data module 132), so that such data can be properly transmitted by the shared antenna 116 as communication 55 directed to the terminal 10. For example, before the antenna 116 (e.g., a non-loop antenna) can be properly enabled for contactless proximity-based communication or NFC communication 55 between the electronic device 100 and the terminal 10, the shared antenna 116 may require amplification from the booster 136 (e.g., transmitting NFC data using the antenna 116 may require more power compared to transmitting other types of data using the antenna 116).

[0036] The NFC controller module 140 can include at least one NFC processor module 142. The NFC processor module 142 can work in conjunction with the NFC device module 130 to enable, activate, permit, and / or otherwise control the NFC component 120 for transmitting NFC communication 55 between the electronic device 100 and the terminal 10. The NFC processor module 142 can exist as an independent component, can be integrated into another chipset, or can be integrated with a processor 102 such as part of a system-on-chip (“SoC”). As Figure 1 shown, the NFC processor module 142 of the NFC controller module 140 can be used to run one or more applications such as an NFC low-power mode or a wallet application 143 that can help determine the functionality of the NFC component 120. The application 143 can include, but is not limited to, one or more operating system applications, firmware applications, NFC low-power applications, or any other suitable applications accessible by the NFC component 120 (e.g., the application 103). The NFC controller module 140 can include one or more protocols, such as the Near Field Communication Interface and Protocol (“NFCIP-1”), for communicating with another NFC device (e.g., the terminal 10). These protocols can be used to adjust the communication speed and specify one of the connected devices as the initiating device for controlling the near field communication.

[0037] The NFC controller module 140 can control the near-field communication mode of the NFC component 120. For example, the NFC processor module 142 can be configured to switch the NFC device module 130 between a reader / writer mode for reading information (e.g., communication 55) from an NFC tag (e.g., from the terminal 10) to the NFC data module 132, a peer-to-peer mode for exchanging data (e.g., communication 55) with another NFC-capable device (e.g., the terminal 10), and a card emulation mode that allows another NFC-capable device (e.g., the terminal 10) to read information (e.g., communication 55) from the NFC data module 132. The NFC controller module 140 can also be configured to switch the NFC component 120 between an active mode and a passive mode. For example, the NFC processor module 142 can be configured to switch the NFC device module 130 (e.g., in conjunction with the NFC antenna 134 or the shared antenna 116) between an active mode in which the NFC device module 130 can generate its own RF field and a passive mode in which the FC device module 130 can use load modulation to transmit data to another device (e.g., the terminal 10) that generates the RF field. Compared with the operation in such an active mode, the operation in such a passive mode can extend the battery life of the electronic device 100. The mode of the NFC device module 130 can be controlled based on the user's preference and / or based on the preference of the manufacturer of the device 100, which can be defined or otherwise specified by an application (e.g., application 103 and / or application 143) running on the device 100.

[0038] The NFC memory module 150 can operate in conjunction with the NFC device module 130 and / or the NFC controller module 140 to perform NFC communication 55 between the electronic device 100 and the terminal 10. The NFC memory module 150 can be embedded within the NFC device hardware or within an NFC integrated circuit (“IC”). The NFC memory module 150 can be tamper-resistant and can include at least a portion of a security element. For example, the NFC memory module 150 can store one or more applications (e.g., application 143) related to NFC communication that are accessible by the NFC controller module 140. Such applications can include, for example, financial payment applications, secure access system applications, loyalty card applications, and other applications, which can be encrypted. In some embodiments, the NFC controller module 140 and the NFC memory module 150 can independently or jointly provide a dedicated microprocessor system that can include an operating system, memory, an application environment, and security protocols dedicated to storing and executing sensitive applications on the electronic device 100. The NFC memory module 150 can be a part of the memory 106 or at least one dedicated chip specific to the NFC component 120. The NFC memory module 150 can reside on the SIM, on a dedicated chip on the motherboard of the electronic device 100, or as an external plug-in in a memory card. The NFC memory module 150 can be completely independent of the NFC controller module 140 and can be provided by different components of the device 100 and / or provided to the electronic device 100 by different removable subsystems.

[0039] The NFC memory module 150 may include one or more of an Issuer Security Domain (“ISD”) 152 and a Supplementary Security Domain (“SSD”) 154 (e.g., a Service Provider Security Domain (“SPSD”), a Trusted Service Manager Security Domain (“TSMSD”), etc.), and may be defined and managed by NFC specification standards (e.g., GlobalPlatform). For example, the ISD 152 may be part of the NFC memory module 150, where a Trusted Service Manager (“TSM”) or an issuing financial institution may store keys and / or other appropriate information therein for creating or otherwise providing (e.g., via the communication component 106) one or more credentials (e.g., credentials associated with various credit cards, bank cards, gift cards, charge cards, transportation passes, etc.) on the electronic device 100 for credential content management and / or security domain management. A particular Supplementary Security Domain (“SSD”) 154 (e.g., one of the SSDs 154-154b) may be associated with a particular credential (e.g., a particular credit card credential or a particular public transportation card credential) that may provide particular privileges or payment permissions to the electronic device 100. Each SSD 154 may have its own manager key 155 for its own application or applet 153, which needs to be activated to enable the particular credential of that SSD 154 to be used as NFC communication 55 by the NFC device module 130. For example, a particular SSD 154 may be associated with a particular credit card credential. However, the particular credential may only be used as NFC communication 55 for transmission by the NFC component 120 to the terminal 10 (e.g., the particular credential may only be accessible by the NFC data module 132) when the particular applet 153 of that particular SSD 154 has been enabled or otherwise activated or unlocked for such use. As described below, security features may be provided to enable the use of the NFC component 120, which may be particularly useful when transmitting payment information such as credit card information or bank account information to the terminal 10. Such security features may also include a secure storage area that may have restricted access. For example, user authentication via personal identification number (“PIN”) entry or via user interaction with a biometric sensing sensor may be required to access the secure storage area. In some embodiments, some or all of the security features may be stored in the NFC memory module 150. Additionally, secure information such as authentication keys for communicating with the terminal 10 may be stored in the NFC memory module 150. In some embodiments, the NFC memory module 150 may include a microcontroller embedded within the electronic device 100.

[0040] The terminal 10 may include a reader for detecting, reading, or otherwise receiving NFC communication 55 from the electronic device 100 (e.g., when the electronic device 100 enters a specific distance or neighborhood D of the terminal 10). Thus, it should be noted that the NFC communication 55 between the terminal 10 and the electronic device 100 can be conducted wirelessly, such that a transparent "line of sight" between the corresponding devices is not required. As described above, the NFC device module 130 can be passive or active. When passive, the NFC device module 130 can be activated only when it is within the response range D of a suitable reader of the terminal 10. For example, the reader of the terminal 10 can emit a lower-power radio frequency wave field that can be used to power an antenna (e.g., the shared antenna 116 or the NFC dedicated antenna 134) utilized by the NFC device module 130, thereby enabling the antenna to transmit appropriate NFC communication information (e.g., credit card credential information) from the NFC data module 132 to the terminal 10 via the antenna 116 or the antenna 134 as the NFC communication 55. When active, the NFC device module 130 can incorporate or otherwise access a power source local to the electronic device 100 (e.g., the power source 108), which can enable the shared antenna 116 or the NFC dedicated antenna 134 to actively transmit NFC communication information (e.g., credit card credential information) from the NFC data module 132 to the terminal 10 via the antenna 116 or the antenna 134 as the NFC communication 55, rather than reflecting radio frequency signals as in the case of the passive NFC device module 130.

[0041] Although the NFC component 120 has been described in connection with near field communication, it should be understood that the component 120 can be configured to provide any suitable contactless proximity-based mobile payment or any other suitable type of contactless proximity-based communication 55 between the electronic device 100 and the terminal 10. For example, the NFC component 120 can be configured to provide any suitable short-range communication, such as those involving electromagnetic coupling technology / electrostatic coupling technology.

[0042] The electronic device 100 may also have a housing 101 that can at least partially enclose one or more of the components of the device 100 to protect against debris and other deteriorating forces external to the device 100. In some embodiments, one or more of the components can be provided within its housing (e.g., the input component 110 can be a separate keyboard or mouse within its housing, which can communicate wirelessly or via a line with a processor 102 that can be provided within its own housing).

[0043] As Figure 2 shown, a specific example of the electronic device 100 can be a handheld electronic device such as an iPhone TM, wherein the housing 101 may allow access to various input components 110a - 110i, various output components 112a - 112c, and various I / O components 114a - 114d, through which the device 100 and the user and / or the surrounding environment may be connected to each other. The input component 110a may include a button, which when pressed, may cause the "home" screen or menu of the currently running application to be displayed by the device 100. The input component 110b may be a button for switching the electronic device 100 between a sleep mode and a wake mode or any other appropriate modes. The input component 110c may include two - position sliders, which may disable one or more of the output components 112 in a specific mode of the electronic device 100. The input components 110d and 110e may include buttons for increasing and decreasing the volume output of the electronic device 100 or any other characteristic output of the output component 112. Each of the input components 110a - 110e may be a mechanical input component such as a dome switch, a slide switch, a control panel, a keypad, a knob, a roller, or a button supported by any other appropriate form.

[0044] The output component 112a may be a display for displaying a visual user interface or a graphical user interface ("GUI") 180, which may allow the user to interact with the electronic device 100. The GUI 180 may include various layers, windows, screens, templates, elements, menus, and / or other components of the currently running application (e.g., application 103 and / or application 143) that may be displayed in all or some areas of the display output component 112a. One or more user input components 110a - 110i may be used to navigate in the GUI 180. For example, one user input component 110 may include a roller, which may allow the user to select one or more graphical elements 182 of the GUI 180. Icons 182 may also be selected via the touch - screen I / O component 114a, which may include the display output component 112a and an associated touch - input component 110f. Such touch - screen I / O components 114a may employ any suitable type of touch - screen input technology, such as but not limited to resistive, capacitive, infrared, surface acoustic wave, electromagnetic, or near - field imaging. In addition, the touch - screen I / O component 114a may employ single - point input sensing or multi - point (e.g., multi - touch) input sensing.

[0045] Icon 182 may represent various layers, windows, screens, templates, components, and / or other parts that may be displayed in some or all areas of display component 112a upon user selection. Additionally, selection of a particular icon 182 may result in a hierarchical navigation process. For example, selection of a particular icon 182 may yield a new screen of GUI 180, which may include one or more additional icons or other GUI elements of the same application or a new application associated with icon 182. A text indicator 181 may be displayed on or near each icon 182 to facilitate user interpretation of each graphical element icon 182. It should be appreciated that GUI 180 may include various components arranged in a hierarchical and / or non-hierarchical manner. Upon selection of a particular icon 182, device 100 may be configured to open a new application associated with that icon 182 and display a corresponding screen of GUI 180 associated with that application. For example, upon selection of a particular icon 182 labeled with the NFC LOW POWER MODE text indicator 181 (i.e., particular icon 183), device 100 may launch or otherwise access a particular NFC low power mode application or wallet mode application (e.g., application 143) and may display a screen of a particular user interface, which may include one or more tools or features for interacting with NFC component 120 in a particular manner (e.g., see Figures 4A - 4G , for a specific example of such a display of GUI 180 during NFC low power mode). For each application, the screen may be displayed on display output component 112a and may include various user interface elements. In addition to or alternatively to this, for each application, various other types of non-visual information may be provided to the user via various other output components 112 of device 100.

[0046] Electronic device 100 may also include various other I / O components 114, which may allow communication between device 100 and other devices. I / O component 114b may be a connection port that may be configured to transfer data files and receive the data files from a remote data source such as a media file or a customer order file, and / or receive power from an external power source. For example, I / O component 114b may be a proprietary port such as the Lightning TM connector or the 30-pin dock connector from Apple Inc. of Cupertino, California. I / O component 114c may be a connection slot for receiving a SIM card or any other type of removable component. I / O component 114d may be a headphone interface for connecting an audio headphone, which may or may not include a microphone component. Electronic device 100 may also include at least one audio input component 110g such as a microphone and at least one audio output component such as an audio speaker.

[0047] The electronic device 100 may further include at least one haptic output component 112c (e.g., a roller), a camera and / or a scanner input component 110h (e.g., a video camera or a still camera and / or a barcode scanner or any other suitable scanner that can obtain product identification information from codes such as barcodes, QR codes, etc.), and a biometric input component 110i (e.g., a fingerprint reader or other feature recognition sensor that can work in conjunction with a feature processing application, and the feature processing application can be accessed by the electronic device 100 for authenticating a user). As Figure 2 shown, at least a portion of the biometric input component 110i may be incorporated under the input component 110a of the device 100 or otherwise combined therewith. For example, the biometric input component 110i may be a fingerprint reader that can be configured to scan the fingerprint of a user's finger when the user interacts with the mechanical input component 110a by pressing the input component 110a with a finger. As another example, the biometric input component 110i may be a fingerprint reader that can be combined with the touch input component 110f of the touch screen I / O component 114a, such that the biometric input component 110i is configured to scan the fingerprint of a user's finger when the user interacts with the touch screen input component 110f by pressing or sliding along the touch screen input component 110f with a finger. In addition, as previously described, the electronic device 100 may further include an NFC component 120, and the terminal 10 may communicatively access the NFC component 120 via the antenna 116 and / or the antenna 134 ( Figure 2 not shown in the figure). The NFC component 120 may be at least partially located within the housing 101, and a mark or symbol 121 provided outside the housing 101 may identify the approximate location of one or more antennas associated with the NFC component 120 (e.g., the approximate location of the antenna 116 and / or the antenna 134).

[0048] For the convenience of the following discussion regarding the operation of the electronic device 100 during NFC low-power operating mode for managing near-field communication (e.g., communicating with the terminal 10 55), reference is made to a schematic diagram of the NFC management subsystem 301 of the electronic device 100 (e.g., as Figure 3 shown in the figure) and a front view 400a - 400g of a screen that may represent a graphical user interface of the electronic device 100 during such near-field communication management (e.g., as Figures 4A - 4G shown in the figure). A wide range of graphical elements and visual schemes may be utilized to implement the described operations. Therefore, Figures 4A - 4G the embodiments are not intended to be limited to the exact user interface specifications adopted herein. Instead, the embodiments may include a wide range of user interface styles.

[0049] Figure 3FIG. 0 shows a schematic diagram of a near field communication management subsystem 301 of an electronic device 100, which can be provided to manage near field communication during different modes of the electronic device 100. For example, the NFC management subsystem 301 can determine when to utilize the low power NFC mode of the electronic device 100 and / or how to manage the NFC component 120 during such low power NFC mode (e.g., how to make the credentials of the NFC component 120 appropriately secure and / or appropriately accessible during such low power NFC mode).

[0050] The electronic device 100 can be configured to operate according to different power management modes for controlling and managing the power consumption of various components of the device 100. For example, as Figure 3 shown, the NFC management subsystem 301 can include a mode detection module 310, which is configured to determine when to enter a specific one of the various power management modes of the electronic device 100. For example, the mode detection module 310 can be configured to determine when to enter a specific one of many possible power management modes, such as the low power NFC mode of the electronic device 100. Specifically, the mode detection module 310 can be configured to switch the operation of the electronic device 100 between various specific power management modes for reducing power consumption when the device 100 is not connected to a remote power source (e.g., when the power supply 108 is not plugged into a wall socket). For example, the operation of the device 100 in a specific power management mode can prevent the device 100 from performing unnecessary power-intensive processes when the device 100 is powered by a battery with a remaining power below a specific threshold.

[0051] As Figure 3 shown, the mode detection module 310 can be configured to probe or otherwise receive power level data 307 from the power supply 108, where the power level data 307 can indicate the remaining power in the power supply 108 (e.g., when the power supply 108 may be a battery whose power level may decrease during use). When the mode detection module 310 detects that the received power level data 307 of the power supply 108 has dropped below a specific threshold (e.g., below a 3.4 volt voltage threshold or any other appropriate threshold), the mode detection module 310 can be configured to generate a switching command 311, which can be configured to switch the electronic device 100 to the low power NFC power management mode (e.g., the "wallet" power management mode). For example, as Figure 3 shown, when the mode detection module 310 detects that the received power level data 307 indicates a specific characteristic of the power supply 108 (e.g., the power supply 108 has dropped below a specific power threshold), the mode detection module 310 can be configured to generate a switching command 311 and provide the switching command 311 to a switching application module 320 of the NFC management subsystem 301.

[0052] As another example of an initiation event for the low-power NFC mode or wallet mode that can be detected by the mode detection module 310, the mode detection module 310 can be configured to receive input mode selection data 309 from the input component 110 (e.g., one or more of the input components 110a - 110i). Such input mode selection data 309 can be any suitable data generated by the input component 110 that can indicate a desire to enter such a wallet mode. For example, the input mode selection data 309 can indicate that the user uses Figure 2 the touchscreen input component 110f of the I / O component 114a to select the "NFC LOWPOWER MODE" icon 183 of the GUI 180, which can be recognized by the mode detection module 310 as an initiation event for entering the wallet mode. Thus, when the mode detection module 310 receives such specific input mode selection data 309, the mode detection module 310 can be configured to generate a switching command 311 and provide the switching command 311 to the switching application module 320 of the NFC management subsystem 301. Thus, in addition to or as an alternative to the device 100 switching to the wallet power management mode when the power supply 108 is below a specific power threshold, such a low-power NFC power management mode can be entered when the user decides or during any other suitable condition.

[0053] Regardless of why the mode detection module 310 generates the switching command 311 and transmits the switching command 311 to the switching application module 320 (e.g., in response to specific received power level data 307 and / or in response to specific received input mode selection data 309), the switching application module 320 can be configured to switch the electronic device 100 to the low-power NFC mode or wallet power management mode in response to receiving such a switching command 311. The switching process can include: the switching application module 320 generating one or more disabling commands and transmitting the disabling commands to one or more components of the device 100 to at least partially turn off such components, remove power from such components, or otherwise at least partially disable at least one function of the component. This can reduce the power consumption of one or more components of the device 100 and / or can at least partially disable one component, some components, or all components of the device 100 that are unnecessary for at least the initial operation of the device 100 in the wallet power management mode.

[0054] For example, in response to receiving a switching command 311, as part of a switching process to a wallet power management mode, the switching application module 320 generates an NFC disable command 321 and transmits the NFC disable command to the NFC component 120. The NFC disable command 321 can be configured to be received by any suitable element of the NFC component 120 such that, in response to receiving the command 321, at least one credential that could be previously enabled by the NFC component 120 before receiving the command 321 is disabled. As a specific example, the command 321 can disable the NFC antenna 134 and / or the booster 136 of the NFC device module 130 when the NFC component 120 receives the command 321, such that after such a disablement, the NFC component 120 does not transmit any NFC communication 55 to the terminal 10. As another example, the command 321 can disable the first applet 153 of the first SSD 154 of the NFC memory module 150 when the NFC component 120 receives the command 321, such that after such a disablement, the NFC component 120 does not transmit any NFC communication 55 associated with the credential of the first applet 153 to the terminal 10. In some embodiments, the command 321 can disable each applet 153 of each SSD 154 of the NFC memory module 150 when the NFC component 120 receives the command 321, such that after such a disablement, the NFC component 120 does not transmit any NFC communication 55 associated with any credential of any applet 153 of any SSD 154 to the terminal 10. However, in other embodiments, when the NFC component 120 receives the command 321, the command 321 can only disable some specific applets 153 of some SSDs 154 of the NFC memory module 150, such that after such a disablement, the NFC component 120 may not transmit any NFC communication 55 associated with the credentials of those specific applets (e.g., credit card credentials that can guarantee a high security level) to the terminal 10, but such that after such a disablement, the NFC component 120 can transmit other NFC communication 55 associated with the credentials of other specific applets (e.g., simple transportation system credentials such as for a subway, but this may not guarantee a high security level) to the terminal 10. When received by the NFC component 120, the NFC disable command 321 can be configured to turn off the NFC component, power down the NFC component 120, or otherwise at least partially disable at least one function of the NFC component.

[0055] In addition to generating the NFC disable command 321 or alternatively, the switching application module 320 can be configured to switch the electronic device 100 to a low-power NFC or wallet power management mode by generating and transmitting an output component disable command 323 to at least one output component 112 (e.g., at least one of the output components 112a - 112c). When received by the output component 112, the output component disable command 323 can be configured to turn off the output component, power down from the output component 112, or otherwise at least partially disable at least one function of the output component. For example, as Figure 4A shown, in response to the display output component 112a receiving such a disable command 323, the display output component 112a can be configured to provide a blank screen 400a (e.g., the display output component 112a can be turned off), which is contrary to the Figure 2 screen 200a that may include various icons 182. As another alternative, as shown in the screen 400a, it can include only a simple message or other elements 401 / 402, which can indicate that the device 100 is now in the wallet power management mode (e.g., the display of the simple elements 401 / 402 of such a screen 400a can be static and / or can exist only on a part of the display output component 112a, which may require less power than providing the display of the screen 200a). As another alternative, a simple icon 401a can be displayed on the screen 400a (and Figures 4B - 4G all other screens 400b - 400g), which can indicate to the user that the device 100 is now in the wallet power management mode rather than in another mode that may have other functions.

[0056] Similarly, the switching application module 320 can be configured to switch the electronic device 100 to a low-power NFC or wallet power management mode by generating and transmitting an input component disable command 325 to at least one input component 110 (e.g., one or more of the input components 110a - 110i). When received by the input component 110, the input component disable command 325 can be configured to turn off the input component, power down from the input component 110, or otherwise at least partially disable at least one function of the input component. Similarly, the switching application module 320 can be configured to switch the electronic device 100 to a low-power NFC or wallet power management mode by generating and transmitting an application disable command 327 to the processor 102. When received by the processor 102, the application disable command 327 can be configured to close one or more application programs currently being run by the processor 102 or otherwise at least partially disable them (e.g., force quit all non-native application programs running on the device 100 before the application disable command 327 is generated). This can reduce the power consumption of the processor 102 associated with switching to the wallet mode. Additionally, in addition to or alternatively, the switching application module 320 can be configured to switch the electronic device 100 to a low-power NFC or wallet power management mode by generating and transmitting one or more additional disable commands (not shown) to at least one other component of the device 100 (e.g., the memory 104, the communication component 106, the antenna 116, etc.), such that when received by the device component, the component disable command can be configured to turn off the device component, power down from the device component, or otherwise at least partially disable at least one function of the device component.

[0057] Accordingly, the switching application module 320 may be configured to initiate a transition of the electronic device 100 to the wallet power management mode by generating and transmitting one or more disabling commands (e.g., disabling commands 321, 323, 325, 327, etc.), which are configured to turn off, power down, or otherwise at least partially disable one component, some components, or all components of the device 100 that are unnecessary for at least the initial operation of the device 100 while in the wallet power management mode. For example, as described above, one or more disabling commands of the switching application module 320 may be configured to at least partially turn off one or more input components 110, one or more output components 112, the processor 102, or at least one or more application programs running by the processor 102, at least some of the memory 104, at least some or all of the communication components 106, the antenna 116, and / or some or all of the NFC components 120. When operating at least initially in such a wallet mode, the electronic device 100 may be configured to avoid powering or otherwise enabling certain device components that are unnecessary for the security management of the NFC components 120. For example, in response to receiving one or more disabling commands from the switching application module 320, the electronic device 100 may turn off the hard drive (e.g., the memory 104), dim or turn off the display (e.g., the output component 112a), place the processor (e.g., the processor 102) in a low-power "sleep" or "hibernate" mode, and / or fully or partially disable the NFC components 120. Some or all of the power management settings of the NFC management subsystem 301 may be set automatically or by the user of the device 100 (e.g., the user may define a duration and / or conditions before the device 100 switches between specific power management modes and / or at least partially disable or turn off components when switching between different power management modes such as the wallet mode). By forcing the electronic device 100 to operate in such a wallet mode, the switching application module 320 may ultimately allow the electronic device 100 to communicate with the NFC components 120 securely and in an efficient manner 55 (e.g., until the power supply 108 is no longer able to power the electronic device 100 to operate in this mode).

[0058] Accordingly, at least certain modules of the NFC management subsystem 301 may be configured as a power management unit (“PMU”) that may be coupled to at least one power source such as, for example, power source 108. Such a PMU may include a microcontroller and may be configured to govern the power functions of device 100. Such a PMU may include its own memory (e.g., loaded with software and / or firmware), a processor with input / output functionality and a timer, and one or more converters for measuring the power supplied by power source 108. Additionally, in addition to or alternatively, such a PMU may include a backup power source that can power components of the NFC management subsystem 301 even when device 100 is completely turned off, such as to maintain the current time of a real-time clock. Such a PMU may be responsible for coordinating certain functions of device 100, including but not limited to monitoring power connections and battery charging, controlling the power supplied to other components of device 100, turning off certain components of device 100 when idle or when not needed for what is considered current normal operation of device 100, regulating the real-time clock of device 100, and controlling the various power management modes of device 100. Connect a battery control circuit or power management stage component to the battery and to the baseband / firmware processor. The NFC management subsystem 301 provides one or more dedicated connections from such a PMU and / or from power source 108 to the various elements of the NFC component 120 (e.g., device module 130, controller module 140, and / or memory module 150). These additional connections may be provided so that the battery control circuit or power supply circuit can selectively power the various components of device 100, particularly the various components necessary for the terminal 10 to perform NFC communication.

[0059] When the switching application module 320 has received a switching command 311 from the mode detection module 310 and then generates and transmits one or more disable commands (e.g., disable commands 321, 323, 325, etc.) for at least partially disabling one component, some components, or all components of device 100 that were initially operating in the wallet power management mode and are unnecessary for device 100, the switching application module 320 may also be configured to generate and transmit a start command 329 to the NFC low power mode control application module 330 of the NFC management subsystem 301. In response to receiving the start command 329, the control application module 330 may be configured to start and run at least one application program (e.g., application program 143) that may be specifically adapted for properly managing and / or otherwise controlling the electronic device 100 in the low power NFC or wallet power management mode. Accordingly, the operation of device 100 in such low power NFC or wallet power management modes may be based on one or more application programs accessible to the electronic device 100 (e.g., application program 143) and / or may be based on any input instructions received by the electronic device 100 (e.g., via input component 110) that can control such application programs.

[0060] When the control application module 330 receives a start command 329 for managing the device 100 in the wallet power management mode, the NFC component 120 may initially be configured by the NFC disable command 321 to be in a disabled antenna mode (e.g., where the antenna 116 and / or the antenna 134 cannot receive or transmit any NFC communication 55 (e.g., where the booster 136 is disabled such that the antenna 116 cannot transmit the NFC communication 55)). As an alternative, when the control application module 330 receives a start command 329 for managing the device 100 in the wallet power management mode, the NFC component 120 may initially be configured by the NFC disable command 321 to be in a passive antenna mode (e.g., where the antenna 116 and / or the antenna 134 may be passively enabled by the terminal 10 for NFC communication when within the response range D of the terminal 10). As yet another alternative, when the control application module 330 receives a start command 329 for managing the device 100 in the wallet power management mode, the NFC component 120 may initially be configured by the NFC disable command 321 to be in an active antenna mode (e.g., where the antenna 116 and / or the antenna 134 may be actively enabled for the NFC communication of the electronic device 100 itself (e.g., via the power supply 108)). It should be understood that when the NFC component 120 is initially configured by the NFC disable command 321 to be in the passive antenna mode or the active antenna mode, one or more other elements of the NFC component 120 (e.g., the applet 153 of one or more SSDs 154) may initially be disabled by the NFC disable command 321 to prevent the passive / active antenna from transmitting the credentials of the NFC component 120 to the terminal 10 as the communication 55.

[0061] Continuing with the embodiment in which the NFC component 120 can initially be configured to be in the antenna-disabled mode by the NFC disable command 321, the electronic device 100 may not be able to detect when the device 100 is within the NFC response range D of the terminal 10 (e.g., via the antenna 116 and / or via the antenna 134) and may not be able to perform NFC communication 55 with the terminal 10. Instead, the control application module 330 can be configured to wait for one or more input commands that indicate that the user desires to interact with the device 100 for potentially enabling the NFC component 120 for NFC communication 55. For example, once initially switched to the wallet mode, the device 100 can provide the screen 400a (e.g., a blank screen or a turned-off display 112a) and can wait for an appropriate UI unlock input command 331a from any suitable input component 110. Such an appropriate unlock input command 331a can be any input command that can be received by the input component 110 to indicate that the user desires to interact with the device 100 in the wallet mode for potentially enabling at least a portion of the NFC component 120. For example, the UI unlock input command 331a can be a simple user interaction with the home button input component 110a. In such embodiments, all other input components 110 of the device 100 may initially be disabled by the input command disable command 325, except for the input component 110a that may be frequently queried by the control application module 330 to detect such UI unlock input commands 331a. This allows the device 100 to use as little power as possible with respect to its input components 110 while still enabling the user to interact with the device 100 during the wallet mode, which may indicate that the user may desire to enable at least a portion of the NFC component 120 for use during the wallet power management mode. It should be understood that the control application module 330 can be configured to detect any suitable user interaction via any suitable input component 110 or any suitable combination of interactions via any suitable combination of input components 110 as an acceptable UI unlock input command 331a. As Figure 4A shown, the initial wallet mode screen 400a can include a message 402 that can prompt the user to provide an appropriate UI unlock input command 331a for utilizing the wallet power management mode, where such a message can assure the user that the device 100 is in the wallet mode and is not completely turned off. As an alternative, the initial wallet mode screen 400a can be blank and / or the display output component 112a can be completely turned off.

[0062] Once an acceptable UI unlock input command 331a has been received by the control application module 330, the control application module 330 can provide the user with various options for utilizing the device 100 in various ways while operating in the wallet power management mode. For example, as Figure 3As shown, the control application module 330 may generate and transmit an acknowledgement UI unlock command 333a to at least one output component 112 of the device 100 in response to receiving an acceptable UI unlock input command 331a. The acknowledgement UI unlock command 333a may be received by the output component 112 and may configure the output component 112 to prompt the user to confirm that they wish to interact with the device 100 to potentially utilize the NFC component 120 (e.g., acknowledge the acceptable UI unlock input command 331a). For example, as Figure 4B shown, the output display component 112a may be configured to provide a screen 400b in response to receiving the UI unlock command 333a from the control application module 330. The screen 400b may prompt the user to interact with the device 100 in one or more ways to confirm that they wish to potentially utilize the NFC component 120. As shown, the screen 400b may include a prompt 403 that may request the user to slide an element along a specific path on the screen 400b. Thus, the acknowledgement UI unlock command 333a may also be received by the input component 110f of the I / O component 114a to enable such a user to interact with the input component 110f of the I / O component 114a if the input component 110f has previously been disabled (e.g., by the command 325). It should be understood that the acknowledgement UI unlock command 333a may be received and configured by any suitable combination of the output components 112 other than the display output component 112a to prompt the user to confirm their UI unlock command 331a. For example, the acknowledgement UI unlock command 333a may be received by the audio speaker output component 112b and may be configured to audibly ask the user to confirm their UI unlock command 331a.

[0063] In response to the acknowledgement UI unlock command 333a prompting the user to confirm their UI unlock command 331a via the output component 112, the input component 110 may be configured to receive and transmit to the control application module 330 an acknowledgement such as UI unlock acknowledgement data 331b. For example, the user may slide an element along a specific path on the screen 400b such that the touch input component 110f of the I / O component 114a can transmit the UI unlock acknowledgement data 331b to the control application module 330. Any other suitable input component 110 (e.g., the microphone input component 110g) may be configured to receive and transmit to the control application module 330 suitable UI unlock acknowledgement data 331b (e.g., the user's voice command). As an alternative, if no UI unlock acknowledgement data 331b is received (e.g., after a specific period of time after receiving the data 331a), the control application module 330 may once again return to the screen 400a (e.g., the state where the user must provide a new appropriate UI unlock input command 331a).

[0064] Once acceptable UI unlock confirmation data 331b is received, the control application module 330 can be configured to provide the user with the ability to authenticate the right to access the NFC component 120 of the device 100. For example, as Figure 3 shown, in response to receiving acceptable UI unlock confirmation data 331b, the control application module 330 can generate and transmit an NFC component authentication request command 333b to at least one output component 112 of the device 100. The NFC component authentication request command 333b can be received by the output component 112 and can configure the output component 112 to prompt the user to provide appropriate authentication information for the device 100 that can grant the user the right to enable at least a portion of the NFC component 120 in the wallet power management mode. For example, as Figure 4C shown, the NFC component authentication request command 333b can be received by the display output component 112a and can configure the display output component 112a to provide the user with a screen 400c. The screen 400c can include a turn off device option 405, an exit wallet mode option 407, a cancel authentication option 409, and / or an authentication prompt 411. The user's selection of the turn off device option 405 can cause the control application module 330 to completely turn off the device 100 (e.g., by transmitting a shutdown command 335 to the power supply 108). The user's selection of the exit wallet mode option 407 can cause the control application module 330 to return to the previous power management mode of the device 100 (e.g., by transmitting a wallet mode exit command 337 to the switching application module 320). And the user's selection of the cancel authentication option 409 can cause the control application module 330 to provide the screen 400a again and / or wait for another acceptable UI unlock input command 331a.

[0065] The authentication prompt 411 may include one or more appropriate NFC component authentication options that a user may follow to attempt to authenticate their general use of the NFC component 120 (e.g., one or more NFC component authentication options 413 and 417). The NFC component authentication option 413 may prompt the user to input using a biometric sensor input component of the device 100 (e.g., the sensor input component 110i) for authenticating that the user has the right to access the NFC component 120. For example, the biometric sensor input component 110i may include a fingerprint reader or other feature recognition device and may work in conjunction with a feature handler accessible by the control application module 330 (e.g., the application 143). The NFC component authentication option 417 may provide a virtual keyboard or other data input mechanism that the user may use to input a personal identification number (“PIN”) or other appropriate code for authenticating that the user has the right to access the NFC component 120. Various other authentication options may be provided by the prompt 411, which may itself be provided by any appropriate output component other than the display output component 112a (e.g., the authentication prompt may be provided to the user via the audio speaker output component 112b, which audibly requests the user to use the biometric sensor or input an appropriate code or password that may cause the display output component 112a to be turned off).

[0066] The user may respond to the authentication prompt 411 for NFC component authentication information by providing any appropriate NFC component user authentication data 331c to the control application module 330 via any appropriate input component 110 or any combination of appropriate input components 110. For example, the user may respond to the NFC component authentication option 413 by providing NFC component user authentication data 331c to the control application module 330 via user interaction with the biometric sensor input component 110i (e.g., by swiping their finger across the fingerprint scanner input of the component 110i). As another example, the user may respond to the NFC component authentication option 417 by providing NFC component user authentication data 331c to the control application module 330 via user interaction with the touch input component 110f of the I / O component 114a (e.g., by inputting a PIN or other code via Figure 4C the virtual keyboard). It should be understood that the NFC component user authentication data 331c may be provided via any appropriate input component 110 or any combination of appropriate input components 110 (e.g., the NFC component user authentication data 331c may be provided by the user pressing one or more mechanical input components 110a - 110e in a specific order for a specific duration or speaking a specific phrase into the microphone input component 110g that may cause the display output component 112a to be turned off).

[0067] The control application module 330 may be configured to analyze any received NFC component user authentication data 331c to determine whether the user is indeed authorized to enable the NFC component 120 for NFC communication 55 when the device 100 is in the wallet power management mode. This operation may be performed by comparing any received NFC component user authentication data 331c with a table of authentication information associated with the NFC component 120. For example, the received NFC component user authentication data 331c may be compared with information associated with the general authentication of the ISD 152 of the NFC component 120, as opposed to the specific authentication of a specific applet 153 of a specific SSD 154.

[0068] Once acceptable NFC component user authentication data 331c is received, the control application module 330 may be configured to determine whether there are multiple credentials available for the NFC component 120 and, if so, provide the user with the ability to select from the multiple credentials that can be used by the NFC component 120 for use during the wallet power management mode. For example, as Figure 1 shown, the memory module 150 may include a first SSD 154, a second SSD 154a, and a third SSD 154b, each of which may be associated with a different credential provided on the NFC component 120. In such embodiments, in response to receiving acceptable NFC component user authentication data 331c, the control application module 330 may be configured to enable the user to select from the three credentials of the SSDs 154 - 154b. As Figure 3 shown, in response to receiving acceptable NFC component user authentication data 331c, the control application module 330 may generate and transmit an NFC credential selection request command 333c to at least one output component 112 of the device 100. The NFC credential selection request command 333c may be received by the output component 112 and may configure the output component 112 to prompt the user to provide any appropriate selection information for the device 100 that may indicate the user's selection of a specific available credential for use by the NFC component 120 in the wallet power management mode. For example, as Figure 4D shown, the NFC credential selection request command 333c may be received by the display output component 112a and may configure the display output component 112a to provide the user with a screen 400d. The screen 400d may include a first credential selection option 419, a second credential selection option 421, a third credential selection option 423, and / or a cancel credential selection option 425. The user's selection of the cancel credential selection option 425 may cause the control application module 330 to provide the screen 400c again and / or wait for appropriate NFC component user authentication data 331c.

[0069] If a user wishes to select a specific available credential for use, the user may select an appropriate option from among the provided credential selection options 419, 421, and 423. The credential selection options 419, 421, and 423 may prompt the user to utilize any appropriate input component 110 for selecting a specific credential option. For example, each of the provided credential selection options 419, 421, and 423 may provide a virtual button or other data input mechanism on the I / O component 114a that may be used by the user to select a specific credential. The credential selection options 419, 421, and 423 may be provided by any other appropriate output component other than the display output component 112a of the I / O component 114a (e.g., a list of credential selection options may be provided to the user via the audio speaker output component 112b, which may enable the display output component 112a to be turned off).

[0070] The user may respond to the credential selection options 419, 421, and 423 by providing any appropriate credential selection response data 331d to the control application module 330 via any appropriate input component 110 or any combination of appropriate input components 110. For example, the user may respond to the credential selection options 419, 421, and 423 by providing the credential selection response data 331d to the control application module 330 via a user interaction with the touch input component 110f of the I / O component 114a (e.g., by selecting Figure 4D one of the virtual buttons). It should be understood that the credential selection response data 331d may be provided via any appropriate input component 110 or any combination of appropriate input components 110 (e.g., the credential selection response data 331d that may each cause the display output component 112a to be turned off may be provided by the user pressing a specific one of the mechanical input components 110a - 110e that may be associated with a specific credential selection option and / or by the user swiping a specific finger across the biometric sensing sensor input component 110i that may be associated with a specific credential selection option).

[0071] The control application module 330 may be configured to analyze any received credential selection response data 331d to determine which available credentials the user wishes to use for NFC communication 55 when the device 100 is in the wallet power management mode. Once acceptable credential selection response data 331d for a specific available credential is received, the control application module 330 may be configured to provide the user with the ability to authenticate their right to access the selected credential. For example, as Figure 3As shown, in response to receiving acceptable credential selection response data 331d, control application module 330 may generate and transmit an NFC credential authentication request command 333d to at least one output component 112 of device 100. The NFC credential authentication request command 333d may be received by any output component 112 and may configure that output component 112 to prompt the user to provide appropriate authentication information for device 100 that grants the user the right to utilize the selected credentials with NFC component 120 in the wallet power management mode. For example, as Figure 4E shown, the NFC credential authentication request command 333d may be received by display output component 112a and may configure the display output component 112a to provide a screen 400e to the user. The screen 400e may include one or more appropriate NFC credential authentication options (e.g., one or more NFC credential authentication options 427 and 429) and / or a delete credential authentication option 431. The user's selection of the cancel credential authentication option 431 may cause the control application module 330 to provide the screen 400d again and / or wait for another acceptable credential selection response data 331d.

[0072] The NFC credential authentication option 427 may prompt the user to utilize a biometric sensor input component of device 100 (e.g., sensor input component 110i) for authenticating the user's right to access the selected credentials of NFC component 120. For example, the biometric sensor input component 110i may include a fingerprint reader or other feature recognition device and may work in conjunction with a feature handler accessible by the control application module 330 (e.g., application 103 and / or application 143). The NFC credential authentication option 429 may provide a virtual keyboard or other data input mechanism by which the user may input a personal identification number ("PIN") or other appropriate code for authenticating the user's right to access the selected credentials of NFC component 120. Various other authentication options may be provided by the NFC credential authentication options 427 and 429, which themselves may be provided by any appropriate output component other than the display output component 112a (e.g., an authentication prompt that may cause the display output component 112a to be turned off may be provided to the user via the audio speaker output component 112b).

[0073] The user can respond to the NFC credential authentication options 427 and / or 429 by providing any suitable NFC credential user authentication data 331e to the control application module 330 via any suitable input component 110 or any suitable combination of input components 110. For example, the user can respond to the NFC credential authentication option 427 by providing NFC component user authentication data 331e to the control application module 330 via user interaction with the biometric sensor input component 110i (e.g., by swiping their finger across the fingerprint scanner input of component 110i). As another example, the user can respond to the NFC credential authentication option 429 by providing NFC credential user authentication data 331e to the control application module 330 via user interaction with the touch input component 110f of the I / O component 114a (e.g., by entering a PIN or other code via the Figure 4E virtual keyboard). It should be understood that the NFC credential user authentication data 331e can be provided via any suitable input component 110 or any suitable combination of input components 110 (e.g., the NFC credential user authentication data 331e that can cause the display output component 112a to be turned off can be provided by the user pressing one or more mechanical input components 110a - 110e in a specific order for a specific duration).

[0074] The control application module 330 can be configured to analyze any received NFC credential user authentication data 331e to determine whether the user is indeed authorized to use the selected credential of the NFC component 120 for NFC communication 55 when the device 100 is in the wallet power management mode. This operation can be performed by comparing any received NFC credential user authentication data 331e with a table of authentication information associated with the selected credential of the NFC component 120. For example, the received NFC credential user authentication data 331e can be compared with the information associated with the SSD 154, which is associated with a specific selected credential.

[0075] Once acceptable NFC credential user authentication data 331e is received, the control application module 330 can be configured to enable the NFC component 120 to perform NFC communication 55 with the terminal 10 using the selected and authenticated credential. As Figure 3As shown, in response to receiving acceptable NFC credential user authentication data 331e, the control application module 330 can enable a selected authorized credential of the NFC component 120 for use by generating and transmitting an NFC enabling command 339 to the NFC component 120. For example, such an NFC enabling command 339 can be received by the NFC component 120 and can be configured to enable the NFC component 120 in any suitable manner for NFC communication 55 with the terminal 10 using the selected and authorized NFC credential (e.g., by unlocking an appropriate applet 153 and / or by providing appropriate data from the applet to the data module 132 and / or by enabling the antenna 116 (e.g., by powering up the booster 136), and / or by enabling the antenna 134 to enable the NFC component 120 to use the selected credential for NFC communication 55).

[0076] In addition, as Figure 3 shown, in response to receiving acceptable NFC credential user authentication data 331e, the control application module 330 can also generate and transmit NFC - supporting data 333e to at least one output component 112 of the device 100. The NFC - supporting data 333e can be received by the output component 112 and can configure the output component 112 to indicate to the user to enable the selected credential for NFC communication 55 in the wallet power management mode. For example, as Figure 4F shown, the NFC - supporting data 333e can be received by the display output component 112a and can configure the display output component 112a to provide the user with a screen 400f. The screen 400f can include credential enabling information 433 and / or a cancel credential enabling option 437. The user's selection of the cancel credential enabling option 437 can cause the control application module 330 to provide the screen 400d again while also disabling the currently enabled credential.

[0077] However, if the user does not select to cancel enabling the credential via the option 437, the control application module 330 can allow the NFC component 120 to potentially utilize the enabled credential for at least a certain duration (e.g., Figure 4FThe shown duration 435). Such a duration 435 can be based on the user's preferences and / or on the preferences of the manufacturer of device 100, and can be defined or otherwise specified by an application running on device 100 (such as application 103 and / or application 143). For example, the duration 435 can vary based on the security level associated with the enabled credential (e.g., the credit card credential of option 419 can grant a high security level and may require a shorter duration 435, while the ticket credential of option 421 can grant a medium security level and may require a medium duration 435, and the one-card pass credential of option 423 can grant a low security level and may require a longer or unlimited duration 435). Such a duration 435 can be timed by the control application module 330 and can be continuously updated as part of the credential enablement information 433 by the NFC-supporting data 333e (e.g., on screen 400f) to indicate to the user how long the credential can be re-enabled before being disabled again and to indicate how long it can be used for NFC communication 55.

[0078] If the enabled credential is actually used for NFC communication 55 by the NFC component 120 at any time during the duration 435 (e.g., in response to the terminal 10 receiving information associated with the enabled credential), then the NFC component 120 can generate and transmit NFC status information 341 to the control application module 330, as Figure 3 shown. Additionally, still as Figure 3 shown, in response to receiving such NFC status information 341, the control application module 330 can generate and transmit NFC usage data 333e to at least one output component 112 of device 100. The NFC usage data 333f can be received by the output component 112 and can configure the output component 112 to indicate to the user that the enabled credential has been used for NFC communication 55 in the wallet power management mode. For example, as Figure 4GAs shown, the NFC usage data 333f can be received by the display output component 112a and can configure the display output component 112a to provide the screen 400g to the user. The screen 400g can include credential usage information 439, and the credential usage information can include specific usage explanation information 441. Such usage information can be based on the NFC usage data 333f and can determine the NFC usage data 333f based on the NFC status information 341 provided by the NFC component 120. Such usage information 439 / 441 can indicate any appropriate characteristics of the enabled credential being used, such as the name of the credential, the usage time, the description of the terminal 10 participating in the usage, etc. Various other types of usage information 439 / 441 can be defined by the NFC usage data 333f, and all such usage information can be provided by any appropriate output component other than the display output component 112a (for example, an authentication prompt that can cause the display output component 112a to be turned off can be provided to the user via the audio speaker output component 112b).

[0079] In addition, if the enabled credential is not actually used as NFC communication 55 by the NFC component 120 during the duration 435, the NFC component 120 can also generate and transmit the NFC status information 341 to the control application module 330. Still as Figure 3 shown, in response to receiving such NFC status information 341 indicating non - usage, the control application module 330 can generate and transmit the NFC usage data 333f to at least one output component 112 of the device 100. The NFC usage data 333f can be received by the output component 112 and can configure the output component 112 to indicate to the user that the enabled credential has not been used for NFC communication 55 within the allowed duration 435. For example, as Figure 4G shown, the NFC usage data 333f can be received by the display output component 112a and can configure the display output component 112a to provide the screen 400g to the user. The screen 400g can include credential usage information 439 that can include specific non - usage explanation information 441. Such non - usage information can be based on the NFC usage data 333f and can determine the NFC usage data 333f based on the NFC status information 341 provided by the NFC component 120. Such non - usage information 439 / 441 can indicate non - usage (such as the allowed duration, etc.). Various other types of non - usage information 439 / 441 can be defined by the NFC usage data 333f, and all such non - usage information can be provided by any appropriate output component other than the display output component 112a (for example, an authentication prompt can be provided to the user via the audio speaker output component 112b, or provided haptically via the roller output component 112c, which can cause the display output component 112a to be turned off).

[0080] After using or not using the enabling credentials of the NFC component 120 in the wallet power management mode, and after providing NFC usage data 333f to at least one output component 112 of the device 100, the control application module 330 can cause the electronic device 100 to return to its state at the start of the wallet power management mode (e.g., by providing Figure 4A the screen 400a and operating the device 100 in a state where the user can provide a new appropriate UI unlock input command 331a).

[0081] The NFC component 120 can include only a single credential. In such cases, once the control application module 330 receives acceptable NFC component user authentication data 331c (e.g., as described in connection with Figure 4C ), rather than providing the user with the ability to select from multiple credentials (e.g., as described in connection with Figure 4D and 4E ), the control application module 330 can be configured to immediately enable the NFC component 120 by generating and transmitting an NFC enabling command 339 to the NFC component 120 and generating and transmitting NFC - supporting data 333e to at least one output component 112 of the device 100 to perform NFC communication 55 with the terminal 10 using the single credential (e.g., as described in connection with Figure 4F ).

[0082] In addition, in some embodiments, as described above, when the device 100 initially enters the wallet power management mode, the NFC component 120 can be initially configured by an NFC disabling command 321 to be in a passive antenna mode or an active antenna mode so that the antenna of the electronic device 100 can detect when the device 100 is within the NFC response range D of the terminal 10. In such embodiments, in addition to or as an alternative to waiting for an appropriate UI unlock input command 331a from any appropriate input component 110 (e.g., as described above in connection with Figure 4A ), the control application module 330 can also wait for an appropriate terminal to detect data 343 from the NFC component 120. As long as the NFC component 120 is in a passive antenna mode or an active antenna mode during the wallet power management mode of the device 100, and as long as such NFC component 120 also detects that the device 100 is within the NFC response range D of the terminal 10, such terminal detection data 343 can be generated and transmitted by the NFC component 120 to the control application module 330. In such cases, the control application module 330 can receive such terminal detection data 343, and then it can be configured to provide the user with the ability to authenticate their right to enable the NFC component 120 for NFC communication 55 with the detected terminal 10. For example, as Figure 3As shown, in response to receiving terminal detection data 343, the control application module 330 may generate and transmit an NFC component authentication request command 333b (e.g., as described above in connection with Figure 4C ), to prompt the user to provide any appropriate authentication information for the device 100 that can grant the user the right to enable at least a portion of the NFC component 120 in the wallet power management mode. Thus, in some embodiments of wallet mode operation, in response to the NFC component 120 detecting the terminal 10, the user may be prompted to authenticate. In some other embodiments of wallet mode operation, the NFC component 120 may not be enabled to detect the terminal 10 until after the user has been authenticated to use the NFC component 120. Thus, the control application module 330 may prompt the user to authenticate the NFC component 120 in response to at least two different types of authentication initiation events (e.g., in response to receiving an appropriate UI unlock input command 331a or in response to receiving appropriate terminal detection data 343).

[0083] FIG. 5 is a flowchart of an exemplary process 500 for managing near field communication. At step 502 of process 500, an initiation event for low power NFC or "wallet" power management mode may be detected. For example, as described in connection with Figure 3 , the mode detection module 310 may be configured to detect such an initiation event based on the received power level data 307 from the power supply 108 and / or based on the input mode selection data 309 received from the input component 110. Process 500 may continuously repeat step 502 until an initiation event is detected.

[0084] Next, upon detecting such an initiation event at step 502, process 500 may continue to switch the electronic device to wallet mode. This switch may include at least one of steps 504, 506, and / or 508. For example, process 500 may proceed from step 502 to step 504 and close at least one running application. As described in connection with Figure 3 , the switch application module 320 may generate and transmit an application disable command 327 to the processor 102 of the electronic device 100 to close one or more applications. Step 504 may additionally or alternatively include at least partially closing any I / O components of the device (e.g., the input component 110 and / or the output component 112 of the device 100), powering them down, or otherwise at least partially disabling at least one of their functions.

[0085] Process 500 may then proceed from step 504 to step 506 and disable at least a portion of the NFC component. For example, as described in connection with Figure 3As described, the switching application module 320 may generate and transmit an NFC disable command 321 to the NFC component 120 for disabling one or more credentials of one or more SSDs 154, for disabling the antenna 134 or the booster 136 of the device 130, or for disabling any other suitable element of the NFC component 120 that may prevent at least one credential of the NFC component 120 from being transmitted to the terminal 10 as NFC communication 55. Such disabling may reduce the power consumption of the NFC component 120 and / or may prevent the NFC component 120 from operating in a passive state. In addition or alternatively, switching the electronic device to the wallet mode in process 500 may include step 508, in which an application for managing the device in the wallet mode may be launched and run by the device. For example, as described in conjunction with Figure 3 As described, the switching application module 320 may generate and transmit a start command 329 to the control application module 330 for starting and running at least one application (e.g., application 143) that may be specifically adjusted for properly managing and / or otherwise controlling the electronic device 100 in the low-power NFC or wallet power management mode.

[0086] Next, once the electronic device is operating in the wallet low-power mode, process 500 may proceed to step 510 for detecting a UI unlock input command. For example, as described in conjunction with Figure 3 As described, the control application module 330 may be configured to wait for one or more suitable UI unlock input commands 331a from the input component 110, which may indicate that the user wishes to interact with the device 100 to possibly utilize the NFC component 120 for NFC communication 55 in the wallet mode. If such a command is detected at step 510, process 500 may proceed to step 512 for confirming that the user wishes to interact with the device 100. For example, as described in conjunction with Figure 3 and Figure 4BAs described above, the control application module 330 may generate and transmit an acknowledgment UI unlock command 333a to at least one output component 112 to prompt the user to confirm that they wish to interact with the device 100 in wallet mode. If such desire is confirmed at step 512 (e.g., by the control application module 330 receiving UI unlock confirmation data 331b), the process 500 may proceed to step 514 to determine whether the user wishes to power off the device, which may be done by proceeding to step 516 and ending the process 500 by powering off the device. However, if the user does not wish to power off the device at step 514, the process 500 may proceed to step 518 to determine whether the user wishes to cancel the unlock and exit the interaction with the device, which the user may do by returning the process 500 to step 510. However, if the user does not wish to exit the interaction with the device at step 518, the process 500 may proceed to step 520 to determine whether the user wishes to exit wallet mode, which may be done by exiting the mode at step 521 and returning to step 502. However, if the user does not wish to exit wallet mode at step 520, the process 500 may proceed to step 522 to attempt to authenticate the user to enable the NFC component. For example, it may be combined with Figure 3 and 4C to describe each step in steps 512 - 522.

[0087] At step 522, the process 500 may prompt the user to authenticate themselves to use the NFC component. For example, as combined with Figure 3 and 4C described above, the control application module 330 may generate and transmit an NFC component authentication request command 333b to at least one output component 112 of the device 100. If the user cannot be successfully authenticated to use the NFC component (e.g., by providing NFC component user authentication data 331c to the control application module 330 via user interaction with the input component 110), the process 500 may proceed to step 524, otherwise the process 500 may return to step 510.

[0088] In some embodiments, the user may be authenticated by interacting with the same user of the device 100, which may generate the UI unlock input command 331a detected at step 510, such that the process 500 may combine steps 510 and 522. For example, as combined above with Figure 2 described above, a biometric input component (e.g., biometric input component 110i) may be incorporated into another input component (e.g., home button input component 110a), and as combined above with Figure 3 and 4AAs described above, the UI unlock input command 331a can be a simple user interaction with the home button input component 110a. Therefore, such a user interaction with the home button input component 110a for generating the UI unlock input command 331a can also be a user interaction with the biometric sensor input component 110i to provide the NFC component user authentication data 331c to the control application module 330. In such cases, the process 500 can skip from step 510 to step 524 (e.g., bypass one or more of steps 512 - 522), as the authentication step 522 may be unnecessary due to the NFC component user authentication data 331c detected together with the UI unlock input command 331a at step 510.

[0089] In addition or alternatively, the user can be authenticated through the same user interaction with the device 100, which can generate the UI unlock confirmation data 331b detected at step 512, such that the process 500 can combine steps 512 and 522. For example, as described above in connection with Figure 2 As described above, a biometric input component (e.g., the biometric input component 110i) can be incorporated into another input component of the device 100 (e.g., the touch input component 110f of the I / O component 114a), and as described above in connection with Figure 3 and 4B As described above, the UI unlock confirmation data 331b can be a simple user interaction with the touch input component 110f of the I / O component 114a for sliding an element along a specific path on the screen 400b. Therefore, such a user interaction with the touch input component 110f of the I / O component 114a for generating the UI unlock confirmation data 331b can also be a user interaction with the biometric sensor input component 110i to provide the NFC component user authentication data 331c to the control application module 330. In such cases, the process 500 can skip from step 512 to step 524 (e.g., bypass one or more of steps 512 - 522), as the authentication step 522 may be unnecessary due to the NFC component user authentication data 331c detected together with the UI unlock confirmation data 331b at step 512.

[0090] At step 524, process 500 may determine whether the NFC component for user authentication has access to more than one credential. If so, process 500 proceeds to step 526; otherwise, process 500 may proceed to step 530. At step 526, process 500 may prompt the user to select one of the multiple credentials available for the NFC component (e.g., the control application module 330 may generate and transmit an NFC credential selection request command 333c to at least one output component 112 of device 100). If the user fails to select one of the multiple credentials at step 526 (e.g., by providing any appropriate credential selection response data 331d to the control application module 330 via any appropriate input component 110), process 500 may proceed to step 528; otherwise, process 500 may return to step 522.

[0091] At step 528, process 500 may prompt the user to authenticate themselves to use the selected credential. For example, as described in conjunction with Figure 3 and 4E , the control application module 330 may generate and transmit an NFC credential authentication request command 333d to at least one output component 112 of device 100. If the user fails to be authenticated to use the selected credential (e.g., by providing NFC credential user authentication data 331e to the control application module 330 via user interaction with the input component 110), process 500 may proceed to step 530; otherwise, process 500 may return to step 526.

[0092] At step 530, process 500 may enable the authorized credential of the NFC component and determine whether the duration of authorization has timed out. For example, as described in conjunction with Figure 3 , the control application module 330 may enable the selected and authorized credential of the NFC component 120 for use by generating and transmitting an NFC enable command 339 to the NFC component 120 to enable the NFC component 120 in any appropriate manner for NFC communication 55 with the terminal 10 using the selected and authorized credential, where the control application module 330 may allow the enabled credential to be potentially utilized by the NFC component 120 for at least a specific duration 435. If the authorization has expired, process 500 may proceed from step 530 to step 534; otherwise, process 500 may proceed from step 530 to step 532.

[0093] At step 532, process 500 may determine whether an authorized credential has been used in an NFC transaction. If the credential has been used in an NFC transaction, process 500 may proceed from step 532 to step 534; otherwise, process 500 may return from step 532 to step 530 to determine whether the duration has expired. At step 534, process 500 may provide a description of whether the authorized credential has been used or not, and may then return to step 510. For example, as described in connection with Figure 3 and 4G if, at any time during duration 435, an enabled credential is actually used by NFC component 120 for NFC communication 55 (e.g., in response to terminal 10 receiving information associated with the enabled credential), NFC component 120 may generate and transmit NFC status information 341 to control application module 330, and in response to receiving such NFC status information 341, control application module 330 may generate and transmit NFC usage data 333f to at least one output component 112 of device 100. Additionally, as described in connection with Figure 3 and 4G if, during duration 435, an enabled credential is not actually used by NFC component 120 for NFC communication 55, NFC component 120 may also generate and transmit NFC status information 341 to control application module 330, and in response to receiving such NFC status information 341 indicating non - use, control application module 330 may generate and transmit NFC usage data 333f to at least one output component 112 of device 100.

[0094] Returning to step 510, if no UI unlock input command is detected, process 500 may proceed from step 510 to step 536. At step 536, process 500 may attempt to detect an NFC terminal. For example, as described in connection with Figure 3 control application module 330 may wait for appropriate terminal detection data 343 from NFC component 120 as long as NFC component 120 is in a passive antenna mode or an active antenna mode during the wallet power management mode of device 100, and as long as such NFC component 120 detects that device 100 is within the NFC response range D of terminal 10, such terminal detection data 343 may be generated and transmitted by NFC component 120 to control application module 330. If such a terminal is detected, process 500 may proceed from step 536 to step 522; otherwise, process 500 may proceed from step 536 to step 510.

[0095] It should be understood that the steps shown in process 500 of FIG. 5 are merely exemplary, and existing steps may be modified or omitted, additional steps may be added, and the order of certain steps may be changed.

[0096] Figure 6is a flowchart of an exemplary process 600 for managing near field communication on an electronic device. At step 602, process 600 may receive authentication information using an input component of the electronic device. For example, as described in conjunction with Figure 3 the control application module 330 may generate and transmit an NFC component authentication request command 333b to at least one output component 112 of the device 100, and in response to this operation, the user may be authenticated to use the NFC component (e.g., by providing NFC component user authentication data 331c to the control application module 330 via user interaction with the input component 110). Next, at step 604, process 600 may power at least a first portion of the near field communication component of the electronic device based on the authentication information received at step 602. For example, as described in conjunction with Figure 3 once the appropriate NFC component user authentication data 331c is received, the control application module 330 may enable the NFC component 120 for use by generating and transmitting an NFC enable command 339 to the NFC component 120. Such an NFC enable command 339 may be configured to enable the NFC component 120 by powering the booster 136, thereby enabling the antenna 116 for NFC communication 55 with the terminal 10.

[0097] It should be understood that Figure 6 the steps shown in process 600 are merely exemplary, existing steps may be modified or omitted, additional steps may be added, and the order of certain steps may be changed.

[0098] Figure 7 is a flowchart of an exemplary process 700 for managing near field communication on an electronic device. At step 702, process 700 may detect a low power mode initiation event. For example, as described in conjunction with Figure 3 the mode detection module 310 may be configured to detect such a low power mode initiation event based on the received power level data 307 from the power supply 108 and / or based on the received input mode selection data 309 from the input component 110. Next, at step 704, process 700 may disable active elements of the electronic device, such as any appropriate portion or function of any appropriate component of the device 100. For example, as described in conjunction with Figure 3 the switching application module 320 may generate and transmit an NFC disable command 321 to the NFC component 120 for disabling one or more credentials of one or more SSDs 154, disabling the antenna 134 and / or the booster 136 of the device 130, and / or disabling any other appropriate element of the NFC component 120 that may prevent the transmission of at least one credential of the NFC component 120 to the terminal 10 as NFC communication 55. Such disabling may reduce the power consumption of the NFC component 120 and / or may prevent the NFC component 120 from operating in a passive state. As another example, as still in conjunction withFigure 3 As described above, the switching application module 320 may generate and transmit an output component disable command 323 to at least one output component 112 (e.g., at least one of output components 112a - 112c) to turn off the output component 112, power it down, or otherwise at least partially disable at least one function of the output component. As yet another example, as still in connection with Figure 3 As described above, the switching application module 320 may generate and transmit an output component disable command 325 to at least one input component 110 (e.g., at least one of input components 110a - 110c) to turn off the input component 112, power it down, or otherwise at least partially disable at least one function of the output component. As yet another example, as still in connection with Figure 3 As described above, the switching application module 320 may generate and transmit one or more additional disable commands (not shown) to at least one other component of the device 100 (e.g., memory 104, communication component 106, antenna 116, etc.), such that upon being received by the device component, the component disable command may be configured to turn off the device component, power it down, or otherwise at least partially disable at least one function of the device component.

[0099] Next, at step 706, process 700 may close at least one active application running on the electronic device prior to the detection step 702. For example, as in connection with Figure 3 As described above, the switching application module 320 may generate and transmit an application disable command 327 to the processor 102 of the electronic device 100 to close one or more applications (e.g., force - quit all inactive applications).

[0100] Next, at step 708, process 700 may run a low - power mode application on the electronic device, where running the low - power mode application may include receiving authentication information from an input component of the electronic device and enabling a near - field communication component based on the received authentication information. For example, as in connection with Figure 3As described above, the switching application module 320 may generate and transmit a start command 329 to the control application module 330 for starting and running at least one application (e.g., application 143) that may be specifically adjusted for properly managing and / or otherwise controlling the electronic device 100 in a low-power NFC or wallet power management mode. When running the application, the control application module 330 may generate and transmit an NFC component authentication request command 333b to at least one output component 112 of the device 100, and in response thereto, may authenticate the user to use the NFC component (e.g., by providing NFC component user authentication data 331c to the control application module 330 via user interaction with the input component 110). Once the appropriate NFC component user authentication data is received, the control application module 330 may enable the NFC component 120 for use by generating and transmitting an NFC enable command 339 to the NFC component 120.

[0101] It should be understood that Figure 7 the steps shown in process 700 are merely exemplary, existing steps may be modified or omitted, additional steps may be added, and the order of certain steps may be changed.

[0102] Figure 8 is a flowchart of an exemplary process 800 for managing near field communication on an electronic device. At step 802, process 800 may detect a low-power mode initiation event. For example, as described in connection with Figure 3 above, the mode detection module 310 may be configured to detect such a low-power mode initiation event based on the received power level data 307 from the power supply 108 and / or based on the received input mode selection data 309 from the input component 110. Next, at step 804, process 800 may disable elements of the electronic device, such as any appropriate portion or function of any appropriate component of the device 100. For example, as described in connection with Figure 3 above, the switching application module 320 may generate and transmit an NFC disable command 321 to the NFC component 120 for disabling one or more credentials of one or more SSDs 154, disabling the antenna 134 and / or the booster 136 of the device 130, and / or disabling any other appropriate element of the NFC component 120 that may prevent the transmission of at least one credential of the NFC component 120 to the terminal 10 as NFC communication 55. Such disabling may reduce the power consumption of the NFC component 120 and / or may prevent the NFC component 120 from operating in a passive state. As another example, still in connection with Figure 3As described above, the switching application module 320 can generate and transmit an output component disable command 323 to at least one output component 112 (e.g., at least one of output components 112a - 112c) to turn off the output component 112, power it down, or otherwise at least partially disable at least one function of the output component. As yet another example, as still in connection with Figure 3 As described above, the switching application module 320 can generate and transmit an output component disable command 325 to at least one input component 110 (e.g., at least one of input components 110a - 110c) to turn off the input component 110, power it down, or otherwise at least partially disable at least one function of the input component. As yet another example, as still in connection with Figure 3 As described above, the switching application module 320 can generate and transmit one or more additional disable commands (not shown) to at least one other component of the device 100 (e.g., memory 104, communication component 106, antenna 116, etc.), such that when received by the device component, the component disable command can be configured to turn off the device component, power it down, or otherwise at least partially disable at least one function of the device component.

[0103] Next, at step 806, the process 800 can identify an authentication initiation event. Then, at step 808, in response to the authentication of step 806, the process 800 provides an output for requesting user interaction on an output component of the electronic device, the user interaction being for enabling the near - field communication component. For example, as in connection with Figure 3 As described above, the control application module 330 can prompt the user to authenticate the NFC component 120 in response to at least two different types of authentication initiation events (e.g., in response to receiving an appropriate UI unlock input command 331a or in response to receiving appropriate terminal detection data 343).

[0104] It should be understood that Figure 8 the steps shown in the process 800 of

[0105] are merely exemplary, existing steps can be modified or omitted, additional steps can be added, and the order of certain steps can be changed. Figures 1 - 8One, some, or all of the processes described above may be implemented by software, but may also be implemented in hardware, firmware, or any combination of software, hardware, and firmware. The instructions for performing these processes may also be implemented as machine-readable code or computer-readable code recorded on a machine-readable medium or computer-readable medium. In some embodiments, the computer-readable medium may be a non-transitory computer-readable medium. Examples of such non-transitory computer-readable media include, but are not limited to, read-only memory, random access memory, flash memory, CD-ROMs, DVDs, magnetic tapes, removable memory cards, and data storage devices (e.g., optical data storage devices such as Figure 1 the memory 104 and / or the memory module 150). In other embodiments, the computer-readable medium may be a transitory computer-readable medium. In such embodiments, the transitory computer-readable medium may also be distributed across a network-coupled computer system such that the computer-readable code is stored and executed in a distributed manner. For example, any suitable communication protocol may be used to transfer such transitory computer-readable media from one electronic device to another (e.g., the computer-readable media may be transferred to the electronic device 100 via the communication component 106 (e.g., at least a portion of the application 103 and / or the application 143)). Such transitory computer-readable media may contain computer-readable code, instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transmission mechanism and may include any information transmission medium. A modulated data signal may be a signal whose one or more characteristics are set or changed to encode information in the signal.

[0106] It should be understood that any module or each module of either or both of the NFC component 120 and the NFC management subsystem 301 may be provided as a software construct, a firmware construct, one or more hardware components, or a combination thereof. For example, any module or each module of either or both of the NFC component 120 and the NFC management subsystem 301 may be described in the general context of computer-executable instructions, such as in the context of program modules that may be executed by one or more computers or other devices. Generally, program modules may include one or more routines, programs, objects, components, and / or data structures that may perform one or more specific tasks or may implement one or more specific abstract data types. It should also be understood that the number, configuration, functions, and interconnections of the modules of either or both of the NFC component 120 and the NFC management subsystem 301 are merely exemplary, the number, configuration, functions, and interconnections of existing modules may be modified or omitted, additional modules may be added, and the interconnections of specific modules may be changed.

[0107] As described above, various disabling commands can be configured to turn off various components of device 100, power them down or otherwise at least partially disable at least one function of the device. For example, the input component disabling command 325 can be configured to turn off the input component 110, power it down or otherwise at least partially disable at least one function of the input component, and the application disabling command 327 can be configured to turn off one or more applications currently running on the processor 102, power them down or otherwise at least partially disable one or more applications (e.g., force quit all non-native applications running on device 100 before generating the application disabling command 327), while the NFC disabling command 321 can be configured to turn off the NFC component 120, power it down or otherwise at least partially disable at least one function of the NFC component. Similarly, various enabling commands can be configured to turn on various components of device 100, power them on or otherwise at least partially enable at least one function of the various components of the device. For example, the NFC enabling command 339 can turn on the NFC component 120, power it on or otherwise at least partially enable at least one function of the NFC component. Such commands can enable or disable one or more various elements of a component of device 100 (e.g., software constructs, firmware constructs, one or more hardware components, or combinations thereof) in one or more suitable ways to enable or disable at least one function of the component. For example, an application can be disabled by unloading a software application running on the processor 102 from the processor 102 and / or completely turning off the processor 102. As another example, at least one credential activated for use can be finally enabled by providing appropriate power to the booster 136, thereby otherwise powering on the NFC component 120 for NFC communication 55, such that the shared antenna 116 can be appropriately used to transmit such NFC communication 55. As yet another example, the antenna ready to transmit NFC communication 55 can be finally enabled for transmitting NFC communication 55 by enabling at least one credential of the NFC component 120 for use in such communication 55, thereby otherwise powering on the NFC component 120. Enabling of at least one credential (e.g., activating the applet 153) can be accomplished by powering on the memory element storing the credential or otherwise turning on the memory element and / or by transmitting a key or other security data to the SSD of the credential in order to decrypt the information of the credential for use by the NFC component 120 as NFC communication 55.

[0108] Storage may be performed in device 100 in any suitable manner (e.g., as at least a part of application 103 and / or application 143), or at least a part of one or more modules of either or both of NFC component 120 and NFC management subsystem 301 may be accessible to device 100 (e.g., in memory 104 of device 100). Any suitable technology may be utilized to implement any or each module of either or both of NFC component 120 and NFC management subsystem 301 (e.g., as one or more integrated circuit devices), and different modules may be the same or different in structure, capabilities, and operation. Any module or all modules or other components of either or both of NFC component 120 and NFC management subsystem 301 may be mounted on an expansion card, directly on the system motherboard, or integrated into a system chipset component (e.g., integrated into a "northbridge" chip).

[0109] Any module or each module of either or both of NFC component 120 and NFC management subsystem 301 may be a dedicated system implemented using one or more expansion cards suitable for various bus standards. For example, all modules may be mountable on different interconnect expansion cards or all modules may be mounted on one expansion card. For NFC component 120, by way of example only, the modules of NFC component 120 may interface with the motherboard or processor 102 of device 100 through an expansion slot (e.g., a Peripheral Component Interconnect ("PCI") slot or a PCI express slot). As an alternative, NFC component 120 need not be removable, but may include one or more dedicated modules, and the one or more dedicated modules may include memory (e.g., RAM) dedicated to the utilization of the modules. In other embodiments, NFC component 120 may be integrated into device 100. For example, the modules of NFC component 120 may utilize a part of device memory 104 of device 100. Any module or each module of either or both of NFC component 120 and NFC management subsystem 301 may include its own processing circuitry and / or memory. As an alternative, any module or each module of either or both of NFC component 120 and NFC management subsystem 301 may share processing circuitry and / or memory with any other module of NFC component 120 and / or NFC management subsystem 301 and / or processor 102 and / or memory 104 of device 100.

[0110] As described above, input component 110 (e.g., input component 110f) of device 100 may include a touch input component that may receive touch input for interacting with other components of device 100 via a wired bus or wireless bus 118. Such a touch input component 110 may be used to provide user input to device 100 in place of or in combination with other input components such as a keyboard, a mouse, etc.

[0111] The touch input component 110 may include a touch-sensitive panel, which may be fully transparent, partially transparent, translucent, opaque, non-transparent, or any combination thereof. The touch input component 110 may be implemented as a touch screen, a touch pad, a touch screen acting as a touch pad (e.g., a touch screen replacing the touch pad of a laptop), a touch screen or touch pad combined or integrated with any other input device (e.g., a touch screen or touch pad disposed on a keyboard), or any multi-dimensional object having a touch-sensitive surface for receiving touch input. In some embodiments, the terms touch screen and touch pad may be used interchangeably.

[0112] In some embodiments, the touch input component 110 implemented as a touch screen may include a transparent and / or translucent touch-sensitive panel that is partially or fully located above, below, and / or within at least a portion of the display (e.g., the display output component 112a). In other embodiments, the touch input component 110 may be implemented as an integrated touch screen, where the touch-sensitive component / device is integral with the display component / device. In other embodiments, the touch input device 110 may be used as a supplementary display screen or an additional display screen for displaying supplementary graphic data or the same graphic data as the main display and for receiving touch input.

[0113] The touch input component 110 may be configured to detect the location of one or more touches or near touches based on capacitance, resistance, optics, acoustics, induction, mechanics, chemical measurements, or any phenomenon that can be measured relative to one or more touches or near touches occurring in the vicinity of the input component 110. Software, hardware, firmware, or any combination thereof may be used to process the measurements of the detected touches in order to identify and track one or more gestures. Gestures may correspond to stationary or non-stationary, single or multiple touches or near touches on the touch input component 110. Gestures may be performed by moving one or more fingers or other objects on the touch input component 110 in a particular manner, either substantially simultaneously, continuously, or sequentially, such as by tapping, pressing, shaking, rubbing, rotating, twisting, changing orientation, pressing with different pressures, etc. Gestures may be characterized by, but not limited to, pinching, pulling, sliding, swiping, rotating, flexing, dragging, or tapping actions between or with any other one or more fingers. One or more users may perform a single gesture using one or more hands or any combination thereof.

[0114] As described above, the electronic device 100 can utilize graphic data to drive a display (e.g., the display output component 112a) to display a graphical user interface (“GUI”) 180. The GUI 180 can be configured to receive touch inputs via the touch input component 110f. Implemented as a touch screen (e.g., where the display output component 112a serves as the I / O component 114a), the touch I / O component 110f can display the GUI 180. As an alternative, the GUI 180 can be displayed on a display (e.g., the display output component 112a) independent of the touch input component 110f. The GUI 180 can include graphical elements displayed at specific locations within the interface. The graphical elements can include, but are not limited to, various displayed virtual input devices, including virtual rollers, virtual keyboards, virtual knobs, virtual buttons, any virtual user interface (“UI”), etc. The user can perform gestures at one or more specific locations on the touch input component 100f that may be associated with the graphical elements of the GUI 180. In other embodiments, the user can perform gestures at one or more locations independent of the locations of the graphical elements of the GUI 180. Gestures performed on the touch input component 110 can directly or indirectly manipulate, control, modify, move, actuate, initiate, or generally affect graphical elements within the GUI, such as cursors, icons, media files, lists, text, all or part of an image, etc. For example, in the case of a touch screen, the user can directly interact with a graphical element by performing a gesture above the graphical element on the touch screen. As an alternative, a touchpad generally provides indirect interaction. Gestures can also affect GUI elements that are not displayed (e.g., causing a user interface to appear) or can affect other actions of the device 100 (e.g., affecting the state or mode of the GUI, an application, or the operating system). In combination with a displayed cursor, gestures can be performed on or off the touch input component 110. For example, in the case of performing a gesture on a touchpad, a cursor or pointer can be displayed on the display screen or touch screen, and the cursor or pointer can be controlled via touch inputs on the touchpad to interact with graphical objects on the display screen. In other embodiments, where gestures are performed directly on the touch screen, whether or not a cursor or pointer is displayed on the touch screen, the user can directly interact with objects on the touch screen. Feedback can be provided to the user via the bus 118 in response to or based on a touch or near-touch on the touch input component 110. The feedback can be transmitted optically, mechanically, electrically, olfactorily, acoustically, etc., or any combination thereof, and in a variable or immutable manner.

[0115] Although systems, methods, and computer-readable media for managing near field communication have been described, it should be understood that many changes may be made thereto without departing from the spirit and scope of the subject matter described herein in any way. Non-substantive changes regarded by one of ordinary skill in the art as being equivalent to the claimed subject matter, whether now known or later devised, are expressly contemplated as being within the scope of the claims. Accordingly, obvious substitutions now or later known to one of ordinary skill in the art are defined as being within the scope of the defined elements.

[0116] Accordingly, those skilled in the art will recognize that the invention may be practiced by other means than those illustrated, which are provided by way of example and not of limitation.

Claims

1. A method for operating an electronic device, comprising: Detecting a low-power mode initiation event; And In response to the detection: Disabling active components of the electronic device, where the active components include at least one of a communication component or an output component; Closing at least one active application running on the electronic device before the detection; And Running a low-power mode application on the electronic device, where running the low-power mode application includes: Receiving authentication information from an input component of the electronic device; And Enabling a near-field communication component of the electronic device based on the received authentication information.

2. The method according to claim 1, wherein The enabling includes powering a part of the near-field communication component.

3. The method according to claim 1, wherein: Running the low-power mode application further includes providing a visual user interface on a display output component of the electronic device before the receiving; and The receiving includes receiving the authentication information based on the provided visual user interface.

4. The method according to claim 3, wherein the providing includes at least one of the following: Requesting user authorization of the near-field communication component; or Requesting user selection of at least one credential provided on the near-field communication component.

5. The method according to claim 1, wherein detecting the low-power mode initiation event includes one of the following: Receiving user input on an input component of the electronic device; or Detecting that a power level of a power supply of the electronic device is lower than a specific threshold.

6. The method according to claim 1, wherein the enabling includes activating a small application of a credential provided on the near-field communication component.

7. The method according to claim 1, wherein the enabling includes placing the near-field communication component in one of a passive state or an active state.

8. A non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium containing instructions that, when executed, perform the method for operating an electronic device according to any one of claims 1-7.

9. An electronic device, comprising: A near-field communication component; An input component; And A processor configured to execute the method according to any one of claims 1-7.

10. A device for operating an electronic device, comprising components for performing the steps of the method according to any one of claims 1-7.

Images