HK1195962A - Methods and apparatus for improving nfc data exchange configuration parameter update mechanisms - Google Patents

Description

Method and apparatus for improving NFC data exchange configuration parameter update mechanism

Priority requirements according to 35U.S.C. § 119

This patent application claims priority from provisional application No.61/542,027 entitled "METHODS and apparatus FOR IMPROVING NFC DATA exchange configuration PARAMETER UPDATE mechanism" filed on 30.9.2011, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference.

Background

Aspects disclosed relate generally to communications between devices, and more particularly, to methods and systems for improving mechanisms for prompting a Near Field Communication (NFC) controller (NFCC) to update data exchange parameters for international standards organization data exchange protocol (ISO-DEP) communications between a Device Host (DH) and a remote NFC endpoint.

Technological advances have resulted in smaller and more powerful personal computing devices. For example, there currently exist a wide variety of portable personal computing devices, including wireless computing devices, such as portable wireless telephones, Personal Digital Assistants (PDAs), and paging devices, each of which are small, lightweight, and easy for users to carry. More specifically, for example, portable wireless telephones further include cellular telephones that communicate voice and data packets over wireless networks. Many such cellular telephones are being manufactured with ever increasing computing capabilities and, as such, are becoming tantamount to small personal computers and hand-held PDAs. Moreover, such devices are capable of communications using a wide variety of frequencies and applicable coverage areas, such as cellular communications, Wireless Local Area Network (WLAN) communications, NFC, and so forth.

When NFC is implemented, the NFC-enabled device may initially detect the NFC tag and/or the target device. Thereafter, communication between the NFC devices may use ISO-DEP. The current draft of the NFC forum controller interface (NCI) specification does not address all functionality required to use ISO-DEP.

Currently, NCI defines two RF interfaces that devices can use when communicating using the ISO-DEP RF protocol: ISO-DEP and frame. If the NFC controller is relatively complex, it may be able to handle the ISO-DEP protocol and may use the ISO-DEP RF interface, thereby reducing the processing load on the device host. The frame RF interface may be used if the NFC controller is weak and/or has known defects. In such an implementation, the NFC controller only passes protocol activation, data, and protocol deactivation messages to the device host for processing. Currently, when activating ISO-DEP using a frame RF interface based on NFC-B RF technology, there are parameters in the activation command and response (ATTRIB command and ATTRIB response) that the NFC controller needs, but because the NFC controller only passes data to the DH, the specification does not provide a mechanism to the NFCC to learn these values.

Accordingly, improved apparatus and methods for providing improved mechanisms for updating data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint using interfaces (such as a frame RF interface and an ISO-DEP RF protocol) may be desired.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its purpose is to present some concepts of one or more aspects as a prelude to the more detailed description that is presented later.

Various aspects are described relating to an improved mechanism for prompting a NFCC to update data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint. In an example, with an NFC device, a DH may be configured to: receiving an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology; determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement; generating an RF parameter update command that includes the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters; and sending the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters.

According to related aspects, a method for prompting a NFCC to update improved mechanisms for data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint. The method can include receiving, by a DH, an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology. The method may also include determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. Further, the method may include generating an RF parameter update command that includes the one or more data exchange parameters corresponding to the one or more currently relevant data exchange parameters that are determined to be different. Further, the method may include sending the generated RF parameter update command to the NFCC to prompt the NFCC to update one or more corresponding current relevant data exchange parameters with one or more data exchange parameters included in the RF parameter update command.

Another aspect relates to a communication device. The apparatus may include means for receiving, by a DH, an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology. The communications device may also include means for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. Further, the communications device may include means for generating an RF parameter update command that includes the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters. Further, the communications apparatus can include means for transmitting the generated RF parameter update command to the NFCC to prompt the NFCC to update one or more corresponding current relevant data exchange parameters with one or more data exchange parameters included in the RF parameter update command.

Another aspect relates to a communication device. The apparatus may include a DH configured to receive an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology. The DH may be further configured to determine that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement. Further, the DH may be configured to generate an RF parameter update command that includes one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters. Further, the DH may be configured to send the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters with the one or more data exchange parameters included in the RF parameter update command.

Another aspect relates to a computer program product, which can have a computer-readable medium including code for receiving, by a DH, an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology. The computer-readable medium may also include code for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding currently relevant data exchange parameters that the NFCC is configured to implement. Further, the computer-readable medium may include code for generating an RF parameter update command that includes the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters. Further, the computer-readable medium may include code to send the generated RF parameter update command to the NFCC to prompt the NFCC to update one or more corresponding current relevant data exchange parameters with one or more data exchange parameters included in the RF parameter update command.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the present description is intended to include all such aspects and their equivalents.

Brief Description of Drawings

The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements, and in which:

fig. 1 is a block diagram of a wireless communication system in accordance with an aspect;

fig. 2 is a schematic diagram of a wireless communication system according to an aspect;

fig. 3 is a block diagram of an NFC environment in accordance with an aspect;

FIG. 4 is a flow diagram depicting an example of updating parameters when using an ISO-DEP RF protocol with respect to a frame RF interface with NFC-B technology, according to an aspect;

fig. 5 is a call flow diagram depicting an example of updating parameters when an ISO-DEP RF protocol is used in a listening mode with respect to a frame RF interface with NFC-B technology, according to an aspect;

fig. 6 is a call flow diagram depicting an example of updating parameters when an ISO-DEP RF protocol is used in polling mode with respect to a frame RF interface with NFC-B technology, according to an aspect;

fig. 7 is a functional block diagram of an example architecture of a communication device in accordance with an aspect; and

fig. 8 is a functional block diagram of an example communication system for updating parameters when using an ISO-DEP RF protocol with respect to a frame RF interface with NFC-B technology, according to an aspect.

Detailed Description

Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It should be understood, however, that such aspect(s) may be practiced without these specific details.

As described herein, an NFC target device and/or reader/writer may be identified by the device when the device is within range of the NFC target device and/or the reader/writer's coverage area. Thereafter, the device may obtain information sufficient to allow communication to be established. One form of communication that may be established is an ISO-DEP communication link. Communication between devices may be accomplished through a variety of NFC RF technologies such as, but not limited to, NFC-A, NFC-B, and the like.

In general, when activating the NFC-B based ISO-DEP polling side using the frame RF interface, the DH may select values for several data exchange communication parameters (e.g., minimum TR0, minimum TR1, minimum TR2, inhibit SoS, and inhibit EoS). The DH may use some or all of these values in an activate command it sends to the remote NFC endpoint. Because the local NFC controller may need some or all of these values, the DH may then pack these values into octets (as defined in table 4 below) in RF _ PARAMETER _ UPDATE _ CMD (RF _ PARAMETER _ UPDATE _ command) and send RF _ PARAMETER _ UPDATE _ CMD to the NFCC. The NFCC may then extract the correlation values and use them appropriately for subsequent data exchange.

In addition, when activating the NFC-B based ISO-DEP listening side using the frame RF interface, the NFC controller may pass an activation command it receives from a remote NFC endpoint to the Device Host (DH). The DH may interpret the received activation command and assume it is valid, may extract several values from the command (e.g., minimum TR0, minimum TR1, minimum TR2, inhibit SoS, and inhibit EoS), or it may select values for some or all of these variables. The DH may then pack these values into octets in RF _ PARAMETER _ UPDATE _ CMD (as defined below in table 4) and send RF _ PARAMETER _ UPDATE _ CMD to the NFCC. The NFCC may then extract these values and use them appropriately for subsequent data exchanges.

Fig. 1 illustrates a wireless communication system 100 in accordance with various exemplary embodiments of the present invention. The input power 102 is provided to a transmitter 104 to generate a radiated field 106 for providing energy transfer. The receiver 108 is coupled to the radiated field 106 and generates output power 110 for storage or consumption by a device (not shown) coupled to the output power 110. Both the transmitter 104 and the receiver 108 are separated by a distance 112. In an exemplary embodiment, the transmitter 104 and receiver 108 are configured according to a mutual resonance relationship, and where the resonance frequency of the receiver 108 is very close to the resonance frequency of the transmitter 104, transmission losses between the transmitter 104 and the receiver 108 are minimal when the receiver 108 is located in the "near field" of the radiated field 106.

The transmitter 104 further comprises a transmit antenna 114 for providing a means for energy transmission. The receiver 108 comprises a receive antenna 118 as means for energy reception. The transmit and receive antennas are sized according to the application and device associated therewith. As mentioned, efficient energy transfer is performed by coupling most of the energy in the near field of the transmit antenna to the receive antenna without propagating most of the energy in the electromagnetic wave to the far field. When in the near field, a coupling mode may be formed between the transmit antenna 114 and the receive antenna 118. The area around antennas 114 and 118 where such near-field coupling may occur is referred to herein as a coupling-mode region.

Fig. 2 is a schematic diagram of an example near field wireless communication system. The transmitter 204 includes an oscillator 222, a power amplifier 224, and a filter and matching circuit 226. The oscillator is configured to generate a signal at a desired frequency, which is adjustable in response to the adjustment signal 223. The oscillator signal may be amplified by a power amplifier 224 with an amplification amount responsive to a control signal 225. A filter and matching circuit 226 may be included to filter out harmonics or other unwanted frequencies and match the impedance of the transmitter 204 to the transmit antenna 214.

The receiver 208 may include a matching circuit 232 and a rectifier and switching circuit 234 to generate a DC power output to charge a battery 236 as shown in fig. 2 or to power a device (not shown) coupled to the receiver. A matching circuit 232 may be included to match the impedance of the receiver 208 to the receive antenna 218. The receiver 208 and the transmitter 204 may communicate over separate communication channels 219 (e.g., bluetooth, zigbee, cellular, etc.).

Referring to fig. 3, a block diagram of a communication network 300 according to an aspect is illustrated. The communication network 300 may include a communication device 310, the communication device 310 may be in communication with a remote NFC endpoint 330 using one or more NFC technologies 326 (e.g., NFC-A, NFC-B, NFC-F, etc.) through an antenna 324. In an aspect, remote NFC endpoint 330 is operable to communicate over various interfaces, such as frame RF interface 334 and ISO-DEP RF interface 336, using NFC module 332. In another aspect, the communication device 310 and the remote NFC endpoint 330 may establish an ISO-DEP communication link using an ISO-DEP RF protocol. In yet another aspect, the communication device 310 is operable to be connected to an access network and/or a core network (e.g., a CDMA network, a GPRS network, a UMTS network, and other types of wired and wireless communication networks).

In an aspect, communication device 310 may include an NFC controller 312, an NFC Controller Interface (NCI) 322, and a device host 340. In an aspect, device host 340 is operable to obtain information from remote NFC endpoint 330 via remote NFC endpoint 330NFC module 330 through NCI322 and NFC controller 312.

In an aspect, during ISO-DEP communications, the NFC controller 312 may operate using the ISO-DEP RF interface 316. When operating using ISO-DEP RF interface 316, NFC controller 312 is operable to change various parameters associated with data exchange between device host 340 and remote NFC endpoint 330 using data exchange change module 318.

The device host 340 may include, among other modules, a parameter selection module 342 and a parameter update module 344. In an operational aspect, NFC controller 312 may act as a relay when using frame RF interface 314 and only communicate messages between communication device 310 device host 340 and remote NFC endpoint 330. In this regard, NFC controller 312 may not interpret the content of messages relayed between communication device 310 device host 340 and remote NFC endpoint 330. For example, when using the frame RF interface 314 and NFC-B technology, the NFC controller 312, acting as a polling or as a listening device, cannot interpret the activation message (e.g., ATTRIB command or ATTRB response) and therefore cannot update the data exchange parameters included within the activation message. In this regard, the device host 340 can extract data exchange parameters from the activation message, whether received from the remote NFC endpoint 330 or created by the DH 340. In an aspect, the data exchange parameters may include any combination of a minimum guard time (TR 0), a minimum synchronization time (TR 1), a minimum frame delay time (TR 2), a quench sequence start (SoS), and a quench sequence end (EoS). Parameter update module 344 may communicate some or all of the data exchange values obtained by parameter selection module 342 to NFC controller 312. Further, communications from parameter update module 344 may prompt NFC controller 312 to change various data exchange configuration parameters. In other words, since NFC controller 312 may not detect the content of the activation message, device host 340 may use parameter update module 344 to communicate the necessary data exchange parameters. The parameter update module 344 may use messaging as defined in tables 1, 2, 3, and 4.

Table 1: control messages for parameter update requests

Table 2: control messages for parameter update response

Table 3: type-length-value (TLV) encoding for RF communication parameter IDs

Table 4: NFC-B data exchange configuration parameters

References within tables 2 and 3 (e.g., table 89, table 91, table 92) are made in the context of the NFC forum NCI specification. Additionally, a reference ([ number ]) is made within table 4 in the context of the NFC forum digital specification. Table 4 is not present in the NFC forum NCI specification. As used herein, with reference to tables 1-4, there may be situations where DH340 may attempt to communicate updates to certain data exchange parameters in NFC controller 312. During such a scenario, DH340 sends a PARAMETER UPDATE command (e.g., RF _ PARAMETER _ UPDATE _ CMD) to NFC controller 312. Table 1 provides example parameter update commands.

Continuing with the operational aspect described above, referring to tables 2-4, when NFC controller 312 receives an UPDATE command (e.g., RF _ PARAMETER _ UPDATE _ CMD), NFC controller 312 responds with an UPDATE response (e.g., RF _ PARAMETER _ UPDATE _ RSP). Table 2 provides an example parameter update response. In table 2, a "status" field indicates whether the setting of these RF communication parameters is successful. For example, the "state" of STATUS _ OK (state _ good) should indicate that all RF communication parameters have been set within the NFC controller 312 to the values included in the parameter update command. Conversely, if DH340 attempts to set PARAMETERs that are not suitable for NFC controller 312, NFC controller 312 responds with a PARAMETER UPDATE response (e.g., RF _ PARAMETER _ UPDATE _ RSP) with a "STATUS" field of "INVALID" (e.g., STATUS _ INVALID _ PARAM), and the response may include one or more INVALID RF communication PARAMETER IDs. In an aspect, in the event some parameters are invalid, the remaining valid parameters are still used by NFC controller 312. Once NFC controller 312 has communicated a PARAMETER UPDATE response (e.g., RF _ PARAMETER _ UPDATE _ RSP), NFC controller 312 uses the values of the data exchange PARAMETER values that were successfully updated at the appropriate time. For polling devices, the updated data exchange parameter values may be used upon receipt. For listening devices, the updated data exchange parameter values may be used (e.g., as defined in the current NCI specification) upon the next RF frame having been sent.

Referring to table 3, the "NFC-B data exchange configuration" parameter specifies a number of NFC-B related values to be used by the NFCC during subsequent data exchanges. The parameters include values for minimum TR0, minimum TR1, minimum TR2, SoS suppression, and EoS suppression. The octet format is defined in table 4. In operation, not all values within the "NFC-B data exchange configuration" parameter may be relevant in a given mode of operation. In this regard, the NFC controller may update only those values that are relevant to a given mode of operation.

Thus, communication network 300 provides an environment that allows for the updating of data exchange parameters in NFC controller 312 for ISO-DEP communications between DH340 and remote NFC endpoint 330 while NFC controller 312 is using a frame RF interface and NFC-B technology.

Fig. 4-6 illustrate various methodologies in accordance with various aspects of the presented subject matter. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts or sequence steps, it is to be understood and appreciated that the claimed subject matter is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the claimed subject matter. It should be further appreciated that the methodologies disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methodologies to computers. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.

Referring now to fig. 4, an example flow diagram is illustrated depicting a process 400 for updating data exchange configuration parameters for ISO-DEP communications between a DH and a remote NFC endpoint.

In an optional aspect, the data exchange process may be implemented using the ISO-DEP RF protocol with respect to the frame RF interface at block 402. In an aspect, NFC-B technology is used by the NFCC to receive and/or transmit data associated with an implemented process.

At block 404, the DH may exchange activation messages with a remote NFC endpoint. In an aspect, the activation message is an ATTRIB command and an ATTRIB response and includes one or more parameters associated with the data exchange configuration. At block 406, the DH may compare the relevant data exchange parameters currently used by the NFCC with the data exchange parameters provided in the received activation command.

If the DH determines that none of the relevant parameters are different at block 406, then in an optional aspect, the DH may initiate communication with a remote NFC endpoint using the implemented ISO-DEP protocol at block 408. Conversely, if at block 406 the DH determines that one or more of the relevant data exchange parameter values are different, then at block 410 the DH generates and transmits a parameter update message to the NFCC to prompt the NFCC to update the currently used data exchange parameters to those included in the parameter update message. The update may be performed upon receipt of an update message or may be delayed to a time after transmission of the next RF frame. In an aspect, the parameter update message may be formatted using the fields described in tables 1-4. In particular, the update may be immediate for the polling device and delayed for the listening device. As mentioned in tables 1-4, the reference to the NFC-B data exchange configuration table may be included in the RF parameter update command.

In an optional aspect, at block 412, the DH may receive an RF PARAMETER response (e.g., RF _ PARAMETER _ UPDATE _ RSP) indicating successful receipt and/or implementation of the data exchange PARAMETERs included in the RF PARAMETER UPDATE command. Once the NFCC has updated the one or more parameters, the process may continue to optional block 408 to allow the DH to initiate communication with a remote NFC endpoint using the implemented ISO-DEP protocol.

Referring now to fig. 5, an example listener side call flow diagram is illustrated that describes a system for updating parameters for ISO-DEP communications between a DH and a remote NFC endpoint using a NFCC. As depicted in fig. 5, NFC environment 500 may include a device host 502, a NFCC504, and a remote NFC endpoint 506. Device host 502 may be implemented in a polling mode or a listening mode. As used herein, a polling device is a device that has sent an initial command that the listening device replies with a response. Subsequently, the two devices will take turns "transmitting" and "receiving". In other words, the polling device performs the role of a reader/writer, and the listening device performs the role of a card emulator.

In act 508, the DH502 may initiate communication to use the frame RF interface for ISO-DEP RF protocol communication. In act 510, a sense request and response communication may be sent between NFCC504 and remote NFC endpoint 506. In an aspect, in the case of using the NFC-B technology, the sensing request may be SENSB _ REQ and the sensing response may be SENSB _ RES. In act 512, an activation command (e.g., ATTRIB command) is transmitted from remote NFC endpoint 506 to NFCC 504. Because communication has been established using the frame RF interface, the message may be received as an RF frame (ATTRIB command) message. At act 514, NFCC504 may identify the message as a valid activate command indicating the ISO-DEP protocol. At act 516, NFCC504 may determine that the RF interface used by ISO-DEP protocol communications is a "frame. In response to receiving a communication from a remote NFC endpoint, NFCC504 may transmit an RF interface activation notification (e.g., RF _ INTF _ ACTIVATED _ NTF) message to DH502 in act 518. In an aspect, the notification may indicate that the protocol is ISO-DEP and that the interface is a "frame". Further, in response to detecting that the ISO-DEP protocol is a "frame," NFCC504 transmits an activation command to DH502 in act 520.

In act 522, DH502 may parse the activation command and extract data exchange parameters applicable to NFCC504, and may generate an update message including the relevant extracted data exchange parameters. In an aspect, the data exchange parameters include some or all of minimum TR0, minimum TR1, minimum TR2, SoS suppression, and EoS suppression. In act 524, DH502 may transmit an update message to NFCC 504. In an aspect, the UPDATE message is an RF _ PARAMETER _ UPDATE _ CMD (RF _ PARAMETER _ UPDATE _ command) and includes the relevant extracted data exchange PARAMETERs. Additionally, the determined data exchange parameters may be chosen to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

In act 526, the NFCC504 may store the received data exchange PARAMETERs, and in act 526, an RF PARAMETER UPDATE response (e.g., RF _ PARAMETER _ UPDATE _ RSP) may be sent by the NFCC504 to the DH 502. In act 528, the DH502 transmits a response to the activate command, and in block 530, the response is relayed to the remote NFC endpoint 506. At act 532, the NFCC504 may update the data exchange parameters and the updated NFC-B data exchange parameters may be used for subsequent exchanges of ISO-DEP blocks at the specified time.

As such, the data exchange parameters associated with the NFCC504 are updated according to the activation command received at act 512, and at act 534, the NFCC504 may receive an ISO-DEP chunk from the remote NFC endpoint 506, which the remote NFC endpoint 506 may relay to the DH502 at act 536. The received ISO-DEP block may be processed using an ISO-DEP listening side protocol in act 538, and in act 540, the ISO-DEP block may be transmitted to the NFCC504 to be relayed to the remote NFC endpoint 506 in act 552.

Referring now to fig. 6, an example polling-side call flow diagram is illustrated that describes a system for updating parameters for ISO-DEP communications between a DH and a remote NFC endpoint using a NFCC. As depicted in fig. 6, NFC environment 600 may include a device host 602, an NFCC604, and a remote NFC endpoint 606.

In act 608, the DH602 may initiate communication to use the frame RF interface for ISO-DEP RF protocol communication. In act 610, a sense request and response communication may be sent between NFCC604 and remote NFC endpoint 606. In an aspect, in the case of using the NFC-B technology, the sensing request may be SENSB _ REQ and the sensing response may be SENSB _ RES. At act 612, NFCC604 may transmit an RF interface activation notification (e.g., RF _ INTF _ ACTIVATED _ NTF) message to DH 602. In an aspect, the notification may indicate that the protocol is ISO-DEP and that the interface is a "frame". When acting in polling mode, DH602 may generate an activation command (e.g., ATTRIB command) that may be transmitted to NFCC604 at act 616. Because NFCC604 is using the frame RF interface, NFCC604 may act as a relay and communicate the activation command to remote NFC endpoint 606. The remote NFC endpoint 606 may receive the activation command, generate an activation response, and transmit the activation response (e.g., ATTRIB response) at act 618. At act 620, NFCC604 transmits an activation response to DH 602.

At act 622, DH602 may parse the activation response and extract data exchange parameters applicable to NFCC604, and may generate an update message including the relevant extracted data exchange parameters. In an aspect, the data exchange parameters include some or all of minimum TR0, minimum TR1, minimum TR2, SoS suppression, and EoS suppression. In act 624, DH602 may transmit an update message to NFCC 604. In an aspect, the UPDATE message is RF _ PARAMETER _ UPDATE _ CMD and includes the relevant extracted or selected data exchange PARAMETERs. Additionally, the determined data exchange parameters may be selected to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

At act 626, NFCC604 updates the polling-side parameter values with values included in the command for use during the data exchange. At act 628, an RF PARAMETER UPDATE response (e.g., RF _ PARAMETER _ UPDATE _ RSP) may be transmitted by NFCC604 to DH602 to indicate that the values have been updated.

As such, data exchange parameters associated with NFCC604 are updated according to the activation response received at act 620, and DH602 may generate an ISO-DEP block as part of an ISO-DEP communication with remote NFC endpoint 606 at act 630. At act 632, the data block is communicated to NFCC604, which relays the data to remote NFC endpoint 606 at act 634. The remote NFC endpoint 606 responds to the NFCC604 with an ISO-DEP block transmission in act 636, and the response may be relayed to the DH602 in act 638.

Turning now also to fig. 7, with reference to fig. 3, an example architecture of a communication device 700 is illustrated. As depicted in fig. 7, communication device 700 includes a receiver 702 that receives a signal from, for instance, a receive antenna (not shown), performs typical actions on (e.g., filters, amplifies, downconverts, etc.) the received signal, and digitizes the conditioned signal to obtain samples. Receiver 702 can comprise a demodulator 704 that can demodulate received symbols and provide them to a processor 706 for channel estimation. Processor 706 can be a processor dedicated to analyzing information received by receiver 702 and/or generating information for transmission by a transmitter 720, a processor that controls one or more components of device 700, and/or a processor that both analyzes information received by receiver 702, generates information for transmission by transmitter 720, and controls one or more components of communication device 700. In addition, signals for transmission by transmitter 720 may be prepared by a modulator 718, which modulator 718 may modulate signals for processing by processor 706.

Communication device 700 can additionally comprise memory 708, memory 708 operatively coupled to processor 706 and can store data to be transmitted, received data, information related to available channels, TCP flows, data associated with analyzed signal and/or interference strength, information related to an assigned channel, power, rate, or the like, and any other information suitable for estimating a channel and communicating via a channel.

Further, the processor 706, the receiver 402, the transmitter 420, the NFCC730, and/or the DH760 can provide means for receiving an activation message from the NFCC730 that is using a frame RF interface based on NFC-B RF technology, means for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC730 is configured to implement, means for generating an RF parameter update command that includes the one or more data exchange parameters determined to be different corresponding to the one or more current relevant data exchange parameters, and means for sending the generated RF parameter update command to the NFCC730 to prompt the NFCC730 to update the one or more corresponding current relevant data exchange parameters.

It will be appreciated that the data store (e.g., memory 708) described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include Read Only Memory (ROM), programmable ROM (prom), electrically programmable ROM (eprom), electrically erasable prom (eeprom), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as Synchronous RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct memory bus (Rambus) RAM (DRRAM). The memory 708 of the subject systems and methods may comprise, without being limited to, these and any other suitable types of memory.

In another aspect, the communication device 700 may include the NCI 750. In an aspect, NCI750 is operable to enable communication between DH760 and NFC controller 730.

Communication device 700 may include NFC controller 730. In an aspect, NFC controller 730 is operable to obtain information from other devices (such as remote NFC endpoint 330) through NCI 750. During ISO-DEP communications, NFC controller 730 may operate using frame RF interface 314 or ISO-DEP interface 734. When operating using ISO-DEP interface 734, NFC controller 730 is operable to change various parameters associated with communications between device host 760 and remote NFC endpoint 330 using data exchange change module 736.

The device host 760 may include, among other modules, a parameter selection module 762 and a parameter update module 764. In an operational aspect, when using frame RF interface 732, NFC controller 730 may act as a relay and communicate messages only between device host 760 and a remote NFC endpoint. In this regard, NFC controller 730 may not interpret the content of messages relayed between device host 760 and a remote NFC endpoint. For example, when using frame RF interface 732 and NFC-B technology, NFC controller 730 cannot interpret the activation message (e.g., ATTRIB command or ATTRIB response) and therefore cannot update the data exchange parameters included within the activation message. In such an aspect, device host 760 may extract data exchange parameters from activation messages exchanged with a remote NFC endpoint. In an aspect, the data exchange parameters may include any combination of a minimum guard time (TR 0), a minimum synchronization time (TR 1), a minimum frame delay time (TR 2), a quench sequence start (SoS), and a quench sequence end (EoS). Parameter update module 764 may communicate the relevant data exchange parameters obtained by parameter selection module 762 to NFC controller 730. Further, communications from parameter update module 764 may prompt NFC controller 730 to change various data exchange configuration parameters. In other words, since NFC controller 730 may not detect the content of the activation command, device host 760 may use parameter update module 764 to communicate the necessary data exchange parameters to NFC controller 730. As mentioned above, the parameter update module 764 may use messaging as defined in tables 1, 2, 3, and 4. Again as described above, the parameter update module 764 may update as it has received the parameter update command, or it may save these values (e.g., stored in memory 708) for updating after the next RF frame has been sent (e.g., as mentioned in the current NCI specification).

Additionally, the communication device 700 may include a user interface 740. The user interface 740 may include an input mechanism 742 for generating input into the communication device 700 and an output mechanism 744 for generating information for consumption by a user of the communication device 700. For example, input mechanism 742 may include mechanisms such as keys or a keyboard, a mouse, a touch screen display, a microphone, and so forth. Further, for example, output mechanism 744 may include a display, an audio speaker, a haptic feedback mechanism, a Personal Area Network (PAN) transceiver, and so forth. In the illustrated aspect, the output mechanism 744 may comprise a display operative to present media content in an image or video format or an audio speaker that presents media content in an audio format.

Fig. 8 is an apparatus 800 that improves a mechanism for prompting a NFCC to update data exchange parameters for ISO-DEP communications between a DH and a remote NFC endpoint. It is to be appreciated that apparatus 800 is represented as including functional blocks, which may represent functions implemented by a processor, software, or combination thereof (e.g., firmware).

As such, the apparatus 800 includes a logical grouping 802 of electrical components that can act in conjunction. For example, logical grouping 802 may include means for receiving an activation message from a NFCC that is using a frame RF interface based on NFC-B RF technology (block 804). For example, in an aspect, the apparatus 804 may include the DH760 of the communication device 700 and/or the processor 706 of the communication device 700. In an aspect, the activation message may be an ATTRIB command or ATTRIB response. In another aspect, the means for receiving 804 may be further configured to receive an RF parameter update response from the NFCC indicating that the one or more data exchange parameters have been successfully updated. In this regard, the RF PARAMETER UPDATE response may be an RF _ PARAMETER _ UPDATE _ RSP message.

Further, logical grouping 802 may include means for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement (block 806). For example, in an aspect, the means for determining 806 may comprise the DH760 of the communication device 700 and/or the processor 706 of the communication device 700. In an aspect, the one or more data exchange parameters may include minimum TR0, minimum TR1, minimum TR2, inhibit SoS, EoS, and the like. In another aspect, the one or more data exchange parameters may be determined to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

In an optional aspect, logical grouping 802 may include means for generating an RF parameter update command that includes the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters (block 808). For example, in an aspect, the means for generating 808 may comprise the DH760 of the communication device 700 and/or the processor 706 of the communication device 700. In an aspect, the means for generating 808 may be configured to include a reference to an NFC-B data exchange configuration table in the RF parameter update command, the table including a bitmask indicating the one or more data exchange parameters.

In another optional aspect, logical grouping 802 may include means for sending the generated RF parameter update command to the NFCC to prompt the NFCC to update one or more corresponding current relevant data exchange parameters with one or more data exchange parameters included in the RF parameter update command (block 810). For example, in an aspect, the means for transmitting 810 may comprise the DH760 of the communication device 700 and/or the processor 706 of the communication device 700. In this regard, in the case where the NFCC is in a polling mode, the activation message may be an activation response, and the NFCC may update one or more data exchange parameters prior to transmitting the RF parameter update response to the DH. In another aspect, the activation message may be an activation command in case the NFCC is in listening mode. In such an aspect, the NFCC may store the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, and the means for sending may be further configured to send an activation response to the NFCC, and the NFCC may update the one or more data exchange parameters after sending the activation response message to the remote NFC endpoint. In an aspect, the RF PARAMETER UPDATE response may include an RF _ PARAMETER _ UPDATE _ RSP message.

