type1协议
NFC Forum Type 1 Tag Operation Specification 1.1
Type 1 Tag Operation Specification Technical SpecificationNFC Forum TMT1TOP 1.1NFCForum-TS-Type-1-Tag_1.12011-04-13RESTRICTIONS ON USEThis specification is copyright © 2005-2011 by the NFC Forum, and was made available pursuant to a license agreement entered into between the recipient (Licensee) and NFC Forum, Inc. (Licensor) and may be used only by Licensee, and in compliance with the terms of that license agreement (License). If you are not the Licensee, you may read this Specification, but are not authorized to implement or make any other use of this specification. However, you may obtain a copy of this Specification and implementation rights at the following page of Licensor's website: /specs/spec_license after entering into and agreeing to such license terms as Licensor is then requiring. On the date that this specification was downloaded by Licensee, the non-implementation terms of that license were as follows:1.LICENSE GRANT.Licensor hereby grants Licensee the right, without charge, to copy (for internal purposes only) and share this Specification with Licensee's members, employees and (to the extent related to Licensees use of this Specification) consultants. This license grant does not include the right to sublicense, modify or create derivative works based upon the Specification.2.NO WARRANTIES.THE SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL LICENSOR, ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION.3.THIRD PARTY RIGHTS.Without limiting the generality of Section 2 above, LICENSOR ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.4.TERMINATION OF LICENSE.In the event of a breach of this Agreement by Licensee or any of its employees or members, Licensor shall give Licensee written notice and an opportunity to cure. If the breach is not cured within thirty (30) days after written notice, or if the breach is of a nature that cannot be cured, then Licensor may immediately or thereafter terminate the licenses granted in this Agreement.5.MISCELLANEOUS.All notices required under this Agreement shall be in writing, and shall be deemed effective five days from deposit in the mails. Notices and correspondence to the NFC Forum address as it appears below. This Agreement shall be construed and interpreted under the internal laws of the United States and the Commonwealth of Massachusetts, without giving effect to its principles of conflict of law.NFC Forum, Inc.401 Edgewater Place, Suite 600Wakefield, MA, USA 01880Contents1Introduction (1)1.1Objectives (1)1.2Applicable Documents or References (1)1.3Administration (2)1.4Name and Logo Usage (2)1.5Intellectual Property (3)1.6Special Word Usage (3)1.7Convention and Notations (3)1.7.1Representation of Numbers (3)1.8Abbreviations (3)1.9Glossary (5)2Memory Structure and Management (6)2.1General (6)2.2Static Memory Structure (6)2.2.1Memory Map (6)2.2.2Header ROM Format (7)2.2.3UID Format (7)2.2.4Main Read/Write Memory Format (7)2.2.5Block Dh (7)2.2.6Lock Control/Status Bytes (8)2.2.7OTP Bytes (8)2.3Dynamic Memory Structure (8)2.3.1Dynamic Memory Map (8)2.3.2Dynamic Memory Reserved Bytes (10)2.3.3Dynamic Memory Lock Bytes (10)2.3.4Dynamic Memory Area (10)2.4TLV Blocks (10)2.4.1Format (10)2.4.2Location (12)2.4.3Lock Control TLV (12)2.4.4Reserved Memory Control TLV (13)2.4.5NDEF Message TLV (14)2.4.6Proprietary TLV (15)2.4.7NULL TLV (15)2.4.8Terminator TLV (15)3RF Interface (16)4Framing and Transmission Handling (17)4.1Frame Formats (17)4.2Transmission Handling (17)5Command Set (18)5.1State Diagram (18)5.2Tag Command and Response Set (18)5.2.1Static Memory Model (18)5.2.2Dynamic Memory Model (18)5.3Command Format (19)5.3.1Command List (19)5.3.2Command-Response Format (20)5.3.3Address Operand (20)5.3.4CRC (21)5.3.5UID Echo (21)5.4Command Details (21)5.4.1Detailed Timing (21)5.4.2Timing Definitions (21)5.5SENS_REQ and ALL_REQ (22)5.6Read Identification (RID) (22)5.7Read All Blocks 0-Eh (RALL) (23)5.8Read Byte (READ) (23)5.9Write-Erase Byte (WRITE-E) (24)5.10Write-No-Erase Byte (WRITE-NE) (25)5.11Locking (26)5.12Read Segment (RSEG) (26)5.13Read 8 Bytes (READ8) (27)5.14Write-Erase 8 Bytes (WRITE-E8) (27)5.15Write-No-Erase 8 Bytes (WRITE-NE8) (27)6NDEF Detection and NDEF Access (29)6.1NDEF Management (29)6.1.1Identification as NFC Forum Type 1 Tag (29)6.1.2Write Permission (29)6.1.3Confirmation of Presence of NDEF Message in Type 1 Tag (29)6.1.4Capability Container (29)6.2Version Treatment (30)6.3NDEF Storage (32)6.4Life Cycle (33)6.4.1General (33)6.4.2Overview of Life-Cycle States (33)6.4.3INITIALIZED State (33)6.4.4READ/WRITE State (33)6.4.5READ ONLY State (34)6.4.6Determination of Life Cycle State (34)6.5Rules for Life Cycle Operation (35)6.5.1Detect NDEF on tag (35)6.5.2Read NDEF Message (35)A.Appendix A (37)A.1Example NDEF Mapping (Static Memory Model) (37)A.2Example NDEF Mapping (Dynamic Memory Model) (39)B.Revision History (42)FiguresFiguresFigure 1: Static Memory Map of the Base NFC Forum Type 1 Tag (7)Figure 2: Lock Control/Status Bytes (8)Figure 3: Example Dynamic Memory Map of NFC Forum Type 1 Tag (9)Figure 4: Length Field Formats (11)Figure 5: RALL Command/Response Diagram (23)Figure 6: READ Command/Response Diagram (23)Figure 7: WRITE-E Command/Response Diagram (24)Figure 8: WRITE-NE Command/Response Diagram (25)Figure 9: Location of NDEF Message (32)Figure 10: Memory Map of Example Smartposter NDEF Message (38)Figure 11: Example Dynamic Memory Map (40)TablesTable 1: Abbreviations (3)Table 2: Defined TLV blocks (12)Table 3: Command-Response Byte Count (Static Memory Model) (18)Table 4: Command-Response Summary (Static Memory Model) (18)Table 5: Command-Response Byte Count (Dynamic Memory Model) (19)Table 6: Command-Response Summary (Dynamic Memory Model) (19)Table 7: List of Commands (Static Memory Model) (19)Table 8: List of Additional Commands (Dynamic Memory Model) (20)Table 9: Format of Address Operand ADD (Static Memory Structure) (20)Table 10: Format of Address Operand ADDS (Dynamic Memory Model) (20)Table 11: Format of Address Operand ADD8 (Dynamic Memory Model) (21)Table 12: Timing Definitions (22)Table 13: FDT Timing Calculations (22)Table 14: Example Coding of the CC Bytes of Block 1 (30)Table 15: Rules for Handling of the Version Number (31)Table 16: Example Smartposter NDEF Message (37)Table 17: Revision History (42)1 IntroductionThis specification is part of the NFC Forum documentation about tag types that an NFC Forum Device needs to support in NFC Forum Reader/Writer Mode.This specification documents how an NFC Forum Device SHALL operate an NFC Forum Type 1 Tag. This is not a specification of the NFC Forum Type 1 Tag itself.1.1 ObjectivesThe purpose of this specification is to document the requirements and to specify, with a set of rules and guidelines, the NFC Forum Device operation and management of the Type 1 Tag. This specification assumes that the Collision Detection and Device Activation activities have been performed as documented in the [ACTIVITY], [DIGITAL], and [ANALOG] specifications and these have been completed up to the level of making a single Type 1 Tag identifier (UID) available.This specification also defines the data mapping and how the NFC Forum Device detects, reads, and writes NDEF data into the Type 1 Tag in order to achieve and maintain interchangeability and interoperability.1.2 Applicable Documents or References[ACTIVITY] NFC Activity Specification,Version 1.0,NFC Forum[ANALOG] NFC Analog,In progress,NFC Forum[DIGITAL] NFC Digital Protocol,Version 1.0,NFC Forum[ISO/IEC_14443] Identification cards – Contactless integrated circuit cards – ProximitycardsIncludes:•[ISO/IEC 14443-1:2008], Identification cards – Contactlessintegrated circuit cards – Proximity cards – Part 1: Physicalcharacteristics•[ISO/IEC 14443-2:2010], Identification cards – Contactlessintegrated circuit cards – Proximity cards – Part 2: Radio frequencypower and signal balance•[ISO/IEC 14443-3:2001], Identification cards – Contactlessintegrated circuit cards – Proximity cards – Part 3: Initialization andanticollision•[ISO/IEC_14443-3:2001/Amd.1], Identification cards -- Contactlessintegrated circuit(s) cards -- Proximity cards -- Part 3: Initializationand Anti-collision, 1 February 2001 with Amendment 1: Bit rates offc/64, fc/32 and fc/16, 15 June 2005; Amendment 3: Handling ofreserved fields and values, 22 March 2006; and Corrigendum 1:Amendment 1 - Corrigendum, 29 August 2006•[ISO/IEC 14443-4:2008], Identification cards – Contactlessintegrated circuit cards – Proximity cards – Part 4: TransmissionprotocolISO/IEC[NDEF] NFC Data Exchange Format,Version 1.0,NFC Forum[RFC2119] Key words for use in RFCs to Indicate Requirement Levels, RFC 2119,S. Bradner,March 1997,Internet Engineering Task Force1.3 AdministrationThe NFC Type 1 Tag Specification is an open specification supported by the Near Field Communication Forum, Inc., located at:401 Edgewater Place, Suite 600Wakefield, MA, 01880Tel.: +1 781-876-8955Fax: +1 781-610-9864/The NFC Devices Technical Working Group maintains this specification. Comments, errors, and other feedback can be submitted at http://www.nfc-/apps/group_public/document.php?document_id=9774&wg_abbrev=chairs.1.4 Name and Logo UsageThe Near Field Communication Forum’s policy regarding the use of the trademarks NFC Forum and the NFC Forum logo is as follows:•Any company MAY claim compatibility with NFC Forum specifications, whether a member of the NFC Forum or not.•Permission to use the NFC Forum logos is automatically granted to designated members only as stipulated on the most recent Membership Privileges document, during the period of time for which their membership dues are paid.•Member’s distributors and sales representatives MAY use the NFC Forum logo in promoting member’s products sold under the name of the member.•The logo SHALL be printed in black or in color as illustrated on the Logo Page that is available from the NFC Forum at the address above. The aspect ratio of the logo SHALL be maintained, but the size MAY be varied. Nothing MAY be added to or deleted from thelogos.•Since the NFC Forum name is a trademark of the Near Field Communication Forum, the following statement SHALL be included in all published literature and advertising material in which the name or logo appears:NFC Forum and the NFC Forum logo are trademarks of the Near Field Communication Forum.1.5 Intellectual PropertyThe Type 1 Tag Operation Specification conforms to the Intellectual Property guidelines specified in the NFC Forum's Intellectual Property Rights Policy, as outlined in the NFC Forum Rules of Procedure. These documents are available on the NFC Forum website.1.6 Special Word UsageThe key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].1.7 Convention and Notations1.7.1 Representation of NumbersThe following conventions and notations apply in this document unless otherwise stated. •Binary numbers are represented by strings of digits 0 and 1 shown with the most significant bit (msb) left and the least significant bit (lsb) right; “b” is added at the end.Example: 11110101b•Hexadecimal numbers are represented using the numbers 0 - 9 and the characters A – F; an “h” is added at the end. The most significant byte (MSB) is shown on the left and the least significant byte (LSB) on the right.Example: F5h•Decimal numbers are represented as is (without any trailing character).Example: 2451.8 AbbreviationsThe abbreviations as used in this document are defined in Table 1.Table 1: Abbreviations1.9 GlossaryThis section defines all relevant terms and acronyms used in this specification.NFC Forum DeviceA device that supports the following Modus Operandi: Initiator, Target andReader/Writer. It may also support Card Emulation Mode.NFC Forum Reader/Writer ModeIn NFC Forum Reader/Writer Mode, the NFC Forum Device starts the Master/Slave Communication and sends commands to an NFC Forum Tag or contactless card. The communication for this mode is abbreviated as RW.2 Memory Structure and Management2.1 GeneralThe NFC Forum Type 1 Tag utilizes a simple memory model.[RQ_T1T_MEM_001] There SHALL be two memory model mappings depending on the memory size of the tag:•Static memory structure applies for a tag with physical memory size equal to 120 bytes, •Dynamic memory model applies for a tag with physical memory size larger than 120 bytes. [RQ_T1T_MEM_002] The memory SHALL be considered as being divided into blocks containing 8 bytes each.Each block is numbered from 0 to 14 (Eh) for static memory structure or from 0 to k for dynamic memory structure. The number associated to a block is called the ‘block number’.The 8 bytes inside each block are numbered from 0 to 7, where byte 0 is the LSB and byte 7 is the MSB of the block.For the complete tag address space, byte 0 of block 0 corresponds to ByteAddr = 0 as the LSB. Byte 7 of block Eh for static memory structure or byte 7 of block k for dynamic memory structure indicates the MSB.Unless otherwise stated, within this document the byte ordering when defining packets and messages follows the little-endian byte order.The next two sections described in detail the two memory structures.2.2 Static Memory Structure2.2.1 Memory MapThe static memory map of the NFC Forum Type 1 Tag, with HR0 = 11h, is shown in Figure 1.Reserved for internal useUser Block Lock & StatusOTP bitsFigure 1: Static Memory Map of the Base NFC Forum Type 1 Tag2.2.2 Header ROM FormatThe NFC Forum Type 1 Tag includes two bytes of fixed header ROM called HR0 and HR1, as shown in Figure 1. These are not individually addressable by a Read command.The contents are automatically included in the response packet to certain commands.[RQ_T1T_MEM_003] HR0 Upper nibble = 0001b SHALL determine that it is a Type 1, NDEF capable tag.[RQ_T1T_MEM_004] HR0 Lower nibble = 0001b SHALL determine static memory map. [RQ_T1T_MEM_005] HR0 Lower nibble ≠ 0001b SHALL determine the dynamic memory map.[RQ_T1T_MEM_006] HR1 = xxh is undefined and SHALL be ignored.2.2.3 UID FormatBlock 0 is reserved for the read-only Unique Identification (UID) number.Byte 7 is reserved for future use.Byte 6 is the manufacturer’s identification code.Bytes 5, 4, 3, 2, 1, 0 are unique numbers.2.2.4 Main Read/Write Memory FormatThe 12 blocks numbered as 1h to Ch contain 96 bytes of general read/write memory.Each block is individually lockable to become read-only by use of the relevant bits within the lock control bytes, as described in Section 2.2.6.2.2.5 Block DhThe block numbered as Dh is read-only and reserved for internal use.2.2.6 Lock Control/Status BytesBytes 0 and 1 of block Eh function as the lock controls for the various memory blocks.They operate in a bit-wise one-time-programmable fashion.Figure 2 shows the factory default settings for a Type 1 Tag with static memory map.The individual locking bits can be set to 1b by using a suitable bit mask via a standard write command to the relevant bytes in block number Eh.This process is irreversible: if one bit of the lock bytes is set to 1b, it cannot be changed back to 0b again.2.2.7 OTP BytesBytes 2 – 7 of block Eh are allocated as One Time Programmable (OTP) bits and are not defined for NFC Forum purposes.2.3 Dynamic Memory Structure2.3.1 Dynamic Memory Map[RQ_T1T_MEM_007] The NFC Forum Type 1 Tag with dynamic memory map is indicated by HR0 = 1yh, where y ≠ 1. In this case, a capability container shall be included in the tag memory containing information about the physical memory size. See Section 6.1.4.An example of the dynamic memory map representation of the NFC Forum Type 1 Tag with HR0 = 1yh, where y ≠ 1, is shown in Figure 3.In Figure 3, each memory block is numbered from 0 to k.[RQ_T1T_MEM_008] Dynamic lock bytes and reserved bytes might be located at any byte address in between or at the end of the data area starting from block 0Fh.[RQ_T1T_MEM_009] Compared to the static memory structure, the dynamic memory structure SHALL contain configuration information to describe the details of dynamic lock bits and to identify reserved memory areas in the data area using the Lock Control TLV and the Memory Control TLV.The capability container and TLV data areas are not shown in Figure 3. For an example, refer toA.2.2.3.2 Dynamic Memory Reserved Bytes[RQ_T1T_MEM_010] These bytes belong to Reserved memory areas and SHALL be ignored / jumped over during read and write parsing operations of NFC Forum data.[RQ_T1T_MEM_011] The location of Reserved bytes SHALL be identified by one or more Memory Control TLV blocks, as described in Section 2.4.2.3.3 Dynamic Memory Lock BytesA tag with a dynamic memory structure contains two kinds of lock bytes:•Static lock bytes as specified in Section 2.2.6.•Dynamic memory lock bytes.[RQ_T1T_MEM_012] The position of the dynamic memory lock bytes within the tag memory MAY change.2.3.4 Dynamic Memory AreaThe additional dynamic memory area is located from block Fh onward.The available data area for the dynamic memory structure is contained from block 1 up to the last block of the memory, including the 96 bytes of the static memory structure and excluding static and dynamic lock bytes and reserved bytes.Addressing of memory blocks is relative to and includes Block 0.The available data area capacity in bytes is equal to:−⋅)3(−8ervedBytesk−DynamicReskBytesDynamicLocThis calculation includes the data area of the static memory structure equal to 96 bytes and discounts blocks 0, Dh, and Eh.2.4 TLV Blocks2.4.1 FormatA TLV block consists of one to three fields:•T(tag field or T field) identifies the type of the TLV block and consists of a single byte encoding a number from 00h to FFh. The tag values 04h to FCh and FFh are reserved for future use by the NFC Forum.•L(length field or L field) provides the size in bytes of the value field. It has two different formats composed of one or three bytes.[RQ_T1T_MEM_013] The NFC Forum device SHALL understand both length field formats.Figure 4 shows the two different length field structures.[RQ_T1T_MEM_014] However, depending on the tag field value, the length field may not be present.One byte format:[RQ_T1T_MEM_015] The NFC Forum device SHALL use the one byte format to code the length of the value field between 00h and FEh bytes.[RQ_T1T_MEM_016] The NFC Forum device SHALL interpret this byte as a cardinal if the value is between 00h and FEh.[RQ_T1T_MEM_017] If it contains FFh, the NFC Forum device SHALL interpret the value as flag that specifies that the length field is composed of more than one byte. Three consecutive bytes format:[RQ_T1T_MEM_018] The NFC Forum device SHALL use this format to code the length of the value field between 00FFh and FFFEh bytes.[RQ_T1T_MEM_019] The first byte is assumed to be a flag equal to FFh, indicating that two more bytes are present. The NFC Forum device SHALL interpret the two more bytes as a word. [RQ_T1T_MEM_020] The NFC Forum device SHALL interpret this word as a cardinal if the value is between 00FFh and FFFEh.The value FFFFh is reserved for future use (RFU).1 byte format3 bytes formatFigure 4: Length Field Formats• V (value field or V field). If the length field is equal to 00h or there is no length field, thevalue field is not present (i.e., the TLV block is empty). If there is a length field and itindicates a length N bigger than zero (N>0), the value field consists of N consecutive bytes. Table 2 lists the TLV blocks defined by this document that are described in the following sections.Table 2: Defined TLV blocksTLV Block Name Tag Field Value Short DescriptionNULL TLV 00h [RQ_T1T_MEM_021] May be used for paddingof memory areas and theNFC Forum DeviceSHALL ignore this Lock Control TLV 01h Defines details of the lock bytesMemory Control TLV 02h Identifies reserved memory areasNDEF Message TLV 03h Contains the NDEF messageProprietary TLV FDh Tag proprietary informationTerminator TLV FEh Last TLV block in the data area2.4.2 Location[RQ_T1T_MEM_022] The NFC Forum device SHALL recognize and interpret the TLV blocksin a specific order inside the data area according to the following rules:•NDEF Message TLVs and Proprietary TLVs are present after all Lock Control TLVs and Memory Control TLVs.•If present, the Terminator TLV is the last TLV block on the Type 1 Tag.NULL TLV and Terminator TLV are the only TLV blocks that are 1 byte long (e.g., composed of only the Tag field. See the NOTE below).[RQ_T1T_MEM_023] NFC Forum Devices SHALL ignore and jump over those TLV blocks that make use of reserved Tag field values.[RQ_T1T_MEM_024] To jump over a TLV block with reserved Tag field values, the NFC Forum device SHALL read the length field to understand the length of the value field.NOTE Future definitions of TLV blocks composed of only the Tag field are not backward compatible with this NFC Forum specification.2.4.3 Lock Control TLV[RQ_T1T_MEM_025] The Lock Control TLV can be present inside the Type 1 Tag. An NFC Forum Device SHALL be able to read and process it.The Lock Control TLV provides control information about the lock areas where the dynamic lock bytes are located.Each Lock Control TLV indicates a single lock area. More lock areas are indicated using more Lock Control TLV blocks. The encoding of the 3 TLV fields of the Lock Control TLV is as follows:•T is equal to 01h.•L is equal to 03h.•V is composed of 3 bytes that uniquely identify the position and the size of the lock area and the number of bytes locked by each bit of the dynamic lock bytes. The 3 bytes areencoded as follows:• Position, MSB. It codes the position inside the tag memory of the lock area. The positionbyte consists of 2 parts (to calculate the bytes address from the position byte, see the equation below): • PagesAddr. Most significant nibble (4 bits), coded as number of pages (0h=0…Fh=15)and • ByteOffset. Least significant nibble, coded as number of bytes (0h=0…Fh=15). • Size. Middle byte, coded as number of bits (01h=1…FFh=255, 00h=256). It indicates thesize in bits of the lock area (i.e., the number of dynamic lock bits). If the number of dynamic lock bits is not a multiple of 8, they are stored inside the dynamic lock bytes as explained in the description of the default setting of the dynamic lock bits. • Page control, LSB. The page control provides general control information: the size inbytes of a page and the number of bytes that each dynamic lock bit is able to lock. Page control byte is split up into two nibbles of 4 bits each:• BytesPerPage: Least significant nibble, coded as 2n (0h=RFU, 1h=1…Fh=15). Itindicates the number of bytes per page. • BytesLockedPerLockBit: Most significant nibble, coded as 2n (0h=RFU,1h=1…Fh=15). It indicates the number of bytes that each dynamic lock bit is able to lock.[RQ_T1T_MEM_026] The NFC Forum device SHALL calculate the byte address (ByteAddr) of the beginning of the lock area as follows:ByteOffset PageAddr ByteAddr ge BytesPerPa +⋅=2The ByteAddr is calculated from the beginning of the overall memory of the tag (i.e., Byte 0 of Block 0 is indicated by ByteAddr equal to 0).The ByteAddr is used to read and write the relative lock area using the appropriate tag access commands. The page definition has nothing to do with the block definition used by tag access commands.An example of the BytesLockedPerLockBit is: If the memory area locked by a single dynamic lock bit is 8 bytes, then the BytesLockedPerLockBit is equal to 3 (i.e., 2BytesLockedPerLockBit =23=8 bytes). NOTEThe Lock Control TLV might be skipped if a Type 1 Tag is in READ-ONLY state. Lock Control TLV blocks can be replaced by Reserved Memory Control TLV indicating the same memory areas for Type 1 Tag in READ-ONLY state.2.4.4 Reserved Memory Control TLV[RQ_T1T_MEM_027] The Reserved Memory Control TLV can be present inside the Type 1 Tag and an NFC Forum Device SHALL be able to read and process it.It provides control information about the location and the size of the reserved byte area. [RQ_T1T_MEM_028] If the vendor delivers the Type 1 Tag in the READ-ONLY state, the NFC Forum device MAY use the Reserved Memory Control TLV to indicate control information for a mix of reserved and lock areas.The encoding of the 3 TLV fields of the Reserved Memory Control TLV is: • T is equal to 02h. • L is equal to 03h.• V is composed of 3 bytes that uniquely identify the position and the size of the reservedarea. The 3 bytes are encoded as follows:• Position, MSB. It codes the position inside the tag of the reserved area. The Position byteconsists of 2 parts (to calculate the bytes address from the position byte, see below): • PagesAddr. Most significant nibble, coded as number of pages (0h=0…Fh=15) • ByteOffset. Least significant nibble, coded as number of bytes (0h=0…Fh=15) • Size. Middle byte, coded as number of bytes (1h=1, FFh=255, 0h=256). It indicates thesize in bytes of the reserved area. • Partial Page Control, LSB. The partial page control provides the size in bytes of a page. Itis split up into two nibbles of 4 bits each:• Least significant nibble (BytesPerPage nibble), coded as 2n (0h=RFU,1h=1…Fh=15). It indicates the number of bytes per page. • Most significant nibble is RFU.[RQ_T1T_MEM_029] The NFC Forum device SHALL calculate the byte address (ByteAddr) of each reserved area as follows:ByteOffset PageAddr ByteAddr ge BytesPerPa +⋅=2The ByteAddr is calculated from the beginning of the overall memory of the tag (i.e., Byte 0 of Block 0 is indicated by ByteAddr equal to 0).The page definition has nothing to do with the block definition used by tag access commands.2.4.5 NDEF Message TLVThe NDEF Message TLV is always present inside the Type 1 Tag. It stores the NDEF message inside the Value field (see [NDEF]).[RQ_T1T_MEM_030] The NFC Forum device SHALL be able to read and process the first (or mandatory) NDEF message.Further NDEF Message TLV blocks can be present.。
丹佛斯fc360,profibus,dp,协议
竭诚为您提供优质文档/双击可除丹佛斯fc360,profibus,dp,协议篇一：profibus与danfoss变频器通讯基于pRoFibus―dp总线的danfoss变频器应用thecontrolofFrequencyconverters-danfossbasedonprofi bus-dp一、概述pRoFibus―dp是一种坚固耐用、功能强大、开放性好的通讯总线,主要用于与现场设备的连接并快速、循环地进行数据交换。
除此之外还具有如下优点：符合现代控制思想——集散控制，从而提高系统的实时性和可靠性；通过pRoFibus―dp总线不但能够将不同生产厂商的控制元件（带dp口）连接起来，形成一个兼容、完善的控制系统，而且有利于提高系统的灵活性和可移植性；由于pRoFibus―dp总线的使用，烟厂根据需要能够很方便地组建信息化管理网络。
所以，pRoFibus―dp总线深受设计者和用户的欢迎。
danfoss变频器是由丹佛斯公司生产的、广泛使用的一种变频调速产品。
由于其采用了崭新的VVcplus控制原理，在整个速度范围内能承受极大的负载冲击，同时对参数的变化能做出快速的反应，另外它还具有体积小（书本式设计）、操作简单等优点。
本文主要针对采用pRoFibus—dp总线如何来实现danfoss变频器的控制，以达到与上、下游机速度相匹配。
此控制在烟机生产线产品中具有一定的典型性，可不加修改地进行移植复用。
二、硬件电路下面的硬件电路是某卷烟厂制丝线pRoFibus―dp总线的一部分，现拿来用以说明基于pRoFibus―dp总线的danfoss变频器应用。
图1硬件电路示意图(1)当系统满足某些条件时：plc→通过pRoFibus―dp总线控制电机的启停、运行速度；(2)通过pRoFibus―dp总线，变频器向plc反馈电机m 运行的状态信息，如:电机运行速度、电机扭矩等。
三、变频器参数设置带dp接口的danfoss变频器除了参数组0～参数组6的设置外,还必须针对pRoFibus―dp总线通讯进行如下参数的设置:(1)512报文结构（telegRampRoFile）：danFoss[1]danfoss变频器(带dp接口)与pRoFibus―dp总线通讯有两种控制字结构可供选择：pRoFidRiVe[1]和danFoss[1],其中pRoFidRiVe为国际标准,danFoss[1]为丹佛斯标准。
Type0和Type1型配置请求
Type0和Type1型配置请求
前面的文章中介绍过有两种类型的配置空间，Type0和Type1，分别对应非桥设备（Endpoint）和桥设备（Root和Switch端口中的P2P桥）。
Type0还是Type1是由事务层包（TLP）包头中的Type Field所决定的，而读还是写则是由TLP包头中的Format Field所决定的。
分别以下两张图所示：
之前的文章中强调过，PCIe中只有Root才可以发起配置空间读写请求，并且我们知道Root的每个端口中都包含有一个P2P桥。
当Root发起配置空间读写请求时，相应的桥首先检查请求的BDF中的Bus号是否与自己的下一级总线号（Secondary Bus Number）相等，如果相等，则先将Type1转换为Type0，然后发给下一级（即Endpoint）。
如果不相等，但是在自己的下一级总线号（Secondary Bus Number）和最后一级总线号（Subordinate Bus Number）之间，则直接将Type1型请求发送给下一级。
如果还是不相等，则该桥认为这一请求和自己没什幺关系，则忽略该请求。
中国移动5G SSB配置建议0815
MOD NREXTERNALCELL: Mcc="460", Mnc="08", GnodebId=790158, CellId=68, DlArfcn=504990;
备注：如果现网除锚点小区外其他小区也添加了5G邻区，则相关小区都要添加5G相邻频点；否则，只要锚点小区添加5G相邻频点即可
5
Thank You.
Copyright©2016 Huawei Technologies Co., Ltd. All Rights Reserved. The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.
关于5G的问题及答案
关于5G的问题及答案1、1个RBG中最大包含的PRB数量是多少?（） [单选题] *A.32B.4C.16(正确答案)D.82、3GPP协议规定，C波段的NR系统支持的子载波间隔有以下哪（） *A.60Khz(正确答案)B.120KhzC.15Khz(正确答案)D.30Khz(正确答案)3、5G RAN2.1 64T64R的AAU可以最多支持多少种广播波束场景配置?（） [单选题] *A.17(正确答案)B.3C.8D.54、5G SA组网场景下服务小区的重选参数是在哪个系统消息下发的?（） [单选题] *A.SIB1B.SIB3C.SIB4D.SIB2(正确答案)5、5G SA组网下支持以下哪些语音方案?（） *A.CSFBB.VoLTEC.VoNR(正确答案)D.EPS fabl1lback(正确答案)6、5G的C波段中，Numerology取1时对应的子载波被间隔是多大？（）[单选题] *A.5 khzB.60 khzC.30 khz(正确答案)D.15 khz7、5G无线资源调度的最小单位是以下哪项?（） [单选题] *A.子帧B.符号C.无线帧D.时隙(正确答案)8、64T64R AAU在默认配置场景下，广播波束的水平3dB波宽和垂直3d波宽分别是多少?（） [单选题] *A.105°、6°(正确答案)B.105°、12°C.65°、6°D.65°、12°9、gNodeB CD/DU分离架构中,CU和DU之间的接口是以下哪个?（） [单选题] *A.X2B.eCPRIC.N2D.F1(正确答案)10、ITU对于5G mMTC业务要求的连接能力是多少?（） [单选题] *A.十万终端/小区B.百万终端/小区C.十万终端/平方公里D.百万终端/平方公里(正确答案)11、NR取消了LTE中的CRS功能，其测量可以由NR的哪些代替？（） *A.PDCCHB.SSB(正确答案)C.CSI-RS(正确答案)D.PDSCH12、NR系统中1个CCE包含了多少个REG?（） [单选题] *A.8B.6(正确答案)C.4D.213、NR系统中1个REG包含了多少个RE?（） [单选题] *A.9B.6C.14D.12(正确答案)14、NR子载波配置为30Khz时，其对应每时隙的符号数和时隙数分别是多少?（） [单选题] *A.14;40B.12;20C.14;20(正确答案)D.12;4015、NSA锚点切换流程中使用的是以下哪种事件报告?（） [单选题] *A.A4B.A3(正确答案)C.A5D.A616、Option3x架构下，上行分流的控制参数是在以下哪个网元里配置的？（） [单选题] *A.UEB.SGWC.gNodeBD.eNodeB(正确答案)17、SA场景下，终端进行异频重选时需要用到哪些系统消息里的参数?（） *A.SIB2(正确答案)B.SIB4(正确答案)C.SIB3D.SIB518、SA组网中，UE做小区搜索的第一步是以下哪项?（） [单选题] *A.帧同步，获取PCI组编号B.获取小区信号质量C.半帧同步，获取PCI组内ID(正确答案)D.获取小区其它信息19、SSB的时域占用几个符号?（） [单选题] *A.2B.8C.6D.4(正确答案)20、UE接入LTE网络后，LTE小区会向UE发送哪条消息用以测量NR小区信号?（） [单选题] *A.B2B.B1(正确答案)C.A1D.A221、标识NR随机接入竞争解决完成的是哪个消息?（） [单选题] *A.Msg3B.Msg1C.Msg4(正确答案)D.Msg222、大气环境对无线信号衰减景响较大的频段主要集中在哪个区（） [单选题] *A.70Ghz附近B.28Ghz附近C.60Ghz附近(正确答案)D.3.5Ghz附近23、关于NR s1ot结构，以下哪些描述是正确的?（） *A.口无论子载波带宽如何配置,1个 s1ot的符号数固定为14个B.口下行s1ot只能传下行数据(正确答案)C.口s1ot中的符号包含下行，上行和灵活配置三种(正确答案)D.口下行s1ot也可以传上行数据24、基于以下哪种事件的上报触发育重定向流程?（） [单选题] *A.A3B.A1C.A2(正确答案)D.A425、每个终端最大可以配置多少个专用BWP?（） [单选题] *A.2个B.8个C.4个(正确答案)D.16个26、如果开启了基于业务量的SCG添加，那么eNodeB是通过哪个协议层的业务测量触发的？（） [单选题] *A.PDCPB.PHYC.MACD.RLC(正确答案)27、如果无线RF性能较差，会影响数传过程中的哪些指标？（） *A.BLER(正确答案)B.MCS(正确答案)C.RANK(正确答案)D.调度次数(正确答案)28、上下行解耦特性开通后的增益有哪些?（） *A.口NR小区中心用户下行吞吐率提升B.口NR小区边缘用户体验得到改善(正确答案)C.口N小区边缘上行吞吐率提升(正确答案)D.口NR小区用户数增加(正确答案)29、为了获得较高的5G下载速率，在默认情况下，建议可以把UE开户信息里的QCI配置为以下哪些?（） *B. QCI 9(正确答案)C. QCI 1D. QCI 8(正确答案)30、为了减少5G辅站间的来回频繁变更，可以有以下哪些措施?（） *A.口减少幅度磁滞hysB.口增加幅度磁滞hys(正确答案)C.口增加time-to-trigger的值(正确答案)D.口减少time-to-trigger的值31、为了解决NR网络深度覆盖的问题，以下哪项措施是不可取的?（） [单选题] *A.采用低频段组网B.使用 Lampsi te提供室分覆盖C.增加NR系统带宽(正确答案)D.增加AAU发射功率32、为应对大规模连接,5G适应mMTC物联网场景时，推荐采用的SCS子载波间隔为多少?（） [单选题] *A.60KhzB.30KhzC.15khz(正确答案)D.120Khz33、相比4G,5G重新定义了核心网NGC，主要包括哪些网元？（） *A.UPF(正确答案)C.AMF(正确答案)D.SMF(正确答案)34、以下关干NR子载被带宽的描述，正确的是哪些项?（） *A.SSB最大的子载波带宽可以支持 240kHz(正确答案)B.Sub6G场景下，业务信道最大子载波带宽可以支持60kz(正确答案)C.Above6G场景下，业务信道最大子载波带宽可以支持240kHzD.长格式的PRACH信道可以支持 60kHz子载波带宽35、以下关于 PRACH信道频域位置的指述,正确的是哪一项?（） [单选题] *A.必须置在频带的最下方B.必须包含在初始BWP内(正确答案)C.必须包含在专用BWP内D.可以放在须域任何位置36、以下关于上行DFT-S-OFDM波形的描述，正确的是哪一项?（） [单选题] *A.该波形只支持连续的频率资源分配(正确答案)B.该波形下可以支持多流复用C.该波形支持更灵活的频域资源分配D.该波形PAPR高37、以下关于5G NSA组网的描述，正确的是哪些项?（） *A.Option3架构信令SCG添加信令流程比较简单，现网推荐使用B.NsA组网既可以使用EPC也可以使用5GC作为核心网(正确答案)C.NSA组网一定是采用EPC作为核心网D.Option3x架构对4G侧硬件没有改造要求，现网推荐使用(正确答案)38、以下关于5G小区选择的描述，正确的是哪些项?（） *A.UE优先采用initial search的方式进行小区搜索B.在基于RSRQ的小区选择过程中，UE需要计算补偿值C.UE优先采用stored information的方式进行小区搜(正确答案)D.在基于RSRP的小区选择过程中， UE需要计算补偿值(正确答案)39、以下关于Massive MIMO天线的描述，错误的是哪项?（） [单选题] *A.一般采用AAU作为解决方案B.水平面和垂直面都有多个天线端口C.天线的阵子数可以大于物理端口数D.天线的阵子数和物理端口是一样的(正确答案)40、以下关于NR slot结构的描述，正确的是哪些项？（） *A.下行slot只能传下行数据(正确答案)B.slot中的符号包含下行，上行和灵活配置三种(正确答案)C.无论子载波带宽如何配置，1个 slot的符号数固定为14个D.下行slot也可以传上行数据41、以下关于NSA场景下UE在5G侧接入的描述，错误的是哪一项?（） [单选题] *A.UE和基站之间没有RRC信令B.优先采用基于非竞争的随机接入流程C.UE无需进行小区选择判决D.UE通过syncraster进行扫描找到SSB的位置(正确答案)42、以下关于SA网络中，NR小区重选准则的描述，错误的是哪一项？（） [单选题] *A.满足判决条件至少5s后才会触发重选(正确答案)B.触发最好小区重选时需要满足R_sC.R_n=Qmeeas,n- QoffsetD.R_n=Qmeeas,n+ Qhyst43、以下关于下行频率资源分配的描述，错误的是哪项?（） [单选题] *A.支持type0和 type1两种分配方式B.type0是RBG粒度的分配方式，支持非连续分配和连续分配C.type0是RB粒度的分配方式，仅支持非连续分配(正确答案)D.type1是RB粒度的分配方式，仅支持连续分配44、以下关于下行调度过程的描述，正确的是哪些项？（） [单选题] *A.下行调度过程中的MCS计算主要依靠CQI上报(正确答案)B.UE可以在 PUCCH和 PUSCH上报CQIC.当采用全带CQ1上报时，下行分配RB时采用频率选择算法进行分配D.下行调度需要终端发起请求45、以下几类数传问题中，哪一项不仅仅是空口质量的问题造成的？（） [单选题] *A.调度次数低(正确答案)B.IBLER高C.RAK低D.MCS低46、以下哪个场景属于NR基于非竞争的随机接入?（） [单选题] *A.初始RRC连接建立B.波束恢复(正确答案)C.RRC连接重建D.上行数据到达47、以下哪类测量上报事件用于同频切换的触发？（） [单选题] *A.A3(正确答案)B.A1C.A2D.A448、以下哪项是NR中的基本调度单位?（） [单选题] *A.REB.REGED.PRB(正确答案)49、以下哪些5G组网架构使用的是 SCG split bearer?（） *A.Option7x(正确答案)B.Option4aC.Option3x(正确答案)D.Option350、以下哪些功能是由PDCP层进行处理的?（） *A.IP头压缩(正确答案)B.完整性校验(正确答案)C.加解密(正确答案)D.QoS处理51、以下哪些属于5GC网络的特点？（） *A.基于NFV技术(正确答案)B.云化部署(正确答案)C.基于业务的架构(正确答案)D.支持网络切片(正确答案)52、以下哪些终端能力会影响峰值速率的测试结果?（） *A.SRS天线选择能(正确答案)B.UE支持的带宽(正确答案)C.MINO最大流数(正确答案)D.256QA支持能力(正确答案)53、以下哪种SCS不允许用于SSB?（） [单选题] *A.60KHz(正确答案)B.30KHzC.120KHzD.15KHz54、在5GC中,以下哪个模块用于用户的鉴权管理?（） [单选题] *A.AMFB.AUSF(正确答案)C.PCFD.SMF55、在NR组网下，为了用户能获得接近上行最高速率，其MCS值最低要求应该是多少?（） [单选题] *A.16B.32C.25(正确答案)D.2056、在Option3x架构下，双连接建立过程中，eNB会向MME发送ERAB M odify IND消息，该消息中携带的IP地址是属于以下哪个网元的？（） [单选题] *A.UEB.SGWC.eNodeBD.gNodeB(正确答案)57、在R15标准中，定义系统消息SI有多少种？（） [单选题] *A.11B.10C.9(正确答案)D.1258、在R15的标准中定义的CU和DU分离，以下哪些协议层属于DU部分?（） *A.RLC(正确答案)B.RRCC.MAC(正确答案)D.PDCF59、在RAN3.0版本里，小区专用BWP内PDCCH带宽最小配置是多少?（） [单选题] *A.6RB(正确答案)B.24RBC.48RBD.12RB60、在高频场景下，对于所有的信道和信号，能够使用的最大子载波间隔是多少?（） [单选题] *A.240KHZB.120KHZ(正确答案)C.30KHZD.60KHZ。
ASN.1基本语法和编码规则
ASN.1基本语法和编码规则1 ASN.1 简介ASN.1 (Abstract Syntax Notation One)，抽象语法标记，是描述抽象类型和值的标记，缩写为ASN.1。
它用于对通过接口和通信媒体进行传输的信息的抽象描述，广泛应用于各种通信协议的说明中。
ASN.1是一个很灵活的标记法，它允许定义众多的数据类型——从整数和位串等简单类型到如集合、序列等的组合结构，还可以是其它复杂定义的类型。
一个ASN.1定义可以选用不同的编码规则，但解码器必须采用和编码器相同的编码规则。
目前标准化的编码规则有4个：BER、DER、CER、PER。
BER在19世纪80年代初形成，广泛应用于各种通信协议中，比如SNMP、MHS、TSAPI 等；DER是BER的一种特殊形式，用于对安全性敏感的应用，比如电子商务，要求对一条消息的编码和解码有且只有一条途径；CER是BER 的另一种特殊形式，类似于DER，但它适用于长消息，可以在知道整条消息之前就开始编码，实际中CER很少应用，这是因为工业界把DER作为安全编码的优先方法；PER在上述编码规则之后出现，因它的高效算法而闻名，它的编码速度和压缩程度比BER高，PER适用于带宽资源缺乏的应用，比如空中交通控制和音频—视频通信等。
2 BER的编码规则和传输语法2.1基本规则BER（Basic Encoding Rules）是ASN.1中最早定义的编码规则。
每种BER 编码方法都由三或四部分组成：（1）Tag octets：定义了ASN.1值的类和标签值，并指明编码方法是简单化的还是结构化的。
（2）Length octets：对于定长编码方法，它指出了内容octet的个数；对于结构化、非定长编码方法，它指明了长度是不确定的。
（3）Value octets：对于简单的、定长编码方法，它给出了值的具体表示；对于结构化的方法，它给出了值的内容的BER编码的串联。
（4）End-of-values octets：对于结构化、非定长的编码方法，它表示内容结束；对于其它方法，没有该部分。
OSPF路由协议：LSA1、LSA2与路由计算步骤
OSPF路由协议：LSA1、LSA2与路由计算步骤1、OSPF的区域OSPF路由协议作为⼀种动态路由协议，其⽣成路由表的过程依赖于⽹络中每台路由器保持⼀致的LSDB(链路状态数据库）。
随着⽹络中路由器的不断增多，LSDB会越来越庞⼤，拓扑结构的改变也容易引起⽹络的“动荡”。
因此，动态路由协议（如OSPF、IS-IS）都提供将整个⽹络划分成多个区域的能⼒，减少LSDB的⼤⼩和维护LSDB的开销，也减少LSA泛洪的影响。
在OSPF中，被划开的所有区域必须以⾻⼲区域为中⼼，也即其他区域必须与⾻⼲区域相连。
2、LSA的含义LSA（Link-State Advertisement,链路状态通告），是OSPF路由协议的协议报⽂中携带的、⽤于进⾏路由计算的信息。
根据⽤途及作⽤范围的不同，可以分为11类（即type1~11）。
其中，⽤于区域内路由通告的是type1、type2，⽤于区域间路由通告的主要有type3、type4、type5、type7。
本⽂的主要内容为介绍LSA中⽤于区域内路由通告的LSA1和LSA2，以及路由计算的步骤。
3、LSA type 1 （Router LSA)每台路由器会为⾃⼰所处的每⼀个区域产⽣⼀份RouterLSA，该LSA包含本区域所有链路的状态信息。
LSA1消息包含的字段：LS Age :DoNotAge Flag和age数值（秒）Option位LS type ：1Link State IDAdvertising RouterSequence NumberCheckSumFlagsNumber Of Links: OSPF有向图上的LinkPoint to pointID:邻居路由器的RID；Data：⾃⼰接⼝的IPTransNetwork：MA类型链路ID：DR的接⼝IP ；Data：⾃⼰接⼝IPStubNetwork：末节类型链路/⽹络ID：⽹络号 Data：掩码Virtual LinkID：vlink对端ABR的RID ；Data：本地Vlink的IP有向图的说明每个实节点外出⽅向的链路成本是该接⼝的成本（OSPF Cost值）。
什么是 type1_type2
桌面视频一直是基于video for windows技术的，type2 DV avi 采用VFW格式存储，所以兼容性比较好一些，多数视频软件都可以处理。type 1 DV在2000年以前得到的支持有限，比如premiere5.1就不能支持type 1 DV AVI。最早支持type 1 DV的是ulead的media studio pro6和video studio 3 DV版。 到现在随着Directshow技术的推广，type 1 DV的支持也越来越好，现在premiere 6也可以支持type 1 DV.
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
竭诚为您提供优质文档/双击可除
type1协议
篇一：14443协议浅谈—type_a与type_b之比较[1]
iso/iec14443协议浅谈—typea与typeb之比较
一、非接触ic卡简介
非接触ic卡又称射频卡，是射频识别技术和ic卡技术有机结合的产物。
它解决了无源（卡中无电源）和免接触这一难题，具有更加方便、快捷的特点，广泛用于电子支付、通道控制、公交收费、停车收费、食堂售饭、考勤和门禁等多种场合。
非接触ic卡与条码卡、磁卡、接触式ic卡比较具有高安全性、高可靠性、使用方便快捷。
这主要是由其技术特点决定，在近距耦合应用中主要遵循的标准是iso/iec14443。
二、iso/iec14443简介
iso/iec14443规定了邻近卡（picc）的物理特性；需要供给能量的场的性质与特征，以及邻近耦合设备（pcds）和邻近卡（piccs）之间的双向通信；卡（piccs）进入邻近耦
合设备（pcds)时的轮寻，通信初始化阶段的字符格式，帧结构，时序信息；非接触的半双功的块传输协议并定义了激活和停止协议的步骤。
传输协议同时适用于typea和typeb。
typea和typeb型卡片主要的区别在于载波调制深度及二进制数的编码方式和防冲突机制。
1、调制解调与编码解码技术
根据信号发送和接收方式的不同，iso/iec14443-3定义了typea、typeb两种卡型。
它们的不同主要在于载波的调制深度及二进制数的编码方式。
从pcd向picc传送信号时，二者是通过13.56mhz的射频载波传送信号。
从picc向pcd传送信号时，二者均通过调制载波传送信号,副载波频率皆为847khz。
图1：tyepa、b接口的通信信号
typea型卡在读写机上向卡传送信号时，是通过
13.65mhz的射频载波传送信号。
其采用方案为同步、改进的miller编码方式，通过100%ask传送；当卡向读写机具传送信号时，通过调制载波传送信号。
使用847khz的副载波传送manchester编码。
简单说，当表示信息“1”时，信号会有0.3微妙的间隙，当表示信息“0”时，信号可能有间隙也可能没有，与前后的信息有关。
这种方式的优点是信息区别明显，受干扰的机会少，反应速度快，不容易误操作；缺点是在需要持续不断的提高能量到非接触卡时，能量有可能
会出现波动。
typeb型卡在读写机具向卡传送信号时，也是通过13.65mhz的射频载波信号，但采用的是异步、nRz编码方式，通过用10%ask传送的方案；在卡向读写机具传送信号时，则是采用的bpsk编码进行调制。
即信息“1”和信息“0”的区别在于信息“1”的信号幅度大，即信号强，信息“0”的信号幅度小，即信号弱。
这种方式的优点是持续不断的信号传递，不会出现能量波动的情况；
从pcd到picc的通信信号接口主要区别在信号调制方面，typea调制使用RF工作场的ask100%调制原理来产生一个“暂停（pause）”状态来进行pcd和picc间的通信。
图2typea调制波形
typeb调制使用RF工作场的ask10%调幅来进行pcd和picc间的通信。
调制指数最小应为8%，最大应为14%。
图3typeb调制波形
根据二者的设计方案不同，可看出，typea和typeb有以下不同：
◆typeb接收信号时，不会因能量损失而使芯片内部逻辑及软件工作停止。
在npause到来，typea的芯片得不到时钟，而typeb用10％ask，卡片可以从读写器获得持续的能量；typeb时容易稳压，所以比较安全可靠。
typea卡采用
100％调制方式，在调制发生时候无能量传输，仅
仅靠卡片内部电容维持，所以卡片的通讯必须达到一定的速率，在电容电量耗完之前结束本次调制，否则卡片会复位。
◆负载波采用bpsk调制技术，typeb较typea方案降低了6db的信号燥声，抗干扰能力更强。
◆外围电路设计简单。
读写机具到卡及卡到读写机具的编码方式均采用nRz方案，电路设计对称，设计时可使用简单的uaRts，typeb更容易实现。
2、防冲突机制
iso/iec14443-3规定了typea，typeb的防冲突机制。
二者防冲突机制的原理完全不同。
前者是基于bit冲突检测协议，后者则是通过字节、帧及命令完成防冲突。
RFid的核心是防冲突技术，这也是和接触式ic卡的主要区别。
typeapicc防冲突和通信使用标准帧用于数据交换，并按以下顺序组成：
—通信开始；
—n*（8个数据位+奇数奇偶校验位），n≥1。
每个字节的lsb首先被发送。
每个字节后面跟随一个奇数奇偶校验位。
奇偶校验位p被设置，使在（b1到b8，p）中1s的数目为奇数；
—通信结束。
图4typea标准帧
typeapicc的初始化和比特冲突检测协议是当至少两个picc同时传输带有一个或多个比特位置（该位置内至少有两个picc在传输补充值）的比特模式时，pcd会检测到冲突。
在这种情况下，比特模式合并，并且在整个（100%）位持续时间内载波以负载波进行调制。
图5typeapicc状态图
typebpicc防冲突和通信初始化期间使用的字节、帧和命令的格式。
picc和pcd之间的字节通过字符来发送和接收，在防冲突序列期间，字符的格式如下：—1个逻辑“0”起始位；
—8个数据位发送，首先发送lsb；
—1个逻辑“1”停止位。
用一个字符执行一个字节的发送需要10etu。
图6typeb字符格式
pcd和picc按帧发送字符。
帧通常用soF（帧的起始）和eoF（帧的结束）定界。
在防冲突序列期间，可能发生两个或两个以上的picc
同时响应：这就是冲突。
命令集和允许pcd处理冲突序列以便及时分离picc传输。
在完成防冲突序列后，picc通信将完全处于pcd的控制
之下，每次只允许一个picc通信。
防冲突方案以时间槽的定义为基础，要求picc在时间槽内用最小标识数据进行应答。
时间槽数被参数化，范围从1到某一整数。
在每一个时间槽内，picc响应的概率也是可控制的。
在防冲突序列中，picc仅被允许应答一次。
从而，即便在pcd场中有多个卡，在一个时间槽内也仅有一个卡应答，并且pcd在这个时间槽内能捕获标识数据。
根据标识数据，pcd能够与被标识的卡建立一个通信信道。
防冲突序列允许选择一个或多个picc以便在任何时候进行进一步的通信。
篇二：1、http协议
http协议
一、http概述
二、http协议特点：
1支持客户/服务器模式(b/s)
通常这里所指的客户端是浏览器
2简单快速
客户向服务器请求服务时，只需传送请求方法和路径，请求方法常用的有get/head/post。
每种方法规定了客户与服务器联系的不同类型。
后面会作详解说明。
3灵活http协议允许传输任意类型的数据对象，正在传输的类型由context-type加以标记。
通过在head中定义meta标
签指定。
4无连接：
无连接的含义是指限制每次连接只处理一个请求服务
器修理完客户的请求，并收到客户的应答后，即断开连接。
采用这种方式可以节省传输时间。
5无状态：
http协议是无状态协议。
无状态是指协议对于事务处理没有记忆能力。
缺少状态意味着如果后续处理需要前面的信息，则它必须重传，这样可能导致每次连接传递的数据量增大。
另一方面，在服务器不需要先前信息时他的应答就较快。
三、http协议url：
就像每家每户都有一个门牌地址一样，每个网页也都有一个internet地址。
当你在浏览器的地址框中输入一个uRl 或是单击一个超级链接时，uRl就确定了要浏览的地址。
浏
览器通过超文本传输协议(http)，将web服务器上站点的网页代码提取出来，并翻译成漂亮的网页。
uRl由三部分组成：资源类型、存放资源的主机域名、资源文件名。
一个常用的url地址如下：:80/server/index.html下
面我们对这个url进行详细说明.1、[]这一部分是说明这个请求是基于http协议的，这里请大家注意，我们日常使用
的浏览器默认都是基于http协议的所以这一部分内容我们。