Patent ID: 12222794

DETAILED DESCRIPTION OF THE DISCLOSURE

Systems, methods, and computer-readable media may be provided for managing near field communications. Near field communications may be managed differently according to different power management modes of an electronic device. In certain low power management modes, certain components of an electronic device may be at least partially disabled or shut down to conserve power. When an electronic device operates in these modes, credentials (e.g., payment credentials) of an NFC component in the device may be appropriately secure and/or appropriately accessible, while power consumption of the NFC component is limited or reduced. For example, while in a low powered operating state at which both a system power management unit (“PMU”) and any device operating system may be off or disabled or inactive, an electronic device may be operative to carry out one or more NFC transactions using one or more specific credentials (e.g., credentials previously designated as express mode cards) and provide any suitable output that may be operative to indicate such an attempted or completed transaction to a user of the device. Various transitions between power management states may be accomplished using a system PMU and a boot loader application of the electronic device but not a full operating system application, such that significant power savings may be realized, while certain actions within a state, such as an NFC transaction within a low power management state, which may include generating a haptic or other user detectable output, may be accomplished without even using a system PMU or loading any application for realizing additional power savings while also securely enabling certain NFC transactions for improving user convenience.

FIG.1is a schematic view of an illustrative communications system1that may include a terminal10and an electronic device100for managing near field communications55with terminal10in accordance with some embodiments. Electronic device100can include, but is not limited to, a music player (e.g., an iPod™ available by Apple Inc. of Cupertino, California), video player, still image player, game player, other media player, music recorder, movie or video camera or recorder, still camera, other media recorder, radio, medical equipment, domestic appliance, transportation vehicle instrument, musical instrument, calculator, cellular telephone (e.g., an iPhone™ available by Apple Inc.), other wireless communication device, personal digital assistant, remote control, pager, computer (e.g., a desktop, laptop, tablet (e.g., an iPad™ available by Apple Inc.), server, etc.), monitor, television, stereo equipment, set up box, set-top box, boom box, modem, router, printer, or any combination thereof. In some embodiments, electronic device100may perform a single function (e.g., a device dedicated to managing near field communications) and, in other embodiments, electronic device100may perform multiple functions (e.g., a device that manages near field communications, plays music, and receives and transmits telephone calls).

Electronic device100may be any portable, mobile, hand-held, or miniature electronic device that may be configured to manage near field communications wherever a user travels. Some miniature electronic devices may have a form factor that is smaller than that of hand-held electronic devices, such as an iPod™. Illustrative miniature electronic devices can be integrated into various objects that may include, but are not limited to, watches (e.g., an Apple Watch™ available by Apple Inc.), rings, necklaces, belts, accessories for belts, headsets, accessories for shoes, virtual reality devices, glasses, other wearable electronics, accessories for sporting equipment, accessories for fitness equipment, key chains, or any combination thereof. Alternatively, electronic device100may not be portable at all, but may instead be generally stationary.

As shown inFIG.1, for example, electronic device100may include a processor102, memory104, communications component106, power supply108, input component110, output component112, antenna116, and near field communication (“NFC”) component120. Electronic device100may also include a bus118that may provide one or more wired or wireless communication links or paths for transferring data and/or power to, from, or between various other components of device100. In some embodiments, one or more components of electronic device100may be combined or omitted. Moreover, electronic device100may include other components not combined or included inFIG.1. For example, electronic device100may include motion-sensing circuitry, a compass, any other suitable components, or several instances of the components shown inFIG.1. For the sake of simplicity, only one of each of the components is shown inFIG.1.

Memory104may include one or more storage mediums, including for example, a hard-drive, flash memory, permanent memory such as read-only memory (“ROM”), semi-permanent memory such as random access memory (“RAM”), any other suitable type of storage component, or any combination thereof. Memory104may include cache memory, which may be one or more different types of memory used for temporarily storing data for electronic device applications. Memory104may be fixedly embedded within electronic device100or may be incorporated onto one or more suitable types of cards that may be repeatedly inserted into and removed from electronic device100(e.g., a subscriber identity module (“SIM”) card or secure digital (“SD”) memory card). Memory104may store media data (e.g., music and image files), software (e.g., for implementing functions on device100), firmware, preference information (e.g., media playback preferences), lifestyle information (e.g., food preferences), exercise information (e.g., information obtained by exercise monitoring equipment), transaction information (e.g., information such as credit card information), wireless connection information (e.g., information that may enable device100to establish a wireless connection), subscription information (e.g., information that keeps track of podcasts or television shows or other media a user subscribes to), contact information (e.g., telephone numbers and e-mail addresses), calendar information, any other suitable data, or any combination thereof.

Communications component106may be provided to allow device100to communicate with one or more other electronic devices or servers using any suitable communications protocol. For example, communications component106may support Wi-Fi (e.g., an 802.11 protocol), ZigBee (e.g., an 802.15.4 protocol), WiDi™, Ethernet, Bluetooth™, Bluetooth™ Low Energy (“BLE”), high frequency systems (e.g., 900 MHz, 2.4 GHz, and 5.6 GHz communication systems), infrared, transmission control protocol/internet protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), Stream Control Transmission Protocol (“SCTP”), Dynamic Host Configuration Protocol (“DHCP”), hypertext transfer protocol (“HTTP”), BitTorrent™, file transfer protocol (“FTP”), real-time transport protocol (“RTP”), real-time streaming protocol (“RTSP”), real-time control protocol (“RTCP”), Remote Audio Output Protocol (“RAOP”), Real Data Transport Protocol™ (“RDTP”), User Datagram Protocol (“UDP”), secure shell protocol (“SSH”), wireless distribution system (“WDS”) bridging, any communications protocol that may be used by wireless and cellular telephones and personal e-mail 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 communications protocol that may be used by a low power Wireless Personal Area Network (“6LoWPAN”) module, any suitable cellular communications protocol (e.g., broadband cellular network technologies (e.g., 3G, 4G, 5G, etc.)), any other communications protocol, or any combination thereof. Communications component106may also include or be electrically coupled to any suitable transceiver circuitry (e.g., transceiver circuitry or antenna116via bus118) that can enable device100to be communicatively coupled to another device (e.g., a host computer or an accessory device) and communicate with that other device wirelessly, or via a wired connection (e.g., using a connector port). Communications component106may be configured to determine a geographical position of electronic device100. For example, communications component106may utilize the global positioning system (“GPS”) or a regional or site-wide positioning system that may use cell tower positioning technology or Wi-Fi technology.

Power supply108can include any suitable circuitry for receiving and/or generating power, and for providing such power to one or more of the other components of electronic device100. For example, power supply108can be coupled to a power grid (e.g., when device100is not acting as a portable device or when a battery of the device is being charged at an electrical outlet with power generated by an electrical power plant). As another example, power supply108can be configured to generate power from a natural source (e.g., solar power using solar cells). As another example, power supply108can include one or more batteries for providing power (e.g., when device100is acting as a portable device). For example, power supply108can include one or more of 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 circuitry for processing power received from a power generation source (e.g., power generated by an electrical power plant and delivered to the user via an electrical socket or otherwise). The power can be provided by power supply108as alternating current or direct current, and may be processed to transform power or limit received power to particular characteristics. For example, the power can be transformed to or from 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 received power. Power supply108can be operative to request or provide particular amounts of power at different times, for example, based on the needs or requirements of electronic device100or periphery devices that may be coupled to electronic device100(e.g., to request more power when charging a battery than when the battery is already charged).

One or more input components110may be provided to permit a user to interact or interface with device100. For example, input component110can take a variety of forms, including, but not limited to, a touch pad, dial, click wheel, scroll wheel, touch screen, one or more buttons (e.g., a keyboard), mouse, joy stick, track ball, microphone, camera, scanner (e.g., a bar code scanner or any other suitable scanner that may obtain product identifying information from a code, such as a bar code, a QR code, or the like), proximity sensor, light detector, motion sensor, biometric sensor (e.g., a fingerprint reader or other feature recognition sensor, which may operate in conjunction with a feature-processing application that may be accessible to electronic device100for authenticating a user), and combinations thereof. Each input component110can be configured to provide one or more dedicated control functions for making selections or issuing commands associated with operating device100.

Electronic device100may also include one or more output components112that may present information (e.g., graphical, audible, and/or tactile information) to a user of device100. For example, output component112of electronic device100may take various forms, including, but not limited to, audio speakers, headphones, audio line-outs, visual displays, antennas, infrared ports, rumblers, vibrators, any other suitable haptic elements, or combinations thereof.

As a specific example, electronic device100may include a display output component as an output component112. Such a display output component may include any suitable type of display or interface for presenting visual data to a user. A display output component may include a display embedded in device100or coupled to device100(e.g., a removable display). A display output component may include, for example, 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 combination thereof. Alternatively, a display output component can include a movable display or a projecting system for providing a display of content on a surface remote from electronic device100, such as, for example, a video projector, a head-up display, or a three-dimensional (e.g., holographic) display. As another example, a display output component may include a digital or mechanical viewfinder, such as a viewfinder of the type found in compact digital cameras, reflex cameras, or any other suitable still or video camera. A display output component may include display driver circuitry, circuitry for driving display drivers, or both, and such a display output component can be operative to display content (e.g., media playback information, application screens for applications implemented on electronic device100, information regarding ongoing communications operations, information regarding incoming communications requests, device operation screens, etc.) that may be under the direction of processor102.

It should be noted that one or more input components and one or more output components may sometimes be referred to collectively herein as an input/output (“I/O”) component or I/O interface (e.g., input component110and output component112as I/O component or I/O interface114). For example, input component110and output component112may sometimes be a single I/O component114, such as a touch screen, that may receive input information through a user's touch of a display screen and that may also provide visual information to a user via that same display screen.

Processor102of electronic device100may include any processing circuitry that may be operative to control the operations and performance of one or more components of electronic device100. For example, processor102may receive input signals from input component110and/or drive output signals through output component112. As shown inFIG.1, processor102may be used to run one or more applications, such as an application103. Application103may 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 feature-processing applications, or any other suitable applications. For example, processor102may load application103as a user interface program to determine how instructions or data received via an input component110or other component of device100may manipulate the way in which information may be stored and/or provided to the user via an output component112. Application103may be accessed by processor102from any suitable source, such as from memory104(e.g., via bus118) or from another device or server (e.g., via communications component106). Processor102may include a single processor or multiple processors. For example, processor102may include at least one “general purpose” microprocessor, a combination of general and special purpose microprocessors, instruction set processors, graphics processors, video processors, and/or related chips sets, and/or special purpose microprocessors. Processor102also may include on board memory for caching purposes.

Electronic device100may also include near field communication (“NFC”) component120. NFC component120may be any suitable proximity-based communication mechanism that may enable contact-less transactions or communications55between electronic device100and terminal10(e.g., a payment terminal). NFC component120may allow for close range communication at relatively low data rates (e.g., 424 kbps), and may 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. Alternatively or additionally, NFC component120may allow for close range communication at relatively high data rates (e.g., 560 Mbps), and may comply with any suitable standards, such as the TransferJet™ protocol. Communication between NFC component120and terminal10may occur within any suitable close range distance D between device100and terminal10, such as a range of approximately 2 to 4 centimeters (or any other distance greater than 4 centimeters or less than 2 centimeters), and may operate at any suitable frequency (e.g., 13.56 MHz). For example, such close range communication of NFC component120may take place via magnetic field induction, which may allow NFC component120to communicate with other NFC devices and/or to retrieve information from tags having radio frequency identification (“RFID”) circuitry. NFC component120may provide a manner of acquiring merchandise information, transferring payment information, and otherwise communicating with an external device (e.g., terminal10).

NFC component120may include any suitable modules for enabling contactless proximity-based communication55between electronic device100and terminal10. As shown inFIG.1, for example, NFC component120may include an NFC device module130, an NFC controller module140, and an NFC memory module150.

NFC device module130may include an NFC data module132, an NFC antenna134, and an NFC booster136. NFC data module132may be configured to contain, route, or otherwise provide any suitable data that may be transmitted by NFC component120to terminal10as part of a contactless proximity-based or NFC communication55. Additionally or alternatively, NFC data module132may be configured to contain, route, or otherwise receive any suitable data that may be received by NFC component120from terminal10as part of a contactless proximity-based communication55.

