NFC Controller Interface (NCI) 1.0技术规范概述

5星 · 超过95%的资源需积分: 49 126 浏览量更新于2024-07-20 4 收藏 1.1MB PDF 举报

NFCControllerInterface (NCI) 技术规范是一份由NFC Forum发布的详细文档，针对NFC（Near Field Communication）开发提供了关键的接口指导。这份规范（NFCForum-TS-NCI-1.0）于2012年11月6日发布，主要用于描述NFC设备控制器之间的交互，它定义了控制器之间的通信接口，以便实现设备间的高效数据传输和配对。 NCI 是一种用于管理和协调NFC设备功能的核心组件，它简化了开发者在设计NFC兼容产品时的工作流程。该规范主要关注以下几个方面： 1. **版权与许可**：NFC Forum拥有此规范的版权，任何接收者（许可证持有者，简称Licensee）在使用时必须遵循NFC Forum与之签订的许可协议。非许可证持有者只能阅读规范，未经授权不得实施或使用，如需获取实施权限和完整规范，需通过NFC Forum网站（<http://www.nfc-forum.org/specs/spec_license>），并在同意相应许可条款后获取。 2. **使用限制**：许可证持有者在下载该规范时，必须遵守非实施条款，包括： - 内部使用仅限于授权范围，除非另有明确许可。 - 不得复制或分发规范，除非是为了实现NFC功能。 - 可能存在针对特定日期的非实施条款，这些条款可能规定了许可期限、更新规定等。 3. **功能与架构**：NCI 1.0规范详述了接口的功能定义、数据交换格式、命令集和事件处理机制。开发者可以借此了解如何设计符合标准的NFC控制器，确保设备之间的兼容性和互操作性。 4. **版本更新**：随着技术的发展和需求变化，NFC Forum可能会定期更新规范， Licensee需要保持对最新版本的关注，以确保其产品始终与NFC生态系统保持同步。 NFCControllerInterface (NCI) 技术规范是NFC开发不可或缺的参考资料，对于理解NFC设备如何通过控制器进行通信，以及如何按照标准进行产品设计至关重要。遵循NFC Forum的规定，可以确保设备的性能和市场接受度。

Introduction

NFC Controller Interface (NCI) Specification Page 15

Dynamic Logical Connection

A Logical Connection that is created and closed dynamically as needed.

HCI Network

A Network as described within [ETSI_102622] consisting of a host controller and one or

more hosts.

ISO-DEP Protocol

Half-duplex block transmission protocol defined in [ISO/IEC_14443].

Listen Mode

The mode of an NFC Forum Device where it does not generate a carrier. In this mode,

the NFC Forum Device listens for the RF field of another device.

Logical Connection

A communication channel between the Device Host (DH) and the NFC Controller

(NFCC) that is used for data communication towards either the NFCC itself, an NFCEE,

or a Remote NFC Endpoint.

Message

A generic term for a Command, Response, Notification, or Data object communicated

between the DH and NFCC.

NCI

The logical interface between a Device Host (DH) and an NFC Controller (NFCC).

NCI Core

Defines the basic NCI functionality required between the Device Host (DH) and NFC

Controller (NFCC).

NCI Transport

The physical connection (e.g., SPI, I2C, UART, USB, etc.) and any associated link level

protocol between the DH and NFCC. Each supported NCI Transport has a Transport

Mapping which defines the characteristics of the NCI Transport. An NCI Transport

provides the ability to reliably transfer data without intimate knowledge of the data being

transferred. The NCI specification defines multiple Transport Mappings.

NFC Controller (NFCC)

The logical entity responsible for the transmission of data over the NFC Radio Interface.

The NFC Controller has a connection to the Device Host (DH) and may have connections

to additional NFC Execution Environments (NFCEEs). Those connections are out of

scope of this specification, but the impacts to the NCI are in scope.

NFC Execution Environment (NFCEE)

An environment, either built into the NFCC or connected to the NFCC, where NFC

applications are executed. The NFCEE may be included in entities with various form

factors, some of which can be removable or replaceable.

NFC Radio Interface

A contactless radio interface using NFC technology to communicate with a Remote NFC

Endpoint.

Introduction

NFC Controller Interface (NCI) Specification Page 18

1.11 Coding Conventions

The following coding conventions apply in this document if not stated otherwise.

• Each octet is represented by bits b0 to b7, where b7 is the most significant bit (msb) and b0

the least significant bit (lsb). In all representations, the leftmost bit is the msb.

• All values greater than 1 octet are sent and received in Little Endian format.

• In representations of octet arrays, each octet is numbered, starting at 0. Octet numbered 0 is

sent over the NCI Transport first.

This document uses the following notations for numbers:

• Values expressed in hexadecimal form are preceded by ‘0x’.

• Values expressed in binary form are followed by a lower case ‘b’.

In this document, the following rules apply for fields or values defined as Reserved for Future

Use (RFU):

• For an NCI message including fields with a subset of octets or bits defined as RFU, the

sender SHALL set these octets or bits to the value indicated in this document or to zero if no

value is given.

• For an NCI message including fields with a subset of octets or bits defined as RFU, the

receiver SHALL disregard these octets or bits and SHALL keep the same interpretation of

any other field of the whole message, unless explicitly stated otherwise.

For fields that could contain values that are defined as RFU, the sender of an NCI message

SHALL NOT set these fields to the RFU values.

If a parameter is defined as meaningless in certain conditions, the message sender SHALL

include the parameter, but MAY set its value to any value. The message receiver SHALL ignore

the parameter value.

Values defined as Proprietary MAY be used by implementations for extensions that are out of

scope of this specification.

In this document, Control Messages are defined by using tables specifying the message

parameters. Control Messages SHALL be coded in the order and length as specified by the

corresponding definition table (first parameter being defined in the topmost table row).

The names of Parameters that can be present multiple times in a Control Message are followed by

square brackets surrounding the number of times the parameter is to be included. This

information is expressed by an index range (e.g., [1..10]). The upper bound of this range can be a

variable defined by another parameter. The parameter instances SHALL follow each other

sequentially. The corresponding parameter length indicates the length of a single parameter

instance (not the length of the complete parameter set).

剩余145页未读，继续阅读

OpenLD

粉丝: 459
资源: 94

NFC Controller Interface (NCI) 1.0技术规范概述

NFCForum-TS-NCI-1.1.pdf

protocol_NFC_controller_interface_specification.pdf

NFC Forum协议技术规范

nfc controller interface (nci) technical specification

NFC NCI规范

NFC fourm doc

NFC全套英文协议文档

NFC2.0协议，原文和中文版（deepl翻译）

如何在开发NFC设备时确保控制器接口符合NFC Forum的NCI 1.0规范并实现与其它设备的互操作性？

在NFC技术开发中，如何确保遵循NFC Forum的NCI 1.0规范实现控制器接口的互操作性？请说明该规范的主要内容和实施要点。

最新资源