throbber
INTERNATI O NAL
`
`STANDARD
`
`SO/IEC
`
`mm
`
`First edition
`mm
`
`,p.
`
`Identi ication cards — ontactless
`
`Integrate. Circmt s carcs — 'rOXImIty
`
`,.
`
`t'
`
`.
`
`.
`
`Partie 4: Protocole de transmission
`
`0 IE
`
`14443-42001 E
`
`Apple Ex.
`
`I
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`PDF disclaimer
`This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
`be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
`file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
`area.
`Adobe is a trademark of Adobe Systems Incorporated.
`Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
`were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
`that a problem relating to it is found, please inform the Central Secretariat at the address given below.
`
`© ISO/IEC 2001
`All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
`or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
`in the country of the requester.
`ISO copyright office
`Case postale 56 CH-1211 Geneva 20
`Tel. + 41 22 749 01 11
`Fax + 41 22 749 09 47
`E-mail copyright@iso.ch
`Web www.iso.ch
`Printed in Switzerland
`
`ii
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 2
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`Contents
`
`Scope...............................................................................................................................................................1
`1
`Normative references ....................................................................................................................................1
`2
`Terms and definitions....................................................................................................................................1
`3
`Symbols and abbreviated terms...................................................................................................................2
`4
`Protocol activation of PICC Type A..............................................................................................................4
`5
`Request for answer to select ........................................................................................................................6
`5.1
`Answer to select.............................................................................................................................................6
`5.2
`Structure of the bytes....................................................................................................................................7
`5.2.1
`Length byte.....................................................................................................................................................7
`5.2.2
`Format byte.....................................................................................................................................................7
`5.2.3
`Interface byte TA(1)........................................................................................................................................8
`5.2.4
`Interface byte TB(1)........................................................................................................................................8
`5.2.5
`Interface byte TC(1)........................................................................................................................................9
`5.2.6
`5.2.7 Historical bytes ..............................................................................................................................................9
`5.3
`Protocol and parameter selection request................................................................................................10
`5.3.1
`Start byte.......................................................................................................................................................10
`5.3.2
`Parameter 0...................................................................................................................................................11
`5.3.3
`Parameter 1...................................................................................................................................................11
`5.4
`Protocol and parameter selection response.............................................................................................12
`5.5
`Activation frame waiting time.....................................................................................................................12
`5.6
`Error detection and recovery......................................................................................................................12
`5.6.1 Handling of RATS and ATS.........................................................................................................................12
`5.6.2 Handling of PPS request and PPS response ............................................................................................13
`5.6.3 Handling of the CID during activation........................................................................................................13
`6
`Protocol activation of PICC Type B............................................................................................................14
`7
`Half-duplex block transmission protocol ..................................................................................................14
`7.1
`Block format .................................................................................................................................................15
`7.1.1
`Prologue field ...............................................................................................................................................15
`7.1.2
`Information field...........................................................................................................................................17
`7.1.3
`Epilogue field................................................................................................................................................18
`7.2
`Frame waiting time.......................................................................................................................................18
`7.3
`Frame waiting time extension.....................................................................................................................18
`7.4
`Power level indication .................................................................................................................................19
`7.5
`Protocol operation .......................................................................................................................................20
`7.5.1 Multi-Activation ............................................................................................................................................20
`7.5.2 Chaining........................................................................................................................................................20
`7.5.3 Block numbering rules ................................................................................................................................21
`7.5.4 Block handling rules....................................................................................................................................21
`7.5.5
`Error detection and recovery......................................................................................................................22
`8
`Protocol deactivation of PICC Type A and Type B...................................................................................23
`8.1
`Deactivation frame waiting time.................................................................................................................23
`8.2
`Error detection and recovery......................................................................................................................23
`Annex A (informative) Multi-Activation example....................................................................................................24
`Annex B (informative) Protocol scenarios..............................................................................................................25
`B.1
`Notation.........................................................................................................................................................25
`B.2
`Error-free operation .....................................................................................................................................25
`B.2.1 Exchange of I-blocks ...................................................................................................................................25
`B.2.2 Request for waiting time extension ...........................................................................................................26
`
`© ISO/IEC 2001 – All rights reserved
`
`iii
`
`Apple Ex. 1031, p. 3
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`B.2.3 DESELECT ................................................................................................................................................... 26
`B.2.4 Chaining....................................................................................................................................................... 26
`B.3
`Error handling.............................................................................................................................................. 27
`B.3.1 Exchange of I-blocks .................................................................................................................................. 27
`B.3.2 Request for waiting time extension........................................................................................................... 28
`B.3.3 DESELECT ................................................................................................................................................... 30
`B.3.4 Chaining....................................................................................................................................................... 30
`Annex C (informative) Block and frame coding overview .................................................................................... 33
`
`iv
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 4
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`Foreword
`
`ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
`form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
`participate in the development of International Standards through technical committees established by the
`respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
`collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
`liaison with ISO and IEC, also take part in the work.
`
`International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
`
`In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
`Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
`Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
`
`International Standard ISO/IEC 14443-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
`technology, Subcommittee SC 17, Identification cards and related devices.
`
`ISO/IEC 14443 consists of the following parts, under the general title Identification cards — Contactless integrated
`circuit(s) cards — Proximity cards:
`
`œ Part 1: Physical characteristics
`
`œ Part 2: Radio frequency power and signal interface
`
`œ Part 3: Initialization and anticollision
`
`œ Part 4: Transmission protocol
`
`Annexes A, B and C of this part of ISO/IEC 14443 are for information only.
`
`© ISO/IEC 2001 – All rights reserved
`
`v
`
`Apple Ex. 1031, p. 5
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`Introduction
`
`ISO/IEC 14443 is one of a series of International Standards describing the parameters for identification cards as
`defined in ISO/IEC 7810, and the use of such cards for international interchange.
`
`The protocol as defined in this part of ISO/IEC 14443 is capable of transferring the application protocol data units
`as defined in ISO/IEC 7816-4. Thus application protocol data units may be mapped as defined in ISO/IEC 7816-4
`and application selection may be used as defined ISO/IEC 7816-5.
`
`ISO/IEC 14443 is intended to allow operation of proximity cards in the presence of other contactless cards
`conforming to ISO/IEC 10536 and ISO/IEC 15693.
`
`The International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) draw
`attention to the fact that it is claimed that compliance with this part of ISO/IEC 14443 may involve the use of
`patents.
`
`ISO and IEC take no position concerning the evidence, validity and scope of this patent right.
`
`The holders of these patent rights have assured ISO and IEC that they are willing to negotiate licences under
`reasonable and non discriminatory terms and conditions with applicants throughout the world. In this respect, the
`statements of the holders of patent rights are registered with ISO and IEC. Information may be obtained from:
`
`US Patent US5359323
`
`FRANCE TELECOM
`Centre National d’Etudes des Télécommunications
`38-40 rue de Général Leclerc
`92794 Issy-les-Molineaux
`Cedex 9
`France
`
`MOTOROLA
`Motorola ESG
`207 route de Ferney
`P O Box 15
`1218 Grand-Saconnex
`Geneva
`Switzerland
`
`OMRON
`Intellectual Property Department
`Law & Intellectual Property H.Q.
`20, Igadera Shimokaiinji
`Nagaokakyo City
`Kyoto 617-8510
`Japan
`
`ON-TRACK INNOVATIONS
`Z.H.R. Industrial Zone
`P O Box 32
`Rosh-Pina 12000
`Israel
`
`JP 2129209, JP 2561051, JP 2981517
`
`Contactless Responding Unit
`
`Patent EP 0 492 569 B1
`
`A system and method for the non-contact
`transmission of data.
`
`vi
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 6
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`The following companies may hold patents relating to this part of ISO/IEC 14443 but have not provided details of
`the patents or agreed to provide licences.
`
`ISO/IEC 14443-4:2001(E)
`
`US 4 650 981
`
`US Patent No. 4, 661,691
`
`WO 89 05549 A
`
`WAYNE S FOLETTA
`CA 95129, USA
`4760 Castlewood Drive
`San Jose, California CA 9512
`USA
`
`JOHN W HALPERN
`C/O Vincent M DeLuca
`Rothwell, Figg, Ernst & Kurz, p.c.
`555 Thirteenth Street, N.W.
`Suite 701 East Tower
`Washington, D.C. 20004
`
`MAGELLAN CORPORATION
`8717 Research Drive
`Irvine
`CA 92618
`USA
`
`Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 14443 may be the subject of
`patent rights other than those identified above. ISO and IEC shall not be held responsible for identifying any or all
`such patent rights.
`
`© ISO/IEC 2001 – All rights reserved
`
`vii
`
`Apple Ex. 1031, p. 7
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`Apple Ex. 1031, p. 8
`Apple Ex. 1031, p. 8
` Apple v. Fintiv
`Apple v. Fintiv
`|PR2020-00019
` IPR2020-00019
`
`

`