NFC transceiver or NFC antenna134may be any suitable antenna or other suitable transceiver circuitry that may generally enable communication of communication55from NFC data module132to terminal10and/or to NFC data module132from terminal10. Therefore, NFC antenna134(e.g., a loop antenna) may be provided specifically for enabling the contactless proximity-based communication capabilities of NFC component120.

Alternatively or additionally, NFC component120may utilize the same transceiver circuitry or antenna (e.g., antenna116) that another communication component of electronic device100(e.g., communication component106) may utilize. For example, communication component106may leverage antenna116to enable Wi-Fi, Bluetooth™, or GPS communication between electronic device100and another remote entity, while NFC component120may leverage antenna116to enable contactless proximity-based or NFC communication55between NFC data module132of NFC device module130and another entity (e.g., terminal10). In such embodiments, NFC device module130may include NFC booster136, which may be configured to provide appropriate signal amplification for data of NFC component120(e.g., data within NFC data module132) so that such data may be appropriately transmitted by shared antenna116as communication55to terminal10. For example, shared antenna116may require amplification from booster136before antenna116(e.g., a non-loop antenna) may be properly enabled for communicating contactless proximity-based or NFC communication55between electronic device100and terminal10(e.g., more power may be needed to transmit NFC data using antenna116than may be needed to transmit other types of data using antenna116).

NFC controller module140may include at least one NFC processor module142. NFC processor module142may operate in conjunction with NFC device module130to enable, activate, allow, and/or otherwise control NFC component120for communicating NFC communication55between electronic device100and terminal10. NFC processor module142may exist as a separate component, may be integrated into another chipset, or may be integrated with processor102, for example, as part of a system on a chip (“SoC”). As shown inFIG.1, NFC processor module142of NFC controller module140may be used to run one or more applications, such as an NFC low power mode or wallet application143that may help dictate the function of NFC component120. Application143may include, but is not limited to, one or more operating system applications, firmware applications, NFC low power applications, or any other suitable applications that may be accessible to NFC component120(e.g., application103). NFC controller module140may include one or more protocols, such as the Near Field Communication Interface and Protocols (“NFCIP-1”), for communicating with another NFC device (e.g., terminal10). The protocols may be used to adapt the communication speed and to designate one of the connected devices as the initiator device that controls the near field communication.

NFC controller module140may control the near field communication mode of NFC component120. For example, NFC processor module142may be configured to switch NFC device module130between a reader/writer mode for reading information (e.g., communication55) from NFC tags (e.g., from terminal10) to NFC data module132, a peer-to-peer mode for exchanging data (e.g., communication55) with another NFC enabled device (e.g., terminal10), and a card emulation mode for allowing another NFC enabled device (e.g., terminal10) to read information (e.g., communication55) from NFC data module132. NFC controller module140also may be configured to switch NFC component120between active and passive modes. For example, NFC processor module142may be configured to switch NFC device module130(e.g., in conjunction with NFC antenna134or shared antenna116) between an active mode where NFC device module130may generate its own RF field and a passive mode where NFC device module130may use load modulation to transfer data to another device generating an RF field (e.g., terminal10). Operation in such a passive mode may prolong the battery life of electronic device100compared to operation in such an active mode. The modes of NFC device module130may be controlled based on preferences of a user and/or based on preferences of a manufacturer of device100, which may be defined or otherwise dictated by an application running on device100(e.g., application103and/or application143).

NFC memory module150may operate in conjunction with NFC device module130and/or NFC controller module140to allow for NFC communication55between electronic device100and terminal10. NFC memory module150may be embedded within NFC device hardware or within an NFC integrated circuit (“IC”). NFC memory module150may be tamper resistant and may include at least a portion of a secure element. For example, NFC memory module150may store one or more applications relating to NFC communications (e.g., application143) that may be accessed by NFC controller module140. For example, such applications may include financial payment applications, secure access system applications, loyalty card applications, and other applications, which may be encrypted. In some embodiments, NFC controller module140and NFC memory module150may independently or in combination provide a dedicated microprocessor system that may contain an operating system, memory, application environment, and security protocols intended to be used to store and execute sensitive applications on electronic device100. NFC memory module150may be a portion of memory106or at least one dedicated chip specific to NFC component120. NFC memory module150may reside on a SIM, a dedicated chip on a motherboard of electronic device100, or as an external plug in memory card. NFC memory module150may be completely independent from NFC controller module140and may be provided by different components of device100and/or provided to electronic device100by different removable subsystems.

NFC memory module150may include one or more of an issuer security domain (“ISD”)152and a supplemental security domain (“SSD”)154(e.g., a service provider security domain (“SPSD”), a trusted service manager security domain (“TSMSD”), etc.), which may be defined and managed by an NFC specification standard (e.g., GlobalPlatform). For example, ISD152may be a portion of NFC memory module150in which a trusted service manager (“TSM”) or issuing financial institution may store keys and/or other suitable information for creating or otherwise provisioning one or more credentials (e.g., credentials associated with various credit cards, bank cards, gift cards, access cards, transit passes, etc.) on electronic device100(e.g., via communications component106), for credential content management, and/or security domain management. A specific supplemental security domain (“SSD”)154(e.g., one of SSDs154-154b) may be associated with a specific credential (e.g., a specific credit card credential or a specific public transit card credential or a specific space (e.g., building) access card credential) that may provide specific privileges or payment rights to electronic device100. Each SSD154may have its own manager key155for its own application or applet153that may need to be activated to enable a specific credential of that SSD154for use by NFC device module130as an NFC communication55. For example, a particular SSD154may be associated with a particular credit card credential. However, that particular credential may only be communicated as an NFC communication55to terminal10by NFC component120(e.g., that particular credential may only be accessible by NFC data module132) when a particular applet153of that particular SSD154has been enabled or otherwise activated or unlocked for such use. Security features may be provided for enabling use of NFC component120that may be particularly useful when transmitting payment information, such as credit card information or bank account information to terminal10. Such security features also may 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 sensor may need to be provided to access the secure storage area. In certain embodiments, some or all of the security features may be stored within NFC memory module150. Further, security information, such as an authentication key, for communicating with terminal10may be stored within NFC memory module150. In certain embodiments, NFC memory module150may include a microcontroller embedded within electronic device100.

Terminal10may include a reader for detecting, reading, or otherwise receiving NFC communication55from electronic device100(e.g., when electronic device100comes within a certain distance or proximity D of terminal10). Accordingly, it is noted that NFC communication55between terminal10and electronic device100may occur wirelessly and, as such, may not require a clear “line of sight” between the respective devices. As mentioned, NFC device module130may be passive or active. When passive, NFC device module130may only be activated when within a response range D of a suitable reader of terminal10. For instance, a reader of terminal10may emit a relatively low-power radio wave field that may be used to power an antenna utilized by NFC device module130(e.g., shared antenna116or NFC-specific antenna134) and, thereby, enable that antenna to transmit suitable NFC communication information (e.g., transit card credential information) from NFC data module132, via antenna116or antenna134, to terminal10as NFC communication55. When active, NFC device module130may incorporate or otherwise have access to a power source local to electronic device100(e.g., power supply108) that may enable shared antenna116or NFC-specific antenna134to actively transmit NFC communication information (e.g., transit card credential information) from NFC data module132, via antenna116or antenna134, to terminal10as NFC communication55, rather than reflect radio frequency signals, as in the case of a passive NFC device module130.

While NFC component120has been described with respect to near field communication, it is to be understood that component120may be configured to provide any suitable contactless proximity-based mobile payment or any other suitable type of contactless proximity-based communication55between electronic device100and terminal10. For example, NFC component120may be configured to provide any suitable short-range communication, such as those involving electromagnetic/electrostatic coupling technologies.

Electronic device100may also be provided with a housing101that may at least partially enclose one or more of the components of device100for protection from debris and other degrading forces external to device100. In some embodiments, one or more of the components may be provided within its own housing (e.g., input component110may be an independent keyboard or mouse within its own housing that may wirelessly or through a wire communicate with processor102, which may be provided within its own housing).

FIG.1Aillustrates an exemplary battery chart108adetailing various potential state-of-charge thresholds of an exemplary power supply108(e.g., an exemplary battery) of electronic device100. Specifically,FIG.1Aillustrates how different operating modes of device100may be enabled based on the amount of energy that may be remaining in power supply108, as battery chart108amay represent the actual energy left in a battery of power supply108, where chart108amay detail various possible levels and thresholds that device100may incorporate into its operation. For example, as shown, battery chart108amay include a first or full operating charge level range162that may be any charge level between a maximum threshold charge level161and a first switching threshold or software threshold or low power express mode (“LPEM”)-on threshold charge level163, a second or high battery trap or LPEM operating charge level range164that may be any charge level between LPEM-on threshold charge level163and a second switching threshold or low power or LPEM-off threshold charge level165, a third or low battery trap operating charge level range166that may be any charge level between LPEM-off threshold charge level165and a third switching threshold or over-discharge lockout (“ODL”) threshold charge level167, and a fourth or disconnect operating charge level range168that may be any charge level between ODL threshold charge level167and a minimum threshold charge level169.

When the charge level of power supply108is in full operating charge level range162, device100may usually be configured to operate in a full or normal operating mode, which may allow device100to perform functions such as place telephone calls, connect to Wi-Fi, play media files, and/or any other suitable functions that may be a normal functionality of device100(e.g., by configuring NFC component120to be in an NFC full power mode). LPEM-on threshold charge level163may be provided in order to limit the current output of power supply108once the battery charge has dropped to or below that threshold charge level163. Upon the battery charge decreasing to at least that threshold charge level163and to no less than ODL threshold charge level167, such that the charge level of power supply108is in LPEM operating charge level range164or in low battery trap operating charge level range166, device100may usually be configured to operate in a battery trap operating mode, which may allow device100to perform limited functions by providing power to only certain components for limited purposes (e.g., to perform emergency or high priority functionalities) while preventing certain power intensive functionalities, such as by disabling one, some, or all input components, output components, communications components, applications, and/or the like (e.g., to mitigate discharge of the battery (e.g., to prevent battery swell, loss of capacity, etc.)). For example, while operating in the battery trap operating mode, which may also be referred to herein as a normal off operating mode, device100may be configured to require an external power supply to assist device100in harvesting power when starting up again but may be able to start up or power up immediately in response to being charged by an external power supply in a way that provides full functionality of device100. The charge remaining during the battery trap operating mode may be any charge level of power supply108that is in LPEM operating charge level range164or in low battery trap operating charge level range166. However, should the charge level of power supply108fall below ODL threshold charge level167, device100may not be able to start up or power up immediately in response to being charged by an external power supply in a way that provides full functionality of device100, but instead may first require receiving a significant amount of such external power supply before being able to start up in a way that provides full functionality to device100. For example, fast universal serial bus (“USB”) charging may be enabled immediately if the charge level of power supply108is not below ODL threshold charge level167, yet fast USB charging may be delayed until after a certain amount of external power has charged power supply108up above the charge level of ODL threshold charge level167. Unlike in the full or normal operating mode of charge level range162, where there may be sufficient energy remaining in power supply108to power up all of the components of device100(e.g., at their normal operating frequencies), in the battery trap operating mode(s) of charge level(s)164and/or166there may not be sufficient energy remaining in power supply108to power up all of the sub-components of device100(e.g., at their normal operating frequencies), but there may be enough energy remaining in power supply108to run a subset of the components (e.g., a processor, a communications component (e.g., NFC component120), an output component (e.g., a display and/or a haptic component), an input component (e.g., a mechanical button), etc.) of device100(e.g., at their reduced operating frequencies) for a limited amount of time.

