NFC collision avoidance with controllable NFC transmission delay timing

[0001] This application is a continuation of U.S. patent application Ser. No. 14/462,015, filed Aug. 18, 2014, which itself claims priority to U.S. provisional Patent Application No. 61/942,716, filed 21 Feb. 2014, the disclosure and content of both of which are incorporated by reference herein in their entireties.

[0002] The present invention relates to wireless communication user equipment and, more particularly, to mobile phones and related accessories such as covers that are attachable to mobile phones.

[0003] Cell phones and other user equipment are increasingly including near field communication (NFC) circuits that can be used to communicate with external NFC circuits. Users can now operate user equipment to provide credit/debit account information to retail point-of-sale terminals, read data from NFC tags on items, determine the presence and absence of NFC tagged items, and perform other desirable operations. Unfortunately, with the tremendous proliferation of NFC circuits there are also increasing opportunities for time overlapping collisions to occur between the transmissions of nearby NFC circuits that can interfere with or prevent a user equipment from carrying out communications with a targeted NFC circuit.

[0004] One embodiment of the present disclosure is directed to a first NFC circuit that includes an antenna, a charging circuit, a transceiver circuit, and a transmission delay circuit. The antenna is configured to inductively couple to signals emitted by a second NFC circuit. The charging circuit is configured to output power provided by the inductive coupling through the antenna to the signals emitted by the second NFC circuit. The transceiver circuit is configured to be powered by the charging circuit to transmit data for receipt by the second NFC circuit. The transmission delay circuit is configured to be powered by the charging circuit and control the transceiver circuit to delay transmission of the data until expiration of a defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data.

[0005] In some further embodiments, the transceiver circuit may be configured to receive a delay setting signal transmitted by the second NFC circuit, and the transmission delay circuit is configured to set the defined delay time based on the delay setting signal.

[0006] The transmission delay circuit may be configured to respond to the delay setting signal by disabling subsequent transmission of data by the transceiver circuit until the first NFC circuit is powered off and back on.

[0007] The transmission delay circuit may be configured to set the defined delay time based on determining that signals from a third NFC circuit were received by the transceiver circuit within a threshold time after the transceiver circuit became sufficiently powered on to operate to transmit the data. The transmission delay circuit may be configured to set the defined delay time to disable transmission of the data by the transceiver circuit until the first NFC circuit is subsequently powered off and back on.

[0008] The transmission delay circuit may be configured to set the defined delay time based on determining that signals from a third NFC circuit were received by the transceiver circuit while the transceiver circuit is transmitting the data. The transmission delay circuit may be configured to set the defined delay time to disable further transmission of the data by the transceiver circuit until the first NFC circuit is subsequently powered off and back on.

[0009] The transmission delay circuit may be configured to count a number of times that data has been transmitted by the transceiver circuit, and to set the defined delay time based on the count. The transmission delay circuit may change the defined delay time from a first delay value to a longer second delay value based on the count exceeding a threshold count value.

[0010] The transmission delay circuit may be configured to incrementally increase the defined delay time based on each data transmission by the transceiver circuit until a maximum delay time is reached.

[0011] The first NFC circuit may further include a delay control switch connected to the transmission delay circuit and configured to be mechanically actuated by a user. While the delay control switch is mechanically actuated the transmission delay circuit controls the transceiver circuit to immediately transmit the data when sufficiently powered on to operate to transmit the data, and while the delay control switch is not mechanically actuated the transmission delay circuit controls the transceiver circuit to delay transmission of the data until expiration of the defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data.

[0012] In another embodiment, the first NFC circuit includes a delay control switch connected to the transmission delay circuit and configured to be mechanically actuated by a user. While the delay control switch is mechanically actuated the transmission delay circuit controls the transceiver circuit to delay transmission of the data until expiration of the defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data, and while the delay control switch is not mechanically actuated the transmission delay circuit controls the transceiver circuit to be disabled from transmitting the data.

[0013] Some other embodiments are directed to an accessory for a user equipment. The accessory includes a housing that is connectable to the user equipment, and a first NFC circuit attached to the housing. The first NFC circuit includes an antenna, a charging circuit, a transceiver circuit, and a transmission delay circuit. The antenna is configured to inductively couple to signals emitted by a second NFC circuit. The charging circuit is configured to output power provided by the inductive coupling through the antenna to the signals emitted by the second NFC circuit. The transceiver circuit is configured to be powered by the charging circuit to transmit data for receipt by the second NFC circuit. The transmission delay circuit is configured to be powered by the charging circuit and control the transceiver circuit to delay transmission of the data until expiration of a defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data.

[0014] In some further embodiments, the transceiver circuit may be configured to receive a delay setting signal transmitted by the second NFC circuit, and the transmission delay circuit may be configured to set the defined delay time based on the delay setting signal.

[0015] The transmission delay circuit may be configured to respond to the delay setting signal by disabling subsequent transmission of data by the transceiver circuit to the second NFC circuit until the first NFC circuit is powered off and back on.

[0016] The transmission delay circuit may be configured to set the defined delay time based on determining that signals from a third NFC circuit were received by the transceiver circuit within a threshold time after the transceiver circuit became sufficiently powered on to operate to transmit the data.

[0017] The transmission delay circuit may be configured to set the defined delay time based on determining that signals from a third NFC circuit were received by the transceiver circuit while the transceiver circuit is transmitting the data.

[0018] The transmission delay circuit may be configured to count a number of times that data has been transmitted by the transceiver circuit, and to set the defined delay time based on the count.

[0019] The transmission delay circuit may be configured to incrementally increase the defined delay time based on each data transmission by the transceiver circuit until a maximum delay time is reached.

[0020] The first NFC circuit may further include a delay control switch connected to the transmission delay circuit and configured to be mechanically actuated by a user. While the delay control switch is mechanically actuated the transmission delay circuit controls the transceiver circuit to immediately transmit the data when sufficiently powered on to operate to transmit the data, and while the delay control switch is not mechanically actuated the transmission delay circuit controls the transceiver circuit to delay transmission of the data until expiration of the defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data.

