Low power fast mode management of near field communications using an electronic device

Abstract

The present disclosure relates to managing near field communications using a low power quick mode of an electronic device. The present invention provides systems, methods, and computer readable media for managing near field communications during a low power quick mode of an electronic device that can make credentials of a near field communications ("NFC") component properly secure and properly accessible while also limiting power consumption of the NFC component and other components of the electronic device.

Description

[0001] Cross-references to related applications

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2019 / 024271, international application date of March 27, 2019, entry into the Chinese national phase date of December 22, 2020, Chinese national application number 201980042196.1, and invention title "Managing Near Field Communication Using Low Power Fast Mode of Electronic Device".

[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 679909, filed June 3, 2018, and U.S. Patent Application No. 16 / 128206, filed September 11, 2018, each of which is incorporated herein by reference in its entirety. Technical Field

[0004] This disclosure relates to the management of near-field communications, and more specifically to the management of near-field communications using low-power fast modes of electronic devices. Background Technology

[0005] Portable electronic devices (e.g., cellular phones) may be equipped with near-field communication (“NFC”) components that enable proximity-based contactless communication with another entity. Typically, these communications are associated with monetary transactions or other secure data transactions that users rely on daily, such as credit card payments and public transportation tickets. However, because battery-powered devices have limited power available, their NFC capabilities are often impaired or rendered unusable when the available power drops below a certain threshold. Summary of the Invention

[0006] This document describes systems, methods, and computer-readable media for managing power usage in devices capable of near-field communication and / or other wireless communication technologies.

[0007] For example, a method for operating an electronic device including a near-field communication (NFC) component may be provided, the method comprising: detecting a low-power mode initiation event of the electronic device while the electronic device is operating in a normal power mode of the electronic device, during which the NFC component is operating in a full power mode of the NFC component; and in response to the detection: determining the state of a low-power mode flag (LPMF) of the electronic device, and causing the electronic device to switch from operating in the normal power mode of the electronic device to operating in the low-power mode of the electronic device, wherein causing the electronic device to switch includes: disabling a plurality of subsystems of the electronic device; when the determined state of the LPMF is a first state, switching the NFC component from operating in the full power mode of the NFC component to operating in the low-power mode of the NFC component; and when the determined state of the LPMF is a second state different from the first state, switching the NFC component from operating in the full power mode of the NFC component to operating in a shutdown mode of the NFC component, wherein the NFC component uses less power when operating in the shutdown mode of the NFC component than when operating in the low-power mode of the NFC component.

[0008] For example, a method may be provided for operating an electronic device including a communication component and a power supply, the method comprising: detecting a low-power mode initiation event of the electronic device; and in response to the detection: disabling at least one of the power management unit of the electronic device or the operating system of the electronic device; supplying power from the power supply to the communication component when at least one fast-mode credential is available on the electronic device so that the communication component can transmit data from the at least one fast-mode credential to a remote terminal; and preventing the communication component from receiving any power from the power supply when no fast-mode credential is available on the electronic device.

[0009] For example, a method may be provided for operating an electronic device including a communication component, a storage register, and a battery, the method comprising: detecting that the charge of the battery is below a predetermined threshold; and in response to the detection: disabling multiple subsystems of the electronic device; when the state of the storage register is a first state, supplying power from the battery to the communication component to enable the communication component to transmit data with a remote terminal; and when the state of the storage register is a second state different from the first state, preventing the communication component from receiving any power from the battery.

[0010] The purpose of providing this summary is merely to outline some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described in this summary are merely illustrative and should not be construed as narrowing the scope or substance of the subject matter described herein in any way. Unless otherwise stated, features described in the context of one example may be combined or used in conjunction with features described in the context of one or more other examples. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0011] The following discussion refers to the following figures, wherein similar reference numerals throughout the text refer to similar parts, and wherein:

[0012] Figure 1 A schematic diagram of an exemplary system including electronic devices for managing near-field communication;

[0013] Figure 1A It is shown in detail Figure 1 Exemplary battery charts showing various battery state-of-charge thresholds for exemplary batteries of electronic devices;

[0014] Figure 2 yes Figure 1 A front view of an illustrative example of an electronic device;

[0015] Figure 2A and Figure 2B This illustrates the process used to manage near-field communication. Figure 1 and Figure 2 A front view of an exemplary screen of a graphical user interface for an electronic device;

[0016] Figure 3 for Figures 1 to 2B A schematic diagram of the illustrative portion of an electronic device;

[0017] Figure 4 yes Figures 1 to 3 An exemplary state diagram of various power states of a portion of an electronic device;

[0018] Figure 5 yes Figures 1 to 3 An exemplary state diagram of various configurations of parts of an electronic device; and

[0019] Figures 6 to 8 This is a flowchart of an exemplary process for managing communications. Detailed Implementation

[0020] Systems, methods, and computer-readable media for managing near-field communication (NFC) may be provided. NFC can be managed differently depending on the different power management modes of an electronic device. In certain low-power management modes, certain components of the electronic device may be at least partially disabled or turned off to save power. When the electronic device operates in these modes, credentials (e.g., payment credentials) for NFC components within the device can be appropriately secure and / or appropriately accessible, while the power consumption of the NFC components is limited or reduced. For example, in a low-power operating state where the system power management unit (“PMU”) and any device operating system can be turned off or disabled or inactive, the electronic device can be used to perform one or more NFC transactions using one or more specific credentials (e.g., credentials previously designated as a fast-mode card), and provide any suitable output that can be used to instruct the user of the device on such attempted or completed transactions. Various transitions between power management states can be achieved using the electronic device's system PMU and bootloader application instead of a full operating system application, enabling significant power savings. At the same time, certain actions within a state, such as NFC transactions in a low power management state, which may include generating haptic or other user-detectable outputs, can be achieved even without using the system PMU or loading any application for additional power savings, while also securely implementing certain NFC transactions to improve user convenience.

[0021] Figure 1 This is an illustrative diagram of a communication system 1, which may include a terminal 10 and an electronic device 100 for managing near-field communication 55 with the terminal 10, according to some embodiments. The electronic device 100 may include, but is not limited to, a music player (e.g., an iPod available from Apple Inc. (Cupertino, California)). TM Video players, still image players, game consoles, other media players, music recorders, movie or video cameras or recorders, still life cameras, other media recorders, wireless equipment, medical equipment, home appliances, vehicle instruments, musical instruments, calculators, cellular phones (e.g., iPhones available from Apple Inc.) TM Other wireless communication devices, personal digital assistants, remote controls, pagers, computers (e.g., desktop computers, laptops), tablet computers (e.g., iPads available from Apple Inc.) TM(e.g., servers, etc.), monitors, televisions, audio equipment, set-top boxes, miniature speakers, modems, routers, printers, or any combination thereof. In some embodiments, electronic device 100 may perform a single function (e.g., a device dedicated to managing near-field communications), while in other embodiments, electronic device 100 may perform multiple functions (e.g., a device for managing near-field communications, playing music, and receiving and transmitting telephone calls).

[0022] Electronic device 100 can be any portable, mobile, handheld, or micro electronic device that can be configured to manage near-field communication while the user is in motion. Some micro electronic devices may have features larger than handheld electronic devices such as iPods. TM Small shape factor. Exemplary microelectronic devices can be integrated into a variety of objects, including but not limited to watches (e.g., the Apple Watch available from Apple Inc.). TM Rings, necklaces, belts, belt accessories, headphones, shoe accessories, virtual reality devices, glasses, other wearable electronic devices, accessories for sports equipment, accessories for fitness equipment, keychains, or any combination thereof. Alternatively, electronic device 100 may not be portable at all, but rather generally stationary.

[0023] like Figure 1 As shown, for example, electronic device 100 may include processor 102, memory 104, communication component 106, power supply 108, input component 110, output component 112, antenna 116, and near field communication (“NFC”) component 120. Electronic device 100 may also include bus 118, which provides one or more wired or wireless communication links or paths for transmitting data and / or power to, from, or between various other components of device 100. In some embodiments, one or more components of electronic device 100 may be combined or omitted. Furthermore, electronic device 100 may include components that are not combined or included in... Figure 1 Other components. For example, electronic device 100 may include motion sensing circuitry, a compass, any other suitable components, or Figure 1 Several examples of the components are shown. For simplicity, Figure 1 Only one component of each of these components is shown in the image.

