Annex B (informative): Mapping to RFID technologies ToC Previous

B.3 UHF ToC Previous

KillTag

For RFID Readers working on ISO/IEC 18000-63 UHF transponders, KillTag invokes a Kill procedure to the specified transponder according to [EPCGen2] to permanently disable the tag.

The transponder (tag) can only be disabled, if the kill password stored in bits 00h .. 1Fh in bank 00 of the tag’s memory is different from zero AND the KillPassword parameter given matches the tag’s stored value.

For Version 1.x of the EPC Global standard, both passwords (Kill and Access) are 32-bit values, represented as 4 bytes in a Byte String parameter (MSB first).

The mapping of the KillTag parameters is defined in Table B.8.

Table B.8 – KillTag UHF parameter mapping

Command Argument Description
Identifier The Identifier (i.e. the EPC code) of the tag to be disabled in a data type the RFID reader understands. Usually the reader will accept at least the same type that the reader provides in his own ScanResult and the UID as a Byte String, but may also accept other data types.
If a ScanDataEPC structure according to 9.3.6 is used, only the UId field needs to contain valid data.
CodeType A string defining the type of Identifier used in “Identifier” argument, see 9.1.3, for example “EPC” or “UID”
KillPassword The kill password of the tag (4 bytes)
Status Return value indicating the success of the kill procedure.

LockTag

For RFID Readers working on ISO/IEC 18000-63 UHF transponders, LockTag can set the lock status of a memory region.

Lockable memory regions are:

- the kill password

- the access password

- the (complete) EPC memory bank

- the (complete) TID memory bank

- the (complete) User memory bank

The kill and the access password can be set to one of the states defined in Table B.9 (see 9.2.4).

Table B.9 – LockStateTag UHF mapping

State Meaning
Lock_0 Read and write   operations to the password area are only possible with the correct access password of the tag.
Unlock_1 Read and write   operations to the password area are allowed without knowing the access password of the tag.
PermanentLock_2 Read and write   operations to the password area are not allowed under any circumstances.
It is not possible to unlock the password area again (except by re-commissioning the tag).
PermanentUnlock_3 Read and write   operations to the password area are allowed without knowing the access password of the tag.
It is not possible to lock the password area again (except by re-commissioning the tag).

The EPC, TID and User memory banks can be set to one of these states defined in Table B.10 (see 9.2.4).

Table B.10 – Special LockState UHF mapping

State Meaning
Lock_0 Read   operations to the memory bank are allowed without knowing the access password of the tag.
Write   operations to the memory bank area are only possible with the correct access password of the tag.
Unlock_1 Read and write   operations to the memory bank are allowed without knowing the access password of the tag.
PermanentLock_2 Read   operations to the memory bank are allowed without knowing the access password of the tag.
Write   operations to the memory bank are not allowed under any circumstances.
It is not possible to unlock the memory bank again (except by re-commissioning the tag).
PermanentUnlock_3 Read and write   operations to the memory bank are allowed without knowing the access password of the tag.
It is not possible to lock the memory bank again (except by re-commissioning the tag).

Since it is not possible to lock or unlock specific memory addresses, Offset and Length parameters shall be set to zero for UHF devices.

The mapping of the LockTag parameters is defined in Table B.11.

Table B.11 – LockTag UHF parameter mapping

Command Argument Description
Identifier The Identifier (i.e. the EPC code) of the tag to be locked or unlocked in a data type the RFID reader understands. Usually the reader will accept at least the same type that the reader provides in his own ScanResult and the UID as a Byte String but may also accept other data types.
If a ScanDataEPC structure according to 9.3.6 is used, only the UId field needs to contain valid data.
CodeType A string defining the type of Identifier used in “Identifier” argument, see 9.1.3, for example “EPC” or “UID”
Password (optional) The access password of the tag, if unequal from zero (4 bytes, MSB first).
Region Bank of the memory area to be accessed
The RfidLockRegionEnumeration DataType is defined in 9.2.5.
Lock Specifies the lock action like write/read protection, permanently.
The RfidLockOperationEnumeration DataType is defined in 9.2.4.
Offset 0 for UHF tags
Length 0 for UHF tags
Status Returns the result of the LOCK operation

SetTagPassword

For RFID Readers working on ISO/IEC 18000-63 UHF transponders, the SetTagPassword method can set either the access password or the kill password of a UHF transponder.

Only the values defined in Table B.12 are allowed from the RfidPasswordTypeEnumeration DataType as defined in 9.2.6.

Table B.12 – Password type UHF mapping

Allowed Value Description
Access_0 Access password
Kill_1 Kill password

Other values are currently not defined for UHF readers.

For Version 1.x of the EPC Global standard, both passwords (Kill and Access) are 32-bit values, represented as 4 bytes in a Byte String parameter (MSB first).

Passwords can only be altered when they are not locked (see LockTag command).

The mapping of the SetPassword parameters is defined in Table B.13.

Table B.13 – SetPassword UHF parameter mapping

Command Argument Description
Identifier The Identifier (i.e. the EPC code) of the tag whose password is to be set in a data type the RFID reader understands. Usually the reader will accept at least the same type that the reader provides in his own ScanResult and the UID as a Byte String, but may also accept other data types.
If a ScanDataEPC structure according to 9.3.6 is used, only the UId field needs to contain valid data.
CodeType A string defining the type of Identifier used in “Identifier” argument, see 9.1.3, for example “EPC” or “UID”
PasswordType Either Access_0 or Kill_1, the type of password to be changed
AccessPassword (optional) The current access password of the tag, if unequal from zero (4 bytes, MSB first).
NewPassword The new access or kill password of the tag, if unequal from zero (4 bytes, MSB first).
Status Returns the result of the SetTagPassword method.

ReadTag

For RFID Readers working on ISO/IEC 18000-63 UHF transponders, the ReadTag method can read the raw data of any memory bank of a single UHF transponder.

The address range to be read can be the complete bank or a continuous part of the bank. All addresses from Offset to Offset+Length-1 must be inside the bank’s memory area.

The Region parameter denominates the bank from which data is to be read. The values are defined in Table B.14.

Table B.14 – Region ReadTag UHF mapping

Region Meaning
0 Reserved bank (Kill and Access passwords), usually 8 byte size
1 EPC bank, bank size is tag dependant
2 TID bank, bank size is tag dependant
3 USER data bank, bank size is tag dependant

Other values are currently not defined for UHF readers.

An access password may be required to read from bank 0. See description of LockTag method.

The mapping of the ReadTag parameters is defined in Table B.15.

Table B.15 – ReadTag UHF parameter mapping

Command Argument Description
Identifier The Identifier (i.e. the EPC code) of the tag whose password is to be set in a data type the RFID reader understands. Usually the reader will accept at least the same type that the reader provides in his own ScanResult and the UID as a Byte String, but may also accept other data types.
If a ScanDataEPC structure according to 9.3.6 is used, only the UId field needs to contain valid data.
CodeType A string defining the type of Identifier used in “Identifier” argument, see 9.1.3, for example “EPC” or “UID”
Region The memory bank to be read 0, 1, 2 or 3.
Offset Start address inside the memory bank [0-based byte counting]
Length Number of bytes to be read.
Password (optional) The current access password of the tag, if unequal from zero (4 bytes, MSB first).
ResultData Returns the requested tag data
Status Returns the status of the read operation.

WriteTag

For RFID Readers working on ISO/IEC 18000-63 UHF transponders, the WriteTag method can alter the raw data of any memory bank of a single UHF transponder.

The Region parameter denominates the bank to which data is to be written. The values are defined in Table B.16.

Table B.16 – Region WriteTag UHF mapping

Region Meaning
0 Reserved bank (Kill and Access passwords), usually 8 byte size
1 EPC bank, bank size is tag dependant
2 TID bank, bank size is tag dependant
3 USER data bank, bank size is tag dependant

Other values are currently not defined for UHF readers.

Memory banks may be write protected completely or an access password may be required to write, see LockTag method for details.

The length of the data is defined by the data itself.

The address range to be written can be the complete bank or a continuous part of the bank. All addresses from Offset to Offset+(length of data)-1 must be inside the bank’s memory area.

The mapping of the WriteTag parameters is defined in Table B.17.

Table B.17 – WriteTag UHF parameter mapping

Command Argument Description
Identifier The Identifier (i.e. the EPC code) of the tag whose password is to be set in a data type the RFID reader understands. Usually the reader will accept at least the same type that the reader provides in his own ScanResult and the UID as a Byte String, but may also accept other data types.
If a ScanDataEPC structure according to 9.3.6 is used, only the UId field needs to contain valid data.
CodeType A string defining the type of Identifier used in “Identifier” argument, see 9.1.3, for example “EPC” or “UID”
Region The memory bank to be written 0, 1, 2 or 3.
Offset Start address inside the memory bank [0-based byte counting]
Data Data to be written
Password (optional) The current access password of the tag, if unequal from zero (4 bytes, MSB first).
Status Returns the status of the read operation.

Previous