[0021] In another embodiment, the first NFC circuit includes a delay control switch connected to the transmission delay circuit and configured to be mechanically actuated by a user. While the delay control switch is mechanically actuated the transmission delay circuit controls the transceiver circuit to delay transmission of the data until expiration of the defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data, and while the delay control switch is not mechanically actuated the transmission delay circuit controls the transceiver circuit to be disabled from transmitting the data.

[0022] The accessory may comprise a cover configured to protect a surface of the user equipment and/or a stand that supports and holds the user equipment in a defined orientation.

[0023] Some other embodiments are directed to a user equipment that includes a first NFC circuit and a processor. The first NFC circuit is configured to emit a signal to provide power through inductive coupling to a second NFC circuit of an accessory configured to be used with the user equipment. The processor is configured to transmit a delay setting signal through the first NFC circuit to the second NFC circuit of the accessory that controls a defined delay time that the second NFC circuit delays before beginning to transmit data after the second NFC circuit has become sufficiently powered on to operate to transmit the data.

[0024] In some further embodiments, the processor may be configured to transmit the delay setting signal through the first NFC circuit to the second NFC circuit based on determining that signals from a third NFC circuit were received by the first NFC circuit within a threshold time after the first NFC circuit began emitting the signal to provide power through inductive coupling to the second NFC circuit of the accessory.

[0025] The processor may be configured to transmit the defined delay time through the first NFC circuit to the second NFC circuit based on determining that signals from a third NFC circuit were received by the first NFC circuit while the first NFC circuit was receiving the data from the second NFC circuit of the accessory.

[0026] Other NFC circuits, accessories for user equipment, user equipment, and methods according to other embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional NFC circuits, accessories for user equipment, user equipment, and methods be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.

[0040] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention. It is intended that all embodiments disclosed herein can be implemented separately or combined in any way and/or combination.

[0041] Various embodiments of the present disclosure are directed to an accessory for a user equipment (“UE”). FIG. 1 illustrates an accessory 100 that is configured according to some embodiments for use with a UE 300. The accessory 100 includes a housing 102 that slides (e.g., along direction 101) on the UE 300 to become attached in a stored position relative to the UE 300. FIG. 2 illustrates the accessory 100 attached in a stored position relative to the UE 300 of FIG. 1 according to some embodiments. Although some embodiments of the accessory 100 are described as being configured to slide-on the UE 300, other embodiments may snap on, adhesively connect to, or otherwise maintain contact with or NFC communication range with the UE 300.

[0042] In one embodiment, the housing 102 has raised edge surfaces along at least two sides that form a central recessed surface area that extends to a recessed end of the housing to receive the UE 300 slid through the recessed end of the housing toward the stored position where the raised edge surfaces engage and retain the UE 300 in the stored position.

[0043] The accessory 100 may be a cover that, for example, protects a back surface of the UE 300, or a stand, such as a handsfree phone accessory, that supports and holds the UE 300 in a defined orientation. The UE 300 may be a cellular phone, a tablet computer, a palmtop computer, a mobile music/video player, or any other electronic device.

[0044] The accessory 100 has a NFC circuit 110, which is referred to as the “accessory NFC circuit 110”, that is located on the housing 102, and may be at least partially disposed within the housing 102 or reside entirely within the housing 102. The UE 300 has another NFC circuit 310, which is referred to as the “UE NFC circuit 310”. Thus, depending upon the proximity and configuration of the NFC circuits 110 and 310 while the accessory 100 is attached in the stored position relative to the UE 300, the accessory NFC circuit 110 may interfere with the ability of the UE NFC circuit 310 to communicate with a NFC circuit of a targeted device, such as a point of sale credit card processing terminal, a NFC tag on a product, which a user is attempting to communicate with through the UE 300.

[0045] For example, absent use of various embodiments disclosed herein, the accessory NFC circuit 110 could be positioned between the UE NFC circuit 310 and the NFC circuit of the targeted device, and located much closer to the UE NFC circuit 310 than the NFC circuit of the targeted device. Transmissions from the accessory NFC circuit 110 may thereby undesirably interfere (collide) with transmissions from the targeted device, and prevent reliable receipt by the UE 300 of data from the NFC circuit of the targeted device.

[0046] However, in accordance with some embodiments disclosed herein, the accessory NFC circuit 110 is attached at a location on the housing 102 and configured to be powered by inductive coupling to signals emitted by the other NFC circuit 310 within the UE 300 to temporarily operate to transmit data to the UE NFC circuit 310 as the accessory NFC circuit 110 passes over the UE NFC circuit 310 while the housing 102 is being slid on the UE 300 before reaching the stored position relative to the UE 300.

[0047] In some further embodiments, the accessory NFC circuit 110 becomes powered by inductive coupling to signals emitted by the UE NFC circuit 310 to temporarily operate to transmit data to the UE NFC circuit 310 as the accessory NFC circuit 110 passes over the UE NFC circuit 310 while the housing 102 is being slid off the UE 300. Furthermore, while the housing 102 is in the stored position relative to the UE 300, the accessory NFC circuit 110 is inhibited or prevented from transmitting data to the UE NFC circuit 310 irrespective of whether the UE NFC circuit 310 is emitting signals to attempt to provide inductive coupling to the accessory NFC circuit 110.