Upon the battery charge decreasing to at least LPEM-on threshold charge level163and to no less than LPEM-off threshold charge level165, such that the charge level of power supply108is in LPEM operating charge level range164, device100may be configured to operate in a high battery trap or LPE operating mode, which may allow device100to perform limited functions with NFC communication component120by situationally providing power to NFC communication component120and configuring NFC communication component120to carry out certain actions while device100is operating in the LPE operating mode (e.g., by configuring NFC component120to be in an NFC low power mode or NFC low power express mode in which NFC component120may be enabled to carry out one or more LPEM NFC transactions). However, upon the battery charge decreasing to at least LPEM-off threshold charge level165and to no less than ODL threshold charge level167, such that the charge level of power supply108is in low battery trap operating charge level range166, device100may be configured to operate in a low battery trap operating mode, which may allow device100to perform certain limited functions but without providing power to NFC communication component120(e.g., by configuring NFC component120to be in an NFC OFF mode in which NFC component120may not be enabled to carry out any NFC transactions). Starting up a limited subset of components in a battery trap operating mode (e.g., of charge level164and/or of charge level166) may cause spikes in the current drawn from the PMU and power supply. As the power supply charge level decreases, its ability to cope with those surges may decrease to the point where turning on a component may cause the voltage being supplied to the device to fall below the level at which the device can operate, thereby causing it to crash or behave erratically. LPEM-off threshold charge level165may be defined to avoid this with respect to turning on NFC component120(e.g., the limiting factor may be the ability to power NFC component120sufficiently so that it can communicate with terminal10). ODL threshold charge level167may be provided in order to terminate the current output of power supply108once the battery charge has dropped to or below that threshold charge level167. Upon the battery charge decreasing to at least that threshold charge level167, such that the charge level of power supply108is in disconnect operating charge level range168, device100may be configured to disconnect power supply108from any or all non-required internal discharge components to prevent any further discharge (e.g., to prevent over discharge) of the battery of power supply108(e.g., to operate in a power disconnect operating mode). As mentioned, starting up a limited subset of components in a battery trap operating mode (e.g., of charge level164and/or of charge level166) may cause spikes in the current drawn from the PMU and power supply. As the power supply charge level decreases, its ability to cope with those surges may decrease to the point where turning on a component may cause the voltage being supplied to the device to fall below the level at which the device can operate, thereby causing it to crash or behave erratically. ODL threshold charge level167may be defined to avoid this with respect to turning on any device component (e.g., the limiting factor may be the ability to power any component other than already disabled NFC component120(e.g., the display to present a UI and/or a mechanical button to receive a user input and/or a haptic output component to provide a haptic output and/or the like)).

For example, LPEM-on threshold charge level163(e.g., for defining the initial threshold for enabling an NFC low power mode in which NFC component120may be enabled to carry out one or more LPEM NFC transactions) may be set by a manufacturer of device100to be unchanged throughout the entire period of ownership of device100. Alternatively, LPEM-on threshold charge level163can be dynamic or adaptive, such that the system can set LPEM-on threshold charge level163to be larger or smaller (e.g., through user selection or adjustment or through use of any suitable heuristics or historical device use). In some embodiments, LPEM-on threshold charge level163can use a predictive engine of device100to determine how often the user conducts LPEM NFC transactions (e.g., NFC transactions in an LPE operating mode) and/or NFC transactions generally (e.g., NFC transactions in any device operating mode), and thereafter increase LPEM-on threshold charge level163if the user begins to use NFC transactions more, or decrease LPEM-on threshold charge level163if the user begins to use NFC transactions less. As just one example, maximum threshold charge level161may have a magnitude of about 4.35 Volts or may have a magnitude in a range of about 4.00 Volts to 4.70 Volts, while LPEM-on threshold charge level163may have a magnitude of about 3.20 Volts or may have a magnitude in a range of about 2.85 Volts to 3.55 Volts, while LPEM-off threshold charge level165may have a magnitude of about 2.95 Volts or may have a magnitude in a range of about 2.60 Volts to 3.30 Volts, while ODL threshold charge level167may have a magnitude of about 2.45 Volts or may have a magnitude in a range of about 2.10 Volts to 2.80 Volts. One, some, or each of the power management and threshold features described herein may be opted-into and/or opted-out of by a user of the device (e.g., rather than being set as an automatic or default feature), such that the user may have control over how its device's power supply may operate.

While various NFC transactions may be described herein as being enabled due to NFC communication component120being powered by power supply108of device100while device100is operating either in the normal operating mode of full operating charge level range162(e.g., when NFC communication component120may be in an NFC full power mode state401ofFIG.4) or in the LPE operating mode of LPEM operating charge level range164(e.g., when NFC communication component120may be in an NFC low power mode state451ofFIG.4), in some embodiments, NFC communication component120of device100can be used as a passive transaction device regardless of the level of charge of power supply108being provided to NFC component120(e.g., even when the battery charge is below LPEM-off threshold charge level165or even below ODL threshold charge level167). While being used as a passive transaction device, one or more portions of device100(e.g., one or more portions of NFC communication component120) can be powered by an external electromagnetic field or carrier field that may be associated with a person, business, or system with which a user of device100may intend to conduct contactless proximity-based communication55. For example, a user of device100could be at a public subway station, bus station, or any other suitable transportation facility that may use passive transaction cards in order to provide a person with access to the respective mode of transportation. By placing device100near a carrier field source of terminal10, device100can be provided power for the subsystem(s) of device100that may be configured for passive transactions and thereafter conduct a transaction, thereby allowing the user to access the transportation provided. Of course, for credential security, such passive transactions may only be enabled if an authenticated user has indicated that a particular card may be utilized in such a passive transaction.

As shown inFIG.2, one specific example of electronic device100may be a handheld electronic device, such as an iPhone™, where housing101may allow access to various input components110a-110i, various output components112a-112c, and various I/O components114a-114dthrough which device100and a user and/or an ambient environment may interface with each other. Input component110amay include a button that, when pressed, may cause a “home” screen or menu of a currently running application to be displayed by device100. Input component110bmay be a top or side button for toggling electronic device100between a sleep mode and a wake mode or between any other suitable modes. Input component110cmay include a two-position slider that may disable one or more output components112in certain modes of electronic device100. Input components110dand110emay include buttons for increasing and decreasing the volume output or any other characteristic output of an output component112of electronic device100. Each one of input components110a-110emay be a mechanical input component, such as a button supported by a dome switch, a sliding switch, a control pad, a key, a knob, a scroll wheel, or any other suitable form.

An output component112amay be a display that can be used to display a visual or graphic user interface (“GUI”)180, which may allow a user to interact with electronic device100. GUI180may include various layers, windows, screens, templates, elements, menus, and/or other components of a currently running application (e.g., application103and/or application143) that may be displayed in all or some of the areas of display output component112a. One or more of user input components110a-110imay be used to navigate through GUI180(e.g., from GUI screen190ofFIG.2). For example, one user input component110may include a scroll wheel that may allow a user to select one or more graphical elements182of GUI180. Icons182may also be selected via a touch screen I/O component114athat may include display output component112aand an associated touch input component110f. Such a touch screen I/O component114amay 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. Furthermore, touch screen I/O component114amay employ single point or multi-point (e.g., multi-touch) input sensing.

Icons182may represent various layers, windows, screens, templates, elements, and/or other components that may be displayed in some or all of the areas of display component112aupon selection by the user. Furthermore, selection of a specific icon182may lead to a hierarchical navigation process. For example, selection of a specific icon182may lead to a new screen of GUI180that may include one or more additional icons or other GUI elements of the same application or of a new application associated with that icon182. Textual indicators181may be displayed on or near each icon182to facilitate user interpretation of each graphical element icon182. It is to be appreciated that GUI180may include various components arranged in hierarchical and/or non-hierarchical structures. When a specific icon182is selected, device100may be configured to open a new application associated with that icon182and display a corresponding screen of GUI180associated with that application. For example, when the specific icon182labeled with an NFC LOW POWER MODE textual indicator181(i.e., specific icon183) is selected, device100may launch or otherwise access a specific NFC low power mode or wallet mode application (e.g., application143) and may display screens of a specific user interface that may include one or more tools or features for interacting with NFC component120in a specific manner (e.g., one or more user interfaces for enabling an authenticated user to select one or more credentials that may later be utilized to carry out an LPEM NFC transaction when NFC component120is operating in an NFC low power mode (e.g., for enabling a user to select or provision a credential on device100as an “express mode card”) (e.g., as described with respect to state diagram500ofFIG.5) and/or for enabling an authenticated user to define one or more particular rules for the use of such a credential (e.g., for enabling a user to determine one or more ways in which an identified “express mode card” may be used in an LPEM NFC transaction (e.g., define a maximum number of times that an express mode card may be used during a particular NFC low power mode and/or define a maximum duration of time after a most recent user authentication event that an express mode card may be used in an LPEM NFC transaction))). For each application, screens may be displayed on display output component112aand may include various user interface elements. Additionally or alternatively, for each application, various other types of non-visual information may be provided to a user via various other output components112of device100. For example, device100may be configured to let a user select one or more credentials of a first type but not a second type to be available as an express mode card, where the first type (e.g., simple transit system credentials, such as for the subway, etc.) may be a type of credential that may not warrant as a high a level of security as the second type (e.g., credit card credentials, high security access credentials, etc.).

Electronic device100also may include various other I/O components114that may allow for communication between device100and other devices. I/O component114bmay be a connection port that may be configured for transmitting and receiving data files, such as media files or customer order files, from a remote data source and/or power from an external power source. For example, I/O component114bmay be a proprietary port, such as a Lightning™ connector or a 30-pin dock connector from Apple Inc. of Cupertino, California. I/O component114cmay be a connection slot for receiving a SIM card or any other type of removable component. I/O component114dmay be a headphone jack for connecting audio headphones that may or may not include a microphone component. Electronic device100may also include at least one audio input component110g, such as a microphone, and at least one audio output component112b, such as an audio speaker.

Electronic device100may also include at least one tactile or haptic output component112c(e.g., a rumbler or any other suitable subsystem operative to provide haptic or tactile feedback to a user), a camera and/or scanner input component110h(e.g., a video or still camera, and/or a bar code scanner or any other suitable scanner that may obtain product identifying information from a code, such as a bar code, a QR code, or the like), and a biometric input component110i(e.g., a fingerprint reader or other feature recognition sensor, which may operate in conjunction with a feature-processing application that may be accessible to electronic device100for authenticating a user). As shown inFIG.2, at least a portion of biometric input component110imay be incorporated under or otherwise combined with input component110aor any other suitable I/O component of device100. For example, biometric input component110imay be a fingerprint reader that may be configured to scan the fingerprint of a user's finger as the user interacts with mechanical input component110aby pressing input component110awith that finger. As another example, biometric input component110imay be a fingerprint reader that may be combined with touch input component110fof touch screen I/O component114a, such that biometric input component110imay be configured to scan the fingerprint of a user's finger as the user interacts with touch screen input component110fby pressing or sliding along touch screen input component110fwith that finger. Moreover, as mentioned, electronic device100may further include NFC component120, which may be communicatively accessible to terminal10via antenna116and/or antenna134(not shown inFIG.2). NFC component120may be located at least partially within housing101, and a mark or symbol121can be provided on the exterior of housing101that may identify the general location of one or more of the antennas associated with NFC component120(e.g., the general location of antenna116and/or antenna134).

To facilitate the following discussion regarding the operation of electronic device100in managing near field communications (e.g., communications55with terminal10) during an NFC low power express mode of operation, reference is made to a schematic diagram of a power management subsystem301of electronic device100(e.g., as shown inFIG.3), an exemplary state diagram of various power states of portions of electronic device100(e.g., as shown inFIG.4), an exemplary state diagram of various configurations of portions of electronic device100(e.g., as shown inFIG.5), and front views of screens200aand200bthat may be representative of a graphical user interface of electronic device100during such near field communication management (e.g., as shown inFIGS.2A and2B). The operation described may be achieved with a wide variety of graphical elements and visual schemes. Therefore, the embodiments ofFIGS.2A and2Bare not intended to be limited to the precise user interface conventions adopted herein. Rather, embodiments may include a wide variety of user interface styles.

FIG.3shows a schematic view of near field communication management subsystem301of electronic device100that may be provided to manage near field communications during different operating modes of electronic device100. For example, power management subsystem301may determine when to utilize an NFC low power express mode of electronic device100and/or how to manage NFC component120during such a low power express mode (e.g., how to make credentials of NFC component120appropriately secure and/or appropriately accessible during such a low power express mode).

Electronic device100can be configured to operate according to different power management modes for controlling and managing power consumption by the various components of device100. As shown inFIG.3, for example, power management subsystem301may include a mode detection module310that may be configured to determine when to enter a particular one of various power management modes of electronic device100. For example, mode detection module310may be configured to determine when to enter a particular one of many possible power management modes, such as a full or normal operating mode, a high battery trap or LPE operating mode, a low battery trap operating mode, or a power disconnect operating mode of electronic device100(e.g., as described with respect to battery chart108aofFIG.1A). In particular, mode detection module310can be configured to switch the operation of electronic device100amongst the various particular power management modes for reducing power consumption when device100is not connected to a remote power supply (e.g., when power supply108is not plugged into a wall socket). For example, operation of device100in a particular power management mode can prevent non-essential power intensive processes from being performed by device100while device100is being powered by a battery that has less than a certain threshold of power potential remaining.