`INTERNATIONAL STANDARD
`
`ISO/IEC 14443-4:2001(E)
`
`Identification cards — Contactless integrated circuit(s) cards —
`Proximity cards — Part 4: Transmission protocol
`
`1 Scope
`
`This part of ISO/IEC 14443 specifies a half-duplex block transmission protocol featuring the special needs of a
`contactless environment and defines the activation and deactivation sequence of the protocol.
`
`This part of ISO/IEC 14443 is intended to be used in conjunction with other parts of ISO/IEC 14443 and is
`applicable to proximity cards of Type A and Type B.
`
`2 Normative references
`
`The following normative documents contain provisions, which, through reference in this text, constitute provisions
`of this part of ISO/IEC 14443. For dated references, subsequent amendments to, or revisions of, any of these
`publications do not apply. However, parties to agreements based on this part of ISO/IEC 14443 are encouraged to
`investigate the possibility of applying the most recent editions of the normative documents indicated below. For
`undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC
`maintain registers of currently valid International Standards.
`
`ISO/IEC 7816-3, Information technology – Identification cards – Integrated circuit(s) cards with contacts – Part 3:
`Electronic signals and transmission protocols.
`
`ISO/IEC 7816-4, Information technology – Identification cards – Integrated circuit(s) cards with contacts – Part 4:
`Interindustry commands for interchange.
`
`ISO/IEC 7816-5, Identification cards – Integrated circuit(s) cards with contacts – Part 5: Numbering system and
`registration procedure for application identifiers.
`
`ISO/IEC 14443-2, Identification cards – Contactless integrated circuit(s) cards – Proximity cards – Part 2: Radio
`frequency power and signal interface.
`
`ISO/IEC 14443-3, Identification cards – Contactless integrated circuit(s) cards – Proximity cards – Part 3:
`Initialization and anticollision.
`
`3 Terms and definitions
`
`For the purposes of this part of ISO/IEC 14443, the following terms and definitions apply.
`
`3.1
`bit duration
`one elementary time unit (etu), calculated by the following formula:
`
`1 etu = 128 / (D x fc)
`
`The initial value of the divisor D is 1, giving the initial etu as follows:
`
`1 etu = 128 / fc
`
`Where fc is the carrier frequency as defined in ISO/IEC 14443-2.
`
`© ISO/IEC 2001 – All rights reserved
`
`1
`
`Apple Ex. 1031, p. 9
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`3.2
`block
`special type of frame, which contains a valid protocol data format
`
`NOTE
`
`A valid protocol data format includes I-blocks, R-blocks or S-blocks.
`
`3.3
`invalid block
`type of frame, which contains an invalid protocol format
`
`NOTE
`
`A time-out, when no frame has been received, is not interpreted as an invalid block.
`
`3.4
`frame
`sequence of bits as defined in ISO/IEC 14443-3
`
`NOTE
`
`The PICC Type A uses the standard frame defined for Type A and the PICC Type B uses the frame defined for
`Type B.
`
`4 Symbols and abbreviated terms
`
`ACK
`
`ATS
`
`ATQA
`
`ATQB
`
`CID
`
`CRC
`
`D
`
`DR
`
`DRI
`
`DS
`
`DSI
`
`EDC
`
`etu
`
`fc
`
`FSC
`
`FSCI
`
`FSD
`
`FSDI
`
`FWI
`
`2
`
`positive ACKnowledgement
`
`Answer To Select
`
`Answer To reQuest, Type A
`
`Answer To reQuest, Type B
`
`Card IDentifier
`
`Cyclic Redundancy Check, as defined for each PICC Type in ISO/IEC 14443-3
`
`Divisor
`
`Divisor Receive (PCD to PICC)
`
`Divisor Receive Integer (PCD to PICC)
`
`Divisor Send (PICC to PCD)
`
`Divisor Send Integer (PICC to PCD)
`
`Error Detection Code
`
`elementary time unit
`
`carrier frequency
`
`Frame Size for proximity Card
`
`Frame Size for proximity Card Integer
`
`Frame Size for proximity coupling Device
`
`Frame Size for proximity coupling Device Integer
`
`Frame Waiting time Integer
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 10
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`FWT
`
`Frame Waiting Time
`
`FWTTEMP
`
`temporary Frame Waiting Time
`
`HLTA
`
`I-block
`
`INF
`
`MAX
`
`MIN
`
`NAD
`
`NAK
`
`OSI
`
`PCB
`
`PCD
`
`PICC
`
`PPS
`
`PPSS
`
`PPS0
`
`PPS1
`
`R-block
`
`R(ACK)
`
`R(NAK)
`
`RATS
`
`REQA
`
`RFU
`
`HALT Command, Type A
`
`Information block
`
`INformation Field
`
`Index to define a maximum value
`
`Index to define a minimum value
`
`Node ADdress
`
`Negative AcKnowledgement
`
`Open Systems Interconnection
`
`Protocol Control Byte
`
`Proximity Coupling Device
`
`Proximity Card
`
`Protocol and Parameter Selection
`
`Protocol and Parameter Selection Start
`
`Protocol and Parameter Selection parameter 0
`
`Protocol and Parameter Selection parameter 1
`
`Receive ready block
`
`R-block containing a positive acknowledge
`
`R-block containing a negative acknowledge
`
`Request for Answer To Select
`
`REQuest Command, Type A
`
`Reserved for Future Use
`
`S-block
`
`Supervisory block
`
`SAK
`
`SFGI
`
`SFGT
`
`WUPA
`
`WTX
`
`WTXM
`
`Select AcKnowledge
`
`Start-up Frame Guard time Integer
`
`Start-up Frame Guard Time
`
`Wake-Up Command, Type A
`
`Waiting Time eXtension
`
`Waiting Time eXtension Multiplier
`
`© ISO/IEC 2001 – All rights reserved
`
`ISO/IEC 14443-4:2001(E)
`
`3
`
`Apple Ex. 1031, p. 11
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5 Protocol activation of PICC Type A
`
`The following activation sequence shall be applied:
`
`œ PICC activation sequence as defined in ISO/IEC 14443-3 (request, anticollision loop and select).
`
`œ At the beginning the SAK byte shall be checked for availability of an ATS. The SAK is defined in
`ISO/IEC 14443-3.
`
`œ The PICC may be set to HALT state, using the HLTA Command as defined in ISO/IEC 14443-3, if no ATS is
`available.
`
`œ The RATS may be sent by the PCD as next command after receiving the SAK if an ATS is available.
`
`œ The PICC shall send its ATS as answer to the RATS. The PICC shall only answer to the RATS if the RATS is
`received directly after the selection.
`

`
`If the PICC supports any changeable parameters in the ATS, a PPS request may be used by the PCD as the
`next command after receiving the ATS to change parameters.
`
`œ The PICC shall send a PPS Response as answer to the PPS request.
`
`A PICC does not need to implement the PPS, if it does not support any changeable parameters in the ATS.
`
`The PCD activation sequence for a PICC Type A is shown in Figure 1.
`
`4
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 12
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`ISO/IEC14443-3
`
`Send WUPA
`
`Send HLTA
`
`Non
`ISO/IEC 14443-4
`protocol
`
`Receive DESELECT Response
`
`Send DESELECT Request
`
`Field On
`
`Send REQA
`
`Receive ATQA
`
`Anticollision
`loop
`
`ATS
`available?
`
`no
`
`yes
`
`Use
`ISO/IEC 14443-4
`protocol?
`
`no
`
`yes
`
`Send RATS
`
`Receive ATS
`
`PPS
`supported?
`
`yes
`
`5
`
`Apple Ex. 1031, p. 13
` Apple v. Fintiv
` IPR2020-00019
`
`ISO/IEC14443-4
`
`no
`
`Parameter
`change?
`
`yes
`
`no
`
`Send PPS Request
`
`Receive PPS Response
`
`Exchange
`Transparent
`Data
`
`© ISO/IEC 2001 – All rights reserved
`
`Figure 1 — Activation of a PICC Type A by a PCD
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5.1 Request for answer to select
`
`This clause defines the RATS with all its fields (see Figure 2).
`
`’E0’
`
`Start byte
`
`Parameter
`
`Parameter byte
`codes FSDI and CID
`. .
`..
`.
`
`CRC1
`
`CRC2
`
`Figure 2 — Request for answer to select
`The parameter byte consists of two parts (see Figure 3):
`
`œ The most significant half-byte b8 to b5 is called FSDI and codes FSD. The FSD defines the maximum size of a
`frame the PCD is able to receive. The coding of FSD is given in Table 1.
`
`œ The least significant half byte b4 to b1 is named CID and it defines the logical number of the addressed PICC
`in the range from 0 to 14. The value 15 is RFU. The CID is specified by the PCD and shall be unique for all
`PICCs, which are in the ACTIVE state at the same time. The CID is fixed for the time the PICC is active and
`the PICC shall use the CID as its logical identifier, which is contained in the first error-free RATS received.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`
`CID
`FSDI
`Figure 3 — Coding of RATS parameter byte
`
`‘1’
`
`24
`
`‘2’
`
`32
`
`Table 1 — FSDI to FSD conversion
`‘4’
`‘5’
`‘6’
`‘3’
`
`40
`
`48
`
`64
`
`96
`
`FSDI
`
`FSD
`(bytes)
`
`‘0’
`
`16
`
`‘7’
`
`128
`
`‘8’
`
`256
`
`‘9’-‘F’
`
`RFU
`>256
`
`5.2 Answer to select
`
`This clause defines the ATS with all its available fields (see Figure 4).
`
`In the case that one of the defined fields is not present in an ATS sent by a PICC the default values for that field
`shall apply.
`
`6
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 14
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5.2.1 Structure of the bytes
`
`Figure 4 — Structure of the ATS
`
`The length byte TL is followed by a variable number of optional subsequent bytes in the following order:
`