[0048] While the housing 102 is in the stored position relative to the UE 300, the accessory NFC circuit 110 is too remotely located from the UE NFC circuit 310 to be sufficiently powered by any inductive coupling to signals emitted by the UE NFC circuit 310 to operate the transmit data, according to one embodiment. For example, as shown in the embodiment of FIG. 2, the housing 102 has a top 202 that is adjacent an ear speaker 340 (FIG. 3) of the UE 300 and a bottom 204 that is adjacent a microphone 342 (FIG. 3) of the UE 300 while the housing 102 is in the stored position relative to the UE 300. The accessory NFC circuit 110 is located adjacent the bottom of the housing 102 and spaced apart by distance 200 to be remote from the UE NFC circuit 310 located adjacent the ear speaker of the UE 300. A location where the accessory NFC circuit 110 is fixed to the accessory 100 can be selected to provide sufficient communication isolation between the NFC circuits 110 and 310 to inhibit or prevent data transmission by the accessory NFC circuit 110 while the housing 102 is in the stored position relative to the UE 300.

[0049] FIG. 3 is a block diagram of components of the accessory 100 and the UE 300 that are connectable and configured to operate according to some embodiments. The UE 300 can include a housing 302, a processor circuit 320, a radio access transceiver 330, a NFC circuit 310, a memory device(s) 322, a display device 326, a user input interface 324 (e.g., touch sensitive interface for the display device 326, keypad/keyboard, button(s)/switch(es), etc.), a power source 328 (e.g., rechargeable battery) that supplies power to these and other components, a speaker 340, and a microphone 342. The radio access transceiver 330 may include, but is not limited to, a LTE or other cellular transceiver, Bluetooth transceiver, WiFi transceiver, WiMax transceiver, or other communication transceiver is configured to communicate with a network node of a telecommunications system. The processor 320 may include one or more data processing circuits, such as a general purpose and/or special purpose processor, such as a microprocessor and/or digital signal processor. The processor 320 is configured to execute computer program instructions from functional modules in the memory 322, described below as a computer readable medium, to perform at least some of the operations and methods described herein as being performed by a user equipment.

[0050] The accessory 100 includes a NFC circuit 110 (e.g., accessory NFC circuit) that can be powered by and communicate with the UE NFC circuit 310 using short-range high frequency wireless communication technology which enables the exchange of data between devices over about a 10 cm distance, although the NFC circuits 110 and 310 are not limited to operating in any defined range. The communication protocol and operation can be an extension of the ISO 14443 proximity-card standard (e.g., contactless card, RFID) and can be specified in the ECMA-340 and ISO/IEC 18092 technology standards. Some embodiments of the NFC circuits 110 and 310 may communicate using existing ISO 14443 smartcards and readers and can thereby be compatible with existing contactless communication infrastructure.

[0051] The NFC circuits 110 and 310 may communicate via magnetic field induction. A loop antenna 316 connected to the NFC circuit 310 and a loop antenna 108 of the accessory NFC circuit 110 are placed in close proximity to each other within the other's antenna near field, thereby effectively forming an air-core transformer. Some embodiments of the NFC circuits 110 and 310 can transmit within the globally available and unlicensed radio frequency ISM band of 13.56 MHz, with a bandwidth of almost 2 MHz. Some embodiments of the NFC circuits 110 and 310 can support data rates of 106, 212, or 424 kbit/s using a modified Miller coding or Manchester coding to encode and decode communicated data.

[0052] The accessory NFC circuit 110 can be configured to operate in a passive communication mode, because the accessory 100 does not have its own power source. In contrast, the UE NFC circuit 310 can be configured to operate in an active communication mode because of the power source 322 (FIG. 3), e.g., rechargeable battery, of the UE 300. When operating in the passive communication mode, the UE NFC circuit 310 provides a carrier field and the accessory NFC circuit 110 answers by modulating the carrier field. In this mode, the accessory NFC circuit 110 generates its operating power from the NFC circuit 310 provided electromagnetic field, thus making the accessory NFC circuit 110 a transponder. In some other embodiments the accessory NFC circuit 110 contains a power supply and is configured to operate in an active communication mode.

[0053] The NFC circuit 110 includes a charging circuit 106 that can become inductively coupled to the UE NFC circuit 310 through the antenna 108 to generate power therefrom, and which it provides to a transceiver circuit 104. The transceiver circuit 104 transmits data through the antenna 108 to the UE NFC circuit 310 using the power from the charging circuit 106. The transceiver circuit 104 may optionally be configured to receive data through the antenna 108 from the UE NFC circuit 310.

[0054] After an initial receipt and use of information from the accessory NFC circuit 110, the UE 300 may be configured to subsequently ignore information from the accessory NFC circuit 110 to avoid interference with communications between the NFC circuit 310 of the UE 300 and other NFC devices.

Using NFC Enabled Accessories to Provide Movies, Music, Games, Books, Promotional Information, Coupons, and Other Content

[0055] NFC enabled accessories for UEs can be sold or otherwise provided to consumers to provide applications that are executable by the UEs, activate operational features of the UEs, and/or to provide other content to the UE. The content may include, for example, movies, music (e.g., songs, ring tones, etc.), electronic books, television programs, games, discount coupons, promotional information, etc.

[0056] A movie studio may sell or otherwise provide movie themed covers or other accessories for UEs. The accessories can include a NFC circuit which transmits information that is used by the UE to obtain content from a content server and/or to unlock/activate content that may already reside on the UE that relates to the movie. For example, a NFC circuit may transmit information that contains a universal resource locator (URL) address to particular content stored on a content server, which is accessible through a data network, that can be retrieved by downloading/streaming the movie, music relating to the movie, background display image(s) relating to the movie, promotional information relating to the movie, discount that can be redeemed to purchase or temporarily view the movie, etc. A business may therefore work with a content provider to make content available through a network content server (e.g., a cloud service server), and can configure an accessory NFC circuit to transmit a URL to the location of the content stored on the server. The accessory NFC circuit may further transmit authorization information that can be used by the server to confirm that a UE requesting access to the content is indeed authorized to obtain such access through use of the accessory NFC circuit.

[0057] Other covers/accessories can be provided by music promoters, game developers, sports teams, and/or retail businesses that include a NFC circuit 110 which transmits information that is used by the UE to obtain content from a content server and/or to unlock/activate content that may already reside on the UE relating. For example, the NFC circuit 110 may transmit information that contains a URL to particular content stored on a content server, which is accessible through a data network, that can be retrieved by downloading/streaming the music or game, photographic image(s) relating to the music/game/business, promotional information relating to the music/game/business, discount that can be redeemed to purchase or temporarily access the music/game, and/or that can be used when purchasing through the business.

[0058] The information may contain a URL that points to server location that can provide a plurality of content themes that can be provided to the UE, contain a theme ID that specifies a particular content theme that can be provided to the UE, and/or contain a unique ID, such as an ID that is unique from other accessory NFC circuits, that is used to obtain a user/UE specific license to content.

[0059] For example, an online retailer may sell or otherwise provide phone covers having visible, e.g., printed, branding relating to the online retailer or partner thereof and including a NFC circuit which transmits information that can be used by the UE to download a retail application from a content server, and which may further provide a discount coupon that be used when purchasing through the online retailer. By way of another example, a restaurant may sell or otherwise provide phone covers having visible branding relating to the restaurant and/or a business partner, e.g., a movie studio, music artist, sports team, etc. being promoted by the restaurant, and which provides a URL to a location on a content server having promotional information relating to the restaurant and/or the business partner. Other business models that may beneficially use NFC enabled accessories to provide content to users can include sponsorship businesses, charitable businesses, telecommunication provider businesses, movie studios/distributors, music studios/distributors, and retailers. The NFC enabled accessories can encourage and facilitate collaborative business relationships between accessory manufacturers, UE manufacturers, UE operators, and/or content providers to distribute content through UEs for use by targeted users.

[0060] Information received by a UE from the cover NFC circuit may provide a limited duration license, a limited number of use license, a partially paid-up subscription-based license, or a fully paid-up perpetual license for use of defined content on the UE. A content license may require continuing presence of the cover NFC circuit, such that removal of the cover from the UE automatically terminates the license and disables use of the content. The cover NFC circuit may thereby control licensing of content.

[0061] In the embodiment of FIG. 3, the UE 300 can communicate information through the radio access transceiver 330 to a content server to, for example, download an application program for execution by the processor 320 of the UE 300. The UE 300 may obtain from the content server text, graphics, photographic images (e.g., background display wallpaper, locked screen display wallpaper, etc.), an electronic book, movie, television program, and/or other content for display on the display device 326 of the UE 300, and/or music (e.g., song, ringtone, etc.) or other audio content to be played through the speaker 340 of the UE 300. In a further embodiment, the accessory NFC circuit 110 transmits a product code or other information to the UE NFC circuit 310 that activates functionality within the user equipment 300. The UE 300 may communicate through the radio access transceiver 330 to the content server to, for example, obtain an activation code for an application hosted by the UE 300.

Controlling Activation of Accessory NFC Circuit

[0062] As explained above, NFC enabled covers for UEs can be sold to consumers to provide applications that are executable by the UEs, activate operational features of the UEs, and/or to provide other content to the UE. Because activation of the accessory NFC circuit 110 causes transmission of information that can be used to obtain applications, movies, music, and other proprietary and valuable content, it can be important to control who obtains such information. For example, it is envisioned that NFC enabled accessories can be displayed within stores for sale or otherwise made publicly accessible. It can therefore be important to prevent unauthorized reading of information from the accessory NFC circuit 110 by a person who, for example, seeks to obtain access to the content without purchasing the accessory.

[0063] Some embodiments of the present disclosure are directed to controlling how the accessory NFC circuit 110 is initially or subsequently activated. One or more of these embodiments can be used to prevent a person from using a UE or other NFC reader device to activate an accessory NFC circuit 110 to read information until actions are taken to allow such activation of the NFC circuit 110.

Shielding by a Removable Conductive Sticker

[0064] FIG. 4 illustrates an accessory 100 having a NFC circuit 110. The NFC circuit 110 is covered by a removable conductive sticker 400 that is configured according to one embodiment and positioned over the NFC circuit 110 to shield the NFC circuit 110 from NFC signals generated by an adjacent NFC reader device. The conductive sticker 400 may include conductive (e.g., metal) mesh wiring or a conductive (e.g., metal) layer that extends across at least a major portion of the antenna 108, extends across the entire antenna 108, or extends across the entire NFC circuit 110 to shield the antenna 108 from NFC signals that are generated by an adjacent NFC reader device. The conductive portion of the sticker 400 may be electrically connected to a ground plane of the NFC circuit 110 to raise a voltage of the ground plane responsive to shielded NFC signals and, thereby, nullify any inductive coupling of the NFC signals to the antenna 108. The NFC circuit 110 can be enabled for activation by removing (e.g., peeling-off) the conductive sticker 400.

[0065] Removing the conductive sticker 400 eliminates the shielding and enables the NFC circuit 110 to be inductively powered by NFC signals from a NFC reader device. A user may therefore be instructed to remove the conductive sticker 400 after purchasing or otherwise receiving the accessory 100 to enable initial activation of the accessory NFC circuit 110. The conductive sticker 400 may be reinstalled, e.g., reattached to its original position, after the user has operated the UE 300 to read information from the accessory NFC circuit 110. Reinstalling the conductive sticker 400 can prevent an unauthorized other NFC reader device from reading information from the accessory NFC circuit 110 and, thereby, prevent unauthorized access to the applications, operational features, and/or other content authorized to the user by possession of the accessory 100.

[0066] FIG. 5 illustrates some other embodiments of a removable conductive sticker 500 that electrically connects to one or more locations on the antenna 108, a ground plane of the NFC circuit 100, and/or to another circuit node of the NFC circuit 100. The conductive sticker 500 may include conductive, e.g., metal, mesh wiring, a conductive, e.g., metal, layer, or conductive line. The conductive sticker 500 may electrically connect two locations on the antenna 108 to render the antenna 108 inoperable for receiving sufficient power from NFC signals from a NFC reader device to prevent operational powering of the NFC circuit 110. In one embodiment, the conductive sticker 500 connects an end portion 109a of the antenna 108 that is remote from the transceiver circuit 110 and another portion 109b of the antenna 108 that is adjacent to the transceiver circuit 104, thereby providing a short-circuit across the antenna 108. The antenna 108 may be covered by a protective layer but have one or more openings, e.g. via holes, exposed through the protective layer that are configured to allow electrical connection between the exposed portion(s) of the antenna 108 and the conductive sticker 500.

[0067] In another embodiment, the conductive sticker 500 electrically connects the antenna 108 to a ground plane of the NFC circuit 110 to short-circuit the antenna 108. Accordingly, the ground plane may also be covered by a protective layer having openings that expose a portion of the ground plane for electrical connection to the conductive sticker 500.

[0068] In another embodiment, the conductive sticker 500 electrically connects the antenna 108 to a circuit node between the transceiver circuit 104 and the charging circuit 106 to render the charging circuit 106 incapable of generating sufficient power to operate the NFC circuit 110.

[0069] Removing the conductive sticker 500 eliminates the electrical connection therethrough and enables inductive powering of the NFC circuit 110 by NFC signals from a NFC reader device, such as the user equipment 300. A user may therefore be instructed to remove the conductive sticker 500 after purchasing or otherwise receiving the accessory 100 to enable initial activation of the NFC circuit 110 of the accessory 100. The conductive sticker 500 may be reinstalled, e.g. reattached to its original position, after the user has operated the UE 300 to read information from the accessory NFC circuit 110. Reinstalling the conductive sticker 500 can prevent an unauthorized other NFC reader device from reading information from the accessory NFC circuit 110 and, thereby, prevent unauthorized access to the applications, operational features, and/or other content authorized to the user by possession of the accessory 100.

Conductive Bag for Shielding Accessory NFC Circuit

[0070] FIG. 6 illustrates the accessory 100 that is within a conductive bag 600. The conductive bag 600 may include conductive, e.g., metal, mesh wiring or a conductive (e.g., metal) layer that extends entirely around the NFC circuit 110 and may extend entirely around the accessory 100 residing within the conductive bag 600. The conductive bag 600 shields the NFC circuit 110 therein from NFC signals generated by a NFC reader device and, thereby, prevents operational powering of the NFC circuit 110. While the accessory 100 is within the conductive bag 600, a user cannot energize the NFC circuit 110 to receive information therefrom. Thus, the conductive bag 600 can prevent unauthorized access to (e.g., theft of) information from the NFC circuit 110 before the accessory 110 is purchased or other provided to an authorized user.

[0071] A user may therefore be instructed to remove the accessory 100 from the conductive bag 600 before attempting to operate the UE 300 to read or otherwise activate the accessory NFC circuit 110.

Accessory Configured as a Removable Film

[0072] FIG. 7 illustrates a film 700 that can be removably attached to a major surface of the UE 300. The film 700 includes a NFC circuit 110. The NFC circuit 110 may be attached to the film 700, e.g., adhesively connected thereto, or may be at least partially disposed or entire enclosed within a material of the film 700.

[0073] In one embodiment, one surface of the film 700 has an adhesive or sticky surface that can adhere to a back surface of the UE 300, such a back surface that is opposite to a front surface having a display or user interface. A user may thereby adhere the film 700 to a surface of the UE 300 to enable the UE NFC circuit 310 to read information from the accessory NFC circuit 110.

[0074] The film NFC circuit 110 communicate information to the UE 300 is used to customize operation of the UE 300 and/or that is used by the UE 300 to obtain content from a content server through a communication network. For example, the film NFC circuit 110 may identify a set of parameters used by the UE 300 to customize operation for a geographic region of the world and/or to comply with telecommunication operator preferences. When the UE 300 is initially set up, it can read the parameters from the film NFC circuit 110 and control its initial setup responsive thereto. A user can be instructed to remove (e.g., peel off) the film 700 after completion of the initial UE setup to avoid potential interference from the film NFC circuit 110 when the NFC circuit 310 of the UE 300 communicates with other NFC communication devices.

[0075] FIG. 8 illustrates the film 700 applied to the UE 300 of FIG. 7. A conductive sticker 500 has been connected to the film to shield the accessory NFC circuit 110 from NFC signals from the UE 300 and/or from another NFC device. The conductive sticker 500 may be configured according to one or more of the embodiments of FIGS. 4 and 5.

[0076] The conductive sticker 500 may shield the NFC circuit 110 from NFC signals from a NFC reader device other than the 300 UE. For example, as shown in FIG. 8, the conductive sticker 500 may be on a side of the film 700 that is opposite to a side of the film 700 contacting the UE 300. The conductive sticker 500 can operate to shield the covered NFC circuit 110 from NFC signals from a NFC device which would need to penetrate through the conductive sticker 500 to energize the NFC circuit 110, while allowing the NFC circuit 110 to communicate with the NFC circuit 310 within the UE 300. Such operation may be advantageous to prevent/inhibit reading of information from the NFC circuit 110 by a device other than the UE 300.

[0077] The conductive sticker 500 may be configured to reduce the effective communication range of the NFC circuit 110 so as to reduce the ability of another NFC reader device to receive information from the NFC circuit 110 while the film 700 is attached to the UE 300. The conductive sticker 500 may, for example, electrically connect to one or more locations on the antenna 108 to reduce the effective length of the antenna 108 and/or inductive coupling efficiency of the antenna 108. The antenna 108 may be covered by material of the film 700, which material may be patterned to provide one or more openings exposing a location(s) on the antenna 108 that is electrically connectable to the conductive sticker 500. The one or more locations can be selected to enable the NFC circuit 310 of the UE 300 to communicate with the NFC circuit 110 of the film 700, while effectively preventing another further spaced apart NFC reader device from communicating with the NFC circuit 110 (e.g., prevent a NFC reader device more remote than the UE 300 from being able to operationally power the NFC circuit 110 through inductive coupling and/or prevent the NFC reader device from receiving information transmitted by the NFC circuit 110).

Point-of-Sale Communication of Information from NFC Enabled Accessory

[0078] FIG. 9 illustrates a data flow diagram and flowchart of operations that can be performed by a point-of-sale terminal 900, a content server 910, and a UE 300 to obtain and use information from an accessory NFC circuit tag (NFC tag) to provide an application, operational feature, and/or content to the UE 300.

[0079] Referring to FIG. 9, the point-of-sale terminal 200, such as a retail sale checkout terminal, can be operated to scan (block 920) the NFC tag to obtain information therefrom. The point-of-sale terminal 900 generates (block 922), based on the information from the NFC tag, a message that can contain a URL to a location of an application, operational feature, and/or other content that is stored on the content server 910, a tag ID or unique identifier for the NFC tag, a request for a defined operational feature, user data that identifies contact information for the user and/or identifies the UE, such as a mobile terminal ID, network address, telephone number, etc. The point-of-sale terminal 900 communicates (block 924) the message to the content server 910.

[0080] The content server 910 may validate (block 926) information in the message to confirm that the UE 300 is authorized to receive content. If the information is not properly validated the operations can cease, otherwise the operations can continue by recording (block 928) user data and other information contained in the message to, for example, document what content has been provided to the UE 300. The content server 910 obtains (block 930) that content, which as explained above may include an application, authorization information to activate an operational feature, a movie, music, game, promotional information, discount coupon, etc. The content is communicated (block 932) to the user equipment 300.

[0081] Depending upon characteristics of the received content, the UE 300 may install (block 934) an application, game, background image, such as an image displayed as background in the display device 326 of the UE 300. The UE 300 may use data read from the NFC circuit 110 to set, change, or defined features of the application. The UE may activate (block 936) an operational feature provided by executable program code and/or may activate content that resides in or is downloaded to the UE 300. The UE may play (block 938) a movie, music, or other multimedia content that is downloaded and/or streamed from the content server 910.

[0082] Other communications may occur between the point of sale terminal 900 and the content server 910, and/or between the content server 910 and the user equipment 300 during the operations of blocks 920-938 and/or in addition to those operations to control access to and use of the content by the UE 300.

Controlling Application Installation and Content Operation Using NFC Enabled Accessories

[0083] FIG. 10 illustrates a data flow diagram and flowchart of operations that can be performed by a UE 300 and a content server 910 to obtain and use information from an accessory NFC circuit to provide an application, operational feature, and/or other content to the UE 300.

[0084] Referring to FIG. 10, the UE 300 is operated to scan (block 1000) the NFC tag to obtain information therefrom. The UE 300 communicates (block 1002) an application request message based on the information from the NFC tag. The application request message may contain a URL to an application stored on the content server 910.

[0085] The content server 910 may validate (block 1004) information in the application request message to confirm that the UE 300 is authorized to receive an application. If the information is not properly validated the operations can cease, otherwise the operations can continue by recording (block 1006) a UE ID and/or information from the NFC tag to, for example, document what application will be provided to which UE. The content server 910 obtains (block 1008) the application. The application is communicated (block 1010) to the user equipment 300 (e.g., downloaded from an applications store).

[0086] The UE 300 installs (block 1012) and executes the application. Features of the application may be set, changed, or defined based on the content, such as to request location tracking, request access to user contact information, request access to communication interface(s), etc. The application obtains (block 1014) information relating to the user, the UE 300 (e.g., user login or other credentials, user name and/or contact information, unique UE identifier, etc.), and/or relating to a unique identifier obtained from the NFC tag, and communicates (block 1016) the information to the content server 910. The content server 910 can record (block 1018) the information and use the information to confirm that the UE 300 is authorized to receive content (e.g., hash the received information and compare to expected value) and to select among available content to be provided to the UE 300. The content server 910 communicates (block 1020) the content to the UE 300.

[0087] Depending upon characteristics of the received content, the application executed by the UE 300 can play the content (movie, music, game, multimedia content, etc.), use the content to activate an operational feature of the application, display a background image contained in the content (e.g., an image displayed as background in the display device 326 of the UE 300), display an electronic book contained in the content, display promotional information contained in the content, display a discount coupon contained in the content, etc.

[0088] One or more of the operations of blocks 1000-1022 may be performed once during initial downloading and playing of the content, or may be repetitively performed in response to each attempt by a user to play or otherwise use content through the UE 300. For example, operations of blocks 1000-1022 may be used to download and play a movie through an application on the UE 300, and then at least some of the operations of blocks 1000-1022 may be repeated when a user attempts to re-play the movie to confirm that NFC tag information is readable at that time. Thus, for example, a user may cease having authorization to play or otherwise use content when the NFC enabled cover is removed from the UE 300. The user may regain authorization to play or otherwise use content by reinstalling/attaching the NFC enabled cover to the UE 300 so that the NFC tag information can be properly scanned and used to enable use of the content. The NFC enabled cover or other accessory may thereby operate as a key that must be readable by the UE 300 to obtain continuing use of content.

[0089] Other communications may occur between the content server 910 and the user equipment 300 during the operations of blocks 1000-1022 and/or in addition to those operations to control access to and use of the content by the UE 300.

NFC Transmission Collision Avoidance with Controllable Transmission Time Delay