As shown inFIG.3, mode detection module310may be configured to poll for or otherwise receive power level data307from power supply108, where power level data307may be indicative of the amount of power remaining in power supply108(e.g., when power supply108may be a battery whose power level may diminish during use). When mode detection module310detects that the remaining power of power supply108indicated by received power level data307has dropped below a particular threshold (e.g., below one of threshold charge levels163,165, or167, or any other suitable threshold), mode detection module310may be configured to generate a switch command311that may be configured to switch electronic device100to a particular power management operating mode based on the particular new operating charge level range entered by power supply108(e.g., to a full or normal operating mode when the charge level has entered range162, to a high battery trap or LPE operating mode when the charge level has entered range164, to a low battery trap operating mode when the charge level has entered range166, or to a power disconnect operating mode when the charge level has entered range162(e.g., as described with respect to battery chart108aofFIG.1A)). For example, as shown inFIG.3, when mode detection module310detects that received power level data307is indicative of a particular characteristic of power supply108(e.g., that power supply108has dropped below a particular power threshold), mode detection module310may be configured to generate switch command311and provide switch command311to a switch application module320of power management subsystem301.

As another example of an initiation event of a particular operating mode (e.g., an NFC low power express mode) that may be detectable by mode detection module310, mode detection module310may be configured to receive input mode selection data309from an input component110(e.g., one or more of input components110a-110i). Such input mode selection data309may be any suitable data generated by input component110that may be indicative of a desire to enter a particular mode. For example, input mode selection data309may be indicative of a user selecting “NFC LOW POWER MODE” icon183of GUI180using touch screen input component110fof I/O component114aofFIG.2, and this may be recognized by mode detection module310as an initiation event for entering an NFC low power express mode. Thus, when mode detection module310receives such specific input mode selection data309, mode detection module310may be configured to generate switch command311and provide switch command311to switch application module320of power management subsystem301. Therefore, in addition to or as an alternative to device100switching to an NFC low power express mode when power supply108is below a certain power threshold (e.g., within LPEM operating charge level range164between LPEM-on threshold charge level163and LPEM-off threshold charge level165), such an NFC low power express power management mode may be entered at a user's discretion or during any other suitable situation.

Regardless of why mode detection module310may generate switch command311and transmit switch command311to switch application module320(e.g., in response to a particular received power level data307and/or in response to a particular received input mode selection data309), switch application module320may be configured to switch electronic device100into a particular power management operating mode (e.g., into an NFC low power express mode) in response to receipt of such a switch command311. This switch process into a new power management operating mode can include switch application module320generating and transmitting one or more disabling commands to one or more components of device100for at least partially shutting down, removing power from, or otherwise at least partially disabling at least one function of such components (e.g., if switching to a lower power mode or if a particular component is otherwise to be at least partially disabled for the new operating mode), which may reduce the power consumption of one or more components of device100and/or may at least partially disable one, some, or all components of device100that are not necessary for at least initially operating device100in the new power management operating mode (e.g., one or more NFC communication component switching commands321for shutting down, removing power from, or otherwise at least partially disabling at least one function of NFC communication component120, one or more output component switching commands323for shutting down, removing power from, or otherwise at least partially disabling at least one function of at least one input component110, one or more input component switching commands325for shutting down, removing power from, or otherwise at least partially disabling at least one function of at least one output component112, and/or one or more processor component switching commands327for shutting down, removing power from, or otherwise at least partially disabling at least one function of at least one processor component102). Alternatively or additionally, this switch process into a new power management operating mode can include switch application module320generating and transmitting one or more enabling commands to one or more components of device100for at least partially turning on, providing power to, or otherwise at least partially enabling at least one function of such components (e.g., if switching to a higher power mode or if a particular component is otherwise to be at least partially enabled for the new operating mode), which may increase the power consumption of one or more components of device100and/or may at least partially enable one, some, or all components of device100that are may be necessary or at least utilized for at least initially operating device100in the new power management operating mode (e.g., one or more NFC communication component switching commands321for turning on, providing power to, or otherwise at least partially enabling at least one function of NFC communication component120, one or more output component switching commands323for turning on, providing power to, or otherwise at least partially enabling at least one function of at least one input component110, one or more input component switching commands325for turning on, providing power to, or otherwise at least partially enabling at least one function of at least one output component112, and/or one or more processor component switching commands327for turning on, providing power to, or otherwise at least partially enabling at least one function of at least one processor component102).