[0024] Memory 104 may include one or more storage media, such as hard disk drives, 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. Memory 104 may include cache memory, which may be one or more different types of memory used for temporarily storing data of electronic device applications. Memory 104 may be permanently embedded within electronic device 100, or may be incorporated into one or more suitable types of cards (e.g., a Subscriber Identity Module (“SIM”) card or a Secure Digital (“SD”) memory card that can be repeatedly inserted into and removed from electronic device 100. The memory 104 may store media data (e.g., music files and image files), software (e.g., functions for implementing the device 100), firmware, preference information (e.g., media playback preferences), lifestyle information (e.g., dietary preferences), exercise information (e.g., information acquired by a motion monitoring device), transaction information (e.g., information such as credit card information), wireless connectivity information (e.g., information that enables the device 100 to establish a wireless connection), subscription information (e.g., information for tracking podcasts or TV shows or other media subscribed to by users), contact information (e.g., phone numbers and email addresses), calendar information, any other suitable data, or any combination thereof.

[0025] A communication component 106 may be provided to allow device 100 to communicate with one or more other electronic devices or servers using any suitable communication protocol. For example, the communication component 106 may support Wi-Fi (e.g., 802.11 protocol), ZigBee (e.g., 802.15.4 protocol), WiDi, etc. TM Ethernet, Bluetooth TM Bluetooth TM Low power (“BLE”), high frequency systems (e.g., 900MHz communication systems, 2.4GHz communication systems, and 5.6GHz communication systems), infrared, Transmission Control Protocol / Internet Protocol (“TCP / IP”) (e.g., any protocol used in each TCP / IP layer), Stream Control Transport Protocol (“SCTP”), Dynamic Host Configuration Protocol (“DHCP”), Hypertext Transfer Protocol (“HTTP”), BitTorrent TM File Transfer Protocol ("FTP"), Real-Time Transfer Protocol ("RTP"), Real-Time Streaming Protocol ("RTSP"), Real-Time Control Protocol ("RTCP"), Remote Audio Output Protocol ("RAOP"), Real Data Transfer Protocol TMThe following protocols are used: RTP (“RDTP”), UDP (“UDP”), SSH (“SSH”), WDS (“WDS”) bridging, any communication protocol that can be used by telephone-free and cellular telephone and personal email devices (e.g., Global System for Mobile Communications (“GSM”), GSM plus Enhanced Data Rate GSM Evolution (“EDGE”), Code Division Multiple Access (“CDMA”), Orthogonal Frequency Division Multiple Access (“OFDMA”), High-Speed ​​Packet Access (“HSPA”), Multi-Band, etc.), any communication protocol that can be used by a Low Power Wireless Personal Area Network (“6LoWPAN”) module, any suitable cellular communication protocol (e.g., broadband cellular network technologies (e.g., 3G, 4G, 5G, etc.)), any other communication protocol, or any combination thereof. The communication component 106 may also include or be electrically coupled to any suitable transceiver circuitry (e.g., transceiver circuitry via bus 118 or antenna 116) that enables device 100 to be communicatively coupled to another device (e.g., a host computer or accessory device) and to communicate wirelessly or via a wired connection (e.g., using a connector port) with that other device. The communication component 106 may be configured to determine the geographic location of electronic device 100. For example, the communication component 106 may utilize a Global Positioning System (“GPS”) or a regional or site-range positioning system that may use cell tower positioning technology or Wi-Fi technology.

[0026] Power source 108 may include any suitable circuitry for receiving and / or generating power and supplying that power to one or more other components of electronic device 100. For example, power source 108 may be coupled to a power grid (e.g., when device 100 is not being used as a portable device or when the device's battery is being charged at a power outlet using power generated by a power plant). Alternatively, power source 108 may be configured to generate power from a natural source (e.g., solar energy using solar cells). Alternatively, power source 108 may include one or more batteries for providing power (e.g., when device 100 is used as a portable device). For example, power source 108 may include one or more of the following: batteries (e.g., gel batteries, nickel-metal hydride batteries, nickel-cadmium batteries, nickel-metal hydride batteries, lead-acid batteries, or lithium-ion batteries), uninterruptible power supplies or continuous power supplies (“UPS” or “CPS”), and circuitry for processing power received from a power source (e.g., power generated by a power plant and delivered to the user via a power outlet or otherwise). The power supply 108 can provide the power as alternating current (AC) or direct current (DC), and can be processed to convert the power to have specific characteristics or limit the received power to have specific characteristics. For example, the power can be converted to DC or derived from DC, and constrained to one or more values ​​of the average power, effective power, peak power, energy per pulse, voltage, current (e.g., measured in amperes), or any other characteristic of the received power. For example, based on the needs or demands of electronic device 100 or peripheral devices that can be coupled to electronic device 100, the power supply 108 can be used to request or provide a specific amount of power at different times (e.g., to request more power when charging a battery than when the battery is fully charged).

[0027] One or more input components 110 may be provided to allow a user to interact or interact with device 100. For example, input components 110 may take many forms, including but not limited to touchpads, dial pads, clickable touchscreens, scroll wheels, touchscreens, one or more buttons (e.g., keyboards), mice, joysticks, trackballs, microphones, cameras, scanners (e.g., barcode scanners or any other suitable scanners that can obtain product identification information from codes such as barcodes, QR codes, etc.), proximity sensors, light detectors, motion sensors, biometric sensors (e.g., fingerprint readers or other feature-based sensors that can be operated in conjunction with feature processing applications accessible to electronic device 100 to authenticate the user), and combinations thereof. Each input component 110 may be configured to provide one or more dedicated control functions for making selections or issuing commands associated with operating device 100.

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

[0029] As a specific example, electronic device 100 may include a display output component as output component 112. Such a display output component may include any suitable type of display or interface for presenting visual data to a user. The display output component may include a display embedded in or coupled to device 100 (e.g., a removable display). The 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-conducting electron emission display (“SED”), a carbon nanotube display, a nanocrystal display, any other suitable type of display, or combinations thereof. Alternatively, the display output component may include a movable display or projection system for providing content display on a surface remote from electronic device 100, such as, for example, a video projector, a head-up display, or a three-dimensional (e.g., holographic) display. Furthermore, the display output component may include a digital viewfinder or a mechanical viewfinder, such as the type found in compact digital cameras, reflex cameras, or any other suitable still camera or video camera. Display output components may include display driver circuitry, circuitry for driving the display driver, or both, and such display output components may be used to display content that may be directed by processor 102 (e.g., media playback information, application screens for applications implemented on electronic device 100, information about ongoing communication operations, information about incoming communication requests, device operation screens, etc.).

[0030] It should be noted that one or more input components and one or more output components are sometimes collectively referred to herein as input / output (“I / O”) components or I / O interfaces (e.g., input component 110 and output component 112 are collectively referred to as I / O components or I / O interfaces 114). For example, input component 110 and output component 112 may sometimes be a single I / O component 114, such as a touchscreen, which can receive input information by a user touching the display screen and can also provide visual information to the user via the same display screen.

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

[0032] Electronic device 100 may also include a near field communication (“NFC”) component 120. NFC component 120 may be any suitable proximity-based communication mechanism enabling contactless transactions or communications 55 between electronic device 100 and terminal 10 (e.g., a payment terminal). NFC component 120 may allow short-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 component 120 may allow short-range communication at higher data rates (e.g., 560 Mbps) and may be compatible with any suitable standards such as TransferJet. TMProtocol compatibility. Communication between NFC component 120 and terminal 10 can occur within any suitable short distance D between device 100 and terminal 10, such as a range of approximately 2 cm to 4 cm (or any other distance greater than 4 cm or less than 2 cm), and can operate at any suitable frequency (e.g., 13.56 MHz). For example, such short-range communication of NFC component 120 can occur via magnetic field induction, which allows NFC component 120 to communicate with other NFC devices and / or retrieve information from tags with radio frequency identification (“RFID”) circuitry. NFC component 120 can provide means of acquiring product information, transmitting payment information, and otherwise communicating with external devices (e.g., terminal 10).

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

[0034] NFC device module 130 may include NFC data module 132, NFC antenna 134, and NFC enhancer 136. NFC data module 132 may be configured to include, route, or otherwise provide any suitable data that may be transmitted from NFC component 120 to terminal 10 as part of contactless proximity-based communication or NFC communication 55. Alternatively, NFC data module 132 may be configured to include, route, or otherwise receive any suitable data that may be received from terminal 10 by NFC component 120 as part of contactless proximity-based communication 55.

[0035] The NFC transceiver or NFC antenna 134 can be any suitable antenna or other suitable transceiver circuit that typically enables communication 55 from the NFC data module 132 to the terminal 10 and / or from the terminal 10 to the NFC data module 132. Therefore, the NFC antenna 134 (e.g., a loop antenna) can be provided specifically to enable the proximity-based contactless communication capabilities of the NFC component 120.

[0036] Alternatively or otherwise, NFC component 120 may utilize the same transceiver circuitry or antenna (e.g., antenna 116) as another communication component of electronic device 100 (e.g., communication component 106). For example, communication component 106 may utilize antenna 116 to enable WiFi, Bluetooth communication between electronic device 100 and another remote entity. TMAlternatively, GPS communication may be used, and NFC component 120 may utilize antenna 116 to enable contactless proximity-based communication or NFC communication 55 between the NFC data module 132 of NFC device module 130 and another entity (e.g., terminal 10). In such embodiments, NFC device module 130 may include NFC enhancer 136, which may be configured to provide appropriate signal amplification for data of NFC component 120 (e.g., data within NFC data module 132) such that such data can be properly transmitted to terminal 10 as communication 55 via shared antenna 116. For example, shared antenna 116 may need to be amplified from enhancer 136 before antenna 116 (e.g., a non-loop antenna) can be properly enabled for transmitting contactless proximity-based communication or NFC communication 55 between electronic device 100 and terminal 10 (e.g., the power required to transmit NFC data using antenna 116 may be more than the power required to transmit other types of data using antenna 116).

[0037] NFC controller module 140 may include at least one NFC processor module 142. NFC processor module 142 may operate in conjunction with NFC device module 130 to enable, activate, allow, and / or otherwise control NFC component 120 for transmitting NFC communication 55 between electronic device 100 and terminal 10. NFC processor module 142 may exist as a standalone component, may be integrated into another chipset, or may be integrated with processor 102, for example, as part of a system-on-a-chip (“SoC”). Figure 1 As shown, the NFC processor module 142 of the NFC controller module 140 can be used to run one or more applications, such as an NFC low-power mode application or a wallet application 143 that can help indicate the functionality of the NFC component 120. Application 143 may include, but is not limited to, one or more operating system applications, firmware applications, NFC low-power applications, or any other suitable application that the NFC component 120 can access (e.g., application 103). The NFC controller module 140 may include one or more protocols such as a near-field communication interface and protocol (“NFCIP-1”) for communicating with another NFC device (e.g., terminal 10). The protocol can be used to adjust the communication speed and designate one of the connected devices as the initiating device for controlling near-field communication.

[0038] NFC controller module 140 can control the near-field communication mode of NFC component 120. For example, NFC processor module 142 can be configured to switch NFC device module 130 between a read / write mode for reading information from an NFC tag (e.g., from terminal 10) to NFC data module 132 (e.g., communication 55), a peer-to-peer mode for exchanging data with another NFC-enabled device (e.g., terminal 10) (e.g., communication 55), and a card emulation mode for allowing another NFC-enabled device (e.g., terminal 10) to read information from NFC data module 132 (e.g., communication 55). NFC controller module 140 can also be configured to switch NFC component 120 between an active mode and a passive mode. For example, NFC processor module 142 can be configured to switch NFC device module 130 between an active mode in which NFC device module 130 can generate its own RF field and a passive mode in which NFC device module 130 can use load adjustment to transmit data to another device (e.g., terminal 10) generating the RF field (e.g., in conjunction with NFC antenna 134 or sharing antenna 116). Compared to operation in such an active mode, operation in such a passive module can extend the battery life of the electronic device 100. The mode of the NFC device module 130 can be controlled based on user preferences and / or the preferences of the manufacturer of the device 100, which can be defined or otherwise determined by applications running on the device 100 (e.g., application 103 and / or application 143).

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

[0040] NFC memory module 150 may include one or more of an issuer security domain (“ISD”) 152 and a supplementary security domain (“SSD”) 154 (e.g., a service provider security domain (“SPSD”), a trusted service manager security domain (“TSMSD”) and so on), which may be defined and managed by NFC specification standards (e.g., GlobalPlatform). For example, ISD 152 may be part of NFC memory module 150, wherein a trusted service manager (“TSM”) or issuing financial institution may store keys and / or other suitable information used to create or otherwise provide one or more credentials (e.g., credentials associated with various credit cards, bank cards, gift cards, access cards, passes, etc.) on electronic device 100 (e.g., via communication component 106) for credential content management and / or security domain management. A specific supplemental security domain (“SSD”) 154 (e.g., one of SSDs 154-154b) may be associated with a specific credential (e.g., a specific credit card credential, a specific public transport card credential, or a specific space (e.g., building) access card credential) that enables the electronic device 100 to grant specific privileges or payment rights. Each SSD 154 may have its own manager key 155 for its own application or applet 153, which may need to be activated to enable the specific credential of that SSD 154 to be used by the NFC device module 130 for NFC communication 55. For example, a specific SSD 154 may be associated with a specific credit card credential. However, when the specific applet 153 of that specific SSD 154 has been enabled or otherwise activated or unlocked for such use, the specific credential may only be transmitted by the NFC component 120 to the terminal 10 as NFC communication 55 (e.g., the specific credential may only be accessible by the NFC data module 132). Security features can be provided to enable the use of NFC component 120, which may be particularly useful when transmitting payment information such as credit card information or bank account information to terminal 10. Such security features may also include a secure storage area with restricted access. For example, access to the secure storage area may require user authentication via personal identification number (“PIN”) input or via user interaction with a biometric sensor. In some embodiments, some or all of the security features may be stored within NFC memory module 150. Furthermore, security information used for communicating with terminal 10, such as authentication keys, may be stored within NFC memory module 150. In some embodiments, NFC memory module 150 may include a microcontroller embedded within electronic device 100.

[0041] Terminal 10 may include a reader for detecting, reading, or otherwise receiving NFC communication 55 from electronic device 100 (e.g., when electronic device 100 enters within a distance or proximity D from terminal 10). Therefore, it should be noted that the NFC communication 55 between terminal 10 and electronic device 100 can occur wirelessly, and thus, unobstructed “line of sight” is not required between the respective devices. As described above, NFC device module 130 may be passive or active. When passive, NFC device module 130 may be activated only when within the response range D of a suitable reader of terminal 10. For example, the reader of terminal 10 may emit a relatively low-power radio wave field that can be used to power an antenna (e.g., shared antenna 116 or NFC-dedicated antenna 134) utilized by NFC device module 130, thereby enabling the antenna to transmit appropriate NFC communication information (e.g., credit card credential information) from NFC data module 132 to terminal 10 as NFC communication 55 via antenna 116 or antenna 134. When active, the NFC device module 130 may be combined with or otherwise have access to the local power source of the electronic device 100 (e.g., power source 108), which enables the shared antenna 116 or the dedicated NFC antenna 134 to actively transmit NFC communication information (e.g., credit card credential information) as NFC communication 55 from the NFC data module 132 to the terminal 10 via antenna 116 or antenna 134, instead of reflecting radio frequency signals as in the case of the passive NFC device module 130.

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

[0043] The electronic device 100 may also be provided with a housing 101 that at least partially encloses one or more components of the device 100 to protect them from external debris and other degrading forces. In some embodiments, one or more components may be housed within their own housing (e.g., input component 110 may be a separate keyboard or mouse located within its own housing and capable of communicating wirelessly or via wires with processor 102, which may be housed within its own housing).

[0044] Figure 1AAn exemplary battery diagram 108a is shown, detailing various potential state-of-charge thresholds for an exemplary power source 108 (e.g., an exemplary battery) of an electronic device 100. Specifically, Figure 1A Different operating modes of device 100 can be enabled based on the amount of energy that can be retained in power source 108, as battery diagram 108a can represent the actual energy remaining in the battery of power source 108, wherein diagram 108a can show in detail the various possible levels and thresholds that device 100 can incorporate into its operation. For example, as shown in the figure, battery diagram 108a may include a first or fully operational charge level range 162, which may be any charge level between a maximum threshold charge level 161 and a first switching threshold, software threshold, or low-power fast mode (“LPEM”) on threshold charge level 163; a second or high battery trap or LPEM operational charge level range 164, which may be any charge level between an LPEM on threshold charge level 163 and a second switching threshold, or low-power or LPEM off threshold charge level 165; a third or low battery trap operational charge level range 166, which may be any charge level between an LPEM off threshold charge level 165 and a third switching threshold or over-discharge lockout (“ODL”) threshold charge level 167; and a fourth or disconnect operational charge level range 168, which may be any charge level between an ODL threshold charge level 167 and a minimum threshold charge level 169.

[0045] When the charge level of power supply 108 is within the full operating charge level range 162, device 100 can generally be configured to operate in a full or normal operating mode. This allows device 100 to perform functions such as making phone calls, connecting to Wi-Fi, playing media files, and / or any other suitable function that is part of the normal functioning of device 100 (e.g., by configuring NFC component 120 to be in NFC full power mode). An LPEM turn-on threshold charge level 163 may be provided to limit the current output of power supply 108 once the battery charge has dropped to or below the threshold charge level 163. When the battery charge decreases to at least the threshold charge level 163 and not less than the ODL threshold charge level 167, such that the charge level of power supply 108 is within the LPEM operating charge level range 164 or the low battery trap operating charge level range 166, device 100 can typically be configured to operate in a battery trap operating mode. This allows device 100 to perform limited functions by providing power only to certain components for limited purposes (e.g., performing emergency or high-priority functions), while preventing certain power-intensive functions, such as by disabling one, some, or all input components, output components, communication components, applications, etc. (e.g., to mitigate battery discharge (e.g., to prevent battery swelling, capacity loss, etc.)). For example, when operating in battery trap operating mode (which may also be referred to herein as normal shutdown operating mode), device 100 may be configured to require an external power supply to assist device 100 in obtaining power upon restart, but may be able to start up or power on immediately in response to charging by an external power supply in a manner that provides device 100 with full functionality. The remaining charge during battery trap operation mode can be any charge level of power supply 108 within the LPEM operating charge level range 164 or within the low battery trap operating charge level range 166. However, if the charge level of power supply 108 drops below the ODL threshold charge level 167, device 100 may not be able to immediately start up or power on in response to charging by an external power source in a manner that provides full functionality to device 100; instead, it may first require a significant amount of such external power before it can be started up in a manner that provides full functionality to device 100. For example, if the charge level of power supply 108 is not below the ODL threshold charge level 167, fast universal serial bus (“USB”) charging may be immediately enabled, but fast USB charging may be delayed until a certain amount of external power has charged power supply 108 to a charge level above the ODL threshold charge level 167.Unlike the all-or normal operating mode of charge level range 162, where power supply 108 has sufficient energy remaining to power all components of device 100 (e.g., at its normal operating frequency), in one or more battery trap operating modes of charge levels 164 and / or 166, power supply 108 may not have sufficient energy remaining to power all sub-components of device 100 (e.g., at its normal operating frequency), but power supply 108 may have sufficient energy remaining to operate a subset of components of device 100 (e.g., processor, communication components (e.g., NFC component 120), output components (e.g., display and / or haptic components), input components (e.g., mechanical buttons) etc.) for a limited amount of time (e.g., at its reduced operating frequency).

[0046] When the battery charge decreases to at least the LPEM turn-on threshold charge level 163 and not less than the LPEM turn-off threshold charge level 165, such that the charge level of the power supply 108 is within the LPEM operating charge level range 164, the device 100 can be configured to operate in a high battery trap or LPE operating mode. This allows the device 100 to perform limited functions using the NFC communication component 120 by providing power to the NFC communication component 120 as contextually required and configuring the NFC communication component 120 to perform certain actions when the device 100 operates in LPE operating mode (e.g., by configuring the NFC component 120 to be in an NFC low power mode or an NFC low power fast mode, wherein the NFC component 120 can be enabled to perform one or more LPEM NFC transactions). However, when the battery charge decreases to at least the LPEM shutdown threshold charge level 165 and not less than the ODL threshold charge level 167, such that the charge level of power supply 108 is within the low battery trapping operation charge level range 166, device 100 can be configured to operate in a low battery trapping operation mode. This allows device 100 to perform certain limited functions without providing power to NFC communication component 120 (e.g., by configuring NFC component 120 in an NFC shutdown mode, in which mode NFC component 120 is not enabled to perform any NFC transactions). Enabling a limited subset of components in battery trapping operation modes (e.g., charge levels 164 and / or 166) can result in spikes in current drawn from the PMU and power supply. As the power supply charge level decreases, its ability to handle these surges can decrease to the point that enabling components may cause the voltage supplied to the device to drop below a level where the device is operational, leading to its failure or malfunction. A threshold charge level 165 for LPEM shutdown can be defined to avoid this situation relative to the NFC-enabled component 120 (e.g., the limiting factor could be the ability to fully power the NFC component 120 so that it can communicate with the terminal 10). An ODL threshold charge level 167 can be provided to terminate the current output of the power supply 108 once the battery charge has dropped to or below this threshold charge level 167. When the battery charge decreases to at least the threshold charge level 167, such that the charge level of the power supply 108 is within the disconnect operation charge level range 168, the device 100 can be configured to disconnect the power supply 108 from any or all unwanted internal discharge components to prevent any further discharge of the battery of the power supply 108 (e.g., to prevent over-discharge) (e.g., to operate in a power disconnect operation mode). As mentioned, a finite subset of components activated in battery trap operation modes (e.g., charge levels 164 and / or charge levels 166) can result in spikes in the current drawn from the PMU and the power supply. As the power charge level decreases, its ability to handle these surges can decrease to the point that turning on the components may cause the voltage supplied to the device to drop below the level at which the device can operate, thus causing it to crash or malfunction.The ODL threshold charge level 167 can be defined to avoid this situation relative to turning on any device component (e.g., the limiting factor could be the ability to power any component other than the disabled NFC component 120 (e.g., a display for presenting a UI and / or mechanical buttons for receiving user input and / or haptic output components for providing haptic output, etc.)).

[0047] For example, the LPEM enable threshold charge level 163 (e.g., an initial threshold for enabling NFC low-power mode, where NFC component 120 can be enabled to perform one or more LPEM NFC transactions) may be set by the manufacturer of device 100 to remain constant throughout the ownership life of device 100. Alternatively, the LPEM enable threshold charge level 163 may be dynamic or adaptive, allowing the system to set the LPEM enable threshold charge level 163 to be larger or smaller (e.g., by user selection or adjustment, or by using any suitable heuristic or historical device usage). In some embodiments, the LPEM enable threshold charge level 163 may be determined using a prediction engine of device 100 to determine the frequency with which a user performs LPEM NFC transactions (e.g., NFC transactions in LPE operating mode) and / or general NFC transactions (e.g., NFC transactions in any device operating mode), and then the LPEM enable threshold charge level 163 may be increased if the user begins to use more NFC transactions, or decreased if the user begins to use fewer NFC transactions. As an example only, the maximum threshold charge level 161 may have a value of approximately 4.35 volts or may have a value in the range of approximately 4.00 volts to 4.70 volts, while the LPEM turn-on threshold charge level 163 may have a value of approximately 3.20 volts or may have a value in the range of approximately 2.85 volts to 3.55 volts, while the LPEM turn-off threshold charge level 165 may have a value of approximately 2.95 volts or may have a value in the range of approximately 2.60 volts to 3.30 volts, while the ODL threshold charge level 167 may have a value of approximately 2.45 volts or may have a value in the range of approximately 2.10 volts to 2.80 volts. One, some, or each of the power management and threshold features described herein may be selected to be enabled and / or disabled by the user of the device (e.g., rather than being set to automatic or default features), allowing the user to control how the power supply of their device can operate.

[0048] Although various NFC transactions can be described herein as being due to the normal operating mode of device 100 at a full operating charge level range 162 (e.g., when the NFC communication component 120 may be in a state of...), Figure 4 (when in NFC full power mode state 401) or in LPE operation mode with LPEM operating charge level range 164 (e.g., when NFC communication component 120 can be in...) Figure 4 When operating in NFC low-power mode state 451, the NFC communication component 120 is enabled by power supply 108 of device 100. In some embodiments, the NFC communication component 120 of device 100 can be used as a passive transaction device, regardless of the charge level of the power supply 108 supplied to the NFC component 120 (e.g., even when the battery charge is below the LPEM shutdown threshold charge level 165 or even below the ODL threshold charge level 167). When used as a passive transaction device, one or more parts of device 100 (e.g., one or more parts of NFC communication component 120) can be powered by an external electromagnetic field or carrier field that can be associated with a system that a person, business, or user of device 100 may intend to use for contactless proximity-based communication 55. For example, a user of device 100 may be at a public subway station, bus station, or any other suitable transportation facility where a passive transaction card can be used to provide access to the corresponding mode of transportation. By placing device 100 near the carrier field source of terminal 10, power can be supplied to one or more subsystems of device 100 that can be configured for passive transactions, and then transactions can be made, thereby allowing the user to access the provided means of transport. Of course, for credential security, such passive transactions can only be enabled if an authenticated user has indicated that a specific card can be used for such passive transactions.

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

[0050] Output component 112a may be a display capable of displaying a visual user interface or graphical user interface (“GUI”) 180 that allows a user to interact with electronic device 100. GUI 180 may include various layers, windows, screens, templates, elements, menus, and / or other components of a currently running application (e.g., application 103 and / or application 143) that can be displayed in all or some areas of the display output component 112a. One or more user input components 110a-110i may be used in the GUI 180 (e.g., from...) Figure 2 Navigation is performed on the GUI screen 190. For example, a user input component 110 may include a scroll wheel that allows the user to select one or more graphical elements 182 of the GUI 180. Icons 182 can also be selected via a touchscreen I / O component 114a that may include a display output component 112a and an associated touch input component 110f. Such a touchscreen I / O component 114a may employ any suitable type of touchscreen input technology, such as, but not limited to, resistive, capacitive, infrared, surface acoustic wave, electromagnetic, or near-field imaging. Furthermore, the touchscreen I / O component 114a may employ single-point input sensing or multi-point (e.g., multi-touch) input sensing.

[0051] Icon 182 may represent various layers, windows, screens, templates, elements, and / or other components that can be displayed in some or all areas of display component 112a when selected by the user. Furthermore, selection of a specific icon 182 may result in hierarchical navigation processing. For example, selection of a specific icon 182 may result in a new screen of GUI 180, which may include one or more additional icons or other GUI elements of the same application or a new application associated with that icon 182. Text indicators 181 may be displayed on or near each icon 182 to help the user interpret each graphical element icon 182. It should be understood that GUI 180 may include various components arranged in hierarchical and / or non-hierarchical structures. When a specific icon 182 is selected, device 100 may be configured to open a new application associated with that icon 182 and display the corresponding screen of GUI 180 associated with that application. For example, when a specific icon 182 (i.e., specific icon 183) marked with an NFC Low Power Mode text indicator 181 is selected, device 100 may launch or otherwise access a specific NFC Low Power Mode or Wallet Mode application (e.g., application 143) and may display a screen with a specific user interface that may include one or more tools or features for interacting with NFC component 120 in a specific manner (e.g., one or more user interfaces that enable an authenticated user to select one or more credentials that can later be used to perform LPEM NFC transactions when NFC component 120 is operating in NFC Low Power Mode (e.g., for enabling the user to select or provide credentials as a "Quick Mode Card" on device 100) (e.g., as relative to...). Figure 5 (as described in state diagram 500) and / or for enabling an authenticated user to define one or more specific rules for using such credentials (e.g., one or more ways to enable a user to determine that an identified “Fast Mode Card” can be used in LPEM NFC transactions (e.g., limiting the maximum number of times a Fast Mode Card can be used during a specific NFC low-power mode and / or limiting the maximum duration after the most recent user authentication event in an LPEM NFC transaction)). For each application, a screen can be displayed on display output component 112a and the screen may include various user interface elements. In addition or alternatively, for each application, various other types of non-visual information may be provided to the user via various other output components 112 of device 100. For example, device 100 may be configured to allow the user to select one or more credentials of a first type instead of a second type as available for Fast Mode Card, wherein the first type (e.g., simple access system credentials, such as those for subways, etc.) may be a type of credential that may not guarantee a high level of security like the second type (e.g., credit card credentials, high-security access credentials, etc.).

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

[0053] Electronic device 100 may also include at least one tactile or haptic output component 112c (e.g., a roller or any other suitable subsystem for providing tactile or haptic feedback to a user), a camera and / or scanner input component 110h (e.g., a video camera or still camera, and / or a barcode scanner or any other suitable scanner capable of obtaining product identification information from codes such as barcodes, QR codes, etc.), and a biometric input component 110i (e.g., a fingerprint reader or other feature identification sensor that can be operated in conjunction with a feature processing application accessible to electronic device 100 for user authentication). Figure 2 As shown, at least a portion of the biometric input component 110i can be incorporated under or otherwise combined with the input component 110a or any other suitable I / O component of the device 100. For example, the biometric input component 110i can be a fingerprint reader configured to scan the fingerprint of a finger when a user interacts with the input component 110a by pressing the user's finger against the mechanical input component 110a. As another example, the biometric input component 110i can be a fingerprint reader that can be combined with the touch input component 110f of the touchscreen I / O component 114a, such that the biometric input component 110i can be configured to scan the fingerprint of a finger when a user interacts with the touchscreen input component 110f by pressing the user's finger against the touchscreen input component 110f or sliding along the touchscreen input component 110f. Furthermore, as mentioned, the electronic device 100 may also include an NFC component 120, and the terminal 10 can be connected via antenna 116 and / or antenna 134 (…). Figure 2The NFC component 120 (not shown) can be communicatively accessed. The NFC component 120 may be located at least partially within the housing 101, and a mark or symbol 121 may be provided on the exterior of the housing 101 at the general location of one or more antennas associated with the NFC component 120 (e.g., the general location of antenna 116 and / or antenna 134).

[0054] For the purpose of facilitating the following discussion of the operation of electronic device 100 during NFC low-power fast operation mode in managing near-field communication (e.g., communication 55 with terminal 10), reference is made to a schematic diagram of the power management subsystem 301 of electronic device 100 (e.g., as shown in the diagram). Figure 3 Exemplary state diagrams of various power states of parts of electronic device 100 (e.g., as shown) Figure 4 Exemplary state diagrams of various configurations of parts of electronic device 100 (e.g., as shown) Figure 5 (as shown), and a front view of screens 200a and 200b that may represent the graphical user interface of electronic device 100 during such near-field communication management (e.g., as shown). Figure 2A and Figure 2B (As shown). The operation can be achieved using various graphic elements and visual schemes. Therefore, Figure 2A and Figure 2B The implementation schemes described herein are not intended to be limited to the exact user interface conventions adopted herein. Rather, these implementation schemes may include a variety of user interface styles.

[0055] Figure 3 A schematic diagram of a near-field communication management subsystem 301 for an electronic device 100, which may be provided to manage near-field communication during different operating modes of the electronic device 100, is shown. For example, the power management subsystem 301 may determine when to utilize the electronic device 100's NFC low-power fast mode and / or how to manage the NFC component 120 during such low-power fast modes (e.g., how to make the credentials of the NFC component 120 properly secure and / or properly accessible during such low-power fast modes).

[0056] Electronic device 100 can be configured to operate according to different power management modes used for controlling and managing the power consumption of various components of device 100. For example... Figure 3 As shown, for example, the power management subsystem 301 may include a mode detection module 310, which may be configured to determine when a particular power management mode of the electronic device 100 is entered. For example, the mode detection module 310 may be configured to determine when a particular power management mode of many possible modes is entered, such as the full or normal operation mode of the electronic device 100, the high battery trap or LPE operation mode, the low battery trap operation mode, or the power disconnect operation mode (e.g., as relative to...). Figure 1A (as shown in battery diagram 108a). Specifically, the mode detection module 310 can be configured to switch the operation of the electronic device 100 between various specific power management modes to reduce power consumption when the device 100 is not connected to a remote power source (e.g., when the power supply 108 is not plugged into a wall socket). For example, operation of the device 100 in a specific power management mode can prevent the device 100 from performing unnecessary power-intensive processes when the device 100 is powered by a battery with a remaining power potential less than a certain threshold.

[0057] like Figure 3 As shown, the mode detection module 310 can be configured to poll or otherwise receive power level data 307 from the power supply 108, wherein the power level data 307 can indicate the amount of power remaining in the power supply 108 (e.g., when the power supply 108 may be a battery whose power level can be reduced during use). When the mode detection module 310 detects that the remaining power of the power supply 108, as indicated by the received power level data 307, has dropped below a specific threshold (e.g., below one of threshold charge levels 163, 165, or 167, or any other suitable threshold), the mode detection module 310 can be configured to generate a switching command 311. This switching command can be configured to switch the electronic device 100 to a specific power management operating mode based on a specific new operating charge level range input from the power supply 108 (e.g., switching to full or normal operating mode when the charge level has entered range 162, switching to high battery trap or LPE operating mode when the charge level has entered range 164, switching to low battery trap operating mode when the charge level has entered range 166, or switching to power disconnect operating mode when the charge level has entered range 162). Figure 1A (As shown in battery diagram 108a). For example, as Figure 3 As shown, when the mode detection module 310 detects that the received power level data 307 indicates a specific characteristic of the power supply 108 (e.g., the power supply 108 has dropped below a specific power threshold), the mode detection module 310 can be configured to generate a switching command 311 and provide the switching command 311 to the switching application module 320 of the power management subsystem 301.

[0058] As another example of an initiation event of a specific operating mode (e.g., NFC low-power fast mode) detectable by the mode detection module 310, the mode detection module 310 may be configured to receive input mode selection data 309 from input components 110 (e.g., one or more input components 110a-110i). Such input mode selection data 309 may be any suitable data generated by the input component 110 that indicates a desired entry into a specific mode. For example, input mode selection data 309 may instruct a user to use... Figure 2The touchscreen input component 110f of the I / O component 114a selects the “NFC Low Power Mode” icon 183 of the GUI 180, and this can be recognized by the mode detection module 310 as an initiation event for entering the NFC Low Power Fast Mode. Therefore, when the mode detection module 310 receives such specific input mode selection data 309, the mode detection module 310 can be configured to generate a switching command 311 and provide the switching command 311 to the switching application module 320 of the power management subsystem 301. Therefore, as a supplement or alternative to switching the device 100 to the NFC Low Power Fast Mode when the power supply 108 is below a certain power threshold (e.g., within the LPEM operating charge level range 164 between the LPEM turn-on threshold charge level 163 and the LPEM turn-off threshold charge level 165), such an NFC Low Power Fast Power Management Mode can be entered by the user or under any other suitable circumstances.

[0059] Regardless of why the mode detection module 310 can generate a switching command 311 and transmit the switching command 311 to the switching application module 320 (e.g., in response to specific received power level data 307 and / or in response to specific received input mode selection data 309), the switching application module 320 can be configured to switch the electronic device 100 to a specific power management operating mode (e.g., switch to NFC low power fast mode) in response to receiving such a switching command 311. The switching process to a new power management operating mode may include the switching application module 320 generating one or more disable commands and transmitting them to one or more components of device 100 for at least partially turning off at least one function of such component, removing power from at least one function of such component, or otherwise at least partially disabling at least one function of such component (e.g., if switching to a lower power mode or if a particular component will otherwise be at least partially disabled for the new operating mode). This may reduce the power consumption of one or more components of device 100 and / or may at least partially disable one, some, or all of the components of device 100 that are not essential for at least the initial operation of device 100 in the new power management operating mode (e.g., one or more NFC communication component switching commands 321, which are used to turn off at least one function of NFC communication component 120, remove power from at least one function of NFC communication component 120, or otherwise at least partially disable NFC communication component 120). At least one function of 20; one or more output component switching commands 323, the one or more output component switching commands 323 being used to turn off at least one function of at least one input component 110, remove power from at least one function of at least one input component 110, or otherwise at least partially disable at least one function of at least one input component 110; one or more input component switching commands 325, the one or more input component switching commands 325 being used to turn off at least one function of at least one output component 112, remove power from at least one function of at least one output component 112, or otherwise at least partially disable at least one function of at least one output component 112; and / or one or more processor component switching commands 327, the one or more processor component switching commands 327 being used to turn off at least one function of at least one processor component 102, remove power from at least one function of at least one processor component 102, or otherwise at least partially disable at least one function of at least one processor component 102).Alternatively or otherwise, the switching process to a new power management operating mode may include the switching application module 320 generating one or more enable commands and transmitting them to one or more components of device 100 for at least partially enabling at least one function of such component, providing power to at least one function of such component, or otherwise at least partially enabling at least one function of such component (e.g., if switching to a higher power mode or if a particular component will otherwise be at least partially enabled for the new operating mode). This may increase the power consumption of one or more components of device 100 and / or may at least partially enable one, some, or all of the components of device 100 that may be necessary or at least used for at least the initial operation of device 100 in the new power management operating mode (e.g., one or more NFC communication component switching commands 321, which are used to enable at least one function of NFC communication component 120, provide power to at least one function of NFC communication component 120, or otherwise at least partially enable). At least one function of NFC communication component 120; one or more output component switching commands 323, the one or more output component switching commands 323 being used to enable at least one function of at least one input component 110, to provide power to at least one function of at least one input component 110, or otherwise at least partially enable at least one function of at least one input component 110; one or more input component switching commands 325, the one or more input component switching commands 325 being used to enable at least one function of at least one output component 112, to provide power to at least one function of at least one output component 112, or otherwise at least partially enable at least one function of at least one output component 112; and / or one or more processor component switching commands 327, the one or more processor component switching commands 327 being used to enable at least one function of at least one processor component 102, to provide power to at least one function of at least one processor component 102, or otherwise at least partially enable at least one function of at least one processor component 102).

[0060] For example, in response to receiving a switching command 311 for switching device 100 from normal operating mode to NFC Low Power Fast mode (e.g., in response to the charge level of power supply 108 entering LPEM operating charge level range 164 or in response to user input requesting a manual switch to such NFC Low Power Fast mode (e.g., to save power supply 108)), the switching application module 320 generates an NFC disable command 321 and transmits it to the NFC component 120 as part of the switching process to NFC Low Power Fast mode. This NFC disable command 321 can be configured to be received by any suitable element of the NFC component 120 such that at least one credential previously enabled by the NFC component 120 prior to receiving the command 321 can be disabled in response to receiving the command 321. As a specific example, when NFC component 120 receives command 321, command 321 can disable the NFC antenna 134 and / or amplifier 136 of NFC device module 130, such that after such disabling (e.g., if the user has not yet selected any credentials provided on device 100 for use during such mode), NFC component 120 cannot transmit any NFC communication 55 to terminal 10. Similarly, when NFC component 120 receives command 321, command 321 can disable the first applet 153 of the first SSD 154 of NFC memory module 150, such that after such disabling, NFC component 120 cannot transmit any NFC communication 55 associated with credentials of the first applet 153 to terminal 10. In some implementations, when NFC component 120 receives command 321, command 321 may disable each applet 153 of each SSD 154 of NFC memory module 150, such that after such disabling, NFC component 120 cannot transmit any NFC communication 55 associated with any credentials of any applet 153 of any SSD 154 to terminal 10. However, in other embodiments, when NFC component 120 receives command 321, command 321 may disable only certain applets 153 of some SSDs 154 of NFC memory module 150, such that after such disabling, NFC component 120 cannot transmit any NFC communication 55 associated with credentials of those specific applets (e.g., credit card credentials, which guarantee a high level of security) to terminal 10, but allows NFC component 120 to transmit other NFC communication 55 associated with credentials of other specific applets (e.g., simple access system credentials, such as those for subways that may not guarantee a high level of security) to terminal 10 (e.g., based on default credential settings and / or based on specific user-selected settings for specific single or specific groups or types of credentials provided on device 100).When received by NFC component 120, NFC disable command 321 can be configured to turn off at least one function of NFC component 120, remove power from at least one function of NFC component 120, or otherwise at least partially disable at least one function of NFC component 120. In some embodiments, NFC component 120 may not have NFC disable command 321, and NFC component 120 may operate in the same way as when it is in full power mode (e.g., NFC component 120 may be powered by power supply 108 regardless of whether device 100 is in normal operating mode or NFCLPEM mode). In some implementations, the power management subsystem 301 may be configured to switch the electronic device 100 from a normal operating mode to an NFC low-power fast mode by providing an NFC disable command 321 and / or by providing an NFC direct power command 321d. The NFC disable command 321 prevents the NFC command 120 from receiving any power from the power source 108 via the power management subsystem 301. The NFC direct power command 321d may be used to close a switch 321s to allow any suitable power 321p to be supplied directly from the power source 108 to the NFC component 120 to power the NFC component 120 during NFC LPEM operating mode. In such implementations, the power management subsystem 301 may also be configured to switch the electronic device 100 from the NFC low-power fast mode to an NFC off mode (e.g., when switching to a low battery trap operating mode or switching to a power disconnect operating mode) by providing another NFC direct power command 321d. This other NFC direct power command 321d may be used to open a switch 321s to prevent any power 321p from being supplied directly from the power source 108 to the NFC component 120.

[0061] In addition to generating or as an alternative to NFC disable command 321, the switching application module 320 may be configured to switch electronic device 100 from normal operating mode to NFC low-power fast mode (e.g., in response to the charge level of power supply 108 entering LPEM operating charge level range 164 or in response to user input requesting manual switching to such NFC low-power fast mode (e.g., to save power supply 108)) by generating output component disable command 323 and transmitting it to at least one output component 112 (e.g., at least one of output components 112a-112c). When received by the output component 112, such output component disable command 323 may be configured to turn off at least one function of the output component 112, remove power from at least one function of the output component 112, or otherwise at least partially disable at least one function of the output component 112. For example, in response to display output component 112a receiving such disable command 323, display output component 112a may be turned off (e.g., power may no longer be supplied to display output component 112a). In some implementations, the power management subsystem 301 may be configured to prevent one or more such output components from receiving any power from the power source 108 via the power management subsystem 301 by providing an output component disable command 323 to at least one or all output components 112 and / or to switch the electronic device 100 from a normal operating mode to an NFC low-power fast mode by providing an output direct power command 323d, which can be used to close a switch 323s to enable any suitable power 323p to be provided directly from the power source 108 to a particular output component 112 (e.g., a haptic output component 112c) to power that particular output component 112 during NFC LPEM operating mode. In such implementations, the power management subsystem 301 may also be configured to switch the electronic device 100 from NFC low-power fast mode to NFC off mode (e.g., when switching to low battery trap operation mode or switching to power disconnect operation mode) by providing another output direct power command 323d. This other output direct power command 323d can be used to disconnect the switch 323s to prevent any power 323p from the power supply 108 from being directly supplied to the particular output component 112 (e.g., haptic output component 112c) that has been directly powered previously.

[0062] Similarly, the switching application module 320 can be configured to switch the electronic device 100 from a normal operating mode to an NFC low-power fast mode (e.g., in response to the charge level of power supply 108 entering the LPEM operating charge level range 164 or in response to a user input requesting a switch to such an NFC low-power fast mode (e.g., to save power supply 108)) by generating an input component disable command 325 and transmitting it to at least one input component 110 (e.g., one or more of input components 110a-110i). When received by the input component 110, the input component disable command 325 can be configured to turn off at least one function of the input component 110, remove power from at least one function of the input component 110, or otherwise at least partially disable at least one function of the input component 110. In some implementations, the power management subsystem 301 may be configured to prevent one or more such input devices from receiving any power from the power source 108 via the power management subsystem 301 by providing an input device disable command 325 to at least one or all input devices 110 and / or to switch the electronic device 100 from a normal operating mode to an NFC low-power fast mode by providing an input direct power command 325d, which may be used to close a switch 325s to enable any suitable power 325p to be provided directly from the power source 108 to a particular input device 110 (e.g., a side button input device 110b) to power that particular input device 110 during NFC LPEM operating mode. In such implementations, the power management subsystem 301 may also be configured to switch the electronic device 100 from NFC low-power fast mode to NFC off mode (e.g., when switching to low battery trap operation mode or switching to power disconnect operation mode) by providing another input direct power command 325d, which can be used to disconnect the switch 325s to prevent any power 325p from the power supply 108 from being directly supplied to the particular input component 110 (e.g., side button input component 110b) that has been directly powered previously.

[0063] Similarly, the application switching module 320 can be configured to switch device 100 from normal operating mode to NFC Low Power Fast mode or NFC LPE power management mode by generating an application disable command 327 and transmitting it to processor 102 (e.g., in response to the charge level of power supply 108 entering the LPEM operating charge level range 164 or in response to user input requesting a switch to such NFC Low Power Fast mode (e.g., to conserve power supply 108)). When received by processor 102, the application disable command 327 can be configured to shut down or otherwise at least partially disable one or more applications currently running on processor 102 (e.g., to force quit all non-native applications and / or any non-essential applications and / or all applications running on device 100 prior to the generation of the application disable command 327). This can reduce the power consumption of processor 102 while switching to NFC Low Power Fast mode.

[0064] In addition, or alternatively, the switching application module 320 may be configured to switch the device 100 from a normal operating mode to an NFC low-power fast mode (e.g., in response to the charge level of power supply 108 entering the LPEM operating charge level range 164 or in response to a user input requesting a switch to such an NFC low-power fast mode (e.g., to save power on power supply 108) by generating one or more additional disable commands (not shown) and transmitting them to at least one other component of the device 100 (e.g., memory 104, communication component 106, antenna 116, etc.), such that when received by the device component, the component disable command may be configured to turn off at least one function of the device component, remove power from at least one function of the device component, or otherwise at least partially disable at least one function of the device component.

[0065] Therefore, the switching application module 320 can be configured to initiate a transition of the electronic device 100 to a new power management mode by generating and transmitting one or more disable commands and / or one or more enable commands (e.g., commands 321, 323, 325, 327, etc.). These one or more disable commands and / or one or more enable commands can be configured to turn off, remove power, or otherwise at least partially disable one, some, or all components of the device 100 that are not essential for the initial operation of the device 100 in the new power management mode, and / or can be configured to turn on, provide power, or otherwise at least partially enable one, some, or all components of the device 100 that can be used for the initial operation of the device 100 in the new power management mode. For example, as described above, one or more disable commands of the switching application module 320 can be configured to at least partially turn off one or more input components 110, one or more output components 112, the processor 102 or at least one or more applications running by the processor 102, at least some of the components in the memory 104, at least some or all of the communication components 106, the antenna 116, and / or some or all of the NFC components 120. When operating at least initially in such NFC low-power fast modes, electronic device 100 may be configured to avoid supplying power to or otherwise enable certain device components of the security management NFC component 120 that are not essential to it. For example, in response to receiving one or more disable commands from the switching application module 320, electronic device 100 may shut down a hard drive (e.g., memory 104), dim or turn off a display (e.g., output component 112a), put a processor (e.g., processor 102) into a low-power “sleep” or “hibernate” or “off” mode, and / or completely or partially disable the NFC component 120. Some or all of the power management settings of the power management subsystem 301 may be set automatically or by the user of device 100 (e.g., the user may define the duration and / or conditions before switching between devices that can be at least partially disabled or turned off when switching between different power management modes, such as NFC low-power fast modes). By forcing the electronic device 100 to operate in such a low-power fast NFC mode, the switching application module 320 can ultimately allow the electronic device 100 to communicate securely using the NFC component 120 in an effective manner (e.g., until the power supply 108 is no longer able to power the electronic device 100 to operate in that mode (e.g., until the level of the power supply 108 drops below the threshold charge level 165)).

[0066] Therefore, at least some modules of the power management subsystem 301 may be configured to be coupled to a power management unit (“PMU”) of at least one power source, such as power supply 108. Such a PMU may include a microcontroller and may be configured to manage the power functions of device 100. Such a PMU may include its own memory (e.g., loaded with software and / or firmware), a processor with input / output functions and timers, and one or more converters for measuring the power supplied by power supply 108. Furthermore, or alternatively, such a PMU may include a backup power source that powers components of the power management subsystem 301 even when device 100 is completely powered off, such that the current time of, for example, a real-time clock (“RTC”) can be maintained. For example, RTC 351 may be provided by subsystem 301 (e.g., by power mode control application module 330 or otherwise), wherein RTC 351 may be provided as an integrated circuit (e.g., an integrated circuit with one or more general purpose inputs / outputs (“GPIOs”)) and / or may include one or more registers 353 (e.g., one or more RTC counter registers and / or one or more PMU temporary registers). Such a PMU may be responsible for coordinating certain functions of device 100, including but not limited to monitoring power connection and battery charging, controlling the power supplied to other components of device 100, shutting down certain components of device 100 when they are idle or deemed appropriate for current operation of device 100 and unnecessary, adjusting the real-time clock of device 100, and controlling various power management modes of device 100. Battery control circuitry or a power management stage may be connected to the battery and baseband / firmware processor. One or more dedicated connections from such a PMU and / or from power supply 108 to various elements of NFC component 120 (e.g., device module 130, controller module 140, and / or memory module 150) may also be provided by power management subsystem 301. These additional connections may be provided so that the battery control circuitry or power supply circuitry can selectively power various components of device 100, and especially those necessary for performing NFC communication with terminal 10.

[0067] When the switching application module 320 has received the switching command 311 from the mode detection module 310 and has subsequently generated and transmitted one or more commands (e.g., commands 321, 323, 325, etc.) for at least partially adjusting one, some, or all of the components of the device 100 for at least initial operation of the device 100 in the new power management mode, the switching application module 320 may also be configured to generate a start command 329 and transmit it to the power mode control application module 330 of the power management subsystem 301. In response to receiving the start command 329, the control application module 330 may be configured to start and run at least one application (e.g., application 143), which may be specifically customized to appropriately manage and / or otherwise control the electronic device 100 in the new power management mode. Thus, for example, the operation of the device 100 in NFC LPE mode may be based on one or more applications accessible to the electronic device 100 (e.g., application 143) and / or on any input instructions received by the electronic device 100 (e.g., via input component 110) that control such applications.

[0068] For example, when the control application module 330 receives a start command 329 for managing the device 100 in NFC LPE power management mode, the NFC component 120 may be initially configured to be in active antenna mode by NFC command 321 and / or NFC direct power command 321d (e.g., where antenna 116 and / or antenna 134 may be actively enabled by the electronic device 100 itself (e.g., by power supply 108) for NFC communication). It should be understood that when NFC component 120 is initially configured to be in passive or active antenna mode by NFC command 321 and / or NFC direct power command 321d, one or more other components of NFC component 120 (e.g., one or more applets 153 of SSD 154) can initially be disabled by NFC disable command 321 and / or NFC direct power command 321d to prevent the passive / active antenna from transmitting the credentials of NFC component 120 as communication 55 to terminal 10 (e.g., certain applets associated with certain credentials may set or not set specific registers or tags (e.g., due to user preference) that prevent those credentials from being used for transactions with terminal 10 during NFC LPE power management mode, while other specific applets associated with other specific credentials may set or not set specific registers or tags (e.g., due to user preference) that allow those credentials to be used in transactions with terminal 10 during NFC LPE power management mode). For example, one or more tags or registers in NFC component 120 (e.g., tags or registers in a specific SSD or applet associated with a specific credential) (e.g., when device 100 is operating in full or normal operating mode) can be configured to enable or disable the use of one or more specific credentials in NFC LPE power management mode. Alternatively, the LPM flag (“LPMF”) can be set in a specific manner, for example, in a PMU temporary register (e.g., register 353 (e.g., in non-volatile memory)) based on whether (e.g., by a user) any credentials are enabled for use upon entering NFC LPE mode (e.g., set to '1' or '0'). Figure 5 As shown, an exemplary state machine 500 may be provided to illustrate various configurations of portions of the electronic device 100 for determining whether the device 100 is available in NFC LPE mode. When the NFC component 120 is in... Figure 4When the NFC full-power mode of state diagram 400 is in state 401 of NFC full-power mode, each state of state machine 500 may be possible. For example, at state 501 of state machine 500, electronic device 100 may be in a state where the device 100 (e.g., in NFC component 120) has not provided credentials for potential use in communication 55 with terminal 10 during future NFC low-power fast operation modes of device 100, which have been selected (e.g., by the user or otherwise). In response to any suitable event 502 in which a first credential can be selected for potential use in a future NFC Low Power Fast Mode (e.g., when a user selects or provides a credential on device 100 as a "Fast Mode Card" or "Fast Mode Credential" (e.g., when device 100 is operating in full or normal operating mode)), device 100 may be configured to transition from state 501 to state 521, in which at least one credential is provided on device 100 (e.g., in NFC component 120) that has been (e.g., selected by the user or otherwise) for potential use in communication 55 with terminal 10 during a future NFC Low Power Fast Mode of device 100. During such a transition between state 501 and state 521, device 100 may be configured to take one or more actions 506 (e.g., automatically) so that device 100 performs appropriately according to the new state 521. For example, as shown, one or more actions 506 may include any suitable action or combination of actions, including but not limited to one or more of the following:

[0069] (1) Set NFC_VEN_int = 1;

[0070] (2) Set NFC_GPIO2_AO = OPT_RESET_L = HIGH;

[0071] (3) Set LPMF = 1;

[0072] (4) Load the output waveform onto the driver amplifier;

[0073] (5) Set PMU_ALARM_EN = 1;

[0074] (6) Configure duration X for PMU_RTC_ALARM; and / or

[0075] (7) Configure the duration X-1 for SW_Alarm (e.g., any suitable duration less than the duration X).

[0076] Similarly, in response to any suitable event 522 in which a previous credential can be deselected for potential use in future NFC Low Power Fast Mode (e.g., when a user adjusts the unique credential on device 100 previously identified as a Fast Mode card to a credential not identified as a Fast Mode card or completely removes such a card (e.g., when device 100 is operating in full or normal operating mode)), device 100 can be configured to transition from state 521 to state 501 in which a credential that has been (e.g., by the user or otherwise) selected for potential use in communication 55 with terminal 10 during future NFC Low Power Fast Mode operations is not provided on device 100 (e.g., in NFC component 120). During such a transition between state 521 and state 501, device 100 can be configured to take one or more actions 526 (e.g., automatically) so that device 100 performs appropriately according to the new state 501. For example, as shown, one or more actions 526 may include any suitable action or combination of actions, including but not limited to one or more of the following:

[0077] (1) Set NFC_VEN_int = 0;

[0078] (2) Set LPMF = 0; and / or

[0079] (3) Set PMU_ALARM_EN = 0.

[0080] In addition to or alternatively, in response to any suitable event 532 that SW_Alarm may pass (e.g., be triggered) while device 100 is in state 521, device 100 may be configured to take one or more actions 536 (e.g., automatically) so that device 100 responds correctly to event 532. For example, as shown, one or more actions 536 may include any suitable action or combination of actions, including but not limited to one or more of the following:

[0081] (1) Set PMU_ALARM_EN = 1;

[0082] (2) Configure another duration X for PMU_RTC_ALARM; and / or

[0083] (3) Configure the duration X-1 for SW_Alarm.

[0084] Each of actions 506, 526, and 536 can be relative to Figure 4 The operation of the NFC component 120 in the low-power fast mode of the electronic device 100 is described in more detail. It should be understood that... Figure 5The various operations and conditions shown in state diagram 500 are merely illustrative. 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 changed.

[0085] The control application module 330 can be configured to receive any suitable input device command 331 from any suitable input device 110 (e.g., side button input device 110b), which may be at least partially or at least temporarily enabled during the current power management mode (e.g., during low power fast mode via power 325p). Alternatively, the control application module 330 can be configured to provide any suitable output device command 333 to any suitable output device 112, which may be at least partially or at least temporarily enabled during the current power management mode (e.g., haptic output device 112c powered by power 323p during low power fast mode) or to wake up any suitable output device 112 that is normally disabled during the current power management mode (e.g., display output device 112a during battery trap operation mode (e.g., low power fast mode)). Alternatively or in addition, the control application module 330 may be configured to provide any suitable NFC component input command 339 to any suitable portion of the NFC component 120, which may be at least partially or at least temporarily enabled during the current power management mode (e.g., during a low-power fast mode via power 321p). Alternatively or in addition, the control application module 330 may be configured to receive any suitable NFC component output command 341 from any suitable portion of the NFC component 120, which may be at least partially or at least temporarily enabled during the current power management mode (e.g., during a low-power fast mode via power 321p). The control application module 330 can be configured to generate any one or more of commands 333 and / or 339 (and / or one or more of commands 321d, 323d and / or 325d) during the current power management mode, and / or receive any one or more of commands 331 and / or 341 during the current power management mode, for example, according to any suitable power management mode application or rule set or state machine that can be specifically customized to properly manage and / or otherwise control the electronic device 100 in the current power management mode (e.g., Figure 4 (State machine 400).

[0086] For example, such as Figure 4As shown, an exemplary state machine 400 may be provided to illustrate at least one specific manner in which the power management subsystem 301 is operable to manage near-field communication during the low-power fast mode of the electronic device 100. As shown, in NFC full-power mode (“NFC FPM”) state 401, the NFC component 120 can be powered on and is functioning normally. For example, at state 401, the electronic device 100 can operate in full or normal operating mode (e.g., when the charge level of the power supply 108 is within the full operating charge level range 162 between threshold charge levels 161 and 163), wherein the NFC component 120 and any other suitable component of the device 100 (e.g., display output component 112, touchscreen input component 110, application processor 102 running any suitable operating system application and / or any suitable specific UI application, cellular communication component 106, etc.) can be powered by the power supply 108 (e.g., via the power management system 301 (e.g., via the PMU)) and are functioning normally. For example, as shown, when operating in NFC full-power mode in NFC FPM state 401, NFC component 120 can be configured at operation 401n to perform any suitable transaction or communication 55 between electronic device 100 and terminal 10 using any credentials of device 100 (e.g., regardless of whether the credentials are currently designated as a fast mode card). However, in response to the detection of any suitable first condition 402, the state of electronic device 100 can transition from state 401 to NFC power off mode (“NFC off”) state 471, in which NFC component 120 can be powered off (e.g., for power saving), or in response to the detection of any suitable second condition 412, the state of electronic device 100 can transition from state 401 to NFC low-power mode (“NFC LPM”) state 451, in which NFC component 120 can remain powered but is limited to transactions only for credentials designated as fast mode cards (e.g., for power saving). For example, as shown in the figure, when operating in NFC low-power mode in NFC LPM state 451, NFC component 120 can be configured at operation 451n to actively perform any suitable transaction or communication 55 between electronic device 100 and terminal 10 using any credentials of device 100 currently designated as a fast mode card. However, when operating in NFC off-power mode in NFC off state 471, NFC component 120 may not be configured to actively perform any suitable transaction or communication 55 between electronic device 100 and terminal 10 (e.g., because NFC component 120 has no power in this state (but note that some passive transactions may be possible in NFC off state 471 if certain security measures are in place)).

[0087] For example, in state 471 where the NFC component 120 can be powered off, the electronic device 100 can operate in any suitable operating mode, such as in a completely powered-off mode (e.g., when the device 100 automatically shuts down due to the charge level of the power supply 108 falling below the threshold charge level 167 within the disconnection operation charge range 168, or when the device 100 has any other suitable charge level but has been manually powered off by the user (e.g., possible condition 402)) or in a battery trap operating mode (e.g., when the charge level of the power supply 108 has dropped below the threshold charge level 163 and entered one of ranges 164 or 166 (e.g., possible condition 402)). In state 471, the system PMU of the device 100 can be powered off or inactive, can not supply power to the NFC component 120 (e.g., via the power management system 301 or directly via switches 321s), and can only enable limited functions (if any) for other parts of the electronic device, such as functions to enable the user to determine whether the device 100 is operating in battery trap mode. For example, if device 100 is operating in battery trap mode while in state 471, limited functionality can be enabled by device 100 to enable the sensing of specific user interactions with specific input components (e.g., a user pressing a side button input component 110b (e.g., detecting any suitable wake-up event condition 472), where the side button input component 110b can be at least partially or at least temporarily enabled during the current power management mode (e.g., by power 325p during battery trap mode)), and then temporarily powering the display output component 112a in response to sensing such specific user input component interactions (e.g., by activating the system PMU, and then activating at least another part or the remainder of the system (e.g., activating the loader and possible operating system applications)) for displaying a very specific UI screen (e.g., Figure 2BThe “battery dead UI” screen 190b (e.g., at operation 482) allows the user to determine that the device 100 is operating in battery trap mode (e.g., to let the user know that the device 100 is not in a power disconnect operation mode (e.g., range 168)). For example, when device 100 operates in battery trap mode at state 471 (e.g., when the charge level 307 of power supply 108 is within one of ranges 164 and 166) and the NFC component is in NFC power-off mode, in response to detecting a button press condition 472 on input component 110b that can be directly powered by power 325p, input component 110b can be configured to generate any suitable input component command 331 and transmit it to control application module 330, which can be used to wake up the system PMU, such that control application module 330 can be configured to provide any suitable output component command 333 to display output component 112a, which can normally be disabled during battery trap operation mode, wherein the command 333 can be used to at least temporarily power display output component 112a to present to the user at event 482. Figure 2B The “Dead Battery UI” screen 190b can indicate the current battery trap mode of device 100 (e.g., via the depleted battery icon 201), but may not indicate that any fast mode card is enabled in the current battery trap mode (e.g., because NFC component 120 is in NFC power-off mode state 471) (e.g., with Figure 2ACompared to the "Quick Mode Capability UI" screen 190a, which can be presented to the user at event 455, this screen 190a can indicate the current battery trap mode of device 100 (e.g., via the depleted battery icon 201), but can also indicate that at least one Quick Mode card is enabled in the current battery trap mode (e.g., because NFC component 120 is in NFC low power mode in state 451) (e.g., via text 203). As indicated by the distinguishing line ("DL"), all operations above the line DL in state diagram 400 can be performed when the system PMU of device 100 is powered on and / or woken up and / or active (e.g., when the operating system application or launcher application or otherwise can be used by device 100), while all operations below the line DL in state diagram 400 can be performed when the system PMU of device 100 is off or powered off or inactive. For example, when the PMU is in the off state, it may not be completely shut down, as it may still support processing button presses or one or more other functions (e.g., the PMU may include at least one always-on domain that remains active even when the PMU is off). Alternatively, the PMU may be completely shut down in the off state. NFC transactions and / or haptic feedback and / or other specific output feedback may be able to occur completely independently of the system PMU (e.g., the PMU may remain off, while the NFC component and / or output component may operate in a low-power mode (e.g., the NFC component and / or output component may be powered by its own power supply without relying on any track from the PMU, and / or may receive the same or different amounts of power when operating in low-power or full-power mode)). It should be understood that any suitable wake-up event or condition 452 and / or 472 may be configured to be any suitable user interaction appropriately enabled by device 100 (e.g., a raise-to-wake gesture, a tap on a touch-sensitive display, voice triggering, button press, etc.).

[0088] One or more suitable conditions 402 may be met to transition from state 401 to state 471. These conditions include, but are not limited to, conditions where the user manually turns off (e.g., powers off) device 100 (e.g., by pressing and holding side button 110b for at least a specific duration (e.g., 3 seconds)), or conditions where not only is the current charge of power supply 108 below a threshold charge level 163 (e.g., as can be detected by module 310 using power level data 307), but no credentials on device 100 are currently designated as a fast mode card (e.g., as can be determined when LPMF equals '0' (e.g., as can be implemented by action 526 of state diagram 500)). In some specific embodiments, NFC component 120 may be configured to transition from NFC FPM state 401 to NFC off state 471 when a specific NFC state transition sequence protocol is executed at operation 403. For example, as shown in the NFC state transition sequence protocol of NFC state transition operation 403, NFC component 120 can be configured to transition from NFC FPM state 401 to NFC off state 471 (e.g., after a certain sequence of specific operations (e.g., when the GPIO output from the system PMU to NFC component 120 (e.g., “NFC_EN”) is set to “low” for at least a certain amount of time (e.g., a buffer or margin time (e.g., 3 milliseconds)) before disabling the power rail of NFC component 120 (e.g., the 1.8 volt power rail “PP1V8_NFC”), although any other suitable operation may cause NFC component 120 to transition between state 401 and state 471)).

[0089] Alternatively, one or more suitable other conditions 412 may be satisfied to transition from state 401 to state 451, including but not limited to the condition that at least one credential on device 100 is currently designated as a fast mode card (e.g., as may be determined when LPMF equals T) when the user manually instructs device 100 to enter NFC low-power fast mode (e.g., in response to the power management system receiving specific input mode selection data 309 from input component 110) (e.g., to conserve device power while maintaining the functionality of at least one credential of NFC component 120 designated as a fast mode card). Conditions such as those that can be implemented by action 506 of state diagram 500, or conditions in which at least one credential on device 100 is currently designated as a fast mode card when the current charge of power supply 108 is detected to drop below threshold charge level 163 (e.g., as can be detected by module 310 using power level data 307), or conditions in which at least one credential on device 100 is currently designated as a fast mode card when an undervoltage lockout (“UVLO”) event is detected (e.g., when the voltage of the battery of power supply 108 is detected to drop below any suitable UVLO threshold of the system PMU of device 100). In some specific embodiments, NFC component 120 may be configured to transition from NFC FPM state 401 to NFC LPM state 451 when a specific NFC state transition sequence protocol is executed at operation 413. For example, as shown in the NFC state transition sequence protocol of NFC state transition operation 413, NFC component 120 can be configured to transition from NFC FPM state 401 to NFC LPM state 451 (e.g., after a specific sequence of operations (e.g., when the GPIO output from the system PMU to NFC component 120 (e.g., “NFC_EN”) is set “low” for at least a certain amount of time (e.g., a buffer or margin time (e.g., 3 milliseconds)) while the power rail of NFC component 120 (e.g., the 1.8-volt power rail “PP1V8_NFC”) is disabled, although any other suitable operation could cause NFC component 120 to transition between state 401 and state 451)). For example, such an NFC state transition sequence protocol can be implemented in hardware by the PMU power-down sequencer of device 100.

[0090] In NFC LPM state 451, where the NFC component 120 can be powered (e.g., directly powered by power 321p via switch 321s) and the system PMU can be inactive, the electronic device 100 can be configured to operate in NFC Low Power Fast mode (e.g., where, to save power, the processor 102 and each communication component 106, as well as each output component 112 and each input component 110, are turned off to allow the user to detect that the device 100 is operating in NFC Low Power Fast mode, except for perhaps specific output components 112 (e.g., haptic output component 112c) and / or specific input components 110 (e.g., side button input component 110b). Therefore, in state 451, the system PMU of the device 100 can be powered off or inactive, power can be supplied to the NFC component 120 (e.g., directly via switch 321s), and limited functionality can only be enabled for other parts of the electronic device. (If applicable), such as functions to enable a user to determine whether device 100 is operating in NFC Low Power Fast mode. For example, if device 100 is operating in NFC Low Power Fast mode in state 451, device 100 may enable limited functionality to enable the sensing of any suitable wake-up event or specific user interaction with a specific input device (e.g., the user presses the side button input device 110b (e.g., any suitable wake-up event condition 452 is detected), wherein the side button input device 110b may be at least partially or at least temporarily enabled during the current power management mode (e.g., by power 325p during NFC Low Power Fast mode in battery trap mode)), and then, in response to sensing such specific user input device interaction and in response to determining at operation 453 that a specific power condition 454 is met, the display output device 112a is temporarily powered to display a very specific UI screen (e.g., ...). Figure 2AThe “Fast Mode Capability UI” screen 190a (e.g., at operation 455) enables the user to determine that the device 100 is operating in NFC Low Power Fast Mode (e.g., to let the user know that Fast Mode NFC transactions are possible). For example, when device 100 operates in NFC Low Power Fast mode and the NFC component is in NFC LPM power mode at state 451, in response to detecting any suitable wake-up event 452 (e.g., button press condition 452 of input component 110b, which can be directly powered by power 325p), input component 110b can be configured to generate any suitable input component command 331 and transmit it to control application module 330, which can be used to wake up the system PMU, such that control application module 330 can be configured to determine at operation 453 that a specific power condition 454 has been met, and then provide any suitable output component command 333 to display output component 112a, which is normally disabled during NFC Low Power Fast mode in battery trap operation mode, wherein the command 333 can be used to at least temporarily power display output component 112a to present to the user at event 455. Figure 2A The “Fast Mode Capability UI” screen 190a indicates the current battery trap mode of device 100 and can indicate the fact that at least one Fast Mode card is enabled in the current NFC Low Power Fast Mode of the current battery trap mode (e.g., because NFC component 120 is in NFC LPM power mode state 451) (e.g., with Figure 2B Compared to the “battery dead UI” screen 190b, screen 190b can be presented to the user at event 482, which may only indicate the current battery trap mode of device 100, but may not indicate that at least one fast mode card is enabled in the current battery trap mode (e.g., because NFC component 120 is in NFC power off mode in state 471).

[0091] The determination at operation 453 can be any suitable determination of any appropriate power state. For example, in some embodiments, operation 453 can be used to determine the condition of the “LOW_V” flag, which can be configured to indicate the relationship between the current charge of power supply 108 and a specific threshold charge level. As a particular example, operation 453 can typically be used to determine whether the current charge level of power supply 108 is higher or lower than the LPEM shutdown threshold charge level 165, which can be used to determine whether to keep NFC component 120 in NFC LPM power mode at state 451 or to transition NFC component 120 from NFC LPM power mode at state 451 to NFC shutdown power mode at state 471 (e.g., to save power by powering off NFC component 120 and terminating NFC low-power fast mode while still remaining in battery trap mode (e.g., low battery trap operation mode)). In a specific example, if each of any suitable number of consecutive samples (e.g., 10 consecutive samples) of the current charge level of power supply 108 (e.g., using data 307) is determined to be less than the LPEM shutdown threshold charge level 165, then device 100 (e.g., device firmware) may be configured to set the LOW_V flag (e.g., a flag in a system PMU register) to equal '1', and when the current charge level of power supply 108 is determined to be at least greater than the LPEM shutdown threshold charge level 165 by some amount (e.g., at least 0.05 volts greater than the LPEM shutdown threshold charge level 165), it may be configured to clear or reset the LOW_V flag to equal '0'. Therefore, device 100 may be configured at operation 453 to confidently determine that the current charge level of power supply 108 is greater than the LPEM shutdown threshold charge level 165 by satisfying condition 454 (e.g., LOW_V = 0), or less than the LPEM shutdown threshold charge level 165 by satisfying condition 457 (e.g., LOW_V = 1). Therefore, in response to device 100 detecting button press condition 452, and then determining at operation 453 that the current charge level of power supply 108 is greater than the LPEM shutdown threshold charge level 165 by satisfying condition 454, device 100 can be configured to present at operation 455. Figure 2A The “Quick Mode Capability UI” screen 190a is then returned to state 451 (e.g., keeping NFC component 120 in NFC LPM mode in state 451) (e.g., via operation 456 which can set PMU RTC alarms), because power supply 108 can operate in the LPEM operating charge level range 164.

[0092] Alternatively, in response to device 100 detecting button press condition 452, and then determining at operation 453 that the current charge level of power supply 108 is less than LPEM shutdown threshold charge level 165 by satisfying condition 457, device 100 may be configured to transition NFC component 120 from NFC LPM mode in state 451 to NFC shutdown mode in state 471 (e.g., via operations 458 and 474 or via operations 459 and 462 in state 461), since power supply 108 may no longer be operating within LPEM operating charge level range 164. Conversely, in order to operate in a low-battery-trap operating mode for conserving further power by disabling NFC component 120, device 100 may be used to transition NFC component 120 from NFC low-power mode in NFC LPM state 451 to NFC shutdown power mode in NFC shutdown state 471. Device 100 may be used to perform such a transition by first executing operation 458. At operation 458, device 100 can be configured to set LPMF to '0', which prevents any credentials on device 100 from being used as a quick mode card until once NFC component 120 has transitioned from NFC off-power mode of NFC off state 471 back to NFC full-power mode of NFC FPM state 401 (e.g., via operations 492, 494, and 497). LPMF can then be reset back to '1' (e.g., at operation 499, where the user of device 100 can be re-authenticated (e.g., by entering a PIN to access functions of the device operating system (e.g., access...)). Figure 2The screen 190 provides a security layer to prevent unauthorized users from using a fast card after device 100 has reached NFC Off state 471 if / when the device is to return to NFC LPM state 451. Alternatively, at operation 458, device 100 may be configured to disable alarms (e.g., PMU_RTC_ALARM (e.g., by setting PMU_ALARM_EN to '0')) such that alarms may not time out for initiating routines in NFC Off state 471. After operation 458, device 100 may be configured to directly transition NFC component 120 from NFC LPM mode of state 451 to NFC Off mode of state 471 when a specific NFC state transition sequence protocol is executed at operation 474. Alternatively, NFC component 120 may be configured to indirectly transition from NFC LPM mode of state 451 to NFC Off mode of state 471 via a fast intermediate transition from NFC LPM mode of state 451 to NFC FPM mode of state 461. For example, NFC component 120 may be configured to transition from NFC LPM state 451 to NFC FPM state 461 when a specific NFC state transition sequence protocol is executed at operation 459 (e.g., after a certain sequence of specific operations (e.g., when the power rail of NFC component 120 (e.g., the 1.8 volt power rail "PP1V8_NFC") is enabled for at least a certain amount of time (e.g., a buffer or margin time (e.g., 3 milliseconds)) before the GPIO output from the system PMU to NFC component 120 (e.g., "NFC_EN") is set to "high), although any other suitable operation may cause NFC component 120 to transition between state 451 and state 461)), and then NFC component 120 may be configured to transition from NFC LPM state 451 to NFC FPM state 461 when a specific NFC state transition sequence protocol is executed at operation 462). FPM state 461 transitions to NFC off state 471 (e.g., after a specific sequence of operations (e.g., when the GPIO output from the system PMU to NFC component 120 (e.g., "NFC_EN") is set "low" for at least a certain amount of time (e.g., a buffer or margin time (e.g., 3 milliseconds)) before disabling the power rail of NFC component 120 (e.g., the 1.8-volt power rail "PP1V8_NFC"), although any other suitable operation could cause NFC component 120 to transition between states 461 and 471)). Then, once NFC component 120 has transitioned to the NFC off power mode of NFC off state 471, NFC component 120 may remain in the NFC off power mode of NFC off state 471 until power supply 108 has been charged above a certain threshold charge level (e.g., threshold charge level 163) to achieve a transition back to the NFC full power mode of NFC FPM state 401.For example, as shown, when in state 471, device 100 can be used to perform device charging operation 492 (e.g., in response to any suitable charging event (e.g., a user plugging device 100 into a power outlet to receive external power generated by a power station)). During this time, any suitable “charging and display UI” screen can be presented to the user at event 494 (e.g., to enable the user to determine that the device is being charged correctly). However, before operation 492 causes the charge level of power supply 108 to exceed a specific threshold charge level (e.g., threshold charge level 163) to satisfy condition 496 for transitioning back to NFC full-power mode in NFC FPM state 401 at operation 497, device 100 can satisfy condition 495 and remain in NFC FPM state 471. Therefore, device 100 may enable charging of power supply 108 to return from off state 471 to FPM state 401, but may not enable charging of power supply 108 to return only from off state 471 to LPM state 451. Furthermore, it should be understood that if the device transitions from an on state 401 to an off state 471 in response to a user manually turning off (e.g., powering off) the device 100, operation 492 may include the user attempting to manually turn the device 100 back on, in which case condition 496 may be satisfied and the device 100 may transition from state 471 back to state 401 without any actual charging of the power supply 108.

[0093] Referring further to state 451, if device 100 is operating in NFC Low Power Fast mode while in state 451, and instead of (e.g., previously) detecting any button press condition 452 for initiating a user-initiated device capability check process, an alarm timeout condition 442 can be detected for initiating a silent device-initiated device capability check process. In response to this process, device 100 can be used at operation 463 to determine the current charge level of power supply 108 relative to any suitable threshold charge level (e.g., threshold charge level 165). For example, alarm timeout condition 442 could be a condition where PMU_RTC_ALARM is triggered, where such a condition can be triggered when the RTC counter register value of the RTC (e.g., the value of the first register 353 of RTC 351) is greater than a defined PMU_RTC_ALARM value (e.g., a stored value in the hardware of the system PMU). Figure 5 As shown, when device 100 is in state 521 and operating in full-power mode, in response to any suitable event 532 that SW_Alarm may pass (e.g., be triggered), device 100 may be configured to take one or more actions 536, including but not limited to one or more of the following actions:

[0094] (1) Setting PMU_ALARM_EN = 1 enables and / or sets and / or monitors alarms in the system PMU;

[0095] (2) Configure another duration X for PMU_RTC_ALARM, which can reset the value of PMU_RTC_ALARM to any suitable duration X; and / or

[0096] (3) Configure SW_Alarm for X-1 minutes, which can reset the value of the software alarm to any suitable duration, which may be at least slightly less than the reset duration of PMU_RTC_ALARM, or in other implementations, the SW alarm may be any other suitable software alarm, which may be part of any other periodic system wake-up event (e.g., to check cellular signal strength, etc.).

[0097] When device 100 is in full-power state 521 (e.g., state 401 when LPMF is set to T), this allows PMU_RTC_ALARM to be continuously reset to duration X (e.g., 1 hour, 2 hours, 4 hours, etc.) at a periodic frequency at least slightly less than duration X. Therefore, when device 100 transitions from NFC FPM state 401 to NFC LPM state 451, the hardware-based PMU alarm (PMU_RTC_ALARM) can always be active, ensuring that alarm timeout condition 442 occurs at least within the duration X of the transition from state 401 to state 451. In response to a PMU alarm (PMU_RTC_ALARM) timeout detected at condition 442, device 100 may be used (e.g., additionally) to wake up the system PMU, such that control application module 330 may be configured to determine at operation 463 that a specific power condition 464 is met, and then reset the PMU alarm (PMU_RTC_ALARM) at operation 456 (e.g., reset to duration X) before returning to NFC LPM state 451. Alternatively, in response to a PMU alarm (PMU_RTC_ALARM) timeout detected at condition 442, device 100 may be used (e.g., additionally) to wake up the system PMU, such that control application module 330 may be configured to determine at operation 463 that a specific power condition 465 is met, and then proceed to operation 458 to transition NFC component 120 from NFC LPM state 451 to NFC off state 471.

[0098] The determination at operation 463 can be any suitable determination for any appropriate power condition, such as the same operation as operation 453 or substantially similar to operation 453. For example, in some embodiments, operation 463 can be used to determine the condition of the “LOW_V” flag, which can be configured to indicate the relationship between the current charge of power supply 108 and a specific threshold charge level. As a particular example, operation 463 can typically be used to determine whether the current charge level of power supply 108 is higher or lower than the LPEM shutdown threshold charge level 165, which can be used to determine whether to keep NFC component 120 in NFC LPM power mode at state 451 or to transition NFC component 120 from NFC LPM power mode at state 451 to NFC shutdown power mode at state 471 (e.g., to save power by powering off NFC component 120 and terminating NFC low-power fast mode while still remaining in battery trap mode (e.g., low battery trap operation mode)). In a specific example, if each of any suitable number of consecutive samples (e.g., 10 consecutive samples) of the current charge level of power supply 108 (e.g., using data 307) is determined to be less than the LPEM shutdown threshold charge level 165, device 100 (e.g., device firmware) may be configured to set the LOW_V flag (e.g., a flag in a system PMU register) to '1', and when the current charge level of power supply 108 is determined to be at least greater than the LPEM shutdown threshold charge level 165 by some amount (e.g., at least 0.05 volts greater than the LPEM shutdown threshold charge level 165), it may be configured to clear or reset the LOW_V flag to '0'. Therefore, device 100 may be configured at operation 463 to confidently determine that the current charge level of power supply 108 is greater than the LPEM shutdown threshold charge level 165 by satisfying condition 464 (e.g., LOW_V = 0), or less than the LPEM shutdown threshold charge level 165 by satisfying condition 465 (e.g., LOW_V = 1). Therefore, in response to device 100 detecting RTC alarm timeout condition 442 and then determining at operation 463 that the current charge level of power supply 108 is greater than LPEM shutdown threshold charge level 165 by satisfying condition 464, device 100 may be configured to return to state 451 (e.g., keep NFC component 120 in NFC LPM mode in state 451) (e.g., via operation 456 which can reset PMURTC alarm), since power supply 108 can operate within LPEM operating charge level range 164.Alternatively, in response to device 100 detecting RTC alarm timeout condition 442, and then determining at operation 463 that the current charge level of power supply 108 is less than LPEM shutdown threshold charge level 165 by satisfying condition 465, device 100 may be configured to transition NFC component 120 from NEC LPM mode in state 451 to NFC shutdown mode in state 471 (e.g., via operations 458 and 474 or via operations 459 and 462 in state 461), since power supply 108 may no longer be operating within LPEM operating charge level range 164. Thus, condition 442 allows device 100 to periodically determine whether to transition from state 451 to state 471 (e.g., especially in the absence of any regular condition 452).

[0099] NFC component 120 may maintain the NFC low-power mode of NFC LPM state 451 until power supply 108 has been charged above a specific threshold charge level (e.g., threshold charge level 163) to enable a transition back to the NFC full-power mode of NFC FPM state 401. For example, as shown, when in state 451, device 100 may be used to perform device charging operation 466 (e.g., in response to any suitable charging event (e.g., a user plugging device 100 into a power outlet to receive external power generated by a power station)), during which time any suitable “charging and display UI” screen may be presented to the user at event 467 (e.g., to enable the user to determine that the device is being charged correctly). However, device 100 may satisfy condition 469 and may remain in NFC LPM state 451 until operation 466 causes the charge level of power supply 108 to exceed the specific threshold charge level (e.g., threshold charge level 163) to satisfy condition 468 for transitioning back to the NFC full-power mode of NFC FPM state 401 at operation 498 (e.g., an operation similar to operation 459). Therefore, device 100 can enable charging of power supply 108 to return from LPM state 451 to FPM state 401, and can also enable charging of power supply 108 to return from LPM state 451 to LPM state 451 (e.g., if the charging completed at operation 466 is insufficient to satisfy condition 468, then it remains in LPM state 451). Furthermore, it should be understood that if the device transitions from open state 401 to LPM state 451 in response to condition 412, which is a user's manual instruction to transition from open state 401 to LPM state 451, operation 466 may include the user attempting to manually instruct a transition from state 451 back to state 401 (e.g., through any suitable interaction with an enabled input element (e.g., a long press of button input element 110b or interaction with another input element)), in which case condition 466 may be satisfied, and device 100 may transition from state 451 back to state 401 without any actual charging of power supply 108. It should be understood that... Figure 4 The various operations and conditions shown in state diagram 400 are merely illustrative. 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 changed.

[0100] As mentioned, when operating in NFC low-power mode in NFC LPM state 451, NFC component 120 can be configured at operation 451n to perform any suitable transaction or communication 55 between electronic device 100 and terminal 10 using any credentials of device 100 currently designated as a fast-mode card. Even at any point during an attempt to transact at operation 451n or after a transaction has been completed at operation 451n, device 100 can be configured to generate any suitable output that can be used to indicate to the user of device 100 such an attempt or completed transaction. However, due to the fact that most or all of the software and / or applications and / or even the system PMU may be inactive or turned off during such an attempt or upon completion of such operation 451n, NFC component 120 can be used to control the generation and transmission of appropriate commands to elicit such output to the user. For example, as Figure 3 As shown, NFC component 120 can be configured to generate any suitable NFC activity output command 341 and transmit it directly to any suitable output component 112 that can operate during the NFC LPM operation mode in state 451 (e.g., haptic output component 112c, which can be powered directly from power supply 108 by power 323p during the NFC LPM operation mode in state 451). For example, haptic feedback output component 112c may include haptic driver amplifier 361, on which a haptic waveform 363 may be loaded. When device 100 can operate in the NFC low-power mode of NFC LPM state 451, haptic driver amplifier 361 may automatically play back the haptic waveform 363 in response to haptic feedback output component 112c receiving the NFC activity output command 341 from NFC component 120. This allows device 100 to provide haptic feedback to the user in response to NFC component 120 attempting to transact with terminal 55 using a fast-mode card, even when device 100 is operating in NFC low-power mode of NFC LPM state 451 (e.g., no system PMU may be inactive or off, and may not provide any power to any output component or NFC component of device 100). Figure 5As shown, through action 506, when the first fast mode card is enabled on device 100, an output waveform (e.g., waveform 363) can be loaded onto a driver amplifier (e.g., amplifier 361) (e.g., a haptic waveform can be loaded onto a haptic driver amplifier and / or an audio waveform can be loaded onto an audio driver amplifier), and / or GPIO (“NFC_GPIO2_AO=OPT_RESET_L=HIGH”) can be set to high as always so that the haptic driver amplifier 361 can be triggered in NFC low power mode, thereby ensuring that the haptic waveform can be used for playback during NFC low power mode. Although this output has been described as haptic feedback output using a haptic feedback output component, it should be understood that various other types of output information can be presented by any other suitable output component besides the haptic output component (e.g., user information can be audibly provided to the user via audio speaker output component 112b (e.g., any suitable audio waveform can be loaded onto any suitable audio driver amplifier and used in a manner similar to any of the haptic waveforms and / or any haptic driver amplifiers described above) or visible to the user via a visual output component (e.g., an LED). Therefore, device 100 can be used to perform one or more NFC transactions and provide any suitable output that can be used to indicate to the user of device 100 such an attempted or completed transaction when in a low-power operating state, in which the system PMU and any device operating system can be turned off, disabled, or inactive. Various transitions between states of state diagram 400 (e.g., above line DL) can be implemented using the system PMU of device 100 and a bootloader application instead of a full operating system application, enabling significant power savings. Meanwhile, certain actions within a state (e.g., below line DL (e.g., action 451n, which may include generating haptic or other user-detectable outputs)) can be implemented without even using the system PMU or loading any application for additional power savings, while also securely enabling certain NFC transactions to improve user convenience.

[0101] Although many concepts described herein have been described with respect to managing near-field communication during different power management modes of electronic devices (e.g., via NFC component 120), Figures 1 to 5One, some, or each of these communication types (e.g., via any other suitable communication component or circuitry) and / or any other suitable device function can be similarly managed. For example, any suitable first-type communication circuit 106 (e.g., higher-power communication circuitry, such as broadband cellular network communication circuitry or Wi-Fi, etc.) can be turned off, disabled, or inactive during any suitable battery-trap operating mode, while any suitable second-type communication circuit 106 (e.g., low-power communication circuitry, such as Bluetooth, etc.) can be used selectively or continuously during any suitable battery-trap operating mode. Thus, device 100 can be used to perform one or more specific communication type functions (e.g., Bluetooth communication) and provide any suitable output when in a low-power operating state, which can be used to indicate to the user of device 100 such attempts or completed communication of this type (e.g., playback of a specific audio waveform in response to Bluetooth communication received by the device), in which the system PMU and any device operating system and / or any other communication type function (e.g., cellular) can be turned off, disabled, or inactive. Various transitions between states in state diagram 400 (e.g., above line DL) can be implemented using the system PMU and bootloader application of device 100 instead of a full operating system application, enabling significant power savings. Meanwhile, certain actions within a state (e.g., below line DL (e.g., action 451n, which may include generating haptic or other user-detectable outputs)) can be achieved even without using the system PMU or loading any application for additional power savings, while also securely enabling certain types of communication to improve user convenience (e.g., enabling Bluetooth communication to provide certain functions to the device in low-power operation (e.g., communicating with other devices via Bluetooth to enable device detection in low-power operation)). (e.g., LPMF can be set to '1' if the user wants Bluetooth communication enabled during low-power operation, and '0' if the user does not want Bluetooth communication enabled during low-power operation). Therefore, even if the device's operating system is not running because the device needs charging, sufficient power can still be available in the battery to support fast mode (e.g., supporting "fast card" transactions). The device can be configured to automatically support this feature using any suitable credentials, including but not limited to access cards designated as "Fast Pass" cards (e.g., automatically or manually provided by the user), student ID cards with "Fast Mode" enabled, etc. The device can be configured to display a low battery icon and text indicating that a Fast Pass card is available in response to receiving any suitable user interaction with any appropriate device input component, such as a user pressing a side button.The NFC controller can perform fast card transactions under the same conditions as the device's operating system, except that it can instruct the transaction to have only limited output components used (e.g., haptic notification, but without presenting any visible notification). This feature may not be available when a standard user-initiated power-off is performed.

[0102] Figure 6 This is a flowchart illustrating an exemplary process 600 for operating an electronic device including a near-field communication component. At operation 602 of process 600, while the electronic device is operating in its normal power mode, during which the near-field communication component is operating in its full power mode, a low-power mode initiation event of the electronic device can be detected (e.g., the charge of power supply 108 of device 100 may be detected to be below threshold 163). At operation 604 of process 600, in response to the detection of operation 602 of process 600, the state of the low-power mode flag (LPMF) of the electronic device can be determined (e.g., the state of the LPMF of device 100 may be determined). At operation 606 of process 600, in response to detecting operation 602 of process 600, the electronic device can switch from operating in normal power mode to operating in low power mode by disabling multiple subsystems of the electronic device. When the determined LPMF state is a first state, the near-field communication component switches from operating in full power mode to operating in low power mode, and when the determined LPMF state is a second state different from the first state, the near-field communication component switches from operating in full power mode to operating in off mode. When operating in the off mode, the device uses less power than when operating in the low-power mode of the near-field communication component (e.g., the device 100 can switch from normal power mode to low-power mode by disabling the device 100's power management unit and / or device operating system, and by providing power from the power source 108 to the NFC component 120 for communication of fast mode credentials when LPMF=1 (e.g., by configuring the NFC component 120 to be in NFC low-power mode state 451), or by not providing power from the power source 108 to the NFC component 120 when LPMF=0 (e.g., by configuring the NFC component 120 to be in NFC off mode state 471)).

[0103] It should be understood that Figure 6 The operations shown in process 600 are merely illustrative; existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be changed.

[0104] Figure 7This is a flowchart of an exemplary process 700 for operating an electronic device including a communication component and a power supply. At operation 702 of process 700, a low-power mode initiation event of the electronic device can be detected (e.g., the charge of the power supply 108 of device 100 can be detected to be below a threshold 163). At operation 704 of process 700, in response to the detection of operation 702 of process 700, at least one of the power management unit or the operating system of the electronic device can be disabled (e.g., the power management unit and / or the operating system of device 100 can be disabled). At operation 706 of process 700, in response to the detection of operation 702 of process 700, when at least one fast mode credential is available on the electronic device, power can be supplied from the power supply to the communication component to enable the communication component to transmit data from at least one fast mode credential to a remote terminal (e.g., when LPMF=1, the NFC component 120 can be supplied with power from the power supply 108 for communication using the fast mode credential). At operation 708 of process 700, in response to detecting operation 702 of process 700, when no fast mode credentials are available on the electronic device, the communication component may be prevented from receiving any power from the power source (e.g., when LPMF=0, power source 108 may not provide any power to NFC component 120).

[0105] It should be understood that Figure 7 The operations shown in process 700 are merely illustrative; existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be changed.

[0106] Figure 8 This is a flowchart of an exemplary process 800 for operating an electronic device including a communication component, a storage register, and a battery. At operation 802 of process 800, it can be detected that the battery charge is below a predetermined threshold (e.g., it can be detected that the charge of power supply 108 of device 100 is below threshold 163). At operation 804 of process 800, in response to detecting operation 802 of process 800, multiple subsystems of the electronic device can be disabled (e.g., the power management unit and / or device operating system and / or touchscreen input component of device 100 can be disabled). At operation 806 of process 800, in response to detecting operation 802 of process 800, when the state of the storage register is a first state, power can be supplied from the battery to the communication component to enable the communication component to transmit data with a remote terminal (e.g., when LPMF=1, NFC component 120 can be supplied with power from power supply 108 for communication of fast-mode credentials). At operation 808 of process 800, in response to detecting operation 802 of process 800, when the state of the storage register is a second state different from the first state, the communication component may be prevented from receiving any power from the battery (e.g., when LPMF=0, power supply 108 may not provide any power to NFC component 120).

[0107] It should be understood that Figure 8 The operations shown in process 800 are merely illustrative; existing operations may be modified or omitted, additional operations may be added, and the order of certain operations may be changed.

[0108] In addition, relative to Figures 1 to 8 One, some, or all of the processes described herein may be implemented by software, but may also be implemented by hardware, firmware, or any combination of software, hardware, and firmware. Instructions for performing these processes may also be implemented as machine-readable code or computer-readable code recorded on a machine-readable or computer-readable medium. In some embodiments, the computer-readable medium may be a non-transitory computer-readable medium. Examples of such non-transitory computer-readable media include, but are not limited to, read-only memory, random access memory, flash memory, CD-ROM, DVD, magnetic tape, removable memory cards, and data storage devices (e.g., optical data storage devices, such as…). Figure 1 (Memory 104 and / or memory module 150). In other embodiments, the computer-readable medium may be a transient computer-readable medium. In such embodiments, the transient computer-readable medium may be distributed across a network-coupled computer system, such that computer-readable code is stored and executed in a distributed manner. For example, any suitable communication protocol may be used to transfer such a transient computer-readable medium from one electronic device to another (e.g., the computer-readable medium may be transferred to electronic device 100 via communication component 106 (e.g., as at least part of application 103 and / or application 143)). Such a transient computer-readable medium may be implemented as computer-readable code, instructions, data structures, program modules, or other data in the form of modulated data signals, such as carrier waves or other transmission mechanisms, and may include any information delivery medium. The modulated data signal may be a signal in which one or more of its characteristics are set or modified to encode information in the signal.

[0109] It should be understood that any or each module of either or both of the NFC component 120 and the power management subsystem 301 may 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 or both of the NFC component 120 and the power management subsystem 301 may be described in the general context of computer-executable instructions such as program modules that can 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 can perform one or more specific tasks or implement one or more specific abstract data types. It should also be understood that the number, configuration, function, and interconnection of modules of either or both of the NFC component 120 and the power management subsystem 301 are merely exemplary and the number, configuration, function, and interconnection of existing modules may be modified or omitted, additional modules may be added, and the interconnection of certain modules may be changed.

[0110] At least a portion of one or more modules of either or both of NFC component 120 and power management subsystem 301 may be stored in device 100 or otherwise accessed by device 100 in any suitable manner (e.g., stored in memory 104 of device 100 (e.g., as at least part of application 103 and / or application 143)). Any or each module of either or both of NFC component 120 and NFC management subsystem 301 may be implemented using any suitable technology (e.g., as one or more integrated circuit devices), and different modules may be the same or different in structure, capability, and operation. Any or all modules or other components of either or both of NFC component 120 and power management subsystem 301 may be mounted on an expansion card, directly mounted on the system motherboard, or integrated into a system chipset component (e.g., integrated into a "northbridge" chip).

[0111] Any module or each module of either or both of NFC component 120 and power management subsystem 301 may be a dedicated system implemented using one or more expansion cards suitable for various bus standards. For example, all modules may be mounted on different interconnect expansion cards or all modules may be mounted on a single expansion card. Relative to NFC component 120, by way of example only, modules of NFC component 120 may interact with the motherboard or processor 102 of device 100 via expansion slots (e.g., peripheral component interconnect (“PCI”) slots or PCIexpress slots). Alternatively, NFC component 120 need not be removable, but may include one or more dedicated modules that may include memory (e.g., RAM) dedicated to module use. In other embodiments, NFC component 120 may be integrated into device 100. For example, modules of NFC component 120 may utilize a portion of device memory 104 of device 100. Any module or each module of either or both of NFC component 120 and power management subsystem 301 may include its own processing circuitry and / or memory. Alternatively, any module of either or both of the NFC component 120 and the power management subsystem 301, or each module, may share processing circuitry and / or memory with any other module of the NFC component 120 and / or the power management subsystem 301 and / or the processor 102 and / or the memory 104 of the device 100.

[0112] As mentioned, electronic device 100 may use graphical data to drive a display (e.g., display output unit 112a) to display a graphical user interface (“GUI”) 180. GUI 180 may be configured to receive touch input via touch input unit 110f. Implemented as a touchscreen (e.g., utilizing display output unit 112a as I / O unit 114a), touch I / O unit 110f may display GUI 180. Alternatively, GUI 180 may be displayed on a display (e.g., display output unit 112a) independent of touch input unit 110f. GUI 180 may include graphical elements displayed at specific locations within the interface. Graphical elements may include, but are not limited to, various displayed virtual input devices, including virtual scroll wheels, virtual keyboards, virtual knobs, virtual buttons, any virtual user interface (“UI”), etc. Users may perform gestures at one or more specific locations on touch input unit 110f that can be associated with the graphical elements of GUI 180. In other embodiments, users can perform gestures at one or more locations independent of the position of the graphical elements in the GUI 180. Gestures performed on the touch input component 110 can directly or indirectly manipulate, control, modify, move, actuate, initiate, or generally affect graphical elements within the GUI, such as cursors, icons, media files, lists, text, all or part of an image, etc. For example, with a touchscreen, a user can interact directly with a graphical element by performing a gesture over it. Alternatively, a touchpad typically provides indirect interaction. Gestures can also affect non-displayed GUI elements (e.g., causing a user interface to appear) or other actions of the device 100 (e.g., affecting the state or mode of the GUI, application, or operating system). Gestures can be performed or not performed on the touch input component 110 in conjunction with a displayed cursor. For example, when performing a gesture on a touchpad, a cursor or pointer can be displayed on the screen or touchscreen, and the cursor or pointer can be controlled via touch input on the touchpad to interact with graphical objects on the screen. In other embodiments where gestures are performed directly on the touchscreen, the user can interact directly with objects on the touchscreen regardless of whether a cursor or pointer is displayed on it. Feedback can be provided to the user via bus 118 in response to or based on a touch or proximity touch on the touch input component 110. Feedback can be transmitted via optical, mechanical, electrical, olfactory, acoustic, or any combination thereof and in a variable or invariable manner.

[0113] Although systems, methods, and computer-readable media for managing near-field communications have been described, it should be understood that many modifications may be made thereto without departing in any way from the substance and scope of the subject matter described herein. Any non-substantial modifications to the claimed subject matter, whether now known or hereafter contemplated, that are regarded by one of ordinary skill in the art as equivalent to the claims are expressly considered to be within the scope of the claims. Therefore, obvious substitutions now known or hereafter known by one of ordinary skill in the art are defined as being within the scope of the defined elements.

[0114] Therefore, those skilled in the art will recognize that the invention can be practiced in ways other than those described in the embodiments, which are provided for illustration and not limitation.

Claims

1. A method, the method comprising: The credentials on the electronic device are designated as the initial credentials for use in the low-power mode of the electronic device; In response to designating the credentials on the electronic device as the initial credentials, the state of the low power mode flag of the power management unit of the electronic device is set to a first state, wherein the low power mode flag indicates whether near-field communication is permitted during the low power mode; as well as After setting the state of the low-power mode flag, in response to detecting a low-power mode initiation event: Determine the state of the low-power mode flag of the power management unit of the electronic device; In response to the state of determining the low power mode flag being set to the first state, the near-field communication component is switched from operating in full power mode to operating in low power mode. as well as In response to the determination that the low power mode flag is set to a second state, the near-field communication component is switched from full power mode operation to off mode operation.

2. The method according to claim 1, further comprising: Cancel designating the credentials on the electronic device as the initial credentials used in the low-power mode of the electronic device; In response to the cancellation of designation, the state of the low power mode flag of the power management unit of the electronic device is set to the second state.

3. The method according to claim 1, wherein: When the near-field communication component is operating in the low-power mode, the near-field communication component is configured to actively transmit data from at least one credential on the electronic device to a remote terminal; and When the near-field communication component is operating in the off mode, the near-field communication component is not configured to actively transmit any data from any credentials on the electronic device to the remote terminal.

4. The method of claim 1, wherein detecting the low-power mode initiation event includes receiving specific user input via at least one input component of the electronic device.

5. The method of claim 1, wherein detecting the low-power mode initiation event includes determining that the charge of the power supply of the electronic device is below a predetermined threshold.

6. The method of claim 5, wherein the predetermined threshold is a minimum battery charge value for executing the device operating system of the electronic device.

7. The method of claim 1, wherein the low-power mode flag is a register in at least one of the power management unit of the electronic device or the non-volatile memory of the electronic device.

8. An electronic device, comprising: Memory; Power management unit; Near-field communication components; as well as At least one processor, said at least one processor being configured to: The credentials on the electronic device are designated as initial credentials for use in the low-power mode of the electronic device; In response to designating the credentials on the electronic device as the initial credentials, the state of the low power mode flag of the power management unit of the electronic device is set to a first state, wherein the low power mode flag indicates whether near-field communication is permitted during the low power mode; as well as After setting the state of the low-power mode flag, in response to detecting a low-power mode initiation event: Determine the state of the low-power mode flag of the power management unit of the electronic device; as well as In response to the state of determining the low power mode flag being set to the first state, the near-field communication component is switched from operating in full power mode to operating in low power mode.

9. The electronic device of claim 8, wherein the at least one processor is further configured to: In response to the determination that the low power mode flag is set to a second state, the near-field communication component is switched from full power mode operation to off mode operation.

10. The electronic device of claim 9, wherein the at least one processor is further configured to: Cancel designating the credentials on the electronic device as the initial credentials used in the low-power mode of the electronic device; In response to the cancellation of designation, the state of the low power mode flag of the power management unit of the electronic device is set to the second state.

11. The electronic device according to claim 9, wherein: When the near-field communication component is operating in the low-power mode, the near-field communication component is configured to actively transmit data from at least one credential on the electronic device to a remote terminal; and When the near-field communication component is operating in the off mode, the near-field communication component is not configured to actively transmit any data from any credentials on the electronic device to the remote terminal.

12. The electronic device of claim 8, wherein the at least one processor is further configured to detect the low-power mode initiation event by receiving specific user input via at least one input component of the electronic device.

13. The electronic device of claim 8, wherein the at least one processor is further configured to: detect the low-power mode initiation event by determining that the charge of the power supply of the electronic device is below a predetermined threshold.

14. The electronic device of claim 13, wherein the predetermined threshold is a minimum battery charge value for executing the device operating system of the electronic device.

15. The electronic device of claim 8, wherein the low-power mode flag is a register in at least one of the power management unit of the electronic device or the non-volatile memory of the electronic device.

16. A non-transitory machine-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations including: The credentials on the electronic device are designated as the initial credentials for use in the low-power mode of the electronic device; In response to designating the credentials on the electronic device as the initial credentials, the state of the low power mode flag of the power management unit of the electronic device is set to a first state, wherein the low power mode flag indicates whether near-field communication is permitted during the low power mode; as well as After setting the state of the low-power mode flag, in response to detecting a low-power mode initiation event: Determine the state of the low-power mode flag of the power management unit of the electronic device; as well as In response to the determination that the low-power mode flag is set to the first state, the near-field communication component is switched from operating in full-power mode to operating in low-power mode.

17. The non-transitory machine-readable medium of claim 16, wherein the instructions further include: In response to the determination that the low power mode flag is set to a second state, the near-field communication component is switched from full power mode operation to off mode operation.

18. The non-transitory machine-readable medium according to claim 17, wherein: When the near-field communication component is operating in the low-power mode, the near-field communication component is configured to actively transmit data from at least one credential on the electronic device to a remote terminal; and When the near-field communication component is operating in the off mode, the near-field communication component is not configured to actively transmit any data from any credentials on the electronic device to the remote terminal.

19. The non-transient machine-readable medium of claim 16, wherein detecting the low-power mode initiation event comprises at least one of the following: Receive specific user input via at least one input component of the electronic device; or It is determined that the charge of the power supply of the electronic device is below a predetermined threshold.

20. The non-transient machine-readable medium of claim 16, wherein detecting the low-power mode initiation event includes receiving specific user input via at least one input component of the electronic device.

Images