HK1193691B - Methods and apparatuses for improving nfc parameter update mechanisms - Google Patents

Description

Method and apparatus for improving NFC parameter update mechanism

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

This patent application claims priority from provisional application No.61/500,803 entitled "Methods and Apparatus for improving NFC Parameter Update mechanisms" filed 24/6.2011, which is assigned to the assignee of the present application and is hereby expressly incorporated herein by reference.

Background

FIELD

The disclosed aspects 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 parameter values for peer-to-peer communications between a Device Host (DH) and a remote NFC endpoint.

Background

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, communications between the peer NFC devices may use an NFC data exchange protocol (NFC-DEP) communication link. Currently, the NFC forum controller interface ("NCI") specification does not address all functionality required to create an NFC-DEP communication link.

For example, the active specification defines a mechanism for changing bit rate as part of the device activation process, however, when a peer target uses the NCI frame Radio Frequency (RF) interface, the DH may interpret the message that the bit rate may change, while the NFCC may not interpret the message. There is currently no mechanism for the DH to inform the NFCC that the bit rate must be changed for subsequent peer-to-peer communication. Furthermore, there is no mechanism to change the buffer size that can occur with changes in bit rate. In another example, the current specification does not explicitly specify the operation for link creation when using the NCINFC-DEP RF interface.

Accordingly, improved apparatus and methods for providing improved mechanisms for updating parameter values for peer-to-peer communications between a DH and a remote NFC endpoint using interfaces (such as a frame RF interface and an NFC-DEP RF interface) may be desirable.

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 providing improved mechanisms for updating parameter values for peer-to-peer communications between a DH and a remote NFC endpoint. In one example, a DH associated with an NFC device may be configured to use a frame RF interface to determine that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of a remote NFC endpoint. The DH may be further configured to communicate the one or more parameter values to the NFC controller using a parameter update message. In another example, a NFCC associated with a NFC device may be configured to receive a parameter selection request message including one or more parameter values using a NFC-DEP interface. The NFCC may be further configured to determine to implement the one or more parameter changes based on the received one or more parameter values. The NFCC may also be configured to communicate an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values.

According to related aspects, methods are described for providing improved mechanisms for updating parameter values for peer-to-peer communications between a DH and a remote NFC endpoint. The method may include determining, by the DH using a frame RF interface, that one or more parameter values included in the parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint. The method may also include communicating the one or more parameter values to the NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

Another aspect relates to a communication device. The apparatus may include means for determining, by a DH using a frame RF interface, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of a remote NFC endpoint. The communications apparatus can also include means for communicating the one or more parameter values to the NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

Another aspect relates to a communication device. The apparatus may include a DH configured to determine, using a frame RF interface, that one or more parameter values included in the parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint. The DH may be further configured to communicate the one or more parameter values to the NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

Another aspect relates to a computer program product, which may have a computer-readable medium including code for determining, by a DH, using a frame RF interface, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of a remote NFC endpoint. The computer-readable medium may also include code for communicating the one or more parameter values to the NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

According to a related aspect, another method for providing an improved mechanism for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint is described. The method may include receiving, by the NFC controller, a parameter selection request message including one or more parameter values using the NFC-DEP interface. Further, the method may include determining, based on the received one or more parameter values, that one or more parameter changes are to be implemented. The method may also include communicating an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values.

Another aspect relates to a communication device. The communications apparatus can include means for receiving, by an NFC controller using an NFC-DEP interface, a parameter selection request message including one or more parameter values. Further, the communications apparatus can include means for determining to implement one or more parameter changes based on the received one or more parameter values. The apparatus may also include means for communicating an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values.

Another aspect relates to a communication device. The apparatus may include a NFCC configured to receive, using a NFC-DEP interface, a parameter selection request message including one or more parameter values. The NFCC may also be configured to determine to implement the one or more parameter changes based on the received one or more parameter values. The NFCC may be further configured to communicate an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values.

Another aspect relates to a computer program product that may have a computer-readable medium including code for receiving, by an NFC controller, a parameter selection request message including one or more parameter values using an NFC-DEP interface. The computer-readable medium may include code for determining to implement one or more parameter changes based on the received one or more parameter values. The computer-readable medium may also include code for communicating an activation message to the DH indicating values to which the NFC controller changed the one or more parameter values.

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 the 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 in accordance with an aspect.

FIG. 3 is a block diagram of an NFC environment, according to one aspect;

FIG. 4 is a flow diagram depicting an example for updating parameter values when using a frame RF interface, in accordance with an aspect;

FIG. 5 is a flow diagram depicting another example for updating parameter values while using a frame RF interface, in accordance with an aspect;

FIG. 6 is a flow diagram depicting an example system for updating parameter values when using a NFC-DEP interface, according to one aspect;

FIG. 7 is a flow diagram depicting another example system for updating parameter values when using a NFC-DEP interface, in accordance with an aspect;

FIG. 8 is a call flow diagram depicting an example for updating parameter values when using a frame RF interface, in accordance with an aspect;

FIG. 9A is a call flow diagram depicting an example for updating parameter values when an NFC-DEP interface is used and a DH is in a listening mode, according to one aspect;

FIG. 9B is a call flow diagram depicting an example of updating parameter values when an NFC-DEP interface is used and the DH is in a polling mode, according to one aspect; and

FIG. 10 is a functional block diagram of an example architecture of a communication device, according to an aspect;

FIG. 11 is a block diagram of an example communication system for updating parameter values while using a frame RF interface, according to one aspect; and

fig. 12 is a block diagram of an example communication system for updating parameter values when using a NFC-DEP interface, according to one 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 aspect(s) may be practiced without these specific details.

Generally, a NFC target device and/or tag may be identified by a device when the device is within range of the coverage area of the NFC device and/or tag. Thereafter, the device may obtain information sufficient to allow communication to be established. One form of communication that may be established is a peer-to-peer communication link (e.g., an NFC-DEP based communication link). As described herein, communication between devices may be accomplished through a variety of NFC RF technologies, such as, but not limited to, NFC-A, NFC-B, NFC-F, and the like. Also, different NFC technologies may be implemented during different phases of communication (e.g., an activation phase, a data exchange phase, etc.). Furthermore, different bit rates may be used at different stages of communication.

As described herein, given NCI command and response messages, the DH may use the NCI command and response messages to update certain RF communication parameter values as part of an RF interface activation procedure. Further, an example table is provided that includes standardized text regarding parameter values in the commands and responses. This proposal includes text setting forth the activation procedures for both the frame RF interface and the NFC-DEP RF interface. Changes and/or additions to the current standard are included for activation procedures with respect to both the polling device and the listening device, and with respect to both RF interfaces (e.g., frames and NFC-DEPs).

The word "wireless power" is used herein to mean any form of energy associated with an electric field, a magnetic field, an electromagnetic field, or otherwise transferred from a transmitter to a receiver without the use of a physical electromagnetic conductor.

Fig. 1 illustrates a wireless communication system 100 in accordance with various exemplary embodiments of the present invention. Input electrical energy 102 is provided to a transmitter 104 to generate a radiation field 106 for providing energy transfer. The receiver 108 is coupled to the radiated field 106 and generates output electrical energy 110 for storage or consumption by a device (not shown) coupled to the output electrical energy 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 to provide a means for energy transfer. 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 occurs by coupling most of the energy in the near field of the transmit antenna to the receive antenna rather than propagating most of the energy in the electromagnetic wave to the far field. When in the near field, a coupling mode may be generated between the transmit antenna 114 and the receive antenna 118. The area around the antennas 114 and 118 where this 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 (Osc) 222, a Power Amplifier (PA) 224, and a filtering 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, the power amplifier 224 having an amount of amplification responsive to a control signal 225. A filtering 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.).

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 119 (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 communicate with a peer target device 330 through an antenna 324 using one or more NFC technologies 326 (e.g., NFC-A, NFC-B, NFC-F, etc.). In an aspect, the peer target device 330 may be configured to communicate using an NFC module 332, the NFC module 332 using various interfaces, such as a frame RF interface 334 and an NFC-DEP interface 336. In another aspect, the communication device 310 and the peer target device 330 may establish a peer-to-peer communication link using NRC-DEP. In yet another aspect, the communication device 310 may be configured to connect 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, the NFC controller 312 may be configured to obtain information from the peer target device 330 through the peer target device NFC module 332 through the NCI 322. During peer-to-peer communication, NFC controller 312 may operate using frame RF interface 314 or NFC-DEP interface 316. When operating using the NFC-DEP interface 316, the NFC controller 312 can be configured to use the rate change module 318 to change various parameter values associated with communications between the device host 340 and the peer target device 330. The device host 340 may include, among other modules, a parameter selection module 342 and a parameter update module 344.

In one operational aspect, when using the frame RF interface 314, the NFC controller 312 can act as a relay and communicate messages only between the communication device 310 device host 340 and the peer target device 330. In such aspects, the NFC controller 312 may not interpret the content of the message relayed between the communication device 310 device host 340 and the peer target device 330. For example, when using the frame RF interface 314, the NFC controller cannot interpret the PSL _ REQ and thus cannot update the communication parameter values included within the PSL _ REQ. In such an aspect, the device host 340 may determine, through the parameter selection module 342, that a bit rate change may be requested. The parameter selection module 342 may receive a parameter selection request (e.g., PSL-REQ) message from the peer target device 330. Parameter update module 344 may communicate the selection of parameter 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 parameters such as receive and/or transmit data rate, bit rate, RF technology, buffer size, maximum payload size, and the like.

The parameter selection request message may include parameters such as, but not limited to, a Device Identifier (DID), a data rate received by the initiator (DRI), a data rate sent by the initiator (DSI), a maximum frame length value (FSL), and the like. Since the NFC controller 312 may not detect the content of the parameter selection request, the device host 340 may use the parameter update module 344 to communicate the necessary parameter values. The parameter update module 344 may use messaging as defined in tables 1, 2, and 3.

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

As used herein, referring to tables 1-3, there may be situations where DH340 may attempt to communicate updates to certain RF communication parameter values in NFC controller 312 after RF discovery has begun. 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. The command may be for any RF communication state. In operation, not all RF communication parameter settings are permissible in all modes of operation. In this way, DH340 is responsible for ensuring that the values sent to NFC controller 312 are correct. In other words, in the aspect described above, the NFC controller 312 has no obligation to check whether a given parameter value is permissible.

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 3, the "status" field indicates whether the setting of these RF communication parameter values was successful. For example, the "STATUS" of STATUS _ OK (STATUS _ good) should indicate that all RF communication parameter values 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 that some parameter values are invalid, the remaining valid parameter values are still used by the 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 PARAMETER values that were successfully updated.

Referring to table 3, the "RF technology and mode" parameter specifies the RF technology and mode to be used by the NFC controller 312 in transmitting and receiving. Permitted RF technology and mode values for a given RF interface activation may be found with reference to current standards (not included).

Referring to table 3, the "transmit bit rate" parameter specifies the bit rate to be used by the NFC controller 312 when transmitting. For polling devices this is the polling device to listening device bit rate, and for listening devices this is the listening device to polling device bit rate. The permitted bit rate value for a given RF interface activation can be found with reference to the current standard (not included).

Referring to table 3, the "reception bit rate" parameter specifies the bit rate to be used by the NFC controller at reception. For polling devices this is the listening device to polling device bit rate, and for listening devices this is the polling device to listening device bit rate. The permitted bit rate value for a given RF interface activation can be found with reference to the current standard (not included).

Referring to table 3, the "maximum payload size" parameter specifies the maximum number of payload bytes for NFC controller 312 to use when transmitting. In an aspect, the NFC controller cannot send more than the number of payload bytes specified in the "maximum payload size" parameter to the peer target device 330 in a single transmission. In an aspect, a value of 0 is interpreted by NFC controller 312 to mean 256 bytes. The permitted maximum payload size value for a given RF interface activation may be found with reference to current standards (not included).

In another operational aspect, when NFC-DEP interface 316 is used to facilitate communications between communication device 310 device host 340 and peer target device 330, NFC controller 312 can interpret the content of the message being communicated. In such aspects, NFC controller 312 may determine whether rate change module 318 may be used based on the presence or absence of the parameter selection message. When the device host 340 is in the polling mode, the device host 340 may transmit a parameter selection request message. When device host 340 is in a listening mode, NFC controller 312 can wait to determine whether a message received after the attribute message is a Data Exchange Protocol (DEP) message or a parameter selection request message. When the received message is a parameter selection request message, NFC controller 312 may interpret the contents of the message to determine whether a parameter change may be implemented using rate change module 318. Further, when the message is a parameter selection request message, the NFC controller 312 may use an activation notification message to communicate any updated parameter values to the device host 340. By way of example and not limitation, table 5 provides an activation notification message that NFC controller 312 may generate.

Table 5: example Notification messages

As used herein, a polling mode may be defined as a mode during which a device is transmitting, while a listener mode may be defined as a mode during which a device is available to receive communications. As mentioned above, the tables referenced in table 5 correspond to the tables described in the NFC standard (not included).

Referring to table 5, depending on the selected target handle/RF protocol, NFC controller 312 may perform a protocol activation procedure before activating the RF interface. Protocol activation may be different for each RF interface. In general, the target handle value conveyed in RF _ ACTIVATE _ NTF is valid until the state is changed to an IDLE state (e.g., RFST _ IDLE). When all phases before the RF interface activation are successfully performed, the NFC controller 312 sends a notification (e.g., RF _ ACTIVATE _ NTF) with information about the activated RF interface (RF interface type). The NFC controller 312 may also include activation parameter values. The activation parameter values may be different for each RF interface, while the other parameter values in the RF _ ACTIVATE _ NTF may be the same as those used in the RF _ DISCOVER _ NTF (RF _ DISCOVER _ notify) message. The NFC controller 312 includes in the notification the RF technology and mode used during the activation process (e.g., activates the RF technology and mode). The NFC controller 312 also includes any RF technology specific parameter values that may have been collected during the activation process. These included parameter values may be defined for the RF technology and mode values used during the activation process. If the RF PROTOCOL is a PROTOCOL _ NFC _ DEP (PROTOCOL _ NFC _ DEP) or PROTOCOL _ ISO _ DEP (PROTOCOL _ ISO _ DEP), the NFC controller 312 includes bit rates for poll-to-listen and listen-to-poll established during activation, and bit rates for poll-to-listen and listen-to-poll to be used for subsequent data exchanges. If the RF PROTOCOL is different from the PROTOCOL _ NFC _ DEP or PROTOCOL _ ISO _ DEP, the NFC controller 312 may include a poll-to-listen and a snoop-to-poll bit rate that may be used for subsequent data exchanges.

In one operational aspect, if the RF PROTOCOL is PROTOCOL _ NFC _ DEP, NFC controller 312 includes the RF technology and mode established during activation and to be used for subsequent data exchanges. Note that if the bit rate is changed during activation due to the value specified in BITR _ NFC _ DEP (bit rate _ NFC _ DEP), the RF technology and mode may be different from the one that defines the characteristics of the RF technology specific parameter values. If the RF PROTOCOL is determined to be other than PROTOCOL _ NFC _ DEP, NFC controller 312 may include RF technology and mode values that may be used for subsequent data exchanges. Further, the notification generated by NFC controller 312 can provide information to device host 340 regarding the selected receive and transmit data rates available for subsequent data exchanges.

In this way, the communication device 300 provides an environment that allows the interface to be used to update parameter values for peer-to-peer communications between the DH340 and a remote NFC endpoint.

4-9B 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 parameter values for peer-to-peer communication between a DH and a remote NFC endpoint.

At block 402, a DH associated with a communication device may determine, using a frame radio frequency, RF interface, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of a remote NFC endpoint. In an aspect, when the DH is configured in the polling mode, the DH determining may further include receiving an activation stimulus message from the NFC controller, and generating a parameter selection request message to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message. In such aspects, one or more parameters included in the parameter selection request message may be different from one or more corresponding parameters used during discovery. In another aspect, wherein the DH is configured in a listening mode, the DH determination may be based on a parameter selection request message received from the remote NFC endpoint. In an aspect, the parameter values may include RF technology and mode parameters, transmit bit rate parameters, receive bit rate parameters, maximum payload size parameters, and the like. Further, in such aspects, the RF technology and mode parameters may indicate use of NCF-a technology, NFC-B technology, NFC-F technology, or the like. In an aspect, the remote NFC device may be a remote NFC tag, a reader/writer device, a remote peer target device, or the like.

At block 404, the DH may communicate the one or more parameter values to the NFC controller using a parameter update message. In an aspect, the parameter update message may prompt the NFC controller to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

Referring now to fig. 5, an example flow diagram is illustrated depicting another process 500 for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint.

At block 502, a discovery process may be performed. In an aspect, the device host may transmit a RF _ DISCOVER _ MAP (RF _ discovery _ MAP) to the NFC controller indicating the type of RF interface to use (e.g., frame, NFC-DEP, etc.) and other items. Further, during discovery, the NFCC may communicate with a remote NFC endpoint. The communications may include sensing requests and responses (e.g., SENS _ REQ/RES), attribute requests and responses (e.g., ATR _ REQ/RES), and so forth. In the aspect depicted in fig. 5, the frame RF interface is enabled.

At block 504, the DH may receive a parameter selection request message from a remote NFC endpoint discovered during discovery. At block 506, the DH may compare the parameter values currently used by the DH to the parameter values provided in the received parameter selection request message.

If the DH determines that none of the parameter values are different at block 506, the DH may initiate communication with the remote NFC endpoint using the DEP protocol at block 508. Conversely, if at block 506 the DH determines that one or more of the parameter values are different, then at block 512 the DH generates and transmits a parameter update message to the NFCC to prompt the NFCC to update the currently used parameter values to those included in the parameter update message. In an aspect, the parameter update message may be formatted using the fields described in tables 2-4. Once the NFCC has updated the one or more parameters, the process may continue to block 508 to allow the DH to initiate communication with a remote NFC endpoint using the DEP protocol.

Referring now to fig. 6, another example flow diagram is illustrated that describes a process 500 for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint.

At block 602, an NFC controller associated with a communication device may receive, using an NFC-DEP interface, a parameter selection request message including one or more parameter values. In an aspect in which the DH is in a polling mode, the parameter selection request message may be received from the DH. In an aspect, the parameter values may include RF technology and mode parameters, transmit bit rate parameters, receive bit rate parameters, maximum payload size parameters, and the like. Further, in such aspects, the RF technology and mode parameters may indicate use of NCF-a technology, NFC-B technology, NFC-F technology, or the like.

At block 604, the NFC controller may determine to implement one or more parameter changes based on the received one or more parameter values. In an aspect, where the DH is configured in the listening mode, the NFCC determination may comprise: the method may include receiving attributes from a remote NFC endpoint, waiting for messages communicated by the remote NFC endpoint after the attributes, receiving the waiting messages, determining that the waiting messages are parameter selection request messages, communicating an activation message including the one or more parameters to a DH, and transmitting a parameter selection response to the remote NFC endpoint. In an aspect, the remote NFC device may be a remote NFC tag, a reader/writer device, a remote peer target device, or the like.

At block 606, the NFC controller may communicate an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values. In an aspect, the NFC controller may further transmit the payload to the remote NFC endpoint using the NFC-DEP interface and using at least one of the one or more parameter values.

Referring now to fig. 7, another example flow diagram is illustrated that describes another process 700 for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint. As discussed above, a discovery process may be implemented to locate a remote NFC endpoint. Once such a remote NFC endpoint is discovered, various messages may be communicated between the remote NFC endpoint and the NFCC. In an aspect, these messages include a sense command (e.g., SENS _ REQ), an attribute command (e.g., ATR _ REQ), and the like. Further, in the aspect depicted in fig. 7, an NFC-DEP interface may be used.

At block 702, the NFCC may receive a message after receiving attributes associated with a remote endpoint. Since the communication is implemented using the NFC-DEP interface, the NFCC may determine whether the received message is a parameter selection request message at block 704. If it is determined at block 704 that the message is not a parameter selection message, the NFCC may process the received message (e.g., a DEP request message) and perform DEP setup at block 706. Conversely, if it is determined at block 706 that the received message is a parameter selection request message, the NFCC may parse the received message to determine any differences between the provided parameter values and the currently used parameter values at block 708. If a difference is found, the NFCC may change the parameter values to the received parameter values. At block 710, the NFCC uses an activation notification message to communicate updated parameter values to the DH, and thereafter the NFCC may enable DEP establishment at block 706 upon receiving the DEP message.

Referring now to fig. 8, an example call flow diagram is illustrated that describes a system for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint using a NFCC. As depicted in fig. 8, NFC environment 800 may include a device 802, a NFCC804, and a remote NFC endpoint 806. The device host 802 may be implemented in a polling mode or a listening mode.

In an aspect, to enable polling mode, DH802 may send a discovery message (e.g., RF _ DISCOVER _ CMD (RF _ discovery _ command)) to NFCC804 indicating that discovery for polling mode should begin, at act 808. In another aspect, to enable the listening mode, DH802 may send a discovery message (e.g., RF _ DISCOVER _ CMD) to NFCC804 indicating that discovery for listening devices should begin, at act 808. At act 810, sense request and response messages may be communicated between NFCC804 and remote NFC endpoint 806. In an aspect, multiple sensing responses (e.g., SENSF _ RES) may be sent from one or more remote NFC endpoints 806 connected to NFCC 804. In such an aspect, NFCC804 may assign a time slot to each sens _ RES before sending the respective sens _ RES to remote NFC endpoint 806. If multiple SENSF _ RES are sent to the remote NFC endpoint 806, the NFCC804 may send an RF _ ACTIVATE _ NTF to the DH802 that corresponds to the RF protocol indicated by the RF frame received after sending the SENSF _ RES. At act 812, attribute request and response messages may be communicated between NFCC804 and remote NFC endpoint 806. In act 814, NFCC804 establishes operability in a frame RF interface mode of operation. At act 816, a parameter selection message may be communicated between DH802 and remote NFC endpoint 806 through NFCC 804.

In polling mode, when the NFCC is ready to exchange data (e.g., after receiving a polling response from a remote NFC endpoint), at act 818, the NFCC804 sends an activation message (e.g., RF _ ACTIVATE _ NTF) to the DH802 to indicate that the interface has been activated for use with the designated remote NFC endpoint 806. In an aspect, in the event that multiple remote NFC endpoints 806 are detected, the DH802 may select one remote NFC endpoint 806 to use among them. In aspects where the frame RF interface is in use, activation is under the control of the DH 802. In such aspects, no RF technology is included in any activation parameter value in the RF _ ACTIVATE _ NTF message. Conversely, if the RF protocol is NFC-DEP, then RF _ ACTIVATE _ NTF is sent after the exchange of ATR (attribute) requests and responses, and additional steps may be performed before the data exchange can begin.

In listening mode, if listening device DH802 receives an activation notification (e.g., RF _ ACTIVATE _ NTF) indicating that it has been activated by remote NFC endpoint 806 as a peer initiator, DH802 does not change the RF communication parameter values until the first data packet from the initiator remote NFC endpoint arrives. Further, if it interprets the first data packet as a well-formed DEP _ REQ, the DH802 does not change the RF communication parameter value.

In polling mode, if the DH receives an RF _ ACTIVATE _ NTF indicating that it has activated a remote NFC endpoint as a peer target in act 818, the DH802 determines whether an RF communication parameter value needs to be updated. In the listening mode, if the DH802 interprets the frame as a well-formed PSL _ REQ with a matching DID value, the DH802 sends the frame with a payload corresponding to the parameter value provided in the PSL _ RES message. For example, if the bit rate to be used for data exchange is different than the bit rate used for RF discovery, the DH802 sends a data packet (e.g., a parameter update message) with a payload corresponding to the PSL _ REQ communicated to the NFCC804 at act 816. In an aspect, the value of DID in PSL _ REQ may be used for the parameter update message. Similarly, the values of DSI and DRI are set to values to be used for data exchange. A value for the maximum frame length (FSL) is also defined.

Further, at act 818, once DH802 receives a data packet that it interprets as a well-formed PARAMETER selection response (PSL _ RES) with a matching DID value, DH802 sends a PARAMETER UPDATE message (e.g., RF _ PARAMETER _ UPDATE _ CMD) to UPDATE the RF communication PARAMETER values in NFCC 804. In the depicted aspect, the parameter update message includes both the transmit bit rate and the receive bit rate parameter values. The parameter update message includes RF technology and mode parameters if the selected bit rate changes in the RF technology or mode. Similarly, if the maximum payload has changed, the parameter update message includes a maximum payload size parameter. At act 820, NFCC804 implements a change in the parameter value specified in the parameter update message.

In polling mode, if the bit rate to be used for data exchange is the same as the bit rate used for RF discovery, the DH802 does not send a PSL _ REQ to the remote NFC endpoint. Further, if the parameter value has not changed, the communication does not use the updated parameter value. At act 822, DEP request and response communications are communicated between the DH802 and the remote NFC endpoint 806 through the NFCC804 using the updated parameter values.

Referring now to fig. 9A and 9B, an example call flow diagram is illustrated that describes a system for updating parameter values for peer-to-peer communication between a DH and a remote NFC endpoint using a NFCC. As depicted in fig. 9A and 9B, NFC environment 900 may include a device 902, a NFCC904, and a remote NFC endpoint 906. The device host 602 may be implemented in a polling mode or a listening mode. Fig. 9A depicts the DH in a listening mode, while fig. 9B depicts the DH in a polling mode. Further, the aspects depicted in fig. 9A and 9B include the use of an NFC-DEP interface by the NFCC 904.

Referring to fig. 9A, to enable the listening mode, DH902 sends a discovery message (e.g., RF _ DISCOVER _ CMD) to NFCC904 indicating that discovery for the listening mode should begin, in act 908. At act 910, sense request and response messages may be communicated between NFCC904 and remote NFC endpoint 906. At act 912, attribute request and response messages may be communicated between NFCC904 and remote NFC endpoint 906.

In general, when the NFCC904 is ready to exchange data (e.g., after successful protocol activation), the NFCC904 sends an activation notification (e.g., RF _ ACTIVATE _ NTF) to the DH602 to indicate that the NFC-DEP protocol has been activated. In an aspect, activation may be indicated after an anti-collision sequence, and when an ATR _ REQ has been received from the remote NFC endpoint 906, the NFCC sends an attribute response (e.g., ATR _ RES) to the remote NFC endpoint 906. In an aspect, the ATR _ RES _ GEN _ BYTES is configured during discovery configuration. Further, after transmitting the attribute response, the NFCC904 waits for the arrival of the next command.

If the next command from the remote NFC endpoint 906 is a DEP request (e.g., DEP _ REQ) in act 914a, the NFCC forwards the ATR _ REQ to the DH902 within the activation parameter value (as described in table 6) of the activation notification message (e.g., RF _ ACTIVATE _ NTF). Then, in act 922, the NFCC904 forwards the DEP _ REQ to the DH902 and establishes DEP communication between the NFC endpoint 906 and the DH 902. If the command from the remote NFC endpoint is a parameter selection request (e.g., PSL _ REQ) in act 914a, NFCC904 forwards the ATR _ REQ to DH902 within the activation parameter value (as described in table 6) of the activation notification message (e.g., RF _ ACTIVATE _ NTF) in act 916. In such aspects, the activation parameter value indicates the bit rate and RF technology and mode setting according to the value in PSL _ REQ. The NFCC then sends PSL _ RES to the remote NFC endpoint 906 in act 914b, and the NFCC904 updates the RF communication parameter values according to the values in the PSL _ REQ in act 918. At act 920, DEP request and response communications are communicated between the DH906 and the remote NFC endpoint 904 using the updated parameter values through the NFCC 902.

In an aspect, for NFC-a, RF _ ACTIVATE _ NTF includes the activation parameters defined in table 6

Parameter(s)	Length of	Description of the invention
			ATR _ REQ Command Length	1 byte	Length (n) of ATR _ REQ Command parameter

			ATR _ REQ command	n bytes	Byte 3-byte 16+ n of ATR _ REQ command

Table 6: activation parameter of NFC-DEP (listening mode).

Referring to fig. 9B, to enable polling mode, DH902 sends a discovery message (e.g., RF _ DISCOVER _ CMD) to NFCC904 indicating that discovery for polling mode should begin, at act 908. At act 910, sense request and response messages may be communicated between NFCC904 and remote NFC endpoint 906. At act 912, attribute request and response messages may be communicated between NFCC904 and remote NFC endpoint 906.

In general, when the NFCC904 is ready to exchange data (e.g., after successful protocol activation), the NFCC904 sends an activation notification (e.g., RF _ ACTIVATE _ NTF) to the DH602 to indicate that the NFC-DEP protocol has been activated. In an aspect, activation may be indicated after a collision resistant sequence, and when an ATR _ REQ has been received from the remote NFC endpoint 906, the NFCC sends an attribute response (e.g., ATR _ RES) to the remote NFC endpoint 906. In an aspect, ATR _ RES _ GEN _ BYTES is configured during discovery configuration. When ATR _ RES is received from remote NFC endpoint 906 in act 915 and NFCC904 determines that there is no difference between the current bit rate and any proposed bit rate in act 917, the NFCC forwards the ATR _ RES to the DH to indicate that the NFC-DEP based remote NFC endpoint has been activated within the activation parameters of RF _ ACTIVATE _ NTF (as indicated in table 7) in act 919.

Parameter(s)	Length of	Description of the invention
			ATR _ RES response Length	1 byte	Length (n) of ATR _ RES Command parameter
ATR _ RES response	n bytes	Byte 3-byte 17+ n of ATR _ RES response

Table 7: activation parameters for NFC-DEP (Polling mode)

At act 921, DEP request and response communications are communicated between the DH902 and the remote NFC endpoint 906 through the NFCC904 using the updated parameter values.

Turning now also to fig. 10, with reference to fig. 3, an example architecture of a communication device 1000 is illustrated. As depicted in fig. 10, communications device 1000 includes a receiver 1002 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 1002 can comprise a demodulator 1004 that can demodulate received symbols and provide them to a processor 1006 for channel estimation. Processor 1006 can be a processor dedicated to analyzing information received by receiver 1002 and/or generating information for transmission by a transmitter 1020, a processor that controls one or more components of device 1000, and/or a processor that both analyzes information received by receiver 1002, generates information for transmission by transmitter 1020, and controls one or more components of communication device 1000. In addition, signals for transmission by transmitter 1020 may be prepared by a modulator 1018, which modulator 1018 may modulate signals for processing by processor 1006.

Communication device 1000 may additionally comprise memory 1008 that is operatively coupled to processor 1006 and that may 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 the channel.

Further, the processor 1006 may provide means for determining, by the DH1060 using the frame RF interface 1032, that one or more parameter values included in the parameter selection request message are different from one or more corresponding parameter values used during discovery of the peer target device 330, and means for communicating the one or more parameter values to the NFC controller 1030 using a parameter update message that prompts the NFC controller 1030 to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

Further, the processor 1006 may provide means for receiving, by the NFC controller 1030, using the NFC data exchange protocol (NFC-DEP) interface 1034, a parameter selection request message including one or more parameters, means for determining, based on the received parameter selection request, that one or more parameter changes are to be implemented, and means for communicating an activation message to the DH1060 indicating a value to which the one or more parameter values are changed.

It will be appreciated that the data store (e.g., memory 1008) 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 1008 of the subject systems and methods may include, but is not limited to, these and any other suitable types of memory.

In another aspect, the communication device 1000 may include the NCI 1050. In an aspect, NCI1050 may be configured to enable communication between DH1060 and NFC controller 1030.

The communication device 1000 may include an NFC controller 1030. In an aspect, NFC controller 1030 may be configured to obtain information from other devices (such as peer target device 330) through NCI 1050. During peer-to-peer communication, NFC controller 1030 may operate using frame RF interface 314 or NFC-DEP interface 1034. When operating using NFC-DEP interface 1034, NFC controller 1030 may be configured to use rate change module 1036 to change various parameter values associated with communications between device host 1060 and peer target device 330. The communication device 1000 may further include a device host 1060. The device host 1060 may include, among other modules, a parameter selection module 1062 and a parameter update module 1064.

In one operational aspect, when using the frame RF interface 1032, the NFC controller 1030 may act as a relay and communicate messages only between the communication device 1000 device host 1060 and the peer target device 330. In such aspects, the NFC controller 1030 may not interpret the content of the message relayed between the communication device 1000 device host 1060 and the peer target device 330. In such aspects, the device host 1060 may determine that changes to one or more parameters (such as bit rate) may be requested through the parameter selection module 1062. The parameter selection module 1062 may receive a parameter selection request (e.g., PSL-REQ) message from the peer target device 330. Parameter update module 1064 may communicate a portion of the parameter values obtained by parameter selection module 1062 to NFC controller 1030. Further, communications from parameter update module 1064 may prompt NFC controller 1030 to change various parameters, such as receive and/or transmit data rate, bit rate, RF technology, buffer size, maximum payload size, and so forth.

In another operational aspect, NFC controller 1030 may interpret the content of a message being communicated when NFC-DEP interface 1034 is used to facilitate communications between communications device 1000 device host 1060 and peer target device 330. In such aspects, NFC controller 1030 may determine whether rate change module 1036 may be used based on the presence or absence of a parameter selection message. When the device host 1060 is in the polling mode, the device host 1060 may transmit a parameter selection request message. When the device host 1060 is in the listening mode, the NFC controller 1030 may wait to determine whether a message received after the attribute message is a Data Exchange Protocol (DEP) message or a parameter selection request message. When the received message is a parameter selection request message, NFC controller 1030 may interpret the contents of the message to determine whether a parameter change may be implemented using rate change module 1036.

Additionally, the communication device 1000 may include a user interface 1040. User interface 1040 may include input mechanism 1042 for generating input into communication device 1000, and output mechanism 1044 for generating information for consumption by a user of communication device 1000. For example, input mechanism 1042 may include mechanisms such as a key or keyboard, a mouse, a touch screen display, a microphone, and so forth. Further, for example, output mechanisms 1044 can include a display, an audio speaker, a haptic feedback mechanism, and the like. In the illustrated aspect, output mechanism 1044 may comprise a display configured to present media content in an image or video format, or an audio speaker that presents media content in an audio format.

Fig. 11 illustrates another block diagram of an exemplary communication system 1100 operable to provide an improved mechanism for updating parameter values for communications between a DH and a remote NFC endpoint according to an aspect. For example, system 1100 can reside at least partially within a communication device (e.g., communication device 1000). It is to be appreciated that system 1100 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1100 includes a logical grouping 1102 of electrical components that can act in conjunction.

For example, logical grouping 1102 may include an electrical component that may provide means 1104 for determining, by the DH using the frame RF interface, that one or more parameter values included in the parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint. In an aspect, where the DH is configured in the polling mode, the means for determining 1104 may further include means for receiving an activation stimulus message from the NFC controller, and means for generating a parameter selection request message to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message. In such aspects, one or more parameters included in the parameter selection request message may be different from one or more corresponding parameters used during discovery. In another aspect, the means for monitoring 1104 may further include means for monitoring a signal strength value of the first RAT at a first time and a second time after the first time. In another aspect, where the DH is configured in a listening mode, the means for determining 1104 may further comprise means for receiving a parameter selection request message from a remote NFC endpoint. In an aspect, the parameter values may include RF technology and mode parameters, transmit bit rate parameters, receive bit rate parameters, maximum payload size parameters, and the like. Further, in such aspects, the RF technology and mode parameters may indicate use of NCF-a technology, NFC-B technology, NFC-F technology, or the like. In an aspect, the remote NFC endpoint may be a peer NFC device, a reader device, a writer device, a remote NFC tag, an NFC card, or the like.

Further, logical grouping 1102 may include an electrical component that may provide means for communicating the one or more parameter values to the NFC controller using a parameter update message 1106. In an aspect, the parameter update message may prompt the NFC controller to change one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message. In another aspect, the means for communicating 1106 may comprise means for transmitting the payload to the remote NFC endpoint using a data exchange protocol and using at least one of the one or more parameter values.

Additionally, system 1100 can include a memory 1108 that retains instructions for executing functions associated with electrical components 1104 and 1106, and that stores data used or obtained by electrical components 1104, 1106, and the like. While shown as being external to memory 1108, it is to be understood that one or more of electrical components 1104 and 1106 can exist within memory 1108. In one example, electrical components 1104 and 1106 can include at least one processor, or each electrical component 1104 and 1106 can be a corresponding module of the at least one processor. Further, in additional or alternative examples, electrical components 1104 and 1106 can be a computer program product comprising a computer-readable medium, wherein each electrical component 1104 and 1106 can be corresponding code.

Fig. 12 depicts another block diagram of an exemplary communication system 1200 operable to provide an improved mechanism for updating parameter values for communications between a DH and a remote NFC endpoint in accordance with an aspect. For example, system 1200 may reside at least partially within a communication device (e.g., communication device 1000). It is to be appreciated that system 1200 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1200 includes a logical grouping 1202 of electrical components that can act in conjunction.

For example, logical grouping 1202 may include an electrical component that may provide means 1208 for receiving, by an NFC controller using an NFC-DEP interface, a parameter selection request message including one or more parameter values. In an aspect, means for receiving 1204 may comprise means for receiving a parameter selection request message from a DH when the DH is configured in a polling mode. In an aspect, means for modifying 1204 may comprise means for reducing an interval between polling modes based on the monitored signal strength. In an aspect, the parameter values may include RF technology and mode parameters, transmit bit rate parameters, receive bit rate parameters, maximum payload size parameters, and the like. Further, in such aspects, the RF technology and mode parameters may indicate use of NCF-a technology, NFC-B technology, NFC-F technology, or the like.

Moreover, logical grouping 1202 may include an electrical component that may provide means 1206 for determining, based on the received one or more parameter values, that one or more parameter changes are to be implemented. In an aspect, where the DH is configured in a listening mode, the means for determining 1206 may comprise: the apparatus generally includes means for receiving attributes from a remote NFC endpoint, means for waiting for a message to be communicated by the remote NFC endpoint after the attributes, means for receiving the waiting message, means for determining that the waiting message is a parameter selection request message, means for communicating an activation message including the one or more parameters to a DH, and means for transmitting a parameter selection response to the remote NFC endpoint. In an aspect, the remote NFC endpoint may be a peer NFC device, a reader device, a writer device, a tag, a card, or the like.

Further, the logical grouping 1202 may include an electrical component that may provide means 1208 for communicating an activation message to the DH indicating a value to which the NFC controller changed the one or more parameter values. In an aspect, the means for communicating 1208 may include means for transmitting the payload to the remote NFC endpoint using the NFC-DEP interface and using at least one of the one or more parameter values.

Additionally, system 1200 can include a memory 1210 that retains instructions for executing functions associated with electrical components 1204, 1206, and 1208, storing data used or obtained by electrical components 1204, 1206, and 1208, and the like. While shown as being external to memory 1210, it is to be understood that one or more of electrical components 1204, 1206, and 1208 can exist within memory 1210. In one example, electrical components 1204, 1206, and 1208 can include at least one processor, or each electrical component 1204, 1206, and 1208 can be a corresponding module of the at least one processor. Moreover, in additional or alternative examples, electrical components 1204, 1206, and 1208 can be a computer program product comprising a computer-readable medium, wherein each electrical component 1204, 1206, and 1208 can be corresponding code.

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 (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-range 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 configured 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. Any connection is also known as 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 (39)

1. A method for wireless peer-to-peer communication between a device host, DH, and a remote near field communication, NFC, endpoint, wherein the DH is configured in a listening mode, the method comprising:

receiving a parameter selection request message from the remote NFC endpoint;

determining, by the DH, using a frame Radio Frequency (RF) interface, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint; and

communicating the one or more parameter values to a NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

2. The method of claim 1, wherein the DH is configured to be in a polling mode, and wherein the determining further comprises:

receiving an activation stimulus message from the NFC controller; and

generating the parameter selection request message to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message, wherein the one or more parameter values included in the parameter selection request message are different from the one or more corresponding parameter values used during discovery.

3. The method of claim 1, further comprising:

transmitting a payload to the remote NFC endpoint using a data exchange protocol and using at least one of the one or more parameter values.

4. The method of claim 1, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

5. The method of claim 4, wherein the RF technology and mode parameter indicates a technology among: NFC-a technology, NFC-B technology, and NFC-F technology.

6. The method of claim 1, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

7. A method for wireless peer-to-peer communication between a device host, DH, and a remote near field communication, NFC, endpoint, wherein an apparatus associated with a near field communication, NFC, controller and the DH is configured in a listening mode, the method comprising:

receiving, by the NFC controller, a parameter selection request message including one or more parameters from the remote NFC endpoint using an NFC data exchange protocol (NFC-DEP) interface;

determining, based on the received one or more parameter values, that one or more parameter changes are to be implemented; and

communicating an activation message to a device host DH indicating a value to which the NFC controller changes the one or more parameter values.

8. The method of claim 7, wherein an apparatus associated with the NFC controller and the DH is configured to be in a polling mode, and the parameter selection request message is received from the DH.

9. The method of claim 7, wherein an apparatus associated with the NFC controller and the DH is configured to be in a listening mode, and wherein the determining further comprises:

receiving an attribute from a remote NFC endpoint;

waiting for a message to be communicated by the remote NFC endpoint after receiving the attribute;

receiving the waiting message;

determining that the message waiting is the parameter selection request message;

communicating the activation message comprising the one or more parameters to the DH; and

transmitting a parameter selection response to the remote NFC endpoint.

10. The method of claim 9, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

11. The method of claim 7, further comprising:

transmitting a payload to the remote NFC endpoint using the NFC-DEP interface and using at least one of the one or more parameter values.

12. The method of claim 7, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

13. The method of claim 12, wherein the RF technology and mode parameter indicates a technology among: NFC-A technology, NFC-B technology, or NFC-F technology.

14. An apparatus for wireless peer-to-peer communication between a Device Host (DH) and a remote Near Field Communication (NFC) endpoint, wherein the DH is configured to be in a listening mode, the apparatus comprising:

means for receiving a parameter selection request message from the remote NFC endpoint;

means for determining, by the DH, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint using a frame Radio Frequency (RF) interface; and

means for communicating the one or more parameter values to a NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

15. The apparatus of claim 14, wherein the DH is configured in a polling mode, and the means for determining further comprises:

means for receiving an activation stimulus message from the NFC controller; and

means for generating the parameter selection request message to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message, wherein the one or more parameter values included in the parameter selection request message are different from the one or more corresponding parameter values used during discovery.

16. The apparatus of claim 14, further comprising:

means for transmitting a payload to the remote NFC endpoint using a data exchange protocol and using at least one of the one or more parameter values.

17. The apparatus of claim 14, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

18. The apparatus of claim 17, wherein the RF technology and mode parameter indicates a technology among: NFC-A technology, NFC-B technology, or NFC-F technology.

19. The device of claim 14, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

20. An apparatus for wireless peer-to-peer communication between a Device Host (DH) and a remote Near Field Communication (NFC) endpoint, wherein an apparatus associated with a NFC controller and the DH is configured to be in a listening mode, the apparatus comprising:

means for receiving, by the NFC controller, a parameter selection request message including one or more parameters from the remote NFC endpoint using an NFC data exchange protocol (NFC-DEP) interface;

means for determining, based on the received one or more parameter values, that one or more parameter changes are to be implemented; and

means for communicating an activation message to a DH indicating a value to which the NFC controller changes the one or more parameter values.

21. The apparatus of claim 20, wherein the devices associated with the NFC controller and the DH are operating in a polling mode, and the parameter selection request message is received from the DH.

22. The apparatus of claim 20, wherein an apparatus associated with the NFC controller and the DH is operating in a listening mode, and further comprising:

means for receiving an attribute from a remote NFC endpoint;

means for waiting for a message to be communicated by the remote NFC endpoint after receiving the attribute;

means for receiving the awaited message;

means for determining that the message waiting is the parameter selection request message;

means for communicating the activation message comprising the one or more parameters to the DH; and

means for transmitting a parameter selection response to the remote NFC endpoint.

23. The device of claim 22, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

24. The apparatus of claim 20, further comprising:

means for transmitting a payload to the remote NFC endpoint using the NFC-DEP interface and using at least one of the one or more parameter values.

25. The apparatus of claim 20, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

26. The apparatus of claim 25, wherein the RF technology and mode parameter indicates a technology among: NFC-A technology, NFC-B technology, or NFC-F technology.

27. An apparatus for wireless peer-to-peer communication between a Device Host (DH) and a remote Near Field Communication (NFC) endpoint, wherein the DH is configured to be in a listening mode, the apparatus comprising:

the DH configured to:

receiving a parameter selection request message from the remote NFC endpoint;

determining, using a frame Radio Frequency (RF) interface, that one or more parameter values included in a parameter selection request message are different from one or more corresponding parameter values used during discovery of the remote NFC endpoint; and communicating the one or more parameter values to a NFC controller using a parameter update message, wherein the parameter update message prompts the NFC controller to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message.

28. The apparatus of claim 27, wherein the DH is configured in a polling mode, and the DH is further configured to:

receiving an activation stimulus message from the NFC controller; and

generating the parameter selection request message to change the one or more corresponding parameter values used during discovery to the one or more parameter values included in the parameter selection request message, wherein the one or more parameter values included in the parameter selection request message are different from the one or more corresponding parameter values used during discovery.

29. The apparatus of claim 27, wherein the DH is further configured to:

transmitting a payload to the remote NFC endpoint using a data exchange protocol and using at least one of the one or more parameter values.

30. The apparatus of claim 27, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

31. The apparatus of claim 30, wherein the RF technology and mode parameter indicates a technology among: NFC-A technology, NFC-B technology, or NFC-F technology.

32. The apparatus of claim 27, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

33. An apparatus for wireless peer-to-peer communication between a Device Host (DH) and a remote Near Field Communication (NFC) endpoint, wherein an apparatus associated with a NFC controller and the DH is configured to be in a listening mode, the apparatus comprising:

the NFC controller configured to:

receiving a parameter selection request message including one or more parameters from the remote NFC endpoint, wherein the NFC controller uses an NFC data exchange protocol, NFC-DEP, interface;

determining, based on the received one or more parameter values, that one or more parameter changes are to be implemented; and

communicating an activation message to a DH indicating a value to which the NFC controller changes the one or more parameter values.

34. The apparatus of claim 33, wherein the apparatus associated with the NFC controller and the DH is operating in a polling mode, and wherein the parameter selection request message is received from the DH.

35. The apparatus of claim 33, wherein the apparatus associated with the NFC controller and the DH is operating in a listening mode, and wherein the NFC controller is further configured to:

receiving an attribute from a remote NFC endpoint;

waiting for a message to be communicated by the remote NFC endpoint after receiving the attribute;

receiving the waiting message;

determining that the message waiting is the parameter selection request message;

communicating the activation message comprising the one or more parameters to the DH; and

transmitting a parameter selection response to the remote NFC endpoint.

36. The apparatus of claim 35, wherein the remote NFC endpoint comprises one device among: a peer NFC device, a reader device, a writer device, a remote NFC tag, and an NFC card.

37. The apparatus of claim 33, wherein the NFC controller is further configured to:

transmitting a payload to the remote NFC endpoint using the NFC-DEP interface and using at least one of the one or more parameter values.

38. The apparatus of claim 33, wherein the one or more parameter values comprise at least one value of a parameter from among:

RF technology and mode parameters;

a transmit bit rate parameter;

receiving a bit rate parameter; and

a maximum payload size parameter.

39. The apparatus of claim 38, wherein the RF technology and mode parameter indicates a technology among: NFC-A technology, NFC-B technology, or NFC-F technology.