[0090] With the proliferation of NFC circuits, collisions may occur when a user equipment attempts to read one NFC circuit but unintentionally activates other nearby NFC circuits which all transmit time overlapping signals that can sufficiently interfere or become unreceivable by the user equipment. As explained herein, in some embodiments, the accessory 100 can be a cover that is attachable to (e.g., slid on) the UE 300 and/or is a stand that supports and holds the UE 300 in a defined orientation. The NFC circuit 110 of the accessory 100 can therefore be persistently positioned relatively very close to the NFC circuit 310 of the UE 300. The NFC circuit 110 would therefore become powered on and transmit whenever a user operates the UE 300 to attempt to communicate with a NFC circuit of another targeted device to obtain, e.g., read, information therefrom. The targeted device may be targeted device a retail point-of-sale terminals for credit/debit processing, a NFC tag on merchandise, etc. Because the NFC circuit 110 of the accessory 100 can be much closer to the NFC circuit 310 of the UE 300 then the NFC circuit of the targeted device and thereby provide higher power signals to the UE 300, transmissions from the NFC circuit 110 can interfere with or prevent the NFC circuit 310 of the UE 300 from receiving transmissions from the NFC circuit of the targeted device.

[0091] Some embodiments of the present disclosure are directed to avoiding time overlapping transmission of signals from a plurality of NFC devices and associated signal collisions at another NFC reading circuit, by controlling timing when signal transmissions are performed from NFC devices according to a controllable time delay.

[0092] In one embodiment, the accessory NFC circuit 110 is configured to delay transmission of data to the UE NFC circuit 310 until expiration of a defined delay time after the NFC circuit 110 has become sufficiently powered on to operate to transmit the data. Thus, for example, the transceiver circuit 104 can be configured to delay a defined time after it becomes powered on by the charging circuit 106 through inductive coupling to the UE NFC circuit 310, before transmitting data through the antenna 108. The NFC circuit 110 can include a transmission delay circuit 350 that is configured to be powered by the charging circuit 106 and to control the transceiver circuit 104 to delay its transmission of the data until expiration of a defined delay time such as after when the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data.

[0093] Delaying the accessory NFC circuit's 110 data transmission may avoid its NFC transmission overlapping in time the NFC transmission of a targeted device which is configured to transmit data immediately upon being powering on through coupling to the UE NFC circuit 310. The transmission delay time can therefore be used to avoid or reduce transmission collisions and, thereby, avoid or reduce interference with the ability of the UE NFC circuit 310 to communicate with a NFC circuit of a targeted device.

[0094] In some embodiments, the transmission delay time of one NFC circuit can be controlled by a delay setting signal that is received from another NFC circuit. For example, in one embodiment, the accessory NFC circuit 110 is configured to receive a delay setting signal transmitted by the UE NFC circuit 310, and to set the defined delay time based on the delay setting signal. The UE 300 may thereby communicate the delay setting signal through the UE NFC circuit 310 to control how long the accessory NFC circuit 110 delays from a defined event, such as after being powered on before transmitting data.

[0095] FIG. 11 illustrates operations and methods that can be performed by a NFC circuit to control its transmission delay time based on a received delay setting signal. Referring to FIG. 11, a first NFC circuit, such as accessory NFC circuit 110, receives (block 1100) a delay setting signal transmitted by a second NFC circuit, such as UE NFC circuit 310. The first NFC circuit sets (block 1102) a defined delay time based on the delay setting signal. The first NFC circuit then controls (block 1104) it's transceiver circuit to delay transmission of data until expiration of the defined delay time after the transceiver circuit has become sufficiently powered on to operate to transmit the data. Accordingly, in one embodiment, after the transceiver circuit is powered on and has become operationally able to transmit data, it will wait from that instant in time until the defined delay time has expired and then initiate transmission of the data.

[0096] In some embodiments the transmission delay circuit 350 determines when the defined delay time has expired based on, for example, counting oscillations of a signal emitted by the UE NFC circuit 310, counting oscillations of an internal clock signal, and/or based on charging of voltage/power levels from the charging circuit 106 while inductively coupled to the NFC circuit 310 and/or based on discharging a voltage/power levels from the charging circuit 106 while inductively coupled to or uncoupled from the NFC circuit 310. For example, the transmission delay circuit 350 may be configured to wait until a voltage/power level output from a rechargeable power circuit (e.g., capacitive circuit, battery, etc.) in the charging circuit 106 has dropped, such as during momentary or persistent decoupling from the NFC circuit 310, by an amount determined based on the defined transmission delay time before triggering the transceiver circuit 104 to initiate transmission of the data.

[0097] In some other embodiments, the transmission delay circuit 350 is configured to respond to the delay setting signal by disabling subsequent transmission of data by the transceiver circuit 104 until the NFC circuit 110 is powered off and back on. Accordingly, the delay setting signal can be transmitted by the UE NFC circuit 310 to disable transmission from the accessory NFC circuit 110.

[0098] An NFC circuit can be configured to autonomously set its transmission delay time based on detecting transmission collisions between NFC circuits, in accordance with some embodiments.

[0099] In the embodiment of FIG. 12, the transmission delay circuit 350 is configured to set (block 1200) the defined delay time based on determining that signals from another NFC circuit, such as a NFC circuit other than the UE NFC circuit 310, were received by the transceiver circuit 104 within a threshold time after the transceiver circuit 104 became sufficiently powered on to operate to transmit the data. The transmission delay circuit 350 then controls (block 1202) the transceiver circuit 104 to delay transmission of the data until expiration of the defined delay time after the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data. In one embodiment, the transmission delay circuit 350 is configured to set the defined delay time to disable transmission of the data by the transceiver circuit 104 until the NFC circuit 110 is subsequently powered off and back on.

[0100] In the embodiment of FIG. 13, the transmission delay circuit 350 is configured to set (block 1300) the defined delay time based on determining that signals from another NFC circuit, such as a NFC circuit other than the UE NFC circuit 310, were received by the transceiver circuit 104 while the transceiver circuit 104 is transmitting the data. The transmission delay circuit 350 then controls (block 1302) the transceiver circuit 104 to delay further transmission of the data until expiration of the defined delay time. In one embodiment, the transmission delay circuit 350 is configured to set the defined delay time to disable further transmission of the data by the transceiver circuit 104 until the NFC circuit 110 is subsequently powered off and back on.

[0101] An NFC circuit can be configured to set its transmission delay time based on how many times the NFC circuit has transmitted data, in accordance with some embodiments. Accordingly, when the NFC circuit transmits data during an overlapping time with another NFC circuit activated by the UE NFC circuit 310, subsequent transmissions by the NFC circuit will eventually be delay time shifted so that they may not interfere with the UE NFC circuit 310 receiving data from the other NFC circuit.

[0102] In the embodiment of FIG. 14, the transmission delay circuit 350 is configured to count (block 1400) a number of times the data has been transmitted by the transceiver circuit 104. The transmission delay circuit 350 sets (block 1402) the defined delay time based on the count. The transmission delay circuit 350 then controls (block 1404) the transceiver circuit 104 to delay transmission of data until expiration of the defined delay time after the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data.

[0103] In a further embodiment, the transmission delay circuit 350 changes the defined delay time from a first delay value to a longer second delay value based on the count exceeding a threshold count value. The first delay value may be zero while the second delay value may be a sufficiently large non-zero value to delay transmission sufficiently to likely avoid overlapping transmissions from another NFC circuit. The transmission delay circuit 350 may thereby selectively activate the transmission delay when the data has been transmitted a defined number of times.

[0104] In the embodiment of FIG. 15, the transmission delay circuit 350 is configured to incrementally increase (block 1500) the defined delay time based on each data transmission by the transceiver circuit 104 until a maximum delay time is reached. The transmission delay circuit 350 controls (block 1502) the transceiver circuit 104 to delay transmission of data until expiration of the defined delay time after the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data.

[0105] When the accessory NFC circuit 110 is configured to repetitively transmit data, the transmission delay circuit 350 may incrementally increase the time delay between the repetitive transmissions of the data through the transceiver circuit 104. Accordingly, although the accessory NFC circuit 110 may initially transmit signals that collide with signals transmitted by another NFC circuit, subsequent transmissions from the accessory NFC circuit 110 will become sufficiently delayed so that the UE NFC circuit 310 can receive the signals from the other NFC circuit. The amount of each incremental increase in the defined delay time can be set based on the transmission time of the data in one transmission repetition and/or based on an likely transmission time needed by another NFC circuit to transmit data to the UE NFC circuit 310.

[0106] Referring again to FIG. 3, the NFC circuit 110 can include a delay control switch 352. The delay control switch 352 is connected to the transmission delay circuit 350 and configured to be mechanically actuated by a user.

[0107] In one embodiment, while the delay control switch 352 is mechanically actuated the transmission delay circuit controls the transceiver circuit 104 to immediately transmit the data when it is sufficiently powered on to operate to transmit the data. In contrast, while the delay control switch 352 is not mechanically actuated the transmission delay circuit controls the transceiver circuit 104 to delay transmission of the data until expiration of the defined delay time after the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data.

[0108] In another embodiment, while the delay control switch 352 is mechanically actuated the transmission delay circuit controls the transceiver circuit 104 to delay transmission of the data until expiration of the defined delay time after the transceiver circuit 104 has become sufficiently powered on to operate to transmit the data. In contrast, while the delay control switch 352 is not mechanically actuated the transmission delay circuit controls the transceiver circuit 104 to be disabled from transmitting the data.

[0109] Corresponding operations and methods are now explained that can be performed by a user equipment to control the transmission delay time of a separate NFC circuit from which it can receive data. Referring to FIG. 16, the processor 320 of the UE transmits (block 1600) a delay setting signal through the UE NFC circuit to an accessory NFC circuit that controls a defined delay time that the accessory NFC circuit delays before beginning to transmit data after the accessory NFC circuit has become sufficiently powered on to operate to transmit the data.

[0110] In the embodiment of FIG. 17, the processor 320 is configured to transmit the delay setting signal through the UE NFC circuit 310 to the accessory NFC circuit 110 based on determining that signals from another NFC circuit (e.g., a NFC circuit of a targeted device) were received by the transceiver circuit within a threshold time after the transceiver circuit began emitting the signal to provide power through inductive coupling to the second NFC circuit of the accessory.

[0111] In the embodiment of FIG. 18, the processor 320 is configured to transmit the defined delay time through the UE NFC circuit 310 to the accessory NFC circuit 110 based on determining that signals from another NFC circuit (e.g., a NFC circuit of a targeted device) were received by the UE NFC circuit 310 while the UE NFC circuit 310 was receiving the data from the accessory NFC circuit 110 of the accessory.

[0112] Embodiments disclosed herein may thereby avoid or reduce occurrence of time overlapping transmission of signals from an accessory NFC circuit to improve the ability of a proximately located to communicate with a targeted NFC circuit.

[0113] In the above-description of various embodiments of the present invention, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense expressly so defined herein.

[0114] When a node is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another node, it can be directly connected, coupled, or responsive to the other node or intervening nodes may be present. In contrast, when an node is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another node, there are no intervening nodes present. Like numbers refer to like nodes throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.

[0115] As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, nodes, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, nodes, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.

[0116] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0117] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks.

[0118] A tangible, non-transitory computer-readable medium may include an electronic, magnetic, optical, electromagnetic, or semiconductor data storage system, apparatus, or device. More specific examples of the computer-readable medium would include the following: a portable computer diskette, a random access memory (RAM) circuit, a read-only memory (ROM) circuit, an erasable programmable read-only memory (EPROM or Flash memory) circuit, a portable compact disc read-only memory (CD-ROM), and a portable digital video disc read-only memory (DVD/BlueRay).

[0119] The computer program instructions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.

[0120] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0121] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, the present specification, including the drawings, shall be construed to constitute a complete written description of various example combinations and subcombinations of embodiments and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0122] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present invention. All such variations and modifications are intended to be included herein within the scope of the present invention.