For example, in response to receipt of a switch command311operative to switch device100from a normal operating mode to an NFC low power express mode (e.g., in response to the charge level of power supply108entering into LPEM operating charge level range164or in response to a user input manually requesting a switch into such an NFC low power express mode (e.g., to conserve power of power supply108)), switch application module320generate and transmit an NFC disabling command321to NFC component120as part of the switching process to the NFC low power express mode. Such an NFC disabling command321may be configured to be received by any suitable element of NFC component120such that at least one credential previously enabled by NFC component120prior to receipt of command321may be disabled in response to receipt of command321. As one particular example, command321may disable NFC antenna134and/or booster136of NFC device module130when command321is received by NFC component120, such that no NFC communications55may be transmitted by NFC component120to terminal10after such disablement (e.g., if a user has not selected any credentials provisioned on device100for use during such a mode). As another example, command321may disable a first applet153of a first SSD154of NFC memory module150when command321is received by NFC component120, such that no NFC communications55associated with the credentials of that first applet153may be transmitted by NFC component120to terminal10after such disablement. In some embodiments, command321may disable every applet153of every SSD154of NFC memory module150when command321is received by NFC component120, such that no NFC communications55associated with any credential of any applet153of any SSD154may be transmitted by NFC component120to terminal10after such disablement. However, in other embodiments, command321may disable only some specific applets153of some SSDs154of NFC memory module150when command321is received by NFC component120, such that NFC communications55associated with the credentials of those specific applets (e.g., credit card credentials, which may warrant a high security level) may not be transmitted by NFC component120to terminal10after such disablement, but such that other NFC communications55that are associated with the credentials of other specific applets (e.g., simple transit system credentials, such as for the subway, which may not warrant a high security level) may be transmitted by NFC component120to terminal10after such disablement (e.g., based on default credential settings and/or based on specific user selected settings for particular individual or particular groups or types credentials provisioned on device100). When received by NFC component120, NFC disabling command321may be configured to shut down, remove power from, or otherwise at least partially disable at least one function of NFC component120. In some embodiments, NFC component120may be provided with no NFC disabling command321but instead NFC component120may be operated the same as it was in a full power mode (e.g., NFC component120may be powered the same by power supply108no matter whether device100is in a normal operating mode or an NFC LPEM mode. In some embodiments, power management subsystem301may be configured to switch electronic device100from a normal operating mode to an NFC low power express mode by providing an NFC disabling command321that may prevent NFC command120from receiving any power from power supply108via power management subsystem301and/or by providing an NFC direct power command321dthat may be operative to close a switch321sfor enabling any suitable power321pto be directly provided from power supply108to NFC component120for powering NFC component120during an NFC LPEM mode of operation. In such embodiments, power management subsystem301may also be configured to switch electronic device100from an NFC low power express mode to an NFC off mode (e.g., when switching to a low battery trap operating mode or to a power disconnect operating mode) by providing another NFC direct power command321dthat may be operative to open switch321sfor preventing any power321pfrom being directly provided from power supply108to NFC component120.

In addition to or as an alternative to generating an NFC disabling command321, switch application module320may be configured to switch electronic device100from a normal operating mode to an NFC low power express mode (e.g., in response to the charge level of power supply108entering into LPEM operating charge level range164or in response to a user input requesting a manual switch into such an NFC low power express mode (e.g., to conserve power of power supply108)) by generating and transmitting an output component disabling command323to at least one output component112(e.g., at least one of output components112a-112c). When received by that output component112, such an output component disabling command323may be configured to shut down, remove power from, or otherwise at least partially disable at least one function of that output component112. For example, in response to display output component112areceiving such a disabling command323, display output component112amay be turned off (e.g., no more power may be provided to display output component112a). In some embodiments, power management subsystem301may be configured to switch electronic device100from a normal operating mode to an NFC low power express mode by providing an output component disabling command323to at least one or all output components112for preventing such output component(s) from receiving any power from power supply108via power management subsystem301and by also providing an output direct power command323dthat may be operative to close a switch323sfor enabling any suitable power323pto be directly provided from power supply108to a particular output component112(e.g., haptic output component112c) for powering that particular output component112during an NFC LPEM mode of operation. In such embodiments, power management subsystem301may also be configured to switch electronic device100from an NFC low power express mode to an NFC off mode (e.g., when switching to a low battery trap operating mode or to a power disconnect operating mode) by providing another output direct power command323dthat may be operative to open switch323sfor preventing any power323pfrom being directly provided from power supply108to that particular output component112that had been previously directly powered (e.g., haptic output component112c).

Similarly, switch application module320may be configured to switch electronic device100from a normal operating mode to an NFC low power express mode (e.g., in response to the charge level of power supply108entering into LPEM operating charge level range164or in response to a user input requesting a switch into such an NFC low power express mode (e.g., to conserve power of power supply108)) by generating and transmitting an input component disabling command325to at least one input component110(e.g., one or more of input components110a-110i). When received by that input component110, input component disabling command325may be configured to shut down, remove power from, or otherwise at least partially disable at least one function of that input component110. In some embodiments, power management subsystem301may be configured to switch electronic device100from a normal operating mode to an NFC low power express mode by providing an input component disabling command325to at least one or all input components110for preventing such input component(s) from receiving any power from power supply108via power management subsystem301and by also providing an input direct power command325dthat may be operative to close a switch325sfor enabling any suitable power325pto be directly provided from power supply108to a particular input component110(e.g., side button input component110b) for powering that particular input component110during an NFC LPEM mode of operation. In such embodiments, power management subsystem301may also be configured to switch electronic device100from an NFC low power express mode to an NFC off mode (e.g., when switching to a low battery trap operating mode or to a power disconnect operating mode) by providing another input direct power command325dthat may be operative to open switch325sfor preventing any power325pfrom being directly provided from power supply108to that particular input component110that had been previously directly powered (e.g., side button input component110b).

Similarly, switch application module320may be configured to switch device100from a normal operating mode to an NFC low power express mode or NFC LPE power management mode (e.g., in response to the charge level of power supply108entering into LPEM operating charge level range164or in response to a user input requesting a switch into such an NFC low power express mode (e.g., to conserve power of power supply108)) by generating and transmitting an application disabling command327to processor102. When received by processor102, application disabling command327may be configured to shut down or otherwise at least partially disable one or more applications currently being run by processor102(e.g., to force quit all non-native applications and/or any non-essential applications and/or all applications that were running on device100prior to the generation of that application disabling command327). This may reduce the power consumption of processor102going forward with the switch to the NFC low power express mode.

Moreover, additionally or alternatively, switch application module320may be configured to switch device100from a normal operating mode to an NFC low power express mode (e.g., in response to the charge level of power supply108entering into LPEM operating charge level range164or in response to a user input requesting a switch into such an NFC low power express mode (e.g., to conserve power of power supply108)) by generating and transmitting one or more additional disabling commands (not shown) to at least one other component of device100(e.g., memory104, communication component106, antenna116, etc.), such that, when received by that device component, that component disabling command may be configured to shut down, remove power from, or otherwise at least partially disable at least one function of that device component.

Therefore, switch application module320may be configured to initiate the transition of electronic device100into a new power management mode by generating and transmitting one or more disabling commands and/or one or more enabling commands (e.g., commands321,323,325,327, etc.) that may be configured to shut down, remove power from, or otherwise at least partially disable one, some, or all components of device100that are not necessary for at least initially operating device100in the new power management mode and/or that may be configured to turn on, provide power to, or otherwise at least partially enable one, some, or all components of device100that may be utilized for at least initially operating device100in the new power management mode. For example, as mentioned, one or more disabling commands of switch application module320may be configured to at least partially turn off one or more input components110, one or more output components112, processor102or at least one or more applications being run by processor102, at least some of memory104, at least some or all of communications component106, antenna116, and/or some or all of NFC component120. When at least initially operating in such an NFC low power express mode, electronic device100may be configured to refrain from providing power to or otherwise enabling particular device components that are not necessary for securely managing NFC component120. For example, in response to receiving one or more disabling commands from switch application module320, electronic device100can turn off a hard drive (e.g., memory104), dim or turn off a display (e.g., output component112a), place a processor (e.g., processor102) in a low-power “sleep” or “hibernate” or “off” mode, and/or completely or partially disable NFC component120. Some or all of the power management settings of power management subsystem301can be set automatically or by a user of device100(e.g., the user may define a duration and/or a condition before device100switches between particular power management modes and/or the components that may be at least partially disabled or turned off when switching between different power management modes, such as the NFC low power express mode). By forcing electronic device100to operate in such an NFC low power express mode, switch application module320may eventually allow electronic device100to securely utilize NFC component120for communications55in an efficient manner (e.g., until power supply108is no longer able to power electronic device100to operate in that mode (e.g., until a level of power supply108falls below threshold charge level165)).

Therefore, at least certain modules of power management subsystem301may be configured as a power management unit (“PMU”) that may be coupled to at least one source of power, such as power supply108. Such a PMU may include a microcontroller and can be configured to govern the power functions of device100. Such a PMU may include its own memory (e.g., loaded with software and/or firmware), processor with input/output functionality and timers, as well as one or more converters for measuring the power provided by power supply108. Moreover, additionally or alternatively, such a PMU may include a backup power source that can power components of power management subsystem301even when device100is completely shut down, such that, for example, the current time of a real-time clock (“RTC”) may be maintained. For example, an RTC351may be provided by subsystem301(e.g., by a power mode control application module330or otherwise), where RTC351may be provided as an integrated circuit (e.g., an integrated circuit with one or more general-purpose input/outputs (“GPIOs”)) and/or may include one or more registers353(e.g., one or more RTC counter registers and/or one or more PMU scratch pad registers). Such a PMU may be responsible for coordinating certain functions of device100, including, but not limited to, monitoring power connections and battery charges, controlling power provided to other components of device100, shutting down certain components of device100when they are left idle or deemed to be currently unnecessary to properly operate device100, regulating a real-time clock of device100, and controlling various power management modes of device100. A battery control circuit or power management stage may be connected to a battery and to the base-band/firmware processor. One or more dedicated connections from such a PMU and/or from power supply108to various elements of NFC component120(e.g., device module130, controller module140, and/or memory module150) may also be provided by power management subsystem301. These additional connections may be provided to enable a battery control circuit or power supply circuit to selectively power various components of device100, and especially the various components necessary to perform NFC communication with terminal10.

When switch application module320has received switch command311from mode detection module310and has thereafter generated and transmitted one or more commands (e.g., commands321,323,325, etc.) for at least partially adjusting one, some, or all components of device100for at least initially operating device100in the new power management mode, switch application module320may also be configured to generate and transmit a launching command329to a power mode control application module330of power management subsystem301. In response to receiving launching command329, control application module330may be configured to launch and run at least one application (e.g., application143) that may be specifically tailored to appropriately manage and/or otherwise control electronic device100in the new power management mode. Therefore, for example, operation of device100in an NFC LPE mode may be based on one or more applications accessible to electronic device100(e.g., application143) and/or based on any input instructions being received by electronic device100(e.g., via input component110) that may control such an application.

As an example, when control application module330receives launching command329for managing device100in an NFC LPE power management mode, NFC component120may be initially configured by NFC command321and/or NFC direct power command321dto be in an active antenna mode (e.g., where antenna116and/or antenna134may be actively enabled for NFC communication by electronic device100itself (e.g., by power supply108)). It is to be understood that when NFC component120is initially configured by NFC command321and/or NFC direct power command321dto be in either the passive or active antenna modes, one or more other elements of NFC component120(e.g., an applet153of one or more SSDs154) may be initially disabled by NFC disabling command321and/or NFC direct power command321dto prevent a passive/active antenna from communicating a credential of NFC component120as communication55to terminal10(e.g., certain applets associated with certain credentials may have a particular register or flag set or not set (e.g., due to user preference) that may prevent those credentials from being used in a transaction with terminal10during an NFC LPE power management mode, while other certain applets associated with other certain credentials may have a particular register or flag set or not set (e.g., due to user preference) that may allow those credentials to be used in a transaction with terminal10during an NFC LPE power management mode). For example, one or more flags or registers in NFC component120(e.g., a flag or register in a particular SSD or applet associated with a particular credential) may be set (e.g., while device100is operating in a full or normal operating mode) to enable or not enable one or more particular credentials from being used while in an NFC LPE power management mode. Additionally or alternatively, an LPM flag (“LPMF”) may be set (e.g., to either ‘1’ or ‘0’), for example, in a PMU scratch pad register (e.g., register353(e.g., in non-volatile memory)) in a particular manner based on whether or not any credential has been enabled (e.g., by a user) for use when an NFC LPE mode is entered. For example, as shown inFIG.5, an exemplary state machine500may be provided for illustrating various configurations of portions of electronic device100for determining whether an NFC LPE mode may be utilized by device100. Each state of state machine500may be possible while NFC component120is in an NFC full power mode of an NFC full power mode state401of state diagram400ofFIG.4. For example, at state501of state machine500, electronic device100may be in a state in which there is no credential provisioned on device100(e.g., in NFC component120) that has been selected (e.g., by a user or otherwise) for potential use in a communication55with terminal10during a future NFC low power express mode of operation of device100. In response to any suitable event502in which a first credential may be selected for potential use in a future NFC low power express mode (e.g., when a user selects or provisions a credential on device100as an “express mode card” or “express mode credential” (e.g., while device100is operating in a full or normal operating mode)), device100may be configured to transition from state501to a state521in which there is at least one credential provisioned on device100(e.g., in NFC component120) that has been selected (e.g., by a user or otherwise) for potential use in a communication55with terminal10during a future NFC low power express mode of operation of device100. During such a transition between state501and state521, device100may be configured to take one or more actions506(e.g., automatically) in order for device100to properly perform in accordance with that new state521. For example, as shown, action(s)506may include any suitable action or combination of actions, including, but not limited to, one or more of the following actions:(1) setting NFC_VEN_int=1;(2) setting NFC_GPIO2_AO=OPT_RESET_L=HIGH;(3) setting LPMF=1;(4) loading an output waveform onto a driver amplifier;(5) setting PMU_ALARM_EN=1;(6) configuring PMU_RTC_ALARM for a duration X; and/or(7) configuring a SW_Alarm for a duration X−1 (e.g., any suitable duration less (e.g., slightly less than duration X).
Similarly, in response to any suitable event522in which a last credential may be de-selected for potential use in a future NFC low power express mode (e.g., when a user adjusts the only credential on device100previously identified as an express mode card to a credential that is not to be identified as an express mode card or removes such a card altogether (e.g., while device100is operating in a full or normal operating mode)), device100may be configured to transition from state521to state501in which there is no credential provisioned on device100(e.g., in NFC component120) that has been selected (e.g., by a user or otherwise) for potential use in a communication55with terminal10during a future NFC low power express mode of operation of device100. During such a transition between state521and state501, device100may be configured to take one or more actions526(e.g., automatically) in order for device100to properly perform in accordance with that new state501. For example, as shown, action(s)526may include any suitable action or combination of actions, including, but not limited to, one or more of the following actions:(1) setting NFC_VEN_int=0;(2) setting LPMF=0; and/or(3) setting PMU_ALARM_EN=0.
Additionally or alternatively, in response to any suitable event532in which a SW_Alarm may elapse (e.g., be triggered) while device100is in state521, device100may be configured to take one or more actions536(e.g., automatically) in order for device100to properly respond to event532. For example, as shown, action(s)536may include any suitable action or combination of actions, including, but not limited to, one or more of the following actions:(1) setting PMU_ALARM_EN=1;(2) configuring PMU_RTC_ALARM for another duration X; and/or(3) configuring a SW_Alarm for duration X−1.
Each one of actions506,526, and536may be described in more detail with respect toFIG.4and operation of NFC component120in a low power express mode of electronic device100. It is understood that the various operations and conditions shown in state diagram500ofFIG.5are only illustrative and that existing operations and conditions may be modified or omitted, additional operations and conditions may be added, and the order of certain operations and conditions may be altered.

Control application module330may be configured to receive any suitable input component command331from any suitable input component110(e.g., side button input component110b) that may be at least partially or at least temporarily enabled during the current power management mode (e.g., by power325pduring a low power express mode). Additionally or alternatively, control application module330may be configured to provide any suitable output component command333to any suitable output component112that may be at least partially or at least temporarily enabled during the current power management mode (e.g., haptic output component112cby power323pduring a low power express mode) or for waking up any suitable output component112that may be normally disabled during the current power management mode (e.g., display output component112aduring a battery trap operating mode (e.g., a low power express mode)). Additionally or alternatively, control application module330may be configured to provide any suitable NFC component input command339to any suitable portion of NFC component120that may be at least partially or at least temporarily enabled during the current power management mode (e.g., by power321pduring a low power express mode). Additionally or alternatively, control application module330may be configured to receive any suitable NFC component output command341from any suitable portion of NFC component120that may be at least partially or at least temporarily enabled during the current power management mode (e.g., by power321pduring a low power express mode). Control application module330may be configured to generate any suitable one or more of commands333and/or339(and/or one or more of commands321d,323d, and/or325d) during the current power management mode, and/or to receive any suitable one or more of commands331and/or341during the current power management mode, for example, in accordance with any suitable power management mode application or rule set or state machine that may be specifically tailored to appropriately manage and/or otherwise control electronic device100in the current power management mode (e.g., state machine400ofFIG.4).

For example, as shown inFIG.4, an exemplary state machine400may be provided for illustrating at least one particular manner in which power management subsystem301may operate for managing near field communications during a low power express mode of electronic device100. As shown, at an NFC full power mode (“NFC FPM”) state401, NFC component120may be powered on and may be functioning normally. For example, at state401, electronic device100may be operating in the full or normal operating mode (e.g., when a charge level of power supply108is within full operating charge level range162between threshold charge levels161and163), in which NFC component120and any other suitable components of device100(e.g., a display output component112, a touch screen input component110, an application processor102running any suitable operating system application and/or any suitable specific UI applications, a cellular communications component106, etc.) may be provided with power by power supply108(e.g., via power management system301(e.g., via a PMU)) and may be functioning normally. For example, as shown, while operating in an NFC full power mode of NFC FPM state401, NFC component120may be configured to carry out any suitable transactions or communications55between electronic device100and terminal10at operation401nusing any credential of device100(e.g., whether or not the credential is currently designated as an express mode card). However, in response to detecting any suitable first condition402, the state of electronic device100may transition from state401to an NFC off power mode (“NFC OFF”) state471, at which NFC component120may be powered off (e.g., for conserving power), or, in response to detecting any suitable second condition412, the state of electronic device100may transition from state401to an NFC low power mode (“NFC LPM”) state451, at which NFC component120may remain powered but limited to enabling transactions for only credentials designated as an express mode card (e.g., for conserving power). For example, as shown, while operating in an NFC low power mode of NFC LPM state451, NFC component120may be configured to actively carry out any suitable transactions or communications55between electronic device100and terminal10at operation451nusing any credential of device100that is currently designated as an express mode card. However, while operating in an NFC off power mode of NFC OFF state471, NFC component120may not be configured to actively carry out any suitable transactions or communications55between electronic device100and terminal10(e.g., due to NFC component120being not provided with any power in that state (although it is to be noted that certain passive transactions may be able to occur at NFC OFF state471if certain security measures are taken)).

For example, at state471, in which NFC component120may be powered off, electronic device100may be operating in any suitable operating mode, such as in a completely powered off mode (e.g., when device100has automatically shut down due to a charge level of power supply108falling within disconnect operating charge range168below threshold charge level167or when device100has any other suitable charge level but has been manually shut down by a user (e.g., a possible condition402)) or in a battery trap operating mode (e.g., when a charge level of power supply108has fallen below threshold charge level163and into one of ranges164or166(e.g., a possible condition402)). At state471, a system PMU of device100may be powered off or inactive, power may not be provided to NFC component120(e.g., via power management system301or directly through switch321s), and only limited functionality, if any, may be enabled for other portions of electronic device, such as a functionality for enabling a user to determine if device100is operating in the battery trap mode. For example, if device100is operating in the battery trap mode while at state471, a limited functionality may be enabled by device100for enabling the sensing of a particular user interaction with a particular input component (e.g., a user press of side button input component110b(e.g., detection of any suitable wake event condition472), where side button input component110bmay be at least partially or at least temporarily enabled during the current power management mode (e.g., by power325pduring the battery trap mode)) and then temporarily powering on display output component112a(e.g., by booting up a system PMU, then booting up at least another portion or the rest of the system (e.g., a boot loader and potentially an operating system application)) for displaying a very specific UI screen (e.g., a “dead battery UI” screen190bofFIG.2B(e.g., at an operation482)) in response to sensing such a particular user input component interaction, such that a user may be able to determine that device100is operating in the battery trap mode (e.g., to provide a user some peace of mind that device100is not in a power disconnect operating mode (e.g., of range168)). For example, while device100is operating in a battery trap mode (e.g., when the charge level307of power supply108is within one of ranges164and166) while NFC component is in an NFC off power mode at state471, in response to detection of a button press condition472by input component110bthat may be powered directly by power325p, input component110bmay be configured to generate and transmit any suitable input component command331to control application module330, which may be operative to wake up a system PMU such that control application module330may be configured to provide any suitable output component command333to display output component112athat may normally be disabled during a battery trap operating mode, where that command333may be operative to at least temporarily power on display output component112afor presenting at event482the “dead battery UI” screen190bofFIG.2Bto the user that may be indicative of the current battery trap mode of device100(e.g., via drained battery icon201) but that may not be indicative of any express mode cards being enabled in the current battery trap mode (e.g., due to NFC component120being in the NFC OFF power mode state of state471) (e.g., as compared to a “Express Mode capability UI” screen190aofFIG.2Athat may be presented to a user at event455that may be indicative of a current battery trap mode of device100(e.g., via drained battery icon201) but that may also be indicative of at least one express mode card being enabled in the current battery trap mode (e.g., due to NFC component120being in an NFC low power mode of state451) (e.g., via text203). As shown by a distinction line (“DL”), all operations above line DL in state diagram400may be carried out when a system PMU of device100may be powered on and/or awake and/or active (e.g., when an operating system application or a boot loader application or otherwise may be in use by device100), while all operations below line DL in state diagram400may be carried out when a system PMU of device100may be in an off state or powered off or inactive. For example, when a PMU is in an off state, the PMU may still not be completely turned off, as it may still support processing button presses or one or more other functionalities (e.g., a PMU may include at least one always on domain in the PMU that's still alive when the PMU is in an off state). Alternatively, a PMU may be completely off in an off state. NFC transactions and/or haptic feedback and/or other certain output feedback may be able to occur completely independent of a system PMU (e.g., a PMU can remain in an off state while an NFC component and/or an output component may operate in a low power mode (e.g., an NFC component and/or an output component may be powered on by its own by a power source without relying on any rails from the PMU, and/or may receive the same or different amounts of power when operating in a low power mode or full power mode)). It is to be understood that any suitable wake event or condition452and/or472may be configured as any suitable user interaction that is properly enabled by device100(e.g., raise to wake gesture, a tap on a touch-sensitive display, a voice trigger, a button press, etc.).

One or more suitable conditions402may be satisfied in order to transition from state401to state471, including, but not limited to, a condition in which a user manually shuts down (e.g., powers off) device100(e.g., by pressing and holding side button110bfor at least a particular duration of time (e.g., 3 seconds)), or a condition in which not only is the current charge of power supply108below threshold charge level163(e.g., as may be detected by module310using power level data307) but also no credential on device100is currently designated as an express mode card (e.g., as may be determined when LPMF is equal to ‘0’ (e.g., as may be enforced by an action526of state diagram500)). In some particular embodiments, NFC component120may be configured to transition from NFC FPM state401to NFC OFF state471when a particular NFC state transition sequencing protocol is carried out at operation403. For example, as shown by an NFC state transition sequencing protocol of an NFC state transition operation403, NFC component120may be configured to transition from NFC FPM state401to NFC OFF state471(e.g., after a certain order of certain operations (e.g., when a GPIO output from a system PMU to NFC component120(e.g., “NFC_EN”) is set to “LOW” at least a certain amount of time (e.g., buffer or margin time (e.g., 3 milliseconds)) prior to disabling a supply rail for NFC component120(e.g., a 1.8 Volt supply rail “PP1V8_NFC”), although any other suitable operations may transition NFC component120between state401and state471)).

Alternatively, one or more suitable other conditions412may be satisfied in order to transition from state401to state451, including, but not limited to, a condition in which at least one credential on device100is currently designated as an express mode card (e.g., as may be determined when LPMF is equal to ‘1’ (e.g., as may be enforced by an action506of state diagram500)) when a user manually instructs device100to enter an NFC low power express mode (e.g., in response to power management system receiving particular input mode selection data309from an input component110) (e.g., for conserving device power while maintaining the functionality of the at least one credential of NFC component120designated as an express mode card), or a condition in which at least one credential on device100is currently designated as an express mode card when the current charge of power supply108is detected to fall below threshold charge level163(e.g., as may be detected by module310using power level data307), or a condition in which at least one credential on device100is currently designated as an express mode card when an undervoltage-lockout (“UVLO”) event is detected (e.g., when a voltage of a battery of power supply108is detected to fall below any suitable UVLO threshold of a system PMU of device100). In some particular embodiments, NFC component120may be configured to transition from NFC FPM state401to NFC LPM state451when a particular NFC state transition sequencing protocol is carried out at operation413. For example, as shown by an NFC state transition sequencing protocol of an NFC state transition operation413, NFC component120may be configured to transition from NFC FPM state401to NFC LPM state451(e.g., after a certain order of certain operations (e.g., when a GPIO output from a system PMU to NFC component120(e.g., “NFC_EN”) is set to “LOW” within at least a certain amount of time (e.g., buffer or margin time (e.g., 3 milliseconds)) of disabling a supply rail for NFC component120(e.g., a 1.8 Volt supply rail “PP1V8_NFC”), although any other suitable operations may transition NFC component120between state401and state451)). For example, such an NFC state transition sequencing protocol may be implemented in hardware by a PMU power down sequencer of device100.

At NFC LPM state451, in which NFC component120may be powered (e.g., directly by power321pvia switch321s) while a system PMU may be inactive, electronic device100may be configured to operate in an NFC low power express mode (e.g., mode in which device100, to conserve power, has turned off processor102and every communications component106and every output component112and every input component110, except, perhaps, a particular output component112(e.g., haptic output component112c) and/or a particular input component110(e.g., side button input component110b) to enable a user to detect that device100is operating in the NFC low power express mode. Therefore, at state451, a system PMU of device100may be powered off or inactive, power may be provided to NFC component120(e.g., directly through switch321s), and only limited functionality, if any, may be enabled for other portions of electronic device, such as a functionality for enabling a user to determine if device100is operating in the NFC low power express mode. For example, if device100is operating in the NFC low power express mode while at state451, a limited functionality may be enabled by device100for enabling the sensing of any suitable wake event or particular user interaction with a particular input component (e.g., a user press of side button input component110b(e.g., detection of any suitable wake event condition452), where side button input component110bmay be at least partially or at least temporarily enabled during the current power management mode (e.g., by power325pduring the NFC low power express mode of a battery trap mode)) and then, in response to sensing such a particular user input component interaction and in response to a determination at operation453that a particular power supply condition454is satisfied, temporarily powering on display output component112afor displaying a very specific UI screen (e.g., a “Express Mode capability UI” screen190aofFIG.2A(e.g., at an operation455)), such that a user may be able to determine that device100is operating in the NFC low power express mode (e.g., to provide a user some peace of mind that an express mode NFC transaction may be possible). For example, while device100is operating in the NFC low power express mode while NFC component is in an NFC LPM power mode at state451, in response to detection of any suitable wake event452(e.g., button press condition452by input component110bthat may be powered directly by power325p), input component110bmay be configured to generate and transmit any suitable input component command331to control application module330, which may be operative to wake up a system PMU such that control application module330may be configured to make a determination at operation453that particular power supply condition454is satisfied and then to provide any suitable output component command333to display output component112athat may normally be disabled during a NFC low power express mode of a battery trap operating mode, where that command333may be operative to at least temporarily power on display output component112afor presenting at event455the “Express Mode capability UI” screen190aofFIG.2Ato the user that may be indicative of the current battery trap mode of device100and that may be indicative of the fact that at least one express mode card is enabled in the current NFC low power express mode of the current battery trap mode (e.g., due to NFC component120being in the NFC LPM power mode state of state451) (e.g., as compared to a “dead battery UI” screen190bofFIG.2Bthat may be presented to a user at event482that may be indicative of only a current battery trap mode of device100but that may not also be indicative of at least one express mode card being enabled in the current battery trap mode (e.g., due to NFC component120being in an NFC OFF power mode of state471).

The determination at operation453may be any suitable determination of any suitable power supply condition. For example, in some embodiments, operation453may be operative to determine a condition of a “LOW_V” flag, which may be configured to be indicative of a relationship between the current charge of power supply108and a particular threshold charge level. As a particular example, operation453may generally be used to determine whether the current charge level of power supply108is above or below LPEM-off threshold charge level165, which may be useful to determine whether to keep NFC component120in the NFC LPM power mode of state451or to transition NFC component120from the NFC LPM power mode of state451to the NFC OFF power mode of state471(e.g., for conserving power by powering off NFC component120and terminating the NFC low power express mode while still remaining in a battery trap mode (e.g., a low battery trap operating mode)). In a particular example, device100(e.g., device firmware) may be configured to set a LOW_V flag (e.g., a flag of a register of a system PMU) to be equal to ‘1’ if each one of any suitable number of consecutive samples (e.g.10consecutive samples) of the current charge level of power supply108(e.g., using data307) is determined to be less than LPEM-off threshold charge level165and may be configured to clear or reset the LOW_V flag to be equal to ‘0’ when the current charge level of power supply108is determined to be at least a certain amount greater than LPEM-off threshold charge level165(e.g., at least 0.05 Volts greater than LPEM-off threshold charge level165). Therefore, device100may be configured to make a confident determination at operation453that the current charge level of power supply108is either greater than LPEM-off threshold charge level165by satisfying condition454(e.g., LOW_V=0) or less than LPEM-off threshold charge level165by satisfying condition457(e.g., LOW_V=1). Thus, in response to device100detecting button press condition452and then determining at operation453that the current charge level of power supply108is greater than LPEM-off threshold charge level165by satisfying condition454, device100may be configured to present “Express Mode capability UI” screen190aofFIG.2Aat operation455and then return to (e.g., maintain NFC component120in the NFC LPM mode of) state451(e.g., via operation456, at which a PMU RTC Alarm may be set), as power supply108may be operating in LPEM operating charge level range164.

Alternatively, in response to device100detecting button press condition452and then determining at operation453that the current charge level of power supply108is less than LPEM-off threshold charge level165by satisfying condition457, device100may be configured to transition NFC component120from the NFC LPM mode of state451to the NFC OFF mode of state471(e.g., via operation458and either operation474or operations459and462via state461), as power supply108may no longer be operating in LPEM operating charge level range164. Instead, in order to operate in a low battery trap operating mode for conserving further power by disabling NFC component120, device100may be operative transition NFC component120from the NFC low power mode of NFC LPM state451to the NFC off power mode of NFC OFF state471. Device100may be operative to carry out such a transition by first carrying out operation458. At operation458, device100may be configured to set LPMF to ‘0’, which may prevent any credential on device100from being used as an express mode card until LPMF may be re-set back to ‘1’ (e.g., at operation499, where a user of device100may be reauthenticated (e.g., by entering a PIN to access functionality of a device operating system (e.g., to access screen190ofFIG.2)) once NFC component120has been transitioned back from the NFC off power mode of NFC OFF state471to the NFC full power mode of NFC FPM state401(e.g., via operations492,494, and497), which may provide a layer of security to prevent an unauthorized user from being able to use an express card if/when device100were to ever return to NFC LPM state451after arriving at NFC OFF state471). Additionally or alternatively, at operation458, device100may be configured to disable an alarm (e.g., a PMU_RTC_ALARM (e.g., by setting PMU_ALARM_EN to ‘0’)), such that the alarm may not timeout for initiating a routine while in NFC OFF state471. After operation458, device100may be configured to transition NFC component120from the NFC LPM mode of state451directly to the NFC OFF mode of state471when a particular NFC state transition sequencing protocol is carried out at operation474. Alternatively, NFC component120may be configured to transition from the NFC LPM mode of state451to the NFC OFF mode of state471indirectly via a quick intermediate transition from the NFC LPM mode of state451to the NFC FPM mode of state461. For example, NFC component120may be configured to transition from NFC LPM state451to NFC FPM state461when a particular NFC state transition sequencing protocol is carried out at operation459(e.g., after a certain order of certain operations (e.g., when a supply rail for NFC component120(e.g., a 1.8 Volt supply rail “PP1V8_NFC”) is enabled at least a certain amount of time (e.g., buffer or margin time (e.g., 3 milliseconds)) prior to setting to “HIGH” a GPIO output from a system PMU to NFC component120(e.g., “NFC_EN”), although any other suitable operations may transition NFC component120between state451and state461)), and then NFC component120may be configured to transition from NFC FPM state461to NFC OFF state471when a particular NFC state transition sequencing protocol is carried out at operation462(e.g., after a certain order of certain operations (e.g., when a GPIO output from a system PMU to NFC component120(e.g., “NFC_EN”) is set to “LOW” at least a certain amount of time (e.g., buffer or margin time (e.g., 3 milliseconds)) prior to disabling a supply rail for NFC component120(e.g., a 1.8 Volt supply rail “PP1V8_NFC”), although any other suitable operations may transition NFC component120between state461and state471)). Then, once NFC component120has been transitioned to the NFC off power mode of NFC OFF state471, NFC component120may remain in the NFC off power mode of NFC OFF state471until power supply108has been charged above a particular threshold charge level (e.g., threshold charge level163) for enabling the transition back to the NFC full power mode of NFC FPM state401. For example, as shown, when in state471, device100may be operative to carry out a device charging operation492(e.g., in response to any suitable charging event (e.g., a user plugging device100into an electrical outlet for receiving external power generated by an electrical power plant)), during which any suitable “Charge & Display UI” screen may be presented to a user at event494(e.g., to enable a user to determine that the device is being properly charged). However, until operation492results in the charge level of power supply108passing above a particular threshold charge level (e.g., threshold charge level163) for satisfying condition496for enabling the transition back to the NFC full power mode of NFC FPM state401at operation497, device100may satisfy condition495and may remain in the NFC FPM state471. Therefore, device100may enable charging of power supply108for returning to FPM state401from OFF state471, but may not enable charging of power supply108for returning only to LPM state451from OFF state471. Moreover, it is to be understood that if device transitioned to OFF state471from ON state401in response to a condition402in which a user manually shut down (e.g., powered off) device100, then operation492may include a user attempting to manually turn back on device100, in which case condition496may be satisfied and device100may transition back from state471to state401without any actual charging of power supply108.

With further reference to state451, if device100is operating in the NFC low power express mode while at state451, rather than (e.g., before) detection of any button press condition452for initiating a user-initiated device capability check process, an alarm timeout condition442may be detected for initiating a silent device-initiated device capability check process, in response to which device100may be operative to make a determination at operation463about the current charge level of power supply108with respect to any suitable threshold charge level (e.g., threshold charge level165). For example, alarm timeout condition442may be a condition in which a PMU_RTC_ALARM is triggered, where such a condition may be triggered when an RTC counter register value of an RTC (e.g., a value of a first register353of RTC351) is greater than a defined PMU_RTC_ALARM value (e.g., a stored value in hardware of a system PMU). As shown inFIG.5, while device100may be in state521and operating in a full power operating mode, in response to any suitable event532in which a SW_Alarm may elapse (e.g., be triggered), device100may be configured to take one or more actions536, including, but not limited to, one or more of the following actions:(1) setting PMU_ALARM_EN=1, which may enable an alarm of a system PMU to be enabled and/or set and/or monitored;(2) configuring PMU_RTC_ALARM for another duration X, which may reset the value of PMU_RTC_ALARM by any suitable duration X; and/or(3) configuring a SW_Alarm for X−1 minutes, which may reset the value of a software alarm by any suitable duration that may be at least slightly less that the reset duration of the PMU_RTC_ALARM, or, other embodiments, the SW_alarm may be any other suitable software alarm, which could be a part of any other periodic system wakeup event (e.g., to check for cellular signal strength, etc.).

This may enable the PMU_RTC_ALARM to be continuously reset to a duration X (e.g., 1 hour, 2 hours, 4 hours, etc.) at a periodic frequency at least slight less than duration X while device100may be in the full power state521(e.g., state401when LPMF is set to ‘1’). Therefore, a hardware based PMU alarm (PMU_RTC_ALARM) may always be active when device100may transition from NFC FPM state401to NFC LPM state451, such that alarm timeout condition442ought to occur at least within duration X of the transition from state401to state451. In response to detection of a PMU alarm (PMU_RTC_ALARM) timing out at condition442, device100may be operative to (e.g., further) wake up a system PMU such that control application module330may be configured to make a determination at operation463that particular power supply condition464is satisfied and then to re-set the PMU alarm (PMU_RTC_ALARM) (e.g., to duration X) at operation456before returning to NFC LPM state451. Alternatively, in response to detection of a PMU alarm (PMU_RTC_ALARM) timing out at condition442, device100may be operative to (e.g., further) wake up a system PMU such that control application module330may be configured to make a determination at operation463that particular power supply condition465is satisfied and then to proceed to operation458for transitioning NFC component120from NFC LPM state451to NFC OFF state471.

The determination at operation463may be may be any suitable determination of any suitable power supply condition, such as the same operation as operation453or an operation substantially similar to operation453. For example, in some embodiments, operation463may be operative to determine a condition of a “LOW_V” flag, which may be configured to be indicative of a relationship between the current charge of power supply108and a particular threshold charge level. As a particular example, operation463may generally be used to determine whether the current charge level of power supply108is above or below LPEM-off threshold charge level165, which may be useful to determine whether to keep NFC component120in the NFC LPM power mode of state451or to transition NFC component120from the NFC LPM power mode of state451to the NFC OFF power mode of state471(e.g., for conserving power by powering off NFC component120and terminating the NFC low power express mode while still remaining in a battery trap mode (e.g., a low battery trap operating mode)). In a particular example, device100(e.g., device firmware) may be configured to set a LOW_V flag (e.g., a flag of a register of a system PMU) to be equal to ‘1’ if each one of any suitable number of consecutive samples (e.g.10consecutive samples) of the current charge level of power supply108(e.g., using data307) is determined to be less than LPEM-off threshold charge level165and may be configured to clear or reset the LOW_V flag to be equal to ‘0’ when the current charge level of power supply108is determined to be at least a certain amount greater than LPEM-off threshold charge level165(e.g., at least 0.05 Volts greater than LPEM-off threshold charge level165). Therefore, device100may be configured to make a confident determination at operation463that the current charge level of power supply108is either greater than LPEM-off threshold charge level165by satisfying condition464(e.g., LOW_V=0) or less than LPEM-off threshold charge level165by satisfying condition465(e.g., LOW_V=1). Thus, in response to device100detecting RTC alarm timeout condition442and then determining at operation463that the current charge level of power supply108is greater than LPEM-off threshold charge level165by satisfying condition464, device100may be configured to return to (e.g., maintain NFC component120in the NFC LPM mode of) state451(e.g., via operation456, at which a PMU RTC Alarm may be re-set), as power supply108may be operating in LPEM operating charge level range164. Alternatively, in response to device100detecting RTC alarm timeout condition442and then determining at operation463that the current charge level of power supply108is less than LPEM-off threshold charge level165by satisfying condition465, device100may be configured to transition NFC component120from the NFC LPM mode of state451to the NFC OFF mode of state471(e.g., via operation458and either operation474or operations459and462via state461), as power supply108may no longer be operating in LPEM operating charge level range164. Therefore, condition442may enable device100to periodically determine whether or not to transition from state451to state471(e.g., especially in absence of any regular condition452).

NFC component120may remain in the NFC low power mode of NFC LPM state451until power supply108has been charged above a particular threshold charge level (e.g., threshold charge level163) for enabling the transition back to the NFC full power mode of NFC FPM state401. For example, as shown, when in state451, device100may be operative to carry out a device charging operation466(e.g., in response to any suitable charging event (e.g., a user plugging device100into an electrical outlet for receiving external power generated by an electrical power plant)), during which any suitable “Charge & Display UI” screen may be presented to a user at event467(e.g., to enable a user to determine that the device is being properly charged). However, until operation466results in the charge level of power supply108passing above a particular threshold charge level (e.g., threshold charge level163) for satisfying condition468for enabling the transition back to the NFC full power mode of NFC FPM state401at operation498(e.g., an operation that may be similar to operation459), device100may satisfy condition469and may remain in the NFC LPM state451. Therefore, device100may enable charging of power supply108for returning to FPM state401from LPM state451, and may also enable charging of power supply108for returning to LPM state451from LPM state451(e.g., to remain in LPM state451if the charging accomplished at operation466is not sufficient to satisfy condition468). Moreover, it is to be understood that if device transitioned to LPM state451from ON state401in response to a condition412in which a user manually instructed such a transition, then operation466may include a user attempting to manually instruct a transition back from state451to state401(e.g., through any suitable interaction with an enabled input component (e.g., through a long hold of button input component110bor another input component interaction)), in which case condition466may be satisfied and device100may transition back from state451to state401without any actual charging of power supply108. It is understood that the various operations and conditions shown in state diagram400ofFIG.4are only illustrative and that existing operations and conditions may be modified or omitted, additional operations and conditions may be added, and the order of certain operations and conditions may be altered.

As mentioned, while operating in an NFC low power mode of NFC LPM state451, NFC component120may be configured to carry out any suitable transactions or communications55between electronic device100and terminal10at operation451nusing any credential of device100that is currently designated as an express mode card. At any point during even an attempt at a transaction at operation451nor after a transaction has been completed at operation451n, device100may be configured to generate any suitable output that may be operative to indicate such an attempted or completed transaction to a user of device100. However, due to the fact that a majority or the entirety of all software and/or applications and/or even a system PMU may be inactive or off during such an attempt or at such a completion of operation451n, NFC component120may be operative to control the generation and transmission of an appropriate command for inciting such an output to user. For example, as shown inFIG.3, NFC component120may be configured to generate and transmit any suitable NFC activity output command341directly to any suitable output component112that may be operable during the NFC LPM mode of operation of state451(e.g., haptic output component112cthat may be powered by power323pdirectly from power supply108during the NFC LPM mode of operation of state451). For example, haptic feedback output component112cmay include a haptic driver amplifier361on which may be loaded a haptic waveform363that may be automatically played back by haptic driver amplifier361in response to haptic feedback output component112creceiving an NFC activity output command341from NFC component120while device100may be operating in an NFC low power mode of NFC LPM state451. This may enable device100to provide haptic feedback to a user in response to NFC component120at least attempting to conduct a transaction with terminal55using an express mode card while device100may be operating in an NFC low power mode of NFC LPM state451(e.g., without a system PMU may be inactive or off and may not be providing any power to any output component or NFC component of device100). As shown inFIG.5by an action506when a first express mode card is enabled on device100, an output waveform (e.g., waveform363) may be loaded onto a driver amplifier (e.g., amplifier361) (e.g., a haptic waveform may be loaded onto a haptic driver amplifier and/or an audio waveform may be loaded onto an audio driver amplifier), and/or a GPIO (“NFC_GPIO2_AO=OPT_RESET_L=HIGH”) may be set high as always on to enable haptic driver amplifier361to be triggered in an NFC low power mode, such that it may be ensured that a haptic waveform may be available for playback during an NFC low power mode. Although this output has been described as a haptic feedback output using a haptic feedback output component, it is to be understood that various other types of output information may be presented by any other suitable output component other than a haptic output component (e.g., user information may be provided audibly to a user via audio speaker output component112b(e.g., any suitable audio waveform may be loaded onto any suitable audio driver amplifier and used in a similar manner to any haptic waveform and/or any haptic driver amplifier described above) or visibly to a user via a visual output component (e.g., an LED)). Therefore, device100may be operative to carry out one or more NFC transactions and provide any suitable output that may be operative to indicate such an attempted or completed transaction to a user of device100while in a low powered operating state at which both a system PMU and any device operating system may be off or disabled or inactive. Various transitions between states of state diagram400(e.g., above line DL) may be accomplished using a system PMU and a boot loader application of device100but not a full operating system application, such that significant power savings may be realized, while certain actions within a state (e.g., below line DL (e.g., action451n, which may include generating a haptic or other user detectable output)) may be accomplished without even using a system PMU or loading any application for realizing additional power savings while also securely enabling certain NFC transactions for improving user convenience.

Although many of the concepts described herein (e.g., with respect to one, some, or each ofFIGS.1-5) have been described with respect to managing near field communications (e.g., by NFC component120) during different power management modes of an electronic device, it is to be understood that various other types of communications (e.g., by any other suitable communications component or communications circuitry) and/or any other suitable device functionalities may be similarly managed. For example, any suitable first type of communications circuitry106(e.g., a higher powered communications circuitry, such as broadband cellular network communications circuitry or Wi-Fi, etc.) may be turned off or disabled or inactive during any suitable battery trap operating mode while any suitable second type of communications circuitry106(e.g., a lower powered communications circuitry, such as Bluetooth or the like) may be selectively or continuously used during any suitable battery trap operating mode. Therefore, device100may be operative to carry out one or more specific communication type functionalities (e.g., Bluetooth communications) and provide any suitable output that may be operative to indicate such an attempted or completed communication of that type to a user of device100(e.g., playing back a particular audio waveform in response to a Bluetooth communication being received by the device) while in a low powered operating state at which both a system PMU and any device operating system and/or any other communication type functionalities (e.g., cellular) may be off or disabled or inactive. Various transitions between states of state diagram400(e.g., above line DL) may be accomplished using a system PMU and a boot loader application of device100but not a full operating system application, such that significant power savings may be realized, while certain actions within a state (e.g., below line DL (e.g., action451n, which may include generating a haptic or other user detectable output)) may be accomplished without even using a system PMU or loading any application for realizing additional power savings while also securely enabling certain types of communications for improving user convenience (e.g., enabling Bluetooth communications to provide certain functionality to the device in the low powered operating state (e.g., communicate with other devices via Bluetooth to enable detection of the device in the low powered operating state) (e.g., the LPMF may be set to ‘1’ if a user wishes for the Bluetooth communication component to be enabled during the low powered operating state and the LPMF may be set to ‘0’ if a user wishes for the Bluetooth communication component not to be enabled during the low powered operating state)). Therefore, if the device's operating system is not running because the device needs to be charged, there may still be enough power in the battery to support the express mode (e.g., to support “Express Card” transactions). The device may be configured to automatically support this feature with any suitable credentials, including, but not limited to, a transit card designated as an “Express Transit” card (e.g., automatically upon provisioning or manually by a user), student ID cards with “Express Mode” turned on, and/or the like. The device may be configured such that, in response to receiving any suitable user interaction with any suitable device input component, such as a user pressing a side button, the device may display a low battery icon as well as text indicating Express Cards are available to use. The NFC controller may perform express card transactions under the same conditions as when the device's operating system is running, except that transactions may be indicated with only limited output component use (e.g., haptic notification, but without any visible notification being presented). This feature may not be available when a standard user initiated shutdown is performed.

FIG.6is a flowchart of an illustrative process600for operating an electronic device that includes a near field communication component. At operation602of process600, while the electronic device is operating in a normal power mode of the electronic device, during which the near field communication component is operating in a full power mode of the near field communication component, a low power mode initiation event may be detected with the electronic device (e.g., the charge of power supply108of device100may be detected to be below threshold163). At operation604of process600, in response to the detection of operation602of process600, a status of a low power mode flag (LPMF) of the electronic device may be determined (e.g., a status of the LPMF of device100may be determined). At operation606of process600, in response to the detection of operation602of process600, the electronic device may be transitioned from operating in the normal power mode of the electronic device to operating in a low power mode of the electronic device by disabling a plurality of subsystems of the electronic device, transitioning the near field communication component from operating in the full power mode of the near field communication component to operating in a low power mode of the near field communication component when the determined status of the LPMF is a first status, and transitioning the near field communication component from operating in the full power mode of the near field communication component to operating in an off mode of the near field communication component when the determined status of the LPMF is a second status that is different than the first status, wherein the near field communication component uses less power when operating in the off mode of the near field communication component than when operating in the low power mode of the near field communication component (e.g., device100may transition from a normal power mode to a low power mode by disabling a power management unit and/or a device operating system of device100, and by providing power from power supply108to NFC component120for enabling communication of an express mode credential when LPMF=1 (e.g., by configuring NFC component120in an NFC low power mode state451) or by providing no power from power supply108to NFC component120when LPMF=0 (e.g., by configuring NFC component120in an NFC off mode state471)).

It is understood that the operations shown in process600ofFIG.6are only illustrative and that existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be altered.

FIG.7is a flowchart of an illustrative process700for operating an electronic device that includes a communication component and a power supply. At operation702of process700, a low power mode initiation event may be detected with the electronic device (e.g., the charge of power supply108of device100may be detected to be below threshold163). At operation704of process700, in response to the detection of operation702of process700, at least one of a power management unit of the electronic device or an operating system of the electronic device may be disabled (e.g., a power management unit and/or a device operating system of device100may be disabled). At operation706of process700, in response to the detection of operation702of process700, when at least one express mode credential is available on the electronic device, power may be provided from the power supply to the communication component for enabling the communication component to communicate data from the at least one express mode credential to a remote terminal (e.g., NFC component120may be provided with power from power supply108for enabling communication of an express mode credential when LPMF=1). At operation708of process700, in response to the detection of operation702of process700, when no express mode credential is available on the electronic device, the communication component may be prevented from receiving any power from the power supply (e.g., no power may be provided by power supply108to NFC component120when LPMF=0).

It is understood that the operations shown in process700ofFIG.7are only illustrative and that existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be altered.

FIG.8is a flowchart of an illustrative process800for operating an electronic device that includes a communication component, a memory register, and a battery. At operation802of process800, a charge of the battery may be detected to be below a predetermined threshold (e.g., the charge of power supply108of device100may be detected to be below threshold163). At operation804of process800, in response to the detection of operation802of process800, a number of subsystems of the electronic device may be disabled (e.g., a power management unit and/or a device operating system and/or a touch screen input component of device100may be disabled). At operation806of process800, in response to the detection of operation802of process800, when the status of the memory register is a first status, power may be provided from the battery to the communication component for enabling the communication component to communicate data with a remote terminal (e.g., NFC component120may be provided with power from power supply108for enabling communication of an express mode credential when LPMF=1). At operation808of process800, in response to the detection of operation802of process800, when the status of the memory register is a second status that is different than the first status, the communication component may be prevented from receiving any power from the battery (e.g., no power may be provided by power supply108to NFC component120when LPMF=0).

It is understood that the operations shown in process800ofFIG.8are only illustrative and that existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be altered.

Moreover, one, some, or all of the processes described with respect toFIGS.1-8may each be implemented by software, but may also be implemented in hardware, firmware, or any combination of software, hardware, and firmware. Instructions for performing these processes may also be embodied as machine- or computer-readable code recorded on a machine- or computer-readable medium. In some embodiments, the computer-readable medium may be a non-transitory computer-readable medium. Examples of such a non-transitory computer-readable medium include but are not limited to a read-only memory, a random-access memory, a flash memory, a CD-ROM, a DVD, a magnetic tape, a removable memory card, and a data storage device (e.g., an optical data storage device, such as memory104and/or memory module150ofFIG.1). In other embodiments, the computer-readable medium may be a transitory computer-readable medium. In such embodiments, the transitory computer-readable medium can be distributed over network-coupled computer systems so that the computer-readable code is stored and executed in a distributed fashion. For example, such a transitory computer-readable medium may be communicated from one electronic device to another electronic device using any suitable communications protocol (e.g., the computer-readable medium may be communicated to electronic device100via communications component106(e.g., as at least a portion of application103and/or application143)). Such a transitory computer-readable medium may embody computer-readable code, instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A modulated data signal may be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.

It is to be understood that any or each module of either one or both of NFC component120and power management subsystem301may be provided as a software construct, firmware construct, one or more hardware components, or a combination thereof. For example, any or each module of either one or both of NFC component120and power management subsystem301may be described in the general context of computer-executable instructions, such as program modules, that may be executed by one or more computers or other devices. Generally, a program module may include one or more routines, programs, objects, components, and/or data structures that may perform one or more particular tasks or that may implement one or more particular abstract data types. It is also to be understood that the number, configuration, functionality, and interconnection of the modules of either one or both of NFC component120and power management subsystem301are only illustrative, and that the number, configuration, functionality, and interconnection of existing modules may be modified or omitted, additional modules may be added, and the interconnection of certain modules may be altered.

At least a portion of one or more of the modules of either one or both of NFC component120and power management subsystem301may be stored in or otherwise accessible to device100in any suitable manner (e.g., in memory104of device100(e.g., as at least a portion of application103and/or application143)). Any or each module of either one or both of NFC component120and power management subsystem301may be implemented using any suitable technologies (e.g., as one or more integrated circuit devices), and different modules may or may not be identical in structure, capabilities, and operation. Any or all of the modules or other components of either one or both of NFC component120and power management subsystem301may be mounted on an expansion card, mounted directly on a system motherboard, or integrated into a system chipset component (e.g., into a “north bridge” chip).

Any or each module of either one or both of NFC component120and power management subsystem301may be a dedicated system implemented using one or more expansion cards adapted for various bus standards. For example, all of the modules may be mounted on different interconnected expansion cards or all of the modules may be mounted on one expansion card. With respect to NFC component120, by way of example only, the modules of NFC component120may interface with a motherboard or processor102of device100through an expansion slot (e.g., a peripheral component interconnect (“PCI”) slot or a PCI express slot). Alternatively, NFC component120need not be removable but may include one or more dedicated modules that may include memory (e.g., RAM) dedicated to the utilization of the module. In other embodiments, NFC component120may be integrated into device100. For example, a module of NFC component120may utilize a portion of device memory104of device100. Any or each module of either one or both of NFC component120and power management subsystem301may include its own processing circuitry and/or memory. Alternatively, any or each module of either one or both of NFC component120and power management subsystem301may share processing circuitry and/or memory with any other module of NFC component120and/or power management subsystem301and/or processor102and/or memory104of device100.

As mentioned, electronic device100may drive a display (e.g., display output component112a) with graphical data to display a graphical user interface (“GUI”)180. GUI180may be configured to receive touch input via a touch input component110f. Embodied as a touch screen (e.g., with display output component112aas I/O component114a), touch I/O component110fmay display GUI180. Alternatively, GUI180may be displayed on a display (e.g., display output component112a) separate from touch input component110f. GUI180may include graphical elements displayed at particular locations within the interface. Graphical elements may include, but are not limited to, a variety of displayed virtual input devices, including virtual scroll wheels, a virtual keyboard, virtual knobs, virtual buttons, any virtual user interface (“UI”), and the like. A user may perform gestures at one or more particular locations on touch input component110f, which may be associated with the graphical elements of GUI180. In other embodiments, the user may perform gestures at one or more locations that are independent of the locations of graphical elements of GUI180. Gestures performed on a touch input component110may directly or indirectly manipulate, control, modify, move, actuate, initiate, or generally affect graphical elements, such as cursors, icons, media files, lists, text, all or portions of images, or the like within the GUI. For instance, in the case of a touch screen, a user may directly interact with a graphical element by performing a gesture over the graphical element on the touch screen. Alternatively, a touch pad may generally provide indirect interaction. Gestures may also affect non-displayed GUI elements (e.g., causing user interfaces to appear) or may affect other actions of device100(e.g., affect a state or mode of a GUI, application, or operating system). Gestures may or may not be performed on a touch input component110in conjunction with a displayed cursor. For instance, in the case in which gestures are performed on a touchpad, a cursor or pointer may be displayed on a display screen or touch screen and the cursor or pointer may be controlled via touch input on the touchpad to interact with graphical objects on the display screen. In other embodiments, in which gestures are performed directly on a touch screen, a user may interact directly with objects on the touch screen, with or without a cursor or pointer being displayed on the touch screen. Feedback may be provided to the user via bus118in response to or based on the touch or near touches on a touch input component110. Feedback may be transmitted optically, mechanically, electrically, olfactory, acoustically, or the like or any combination thereof and in a variable or non-variable manner.

While there have been described systems, methods, and computer-readable media for managing near field communications, it is to be understood that many changes may be made therein without departing from the spirit and scope of the subject matter described herein in any way. Insubstantial changes from the claimed subject matter as viewed by a person with ordinary skill in the art, now known or later devised, are expressly contemplated as being equivalently within the scope of the claims. Therefore, obvious substitutions now or later known to one with ordinary skill in the art are defined to be within the scope of the defined elements.

Therefore, those skilled in the art will appreciate that the invention can be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation.