### BEFORE THE

DEPARTMENT OF TRANSPORTATION

WASHINGTON, D.C.

Notice of IATA Traffic Conference Actions Tentatively Exempted From Filing for Approval Docket OST

- 2012

- 0058

NOTICE OF TIER 1 AGREEMENTS FILING

BY THE

INTERNATIONAL AIR TRANSPORT ASSOC IATION

1 November 201 3

Communications with respect to this

Document should be sent to

Douglas Lavin Regional Vice President

– North America International Air Transport Association
1201 F Street, NW, Suite 650 Washington, DC 20004
(202) 62 8

- 9292

### Summary DOCKET: DOT

- OST

- 2012

- 0058 DOT ORDER: None Requested

Date: 1 Nov 201 3

Filing fee/IATA Acct: Waived by Order 2012

- 4

- 18, Appendix
A, Section D

US/UST involved Yes

Intended effective date: 1 J anuary 201 4

Meeting site, date: CSC Noti ce of Amendment dated 12 August 2013

Agreement(s)/Minutes CSC/Notif/007/2013 dated 12 August 2013

, CSC/FAR/002/2013 dated 1 November 2013

### NOTICE OF TIER 1 AGREEMENTS FILING

Pursuant to statements submitted by Member airlines of the International A ir Transport

Association (IATA), the undersigned has been constituted to be their attorney

- in

- fact for filing

with the Department of Transportation copies of agreements adopted by the IATA Traffic

Conferences.

On their behalf, and pursuant to the procedure s specified in Order 2012

- 4

- 18 (13 April

2012), I am filing with the Department, in Docket OST

- 2012

- 0058, this Notice, the subject

agreements and supporting documentation. These agreements are Tier 1 agreements tentatively

exempted by Order 2012

- 4

- 18 from Condition #2 to the Department’s approval of the Provisions

for the Conduct of the IATA Traffic Conferences, which condition requires pre

- implementation

Department review. The intended effective date of the agreements i s 1 January 201 4

.

The subject agreeme nts amend or establish Resolutions and/or Recommended Practices

that do not address subject areas which the Department has indicated it still chooses to review

under Condition #2. The text of the agreements and other conference documentation sent to

airli ne Members of IATA accompany this Notice. The cover pages of the documentation clearly

identify each affected Resolution and /or Recommended Practice and show whether the subject

agreements are amendments or new agreements. Other pages provide the text o f each subject

agreement. Where an affected Resolution or Recommended Practice has previously been

exempted from Condition #2 by Department action, the cover pages include the appropriate

docket and order number. The cover pages include a summary to expla in the nature and purpose

of the subject amendments and/or agreements.

### - 2

-

13 461343.1 

### Respectfully submitted,

/s/ Douglas Lavin Douglas Lavin

Regional Vice President

– North America International Air Transport Association Attorney

- In

- Fact

### - 3

-

13 461343.1 

### CERTIFICATE OF SE RVICE

A copy of this notice has been served this day by first class or priority mail on the following person:

Chief, Transportation, Energy & Agriculture Section

Antitrust Division Department of Justice Washington, D.C. 20530

A copy of this notice has been sent this day by email to John Kiser (John.Kiser@dot.gov) and to Della Davis (Della.Davis@dot.gov) of the Department of Transportation.

/s/ Douglas Lavin Douglas Lavin

1 Nov 201 3

Date Served

## INTERNATIONAL AIR TRANSPORT A SSOCIATION



# FINALLY ADOPTED RESOLUTION

CARGO SERVICES CONFERENCE (CSC)

### M E M O R AN D U M

CSC/FAR/00 2 /201 3

TO: All Members of IATA

Cargo Services Conference Accredited Representatives

CC: Members, Cargo Procedures Conferences Management G roup

Members, IATA/FIATA Consultative Council

IATA Regional Cargo Managers IATA Strategic Partners

FROM: Secretary, Cargo Services Conference

DATE: 1 November 201 3

SUBJECT: FINALLY ADOPTED RESOLUTION

– RECOMMENDED PRACTICE 16 40

Please find attached the amendment to Recommended Practice 16 40 (RP16 40 ) agreed by the Cargo Business Processes Panel (CBPP) and adopted through CSC Notice of Amendment ( CSC/Notif/007/2013 ) for normal effectiveness.

The filing period runs from 1 November 201 3 to 30 December 201 3 , with an intended effective

date of 1 January 201 4 . The final effectiveness date will be communicated to Members by a Declaration of Effectiveness Memorandum as soon as all required government approvals have

been obtained.

Members are requested to file the revised RP16 40 with their g overnment authorities where required, and to advise IATA Secretariat of their g overnments’ action latest by 30

December 201 3 , the end of the filing period. As usual, filing formalities with the U.S. Department of Transpo rtation and the Canadian Transportation Agency will be handled by IATA.

Please note that the revised RP16 40 will be declared effective upon receipt of the

necessary g overnment approvals, in accordance with Resolutions 001 and 006.

Andrea Gruber

Secretar y, Cargo Services Conference

Attachment Finally Adopted Resolution

– CSC Mail Vote (S07 5)

– RP16 81

FINALLY ADOPTED RESOLUTION SUMMARY

The following amendment to RP1640 is requested for approval. The intended effective date is 1 January 2014

.

Resolution Summary of Amendment

RECOMMENDED PRACTICE 1640

USE OF RADIO FREQUENCY

TECHNOLOGY FOR THE AUTOMATIC

IDENTIFICATION OF UNIT LOAD DEVICES

(Amending) Amendment to reflect the latest technologies and international standards whilst ensuring close alignment with the Passenger Services Conference

Recommended Pra ctice 1740c ( Radi o Frequency Identification Specifications For Interline Baggage ).

Background of Amendment to RP1640 :

Introduced in 1991

, the most recent amendment to Recommended Practice 1640 was made in 1996, and it has not been updated since

. Owing to the recent fast growing industry application of RFID technologies and international standards, the current Recommended Practice 1640 was found to be no longer valid or applicable.

I n March 2011, the Cargo Services Conference endorsed the creation of the Cargo RFID Working Group under the CBPP with the first objective to review the provisions of

R ecommended P ractice 1640 and propose necessary amendments to Conference for adoption. A ccordingly, the Working Group comprising of experts from Airlines, RFID

ma nufacturers, Aircraft manufacturers, ULD Service Providers, Freight Forwarders, Ground Handlers, and ULD manufacturers, did an extensive review of Recommended Practice 1640 over the past two years via web conferencing. The Working Group finally cam e up wit h a recommendation to completely revamp R ecommended P ractice 1640 to reflect the latest technologies and international standards whilst ensuring close alignment with the Passenger Services Conference Recommended Practice 1740c ( Radi o Frequency Identificati on Specifications For Interline Baggage ). The proposed revamped R ecommended P ractice 1640 was subsequently presented and endorsed by the CBPP and adopted through the CSC Notice

of Amendmen t

.Finally Adopted Resolution

– RP16 40



### Page 1 of 11 Note: As the text of Recommended Practice 1640 has been complet ely redrafted, the amendments are not shown in track changes

.

RECOMMENDED PRACTICE 1640
USE OF RADIO FREQUENCY TECHNOLOGY FOR THE AUTOMATIC IDENTIFICATION OF

UNIT LOAD DEVICES

CBPP(67)1640

RECOMMENDED that:

The following specifications be followed as the community develops radio frequency identification (RFID) technology for the automatic identification of unit load devices (ULD), utilizing the IATA ULD Identification Code as defined in Resolution 686. The community shall ensure the compatibility of this technology and the ability of RFID to be used in the ULD operations and management environment, including interoperability with any other business using the same ULDs as shared assets.

1. INTRODUCTION In this Recommended Practice ULD terminology is in accordance with the provisions of Resolution 680, General Rules for the use of Unit Load Devices.

ULD identification codes are in accordance with the provisions of Resolutions 686, IATA

Identification Code for Unit Load Devices.

This Recommended Pra ctice describes the requirements for a system of identification of aircraft ULDs. The RFID system shall consist of two basic elements:

- The RFID device or transponder (also called tag)

- The RFID readers/writers. This RFID system supplements visual markings

.

2. CONSIDERATIONS

2.1 This Recommended Practice provides for the automatic identification of ULDs by use of a radio frequency identification (RFID) tag and reader/writer operating in the UHF spectrum, and

the transfer of the information contained in such a tag to data processing systems.

The standard embodied in this Recommended Practice is not restricted. The intent of this standard is to provide read/write compatibility between RFID tags of different ULD

manufacturers.

2.2 This Recommended Practi ce is made available to members for their use in selecting vendors and ensuring global compatibility within IATA by referencing the product as IATA Recommended Practice 1640 compliant.

2.3 This Recommended Practice considers that there is scope for substa ntial implementation savings and increased utility by configuring reading equipment in the UHF spectrum to be

available for use in both Recommended Practice 1640 and Recommended Practice 1740c

Modes.Finally Adopted Resolution

– RP16 40



### Page 2 of 11 2.4 The use of RFID equipment must comply with local go vernment regulations to assure that health and safety requirements are met.

2.5 The use of RFID equipment is a potential for:

 higher speed throughput at read/write locations;

 future elimination of manual information;

 elimination of paper handling and pro cessing costs;

 ensuring reliability and accuracy in data capturing;

 real

- time tracking/ locating of the ULDs within the local RFID system.

3. SCOPE AND APPLICATION The Scope and Application are:

3.1 An RFID system capable of continued enhancement to mee t changing requirements.

3.2 An RFID system must allow the transfer of information from a ULD to an automatic processing system by RF transmission and vice versa.

3.3 ULD RFID applications shall not interfere with other applications, e.g. passenger, carg o, mail, catering, etc. and vice versa.

4. DEFINITIONS

4.1 Community The community consists of airlines, independent handling companies, airports, freight forwarders, suppliers and other actors in the air cargo supply chain.

4.2 Encoding Capacity

Is th e amount of information (in bits) capable of being held within an RFID tag. The encoding rules determine how user data relates to the actual bit string within the RFID tag (see chapter

10

— encoding the data on the RFID tag)

4.3 Mandatory Information

Refe rs to absolutely required minimum information that must be stored in the RFID tag and

must be read on demand.

4.4 Optional Information Refers to information that can be optionally stored in the RFID tag but is not mandatory. This

data is included at the d iscretion of the user.

4.5 RFID Tag An electronic device consisting of an integrated circuit and antenna which, when embedded in a mould, is capable of receiving, holding and transmitting information related to the ULD. Tag

can be read and written to mult iple times.

4.6 Reader/Writer An electronic device for performing the process of retrieving data from and potentially transmitting data to an RFID tag and, as appropriate, the contention and error control management, and channel and source decoding requir ed to recover and communicate theFinally Adopted Resolution

– RP16 40



### Page 3 of 11 data entered at source. The device may also interface with an integral display and/or industrial

controller.

4.7 Memory Structure The RFID tag comprises of 4 memory banks, as shown in Table 1 (below). (see paragraph

10.5

– ISO/IEC 18000

- 63 Memory Banks).

Table 1: ISO/IEC 18000

- 63 memory structure

Name 1 Abbreviati

on Purpose

Memory Bank

00 2 MB00 Reserved (access and/or kill passwords)

Memory Bank

01 2 MB01 UII (unique identification of the object to which the RF tag

is af fixed and an indicator as to whether MB11 contains any data) Memory Bank

10 2 MB10 TID (unique identification of the RF tag according to ISO/IEC 15963) Memory Bank

11 2 MB11 User (user

- specific data storage)

4.8 System Accuracy The capability of avoidin g errors in the read, write and storage process.

4.9 System Reliability

4.9.1 Read The ability of an RFID system to capture information from an RFID tag properly programmed and presented which enters the readers specified coverage area.

4.9.2 Write

The ability of an RFID system to write information to an RFID tag in the specified coverage

area.

4.10 Open Application An open application is an RFID system that is implemented for the use of several actors such as airlines or other members of the community at one or multiple locations such as airports or

cargo areas. 4.11 Abbreviations

AFI Application Family Identifier

IEC International Electrotechnical Commission

ISO International Organization for Standardization

MHz Megahertz

OID Object Identifier

RF Radi o Frequency

RFID Radio Frequency Identification

TID Tag Identifier

UHF Ultra High Frequency

UII Unique Item Identifier

ULD Unit Load Device

1 The subscript following the memory bank number indicates that the value presented is in binary.Finally Adopted Resolution

– RP16 40



### Page 4 of 11 5. SYSTEM REQUIREMENTS The RFID System must meet the following requirements:

5.1 The air interface protocol shall be in accordance with ISO/IEC 18000

- 63 (Type C). The data is encoded in memory bank 01 and 11 according to this Recommended Practice.

5.2 Conformance testing of the system shall be in accordance with ISO/IEC 18047

- 6 (for 860 to 960 MHz).

5.3 Be capable of transferring the information to and from automated systems, using airline accepted industry protocols and data elements.

5.4 Provide readers/writers adaptable to fixed, mobile or portable applications.

5.5 The components of the system shall be config ured to achieve the highest measured reliability, taking into account the physical constraints of the various actors and radio regulations. Performance shall be measured in accordance with ISO/IEC 18046.

5.6 In a controlled test environment the read/writ e rate of the chip and antenna should be

99.7% or better.

5.7 In operational conditions the read rate of the system should be 99.5% or better.

5.8 Fulfil local environmental regulations related to RFID tag disposal.

5.9 No interference with other electr onic equipment. Not affected by other electrical equipment and/or radio emissions which can occur on the system operating frequencies normally found in the airline industry. When equipment is in the vicinity of operating aircraft, electronic hardware

needs to be RTCA DO

- 160 compliant.

5.10 When installed or operated in a particular country, the system must comply with all international, national and local governmental health, safety, aeronautical and radio regulations, and any other governmental rules and regulations which may apply, including those regarding human exposure levels and medical implants.

6. THE RFID TAG REQUIREMENTS, CHARACTERSITICS AND SPECIFICATIONS The RFID tag must meet the following requirements:

6.1 As a minimum, being capable of bei ng programmed in accordance with the composition of the IATA Identification Code for ULDs stipulated in Resolution 686 as physically marked on the

ULD.

6.2 The information on the RFID tag must not conflict with human readable formats.

6.3 Be capable of meeting requirements in accordance with SAE AS5678.

6.4 Be capable of retaining programmed data and responding to an RFID reader.

6.5 Be read or written to without any unauthorized modification.Finally Adopted Resolution

– RP16 40



### Page 5 of 11 6.6 RFID tags for the purpose of automatic identification of ULDs must be based on passive technology.

6.7 Have a minimum life of 5 (five) years for passive tags.

6.8 Environmental

6.8.1 The RFID tag shall function properly in all of the environmental conditions encountered in the air transport operational env ironment.

6.8.2 An RFID tag must be capable of operating in temperature ranges of

- 40°C (

- 40°F) to +70°C (+158°F) and must maintain the integrity of stored data at temperatures from

- 51°C (

- 60°F) to +85°C (+185°F), with both storage and operating humidit y ranges of up to 99%, be water and chemical (glycol or other de

- icing fluids) resistant, as well as to changes in atmospheric pressure. Certain site specific conditions may require higher or lower operating temperature ranges and environmental characteris tics.

6.8.2.1 Low temperature An RFID tag must fully operate at a minimum low temperature of

- 40°C (

- 40°F). An RFID tag must fully operate at such minimum temperatures after having been stored at a minimum low temperature of

- 51°C (

- 60°F) with an exposure time of 24 hours per day for a period of up to 60 days. Testing will be accomplished in accordance with IEC 60068

- 2

- 1 (MIL

- STD

- 810G, Method 502.5).

6.8.2.2 High temperature An RFID tag must fully operate after having been cycled between +70°C (+158°F) an d +38°C (+100°F). An RFID tag must fully operate at such temperature extremes after having been stored at a minimum high temperature of +85°C (+185°F) with an exposure time of 12 to 15 hours per day for a period of up to 60 days. Testing will be accomplish ed in accordance with

IEC 60068

- 2

- 2 (MIL

- STD

- 810G, Method 501.5).

6.8.3 Mechanical Shock: IEC Series 60068

- 2

- 27 (MIL STD 810G Method 516.6 Procedure I); 30g for 11 milliseconds, half sine pulse.

6.8.4 Random Vibration: IEC Series 60068

- 2

- 53 (MIL STD 810G Method 514.6, Category 5, Procedure III).

6.9 Electromagnetic Compatibility and Nuclear Radiation Environment The RFID shall function and maintain the integrity of its stored data.

6.9.1 In the electro

- magnetic environment of air traffic; e.g. as an exa mple in a maximum peak field strength of 200 V/m peak exposure level test for 1300 MHz and 2800 MHz to simulate airport radar exposures.

6.9.2 In security check environments as an example having received a maximum x

- ray exposure of 25 mR or an absorbed do se of 250 uG.

6.9.3 After being exposed to cosmic radiation during flights, for example having received a maximum exposure to thermal neutron bombardment from an 80 mC Am

- 241/Be source or its equivalent.

7. READER/WRITER REQUIREMENTS, CHARACTERISTICS AN D SPECIFICATIONS The reader/writer must meet the following requirements:Finally Adopted Resolution

– RP16 40



### Page 6 of 11 7.1 Should be one of the following configurations, based on the application requirements: fixed, mobile, or hand

- held devices.

7.2 Be capable of reading from and writing to the RFID tag.

7.3 Be capable of transferring the information to/from automatic data processing systems, using air transport industry accepted protocols and data elements.

7.4 Be capable of being integrated into a portable data terminal which may contain RFI D

communications modules.

7.5 All RFID readers must be capable of safe operation in and around stationary aircraft, in proximity to moving aircraft and in other airport areas.

7.6 Should be capable of reprogramming an RFID tag when required.

7.7 Perform ance Specifications The RFID Reader must meet the following requirements:

7.7.1 Be able to read a tag as it passes through a specified unobstructed reading range of up to 3 m (10 ft) at the passing speed up to 15 km/h (9 mph), so that the system can diffe rentiate tags based on operational constraints including the following examples:

 In the case of reading ULD on moving dolly, at a distance of 3 m at 15 km/h passing speed with rate of reading at 99.5%

 In the case of reading ULD on moving conveyer, at a dis tance of 80 cm at 18 m/min (60 ft/min) with rate of reading at 99.5%

 In the case of reading ULD in a stationary position with a mobile handheld device, at a distance of 50 cm with rate of reading at 99.5%

7.7.2 Be capable of reading RFID tags passing the reader at conventional speeds up to 15 km/h (9 mph).

7.7.3 RFID readers located on parallel axis must not interfere with each other.

7.7.4 RFID readers located on one axis must not read RFID tags from an adjacent axis.

7.8 Environmental

7.8.1 All fixed, mobile and portable ULD RFID readers compliant with this Recommended C (

- 4°F) to +50 C (+122°F), humidity ranges of up to 99%, be water and chemical (glycol or other de

- icing fluids)

resis tant, as well as to changes in atmospheric pressure. Certain site specific conditions may require higher or lower operating temperature ranges and environmental characteristics. Portable equipment, which is utilized in outdoor applications, must be rated N EMA 4 or equivalent.

7.8.2 Portable RFID readers shall function correctly after a drop shock test IEC Series 60068

- 2

- 27 (Mil Std 810G Method 516.6, Procedure I); Height 122 cm (48 in) to concrete.

8 TAG POSITIONNING Depending on the process, two to four ULD RFID tags should be attached to the sides of ULD to facilitate interoperability and interlining.Finally Adopted Resolution

– RP16 40



### Page 7 of 11 It is a minimum requirement that the attaching of ULD RFID tag shall not have any effect on the certification, operation and airworthiness of the ULD. Th e attaching of ULD RFID tag should be done only after obtaining written approval for both position and method of

attachment from the ULD manufacturer.

No part of the ULD RFID tag or its enclosure should extend beyond the base dimensions and

maximum allowa ble ULD contour (see IATA ULD Regulations) or any other operationally critical dimensions. The ULD RFID tag should not be located in a position where it is vulnerable to damage during operations.

8.1 Pallets: It is recommended that the ULD RFID tag attach ing to pallet be located inside the seat track of the edge rail without preventing the attachment of cargo nets or straps in locations specified in the certification requirements available from the ULD manufacturer or the

airlines.

8.2 Containers: It is r ecommended that the ULD RFID tag attaching to container be placed at least 51 cm (20 in) above the base of the container.

9. OPEN ARCHITECTURE

9.1 In order to meet international standards required for interline operations, RFID

readers/writers shall be based on open architecture RFID standards, such that any manufacturer’s RFID ULD tags are read and/ or programmed by any other manufacturer’s reader/writer; and that any one manufacturer’s reading/writing equipment may read or write to any other manufactur er’s RFID ULD tags.

9.2 In compliance with the ISO Patent Policy, if the protocols and/or technologies contained in the relevant standards are not in the public domain, the proprietor shall license them throughout the world on reasonable and non

- discrimin atory terms and conditions.

10. ENCODING THE DATA ON THE RFID TAG

10.1 Introduction The encoding for this Recommended Practice 1640 shall be according to ISO/IEC 15962 for

the ISO/IEC 18000

- 63 tag memory architecture.

10.2 Basic Encoding Rules

Data sh all be written to, and read from, the RFID tag using rules defined in ISO/IEC 15962. This allows airlines and airports complete flexibility in selecting from the present set of optional data elements, and for supporting new data elements should these be ad ded at a future date. This flexibility can be implemented even to differentiate between the requirements of different routes, and to support the handling of different types of ULDs.

The encoded byte stream on the RFID tag shall be encoded according to the rules of ISO/IEC 15962. These rules are implemented automatically through a system that has both ISO/IEC 15961 and 15962 as part of the complete data protocol. The adoption of this data protocol also allows for IATA to extend the system to RFID tags on UL Ds and other devices.Finally Adopted Resolution

– RP16 40



### Page 8 of 11 The No

- Directory encoding rules defined in ISO/IEC 15962 shall be used for encoding all the data elements. These support encoding and decoding of data respectively to and from the RFID tag.

10.3 ISO/IEC 15961 Related Features

10.3. 1 Object Identifier (OID)

ISO/IEC 15961

- 2 requires that an OID structure is used to uniquely identify each type of data encoded on an RFID tag. An OID structure has been assigned to IATA with the common root: 1 0 15961 11. The final component of the OID is as defined in table 2 (below). For most object identifiers, only the final component will need to be encoded.

Table 2: Object Identifiers & Data Elements

Object

Identifier Object (Data

Element) Mandator

y Memory bank Decoded data characters

1 0 15961 11

5 ULD ID Code Y 01 15 Alpha Numeric

1 0 15961 11

30 ULD OEM Name N 11 5 Alpha Numeric (CAGE Code)

1 0 15961 11

31 ULD OEM Serial

Number N 11 1

- 15 Alpha Numeric

1 0 15961 11

32 ULD Part Number N 11 1

- 15 Alpha Numeric

1 0 15961 11

33 Date of Manufacture N 11 6 Numeric (YYYYMM)

Once the RFID tag is encoded, the memory on the RFID tag shall be locked.

10.3.1.1 Encoding Rules for the ULD ID Code Object ID 1 0 15961 11 5

This element is mandatory

. This element can only be defined by the ULD owner. The sys tem should be able to read the ULD ID Code as per the composition stated in CSC Resolution 686 with the system capacity of 15 characters.

Note: The standard IATA ULD ID Code as stated in CSC Resolution 686 consists of nine (9) or ten (10) characters.

10.3 .1.2 Encoding Rules for the ULD OEM Name Object ID 1 0 15961 11 30

This element is optional. This element can only be defined by the ULD OEM.

It is recommended that the code of the ULD OEM Name be based on the Commercial and Government Entity (CAGE) Code ( US) or NATO Commercial and Governmental Entity (NCAGE) Code (other countries), which comprises of 5 alpha numeric characters.

10.3.1.3 Encoding Rules for ULD Serial Number Object ID 1 0 15961 11 31

This element is optional. This element can only be define d by the ULD OEM. It comprises of maximum 15 alpha numeric characters.Finally Adopted Resolution

– RP16 40



### Page 9 of 11 10.3.1.4 Encoding Rules for ULD Part Number Object ID 1 0 15961 11 32

This element is optional. This element can only be defined by the ULD OEM. It comprises of maximum 15 alpha numer ic characters.

10.3.1.5 Encoding Rules for Date of Manufacture Object ID 1 0 15961 11 33

This element is optional. This element can only be defined by the ULD OEM. It comprises of 6 numeric characters in the format of YYYYMM. e.g.: 201302 for February 20 13.

10.3.2 AFI The AFI is a single byte code that is used to distinguish particular types of tag across the air interface, enabling the interrogator to ignore tags with different AFI values. The AFI assigned to IATA for ULD identification is 91 (hexadecim al).

10.3.3 Data Format The data format code is used to distinguish between the semantics of different types of data on RFID tags that are compliant with ISO systems.

Note: The data format is a mechanism that allows the OID to be significantly truncated so that, in the case of this Recommended Practice, the common elements of the OID structure do not have to be encoded on the RFID tag. They are only present in the communication to ensure interoperability with RFID equipment.

For IATA ULD automatic identi fication purposes, the data format is the decimal code 11. This particular code needs to be used in some of the commands to configure the tag so that data can be interpreted properly.

10.4 ISO/IEC 15962 Related Features Encoding in accordance with ISO/IEC 15962 ensures:

- That maximum use is made of the encoding capacity (memory on the RFID tag), by avoiding the structured “message”.

- Allows any authorised user to read the RFID tag and abstract any, or all, of the

encoded data without the need to understand t he sequence.

- Allows for different air cargo supply chain actors to adopt different data elements within

this Recommended Practice without reference to others.

- Allows this Recommended Practice to be updated with new data elements without any

concerns about backwards compatibility.

What follows is based on the use of ISO/IEC 18000

- 63 (Type C).

10.5 ISO/IEC 18000

- 63 Memory Banks

ISO/IEC 18000

- 63 (Type C) specifies an air interface protocol. The air interface standard does not specify the size of the memory, only the overall architecture. The RFID tag comprises of 4 memory banks, as defined in paragraph 4.7.

MB 00 Reserved Memory Although this is defined as “reserved”, it is actually used for encoding a kill password and/or an access password.Finally Adopted Resolution

– RP16 40



### Page 10 of 11 MB 01 Unique I tem Identifier It is recommended that MB 01 be of a minimum capacity of 128 bits.

MB 10 Tag Identification Memory This memory is pre

- encoded by the tag manufacturer, and is not directly related to the

functions of this Recommended Practice.

MB 11 User D efined Memory

For ISO

- related applications, this is used exactly as defined in ISO/IEC 15962 using the No

Directory encoding method. It is recommended that MB 11 be of a minimum capacity of 512 bits.

When purchasing RFID tags, air cargo supply chain actor s are advised to check the capacity of MB 01 and 11. It is then necessary to match the amount of data to be encoded to the memory bank (see paragraph 10.3.1).

11. SECURITY

11.1 Tags should be supplied without any data in MB 00, MB 01 and MB 11.

11.2 The system must be programmable only by the authorized user(s).

11.3 The system must be electronically secure and protected against unauthorized alteration. Once the RFID tag is encoded, the memory on the RFID tag shall be locked.

12. IMPLEMENTATION

The tran sition phase will be the time from the first live application of the RFID technology in ULD handling until a fairly large majority of airlines, independent ground handling companies and airports have adopted the RFID technology. During this phase, commonly used ULD handling systems will either use both barcode scanning and RFID identification, or barcode scanning only.

13. REFERENCES

IATA Documents referred to in this Recommended Practice are: IATA Passenger Services Conference Resolutions Manual

Recommen ded Practice 1740c

– Radio frequency identification (RFID) specifications for interline baggage IATA Cargo Services Conference Resolutions Manual

Resolution 680

- General Rules for the use of Unit Load Devices

Resolution 686

– IATA identification code for Unit Load Devices

IATA’s web

- site can be visited at: http://www.iata.org

.

DO

- 160G, Environmental Conditions and Test Procedures for Airborne Equipment, standard for environmental test of avionics hardware published by R adio Technical Commission for Aeronautics ( RTCA), Incorporated

. ISO Reference Documents:

ISO/IEC 15961

- 1 Information technology

— Radio frequency identification (RFID) for item management

— Data protocol: application interface

This standard:

 provides guidelines on how data shall be presented as objects

 defines the structure of object identifiers, based on ISO/IEC 9834

