Device and method of operating a controllable electronic device
Abstract
A device may include a near field communication antenna, a monitor, a comparator, and a trigger. The near field communication antenna may be configured to detect an external near field communication device. The monitor may be configured to monitor a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device. The comparator may be configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions. The trigger may be configured to initiate a predefined action of the device based on the comparison.
Term
9.7 yearsto projected expiry
Projected expiry 18 May 2036, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
15 claims: 2 independent, 13 dependent
- 1A method of operating a controllable electronic device, the method comprising:with NFC circuitry in the controllable electronic device, sensing movement of the NFC accessory relative to the controllable electronic device;with processing circuitry in the controllable electronic device, identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements, wherein the database of predefined movements associates each predefined movement with a predefined action of the controllable electronic device;and with the processing circuity, triggering the predefined action associated, in the database, with the given predefined movement.
- 7A device comprising:a near field communication antenna configured to detect an external near field communication device;a monitor configured to monitor a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device;a comparator configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions;and a trigger configured to initiate a predefined action of the device based on the comparison.
Independent claims2
310 paragraphs, as filed
<u>Technical Field</u>
0001Various embodiments relate generally to a device and a method operating a controllable electronic device.
<u>Background</u>
0002Conventional smart devices, such as e.g. smartphones and tablets, primarily utilize virtual and physical buttons in order to enable a user to control the smart device. For example, a user may trigger different operations of a smart device such as "return/back", "return to home screen", "list recent activities/task" by pressing one or more buttons. A number of separate buttons are traditionally utilized to individually trigger each corresponding operation, such as a "home button" for triggering a return to home screen or a "back button" for returning to a previous screen. Sequences of button presses may also be predefined in order to trigger an operation of the smart device, such as pressing virtual buttons on one or more displayed menu screens in order to navigate through virtual screens of a smart device and to trigger one or more related operations.
<u>Brief Description of the Drawings</u>
0003In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various embodiments of the invention are described with reference to the following drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> shows an exemplary near field communication (NFC) accessory;</li><li><figref idref="f0002">FIG. 2</figref> shows various components and circuits of an NFC-enabled smart device and an NFC accessory;</li><li><figref idref="f0003">FIG. 3</figref> shows a flow diagram illustrating an NFC-based smart device control process;</li><li><figref idref="f0004">FIG. 4</figref> shows a flow diagram further illustrating the NFC-based smart device control process of <figref idref="f0003">FIG. 3</figref>;</li><li><figref idref="f0005">FIG. 5</figref> shows a digital waveform representations of a number of NFC accessory movements;</li><li><figref idref="f0006">FIG. 6</figref> shows positioning scenarios of an NFC accessory relative to an NFC-enabled smart device;</li><li><figref idref="f0007">FIG. 7</figref> shows several digital waveforms illustrating an active-delay mechanism for NFC-based smart device control;</li><li><figref idref="f0008">FIG. 8</figref> shows a flow diagram illustrating a further NFC-based smart device control process using an active-delay mechanism;</li><li><figref idref="f0009">FIG. 9</figref> shows a flow diagram illustrating a method for controlling an NFC-enabled smart device according to an aspect of the disclosure;</li><li><figref idref="f0010">FIG. 10</figref> shows a flow diagram illustrating a method for controlling a smart device according to a further aspect of the disclosure;</li><li><figref idref="f0011">FIG. 11</figref> shows a block diagram illustrating internal components of core hardware of a smart device; and</li><li><figref idref="f0012">FIG. 12</figref> shows a flow diagram illustrating a method for operating a controllable electronic device.</li></ul>
<u>Description</u>
0004The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and embodiments in which the invention may be practiced.
0005The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
0006As used herein, a "circuit" may be understood as any kind of a logic implementing entity, which may be special purpose circuitry or a processor executing software stored in a memory, firmware, or any combination thereof. Furthermore, a "circuit" may be a hard-wired logic circuit or a programmable logic circuit such as a programmable processor, for example a microprocessor (for example a Complex Instruction Set Computer (CISC) processor or a Reduced Instruction Set Computer (RISC) processor). A "circuit" may also be a processor executing software, for example any kind of computer program, for example a computer program using a virtual machine code such as for example Java. Any other kind of implementation of the respective functions which will be described in more detail below may also be understood as a "circuit". It may also be understood that any two (or more) of the described circuits may be combined into one circuit.
0007The incorporation of Near Field Communication (NFC) technology has become commonplace in many new smart phone and tablet products. This NFC technology has been conventionally deployed to exchange basic data between two NFC terminals, such as between an NFC-enabled smart device and an NFC accessory, such as e.g. a ring, key fob, wearable device with an NFC inlay, or other similar NFC accessories. Such NFC accessories may be conventionally used to trigger an operation on a smart device, such as initiating a phone call to a preselected contact, enabling external services such as e.g. Wireless Fidelity (WiFi) or Bluetooth, or locking a device. For example, a user may position an NFC accessory within the NFC field range of an NFC-enabled smart device. The NFC-enabled smart device may identify the NFC accessory (such as by reading identification information or other stored data provided wirelessly by the NFC accessory over), and may trigger a predefined smart device operation upon identification of an eligible NFC accessory. A user may thus predefine a smart device to execute a selected operation in response to identifying a certain NFC accessory, and may even program a smart device to execute a different operation in response to identification of each of a number of different NFC accessories.
0008However, these conventional use cases for NFC accessories and NFC-enabled smart devices may be limited by the detection of static content of an NFC accessory. In other words, current NFC-enabled smart devices may simply identify the presence of a recognized NFC accessory and trigger a single predefined operation. It may thus not be possible to perform different operations with a single NFC accessory without re-programming the NFC smart device every time to perform a different operation in response to a subsequent detection of the NFC accessory. The degree of control offered by existing NFC use cases is therefore limited.
0009Accordingly, it may be desirable to dynamically expand the capability of NFC interactions between NFC-enabled devices (e.g. an NFC-enabled smart device and NFC accessory) by allowing a single NFC accessory to trigger multiple different operations of a proximate NFC-enabled smart device, such as e.g. by detecting spatial movements of an NFC accessory relative to an NFC-enabled smart device.
0010Such an improvement may be particularly desirable in providing a degree of control to a user for operating a smart device. As previously detailed, smart devices are conventionally controlled by button press(es), such as either physical buttons distributed on the surface of a smart device or virtual buttons displayed on an interactive display screen. Due to the spatial distribution of buttons across the smart device, it may be unnecessarily inconvenient for a user to control a smart device with a single hand. This problem may be accentuated for the use of larger devices, such as tablets and larger smartphones, where re-handling of the smart device or use of two hands may be necessary in order for a user to access the desired buttons. Furthermore, certain buttons such as the "home button" or "function button" may be utilized by a user at a substantially high rate, which may potentially lead to potential damage due to over-usage.
0011Accordingly, it may be possible to provide an enhanced user experience by offering the user with an alternative method to control a smart device in the form of enhanced NFC-based smart device control. While the above-detailed existing NFC-based approaches may be used to trigger certain smart device operations, the use cases are severely limited. In particular, conventional NFC-based smart device control only allows a single smart device operation to be programmed to an NFC accessory at one time, and accordingly a single NFC accessory may only be capable of triggering a single operation of an NFC-enabled smart device. A user may thus need to re-program an NFC device every time to perform a different operation in response to the same NFC accessory, which may severely restrict the usefulness of NFC-based smart device control.
0012In contrast, NFC-based smart device control may utilize timing information associated with detection of an NFC accessory by an NFC-enabled smart device in order to recognize different spatial movement patterns of the NFC accessory relative to the NFC-enabled smart device. In doing so, an NFC-enabled smart device may be capable of triggering a variety of different movements by detecting distinct spatial movement patterns, herein also referred to as NFC movements, of a proximate NFC accessory.
0013NFC-enabled smart devices may conventionally operate by constantly monitoring for the presence of NFC-enabled devices such as NFC accessories. NFC-enabled smart devices may thus have a finite NFC field range that dictates how proximate an NFC accessory must be in order to be successfully detected by the NFC-enabled smart device. An NFC-enabled smart device may detect the presence of an NFC accessory that has entered the detection range, and may proceed to identify the detected NFC accessory, such as by extracting NFC identification information from an NFC signal received from the detected NFC accessory. The NFC-enabled smart device may then compare the identity of the detected NFC accessory to a database in order to determine whether an operation has been associated with the detected NFC accessory and may proceed to perform an associated operation in the event that an operation has been previously associated with the detected NFC accessory.
0014Existing NFC-based smart device control approaches may thus be based solely on identifying whether or not a predefined NFC accessory is in range, and performing a single operation associated with identification information of the NFC accessory if the NFC accessory is in range. In contrast, an improved NFC-enabled smart device may be configured to assess the timing associated with the detection of an NFC accessory. In other words, the temporal variance of an NFC accessory between a detected state (i.e. within the detection range of an NFC-enabled smart device) and an undetected state (i.e. out of range of an NFC-enabled smart device) caused by the user moving the NFC accessory may be used to trigger one or more different operations of the smart device.
0015An NFC-enabled smart device may monitor the varying NFC detection state (i.e. detected or undetected) of an NFC accessory in terms of time in order to recognize a variety of spatial movement patterns, referred to herein as either "NFC movements" or simply "movements". These movements may be characterized by timing information associated with state changes in detection state, such as by one or more timestamps indicating detected or undetected state. The NFC-enabled smart device may then trigger a variety of different operations based on the particular detected movement of the NFC accessory. In this manner, a user may be able to control an NFC-enabled smart device with an NFC accessory to perform a variety of different operations, thus offering a distinct advantage over the existing NFC use cases that may only support a single operation per NFC accessory. A user may thus be given greater control over an NFC-enabled smart device while reducing the number of operations that explicitly require a button press, thereby contributing to an improved user experience.
0016<figref idref="f0001">FIG. <b>1</b></figref> shows an exemplary NFC accessory <b>100.</b> As shown in <figref idref="f0001">FIG. 1</figref>, NFC accessory <b>100</b> may be formed in the shape of a ring and be made of material <b>110,</b> which may be light and foldable, such as e.g. plastic film. NFC accessory <b>100</b> may be provided with NFC inlay <b>120,</b> which may integrated into material <b>110</b> and may be detectable by an external NFC-enabled smart device using NFC signaling. NFC accessory <b>100</b> may be worn on a fingertip or middle part of a user's finger. A proximate NFC-enabled smart device may detect NFC inlay <b>120</b> if the user positions their finger within the NFC field range of the proximate NFC-enabled smart device, and may subsequently attempt to identify NFC accessory <b>100</b> based on identification information provided by NFC inlay <b>120.</b> An NFC-enabled device may detect the absence ofNFC accessory <b>100,</b> i.e. be aware of the absence of NFC accessory <b>100,</b> if a user wearing NFC accessory <b>100</b> moves their finger out of the NFC field range.
0017An NFC-enabled smart device may accordingly be in either <i>NFC_Detection_Active</i> state or <i>NFC_Detection_Inactive</i> state based on whether or not an NFC accessory, such as NFC accessory <b>100,</b> is within the NFC field range of an NFC-enabled smart device following certain spatial movements of NFC accessory <b>100</b> relative to an NFC-enabled device, e.g. according to the movement of a user's finger equipped with NFC accessory <b>100.</b> The NFC detection state of an NFC-enabled smart device may vary from <i>NFC_Detection_Inactive</i> to <i>NFC_Detection_Active,</i> and then back to <i>NFC_Detection_Inactive</i> state as the user moves NFC accessory <b>100</b> into and out of the NFC field range, such as e.g. with finger movements.
0018A user may typically hold their forefinger near the back of a smart device, and may be free to move their forefinger along the back of the smart device in addition to bending and unbending their forefinger, thereby bringing their finger closer to and further away from the back of a smart device. A user may therefore utilize such finger movements to make NFC accessory <b>100</b> enter or exit the NFC field range of an NFC-enabled smart device, i.e. move NFC accessory <b>100</b> into and out of the NFC field range of an NFC-enabled smart device, which as a result may trigger <i>NFC_Detection_Active</i> or <i>NFC_Detection_Inactive</i> state of the NFC-enabled smart device. Different sequences of <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state, defined by timing information (such as e.g. timestamps) representing state transitions, may then be captured by an NFC-enabled smart device and used to trigger a pre-defined smart device operation.
0019NFC accessory <b>100</b> may be rotated on a user's figure (shown as shown by <i>Operation_1</i><b>130</b>) in order to alter the emitted NFC field strength by NFC accessory <b>100.</b> For example, a user may increase the emitted NFC field strength relative to a proximate NFC-enabled smart device by rotating their finger such that NFC inlay <b>120</b> is closer to and/or facing an NFC antenna provided on the NFC-enabled smart device. NFC accessory <b>100</b> may be more easily detected by the NFC-enabled smart device when in this position, and accordingly the NFC-enabled smart device may be more prone to detect NFC accessory <b>100</b> and enter <i>NFC_Detection_Active</i> state. Similarly, a user may rotate NFC accessory <b>100</b> on their finger to be turned sideways relative to the NFC field associated with the NFC antenna provided on the NFC-enabled smart device in order to make NFC accessory <b>100</b> less prone for detection by the NFC-enabled smart device, and thus more likely for the NFC-enabled smart device to be in <i>NFC_Detection_Inactive</i> state.
0020NFC accessory <b>100</b> may be folded along the fold lines <b>140a</b> and <b>140b,</b> such as to prepare NFC accessory <b>100</b> for storage. The thickness of NFC accessory <b>100</b> may be substantially negligible when folded, and thus may be easily stored in a wallet, pocket, desk, or even in a dedicated slot on a smart device similar to those provided for styluses.
0021The detection state of NFC accessory <b>100</b> relative to a proximate NFC-enabled smart device may vary based on the position of NFC accessory <b>100</b> relative to the NFC-enabled smart device. NFC-enabled smart devices may constantly monitor for NFC accessories within NFC field range, and subsequently may determine if an NFC accessory is within NFC field range or outside of NFC field range.
0022<figref idref="f0002">FIG. <b>2</b></figref> illustrates an exemplary scenario in which NFC accessory <b>100</b> is proximate to smart device <b>200.</b> It is appreciated that the illustrated spatial positioning of NFC accessory <b>100</b> relative to smart device <b>200</b> is exemplary, and that NFC accessory <b>100</b> may conventionally be located along the back of smart device <b>200</b> (as will be described regarding <figref idref="f0006">FIG. <b>6</b></figref><b>).</b> Smart device <b>200</b> may be NFC-enabled, and may be e.g. a smartphone or a tablet. Smart device <b>200</b> may include NFC antenna <b>202,</b> NFC controller <b>204,</b> smart device memory <b>206,</b> and core hardware <b>208.</b> The aforementioned circuitry and hardware (such as NFC controller <b>204,</b> smart device memory <b>206,</b> and core hardware <b>208)</b> may be implemented as separated circuits, e.g. such as separate integrated circuits as illustrated in <figref idref="f0002">FIG. <b>2</b></figref><b>.</b> It is understood that some or all of the circuits may be implemented by a common programmable processor, such as e.g. a microprocessor. Accordingly, some or all of the functionality of the one or more aforementioned circuitry may be consolidated into a single hardware component. It is also understood that smart device <b>200</b> may include a number of additional components, including hardware, processors, memory, and other specialty or generic hardware/processors/circuits, etc., in order to support a variety of additional operations of wireless radio communications. Smart device <b>200</b> may also include a variety of user input/output devices such as displays, keypads, touchscreens, speakers, external buttons, etc.
0023Smart device <b>200</b> may be provided with NFC-dedicated components NFC antenna <b>202</b> and NFC controller <b>204</b> in order to support NFC functionality. In addition to the aforementioned NFC-specific components, smart device <b>200</b> may be provided with core hardware <b>208</b> in order to support various functionalities associated with conventional smart device operation, such as executing software components and applications, accepting inputted user data, providing a user with multimedia content, etc. Core hardware <b>208</b> may thus be e.g. a core central processing unit (CPU) responsible for a substantial degree of control over smart device <b>200.</b> Smart device <b>200</b> may be provided with one or more additional antennas or antenna arrays, such as antennas for transmission and/or reception of wireless radio signals associated with cellular communications or other radio access networks. As shown in <figref idref="f0002">FIG. 2</figref>, NFC controller <b>204</b> is capable of interacting with core hardware <b>208.</b>
0024As will be described, smart device <b>200</b> may therefore include a near field communication antenna (antenna <b>202)</b> configured to detect an external near field communication device. Smart device <b>200</b> may also include a processor (core hardware <b>208)</b> configured to pilot NFC controller 204 to detect a change in detection state of the smart device from a first detection state to a second detection state, wherein the change in detection state of the smart device is based on whether the near field communication antenna detects the external near field communication device, determine a duration of a first time period during which the smart device remains in the second detection state, and trigger a predefined action of the smart device based on at least the duration of the first time period. Smart device <b>200</b> may additionally a memory (NFC smart device memory <b>206).</b>
0025In another aspect of the disclosure, the processor (core hardware <b>208)</b> may be configured to monitor a series of one or more transitions in a detection state of the smart device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device, perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with predefined series of one or more transitions, and trigger a predefined action of the smart device based on the comparison. As will be described, the first and second timing information may be based on e.g. timestamps or durations of time.
0026In a further aspect of the disclosure, the processor (NFC controller <b>204)</b> may be configured to detect a transition in detection state of the smart device from a first detection state to a second detection state, wherein the detection state of the smart device is based on whether the near field communication antenna detects the external near field communication device, control the smart device to operate according to a first operation mode during a first time period before the transition in which the smart device remains in the first detection state, and control the smart device to operate according to a second operation mode during a second time period after the transition once the smart device transitions from the first detection state to the second detection state. As will be described, the first operation mode and the second operation mode may be a predefined operation mode of the smart device, such as e.g. text entry modes, virtual window scrolling modes, and/or copy/paste modes.
0027Smart device <b>200</b> may thus be capable of interacting with NFC accessories such as NFC accessory <b>100</b> using NFC antenna <b>202,</b> NFC controller <b>204,</b> and smart device memory <b>206.</b> For example, NFC controller <b>204</b> may be configured to detect the presence of NFC accessory <b>100</b> within NFC field range using NFC antenna <b>202.</b> As previously detailed, NFC controller <b>204</b> may be configured to interact with core hardware <b>208.</b> Core hardware <b>208</b> may thus be configured to interact with NFC controller <b>204</b> in order to monitor whether or not NFC controller <b>204</b> detects an NFC accessory such as NFC accessory <b>100.</b>
0028For example, core hardware <b>208</b> may be configured to execute software, such as e.g. software stored in smart device memory <b>206.</b> Core hardware <b>208</b> may thus be configured to execute one or more software routines based on NFC applications, which may e.g. include software routines configured to interact with NFC controller <b>204</b> to control various operations of smart device <b>200</b> based on whether NFC controller <b>204</b> detects the presence of an NFC accessory such as e.g. NFC accessory <b>100.</b>
0029Core hardware <b>208</b> may thus be configured interact with NFC controller <b>204</b> in order to determine whether or not NFC controller <b>204</b> detects an NFC accessory, such as e.g. according to one or more software routines stored in smart device memory <b>206.</b> Core hardware <b>208</b> may additionally be configured to determine timing information associated with changes in detection state of an NFC accessory in addition to identification information of a detected NFC accessory through interactions with NFC controller <b>204.</b> It is appreciated that such functionality involving timing and identification information determination may be implemented in a number of different ways, such as by determining timing and/or identification information solely in NFC controller <b>204</b> and providing such information to core hardware <b>208.</b> Alternatively, such functionality may be implemented in part by both NFC controller <b>204</b> and core hardware <b>208,</b> or may be substantially implemented in core hardware <b>208</b> based on raw information provided by NFC controller <b>204.</b>
0030Core hardware <b>208</b> may thus determine an NFC detection state based on the data/responses received from NFC controller <b>204,</b> such as data indicating whether or not NFC accessory <b>100</b> is within NFC field range., i.e. is detected by NFC controller <b>204.</b> Core hardware <b>208</b> then may enter <i>NFC</i>_<i>Detection</i>_<i>Active</i> state if NFC controller <b>204</b> indicates that NFC accessory <b>100</b> is within NFC field range, i.e. is detectable, which may be on a software level as executed by core hardware <b>208.</b> Core hardware <b>208</b> may additionally be configured to determine a point in time in which NFC accessory <b>100</b> enters NFC field range, such as e.g. a time stamp or similar timing information, which may be based on data provided by NFC controller <b>204.</b>
0031Similarly, core hardware <b>208</b> may be able to determine if NFC accessory <b>100</b> is outside of NFC field range based on data/responses received from NFC controller <b>204.</b> Core hardware <b>208</b> may additionally be able to determine a point in time when NFC accessory <b>100</b> exits NFC field range after being within NFC field range, which may be e.g. in the form of a timestamp and similarly based on data received from NFC controller 204. Core hardware <b>208</b> may then enter <i>NFC_Detection_Inactive</i> state, which as previously detailed regarding <i>NFC_Detection_Active</i> state may be on a software level as executed by core hardware <b>208.</b>
0032It is appreciated that for purposes of explanation, smart device <b>200</b> may similarly be considered to in <i>NFC_Detection_Active</i> or <i>NFC_Detection_Inactive</i> state in accordance with detection state held by core hardware <b>208</b> at a given point in time. It is thus understood that references to smart device <b>200</b> being in a particular detection state corresponds to core hardware <b>208</b> also being in the same particular detection state, such as e.g. dictated on a software level within core hardware <b>208.</b> Similarly, it is understood that references to core hardware <b>208</b> being in a particular detection state corresponds to smart device <b>200</b> also being in the same particular detection state.
0033Likewise, it is appreciated that references to smart device <b>200</b> performing a particular operation refer to core hardware <b>208</b> performing the particular operation, such as by executing one or more software routines to perform the particular operation.
0034<figref idref="f0003">FIG. <b>3</b></figref> illustrates an exemplary process <b>300</b> which smart device <b>200</b> may execute. As previously detailed, smart device <b>200</b> may include NFC controller <b>204</b> and core hardware <b>208,</b> which in conjunction may be configured to control detection, identification, and communication with NFC devices. Smart device <b>200</b> may begin in <i>NFC_Detection_Inactive</i> state in <b>302.</b> NFC controller <b>204</b> may be in an "NFC polling mode" and enable an "NFC Card Detection Loop" to detect precisely when an NFC accessory, such as NFC accessory <b>100,</b> enters the NFC field range of the smart device <b>200.</b> The NFC Card Detection Loop may be implemented at a firmware level within NFC controller <b>204,</b> and may be configured by the original equipment manufacturer of smart device <b>200.</b> The NFC Card Detection Loop may operate on a millisecond scale, such as 50 ms or 100 ms, which may be configurable via an upper software level such as an Application Program Interface (API).
0035NFC accessory <b>100</b> may move into NFC field range of smart device <b>200,</b> such as e.g. due to a user performing a finger movement with a finger equipped with NFC accessory <b>100.</b> For example, the user may slide their finger equipped with NFC accessory 100 from an initial location outside of NFC field range to another location inside of NFC field range. Alternatively, the user may straighten their finger from a bent position such that NFC accessory <b>100</b> moves from an initial location outside ofNFC field range to another location inside of NFC field range. NFC controller <b>204</b> may thus be able to detect an NFC signal emitted from NFC inlay <b>120</b> ofNFC accessory <b>100,</b> and thus may detect the NFC accessory in <b>304</b> of method <b>300.</b> NFC controller <b>204</b> may then exchange an initial command/answer (i.e. NFC Technology detection phase, Collision resolution phase, and Activation phase) with NFC accessory <b>100.</b> Smart device <b>200</b> may then enter into <i>NFC_Detection_Active</i> state in <b>306</b> by receiving a notification from the firmware layer (i.e. Activate Notification), and may record a timestamp signifying the point in time which NFC accessory <b>100</b> was detected by smart device <b>200,</b> which may e.g. be executed by core hardware <b>208.</b> The timestamp may thus indicate the time during which NFC device 200 entered <i>NFC_Detection_Active</i> state, and may accordingly be used by core hardware <b>208</b> to identify user movements of NFC accessory <b>100</b> in order to trigger a variety of smart device operations.
0036In contrast to conventional use cases for NFC, smart device <b>200</b> may be configured to trigger multiple operations with a single NFC accessory without constant re-programming. However, smart device <b>200</b> may additionally be configured to support the aforementioned conventional use cases for NFC in addition to the enhanced NFC-based smart device control described herein.
0037Smart device <b>200</b> may rely on identification information in order to determine whether to operate according to the conventional NFC use cases or according to enhanced NFC-based smart device control. After entering <i>NFC_Detection_Active</i> state and recording a timestamp to indicate entry into <i>NFC_Detection_Active</i> state, smart device <b>200</b> may attempt to identify NFC accessory <b>100</b> by reading information provided by NFC accessory <b>100,</b> which may be e.g. performed by NFC controller <b>204.</b> For example, NFC controller <b>204</b> may read the Unique Identification Number (UID) provided by NFC accessory <b>100,</b> such as e.g. from a memory provided in NFC inlay <b>120.</b> NFC controller <b>204</b> may additionally read block data provided by NFC accessory <b>100</b> or may read an NFC Data Exchange Format (NDEF) message provided by NFC accessory <b>100.</b> NFC controller <b>204</b> may be configured to determine which information provided by NFC accessory <b>100</b> should be read, and may then perform the associated reading operation in several milliseconds. NFC controller <b>204</b> may then proceed to determine whether or not NFC accessory <b>100</b> has been pre-configured to operate according to enhanced NFC-based smart device control protocols in <b>308. 308</b> may thus include determining if NFC accessory <b>100</b> is an Eligible Tag (i.e. eligible NFC accessory), i.e. has been pre-configured to trigger enhanced NFC-based smart device control. If NFC accessory <b>100</b> is an Eligible Tag, method <b>300</b> may proceed to enhanced NFC-based smart device control mechanism in <b>310,</b> i.e. may proceed to implement smart device control based on NFC movements according to aspects of this disclosure provided herein. If NFC accessory <b>100</b> is not an Eligible Tag, method <b>300</b> may instead proceed to default NFC tag reading procedure in <b>312.</b> Default NFC tag reading procedure may include the aforementioned conventional NFC accessory protocols, such as e.g. triggering a single smart device operation based on the identity of NFC accessory <b>100</b> or a normal NFC tag -reading procedure as implemented in conventional Android systems..
0038The proposed enhanced NFC-based smart device control mechanism of <b>310</b> may therefore not interfere with existing NFC-based solutions, such as normal NFC tag reading or the triggering of a single smart device operation based on the identity of a detected NFC accessory. If the detected NFC accessory has been preconfigured for enhanced NFC-based smart device control (such as e.g. by a user, vendor, manufacturer, etc.), the detection and identification of an eligible NFC accessory (i.e. the NFC accessory is an Eligible Tag) may trigger enhanced NFC-based smart device control. Otherwise, default NFC protocols may instead be performed, such as default reading of NFC tag information and any other configured operations.
0039As depicted in <figref idref="f0003">FIG. <b>3</b></figref><b>,</b> method <b>300</b> may be implemented in a repetitive manner. After smart device <b>200</b> has executed the enhanced NFC-based smart device control mechanism in <b>310,</b> method <b>300</b> may return to <i>NFC_Detection_Inactive</i> state in 302.
0040<figref idref="f0004">FIG. <b>4</b></figref> shows method <b>400</b> detailing enhanced NFC-based smart device control according an aspect of the disclosure. As detailed regarding method <b>300,</b> NFC controller 204 of smart device <b>200</b> may detect the presence of an NFC accessory such as NFC accessory <b>100</b> within the NFC field range of smart device <b>200.</b> NFC controller <b>204</b> may identify NFC accessory <b>100</b> based on emitted NFC information, and may then determine whether or not NFC accessory <b>100</b> is an Eligible Tag and should be interacted with according to enhanced NFC-based smart device control protocols, such as in <b>310</b> of method <b>300.</b> As indicated in <figref idref="f0004">FIG. <b>4</b></figref><b>,</b> it is appreciated that method <b>400</b> may be executed as part or all of the enhanced NFC-based smart device control mechanism of <b>310</b> in method <b>300.</b>
0041If NFC accessory <b>100</b> is an Eligible Tag (i.e. as determined in <b>308</b> and <b>310</b> of method <b>300),</b> NFC controller <b>204</b> may proceed according to method <b>400.</b> Smart device <b>200</b> may initiate NFC Tag Presence Loop <b>402</b> via NFC controller <b>204,</b> during which smart device <b>200</b> may continuously monitor whether or not NFC accessory <b>100</b> remains within the NFC field range of smart device <b>200</b> as detected by NFC controller <b>204.</b> NFC Tag Presence Loop <b>402</b> may be implemented at a software level (e.g. a framework layer in an Android operating system), and may have a loop interval configurable in an order of milliseconds, such as e.g. 60, 80, or 125 ms.
0042By monitoring whether NFC accessory <b>100</b> is within NFC field range, NFC Tag Presence Loop <b>402</b> may detect NFC movements based on timing information. Smart device <b>200</b> may record a timestamp each time NFC accessory <b>100</b> either exits or re-enters NFC field range, thereby triggering NFC controller <b>204</b> to be in <i>NFC_Detection_Active</i> state (NFC accessory <b>100</b> within range) or <i>NFC_Detection_Inactive</i> state (NFC accessory <b>100</b> out of range). A series of timestamps associated with <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state may be utilized to represent an NFC movement. The initial timestamp recorded in <b>306</b> of method <b>300</b> may also be utilized as a movement timestamp. NFC controller <b>200</b> may then compare the series of timestamps representing a performed user movement to one or more predefined series of timestamps representing predefined user movements. NFC controller <b>200</b> may then determine whether the series of timestamps matches with one of the predefined series of timestamps, and may perform a predefined action associated with the represented predefined user movement.
0043A user may therefore define NFC movements composed of time periods in which NFC accessory <b>100</b> is within NFC field range of smart device <b>200</b> and in which NFC accessory <b>100</b> is outside of NFC field range, and may assign a specific smart device operation to each NFC movement. A user may then perform the associated movement by moving NFC accessory <b>100</b> into and out of NFC field range of smart device <b>200</b> in a manner that matches to one of the predefined movements in order to trigger an associated operation of smart device <b>200.</b> As numerous different movements can be made with a single NFC accessory, each NFC accessory can be utilized to trigger a plurality of different movements. Unlike conventional NFC-based smart device control, a user may be able to exert greater control over smart device <b>200</b> without the use of conventional buttons.
0044Smart device <b>200</b> may therefore detect an NFC movement in <b>404</b> by recording timestamps in which NFC accessory <b>100</b> moves into NFC field range (triggering <i>NFC_Detection_Active</i> state) and out of NFC field range (triggering <i>NFC_Detection_Inactive</i> state). Smart device <b>200</b> may determine if the NFC movement is recognized based on the recorded timestamps, i.e. if the performed NFC movement matches a preconfigured/preprogrammed NFC movement based on the recorded timestamps. Smart device <b>200</b> may determine if the NFC movement is recognized by comparing the NFC movement to a database of NFC movements, such as stored in smart device memory <b>206</b> of smart device <b>200.</b>
0045It is appreciated that the aforementioned database ofNFC movements may be implemented by smart device <b>200</b> in a variety of alternate manners, such as a waveform database, movement database, time stamp data base, time duration/window database, etc. It is thus appreciated that numerous approaches to compare detected NFC movements to the database of NFC movements may be similarly available and accordingly embraced herein by this disclosure. It is understood that substantially all such movement comparison approaches may involve a certain degree of comparison of timing information, especially a duration of time as manifested by any plurality of points of time, due to the inherent relationship all temporal time waveforms have with time.
0046Smart device <b>200</b> may be configured to recognize NFC movements by comparing timing characteristics of a detected NFC movement to one or more predefined NFC movements. As previously detailed, smart device <b>200</b> may record timestamps, e.g. as performed by core hardware <b>208</b> via one or more software levels based on data provided by NFC controller <b>204,</b> indicated <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state. Smart device <b>200</b> may then compare the recorded timestamps to a database of predefined NFC movements, where each of the predefined NFC movements is also associated with one or more timestamps. Smart device <b>200</b> may calculate a duration of time in which NFC accessory <b>100</b> is within NFC field range (<i>NFC_Detection_Active</i>) or calculate a duration of time in which the NFC accessory <b>100</b> is outside of NFC field range (<i>NFC_Detection_Inactive</i>), such as based on the recorded timestamps, and may then compare the calculated duration of time to durations of time associated with the predefined NFC movements. It is appreciated that such a "duration" as used herein may additionally include comparing two distinct points in time, as a duration in time inherently exists between two such points. Smart device <b>200</b> may therefore determine if the NFC movement is recognized based on the comparison between the detected NFC movement and the predefined NFC movements.
0047Upon detecting an NFC movement and determining a series of timestamps indicating NFC detection state transitions representing the detected NFC movement, smart device <b>200</b> may access smart device memory <b>206,</b> e.g. in the form of core hardware <b>208</b> accessing smart device memory <b>206.</b> NFC device <b>200</b> may obtain timing information associated with one or more predefined NFC movements stored in smart device memory <b>206.</b> For example, the timing information may include a series of timestamps or durations of time periods (such as e.g. in the form of timestamps) corresponding to <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state. Smart device <b>200</b> may then compare the timing information associated with the detected NFC movement to the timing information stored in smart device memory <b>206</b> associated with the one or more predefined NFC movements. Smart device memory <b>206</b> may additionally contain information associating each of the predefined NFC movements with one or more smart device operations. Smart device <b>200</b> may then identify a predefined NFC movement that matches with the detected NFC movement based on the comparison of timing information, and then may perform a smart device action associated with predefined NFC movement.
0048If the NFC movement is not recognized in <b>406,</b> smart device <b>200</b> may ignore the current detected movement and return to <i>NFC_Detection_Inactive,</i> i.e. to <b>302</b> in method <b>300.</b> Alternatively, if the NFC movement is recognized, smart device <b>200</b> may trigger a respective smart device operation. For example, a user may have pre-programmed a smart device operation, such as "return to home screen", "back/previous screen", etc., to match a particular NFC movement. Upon recognizing the particular NFC movement in <b>408,</b> smart device <b>200</b> may trigger the associated smart device operation.
0049Core hardware <b>208</b> may be configured to trigger the associated smart device operation of smart device <b>200.</b> Upon recognizing an NFC movement and identifying a corresponding smart device operation, core hardware <b>208</b> may then perform the proper smart device operation, such as by interacting with one or more further components of smart device <b>200</b> dependent on the requirements of the corresponding smart device operation.. For example, a user may produce an NFC movement matched with a "return to home screen" operation of smart device <b>200.</b> Core hardware <b>208</b> may then perform a "return to home screen operation", i.e. by changing a display screen of smart device <b>200</b> to a home screen, thereby interacting the display screen in order to complete the operation associated with the detected NFC movement. Alternatively, a user may produce an NFC movement matched with a camera operation, such as "take picture". Core hardware <b>208</b> may then perform a "take picture" operation, such as by interacting with a camera of smart device <b>200</b> to take a picture.
0050A variety of different NFC movements may be possible, and may each be defined by a series of timestamps representing times when a proximate NFC accessory entered into NFC field range or exited NFC field range. The series of timestamps indicating <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state, respectively, may be represented as a digital waveform representing an NFC movement. For example, <i>NFC_Detection_Active</i> may represent a high level digital signal in the digital waveform, while <i>NFC_Detection_Inactive</i> may represent a low level digital signal in the digital waveform. Each NFC movement may thus be visually represented with a separate digital waveform composed of high level (<i>NFC_Detection_Active</i>, i.e. NFC accessory within NFC field range) and low level (<i>NFC_Detection_Inactive,</i> i.e. NFC accessory outside of NFC field range) time periods. Each NFC accessory may be associated with any number of separate waveforms, and consequently a number of different operations (e.g. each corresponding to distinct a waveform/movement) may be triggered by each NFC accessory. As the NFC controller <b>204</b> may be capable of detecting a UID for each NFC accessory, NFC movements may be re-used between different NFC accessories, and may be configured to trigger the same or different smart device operations. It is appreciated that such variation may be configured or programmed according to user preference or may be implemented by a manufacturer.
0051As previously detailed, such movements defined by multiple timestamps may be inherently associated with durations, e.g. durations of time representing the time between time stamps. Additionally, it is appreciated that even a single time stamp may entail a duration, as a duration may be determined based on the time following the timestamp, thereby representing the time spent in <i>NFC_Detection_Active</i> or <i>NFC_Detection_Active</i> state following a transition into the state. It is thus understood that related time waveforms are recognized herein as inherently being characterized by at least one duration.
0052<figref idref="f0005">FIG. <b>5</b></figref> illustrates a set of different possible NFC movements <b>M1 - M10</b> represented by respective digital waveforms according to an aspect of the disclosure. It is appreciated that each of the detailed NFC movements may be assigned by a user or manufacturer to a different smart device operation, and accordingly may be able to trigger the associated smart device operation upon detection by an NFC-enabled smart device. NFC movements <b>M1 - M10</b> are exemplary in nature, and it is appreciated that a number of variations or alternate movements are possible.
0053A user may equip NFC accessory <b>100</b> on one of their fingers, e.g. a forefinger, and may naturally position their fingers along the back side of a smart device, thereby positioning NFC accessory <b>100</b> near the back side of a smartphone. As previously detailed, NFC antennas are conventionally located on the back side of a smart device, and NFC accessory <b>100</b> may thus be positioned proximate to the NFC field range.
0054A user may then slide their finger along the back side of a smart device in order to move NFC accessory <b>100</b> within NFC field range (<i>NFC_Detection_Active</i> state) and out of NFC field range (<i>NFC_Detection_Inactive</i> state). The smart device may record then record a timestamp indicating the time in which <i>NFC_Detection_ActivelNFC_Detection_Inactive</i> state was entered/exited, and may create a digital waveform with high level and low level signals corresponding to periods of <i>NFC_Detection_Active</i> state and <i>NFC_Detection_Inactive</i> state, respectively. The smart device may then utilize the resulting digital waveform as an NFC movement, and may attempt to match the resulting digital waveform with one or more pre-defined NFC movements (represented by unique digital waveforms) each associated with a pre-registered smart device operation. Alternative to sliding their finger along the back side of a smart device, a user may bend or straighten their finger equipped with NFC accessory <b>100</b> in order to alternatively bring NFC accessory <b>100</b> further from and closer to the NFC antenna, thereby entering and exiting NFC field range.
0055NFC controller <b>204</b> may thus be configured to provide core hardware <b>208</b> with NFC detection information associated with an NFC accessory, such as an indication from a hardware level as to whether an NFC accessory is detected or not. Core hardware 208 may then be configured to determine a corresponding movement waveform based on the NFC detection information, such as in the form of timestamps or durations, thereby allowing smart device <b>200</b> to determine a detected NFC movement, e.g. in the form of a waveform.
0056Smart device <b>200</b> may then be configured to compare the detected NFC movement with a database ofNFC movements (e.g. as performed on a software layer by core hardware <b>208),</b> such as stored in smart device memory <b>206.</b> Smart device <b>200</b> may be configured to perform this comparison based on timing information, such as timestamps and durations of time between timestamps. If the detected NFC movement matches with an NFC movement stored in the database, and if the NFC movement stored in the database has been previously assigned a smart device operation, smart device <b>200</b> may trigger the assigned smart device operation. For example, core hardware <b>208</b> perform the assigned smart device operation by interacting with any necessary further components of smart device <b>200</b> as required by the corresponding smart device operation.
0057NFC movement <b>M1</b> is illustrated as such a digital waveform consisting of high level and low level signals corresponding to <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state. NFC movement <b>M1</b> is depicted as a "Quick Pulse" (QP), where an NFC accessory such as NFC accessory <b>100</b> enters into NFC field range (<i>NFC_Detection_Active</i> state) and then quickly moves out of NFC field range (<i>NFC_Detection_Inactive</i> state).
0058A user wearing NFC accessory <b>100</b> may thus perform NFC movement <b>M1</b> by initially holding their finger equipped with NFC accessory <b>100</b> in an inactive state, i.e. along the backside of the smart device such that NFC accessory <b>100</b> does not fall within NFC field range (<i>NFC_Detection_Inactive</i> state). The user may then slide their finger along the back side of the smart device such that NFC accessory <b>100</b> falls within the NFC field range (<i>NFC_Detection_Active</i> state) for a short period of time before sliding their finger back outside of the NFC field range, thereby causing NFC accessory <b>100</b> to leave the NFC field range. Alternatively, a user wearing NFC accessory <b>100</b> may initially hold their finger in a bent position such that NFC accessory <b>100</b> is positioned slightly off the back side of the smart device, and is thus outside of NFC field range (<i>NFC_Detection_Active</i> state). The user may then straighten their finger for a short period of time, causing NFC accessory <b>100</b> to become positioned closer to the back of the smart device and thus within NFC field range. The user may then quickly re-bend their finger in order to move NFC accessory <b>100</b> back out of NFC detection range.
0059The illustrated waveform for NFC movement <b>M1</b> is thus depicted as a period <b>502</b> in <i>NFC_Detection_Inactive</i> state (i.e. low level signal) followed by a period <b>504</b> in <i>NFC_Detection_Active</i> state (i.e. high level signal) and subsequently followed by a period <b>506</b> in <i>NFC_Detection_Inactive</i> state (i.e. low level signal). The time duration of period <b>504</b> should be less than a custom defined <i>N<sub>1</sub></i> milliseconds, i.e. <i>t<sub>1</sub> < N<sub>1</sub></i> where <i>t<sub>1</sub></i> is the duration of period <b>504.</b>
0060NFC movement <b>M2</b> is depicted as a "Double Quick Pulse" (DQP), where an NFC accessory performs two consecutive QP movements (each with a period <i>N<sub>1</sub></i> in <i>NFC_Detection_Active</i> state) and the interval <i>t<sub>2</sub></i> between the two consecutive QP movements is less than a custom defined <i>M</i> milliseconds.
0061In addition to depicting the shape of the digital waveform associated with NFC movements <b>M1</b> and <b>M2,</b><figref idref="f0005">FIG. <b>5</b></figref> additionally depicts triggering points <b>520</b> and <b>522.</b> Triggering points <b>520</b> and <b>522</b> indicate the point in time in which smart device <b>200</b> may complete recognition ofNFC movements <b>M1</b> and <b>M2</b> and proceed to trigger an associated smart device operation. Smart device <b>200</b> may be configured to complete recognition of NFC movements <b>M1</b> and <b>M2</b> according to triggering points <b>520</b> and <b>522</b> in order to differentiate between the QP and DQP movements of NFC movements <b>M1</b> and <b>M2.</b> For example, if smart device <b>200</b> is configured to immediately trigger movement <b>M1</b> upon detection of an <i>NFC_Detection_Inactive</i>→<i>NFC_Detection_Active</i> →<i>NFC_Detection_Inactive</i> state sequence where the <i>NFC_Detection_Active</i> state is less than <i>N<sub>1</sub></i> milliseconds, smart device <b>200</b> may mistakenly recognize NFC movement <b>M2</b> as NFC movement <b>M1</b> (and similarly for the NFC movement <b>M3).</b> Accordingly, smart device <b>200</b> may be configured to wait a certain amount of time until triggering points <b>520</b> and <b>522</b> following completion of a QP in order to determine which NFC movement was completed. As shown regarding NFC movement <b>M2,</b> a DQP movement may be recognized upon detection of an <i>NFC_Detection_Inactive</i>→<i>NFC_Detection_Active</i>→ <i>NFC_Detection_Inactive</i>→<i>NFC_Detection_Active</i> →<i>NFC_Detection_Inactive</i> state sequence, where the second <i>NFC_Detection_Inactive</i> period is less than <i>M</i> milliseconds. Accordingly, smart device <b>200</b> may be configured to wait at least M milliseconds following detection of a QP movement in order to determine that the most recent QP movement is the final QP movement of the current NFC movement. In this manner, NFC controller <b>204</b> may ensure that all desired QP movements are detected (assuming the user has correctly performed the QP movements according to the timing constraints <i>N<sub>1</sub></i> and <i>M</i>) and avoid prematurely triggering recognition of a QP-based NFC movement before a user has finished performing the full NFC movement.
0062NFC movement <b>M3</b> is depicted as a "Triple Quick Pulse" (TQP), where an NFC accessory does three consecutive QP movements and the interval <i>t<sub>2</sub></i> is less than a custom defined <i>M</i> milliseconds. As shown in <figref idref="f0005">FIG. <b>5</b></figref><b>,</b> triggering point <b>524</b> for NFC movement <b>M3</b> is temporally located at the exact point in time where the third QP in the triple QP sequence is completed. As the provided set of NFC movements have a maximum of three QPs (for TQP), it may be possible to recognize three quick pulses as NFC movement <b>M3</b> immediately after the third QP is complete, as there is no defined NFC movement consisting of four QPs that could potentially be mistakenly recognized as NFC movement <b>M3.</b> Accordingly, trigger point <b>524</b> may need to be adjusted if NFC movements are utilized that consist of three or more QPs.
0063NFC movement <b>M4</b> is depicted as a "Normal Pulse" (NP), where an NFC accessory enters into NFC field range and then moves out of NFC field range and the duration of the <i>NFC_Detection_Active</i> state (i.e. time spent within NFC field range) is greater than the custom defined <i>N<sub>1</sub></i> value and less than a custom defined <i>N<sub>2</sub></i> value.
0064NFC movement <b>M5</b> is depicted as "Turn Active" (TA), where an NFC accessory enters into NFC field range (<i>NFC_Detection_Active</i> state) and remains in <i>NFC_Detection_Active</i> state for more than <i>N<sub>2</sub></i> milliseconds.
0065Smart device <b>200</b> may therefore detect NFC movements and determine whether or not the NFC movement is recognized. If the NFC movement is recognized and has been associated with a smart device operation, the respective operation is then triggered, such as by signaling between NFC controller <b>204</b> and core hardware <b>208.</b>
0066NFC movements <b>M1 - M5</b> may be utilized if the "Idle State" of a user wearing an NFC accessory is <i>NFC_Detection_Inactive.</i> In other words, if a user naturally holds a smart device in their hand and the NFC accessory is not within NFC field range, the Idle State is defined as <i>NFC_Detection_Inactive.</i> In contrast, if a user naturally holds a smart device in their hand and the NFC accessory is within NFC field range, the Idle State is defined as <i>NFC_Detection_Active.</i> Accordingly, a user with Idle State as <i>NFC_Detection_Inactive</i> may naturally position an NFC accessory in <i>NFC_Detection_Inactive</i> state, and may perform one of NFC movements <b>M1</b> - <b>M5</b> starting from <i>NFC_Detection_Inactive</i> state (i.e. as in period <b>502).</b> It is appreciated that method <b>300</b> as detailed regarding <figref idref="f0003">FIG. <b>3</b></figref> and method <b>800</b> to be detailed regarding <figref idref="f0008">FIG. <b>8</b></figref> may be similarly adapted to initiate from <i>NFC_Detection_Active</i> state as opposed to <i>NFC_Detection_Inactive</i> to correspond with a potential user having Idle State as <i>NFC_Detection_Active</i> state.
0067A user with Idle State as <i>NFC_Detection_Active</i> state may therefore wish to perform NFC movements starting from an initial <i>NFC_Detection_Active</i> state. Accordingly, NFC movements <b>M6 - M10</b> represent the exclusive OR (XOR) logical operation of movements <b>M1</b> - <b>M5,</b> and correspondingly may be initiated from an <i>NFC_Detection_Active</i> state as in period <b>508.</b> The initial <i>NFC_Detection_Active</i> state in period <b>508</b> may be followed by e.g. at least one <i>NFC_Detection_Inactive</i> state in period <b>510</b> and a further <i>NFC_Detection_Active</i> state in period <b>512.</b>
0068NFC movements <b>M6 - M10</b> represent the exclusive OR (XOR) signal of NFC movements <b>M1 - M5,</b> and may be utilized dependent on the "Idle" NFC detection state of a user wearing an NFC accessory. It is additionally appreciated that while many of the implementations detailed herein relate to users with and <i>NFC_Detection_Active</i> Idle State, the operations may be inversed (such as done regarding NFC movements <b>M6 - M10)</b> to operate according to a user with an <i>NFC_Detection_Inactive</i> Idle State.
0069Although NFC movements <b>M1 - M10</b> have been depicted as either containing one of QP movements, NP movements, or TA movements, it is appreciated that other different movements may be utilized to define NFC movements, such as e.g. one or more QP movements may be combined with one or more NP movements in addition to at least one TA movement in order to define numerous other NFC movements. The provided NFC movements are exemplary in nature, and not intended to be limiting in any respect to a possible set of NFC movements.
0070As previously detailed, smart device <b>200</b> may be configured to record timestamps indicating when NFC accessory <b>100</b> enters NFC field range and exits NFC field range, and may be configured to recognize an associated NFC movement based on the recorded timestamps. Smart device <b>200</b> may be configured to calculate one or more durations of time during which smart device <b>200</b> is in <i>NFC_Detection_Active</i> state or in <i>NFC_Detection_Inactive</i> state (e.g. on a software level as executed by core hardware <b>208),</b> such as by comparing the differences between timestamps indicating an entry into <i>NFC_Detection_Active</i> state and subsequent exit therefrom. Smart device <b>200</b> may calculate one or more such durations, such as duration <i>t<sub>1</sub></i> for NFC movement <b>M1</b> (corresponding to the duration of time in <i>NFC_Detection_Active</i> state for a QP movement), durations <i>t<sub>1</sub></i> and <i>t<sub>2</sub></i> for NFC movement <b>M2</b> (corresponding to the two durations of time in <i>NFC_Detection_Active</i> state for the two QP movements), durations <i>t<sub>1</sub></i> and <i>t<sub>2</sub></i> for NFC movement <b>M3,</b> etc.
0071Smart device <b>200</b> may then compare the calculated durations <i>t<sub>1</sub></i> and/or <i>t<sub>2</sub></i> to one or more duration thresholds, such as <i>N<sub>1</sub></i>, <i>N<sub>2</sub></i>, and <i>M,</i> and may trigger an associated smart device operation based thereon. For example, in order to detect NFC movement <b>M1,</b> smart device <b>200</b> may record timestamps corresponding to state transitions from <i>NFC_Detection_Inactive</i> → <i>NFC_Detection_Active</i> → <i>NFC_Detection_Inactive.</i> Smart device <b>200</b> may then compare the duration of time in <i>NFC_Detection_Active</i> state <i>t<sub>1</sub></i> to <i>N<sub>1</sub></i> and <i>N<sub>2</sub></i> to determine whether <i>t<sub>1</sub></i> < <i>N<sub>1</sub></i>, <i>N<sub>1</sub></i><<i>t<sub>1</sub></i><<i>N<sub>2</sub></i>, or <i>t<sub>1</sub></i>≥<i>N<sub>2</sub></i>. If <i>t<sub>1</sub></i> < <i>N<sub>1</sub></i>, smart device <b>200</b> may determine that a QP movement has been performed, which may correspond to any of NFC movement <b>M1</b> - <b>M3</b> has been performed as shown in <figref idref="f0005">FIG. 5</figref>. As will be later detailed, smart device <b>200</b> may be configured to distinguish between NFC movements <b>M1 - M3</b> using triggering points. In the current exemplary scenario, smart device <b>200</b> may determine that NFC movement <b>M1</b> has been performed, such as through the use of triggering points, and may subsequently trigger a predefined operation corresponding to NFC movement <b>M1</b> (such as pre-programmed by a user). Alternatively, smart device <b>200</b> may determine that <i>N<sub>1</sub></i> < <i>t<sub>1</sub></i> < <i>N<sub>2</sub></i>, and thus an NP movement corresponding to NFC movement <b>M4</b> has been performed. Smart device <b>200</b> may alternatively determine that <i>t<sub>1</sub></i> ≥ <i>N<sub>2</sub></i>, in which case a TA movement corresponding to <b>M5</b> has been performed. Smart device <b>200</b> may therefore utilized recorded timestamps in order to determine the appropriate duration in a particular state, such as the duration of <i>t<sub>1</sub></i> in which smart device <b>200</b> is in <i>NFC_Detection_Active</i> state in the aforementioned examples, and compare the determined duration to one or more thresholds or other timing measures in order to identify which NFC movement has been performed.
0072Smart device <b>200</b> may also be configured to compare durations of time in order to implement triggering points, such as triggering points <b>520</b> and <b>522</b> as shown in <figref idref="f0005">FIG. <b>5</b></figref><b>.</b> As previously indicated, smart device <b>200</b> may employ triggering points in order to distinguish between certain NFC movements, such as the NFC movements <b>M1</b> - <b>M3</b> as shown in <figref idref="f0005">FIG. <b>5</b></figref><b>.</b> For example, smart device <b>200</b> may be configured to calculate the duration of time that has passed since the last state change. In reference to NFC movement <b>M1</b>, after identifying the duration of period <i><b>504</b> t<sub>1</sub></i> as consistent with a QP movement, smart device <b>200</b> may determine how much time has passed in period <b>506</b> since the transition from <i>NFC_Detection_Active</i> state to <i>NFC_Detection_Inactive</i> state. If the duration of time exceeds <i>M</i>, smart device <b>200</b> may recognize that the performed movement qualifies as NFC movement <b>M1</b> (as the user did not perform a second QP within M milliseconds), and proceed to trigger any corresponding smart device operation. Smart device <b>200</b> may be required to operate similarly to recognize e.g. NFC movement <b>M2,</b> as smart device <b>200</b> may need to determine that the second QP movement was performed within M milliseconds of the first QP movement. Accordingly, the NFC movement being performed should be interpreted as an NFC movement <b>M2</b> or <b>M3</b> instead of a series of separate NFC movements <b>M1</b>.
0073Smart device <b>200</b> may utilize a waveform database containing timing information regarding each stored movement to compare a performed movement (i.e. an NFC movement performed by a user with an NFC accessory) to one or more predefined movements. Smart device <b>200</b> may determine corresponding timing information corresponding to a performed movement, and compare the timing information corresponding to a performed movement to timing information stored in the database. For example, smart device <b>200</b> may compare timing information corresponding to a performed movement to timing information for each movement stored in the database in order to determine if the timing information corresponding to the performed movement matches timing information for any of the movements stored in the database. Timing information may be based on timestamps, where the timestamps indicate a transition between <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state, and may be in the form of timestamps and/or duration information indicating time periods between successive timestamps.
0074Such duration-based comparisons may be based on the timestamps recording indicating state transitions between <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state. Smart device <b>200</b> may thus calculate durations from the recorded timestamps, and utilize the calculated durations in order to recognize different NFC movements.
0075<figref idref="f0006">FIG. 6</figref> illustrates scenarios <b>600 - 606.</b> Scenarios <b>600 - 606</b> depict examples of NFC accessory positioning in relation to NFC detection state and the position of NFC field range of smart device <b>200.</b> In scenario <b>600</b> and <b>602,</b> a user is depicted as wearing NFC accessory <b>100</b> on their forefinger. The user may position NFC accessory <b>100</b> on the back of smart device <b>200,</b> and may perform the requisite movements to trigger <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state by moving their finger along the backside of smart device <b>200</b> into and out of the NFC field range. The user may naturally hold their finger equipped with NFC accessory <b>100</b> in location <b>610.</b> As shown in scenario <b>600,</b> the NFC field range (shaded area) of smart device <b>200</b> is positioned in the top region of the profile of smart device <b>200.</b> Accordingly, the user's Idle State is <i>NFC_Detection_Inactive.</i> The user may trigger smart device operations according to the enhanced NFC-based smart device control protocols by moving NFC accessory <b>100</b> into the NFC field range in scenario <b>600.</b> For example, the user may slide their forefinger equipped with NFC accessory <b>100</b> to location <b>612,</b> which is located within the NFC field range. The user may then create different waveforms by moving their forefinger into the NFC field range and out of the NFC field range, thereby creating a waveform of high and low level signals representing <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> states. By performing preconfigured NFC movements, such as movements <b>M1</b> - <b>M5</b> (as the user's Idle State is <i>NFC_Detection_Inactive</i>), a user may trigger a variety of different smart device operations using NFC accessory <b>100.</b>
0076In scenario <b>602,</b> the NFC field range of smart device <b>200</b> may be located in the bottom region of the profile of smart device <b>200.</b> It is appreciated that the NFC field range of a smart device may be dependent on factors such as the position of the NFC antenna and additional profile characteristics of the smart device. Conventionally, NFC antennas are built close to the back of a smart device, and the NFC field range is typically limited to an area at the back of a smartphone. Additionally, the user may rotate their finger so NFC inlay <b>120</b> is pointing towards or sideways to the NFC filed of smart device <b>200</b> as detailed regarding <figref idref="f0001">FIG. <b>1</b></figref> in order to adjust the detection sensitivity of NFC accessory <b>100</b> by smart device <b>200.</b>
0077As depicted in scenario <b>602,</b> the user may naturally hold their forefinger equipped with NFC accessory <b>100</b> near the back of smart device <b>200</b> in location <b>612.</b> Accordingly, the user's natural positioning of NFC accessory <b>100</b> may fall outside the NFC field range of smart device <b>200.</b> The user's Idle State is therefore <i>NFC_Detection_Inactive</i> state, and the user may thus utilize movements <b>M1</b> - <b>M5</b> to trigger smart device operations by moving their finger into NFC field range (<i>NFC_Detection_Inactive</i>) and out of NFC field range, such as to location <b>610</b> (<i>NFC_Detection_Active</i>).
0078Scenario <b>604</b> illustrates an alternative example in which a user naturally bends their finger equipped with NFC accessory <b>100,</b> which is located at location <b>614.</b> As the user's bent finger equipped with NFC accessory <b>100</b> is slightly displaced from the back of smart device <b>200,</b> NFC accessory <b>100</b> may fall outside of the NFC field range. Accordingly, the user's Idle State may be <i>NFC_Detection_Inactive</i>. The user may thus perform NFC movements by straightening and re-bending their finger, thereby moving NFC accessory <b>100</b> closer to and further from the back of smart device <b>200</b> and correspondingly triggering <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state. For example, the user may straighten their finger equipped with NFC accessory <b>100</b> to move NFC accessory <b>100</b> into location <b>616,</b> which may be proximate to the back of smart device <b>200</b> and consequently within NFC field range.
0079Alternatively, a user may naturally position their finger equipped with NFC accessory <b>100</b> in a straightened (i.e. un-bent) position as shown in scenario <b>606.</b> Accordingly, the user may naturally position NFC accessory <b>100</b> in location <b>616,</b> which is located within the NFC field range of smart device <b>200.</b> The user's Idle State may thus be <i>NFC_Detection_Active</i> state. The user may then bend and straighten (i.e. un-bend) their finger equipped with NFC accessory <b>100</b> in order to move NFC accessory <b>100</b> into the NFC field range and out of the NFC field range in order to perform one of e.g. NFC movements <b>M6 - M10</b> (as the user's Idle State is <i>NFC_Detection_Active</i>).
0080Alternatively, a manufacturer or user may be able to configure (e.g. via an Application Program Interface) the NFC field strength or other NFC related parameters to adjust the detection sensitivity of NFC accessory <b>100</b> by smart device <b>200.</b>
0081It is appreciated that implementations related to this disclosure are not limited to the movements and scenarios as detailed herein, and it is thus understood that the implementations detailed herein are exemplary in nature. It is appreciated that the NFC movements <b>M1 - M10,</b> in particular NFC movements <b>M1 - M4</b> and <b>M6 - M9</b> may be completed by a user in relatively short duration, e.g. several hundreds of milliseconds, before triggering a smartphone operation. Accordingly, users may not experience noticeable latency when triggering smart phone operations with the proposed NFC movements. The enhanced NFC-based smart device control mechanisms provided herein may be executed quickly compared to traditional button presses, and may additionally provide further simplicity due to the eliminated requirement to physically reach each smart device button.
0082The movement criteria associated with each NFC movement, such as recorded timestamps and the resulting timing durations <i>N<sub>1</sub></i>, <i>N<sub>2</sub></i>, and <i>M,</i> may be configured based on a user's preference. In addition, further waveforms represented by alternating high level (<i>NFC_Detection_Active</i>) and low level (<i>NFC_Detection_Inactive</i>) may be defined by a user, thereby allowing a user to the option to freely define the mappings of finger movements and associate any desired smart device operations therewith. The NFC movements may be defined according to a user's preference. The NFC movements may also be based on "fuzzy logic", which does not require a user to exactly match a performed finger movement to a registered NFC movement in order to trigger an associated smart device operation. Smart device <b>200</b> may be configured to recognize the defined movements using fuzzy logic, and the user may thus not be required to move the finger to identically match a particular movement or stay in place (i.e. within NFC field range or out ofNFC field range) for exactly a certain amount of time to trigger an operation. A user may therefore be provided with a greater ease of use and improved user experience.
0083Furthermore, an NFC Detection State Indicator may be implemented on a smart device, such as on a status bar on a virtual display or as a physical light indicator. The NFC Detection State Indicator may then be used to visually indicate the current NFC detection state (<i>NFC_Detection_Active</i> or <i>NFC_Detection_Inactive</i>) based on the current positioning of an eligible NFC accessory. Such an instantaneous display of NFC detection state may assist in keeping a user aware of the varying NFC detection states in real time, and may assist in allowing a user to perform more accurate movements to trigger expected operations.
0084Additionally, a user or manufacturer may be able to custom-define different movements, which may accordingly not be limited to the provided NFC movements <b>M1</b> - <b>M10.</b> A user may therefore be provided with a smart device application to record specific movements, such as by recording a waveform representing varying NFC detection states. The recorded NFC movement may then be defined and stored according to the associated timing information, such as timestamps indicating NFC detection state transitions between <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive.</i> After recording and approving an NFC movement, a user may be able to assign a specific smart device operation to the movement, thereby allowing the user an increased level of customization.
0085Each of the defined NFC movements may be utilized to trigger different actions depending on the current status of smart device <b>200.</b> For example, a specific movement may be assigned to trigger a "back/previous screen" if smart device <b>200</b> is virtually displaying a first virtual menu or at system level, and may be also assigned to trigger "start/stop playback" if smart device <b>200</b> is providing multimedia, such as in a steam play application. Other similar options include taking a picture when a camera application is on and locking the screen when smart device <b>200</b> is at the home screen. Such configuration options may be made available to a user for increased customization.
0086In the exemplary aspects of the disclosure detailed above, smart device operations are triggered based on NFC movements defined by NFC detection state waveforms. NFC movements must therefore be identified by a smart device (such as by smart device <b>200</b> via a software layer) before a smart device operation is triggered. In an alternative implementation, operations of a smart device may be triggered immediately based on the current NFC detection state, and consequently no movements need to be recognized before triggering an operation.
0087For example, a user may be performing text editing using a soft keyboard (i.e. virtual) on smart device <b>200,</b> such as in a text message. Smart device <b>200</b> may detect NFC accessory <b>100</b> within NFC field range (<i>NFC_Detection_Active</i> state), and may shift to capital letter entry for text editing. Smart device <b>200</b> may then shift back to lowercase letter entry if smart device <b>200</b> enters back into <i>NFC_Detection_Inactive</i> state.
0088In another example, smart device <b>200</b> may trigger a "scroll down" operation when <i>NFC_Detection_Active</i> state is triggered and smart device <b>200</b> is in a page-view interface, such as e.g. displaying a webpage. Alternatively, smart device <b>200</b> may stop scrolling upon triggering of <i>NFC_Detection_Inactive</i> state.
0089In a further example, NFC accessory <b>100</b> may be used to copy and paste data between two separate smart devices. In contrast to the default "copy/paste" operation, which is only available in one smart device through "clipboard" functionality, the proposed enhanced NFC-based copy/paste operation may enable interoperation between two NFC-enabled smart devices. For example, if an NFC accessory such as NFC accessory <b>100</b> is detected (i.e. <i>NFC_Detection_Active</i> state) and a "copy" command (i.e. via an edit menu or "Ctrl + C") is triggered, the selected text may be written into NFC accessory <b>100,</b> such as e.g. by NFC signaling through NFC antenna <b>202</b> controlled by NFC controller <b>204.</b> The selected text may be written as an NDEF message in NFC accessory <b>100</b> instead of being simply copied onto the local clipboard of smart device <b>200.</b> If NFC accessory <b>100</b> is then detected by another NFC-enabled smart device and a "paste" command is triggered, the text previously copied onto NFC accessory <b>100</b> may be read from NFC accessory <b>100</b> (such as from the NDEF message of NFC accessory <b>100)</b> by the other NFC-enabled smart device and pasted into the selected area.
0090The operations detailed above may thus be classified as "operation modes", and may be predefined, such as e.g. by a user or manufacturer. Smart device <b>200</b> may thus be configured to switch between operation modes, such as a first operation mode and a second operation mode, based on the detection state of smart device <b>200.</b> For example, a user may be able to configure smart device <b>200</b> to operate with uppercase text entry as a first operation mode and with lowercase text entry as a second operation mode. The user may then configured the first operation mode to be associated with <i>NFC_Detection_Active</i> state and the second operation mode to be associated with <i>NFC_Detection_Inactive</i> state, where the user's Idle State is <i>NFC_Detection_Inactive.</i>
0091Smart device <b>200</b> may then switch between uppercase and lower text entry corresponding to the first operation mode and the second operation mode depending on the current detection state of smart device <b>200.</b> It is appreciated that the above example is exemplary in nature, and may be configurable in various additional manners, such as depending on desired operation modes and/or the user's Idle State.
0092Furthermore, smart device <b>200</b> may be configured to operate according to such operation modes based on context information, such as the action a user is currently performing on smart device <b>200.</b> For example, smart device <b>200</b> may be configured to have uppercase text entry as a first operation mode, lowercase text entry as a second operation mode, scroll down as a third operation mode, and no scroll as a fourth operation mode.
0093If a user is operating a text-entry application, such as a text messaging or other word-processing application, smart device <b>200</b> may be configured to operate in either the first operation mode or the second operation mode (e.g. corresponding to text entry) depending on the detection state of smart device <b>200.</b> If the user is not operating a text entry application and is e.g. utilizing an application that supports scrolling such as a web page browser or mobile reader, smart device <b>200</b> may be configured to operate in either the third operation mode or fourth operation mode (i.e. scroll-down or no scroll) depending on the detection state of smart device <b>200.</b> It is appreciated that many further variations are possible and embraced herein by this disclosure.
0094As detailed regarding <figref idref="f0003">FIG. <b>3</b></figref><b>,</b> an important feature of the proposed enhanced NFC-based smart device control is that there is no impact on current standard NFC functionality and operations. When a smart device such as smart device <b>200</b> implementing enhanced NFC-based smart device control first detects an NFC accessory, smart device <b>200</b> initially reads information specific to the NFC accessory. The information may include a UID, block data, NDEF message, etc., and may be stored in a memory or storage device as part of an NFC inlay. Smart device <b>200</b> may be configured to decide which information should be read to perform proper identification of the NFC accessory, and may complete the reading operation in several milliseconds. Based on the read information, smart device <b>200</b> may then render a decision as to whether the NFC accessory is an Eligible Tag (i.e. the NFC accessory been pre-registered to interact with smart device <b>200</b> according to enhanced NFC-based smart device control protocols) or is alternatively a "normal" tag (i.e. the NFC accessory has not been pre-configured and should be interacted with according to default NFC procedures).
0095Smart device <b>200</b> may be provided with an Eligible Tag Information Table (RTIT) that contains information regarding Eligible Tags (i.e. eligible NFC accessories), such as UIDs, block data, and NDEF messages associated with Eligible Tags. The RTIT may be open to customization to a user, and accordingly may allow a user to add or remove identification information associated with specific NFC accessories in order to configured desired NFC accessories for use with enhanced NFC-based smart device control.
0096Smart device <b>200</b> may customize which information provided by a detected NFC accessory to read. Once smart device <b>200</b> detects an NFC accessory, smart device <b>200</b> may read the appropriate identification information and perform a comparison with the information in the RTIT to determine whether the NFC accessory is an Eligible Tag (i.e. as done in <b>308</b> of method <b>300).</b> If the information read from the NFC accessory matches information in the RTIT, the NFC accessory is considered as an Eligible Tag and may accordingly be used as a controller for enhanced NFC-based smart device control, such as detailed regarding method <b>400</b> of <figref idref="f0004">FIG. <b>4</b></figref><b>.</b> The NFC accessory may be either used for movement recognition-based control (recognition of predefined NFC movements) or state-based control (immediate triggering of a predefined operation based on NFC detection state). Accordingly, the default NFC tag reading procedure may be ignored.
0097Alternatively, if the information read from the NFC accessory does not match any identification information in the RTIT, smart device <b>200</b> may treat the NFC accessory as a normal NFC tag (i.e. not an Eligible Tag). Smart device <b>200</b> may then proceed with default NFC operations.
0098The implementation of the identification scenarios may be deployed at an upper software layer, such as the Framework layer in an Android Operating System, and may be physically executed by e.g. a processor. The implementation of the identification scenarios at an upper layer may avoid any impact on the current NFC tag reading procedures.
0099A user may add the UID unique to an NFC accessory to the RTIT in order to register the NFC accessory as an Eligible Tag. Additionally, a user may also custom-define a specific type of data stored in an NFC accessory (e.g. eligible NFC block data , eligible NDEF message, etc.) and update the data to both the RTIT and the normal tag.
0100Smart device <b>200</b> may additionally be provided with an active-delay based mechanism to enhance the robustness of the ability of smart device <b>200</b> to correctly recognize NFC movements. In reference to <figref idref="f0004">FIG. <b>4</b></figref><b>,</b> smart device <b>200</b> may implement an NFC Tag Presence Loop via NFC controller <b>204,</b> which may perform a check every <i>X</i> milliseconds as to whether an NFC accessory such as NFC accessory <b>100</b> remains within NFC field range. The NFC Tag Presence Loop may thus be utilized in order to detect when a previously detected NFC accessory exits the NFC field range. Smart device <b>200</b> may record a series of timestamps signifying <i>NFC_Detection_Active</i> and <i>NFC_Detection_Inactive</i> state based on whether the NFC Tag Presence Loop determines that the NFC accessory has entered or exited the NFC field range.
0101However, the NFC Tag Presence loop may be prone to false results, such as where the NFC Tag Presence Loop mistakenly signals a "Tag Not Present" (i.e. indicating that the NFC accessory is no longer within NFC field range) when the NFC accessory has remained in the NFC field range. Smart device <b>200</b> may therefore incorrectly record a timestamp signaling <i>NFC_Detection_Inactive</i> state, which may prevent a desired user NFC movement from being properly recognized due to the incorrect timestamp. A potential cause for a mistaken "Tag Not Present" result is extremely rapid movement of the NFC accessory within the NFC field range. Such rapid movement may mistakenly cause NFC controller <b>204</b> to fail to determine that the NFC accessory remains within NFC field range. However, the NFC accessory may be rapidly re-detected by the Card Detection Loop <b>(304</b> in method <b>300)</b> implemented in Firmware level. Smart device <b>200</b> may record the associated timestamps (recorded at the "Tag Not Present" result time of NFC Tag Presence Loop and at the re-detection by Card Detection Loop) as a series of <i>NFC_Detection_Active</i> and <i>NFC_Detection_Active</i> states similar to a QP movement. However, the user has in actuality not performed any such QP movement, and NFC controller <b>204</b> may then mistakenly recognize or fail to recognize an NFC movement performed by the user.
0102In order to prevent such mistaken "Tag Not Present" results from NFC Tag Presence Loop, smart device <b>200</b> may implement an active-delay mechanism. Once smart device <b>200</b> enters <i>NFC_Detection_Active</i> state (following initial detection of an NFC accessory), if the NFC accessory is detected or re-detected either by the Card Detection Loop (e.g. at firmware level) or if the NFC Tag Presence Loop returns a "Tag Present" result (e.g. at software level) at a time <i>timestamp<sub>i</sub></i>, smart device <b>200</b> may forcibly extend <i>NFC_Detection_Active</i> state for a period of time <i>t</i> following <i>timestamp<sub>i</sub></i>. The parameter <i>t</i> may be customized in a custom manner, such set to any value <i>t</i> = <i>k*X</i>, <i>where X</i> is the loop duration of the NFC Presence Tag Loop and <i>k</i> = 2, 3, etc. This process may recursively repeat, causing smart device <b>200</b> to remain in <i>NFC_Detection_Active</i> state for a period of time <i>t</i> following the most recent detection by the Card Detection Loop or "Tag Present" result from the NFC Presence Tag Loop, even if the NFC Presence Tag Loop returns a "Tag Not Present" result during the period of time <i>t</i>. However, if all of the NFC Presence Tag Loop results during the period of time <i>t</i> are "Tag Not Present" and the NFC accessory is not re-detected by the Card Detection Loop, NFC controller <b>204</b> may then consider that the NFC accessory has exited the NFC field range. NFC controller <b>204</b> may then enter <i>NFC_Detection_Inactive</i> state.
0103<figref idref="f0007">FIG. 7</figref> illustrates a scenario in which smart device <b>200</b> may implement the active-delay mechanism with parameter <i>k</i> = 3. Waveform <b>700</b> depicts whether the NFC accessory is physically within NFC field range (high level signal) or is physically outside of NFC field range (low level signal). Waveform <b>702</b> depicts the NFC detection state of smart device <b>200</b> before applying the active delay mechanism. As shown in waveform <b>702,</b> NFC Tag Presence Loop may mistakenly return incorrect "Tag Not Present" results, which are shown at <i>t</i> = 2 and <i>t</i> = 12. However, the Card Detection Loop may quickly re-detect the presence of the NFC accessory, as the NFC accessory has not physically exited the NFC field range (as indicated by waveform <b>700).</b> Accordingly, waveform <b>704</b> depicts the NFC detection state of smart device <b>200</b> after applying active-delay mechanisms. As the presence of the NFC accessory is quickly re-detected by the Card Detection Loop within <i>t</i> = <i>3X</i> milliseconds, smart device <b>200</b> remains in <i>NFC_Detection_Active</i> state and does not immediately fall back to <i>NFC_Detection_Inactive</i> state upon return of a "Tag Not Present" result by the NFC Tag Presence Loop.
0104In other words, smart device <b>200</b> will remain in <i>NFC_Detection_Active</i> state unless the NFC Tag Presence Loop indicates that the NFC accessory is not within NFC field range for a period of <i>t</i> = <i>3X</i> milliseconds following detection of the NFC accessory by either loop. Accordingly, smart device <b>200</b> delays <i>NFC_Detection_Active</i> state for a period of time (<i>k</i>-1)*<i>X</i> milliseconds before falling to <i>NFC_Detection_Inactive</i> state. Incorrect premature triggering of <i>NFC_Detection_Inactive</i> state may thus be avoided through the implementation of the active-delay mechanism. In the event that the NFC accessory is determined to have exited the NFC field range, the timestamp associated with the initial "Tag Not Present" result may be utilized by smart device <b>200</b> to define the recorded NFC movement. The custom-defined movement criteria related to NFC movements <b>M1</b> - <b>M10,</b> such as <i>N<sub>1</sub></i>, <i>N<sub>2</sub></i>, etc., may be also adjusted accordingly. It is appreciated that the active-delay mechanism may also be applied to the non-movement based operation triggering, such as toggling uppercase text entry or scrolling up/down a displayed page.
0105<figref idref="f0008">FIG. <b>8</b></figref> illustrates an exemplary method <b>800</b> for enabling smart device <b>200</b> to detect an NFC accessory such as NFC accessory <b>100</b> using the active-delay mechanism. In <b>802,</b> method <b>800</b> may begin in <i>NFC_Detection_Inactive</i> state, where no NFC accessory is detected within the NFC field range. Smart device <b>200</b> may be in an "NFC polling mode" and have an NFC Card Detection Loop enabled. In <b>804,</b> NFC controller <b>204</b> may detect an NFC accessory, such as on a firmware level by the NFC Card Detection Loop. Smart device <b>200</b> may subsequently enter <i>NFC_Detection_Active</i> state, such as on a software level within core hardware <b>208,</b> and may record a timestamp indicating the initiation of <i>NFC_Detection_Active</i> state in <b>806.</b> NFC controller may then determine if the detected NFC accessory is an Eligible Tag in <b>808,</b> such as by performing a read operation of information stored on the NFC accessory and comparing the read information to a database containing identification information for Eligible Tags. If the NFC accessory is not an Eligible Tag, method <b>800</b> may proceed to <b>812</b> to perform default NFC accessory procedures. If the NFC accessory is an Eligible Tag, method <b>800</b> may apply an active-delay mechanism in <b>810.</b> As smart device <b>200</b> entered into <i>NFC_Detection_Active</i> state in <b>806,</b> the active-delay mechanism may involve extending <i>NFC_Detection_Active</i> state until the NFC Tag Presence Loop signal that the NFC accessory is not within NFC field range for at least a pre-defined duration (e.g. <i>t</i> = <i>k*X</i> milliseconds). Method <b>800</b> may then utilize the active delay mechanism to proceed to enhanced NFC-based smart device control in <b>814</b> in order to detect user NFC movements, thereby enabling smart device control. As further depicted in <figref idref="f0008">FIG. <b>8</b></figref><b>,</b> method <b>800</b> may be implemented in a repetitive manner, and may return to <i>NFC_Detection_Inactive</i> state in <b>802</b> after executing the enhanced NFC-based smart device control mechanism in <b>814.</b>
0106<figref idref="f0009">FIG. <b>9</b></figref> shows a flow diagram illustrating method <b>900</b> for controlling a smart device. Method <b>900</b> may change a detection state of the smart device from a first detection state to a second detection state based on whether a near field communication antenna of the smart device detects an external near field communication device in <b>910.</b> In <b>920,</b> method <b>900</b> may determine a duration of a first time period during which the smart device remains in the second detection state. Method <b>900</b> may then trigger a predefined action of the smart device based on at least the duration of the first time period in <b>930.</b>
0107<figref idref="f0010">FIG. <b>10</b></figref> shows a flow diagram illustrating method <b>1000</b> for controlling a smart device. In <b>1010,</b> method <b>1000</b> may detect a transition in detection state of the smart device from a first detection state to a second detection state, wherein the detection state of the smart device is based on whether a near field communication antenna of the smart device detects an external near field communication device. Method <b>1000</b> may then control the smart device to operate according to a first operation mode during a first time period before the transition in which the smart device remains in the first detection state in <b>1020.</b> Method <b>1000</b> may control the smart device to operate according to a second operation mode during a second time period after the transition once the smart device transitions from the first detection state to the second detection state in <b>1030.</b>
0108<figref idref="f0011">FIG. <b>11</b></figref> shows a block diagram illustrating exemplary internal components of core hardware <b>208</b> of <figref idref="f0002">FIG. <b>2</b></figref><b>.</b>
0109As shown in <figref idref="f0011">FIG. <b>11</b></figref><b>,</b> core hardware <b>208</b> may include monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108.</b> Monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> may each be configured to implement features of the smart device control process detailed above, in particular the enhanced NFC-based smart device control detailed regarding <figref idref="f0003 f0004 f0005 f0006 f0007 f0008">FIGS. <b>3</b> - <b>8</b></figref>.
0110In an exemplary aspect of the disclosure, core hardware <b>208</b> may be provided as an internal component of a smart device, such as detailed regarding smart device <b>200</b> in <figref idref="f0002">FIG. <b>2</b></figref><b>.</b> In this exemplary aspect of the disclosure, smart device <b>200</b> may include an antenna such as antenna <b>202</b> configured to detect an external near field communication device. Monitor <b>1102</b> may be configured to monitor a series of one or more transitions in a detection state of smart device <b>200</b> between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device.
0111Comparator <b>1104</b> may be configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions.
0112Trigger <b>1106</b> may be configured to initiate a predefined action of smart device <b>200</b> based on the comparison.
0113Identifier <b>1108</b> may be configured to determine identification information of the external near field communication device.
0114Accordingly, monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger 1108 may be configured to perform one or more features of core hardware <b>208.</b> It is appreciated that one or more of the features and/or functionality of monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> may e.g. be combined into a single component, or may e.g. all be integrated to form a single component, such as core hardware <b>208.</b>
0115Monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> may be implemented as hardware, software, or a combination of hardware and software. In an exemplary aspect of the present disclosure, monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> may each be implemented as one or more software modules by processing circuity of core hardware <b>208,</b> such as software processes executed by an application processor (i.e. core hardware <b>208)</b> of smart device <b>200.</b> In another exemplary aspect of the present disclosure, monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> may each be implemented as one or more dedicated hardware components of core hardware <b>208.</b> It is appreciated that many such variations are considered within the scope of this disclosure and accordingly are understood to be embraced herein.
0116It is appreciated that core hardware <b>208</b> may further or alternatively include one or more additional elements. In an exemplary aspect of the disclosure, core hardware <b>208</b> may include e.g. a detector configured to change a transition in detection state of the device from a first detection state to a second detection state, wherein the detection state of the device is based on whether the near field communication antenna detects the external near field communication device or e.g. a controller configured to control the device to operate according a first operation mode during a first time period before the transition in which the device remains in the first detection state and control the device to operate according to a second operation mode during a second time period after the transition once the device transitions from the first detection state to the second detection state. In a further exemplary aspect of the disclosure, core hardware <b>208</b> may include e.g. a monitor configured to monitor a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device, e.g. a comparator is configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions, and/or e.g. a trigger configured to initiate a predefined action of the device based on the comparison. Similarly to as detailed regarding , monitor <b>1102,</b> identifier <b>1104,</b> comparator <b>1106,</b> and trigger <b>1108</b> in <figref idref="f0011">FIG. <b>11</b></figref><b>,</b> one or more of the exemplary detector, controller, monitor, comparator, and/or trigger may be implemented one or more components of core hardware <b>208,</b> and thus may be implemented as hardware, software, and/or a combination of hardware and software.
0117<figref idref="f0012">FIG. <b>12</b></figref> shows method <b>1200</b> for operating a controllable electronic device. In <b>1210,</b> method <b>1200</b> may, with NFC circuitry in the controllable electronic device, sense movement of an NFC accessory relative to the controllable electronic device. Method <b>1200</b> may then, with processing circuitry in the controllable electronic device, identify the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements, wherein the database of predefined movements associates each predefined movement with a predefined action of the controllable electronic device in <b>1220.</b> In <b>1230,</b> method <b>1200</b> may, with the processing circuitry, trigger the predefined action associated, in the database, with the given predefined movement.
0118In further exemplary aspects of the disclosure, one or more of methods <b>900, 1000,</b> or <b>1200</b> may be associated with features detailed regarding any one or more of <figref idref="f0001 f0002 f0003 f0004 f0005 f0006 f0007 f0008 f0009">FIGS. <b>1</b> - <b>9</b></figref>, and may be accordingly configured to implement functionality detailed with respect thereto. This disclosure is considered demonstrative in nature, and accordingly any such combinations between one or aspects of this disclosure detailed herein are considered to be fully embraced.
0119The implementation of enhanced NFC-based smart device control as detailed herein may be used to trigger a number of different smart device operations based on the variety of unique movements a user may perform with an NFC accessory. The smart device may record time stamps representing points in time in which the NFC accessory enters and exits the NFC field range, thereby defining a digital waveform. The smart device may then compare the recorded digital waveform against a waveform database in order to determine whether the performed movement has been pre-configured by a user or manufacturer to trigger a predefined smart device operation. The smart device may then perform the associated predefined smart device operation, such as through use of an NFC controller.
0120The enhanced NFC-based smart device control may also be utilized to trigger certain operation states directly based on <i>NFC_Detection_Active</i> or <i>NFC_Detection_Inactive</i> state, such as toggling uppercase/lowercase text entry, scrolling on a virtually displayed page, or copy/paste operations.
0121Although the implementations described herein have been detailed as involving a single NFC accessory associated with two states <i>(NFC_Detection_Active</i> and <i>NFC_Detection_Inactive),</i> it is appreciated that similar approaches may be expanded to operate with multiple NFC accessories. For example, a user may equip two or more NFC accessories and define NFC movements based on digital waveforms for each NFC accessory. A user may consequently define further movements based on the NFC detection state of each NFC accessory.
0122In addition to performing predefined smart device operations, NFC accessories may be used similarly to as detailed above to support other user multimedia operations, such as playing a virtual game on a smart device. Various NFC movements may be defined and configured to trigger certain operations within the virtual game, such as to move a virtual avatar within a game or perform a series of actions within the virtual game. The approaches detailed above regarding triggering certain operation states directly based on NFC detection state may additionally be utilized, such as triggering a virtual avatar to perform a running action movement when an NFC accessory enters into the NFC field range (<i>NFC_Detection_Active</i> state) and to perform a walking/default action movement when the NFC accessory exits the NFC field range (<i>NFC_Detection_Inactive</i> state).
0123Similarly, while sections of this disclosure have focused on controlling a smart device, it is appreciated that any number of controllable devices may be similarly operated utilizing one or more features detailed herein. It is understood that the implementations detailed herein may be applicable to any number of handheld and/or portable devices that are NFC-capable, such as any number of cellular phones, laptops, tablets, keyboards, computer mice, or any such device capable of receiving user input. Furthermore, it is understood that the applications are not limited to portable and/or handheld devices, and e.g. may be applied to stationary devices including personal computers, entertainment systems, home security systems (including e.g. locking and/or door mechanisms), and any number of controllable consumer appliances and/or devices.
0124The following examples pertain to further aspects of the disclosure:
0125Example 1 is a device. The device includes a near field communication antenna configured to detect an external near field communication device, and a processor configured to detect a change in detection state of the device from a first detection state to a second detection state, wherein the change in detection state of the device is based on whether the near field communication antenna detects the external near field communication device, determine a duration of a first time period during which the device remains in the second detection state, and trigger a predefined action of the device based on at least the duration of the first time period.
0126In Example 2, the subject matter of Example 1 can optionally include wherein the first time period is associated with a performed series of one or more transitions in detection state of the device and the predefined action is associated with a predefined series of one or more transitions in detection state of the device, and wherein the processor is further configured to determine whether the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period.
0127In Example 3, the subject matter of Example 2 can optionally include wherein the processor is configured to trigger the predefined action of the device if the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period.
0128In Example 4, the subject matter of Example 3 can optionally include wherein the processor is configured to trigger the predefined action of the device if the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period and the duration of a time period associated with the predefined series of one or more transitions.
0129In Example 5, the subject matter of Example 2 can optionally include wherein the processor is further configured to detect a change in detection state of the device from the second detection state to the first detection state after the first time period, determine a duration of a second time period occurring after the first time period during which the device remains in the first detection state, and determine whether the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period and the duration of the second time period.
0130In Example 6, the subject matter of Example 2 can optionally include wherein the duration of the first time period is based on a first transition time when the detection state of the device changes from the first detection state to the second detection state.
0131In Example 7, the subject matter of Example 6 can optionally include wherein the processor is configured to determine a timestamp indicating the time of the first transition time.
0132In Example 8, the subject matter of Example 6 can optionally include wherein the duration of the first time period is further based on a second transition time when the detection state of the device changes from the second state to the first detection state.
0133In Example 9, the subject matter of Example 2 can optionally include wherein the performed series of one or more transitions is based on a spatial movement pattern of the external near field communication device relative to the device.
0134In Example 10, the subject matter of Example 2 can optionally include wherein the performed series of one or more transitions includes a first plurality of transitions in detection state of the device.
0135In Example 11, the subject matter of Example 10 can optionally include wherein the processor is configured to trigger the predefined action of the device based on timing information associated with the first plurality of transitions.
0136In Example 12, the subject matter of Example 11 can optionally include wherein the timing information associated with the first plurality of transitions includes at least the duration of the first time period.
0137In Example 13, the subject matter of Example 12 can optionally include wherein the timing information associated with the first plurality of transitions includes one or more further durations.
0138In Example 14, the subject matter of Example 12 can optionally include wherein the duration of the first time period is the duration of time between a first transition and a second transition of the first plurality of transitions.
0139In Example 15, the subject matter of Example 10 can optionally include wherein the predefined series of one or more transitions includes a second plurality of transitions, and wherein the processor is configured to trigger the predefined action of the device based on timing information associated with the first plurality of transitions and timing information associated with the second plurality of transitions.
0140In Example 16, the subject matter of Example 15 can optionally include wherein the processor is configured to trigger the predefined action of the device based on whether the timing information associated with the first plurality of transitions matches the timing information associated with the second plurality of transitions.
0141In Example 17, the subject matter of Example 16 can optionally include wherein the processor is configured to determine whether the timing formation associated with the first plurality of transitions matches the timing information associated with the second plurality of transitions based on fuzzy logic.
0142In Example 18, the subject matter of Example 1 can optionally include wherein the duration of the first time period is based on a first transition time when the detection state of the device changes from the first detection state to the second detection state.
0143In Example 19, the subject matter of Example 18 can optionally include wherein the duration of the first time period is further based on a second transition time when the detection state of the device changes from the second state to the first detection state.
0144In Example 20, the subject matter of Example 1 can optionally include wherein the processor is further configured to detect a change in detection state of the device from the second detection state to the first detection state after the first time period, determine a duration of a second time period occurring after the first time period during which the device remains in the first detection state, and trigger the predefined action of the device based on at least the duration of the first time period and the duration of the second time period.
0145In Example 21, the subject matter of Example 20 can optionally include wherein the processor is configured to trigger the predefined action of the device based on at least the duration of the first time period and the duration of the second time period by comparing the duration of the first time period and the duration of the second time period to one or more duration thresholds, wherein the one or more duration thresholds are associated with a predefined series of one or more transitions in the detection state of the device between the first detection state and the second detection sate.
0146In Example 22, the subject matter of Example 20 or 21 can optionally include wherein the processor is configured to trigger the predefined action of the device if the duration of the first time period and the duration time period match with the one or more duration thresholds.
0147In Example 23, the subject matter of Example 21 can optionally include wherein the predefined series of one or more transitions is associated with the predefined action of the device.
0148In Example 24, the subject matter of Example 1 can optionally include wherein the processor is further configured to determine durations of one or more further time periods during which the device remains in the first detection state or the second detection state, and trigger the predefined action of the device based on the duration of the first time period and the durations of the one or more further time periods.
0149In Example 25, the subject matter of Example 24 can optionally include wherein the processor is configured to trigger a predefined action of the device by comparing the duration of the first time period and the one or more further time periods to at least one predefined duration threshold, and triggering the predefined action of the device based on the comparison.
0150In Example 26, the subject matter of Example 25 can optionally include wherein the at least one predefined duration threshold is associated with a predefined series of one or more transitions in the detection state of the device.
0151In Example 27, the subject matter of Example 1 can optionally include wherein the processor is configured to trigger a predefined action of the device by comparing the duration of the first time period to at least one predefined duration threshold, and triggering the predefined action based on the comparison.
0152In Example 28, the subject matter of Example 27 can optionally include wherein the at least one predefined duration threshold is associated with a predefined series of one or more transitions in the detection state of the device.
0153In Example 29, the subject matter of Example 28 can optionally include wherein the at least one predefined duration threshold is the duration in time between a first transition and a second transition in the predefined series of one or more transitions.
0154In Example 30, the subject matter of Example 1 can optionally further include a memory configured to store identification information, and wherein the processor is configured to trigger the predefined action of the device further based on whether identification information of the external near field communication device matches the identification information stored in the memory.
0155In Example 31, the subject matter of Example 1 can optionally include wherein the first detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is detected by the near field communication antenna.
0156In Example 32, the subject matter of Example 1 can optionally include wherein the first detection state is a detection state in which the external near field communication device is detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna.
0157In Example 33, the subject matter of Example 1 can optionally include wherein the external near field communication device is located on the finger of a user.
0158Example 32 is a device. The device includes a near field communication antenna configured to detect an external near field communication device. The device further includes a monitor configured to monitor a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device, a comparator configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions, and a trigger configured to initiate a predefined action of the device based on the comparison.
0159In Example 35, the subject matter of Example 34 can optionally include wherein the predefined series of one or more transitions is based on a spatial movement pattern of the external near field communication device relative to the device.
0160In Example 36, the subject matter of Example 34 can optionally include wherein the trigger is configured to initiate the predefined action if the first timing information matches the second timing information.
0161In Example 37, the subject matter of Example 36 can optionally include wherein the comparator is configured to determine if the first timing information matches the second timing information based on fuzzy logic.
0162In Example 38, the subject matter of Example 34 can optionally include wherein the comparator is further configured to compare the first timing information with third timing information associated with a second predefined series of one or more transitions, and wherein the trigger is further configured to initiate a further predefined action of the device if the first timing information matches the third timing information.
0163In Example 39, the subject matter of Example 34 can optionally further inclue a memory configured to store the second timing information and third timing information.
0164In Example 40, the subject matter of Example 39 can optionally include wherein the memory is further configured to store information associating the second timing information with the first predefined series of one or more transitions and information associating the third timing information with the second predefined series of one or more transitions.
0165In Example 41, the subject matter of Example 34 can optionally include wherein the first predefined series of one or more transitions is associated with the predefined action of the device, and wherein the second predefined series of one or more transitions is associated with the further predefined action.
0166In Example 42, the subject matter of Example 34 can optionally include wherein the first timing information associated with the series of one or more transitions includes a first plurality of timestamps.
0167In Example 43, the subject matter of Example 42 can optionally include wherein the second timing information associated with the predefined series of one or more transitions includes a second plurality of time stamps, and wherein the comparator is configured to perform the comparison between the first timing information and the second timing information by comparing the first plurality of time stamps with the second plurality of time stamps.
0168In Example 44, the subject matter of Example 34 can optionally include wherein the first timing information associated with the series of one or more transitions include a first set of one or more durations.
0169In Example 45, the subject matter of Example 44 can optionally include wherein the second timing information associated with the predefined series of one or more transitions includes a second set of one or more durations, and wherein the comparator is configured to perform the comparison between the first timing information and the second timing information by comparing the first set of one or more durations with the second set of one or more durations.
0170In Example 46, the subject matter of Example 34 can optionally include wherein the first predefined series of one or more transitions is associated with the predefined action of the device.
0171In Example 47, the subject matter of Example 34 can optionally further inclue a memory configured to store the second timing information.
0172In Example 48, the subject matter of Example 47 can optionally include wherein the first predefined series of one or more transitions is associated with the predefined action of the device, and wherein the memory is further configured to store information associating the first predefined series of one or more transitions with the predefined action of the device.
0173In Example 49, the subject matter of Example 34 can optionally include wherein the first timing information and second timing information each include one or more timestamps indicating a transition time between the first detection state and the second detection state, and wherein the comparator is configured to perform the comparison by comparing the one or more timestamps.
0174In Example 50, the subject matter of Example 49 can optionally include wherein the trigger is configured to initiate the predefined action of the device if the one or more timestamps of the first timing information match the one or more timestamps of the second timing information.
0175In Example 51, the subject matter of Example 49 can optionally further inclue a memory configured to store the one or more timestamps of the second timing information.
0176In Example 52, the subject matter of Example 51 can optionally include wherein the memory is further configured to store information associating the predefined action with the first predefined series of one or more transitions.
0177In Example 53, the subject matter of Example 51 can optionally include wherein the information associating the predefined action with the predefined series of one or more transitions is configurable by a user.
0178In Example 54, the subject matter of Example 34 can optionally further inclue an identifier configured to determine identification information of the external near field communication device, and wherein the trigger is configured to initiate the predefined action of the device further based on the identification information of the external near field communication device.
0179In Example 55, the subject matter of Example 1 can optionally include wherein the comparator is configured to compare the identification of external near field communication device with identification information stored in a memory.
0180In Example 56, the subject matter of Example 34 can optionally include wherein the comparator is configured to perform the comparison in real time.
0181In Example 57, the subject matter of Example 34 can optionally include wherein the first detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is detected by the near field communication antenna.
0182In Example 58, the subject matter of Example 34 can optionally include wherein the first detection state is a detection state in which the external near field communication device is detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna.
0183In Example 59, the subject matter of Example 34 can optionally include wherein the external near field communication device is located on the finger of a user.
0184In Example 60, the subject matter of Example 34 can optionally include wherein the comparator is configured to perform the comparison using fuzzy logic.
0185Example 61 is a method for controlling a device. The method includes monitoring a change in detection state of the device from a first detection state to a second detection state, wherein the change in detection state of the smart phone is based on whether a near field communication antenna of the device detects an external near field communication device, determining a duration of a first time period during which the device remains in the second detection state, and triggering a predefined action of the device based on at least the duration of the first time period.
0186In Example 62, the subject matter of Example 61 can optionally include wherein the first time period is associated with a performed series of one or more transitions in detection state of the device and the predefined action is associated with a predefined series of one or more transitions in detection state of the device, and further including determining whether the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period.
0187In Example 63, the subject matter of Example 62 can optionally include wherein the triggering the predefined action of the device includes triggering the predefined action of the device if the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period.
0188In Example 64, the subject matter of Example 63 can optionally include wherein the triggering the predefined action of the device includes triggering the predefined action of the device if the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period and the duration of a time period associated with the predefined series of one or more transitions.
0189In Example 65, the subject matter of Example 62 can optionally further include monitoring a change in detection state of the device from the second detection state to the first detection state, determining a duration of a second time period occurring after the first time period during which the device remains in the first detection state, and determining whether the performed series of one or more transitions matches with the predefined series of one or more transitions based on at least the duration of the first time period and the duration of the second time period.
0190In Example 66, the subject matter of Example claim can optionally include , wherein the duration of the first time period is based on a first transition time when the detection state of the device changes from the first detection state to the second detection state.
0191In Example 67, the subject matter of Example 66 can optionally further include recording a timestamp indicating the time of the first transition time.
0192In Example 68, the subject matter of Example 66 can optionally include wherein the duration of the first time period is further based on a second transition time when the detection state of the device changes from the second state to the first detection state.
0193In Example 69, the subject matter of Example 61 can optionally further include determining the duration of the first time period based on a first transition time when the detection state of the device changes from the first detection state to the second detection state.
0194In Example 70, the subject matter of Example 69 can optionally further include determining the duration of the first time period based on a second transition time when the detection state of the device changes from the second state to the first detection state.
0195In Example 71, the subject matter of Example 62 can optionally include wherein the performed series of one or more transitions is associated with a spatial movement pattern of the external near field communication device relative to the device.
0196In Example 72, the subject matter of Example 62 can optionally include wherein the performed series of one or more transitions includes a first plurality of transitions in detection state of the device.
0197In Example 73, the subject matter of Example 72 can optionally include wherein the processor is configured to trigger the predefined action of the device based on timing information associated with the first plurality of transitions.
0198In Example 74, the subject matter of Example 73 can optionally include wherein the timing information associated with the first plurality of transitions includes at least the duration of the first time period.
0199In Example 75, the subject matter of Example 74 can optionally include wherein the timing information associated with the first plurality of transitions further includes one or more further durations.
0200In Example 76, the subject matter of Example 74 can optionally include wherein the duration of the first time period is the duration of time between a first transition and a second transition of the first plurality of transitions.
0201In Example 77, the subject matter of Example 72 can optionally include wherein the predefined series of one or more transitions includes a second plurality of transitions, and wherein the triggering the predefined action of the device includes triggering the predefined action of the device based on timing information associated with the first plurality of transitions and timing information associated with the second plurality of transitions.
0202In Example 78, the subject matter of Example 77 can optionally further include determining whether the timing formation associated with the first plurality of transitions matches the timing information associated with the second plurality of transitions based on fuzzy logic.
0203In Example 79, the subject matter of Example 61 can optionally further include monitoring a change in detection state of the device from the second detection state to the first detection state after the first time period, determining a duration of a second time period occurring after the first time period during which the device remains in the first detection state, and triggering the predefined action of the device based on at least the duration of the first time period and the duration of the second time period.
0204In Example 80, the subject matter of Example 79 can optionally include wherein the triggering the predefined action of the device based on at least the duration of the first time period and the duration of the second time period includes comparing the duration of the first time period and the duration of the second time period to one or more duration thresholds, wherein the one or more duration thresholds are associated with a predefined series of one or more transitions in the detection state of the device between the first detection state and the second detection state.
0205In Example 81, the subject matter of Example 79 or 80 can optionally further include triggering the predefined action of the device if the duration of the first time period and the duration of the second period match with one or more duration thresholds.
0206In Example 82, the subject matter of Example 80 can optionally include wherein the predefined series of one or more transitions is associated with the predefined action of the device.
0207In Example 83, the subject matter of Example 61 can optionally further include determining durations of one or more further time periods during which the device remains in the first detection state or the second detection state, and triggering the predefined actin of the device based on the duration of the first time period and the durations of the one or more further time periods.
0208In Example 84, the subject matter of Example 83 can optionally include wherein the triggering the predefined action of the device based on the duration of the first time period and the durations of the one or more further time periods includes comparing the duration of the first time period and the one or more further time periods to at least one predefined duration threshold, and triggering the predefined action of the device based on the comparison.
0209In Example 85, the subject matter of Example 84 can optionally include wherein the at least one predefined duration threshold is associated with a predefined series of one or more transitions in the detection state of the device.
0210In Example 86, the subject matter of Example 61 can optionally include wherein the triggering a predefined action of the device includes comparing the duration of the first time period to at least one predefined duration threshold, and triggering the predefined action based on the comparison.
0211In Example 87, the subject matter of Example 86 can optionally include wherein the at least one predefined duration threshold is associated with a predefined series of one or more transitions in the detection state of the device.
0212In Example 88, the subject matter of Example 87 can optionally include wherein the at least one predefined duration threshold is the duration in time between a first transition and a second transition in the predefined series of one or more transitions.
0213In Example 89, the subject matter of Example 61 can optionally include wherein the triggering the predefined action of the device includes triggering the predefined action of the device further based on whether identification information of the external near field communication device matches identification information stored in a memory.
0214In Example 90, the subject matter of Example 61 can optionally include wherein the first detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is detected by the near field communication antenna.
0215In Example 91, the subject matter of Example 61 can optionally include wherein the first detection state is a detection state in which the external near field communication device is detected by the near field communication antenna, and wherein the second detection state is a detection state in which the external near field communication device is not detected by the near field communication antenna.
0216In Example 92, the subject matter of Example 61 can optionally include wherein the external near field communication device is located on the finger of a user.
0217Example 93 is a device. The device includes a near field communication antenna configured to detect an external near field communication device, and a processor configured to detect a transition in detection state of the device from a first detection state to a second detection state, wherein the transition in detection state of the device is based on whether the near field communication antenna detects the external near field communication device, control the device to operate according to a first operation mode during a first time period before the transition in which the device remains in the first detection state, and control the device to operate according to a second operation mode during a second time period after the transition once the device transitions from the first detection state to the second detection state.
0218In Example 94, the subject matter of Example 93 can optionally include wherein the processor is configured to control the device to operate according to the second operation mode immediately upon detecting the transition in detection state from the first detection state to the second detection state.
0219In Example 95, the subject matter of Example 93 can optionally include wherein the processor is further configured to detect a further transition in detection state of the device from the second detection state to the first detection state, and control the device to operate according to the first operation mode during a third time period after the further transition.
0220In Example 96, the subject matter of Example 95 can optionally include wherein the processor is configured to control the device to operate according to the first operation mode for the entire duration of the first time period.
0221In Example 97, the subject matter of Example 95 or 96 can optionally include wherein the processor is configured to control the device to operate according to the second operation mode for the entire duration of the second time period.
0222In Example 98, the subject matter of Example 93 can optionally include wherein the processor is configured to control the device to operate according to the first operation mode for the entire duration of the first time period.
0223In Example 99, the subject matter of Example 93 can optionally include wherein the first operation mode is a first type of character text entry and the second operation mode is a second type of character text entry different from the first type of character text entry.
0224In Example 100, the subject matter of Example 99 can optionally include wherein the first operation mode is uppercase character text entry and the second operation mode is lowercase character text entry, or wherein the first operation mode is lowercase character text entry and the second operation mode is uppercase character text entry.
0225In Example 101, the subject matter of Example 93 can optionally include wherein the first operation mode is a first type of scrolling operation, and wherein the second operation mode is a second type of scrolling operation different from the first type of scrolling operation.
0226In Example 102, the subject matter of Example 101 can optionally include wherein the first operation mode is selected from a scrolling type group consisting of a scroll up operation, a scroll down operation, and a no scrolling operation, and wherein the second operation mode is selected from the scrolling type group consisting of a scroll up operation, a scroll down operation, and a no scrolling operation.
0227In Example 103, the subject matter of Example 93 can optionally include wherein the external near field communication device is located on the finger of a user.
0228In Example 104, the subject matter of Example 93 can optionally include wherein the processor is further configured to receive first identification information of the external near field communication device, and perform a comparison between the first identification information and second identification information.
0229In Example 105, the subject matter of Example 104 can optionally include wherein the processor is configured to control the device to operate according to the first operation mode and control the device to operate according to the second operation mode based on the comparison.
0230In Example 106, the subject matter of Example 105 can optionally include wherein the processor is configured to control the device to operate according to the first operation mode and control the device to operate according to the second operation mode if the first identification information matches the second identification information.
0231In Example 107, the subject matter of Example 104 can optionally further include a memory configured to store the second identification information.
0232In Example 108, the subject matter of Example 107 can optionally include wherein the memory is configured to store further identification information, and wherein the device is configured to perform a comparison between the first identification information and the further identification information.
0233In Example 109, the subject matter of Example 108 can optionally include wherein the processor is configured to control the device to operate according to the first operation mode and control the device to operate according to the second operation mode if the first identification information matches the further identification information.
0234In Example 110, the subject matter of Example 93 can optionally include wherein the first detection state corresponds to the near field communication antenna being unable to detect the external near field communication device.
0235In Example 111, the subject matter of Example 93 can optionally include wherein the second detection state corresponds to the near field communication antenna being unable to detect the external near field communication device.
0236Example 112 is a method for controlling a device. The method includes detecting a transition in detection state of the device from a first detection state to a second detection state, wherein the detection state of the device is based on whether a near field communication antenna of the device detects an external near field communication device, controlling the device to operate according to a first operation mode during a first time period before the transition in which the device remains in the first detection state, and controlling the device to operate according to a second operation mode during a second time period after the transition once the device transitions from the first detection state to the second detection state.
0237In Example 113, the subject matter of Example 112 can optionally include wherein the controlling the device to operate according to the second operation mode includes controlling the device to operate according to the second operation mode immediately upon detecting the transition in detection state from the first detection state to the second detection state.
0238In Example 114, the subject matter of Example 112 can optionally further include detecting a further transition in detection state of the device from the second detection state to the first detection state, and controlling the device to operate according to the first operation during a third time period after the further transition.
0239In Example 115, the subject matter of Example 114 can optionally further include controlling the device to operate according to the first operation mode for the entire duration of the first time period.
0240In Example 116, the subject matter of Example 114 or 115 can optionally further include controlling the device to operate according to the second operation mode for the entire duration of the second time period.
0241In Example 117, the subject matter of Example 112 can optionally further include controlling the device to operate according to the first operation mode for the entire duration of the first time period.
0242In Example 118, the subject matter of Example 112 can optionally include wherein the first operation mode is a pre-defined operation triggered by the device, and wherein the second operation mode is a different pre-defined operation triggered by the device.
0243In Example 119, the subject matter of Example 112 can optionally include wherein the first operation mode is a first type of character text entry and the second operation mode is a second type of character text entry different from the first type of character text entry.
0244In Example 120, the subject matter of Example 119 can optionally include wherein the first operation mode is uppercase character text entry and the second operation mode is lowercase character text entry, or wherein the first operation mode is lowercase character text entry and the second operation mode is uppercase character text entry.
0245In Example 121, the subject matter of Example 112 can optionally include wherein the first operation mode is a first type of scrolling operation, and wherein the second operation mode is a second type of scrolling operation different from the first type of scrolling operation.
0246In Example 122, the subject matter of Example 121 can optionally include wherein the first operation mode is selected from a scrolling type group consisting of a scroll up operation, a scroll down operation, and a no scrolling operation, and wherein the second operation mode is selected from the scrolling type group consisting of a scroll up operation, a scroll down operation, and a no scrolling operation.
0247In Example 123, the subject matter of Example 112 can optionally include wherein the external near field communication device is located on the finger of a user.
0248In Example 124, the subject matter of Example 112 can optionally further include receiving first identification information of the external near field communication device, and performing a comparison between the first identification information and second identification information.
0249In Example 125, the subject matter of Example 124 can optionally include wherein the controlling the device to operate according to the first operation mode and the controlling the device to operate according to the second operation mode is based on the comparison.
0250In Example 126, the subject matter of Example 125 can optionally include wherein the controlling the device to operate according to the first operation mode and controlling the device to operate according to the second operation mode includes controlling the device to operate according to the first operation mode and controlling the device to operate according to the second operation mode if the first identification information matches the second identification information.
0251In Example 127, the subject matter of Example 124 can optionally further include storing the second identification information is stored on a memory of the device.
0252In Example 128, the subject matter of Example 127 can optionally further include storing further identification information on the memory, and performing a comparison between the first identification information and the further identification information.
0253In Example 129, the subject matter of Example 128 can optionally include wherein the controlling the device to operate according to the first operation mode and controlling the device to operate according to the second operation mode includes controlling the device to operate according to the first operation mode and controlling the device to operate according to the second operation mode if the first identification information matches the further identification information.
0254In Example 130, the subject matter of Example 112 can optionally include wherein the first detection state corresponds to the near field communication antenna being unable to detect the external near field communication device.
0255In Example 131, the subject matter of Example 112 can optionally include wherein the second detection state corresponds to the near field communication antenna being unable to detect the external near field communication device.
0256Example 132 is a device. The device includes a near field communication antenna configured to detect an external near field communication device. The device also include a monitor, a comparator, and a trigger. The monitor is configured to monitor a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device. The comparator is configured to perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions. The trigger is configured to initiate a predefined action of the device based on the comparison.
0257Example 133 is a device. The device includes a near field communication antenna, a monitor, a detector, a determiner, and a trigger. The near field communication antenna configured to detect an external near field communication device. The detector is configured to change a detection state of the device from a first detection state to a second detection state based on whether the near field communication antenna detects the near field communication device. The determiner is configured to determine a duration of a first time period during which the device remains in the second detection state. The trigger is configured to initiate a predefined action of the device based on at least the duration of the first time period.
0258Example 134 is a device. The device includes a near field communication antenna, a detector, and a controller. The near field communication antenna is configured to detect an external near field communication device. The detector is configured to change a transition in detection state of the device from a first detection state to a second detection state, wherein the detection state of the device is based on whether the near field communication antenna detects the external near field communication device. The controller is configured to control the device to operate according a first operation mode during a first time period before the transition in which the device remains in the first detection state and control the device to operate according to a second operation mode during a second time period after the transition once the device transitions from the first detection state to the second detection state.
0259Example 135 is a method of operating a controllable electronic device. The method includes with NFC circuitry in the controllable electronic device, sensing movement of an NFC accessory relative to the controllable electronic device, with processing circuitry in the controllable electronic device, identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements, wherein the database of predefined movements associates each predefined movement with a predefined action of the controllable electronic device, and with the processing circuity, triggering the predefined action associated, in the database, with the given predefined movement.
0260In Example 136, the subject matter of Example 135 can optionally include wherein the sensing movement of the NFC accessory relative to the controllable electronic device includes sensing user input.
0261In Example 137, the subject matter of Example 135 can optionally include wherein the sensing movement of the NFC accessory relative to the controllable electronic device includes sensing the NFC accessory entering a detection range of the NFC circuitry in the controllable electronic device.
0262In Example 138, the subject matter of Example 137 can optionally include wherein the sensing movement of the NFC accessory relative to the controllable electronic device includes sensing the NFC accessory leaving the detection range of the NFC circuitry in the controllable electronic device.
0263In Example 139, the subject matter of Example 137 can optionally further inclue, with the processing circuitry in the controllable electronic device, calculating a detected duration of time during which the NFC accessory remains within the detection range of the NFC circuitry in the controllable electronic device.
0264In Example 140, the subject matter of Example 139 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing the detected duration of time to a duration of time associated with at least one of the predefined movements in the databased of predefined movements.
0265In Example 141, the subject matter of Example 139 can optionally include wherein the sensing the NFC accessory entering a detection range of the NFC circuitry in the controllable electronic device includes detecting the NFC accessory crossing a detection threshold of the NFC circuitry.
0266In Example 142, the subject matter of Example 137 can optionally include wherein the sensing the NFC accessory entering a detection range of the NFC circuitry in the controllable electronic device includes detecting the NFC accessory crossing a detection threshold of an NFC antenna of the controllable electronic device.
0267In Example 143, the subject matter of Example 135 can optionally include wherein the controllable electronic device includes a handheld electronic device having a display on a front side and having an NFC antenna disposed on a back side.
0268In Example 144, the subject matter of Example 135 can optionally include wherein the external NFC accessory is disposed on a user's finger.
0269In Example 145, the subject matter of Example 135 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes identifying that the sensed movement is substantially similar to the given predefined movement.
0270In Example 146, the subject matter of Example 145 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements further includes identifying that the sensed movement is not substantially similar to one or more other predefined movements of the database of predefined movements.
0271In Example 147, the subject matter of Example 145 can optionally include wherein the identifying that the sensed movement is substantially similar to the given predefined movement includes utilizing fuzzy logic to identify whether or not the sensed movement is substantially similar to the given predefined movement.
0272In Example 148, the subject matter of Example 135 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes determining a sensed waveform based on the sensed movement.
0273In Example 149, the subject matter of Example 148 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing the sensed waveform with one or more defined waveforms associated with the predefined movements in the database of predefined movements.
0274In Example 150, the subject matter of Example 148 can optionally further inclue, with a memory in the controllable electronic device, storing the database of predefined movements.
0275In Example 151, the subject matter of Example 150 can optionally include wherein the storing the database of predefined movements includes storing a designated waveform corresponding to each of the predefined movements in the memory.
0276In Example 152, the subject matter of Example 151 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing the sensed waveform with the designated waveforms corresponding to one or more of the predefined movements.
0277In Example 153, the subject matter of Example 135 can optionally further inclue with a memory in the controllable electronic device, storing the database of predefined movements.
0278In Example 154, the subject matter of Example 153 can optionally include wherein the storing the database of predefined movements includes storing a designated waveform corresponding to each of the predefined movements in the memory.
0279In Example 155, the subject matter of Example 149 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing the sensed waveform with the designated waveforms corresponding to one or more of the predefined movements.
0280In Example 156, the subject matter of Example 145 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes identifying that the sensed movement is substantially similar to the given predefined movement based on timing information associated with the sensed movement and timing information associated with the predefined movements of the database of predefined movements.
0281In Example 157, the subject matter of Example 156 can optionally include wherein the timing information associated with the sensed movement and timing information associated with the predefined movements of the database of predefined movements includes one or more timestamps or one or more time period durations.
0282In Example 158, the subject matter of Example 157 can optionally include wherein the one or more timestamps include timepoints when the NFC accessory enters or leaves a detection range of the NFC circuitry.
0283In Example 159, the subject matter of Example 157 can optionally include wherein the one or more time periods durations include time windows in which the NFC accessory is within the detection range of the NFC circuitry or outside of the detection range of the NFC circuitry.
0284In Example 160, the subject matter of Example 135 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing timing information of the sensed movement to timing information of the predefined movements.
0285In Example 161, the subject matter of Example 160 can optionally include wherein the comparing timing information of the sensed movement to timing information of the predefined movements includes comparing one or more timestamps associated with the sensed movement to one or more timestamps associated with one or more of the predefined movements.
0286In Example 162, the subject matter of Example 161 can optionally include wherein the sensing movement of the NFC accessory relative to the controllable electronic device includes sensing one or detection timepoints at which the NFC accessory enters or leaves a detection range of the NFC circuitry.
0287In Example 163, the subject matter of Example 162 can optionally include wherein the one or more timestamps associated with the sensed movement are based on one or more of the one or more of the detection timepoints.
0288In Example 164, the subject matter of Example 135 can optionally include wherein the sensing movement of the NFC accessory relative to the controllable electronic device includes sensing one or detection timepoints in which NFC accessory enters or leaves a detection range of the NFC circuitry.
0289In Example 165, the subject matter of Example 164 can optionally include wherein the , identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes deriving a sensed waveform based on the one or more detection timepoints.
0290In Example 166, the subject matter of Example 165 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes comparing the sensed waveform to designated waveforms corresponding to one or more of the predefined movements.
0291In Example 167, the subject matter of Example 135 can optionally further inclue, with the NFC circuitry, reading identification information of the NFC accessory.
0292In Example 168, the subject matter of Example 167 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements based on the identification information.
0293In Example 169, the subject matter of Example 135 can optionally include wherein a first predefined movement of the predefined movements is different from a second predefined movement of the predefined movements.
0294In Example 170, the subject matter of Example 169, wherein the first predefined movement is associated with a first spatial movement pattern of the of the NFC accessory relative to the controllable electronic device and the second predefined movement is associated with a second spatial movement pattern of the NFC accessory relative to the controllable electronic device.
0295In Example 171, the subject matter of Example 170 can optionally include wherein the first spatial movement pattern is different than the second spatial movement pattern.
0296In Example 172, the subject matter of Example 169 can optionally include wherein the first predefined movement is associated with one or more first timepoints when the NFC accessory enters or leaves a detection range of the NFC circuitry and the second predefined movement is associated with one or more second timepoints when the NFC accessory enters or leaves a detection range of the NFC circuitry.
0297In Example 173, the subject matter of Example 172 can optionally include wherein the one or more first timepoints are different than the one more second timpeoints.
0298In Example 174, the subject matter of Example 135 can optionally include wherein a first predefined movement of the predefined movements is associated with a first predefined action and a second predefined movement of the predefined movements is associated with a second predefined action.
0299In Example 175, the subject matter of Example 174 can optionally include wherein the first predefined action is different than the second predefined action.
0300In Example 176, the subject matter of Example 135 can optionally include wherein the sensed movement is associated with one or more sensed timepoints when the NFC accessory enters or leaves a detection range of the NFC circuitry and the given predefined movement is associated with one or more defined timepoints when the NFC accessory enters or leaves a detection range of the NFC circuitry.
0301In Example 177, the subject matter of Example 176 can optionally include wherein the identifying the sensed movement of the NFC accessory as a given predefined movement in a database of predefined movements includes identifying that the one or more sensed timepoints are substantially similar to the one or more defined timepoints.
0302In Example 178, the subject matter of Example 177 can optionally include wherein the identifying that the one or more sensed timepoints are substantially similar to the one or more defined timepoints includes utilizing fuzzy logic to identify whether the one or more sensed timepoints are substantially similar to the one or more defined timepoints.
0303In Example 179, the subject matter of Example 135 can optionally include wherein the processing circuitry includes an application processor, and wherein the triggering the predefined movement associated, in the database, with the given predefined movement includes executing the predefined action with the application processor.
0304In Example 180, the subject matter of Example 135 can optionally include wherein the controllable electronic device is a portable electronic device.
0305Example 181 is a device. The device includes a near field communication antenna and a processing circuit. The near field communication antenna is configured to detect an external near field communication device. The processing circuit is configured to monito a series of one or more transitions in a detection state of the device between a first detection state and a second detection state based on whether the near field communication antenna detects the near field communication device, perform a comparison between first timing information associated with the series of one or more transitions and second timing information associated with a first predefined series of one or more transitions, and initiate a predefined action of the device based on the comparison.
0306While the invention has been particularly shown and described with reference to specific embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. The scope of the invention is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced.
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO2008010103A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
| US2014101755A1 | Cites | United States of America | Search report |
| US2014230057A1 | Cites | United States of America | Search report |
| US2015163621A1 | Cites | United States of America | Search report |
4 members in 3 offices; this record represents the family
Members4
| Document | Office | Kind | |
|---|---|---|---|
| EP3109735A1This record | European Patent Office (EPO) | A1 | |
| US2016378192A1 | United States of America | A1 | |
| CN106301487A | China | A | |
| EP3109735B1 | European Patent Office (EPO) | B1 |
72 legal events, as 9 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | NL | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| No opposition filedOpposition26N | 26N | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Invalidated european patentMG4D | MG4D | LT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: REQUEST FOR EXAMINATION WAS MADESTAA | STAA | EP |
Numbers
- Publication
- 3109735
- Application
- 161702402
Titles3
- German
- VORRICHTUNG UND VERFAHREN ZUM BETRIEB EINER STEUERBAREN ELEKTRONISCHEN VORRICHTUNG
- English
- DEVICE AND METHOD OF OPERATING A CONTROLLABLE ELECTRONIC DEVICE
- French
- DISPOSITIF ET PROCÉDÉ D'EXPLOITATION D'UN DISPOSITIF ÉLECTRONIQUE CONTRÔLABLE
Classification
- CPC, 10
- H04B5/48
- G06F3/017
- G06F3/033
- G06K7/10316
- G08C17/02
- H04M2250/04
- H04M1/72412
- H04B5/70
- H04B5/20
- G06F3/0485
- IPC, 6
- G06F3 01
- H04B5 00
- H04M1 725
- H04B5 48
- H04B5 20
- H04M1 72412
Designated states42
- Contracting states, 38
- Albania
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
and 14 moreShow fewer
- Monaco
- North Macedonia
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Serbia
- Sweden
- Slovenia
- Slovakia
- San Marino
- Türkiye
- Extension states, 2
- Bosnia and Herzegovina
- Montenegro
- Validation states, 2
- Morocco
- Republic of Moldova