Additionally, apparatus 800 can include a memory 812 that retains instructions for executing functions associated with electrical components 804, 806, 808, and 810. While shown as being external to memory 812, it is to be understood that one or more of electrical components 804, 806, 808, and 810 can exist within memory 812. In an aspect, for example, the memory 812 may be the same as or similar to the memory 708 (fig. 7). In another aspect, the memory 812 may be associated with a DH760 and/or an NFCC 730.

As used in this application, the terms "component," "module," "system," and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal.

In addition, various aspects are described herein in connection with a terminal, which may be a wired terminal or a wireless terminal. A terminal can also be called a system, device, subscriber unit, subscriber station, mobile device, remote station, remote equipment (ME), remote terminal, access terminal, user terminal, communication device, user agent, user device, or User Equipment (UE). A wireless terminal may be a cellular telephone, a satellite telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing device connected to a wireless modem. Moreover, various aspects are described herein in connection with a base station. A base station may be utilized for communicating with wireless terminal(s) and may also be referred to as an access point, node B, or some other terminology.

Furthermore, the term "or" is intended to mean "inclusive or" rather than "exclusive or". That is, unless specified otherwise, or clear from context, the phrase "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, the phrase "X employs a or B" is satisfied by any of the following examples: x is A; x is B; or X employs both A and B. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form.

The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system may implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA2000, and so on. UTRA includes wideband CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA systems may implement radio technologies such as global system for mobile communications (GSM). The OFDMA system may implement radio technologies such as evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in literature from an organization named "third Generation partnership project" (3 GPP). In addition, cdma2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3 GPP 2). Further, such wireless communication systems may additionally include peer-to-peer (e.g., mobile-mobile) ad hoc network systems that often use unpaired unlicensed spectrum, 802.xx wireless LANs, bluetooth, near field communication (NFC-A, NFC-B, NFD-F, etc.), and any other short-or long-range wireless communication technologies.

Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Combinations of these approaches may also be used.

The various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Further, at least one processor may comprise one or more modules operable to perform one or more of the steps and/or actions described above.

Further, the steps and/or actions of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. In addition, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in some aspects, the steps and/or actions of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.

In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may also be termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, Digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks (disks) usually reproduce data magnetically, while discs (discs) usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/or aspects, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or aspects as defined by the appended claims. Furthermore, although elements of the described aspects and/or modalities may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or aspect may be utilized with all or a portion of any other aspect and/or aspect, unless stated otherwise.

Claims (40)

1. A method of communication, comprising:

receiving, by a Device Host (DH), an activation message from a Near Field Communication Controller (NFCC) that is using a frame Radio Frequency (RF) interface based on NFC-B RF technology;

determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement;

generating an RF parameter update command comprising the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters; and

sending the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters with the one or more data exchange parameters included in the RF parameter update command.

2. The method of claim 1, wherein the one or more data exchange parameters comprise at least one of: minimum guard time (TR 0), minimum synchronization time (TR 1), minimum frame delay time (TR 2), quench sequence start (SoS), or quench sequence end (EoS).

3. The method of claim 1, wherein the generating further comprises:

including in the RF parameter update command a reference to a NFC-B data exchange configuration table, the NFC-B data exchange configuration table including a bitmask indicating the one or more data exchange parameters.

4. The method of claim 1, further comprising:

receive an RF parameter update response from the NFCC indicating that the one or more data exchange parameters have been successfully updated.

5. The method of claim 4, wherein the NFCC is in a polling mode, wherein the activation message is an activation response, and wherein the NFCC updates the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH.

6. The method of claim 4, wherein the NFCC is in a listening mode, wherein the activation message is an activation command, wherein the NFCC stores the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, wherein the method further comprises sending an activation response to the NFCC, and wherein the NFCC updates the one or more data exchange parameters after sending the activation response message to the remote NFC endpoint.

7. The method of claim 1, wherein the activation message comprises an ATTRIB command or ATTRIB response.

8. The method of claim 1, wherein the RF PARAMETER UPDATE command comprises an RF _ PARAMETER _ UPDATE _ CMD message.

9. The method of claim 4, wherein the RF PARAMETER UPDATE response comprises an RF _ PARAMETER _ UPDATE _ RSP message.

10. The method of claim 1, wherein the one or more data exchange parameters are determined to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

11. A computer program product, comprising:

a computer-readable medium comprising code for:

receiving, by a Device Host (DH), an activation message from a Near Field Communication Controller (NFCC) that is using a frame Radio Frequency (RF) interface based on NFC-B RF technology;

determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement;

generating an RF parameter update command comprising the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters; and

sending the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters with the one or more data exchange parameters included in the RF parameter update command.

12. The computer program product of claim 11, wherein the one or more data exchange parameters include at least one of: minimum guard time (TR 0), minimum synchronization time (TR 1), minimum frame delay time (TR 2), suppress SoS, or suppress EoS.

13. The computer program product of claim 11, wherein the computer-readable medium further comprises code for:

including in the RF parameter update command a reference to a NFC-B data exchange configuration table, the NFC-B data exchange configuration table including a bitmask indicating the one or more data exchange parameters.

14. The computer program product of claim 11, wherein the computer-readable medium further comprises code for:

receive an RF parameter update response from the NFCC indicating that the one or more data exchange parameters have been successfully updated.

15. The computer program product of claim 14, wherein the NFCC is in a polling mode, wherein the activation message is an activation response, and wherein the NFCC updates the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH.

16. The computer program product of claim 14, wherein the NFCC is in a listening mode, wherein the activation message is an activation command, wherein the NFCC stores the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, wherein the computer-readable medium further comprises code for sending an activation response to the NFCC, and wherein the NFCC updates the one or more data exchange parameters after sending the activation response message to the remote NFC endpoint.

17. The computer program product of claim 11, wherein the activation message comprises an ATTRIB command or an ATTRIB response.

18. The computer program product of claim 11, wherein the RF PARAMETER UPDATE command comprises an RF _ PARAMETER _ UPDATE _ CMD message.

19. The computer program product of claim 14, wherein the RF PARAMETER UPDATE response comprises an RF _ PARAMETER _ UPDATE _ RSP message.

20. The computer program product of claim 11, wherein the one or more data exchange parameters are determined to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

21. An apparatus for communication, comprising:

means for receiving, by a Device Host (DH), an activation message from a Near Field Communication Controller (NFCC) that is using a frame Radio Frequency (RF) interface over NFC-B RF technology;

means for determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement;

means for generating an RF parameter update command comprising the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters; and

means for sending the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters with the one or more data exchange parameters included in the RF parameter update command.

22. The apparatus of claim 21, wherein the one or more data exchange parameters comprise at least one of: minimum guard time (TR 0), minimum synchronization time (TR 1), minimum frame delay time (TR 2), suppress SoS, or suppress EoS.

23. The apparatus of claim 21, wherein the means for generating is further configured to:

including in the RF parameter update command a reference to a NFC-B data exchange configuration table, the NFC-B data exchange configuration table including a bitmask indicating the one or more data exchange parameters.

24. The apparatus of claim 21, wherein the means for receiving is further configured to receive an RF parameter update response from the NFCC indicating that the one or more data exchange parameters have been successfully updated.

25. The apparatus of claim 24, wherein the NFCC is in a polling mode, wherein the activation message is an activation response, and wherein the NFCC updates the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH.

26. The apparatus of claim 24, wherein the NFCC is in a listening mode, wherein the activation message is an activation command, wherein the NFCC stores the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, wherein the means for sending is further configured to send an activation response to the NFCC, and wherein the NFCC updates the one or more data exchange parameters after sending the activation response message to the remote NFC endpoint.

27. The apparatus of claim 21, wherein the activation message comprises an ATTRIB command or ATTRIB response.

28. The apparatus of claim 21, wherein the RF PARAMETER UPDATE command comprises an RF _ PARAMETER _ UPDATE _ CMD message.

29. The apparatus of claim 24, wherein the RF PARAMETER UPDATE response comprises an RF _ PARAMETER _ UPDATE _ RSP message.

30. The apparatus of claim 21, wherein the one or more data exchange parameters are determined to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.

31. An apparatus for communication, comprising:

a Device Host (DH) configured to:

receiving an activation message from a Near Field Communication Controller (NFCC) that is using a frame Radio Frequency (RF) interface based on NFC-B RF technology;

determining that one or more data exchange parameters included in the activation message are different from one or more corresponding current relevant data exchange parameters that the NFCC is configured to implement;

generating an RF parameter update command comprising the one or more data exchange parameters determined to be different corresponding to the one or more currently relevant data exchange parameters; and

sending the generated RF parameter update command to the NFCC to prompt the NFCC to update the one or more corresponding current relevant data exchange parameters with the one or more data exchange parameters included in the RF parameter update command.

32. The apparatus of claim 31, wherein the one or more data exchange parameters comprise at least one of: minimum guard time (TR 0), minimum synchronization time (TR 1), minimum frame delay time (TR 2), suppress SoS, or suppress EoS.

33. The apparatus of claim 31, wherein the DH is further configured to:

including in the RF parameter update command a reference to a NFC-B data exchange configuration table, the NFC-B data exchange configuration table including a bitmask indicating the one or more data exchange parameters.

34. The apparatus of claim 31, wherein the DH is further configured to:

receive an RF parameter update response from the NFCC indicating that the one or more data exchange parameters have been successfully updated.

35. The apparatus of claim 34, wherein the apparatus further comprises the NFCC, wherein the NFCC is in a polling mode, wherein the activation message is an activation response, and wherein the NFCC is configured to update the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH.

36. The apparatus of claim 34, wherein the apparatus further comprises the NFCC, wherein the NFCC is in a listening mode, wherein the activation message is an activation command, wherein the NFCC is configured to store the one or more data exchange parameters prior to transmission of the RF parameter update response to the DH, wherein the DH is further configured to send an activation response to the NFCC, and wherein the NFCC is configured to update the one or more data exchange parameters after sending the activation response message to the remote NFC endpoint.

37. The apparatus of claim 31, wherein the activation message comprises an ATTRIB command or ATTRIB response.

38. The apparatus of claim 31, wherein the RF PARAMETER UPDATE command comprises an RF _ PARAMETER _ UPDATE _ CMD message.

39. The apparatus of claim 34, wherein the RF PARAMETER UPDATE response comprises an RF _ PARAMETER _ UPDATE _ RSP message.

40. The apparatus of claim 31, wherein the one or more data exchange parameters are determined to align with one or more parameters communicated as part of an ISO-DEP RF protocol update process.