- 1Finally Adopted Resolution

– RP16 40



### Page 11 of 11  defines access and formatting features such as the A pplication Family Identifier, and

data format

 specifies commands and responses that support the transfer data between the application and the RF tag

ISO/IEC 15962 Information technology

— Radio frequency identification (RFID) for item
management

— Data prot ocol: data encoding rules and logical memory functions

This standard:

 defines the encoded structure of object identifiers

 specifies the data compaction rules that apply to the encoded data

 specifies a Precursor for encoding syntax features efficiently

 spec ifies formatting rules for the data, e.g. depending on whether a directory is used or

not

 defines how application commands, e.g. to lock data, are transferred to the Tag Driver

ISO/IEC 18000

- 63 Information technology

— Radio frequency identification for i tem management

— Part 63: Parameters for air interface communications at 860 MHz to 960

MHz This standard defines, for three types of RFID tag, of the following features (some of which are shared by one or more of the types):

 Anticollision algorithm that e nables one tag to be selected from many tags

 Modulation of the radio signal

 Bit encoding rules across the air interface

 Air interface commands and responses

 Some tag structuring features

ISO/IEC 18000

- 63 (Type C) is the only type relevant to this Recommend ed Practice.

ISO/IEC 18047

- 6 I nformation technology

— Radio frequency identification device

conformance test methods

— Part 6: Test methods for air interface communications at

860 to 960 MHz

ISO/IEC 18046

- 1 Information technology

— Radio frequency identifi cation device performance test methods

— Part 1: Test methods for system performance

ISO/IEC 18046

- 2 Information technology

— Radio frequency identification device performance test methods

— Part 2: Test methods for interrogator performance

ISO/IEC 18046

- 3 Information technology

— Radio frequency identification device performance test methods

— Part 3: Test methods for tag performanceInternational Air Transport Association

Route de l'Aéroport 33, PO Box 416

CH

- 1215 Geneva 15 Airport

Switzerland

www.iata.org 

### M E M O R AN D U M

CSC/Notif/0 1 3 /201 3

TO: All Members of IATA

Cargo Services Conference Accredited Representatives and Alternates

CC: Members

– Cargo Procedures Conferences Management Group (CPCMG)

Members

– IATA/FIATA Consultative Council (IFCC)

Members

– Cargo Business Process Panel ( CBPP )

Members

– IATA Strategic Partners, Cargo Services IATA Cargo Managers

FROM: Secretary, Cargo Services Conference

DATE: 11 October 201 3

SUBJECT: RESULT

- NOTICE OF AMENDMENT TO RECOMMENDED PRACTICE 1640

Further to the circulation of Memorandum CSC/Notif/007/201 3 , notifying Members on the proposed amendment to the CSC Recommended Practice 1640 “Use of Radio Frequency Technology for the Automatic Identification of Unit Load Devices” in accordance with

Resolution 601, we would like to inform Members that there are no protests and therefore t he amendment is hereby declared as adopted by Conference.

IATA Cargo Services

### MEMORANDUM

CSC/Notif/007/2013

TO: All Members of IATA Cargo Services Conference Accredited Representatives and Alternates

CC: Members – Cargo Procedures Conferences Management Group (CPCMG) Members – IATA/FIATA Consultative Council (IFCC) Members – Cargo Business Process Panel (CBPP) Members – ULD Panel (ULDP) Members – IATA Strategic Partners, e-Cargo Regional Cargo Managers IDFS Cargo Deputies

FROM: Secretary, Cargo Services Conference

DATE: 12 August 2013

SUBJECT: RECOMMENDED PRACTICE 1640 – USE OF RADIO FREQUENCY

TECHNOLOGY FOR THE AUTOMATIC IDENTIFICATION OF UNIT LOAD

DEVICES

In accordance with the Notice of Amendment procedure stipulated in Resolution 601, please find attached the proposed CSC Recommended Practice 1640 “Use of Radio Frequency Technology for the Automatic Identification of Unit Load Devices”, that has been agreed by the

CBPP.

Any IATA Member may, within 30 days after th e circulation of this Memorandum, protest these amendments by informing the Secretary of the Ca rgo Services Conference (CSC) with specific reasons for the protest.

If no protests are received by the close of business on 12 September 2013 , the proposed

amendments will become effective and implementable as of that date and will be reflected in

the 35 th edition of the Cargo Services Conference Resolutions Manual to be released in 2014.

Frederic Leger Head of Cargo Business Process & Standards, IATA

Tel: + 41 22 770 26 44

Fax: + 41 22 770 26 78

E-mail: legerf@iata.org



###  AttachmentBackgroun d

Introduced in 1991, the most recent amendment to Recommended Practice 1640 wa s made in 1996, and it has not been updated since. Owing to the recent fast growing industry a pplication of RFID technologies a nd international standa rds, the cur r ent Recommended Practice 1640 was found to be no long er valid or applicable.

At CSC/33 i n March 20 11, the Conf erence endorsed the creation of the Cargo RFI D Working Group unde r the CBPP with the first objective to revie w t he provisions of Recommended

Practice 164 0 and propose necessar y amend me nts to Conference for ad option.

Accordingly, the Working Group co mprising of experts fro m Airlines, RFID manu facturers,

Aircraft ma nufacturers, ULD Service Providers, Freight Forwarders, Ground Ha ndlers, and

ULD manufacturers, did an extensive review o f Recomme nded Practice 1640 over the past
two years vi a web conferencing. The Working Group finally came up with a recommendation to completely reva mp Recommen ded Practice 1640 to reflect the latest techn o logies and

international standards whilst en suring clo s e alignment with the Passenge r Services

Conference Recommended Practice 17 40 c (Radio Frequency Identification (RFID) Specificatio ns For Interline Baggage). The proposed revamped Recommended Pra c tice 164 0 was subsequently presented and endorsed by t he CBPP and now being presented to the CSC for adoption.

### 1 Note: As the text of Recommended Practice 1640 has been completely redrafted, the amendments are not shown in track changes

.



### RECOMMENDED PR ACTICE 1640

USE OF RADIO FREQUENCY TECH NOLOGY FOR THE AUTOMATIC

IDENTIFICATION OF UNIT LOAD DEVICES

CBPP(67)1640

RECOMMENDED that:

The following specifications be followed as the community dev elops radio frequency identificatio n (RFID) technology for the

automatic identification of unit load devices (ULD), utilizing the IATA ULD Identification Code as defined in Resolution 686. The community shall ensure the compatibilit y of this technology and the ability of RFID to be used in the ULD operations and management environment, including interoperability with any ot her business using the same ULDs as shared assets.

1. INTRODUCTION
In this Recommended Practice ULD terminology is in accordance with the provisions of Resolution 680, General Rules for

the use of Unit Load Devices.

ULD identification codes are in accordance with the provisions of Resolutions 686, IATA Identification Code for Unit Load

Devices.

This Recommended Practice describes the requirements for a syst em of identification of airc raft ULDs. The RFID system

shall consist of two basic elements:

- The RFID device or transponder (also called tag)

- The RFID readers/writers. This RFID system supplements visual markings.

2. CONSIDERATIONS

2.1 This Recommended Practice provides for the automatic identif ication of ULDs by use of a radio frequency identification (RFID) tag and reader/writer operating in the UHF spectrum, and the transfer of the information contained in such a tag to data processing systems.

The standard embodied in this Recommended Practice is not restrict ed. The intent of this sta ndard is to provide read/write compatibility between RFID tags of different ULD manufacturers.

2.2 This Recommended Practice is made available to members for their use in selecting vendors and ensuring global compatibility within IATA by referencing the product as IATA Recommended Practice 1640 compliant.

2.3 This Recommended Practice considers that there is scope fo r substantial implementation savings and increased utility by configuring reading equipment in the UHF spectrum to be available for use in both Recommended Practice 1640 and

Recommended Practice 1740c Modes.

2.4 The use of RFID equipment must comply with local gov ernment regulations to assure that health and safety requirements are met.

2.5 The use of RFID equipment is a potential for:

• higher speed throughput at read/write locations;

• future elimination of manual information;

• elimination of paper handling and processing costs;

• ensuring reliability and accuracy in data capturing;

• real-time tracking/ locating of the ULDs within the local RFID system.

3. SCOPE AND APPLICATION
The Scope and Application are:

3.1 An RFID system capable of continued enha ncement to meet changing requirements.

### 2 3.2 An RFID system must allow the transfer of information from a ULD to an automatic processing system by RF

transmission and vice versa.

3.3 ULD RFID applications shall not interfer e with other applications, e.g. passenger , cargo, mail, catering, etc. and vice

versa.

4. DEFINITIONS

4.1 Community
The community consists of airlines, independent handling companies , airports, freight forwarders, suppliers and other actors in the air cargo supply chain.

4.2 Encoding Capacity
Is the amount of information (in bits) capable of being held wi thin an RFID tag. The encoding rules determine how user data relates to the actual bit string wi thin the RFID tag (see chapter 10 — encoding the data on the RFID tag)

4.3 Mandatory Information
Refers to absolutely required minimum information that must be stored in the RFID tag and must be read on demand.

4.4 Optional Information
Refers to information that can be option ally stored in the RFID tag but is not mandatory. This data is included at the

discretion of the user.

4.5 RFID Tag
An electronic device consisting of an integrated circui t and antenna which, when embedded in a mould, is capable of receiving, holding and transmitting information related to t he ULD. Tag can be read and written to multiple times.

4.6 Reader/Writer
An electronic device for performing the process of retrieving data from and potentially transmitting data to an RFID tag and, as appropriate, the contention and error control management , and channel and source decoding required to recover and communicate the data entered at source. The device may also inte rface with an integral display and/or industrial controller.

4.7 Memory Structure
The RFID tag comprises of 4 memory banks, as show n in Table 1 (below). (s ee paragraph 10.5 – ISO/IEC 18000-63 Memory Banks).

Table 1: ISO/IEC 18000-63 memory structure

Name 1 Abbreviation Purpose Memory Bank 00 2 MB00 Reserved (access and/or kill passwords) Memory Bank 01 2 MB01 UII (unique identification of the object to which the RF tag is affixed and an indicator as to whether MB11 contains any data) Memory Bank 10 2 MB10 TID (unique identification of t he RF tag according to ISO/IEC 15963) Memory Bank 11 2 MB11 User (user-specific data storage)

4.8 System Accuracy
The capability of avoiding errors in the read, write and storage process.

4.9 System Reliability

4.9.1 Read
The ability of an RFID system to capture information fr om an RFID tag properly progr ammed and presented which enters the readers specified coverage area.

4.9.2 Write
The ability of an RFID system to write informati on to an RFID tag in the specified coverage area.

4.10 Open Application
An open application is an RFID system that is implemented for the use of several acto rs such as airlines or other members of the community at one or multiple loca tions such as airports or cargo areas.

1 The subscript following the memory bank number in dicates that the value presented is in binary.

### 3 4.11 Abbreviations
AFI Application Family Identifier

IEC International Electrotechnical Commission ISO International Organi zation for Standardization MHz Megahertz OID Object Identifier RF Radio Frequency RFID Radio Frequency Identification TID Tag Identifier UHF Ultra High Frequency UII Unique Item Identifier

ULD Unit Load Device

5. SYSTEM REQUIREMENTS
The RFID System must meet the following requirements:

5.1 The air interface protocol shall be in accordance with ISO/IEC 18000-63 (Type C). The data is encoded in memory bank 01 and 11 according to this Recommended Practice.

5.2 Conformance testing of the system shall be in accordance with ISO/IEC 18047-6 (for 860 to 960 MHz).

5.3 Be capable of transferring the information to and from automat ed systems, using airline acc epted industry protocols and

data elements.

5.4 Provide readers/writers adaptable to fi xed, mobile or portable applications.

5.5 The components of the system shall be c onfigured to achieve the highest measur ed reliability, taking into account the physical constraints of the various actors and radio regulations . Performance shall be measured in accordance with ISO/IEC

18046.

5.6 In a controlled test environment the read/write rate of the chip and antenna should be 99.7% or better.

5.7 In operational conditions the read rate of the system should be 99.5% or better.

5.8 Fulfil local environmental regulati ons related to RFID tag disposal.

5.9 No interference with other electronic equipment. Not affect ed by other electrical equipment and/or radio emissions which can occur on the system operating frequencies normally found in t he airline industry. When equipment is in the vicinity of operating aircraft, electronic hardwar e needs to be RTCA DO-160 compliant.

5.10 When installed or operated in a particular country, the system must comply with all international, national and local governmental health, safety, aeronautical and radio regulations, and any other governmental rules and regulations which may apply, including those regarding human exposure levels and medical implants.

6. THE RFID TAG REQUIREMENTS, CHARACTERSITICS AND SPECIFICATIONS
The RFID tag must meet the following requirements:

6.1 As a minimum, being capable of being programmed in accordanc e with the composition of the IATA Identification Code for ULDs stipulated in Resolution 686 as physically marked on the ULD.

6.2 The information on the RFID tag must not conflict with human readable formats.

6.3 Be capable of meeting requirements in accordance with SAE AS5678.

6.4 Be capable of retaining programmed data and responding to an RFID reader.

6.5 Be read or written to without any unauthorized modification.

6.6 RFID tags for the purpose of automatic identifica tion of ULDs must be based on passive technology.

6.7 Have a minimum life of 5 (five) years for passive tags.

6.8 Environmental

6.8.1 The RFID tag shall function properly in all of the environmental conditions enc ountered in the air transport operational

environment.

### 4 6.8.2 An RFID tag must be capable of operating in temperat ure ranges of -40°C (-40°F) to +70°C (+158°F) and must maintain the integrity of stored data at temperatures from -51°C (-60°F) to +85°C (+185°F), with both storage and operating humidity ranges of up to 99%, be water and chemical (glycol or other de-icing fluids) resistant, as well as to changes in atmospheric pressure. Certain site specific conditions ma y require higher or lower operating temperature ranges and

environmental characteristics.

6.8.2.1 Low temperature An RFID tag must fully operate at a mini mum low temperature of -40°C (-40°F). An RFID tag must fully operate at such minimum temperatures after having been stored at a minimum low temperature of -51°C (-60°F) with an exposure time of 24 hours per day for a period of up to 60 days. Testing will be accomplished in accordance with IEC 60068-2-1 (MIL-STD810G, Method 502.5).

6.8.2.2 High temperature An RFID tag must fully operate after having been cycled between +70°C (+158°F) and +38°C (+100°F). An RFID tag must fully operate at such temperature extremes after having been stored at a minimum high temper ature of +85°C (+185°F) with an exposure time of 12 to 15 hours per day for a period of up to 60 days. Testing will be accomplished in accordance with IEC 60068-2-2 (MIL-STD-810G, Method 501.5).

6.8.3 Mechanical Shock: IEC Series 60068-2-27 (MIL STD 810G Method 516.6 Procedure I); 30g for 11 milliseconds, half sine pulse.

6.8.4 Random Vibration: IEC Series 60068-2-53 (MIL STD 810G Me thod 514.6, Category 5, Procedure III).

6.9 Electromagnetic Compatibility and Nuclear Radiation Environment The RFID shall function and maintain the integrity of its stored data.

6.9.1 In the electro-magnetic environment of air traffic; e.g. as an example in a maximum peak field strength of 200 V/m peak exposure level test for 1300 MHz and 2800 MH z to simulate airport radar exposures.

6.9.2 In security check environments as an example having received a maximum x-ray exposure of 25 mR or an absorbed

dose of 250 uG.

6.9.3 After being exposed to cosmic radiation during flights, for example having received a maximum exposure to thermal

neutron bombardment from an 80 mC Am-241/Be source or its equivalent.

7. READER/WRITER REQUIREMENTS, CHARACTERISTICS AND SPECIFICATIONS
The reader/writer must meet the following requirements:

7.1 Should be one of the following configurations, based on the application requirements: fixed, mobile, or hand-held

devices.

7.2 Be capable of reading from and writing to the RFID tag.

7.3 Be capable of transferring the information to/from autom atic data processing systems, using air transport industry accepted protocols and data elements.

7.4 Be capable of being integrated into a portable data te rminal which may contain RF ID communications modules.

7.5 All RFID readers must be capable of safe operation in and around stationary aircraft, in proximity to moving aircraft and in other airport areas.

7.6 Should be capable of reprogramming an RFID tag when required.

7.7 Performance Specifications The RFID Reader must meet the following requirements:

7.7.1 Be able to read a tag as it passes through a specified un obstructed reading range of up to 3 m (10 ft) at the passing speed up to 15 km/h (9 mph), so that the system can differentiate tags based on operati onal constraints including the following examples:

• In the case of reading ULD on moving dolly, at a distance of 3 m at 15 km/h passing speed with rate of reading at

99.5%

• In the case of reading ULD on moving conveyer, at a dist ance of 80 cm at 18 m/min (60 ft/min) with rate of reading

at 99.5%

• In the case of reading ULD in a stati onary position with a mobile handheld device , at a distance of 50 cm with rate of reading at 99.5%

7.7.2 Be capable of reading RFID tags passing the reader at conventional speeds up to 15 km/h (9 mph).

### 5 7.7.3 RFID readers located on parallel axis must not interfere with each other.

7.7.4 RFID readers located on one axis must not read RFID tags from an adjacent axis.

7.8 Environmental

7.8.1 All fixed, mobile and portable ULD RF ID readers compliant with this Recommended Practice must be capable of operating in temperature ranges of

− 20 ° C (-4°F) to +50 ° C (+122°F), humidity ranges of up to 99%, be water and chemical (glycol or other de-icing fluids) resistant, as well as to change s in atmospheric pressure. Certain site specific conditions ma y require higher or lower operating temperature ranges and env ironmental characteristics. Portable equipment, which is utilized in outdoor applications, mu st be rated NEMA 4 or equivalent.

7.8.2 Portable RFID readers shall function correctly after a dr op shock test IEC Series 60068-2-27 (Mil Std 810G Method 516.6, Procedure I); Height 122 cm (48 in) to concrete.

8 TAG POSITIONNING
Depending on the process, two to four ULD RFID tags should be attached to the sides of ULD to facilitate interoperability and interlining.

It is a minimum requirement that the attach ing of ULD RFID tag shall not have any effect on the certification, operation and airworthiness of the ULD. The attaching of ULD RFID tag should be done only after obtaining written approval for both position and method of attachment from the ULD manufacturer.

No part of the ULD RFID tag or it s enclosure should extend beyond the base dimensions and maximum allowable ULD contour (see IATA ULD Regulations) or any other operationally critical dimensions . The ULD RFID tag should not be located in a position where it is vulnerable to damage during operations.

8.1 Pallets: It is recommended that the ULD RFID tag attaching to pallet be located inside the seat track of the edge rail without preventing the attachment of cargo nets or straps in locations specified in the certification r equirements available

from the ULD manufacturer or the airlines.

8.2 Containers: It is recommended that the ULD RFID tag attach ing to container be placed at least 51 cm (20 in) above the

base of the container.

9. OPEN ARCHITECTURE

9.1 In order to meet international standards required for in terline operations, RFID reader s/writers shall be based on open architecture RFID standards, such that any manufacturer’s RFID ULD tags are read and/ or programmed by any other manufacturer’s reader/writer; and that any one manufacturer’s reading/writing equipment may read or write to any other manufacturer’s RFID ULD tags.

9.2 In compliance with the ISO Patent Policy, if the protocols and/or technologies cont ained in the relevant standards are not in the public domain, the proprietor shall license them th roughout the world on reasonable and non-discriminatory terms and

conditions.

10. ENCODING THE DATA ON THE RFID TAG

10.1 Introduction The encoding for this Recommended Practice 1640 shall be according to ISO/IEC 15962 for the ISO/IEC 18000-63 tag memory architecture.

10.2 Basic Encoding Rules Data shall be written to, and read from, the RFID tag using rule s defined in ISO/IEC 15962. This al lows airlines and airports complete flexibility in selecting from the present set of optional data elements, and for supporting new data elements should these be added at a future date. This flexibility can be implemented even to differentiate between the requirements of different routes, and to support the handl ing of different types of ULDs.

The encoded byte stream on the RFID tag shall be encoded according to the rules of ISO/IEC 15962. These rules are implemented automatically through a system that has both IS O/IEC 15961 and 15962 as part of the complete data protocol. The adoption of this data protocol also allows for IATA to extend the system to RFID tags on ULDs and other devices.

The No-Directory encoding rules defined in ISO/IEC 15962 shall be used for encoding all the data elements. These support encoding and decoding of data respectively to and from the RFID tag.

### 6 10.3 ISO/IEC 15961 Related Features

10.3.1 Object Identifier (OID) ISO/IEC 15961-2 requires that an OID structure is used to un iquely identify each type of dat a encoded on an RFID tag. An OID structure has been assigned to IATA with the common roo t: 1 0 15961 11. The final component of the OID is as defined in table 2 (below). For most object identifie rs, only the final component will need to be encoded.

Table 2: Object Identifiers & Data Elements

Object Identifier Object (Data Element) M andatory Memory bank Decoded data characters

1 0 15961 11 5 ULD ID Code Y 01 15 Alpha Numeric

1 0 15961 11 30 ULD OEM Name N 11 5 Alpha Numeric (CAGE Code)

1 0 15961 11 31 ULD OEM Serial Number N 11 1-15 Alpha Numeric

1 0 15961 11 32 ULD Part Number N 11 1-15 Alpha Numeric

1 0 15961 11 33 Date of Manufacture N 11 6 Numeric (YYYYMM)

Once the RFID tag is encoded, the memory on the RFID tag shall be locked.

10.3.1.1 Encoding Rules for the ULD ID Code Object ID 1 0 15961 11 5

This element is mandatory

. This element can only be defined by the ULD owner. The system should be able to read the ULD ID Code as per the composition stated in CSC Resolution 686 with the system

capacity of 15 characters.

Note:

The standard IATA ULD ID Code as stated in CSC Resoluti on 686 consists of nine (9) or ten (10) characters.

10.3.1.2 Encoding Rules for the ULD OEM Name Object ID 1 0 15961 11 30

This element is optional. This element can only be defined by the ULD OEM.

It is recommended that the code of the ULD OEM Name be bas ed on the Commercial and Government Entity (CAGE) Code (US) or NATO Commercial and Governmental Entity (NCAGE) Co de (other countries), which comprises of 5 alpha numeric

characters.

10.3.1.3 Encoding Rules fo r ULD Serial Number Object ID 1 0 15961 11 31

This element is optional. This element can only be defined by the ULD OEM. It comprises of maximum 15 alpha numeric characters.

10.3.1.4 Encoding Rules for ULD Part Number Object ID 1 0 15961 11 32

This element is optional. This element can only be defined by the ULD OEM. It comprises of maximum 15 alpha numeric characters.

10.3.1.5 Encoding Rules for Date of Manufacture Object ID 1 0 15961 11 33

This element is optional. This element can only be defined by the ULD OEM. It comprises of 6 numeric characters in the format of YYYYMM. e.g.: 201302 for February 2013.

10.3.2 AFI The AFI is a single byte code that is used to distinguish particular types of tag across the air interface, enabling the interrogator to ignore tags with different AFI values. The AF I assigned to IATA for ULD identification is 91 (hexadecimal).

10.3.3 Data Format The data format code is used to distinguish between the semantics of different types of data on RF ID tags that are compliant with ISO systems.

Note: The data format is a mechanism that allows the OID to be significantly truncated so that, in the case of this Recommended Practice, the common elements of the OID structur e do not have to be encoded on the RFID tag. They are only present in the communication to ensur e interoperability with RFID equipment.

### 7 For IATA ULD automatic identification purpo ses, the data format is the decimal code 11. This particular code needs to be used in some of the commands to configure t he tag so that data can be interpreted properly.

10.4 ISO/IEC 15962 Related Features Encoding in accordance with ISO/IEC 15962 ensures:

- That maximum use is made of the encoding capacity (memory on the RFID tag), by avoiding the structured “message”.

- Allows any authorised user to read the RFID tag and abstr act any, or all, of the encoded data without the need to understand the sequence.

- Allows for different air cargo supply chain actors to adopt different data elements within this Recommended

Practice without reference to others.

- Allows this Recommended Practice to be updated with new data elements without any concerns about backwards compatibility.

What follows is based on the use of ISO/IEC 18000-63 (Type C).

10.5 ISO/IEC 18000-63 Memory Banks ISO/IEC 18000-63 (Type C) specifies an air interface protocol. T he air interface standard does not specify the size of the memory, only the overall architecture. The RFID tag comp rises of 4 memory banks, as defined in paragraph 4.7.

MB 00 Reserved Memory Although this is defined as “reserved”, it is actually used for encoding a kill password and/or an access password.

MB 01 Unique Item Identifier

It is recommended that MB 01 be of a minimum capacity of 128 bits.

MB 10 Tag Identification Memory This memory is pre-encoded by the tag manufacturer, and is not directly related to the functions of this Recommended

Practice.

MB 11 User Defined Memory For ISO-related applications, this is used exactly as def ined in ISO/IEC 15962 using the No-Directory encoding method.

It is recommended that MB 11 be of a minimum capacity of 512 bits.

When purchasing RFID tags, air cargo supply chain actors are advised to check the capacity of MB 01 and 11. It is then necessary to match the amount of data to be encoded to the memory bank (see paragraph 10.3.1).

11. SECURITY

11.1 Tags should be supplied without any data in MB 00, MB 01 and MB 11.

11.2 The system must be programmable only by the authorized user(s).

11.3 The system must be electronically secure and protected against unauthorized alteration. Once the RFID tag is encoded, the memory on the RFID tag shall be locked.

12. IMPLEMENTATION
The transition phase will be the time from the first live application of the RFID technology in ULD handling until a fairly lar ge majority of airlines, independent ground handling companies and airports have adopted the RFID technology. During this phase, commonly used ULD handling systems will either use both barcode scanning and RFID identification, or barcode scanning only.

13. REFERENCES

IATA Documents referred to in this Recommended Practice are: IATA Passenger Services Conference Resolutions Manual Recommended Practice 1740c – Radio frequency identif ication (RFID) specifications for interline baggage IATA Cargo Services Conference Resolutions Manual

Resolution 680 - General Rules for the use of Unit Load Devices

Resolution 686 – IATA identification code for Unit Load Devices

IATA’s web-site can be visited at: http://www.iata.org

.

DO-160G, Environmental Conditions and Test Procedures fo r Airborne Equipment, standard for environmental test of avionics hardware published by Radio Te chnical Commission for Aeronautics ( RTCA), Incorporated

.

### 8 ISO Reference Documents:

ISO/IEC 15961-1 Information technology — Radio frequenc y identification (RFID) fo r item management—Data protocol: application interface

This standard:

 provides guidelines on how data shall be presented as objects

 defines the structure of object identifiers, based on ISO/IEC 9834-1

 defines access and formatting features such as t he Application Family I dentifier, and data format

 specifies commands and responses that support the transfer data between the application and the RF tag

ISO/IEC 15962 Information technology — Radio frequency identification (RFID) for item management—Data protocol: data encoding rules and logical memory functions

This standard:

 defines the encoded structure of object identifiers

 specifies the data compaction rules that apply to the encoded data

 specifies a Precursor for encoding syntax features efficiently

 specifies formatting rules for the data, e.g. depending on whether a directory is used or not

 defines how application commands, e.g. to lock data, are transferred to the Tag Driver

ISO/IEC 18000-63 Information technology — Radio frequency identification fo r item management — Part 63:

Parameters for air interface communications at 860 MHz to 960 MHz This standard defines, for three types of RFID tag, of the follo wing features (some of which are shared by one or more of the types):

 Anticollision algorithm that enables on e tag to be selected from many tags

 Modulation of the radio signal

 Bit encoding rules across the air interface

 Air interface commands and responses

 Some tag structuring features ISO/IEC 18000-63 (Type C) is the only type relevant to this Recommended Practice.

ISO/IEC 18047-6 Information technology—Radio frequency identification device conformance test methods — Part

6: Test methods for air interfa ce communications at 860 to 960 MHz

ISO/IEC 18046-1 Information technology—R adio frequency identification device performance test methods—Part 1: Test methods for system performance

ISO/IEC 18046-2 Information technology—R adio frequency identification device performance test methods—Part 2: Test methods for interrogator performance

ISO/IEC 18046-3 Information technology—R adio frequency identification device performance test methods—Part 3: Test methods for tag performance