`
`format byte T0,
`

`
`interface bytes TA(1), TB(1), TC(1) and
`
`œ historical bytes T1 to Tk.
`
`5.2.2 Length byte
`
`The length byte TL is mandatory and specifies the length of the transmitted ATS including itself. The two CRC
`bytes are not included in TL. The maximum size of the ATS shall not exceed the indicated FSD. Therefore the
`maximum value of TL shall not exceed FSD-2.
`
`5.2.3 Format byte
`
`The format byte T0 is optional and is present as soon as the length is greater than 1. The ATS can only contain the
`following optional bytes when this format byte is present.
`
`T0 consists of three parts (see Figure 5):
`
`œ The most significant bit b8 shall be set to 0. The value 1 is RFU.
`
`œ The bits b7 to b5 contain Y(1) indicating the presence of subsequent interface bytes TC(1), TB(1) and TA(1).
`
`œ The least significant half byte b4 to b1 is called FSCI and codes FSC. The FSC defines the maximum size of a
`frame accepted by the PICC. The default value of FSCI is 2 and leads to a FSC of 32 bytes. The coding of
`FSC is equal to the coding of FSD (see Table 1).
`
`© ISO/IEC 2001 – All rights reserved
`
`7
`
`Apple Ex. 1031, p. 15
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`b8 b7 b6 b5 b4 b3 b2 b1
`0
`
`FSCI
`TA(1) is transmitted, if bit is set to 1
`TB(1) is transmitted, if bit is set to 1
`TC(1) is transmitted, if bit is set to 1
`shall be set to 0, 1 is RFU
`Figure 5 — Coding of format byte
`
`Y(1)
`
`5.2.4
`
`Interface byte TA(1)
`
`The interface byte TA(1) consists of four parts (see Figure 6):
`
`œ The most significant bit b8 codes the possibility to handle different divisors for each direction. When this bit is
`set to 1 the PICC is unable to handle different divisors for each direction.
`
`œ The bits b7 to b5 code the bit rate capability of the PICC for the direction from PICC to PCD, called DS. The
`default value shall be (000)b.
`
`œ The bit b4 shall be set to (0)b and the other value is RFU.
`
`œ The bits b3 to b1 code the bit rate capability of the PICC for the direction from PCD to PICC, called DR. The
`default value shall be (000)b.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`0
`
`DR=2 supported, if bit is set to 1
`DR=4 supported, if bit is set to 1
`DR=8 supported, if bit is set to 1
`shall be set to 0, 1 is RFU
`DS=2 supported, if bit is set to 1
`DS=4 supported, if bit is set to 1
`DS=8 supported, if bit is set to 1
`Only the same D for both directions
`supported, if bit is set to 1
`Different D for each direction
`supported, if bit is set to 0
`Figure 6 — Coding of interface byte TA(1)
`The selection of a specific divisor D for each direction may be done by the PCD using a PPS.
`
`5.2.5
`
`Interface byte TB(1)
`
`The interface byte TB(1) conveys information to define the frame waiting time and the start-up frame guard time.
`
`The interface byte TB(1) consists of two parts (see Figure 7):
`
`œ The most significant half-byte b8 to b5 is called FWI and codes FWT (see 7.2).
`
`8
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 16
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`œ The least significant half byte b4 to b1 is called SFGI and codes a multiplier value used to define the SFGT.
`The SFGT defines a specific guard time needed by the PICC before it is ready to receive the next frame after it
`has sent the ATS. SFGI is coded in the range from 0 to 14. The value of 15 is RFU. The value of 0 indicates no
`SFGT needed and the values in the range from 1 to 14 are used to calculate the SFGT with the formula given
`below. The default value of SFGI is 0.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`
`SFGI
`FWI
`Figure 7 — Coding of interface byte TB(1)
`SFGT is calculated by the following formula:
`
`SFGT = (256 x 16 / fc) x 2SFGI
`
`SFGTMIN = minimum value of the frame delay time as defined in ISO/IEC 14443-3
`
`SFGTDEFAULT = minimum value of the frame delay time as defined in ISO/IEC 14443-3
`
`SFGTMAX = ~4949 ms
`
`5.2.6
`
`Interface byte TC(1)
`
`The interface byte TC(1) specifies a parameter of the protocol.
`
`The specific interface byte TC(1) consists of two parts (see Figure 8):
`
`œ The most significant bits b8 to b3 shall be (000000)b and all other values are RFU.
`
`œ The bits b2 and b1 define which optional fields in the prologue field a PICC does support. The PCD is allowed
`to skip fields, which are supported by the PICC, but a field not supported by the PICC shall never be
`transmitted by the PCD. The default value shall be (10)b indicating CID supported and NAD not supported.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`0
`0
`0
`0
`0
`0
`
`NAD supported, if bit is set to 1
`CID supported, if bit is set to 1
`shall be set to (000000)b, all other values are RFU
`Figure 8 — Coding of interface byte TC(1)
`
`5.2.7 Historical bytes
`
`The historical bytes T1 to Tk are optional and designate general information. The maximum length of the ATS gives
`the maximum possible number of historical bytes. ISO/IEC 7816-4 specifies the content of the historical bytes.
`
`© ISO/IEC 2001 – All rights reserved
`
`9
`
`Apple Ex. 1031, p. 17
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5.3 Protocol and parameter selection request
`
`PPS request contains the start byte that is followed by two parameter bytes (see Figure 9).
`
`Start byte
`
`PPSS
`
`PPS0
`
`PPS1
`
`CRC1
`
`CRC2
`
`Parameter 0
`codes presence of PPS1
`Parameter 1
`codes DRI and DSI
`
`. .
`
`. .
`
`. .
`
`. .
`
`. .
`
`Figure 9 — Protocol and parameter selection request
`
`5.3.1 Start byte
`
`PPSS consists of two parts (see Figure 10):
`
`œ The most significant half byte b8 to b5 shall be set to ‘D’ and identifies the PPS.
`
`œ The least significant half byte b4 to b1 is named CID and it defines the logical number of the addressed PICC.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`1
`0
`1
`1
`
`CID
`shall be set to 1, 0 is RFU
`shall be set to 0, 1 is RFU
`shall be set to (11)b, all other values are RFU
`Figure 10 — Coding of PPSS
`
`10
`
`© ISO/IEC 2001 – All rights reserved
`
`Apple Ex. 1031, p. 18
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5.3.2 Parameter 0
`
`PPS0 indicates the presence of the optional byte PPS1 (see Figure 11).
`
`b8 b7 b6 b5 b4 b3 b2 b1
`0
`0
`0
`0
`0
`0
`1
`
`shall be set to 1, 0 is RFU
`shall be set to (000)b, all other values are RFU
`PPS1 is transmitted, if bit is set to 1
`shall be set to (000)b, all other values are RFU
`Figure 11 — Coding of PPS0
`
`5.3.3 Parameter 1
`
`PPS1 consists of three parts (see Figure 12):
`
`œ The most significant half byte b8 to b5 shall be (0000)b and all other values are RFU.
`
`œ The bits b4 and b3 are called DSI and code the selected divisor integer from PICC to PCD.
`
`œ The bits b2 and b1 are called DRI and code the selected divisor integer from PCD to PICC.
`
`b8 b7 b6 b5 b4 b3 b2 b1
`0
`0
`0
`0
`
`DRI
`DSI
`shall be set to (0000)b, all other values are RFU
`Figure 12 — Coding of PPS1
`For the definition of DS and DR, see 5.2.4.
`
`The coding of D is given in Table 2.
`
`Table 2 — DRI, DSI to D conversion
`DRI, DSI
`(00)b
`(01)b
`(10)b
`(11)b
`
`D
`
`1
`
`2
`
`4
`
`8
`
`© ISO/IEC 2001 – All rights reserved
`
`11
`
`Apple Ex. 1031, p. 19
` Apple v. Fintiv
` IPR2020-00019
`
`

`

`ISO/IEC 14443-4:2001(E)
`
`5.4 Protocol and parameter selection response
`
`The PPS response acknowledges the received PPS request (see Figure 13) and it contains only the start byte (see
`5.3.1).
`
`Start byte
`
`PPSS
`
`CRC1
`
`CRC2
`
`Figure 13 — Protocol and parameter selection response
`
`5.5 Activation frame waiting time
`
`The activation frame waiting time defines the maximum time for a PICC to start sending its response frame after
`the end of a frame received from the PCD and has a value of 65536/fc (~4833 µs).
`
`NOTE
`
`The minimum time between frames in any direction is defined in ISO/IEC 14443-3.
`
`5.6 Error detection and recovery
`
`5.6.1 Handling of RATS and ATS
`
`5.6.1.1
`
`PCD rules
`
`When the PCD has sent the RATS and receives a valid ATS the PCD shall continue operation.
`
`In any other case the PCD may retransmit the RATS before it shall use the deactivation sequence as defined in
`clause 8. In case of failure of this deactivation sequence it may use the HLTA Command as defined in ISO/IEC
`14443-3.
`
`5.6.1.2
`
`PICC rules
`
`When the PICC has been selected with the last command and
`
`a) receives a valid RATS, the PICC
`
`œ shall send back its ATS and
`
`œ shall disable the RATS (stop responding to received RATS).
`
`b)
`
`receives any other block valid or invalid, except a HLTA Command, the PICC
`
`œ shall ignore the block and
`
`œ shall remain in receive mode.
`
`12
`
`© ISO/IEC 2001 – All

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket