Attachment_0015_aRFID_ITV_Server_Interface_Document.pdf

DL2-SWD-08148-005-L

FOR OFFICIAL USE ONLY

Version 5.5

Radio Frequency - In-Transit Visibility

(RF-ITV)

ITV Server Interface Document

Validated for RF-ITV System Version 4.0

Validated for S-ITV System Version 3.0

6 January 2016

Disclaimer:

The information contained in this document and any file transmitted with it is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure. Any disclosure, distribution, copying or use of the information by anyone other than the intended recipient, regardless of address or routing, is strictly prohibited. Distribution authorized to Department of Defense (DoD) components, and U.S. DoD specified contractors only, for administrative or operational use.

DL2-SWD-08148-005-L

DISCLAIMER

The use of trade names in this document does not constitute an official endorsement or approval of the use of such commercial hardware or software. Do not cite this document for advertisement.

DISPOSITION INSTRUCTIONS

Destroy this document when no longer needed. Do not return it to the organization. Safeguard and destroy this document with consideration given to its classification or distribution statement requirements.

Version 5.5 FOR OFFICIAL USE ONLY - iii -

Summary of Changes

Revision Number

Date Major Changes Party Responsible for

Change

4.1 2008 Updated section on Sensor Message

Formats.

Bob Lytle & Jean

Meslie, Unisys

4.2 2008 Added the “Physical Write Indicator” on the Write “W” Record Format (field 9).

Change LOT_NBR from 14 to 17 characters

(Ammo Detail “A” Record Format - field 6).

Steve Miller, Unisys

4.3 27 January 2009 Changed Asset Manager Org from length of 1 to 9 (Asset Tag “A2” Record Format -field 11).

Steve Miller, Unisys

5.0 21 October 2009 Replaced Registration Format 2.0 with

Registration Format 3.0. Reformatted document. Approved by PM J-AIT.

Maria Di Paolo-Greer, Unisys

5.0.1 20 January 2010 Removed reference to SWA in response to

MR02808

Greg Smith, Unisys

5.1 29 March 2010 Record R3A: NON DOD was removed as an accepted value for Geographic Command.

Record R31: Clarified values for Communication Type.

Maria Di Paolo-Greer, Unisys

5.1.1 10 May 2010 Removed all references to section numbers.

Maria Di Paolo-Greer, Unisys

5.1.2 30 June 2010 Sections “Sensor Tag Messages” through

“Appendix B” were updated to the RFID III Released Version.

Maria Di Paolo-Greer, Unisys

5.2 03 August 2010 Sensor and Timer IDs added to the Timer and Sensor tables in “Sensor Tag Messages” section.

Changes to “Sensor Tag Messages” section, Appendix A, and Appendix B to address several issues with the Sensor Tag

Message WSDL and XSD.

Perry Stephens, Eric

Wang, and Jimmy Li, Unisys

5.3 8 June 2012 1. Updated Record U5 with Container ID and Container ID Type to support Unit

Move Shipments.

2. Removed references to the Europe and

Pacific servers.

3. Removed RFID-III from document title

4. Added section for “General rules for

TIP filename format for upload”.

5. Updated U5 Field 2 – specified valid values.

6. Updated R38 Field 3 – added note that spaces should be removed in Device

Name.

7. Updated E Record Field 5 – changed to optional

Maria Di Paolo-Greer, Lockheed Martin

Version 5.5 FOR OFFICIAL USE ONLY - iv -

8. Changed logo

5.4 21 May 2013 Changed logo to PD AMIS, removed section 7 and Appendix A and B as not implemented

Greg Smith, Lockheed Martin

5.5 6 January 2016 1. Registration “R3A” Record Format, Field 3 Country Code: change to read “Use ISO Country Code.”

2. Registration “R3A” Record Format, Field 6 Site Representation: add additional “Valid Values.”

Bob Moore, Lockheed Martin

Version 5.5 FOR OFFICIAL USE ONLY - v -

Table of Contents

Summary of Changes ............................................................................................................. iii Table of Contents.................................................................................................................... v 1 Overview

1.1 General rules for all records and formats

1.2 General rules for TIP filename format for upload

1.3 Registration Format

1.3.1 Business Rules for Identifying and reporting RFID Devices

1.3.1.1 Active Devices: 48-bit Device ID

1.3.1.2 Inactive Devices: Host Media Access Control (MAC) Address

1.4 Tag Write Formats

1.5 Read Formats

2 Registration Format 3.0

2.1 Overview

2.2 Registration Fields

2.3 Registration Record Types - Summary

2.4 Summary of Changes

2.5 Registration “R31” Record Format

2.6 Registration “R32” Record Format

2.7 Registration “R33” Record Format

2.8 Registration “R34” Record Format

2.9 Registration “R35” Record Format

2.10 Registration “R36” Record Format

2.11 Registration “R37” Record Format

2.12 Registration “R38” Record Format

2.13 Registration “R39” Record Format

2.13.1 Converting Degrees/Minutes/Seconds to Decimal

2.14 Registration “R3A” Record Format

2.15 Registration “R3B” Record Format

2.16 Registration “R3C” Record Format

2.17 Registration “RD” Record Format

2.18 Registration “S” Record Format

3 Registration Format 2.0 (Legacy - for reference only)

3.1 Overview

3.2 Registration Record Types

3.3 Registration “R1” Record Format

3.3.1 RF-ITV Server Communication Mode Table

3.4 Registration “R2” Record Format

3.5 Registration “R3” Record Format

3.6 Registration “R4” Record Format

3.7 Registration “R5” Record Format

3.8 Registration “R6” Record Format

3.9 Registration “R7” Record Format

3.10 Registration “R8” Record Format

3.11 Registration “R9” Record Format

3.12 Registration “RD” Record Format

4 TIPS Write Upload Formats

4.1 Overview

4.2 Sustainment Write Record types

Version 5.5 FOR OFFICIAL USE ONLY - vi -

4.3 Unit Move Write Record types

4.4 Asset Write Record Types

4.5 Date “D” Record Format

4.6 Status “S” Record Format

4.7 Erase “E” Record Format

4.8 Write “W” Tag Record Format

4.9 Sustainment Record Definitions (L1 thru L4)

4.9.1 License Plate “L1” Record Format

4.9.2 License Plate “L2” Record Format

4.9.3 License Plate “L3” Record Format

4.9.4 License Plate “L3A” Record Format

4.9.5 License Plate “L4” Record Format

4.10 Unit Move Record Definitions (U1 thru U5)

4.10.1 License Plate “U1” Record Format

4.10.2 License Plate “U2” Record Format

4.10.3 License Plate “U3” Record Format

4.10.4 License Plate “U4” Record Format

4.10.5 License Plate “U4A” Record Format

4.10.6 License Plate “U5” Record Format

4.11 TCMD TRAILER “T” Record Format

4.12 Commodity Item “N” Record Format

4.13 Ammo Detail “A” Record Format

4.14 ASSET Write/Update Records (A1 thru A5 and “U”)

4.14.1 ASSET Update Record

4.14.2 ASSET “A1” Record Format

4.14.3 ASSET “A2” Record Format

4.14.4 ASSET “A3” Record Format

4.14.5 ASSET “A4” Record Format

4.14.6 ASSET “A5” Record Format

4.15 Checksum Algorithm

4.15.1 Overview

4.15.2 Algorithm

5 TAG Read Reporting Records

5.1 Overview

5.2 Read “C” Record Format

5.2.1 Read “C” Record Format - Legacy

5.2.2 Read “C” Record Format – Enhanced Capability

5.2.3 “SENSOR_DATA” Description 6 Communications

6.1 Communications Protocol

Version 5.5 FOR OFFICIAL USE ONLY - 1 -

1 Overview

This document describes in detail the formats supported by the RF-ITV National server located in the Continental United States (CONUS). The document will also describe how to register a device and upload tag Write/Read information to the RF-ITV server.

1.1 General rules for all records and formats

The following includes rules for all records and format:

All information is to be reported in Upper Case, unless otherwise noted.

Optional Fields: Do not put spaces between the Pipe delimiters when a field is optional.

Just use the back-to-back pipe delimiters (eg. “||” vs “| |”).

The last field in each record will be a checksum value, see checksum algorithm on how to calculate the checksum

Each record will be terminated with a Line Feed (LF) character (ASCII: Octal 012, Hex

A, Decimal 10)

1.2 General rules for TIP filename format for upload

The .tip file contains the registration data of the Read and Write RFID stations and the shipment data processed at a Write RFID station. The .tip file is transferred to the RF-ITV server where it is processed, stored, and displayed on the RF-ITV Tracking Portal. The ITV Server Interface

Document defines the .tip file data format. The RF-ITV server requires the uploaded .tip filenames to be unique and no more than 32 characters each. In addition, incorporating all or part of a .tip file's path into the file name is strictly prohibited (e.g., filename:

C:\Temp\42700038009.tip).

Below are some recommended options for filename format:

Registered Device ID + Sequence Number.tip (for example, 42700038.tip)

Registered Device ID + Sequence Number + Reg.tip for Registration TIP files (for example, 42700039Reg.tip).

A date/time stamp can also be used as a sequence number.

1.3 Registration Format

The following format will be used to register a Read/Write stations with the RF-ITV server.

Registration Format 3.0

The previous Registration Format, version 2.0, has been included in this document for reference only. The RF-ITV server will no longer support this format in the future. All future development of applications should be using Registration Format 3.0.

Version 5.5 FOR OFFICIAL USE ONLY - 2 -

1.3.1 Business Rules for Identifying and reporting RFID Devices

The following covers two classes of devices: active devices and inactive devices. Active devices are capable of reporting their IDs through a published interface; inactive devices, such as USB cables, do not have this capability.

1.3.1.1 Active Devices: 48-bit Device ID

Active Devices will use the same convention as the ISO 18000-7 Tag ID construction. This will apply to all devices used within the RF-ITV network. This new identifier will have the following properties:

48-bits in length consisting of 16-bit manufacturer ID (as defined by ISO 18000-7) followed by 32-bit serial number managed and administered by each manufacturer.

o Vendor XYZ Technology Manufacturer ID: 1150 (hex) o Vendor XYZ assigned 32-bit serial number: 12345678 (hex)

Examples:

Hexadecimal Reported As (Decimal)

115046555F00 19036475055872

115046EDF57F 19036485055871

The Decimal equivalent of the ID will be labeled on the device.

The 48-bit Device ID must be reported in decimal representation to the RF-ITV server.

The 48-bit ID will convert to a maximum of 15 digits, with no leading zeroes.

1.3.1.2 Inactive Devices: Host Media Access Control (MAC) Address

For inactive RFID devices such as tag write cables, the device cannot report its ID. To ensure uniqueness, the host MAC address shall be used as the unique ID. In this case, there is no need to identify individual devices – only the host computer needs to be registered.

The MAC address uniquely identifies an attached network adapter on the host. Any host reporting data to the RF-ITV server must be equipped with a network adapter to report to the RF-

ITV server. The MAC numbering scheme is managed by IEEE, and is designed to be globally unique.

The MAC address shall be reported in hexadecimal form as a series of 12 hexadecimal values prefixed with ‘T’.

Example:

MAC address Reported As (Hexadecimal)

00-05-9A-3C-78-00 T00059A3C7800

In the case where a host has multiple network adapters, the first (primary) adapter shall be queried for its MAC address. If the software detects that the MAC address of the host has changed, it shall inform the user to re-register the new MAC address.

Version 5.5 FOR OFFICIAL USE ONLY - 3 -

1.4 Tag Write Formats

The following formats will be used to upload Tag Write information to the RF-ITV Server:

Sustainment Upload Format, Unit Move Upload Format, and Asset Tag Upload Format.

Sustainment Write Upload Format

Unit Move Write Upload Format

Asset Tag Write Upload Format

1.5 Read Formats

When uploading TAG Read events, the following records should be used to report the information to the RF-ITV server.

Read Event Format

Version 5.5 FOR OFFICIAL USE ONLY - 4 -

2 Registration Format 3.0

2.1 Overview

This format is the newest format used to register a device to the National ITV server. This registration is performed initially when a site is set up. If there are any subsequent changes to the information, then the site needs to re-register.

2.2 Registration Fields

This format is used to register a station to the National ITV server. It is only used once to register the station with the ITV Server.

All records are required (R31 – R3C). RD is optional for Read Sites.

Note: When a field is optional, spaces should not be placed between the pipes (vertical bars).

For example: “R4|||FA|”

The following is an example of a Field Data Unit Registration File:

R31|BRAGG|R|1|0706251802|75|

R32|JOHN.DOE|907 353 3075|DC|

R33|JOHN.DOE@US.ARMY.MIL|8B|

R34|01:00:00| UHF:5.730|8F|

R35|192.192.192.244|WAIN223A0RFIDR5|tips|D0|

R36|x86|Windows XP 5.1|49|

R37|TIPS-Read 3.7.1.52|0E|

R38|43665|WAINWRIGHTR1-2|MARSHALLING AREA INBOUND|A8|

R39|64.500205|147.373330|1|DAS|00:00:20|D1|

R3A|PACOM|US|AK|ARMY|CLASSI|YERTY|21204|A7|

R3B|1|0|0|2|D1|

R3C|||E3|

RD|43665|W2A535|A2|

The following is an example of a Coalition Shared Registration File:

R31|JD5|R||0705100654|95|

R32|||F8|

R33||7D|

R34|||FA|

R35||||77|

R36|||FC|

R37|CMS 1.0|0B|

R38|51825|READER_51825||35|

R39|34.315555|69.111799||||9F|

R3A|NON DOD|AS|0|NA|0|||9A|

R3B|0|0|1|2|4C|

R3C|KAU||3B|

RD|||A2|

Version 5.5 FOR OFFICIAL USE ONLY - 5 -

2.3 Registration Record Types - Summary

Note that the number “3” was added to most of the Record Type to identify the version of the registration format.

Each device should be represented by a separate set of Registration Records.

Record Type Description Detail Mandatory/

Optional Frequency

R31 Registration Record #1, version 3.0 R31| Military Installation | Station Function | Communication Type and

Protocol | Registration Date and Time (GMT) | CHECK_SUM | /r

Mandatory 1

R32 Registration Record #2, version 3.0 R32 | POC Name | POC Phone Number | CHECK_SUM | /r Mandatory 1

R33 Registration Record #3, version 3.0 R33 | POC Email Address | CHECK_SUM | /r Mandatory 1

R34 Registration Record #4, version 3.0 R34 | Site Upload Schedule | Device Firmware Version | CHECK_SUM

| /r

Mandatory 1

R35 Registration Record #5, version 3.0 R35 | Station IP Address | Station Computer Name | Station OS User

Login ID | CHECK_SUM | /r

Mandatory 1

R36 Registration Record #6, version 3.0 R36 | Station Computer Architecture | Station Operation System Name and Version | CHECK_SUM | /r

Mandatory 1

R37 Registration Record #7, version 3.0 R37 | ITV Client Software Name and Version | CHECK_SUM | /r Mandatory 1

R38 Registration Record #8, version 3.0 R38 | Device ID | Device Name | Functional Description of Device |

CHECK_SUM | /r

Mandatory 1

R39 Registration Record #9, version 3.0 R39 | Latitude | Longitude | Location Code Type | Location Code |

Collection Interval | CHECK_SUM | /r

Mandatory 1

R3A Registration Record #A, version 3.0 R3A | Geographic Command | Country Code | U.S. State Code | U.S.

Service | Site Representation | City | Zip Code | CHECK_SUM | /r

Mandatory 1

R3B Registration Record #B, version 3.0 R3B | Mobile Type | Sensor Indicator | Coalition Indicator | Tag

Collection Mode | CHECK_SUM | /r

Mandatory 1

R3C Registration Record #C, version 3.0 R3C | Coalition Routing Code | Coalition Public Code | CHECK_SUM |

/r

Mandatory 1

RD DODAAC Association Record. RD | Device ID | DODAAC | CHECK_SUM | /r Optional 0 to Many

S Status Record Format S | Current Date | Device ID | Status Code | Start Flag | CHECK_SUM |

/r

Mandatory 1

Version 5.5 FOR OFFICIAL USE ONLY - 6 -

2.4 Summary of Changes

The following table represents the changes that were made from Registration Format 2.0 to

Registration Format 3.0. The checkmarks indicate the version where the field resides. A checkmark in both versions signifies that the field is in both versions. A checkmark in one of the versions signifies that the field is in one of the versions only.

Field Name Registration Formats v2.0 v3.0

Installation Location

Station Function

Communication Type and Protocol

Registration Date and Time

POC Name

POC Phone Number

POC Email Address

Site Upload Schedule

RF Relay Channel

Station IP Address

Station Computer Name

Station O/S Login Name

Station Computer Architecture

Station Operating System and Version

ITV Client Software Name and Version

Total Memory

Total Memory Available

Device ID

Device Name

Device Description

Latitude of Device *

Longitude of Device *

Milair Code

Milsea Code

Device Collection Interval

Coalition Routing Code

Coalition Public Code

DODAAC

Military Installation

Iridium SIM Serial Number

Device Firmware Version

Functional Description of Device

Location Code Type

Location Code

Geographic Command

Country Code

U.S. State Code

U.S. Service

Site Representation

City

Station Zip Code

Mobile Type

Sensor Indicator

Coalition Indicator

Tag Collection Mode

Current Date

Status Code

Start Flag

* Format is modified

+ Limited to RF-ITV accepted data values only (refer to lists in document)

Version 5.5 FOR OFFICIAL USE ONLY - 7 -

2.5 Registration “R31” Record Format

The following table represents the registration format for R31 Record Format.

RF Tag Field

Number Field Name

Fixed

Data

Data

Type

Max

Len

IR/DD

Required

Element Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R31 A/N 3 M Record Identifier

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character:

0x7c

Field 2 Military Installation A/N 15 O The name of the base where the station is located.

Do not include prefixes in the name (i.e. FT or CAMP). Examples of military installations are

BRAGG and ARIFJAN.

User input

Field 3 Station Function A 1

M Function the Station is performing.

Valid values are:

“R” = READ/COLLECT

“W” = WRITE

Application Driven

Field 4 Communication Type and

Protocol

A 1 M Communication medium by which data is uploaded.

Communications type for connecting to the Internet to upload data. In Standalone mode, no connection

Application Driven /

FDU user options:

Version 5.5 FOR OFFICIAL USE ONLY - 8 -to the Internet is made for uploading files. The files remain on the client.

The Communication Protocol used for transferring files to servers.

The selection drives the FDU software – if a user selects HTTPS, the FDU software cannot upload using FTP.

Communication Device Protocol Value

Standalone N/A A

LAN

FTP L

HTTPS 1

SFTP 4

Modem via Landline

FTP P

HTTPS 2

SFTP 4

Modem via Satellite- InmarsatC

Email S

Modem via Satellite-

InmarsatM

FTP T

HTTPS 3

SFTP 4

Modem via Satellite-

Iridium

FTP 5

HTTPS 6

SFTP 4

Modem via Cell Phone

FTP 7

HTTPS 8

SFTP 4

Modem via Unknown

Device

FTP Y

HTTPS Z

SFTP 4

Communication

Type:

Standalone

Network

Modem

Satellite

Communication

Protocol:

HTTPS

SFTP

FTP

Version 5.5 FOR OFFICIAL USE ONLY - 9 -

Field 5 Registration Date and Time

(GMT)

N 10 M Date and time of device registration in GMT.

Format is YYMMDDHHMM where:

YY = year (00-99)

MM = month (01-12) DD = day (01-31)

HH = hour (00-23)

MM = minutes (00-59)

Field 6 Iridium SIM Serial Number

A/N 19 C Serial Number of the SIM used in Iridium modem

C is for Conditional:

Communication Type and Protocol = 5 or 6, then Mandatory

Otherwise Optional

User Input

Field 7 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Filler \r M ASCII Code for Carriage Return: 0xd

Version 5.5 FOR OFFICIAL USE ONLY - 10 -

2.6 Registration “R32” Record Format

The following table represents the registration format for R32 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R32 A/N 3 M Record Identifier

Field 2 POC Name A/N 30 M Point of Contact (POC) assigned to the site. If no POC is available, enter FSE name.

Validation:

Allowed Characters:

A thru Z

Hyphen

Apostrophe

Space

Period

Field 3 POC Phone Number A/N 30 M Contact number for the Point of Contact (POC)

A thru Z

0 thru 9

Hyphen

Space

Filler | 1 M Field Delimiter

Version 5.5 FOR OFFICIAL USE ONLY - 11 -

Field 4 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Filler /r M ASCII Code for Carriage Return: 0xd

Version 5.5 FOR OFFICIAL USE ONLY - 12 -

2.7 Registration “R33” Record Format

The following table represents the registration format for R33 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R33 A/N 3 M Record Identifier

Field 2 POC Email Address A/N 50 M E-mail address for the Point-of-Contact (POC) Application Driven /

A thru Z

0 thru 9

@ Symbol

Hyphen

Underscore

Period

Field 3 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 13 -

2.8 Registration “R34” Record Format

The following table represents the registration format for R34 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R34 A/N 3 M Record Identifier

Field 2 Site Upload Schedule A/N 8 C Frequency that device uploads data to the RF-ITV National Server.

Format is HH:MM:SS

HH = hours (00-23)

SS = seconds (00-59)

C is for Conditional:

If Station Function = R, then Mandatory.

If Station Function = W, then Optional

Field 3 Device Firmware Version A/N 80 O A string that contains the version of the firmware currently loaded in the device.

Example:

UHF:5.730

NA:0.424

Version 5.5 FOR OFFICIAL USE ONLY - 14 -

Version 5.5 FOR OFFICIAL USE ONLY - 15 -

2.9 Registration “R35” Record Format

The following table represents the registration format for R35 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R35 A/N 3 M Record Identifier

Field 2 Station IP ADDRESS A/N 23

O Computer Internet Protocol address.

For IPv4:

Format: “0.0.0.0”

Null

For IPv6:

Format: “0.0.0.0.0.0”

Format is:

IPv4: AAA.BBB.CCC.DDD where:

AAA = 0-255 (leading zeros omitted) BBB = 0-255 (leading zeros omitted)

CCC = 0-255 (leading zeros omitted)

DDD = 0-255 (leading zeros omitted)

IPv6: AAA.BBB.CCC.DDD.EEE.FFF where:

AAA = 0-255 (leading zeros omitted)

BBB = 0-255 (leading zeros omitted) CCC = 0-255 (leading zeros omitted)

DDD = 0-255 (leading zeros omitted)

EEE = 0-255 (leading zeros omitted)

FFF = 0-255 (leading zeros omitted)

Version 5.5 FOR OFFICIAL USE ONLY - 16 -

Field 3 Station Computer Name A/N 30 O Computer name usually assigned when operating system is installed.

Application Driven

Field 4 Station OS User Login ID A/N 10 O Computer operating system login name for Field Data Unit (FDU).

Application Driven

Field 5 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 17 -

2.10 Registration “R36” Record Format

The following table represents the registration format for R36 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R36 A/N 3 M Record Identifier

Field 2 Station Computer Architecture

A/N 20 O Computer processor name and type. Application Driven

Field 3 Station Operating System Name and Version

A/N 70 O Computer operating system name, version, and patch number, i.e. “Windows XP” or “Window 2000

SP2”.

delimiters for the check-sum

Application Driven

Version 5.5 FOR OFFICIAL USE ONLY - 18 -

2.11 Registration “R37” Record Format

The following table represents the registration format for R37 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R37 A/N 3 M Record Identifier

Field 2 ITV Client Software Name and Version

A/N 30 M Name and version of FDU client software. Application Driven

Field 3 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 19 -

2.12 Registration “R38” Record Format

The following table represents the registration format for R38 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R38 A/N 3 M Record Identifier

Field 2 Device ID A/N 32

M This field represents one of the following:

Serial number of the device assigned by the manufacturer or

Serial number of the Tag Docking Station or Cable assigned by the manufacturer

Tag docking stations and Cables will precede the serial number with a “T”. For example, if the Serial

Number equals “904110100”, then the Device ID will be “T904110100”.

Note: For the ISO implementation, users will no longer be required to enter the serial number. The client will extract the computer’s MAC address and use it in lieu of a Tag Docking station/Cable serial number.

User Entry or Application Driven.

For smart devices, auto extract ID of the smart device.

A thru Z

0 thru 9

Up to 32 characters

Field 3 Device Name A/N 20

M Short name, i.e. “BAGRAMAFBR1”.

Format is PPPPTN-M (with no spaces), where:

User enters text.

Version 5.5 FOR OFFICIAL USE ONLY - 20 -

PPPP = Military Installation or City (note: remove the spaces that appear in the Military Installation or

City name) T = Station Function (R=read, W=write)

N = sequence number representing the station

<hyphen>

M = sequence number representing the interrogator attached to the same station

If Fort Bragg has three read stations with one interrogator each, then it would have three registered as BRAGGR1, BRAGGR2 and BRAGGR3.

If the first station had 2 interrogators, then the format is BRAGGR1-1, BRAGGR1-2

See naming convention document for detailed information.

Recommendation to

FDUs: The PPPP and T portion of the same should be pre-populated since this information can be extracted from other fields.

Sequence Number should be entered by user.

Field 4 Functional Description of the Device

A/N 40 M Long description of the device being registered.

Physical location and purpose of interrogator.

Format is zz zz = Functional Description

For example,

- CENTRAL RECEIVING ITO

- JDC In/Outbound Bldg 1021

Version 5.5 FOR OFFICIAL USE ONLY - 21 -

Field 5 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 22 -

2.13 Registration “R39” Record Format

The following table represents the registration format for R39 Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R39 A/N 3 M Record Identifier

Field 2 Latitude N 10 M The GPS Latitude Hemisphere of the device.

Format is Decimal. Precision of 6

See conversion formula from deg/min/sec to decimal, below this table.

Valid Range: -90 to

Field 3 Longitude N 11

M GPS longitude where device is installed.

Format is Decimal. Precision of 6

See conversion formula from deg/min/sec to decimal, below this table.

Valid Range: -180 to

Field 4 Location Code Type

N 1 O Used in conjunction with field Location Code (see below).

Valid Values are:

“1”= MILAIR

“2” = MILSEA

Not part of User Interface

Version 5.5 FOR OFFICIAL USE ONLY - 23 -

Field 5 Location Code A/N 20 O Used in conjunction with Location Code Type (see above).

User inputs Military Terms based on Type Code entered (i.e. IAD, DOV).

Not part of User

Interface

Field 6 Collection Interval of Device

A/N 8 C Time interval that the interrogator will read available tags. Used by read-only devices only.

Format is HH:MM:SS

HH = hours (00-23)

SS = seconds (00-59)

Note: Registration of a Write Station, do not put spaces between the pipes

C is for Conditional.

If Station Function = R, then Mandatory.

If Station Function = W, then Optional

Field 7 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 24 -

2.13.1 Converting Degrees/Minutes/Seconds to Decimal

Decimal Degrees = degrees + (minutes/60) + (seconds/3600)

For example, convert 47 degrees / 21 minutes / 56.52 seconds to decimal degrees.

Decimal degrees = 47 + 0.35 + 0.0157 = 47.3657 degrees

So, 47 degrees / 21 minutes / 56.52 seconds = 47.3657 degrees

A positive degree would indicate the northern (in the case of latitude) or eastern (in the case of longitude) hemisphere.

A negative degree would indicate the southern (in the case of latitude) or western (in the case of longitude) hemisphere.

Version 5.5 FOR OFFICIAL USE ONLY - 25 -

2.14 Registration “R3A” Record Format

The following table represents the registration format for R3A Record Format.

RF Tag Field

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R3A A/N 3 M Record Identifier

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 2 Geographic Command A 10 M The Geographic Command assignment in RF-ITV is based on the DoD Unified Command Plan. The World with Commanders'

Area of Responsibility map, included in the DoD plan, establishes the geographic responsibilities among the combatant commanders.

“AFRICOM” = DoD Africa Command

“CENTCOM” = DoD Central Command

“EUCOM” = DoD European Command

“NORTHCOM” = DoD Northern Command

“PACOM” = DoD Pacific Command

“SOUTHCOM” = DoD Southern Command

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 3 Country Code A 2 M Use ISO Country Code.

Field is a two alpha-character code. For example, “US” for

United States of America and “ZW” for Zimbabwe.

Refer to this site for the official list of the ISO official two alpha-character country codes:

http://www.iso.org/iso/country_codes

Valid fields are:

Version 5.5 FOR OFFICIAL USE ONLY - 26 -

2 alpha-character country code

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 4 U.S. State Code A 2 C FIPS State Codes for the U.S. States.

Field is a 2 alpha-character code. For example, “VA” for Virginia and “MI” for Michigan. The field is only user-required when the

Country Code=”US”

Refer to this site for the official list of the 51 FIPS two alpha-character state codes: http://www.itl.nist.gov/fipspubs/fip5-

2.htm

C is for Conditional.

If Country Code = US, then Mandatory.

If Country Code not ≠ US, then Optional (leave Blank)

Valid fields are:

2 alpha-character state code

Recommendation for FDUs: Menu is disabled if the country is not

United States.

Field 5 U.S. Service

A 10 M The branch of service normally associated with the base/post/camp/station.

“USA” = United States ARMY

“DOD” = Department of Defense

“USN” = United States NAVY

“USAF” = United States AIR FORCE

“USMC” = United States MARINE CORPS

“NA” = Non-U.S. Sites

Application Driven / http://www.itl.nist.gov/fipspubs/fip5-2.htm http://www.itl.nist.gov/fipspubs/fip5-2.htm

Version 5.5 FOR OFFICIAL USE ONLY - 27 -

Field 6 Site Representation A/N 40 O What the site represents.

Valid Values are:

“AAFES” =Army and Air Force Exchange Service

“ADF” =Australian Defence Forces Coalition “AWRDS” =Army War Reserve Deployment System

“CLASS I” =Subsistence (Food) “CLASS II” =Clothing, Individual Equipment, Tools, Admin.

Supplies

“CLASS III” =Petroleum, Oils, Lubricants “CLASS IV” =Construction Materials

“CLASS V” =Ammunition “CLASS VI” =Personal Demand Items

“CLASS VII” =Racks, Pylons, Tracked Vehicles, Etc.

“CLASS VIII” =Medical Materials

“CLASS IX” =Repair Parts

“CLASS X” =Material For Nonmilitary Programs “CMOS-AIR FORCE” =Cargo Movement Operation System-Air

Force “CMOS-ARMY” =Cargo Movement Operation System-Army

“CMOS-MARINES” =Cargo Movement Operation System-

Marines “CMOS-NAVY” =Cargo Movement Operation System-Navy

“COMMERCIAL” =Non Commodity generating activities “DLA” =Defense Logistics Agency

“DND” =Canadian Department of National Defence Coalition

“FLC” =Fleet Logistics Center

“FORSCOM” =United States Forces Command “FMS” =Foreign Military Sales

“GATES” =Global Air Transportation Execution System “GCSS-A” =Global Combat Support System-Army

“GSA” =General Services Administration

“MORTUARY AFFAIRS = Mortuary Affairs

Version 5.5 FOR OFFICIAL USE ONLY - 28 -

“NATO” =North Atlantic Treaty Organization (sites using NATO CMA Server)

“SAAS” = Standard Army Ammunition System “SARSS” = Standard Army Retail Supply System

“SAVINET” = SAVI Network “SDDC” = Surface Deployment and Distribution

Command

“TCAIMS” = Transportation Coordinators Automated Information for Movements System

“USAD” =United States Army Depot “USARNG” =Unites States Army National Guard

“UK” =United Kingdom Coalition “OTHER” =Other / Not in List

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 7 City A/N 40 M Mailing Address City Name or Closest City /Town. User input

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 8 Site Zip Code A/N 10 O The Zip code of the physical location of the station. 10 characters allows for hyphens and international zip codes.

Application Driven / User input

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 9 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 29 -

2.15 Registration “R3B” Record Format

The following table represents the registration format for R3B Record Format.

RF Tag Field

Number

Field Name Fixed Data Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R3B A/N 3 M Record Identifier

Field 2 Mobile Type

N 1 M Type of mobile station

“0” = not mobile. Device is fixed/permanent.

(default value)

“1” = OTHER-MOBILE

“2” = PDK

“3” = EEDSK

“4” = HHI

“5” = DK-RFID

Application Driven / User Input

Field 3 Sensor Indicator N 1 M Indicates if the station is collecting sensor data.

Note: The FDU software configuration drives the value of this field.

“0” = station is not collecting sensor data from tags

“1” = station is collecting sensor data from tags

Application Driven

Version 5.5 FOR OFFICIAL USE ONLY - 30 -

Field 4 Coalition Indicator N 1 M Indicates is station is configured to collect data from tags that belong to collation forces.

Note: The FDU software configuration drives the value of this field.

“0” = station is not configured to collect data from tags that belong to coalition forces

“1” = station is configured to collect data from tags that belong to coalition forces

Application Driven

Field 5 Tag Collection Mode N 1 O Indicates the type of tags it is collecting (i.e.

ANSI 256, ISO 18000-7 tags, or both). The default is DUAL mode.

“0” = LEGACY

“1” = ISO180007

“2” = DUAL (default mode)

Application Driven

Field 6 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 31 -

2.16 Registration “R3C” Record Format

The following table represents the registration format for R3C Record Format. Note: This record is used only in Sharing

Registration Information between Coalition Servers (Server to Server)

Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID R3C A/N 3 M Record Identifier

Field 2 Coalition Routing Code N 8 O Coalition ownership routing code which specifies the ownership of the device being registered. This field must be supplied when sharing coalition registration records.

For client apps, always leave fields

NULL.

Field 3 Coalition Public Code N 1 O Indicates if device being registered can be publicly distributed to coalition servers.

No user interaction.

Data is automatically extracted by client.

Version 5.5 FOR OFFICIAL USE ONLY - 32 -

2.17 Registration “RD” Record Format

The following table represents the registration format for RD Record Format. This applies to READ sites only and is used for “tag close” events.

RF Tag Field

Number

Field Name Fixed Data Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID RD A/N 2 O Record Identifier

Filler | 1 M Field Delimiter / ASCII Code for Pipe Character: 0x7c

Field 2 Device ID A/N 32

Serial number of the device assigned by the manufacturer or

Serial number of the Tag Docking

Station or Cable assigned by the manufacturer

Tag docking stations and Cables will precede the serial number with a “T”. For example, if the Serial Number equals “904110100”, then the Device ID will be “T904110100”.

Note: For the ISO implementation, users will no longer be required to enter the serial number. The client software will extract the computer’s MAC address and use it in lieu of a Tag Docking station/Cable serial number.

User Entry or Application Driven.

For smart devices, auto extract ID of the smart device.

A thru Z

0 thru 9

Up to 32 characters

Version 5.5 FOR OFFICIAL USE ONLY - 33 -

Field 3 DoDAAC A/N 6 M Department of Defense Activity Address Code used by tag closeouts and read sites. Each DODAAC consists of 6 uppercase letters.

User enters 6 characters in the text field.

If there is no DoDAAC, user enters the word

“DODAAC”.

Regular

Expression:[A-Z]{6}

Version 5.5 FOR OFFICIAL USE ONLY - 34 -

2.18 Registration “S” Record Format

The following table represents the registration format for S Record Format.

RF Tag Field

Number

Field Name Fixed Data Data Type

Max

Len

IR/DD

Required

Element

Comments

User Interaction with Read-Write Client

Field 1 RECORD_TYPE_ID S A 1 M Record Identifier

Field 2 Current Date N 6 M Current Date of the Interrogator Status

Format is DDHHMM

DD = Day of the Month (01-31)

HH = Hour of the Day

MM = Minute of the Hour

Field 3 Device ID A/N 32

Serial number of the device assigned by the manufacturer

Tag docking stations and Cables will precede the serial number with a “T”. For example, if the Serial Number equals “904110100”, then the Device ID will be “T904110100”.

Note: For the ISO implementation, users will no longer be required to enter the serial number. The client software will extract the computer’s MAC address and use it in lieu of a Tag Docking station/Cable serial number.

Version 5.5 FOR OFFICIAL USE ONLY - 35 -

Field 4 Status Code A/N 64 M Status of the interrogator. If the computer is communicating with the interrogator and everything is functioning properly, then a zero (0) is reported. If the computer is having communication problems with the interrogator then report the error code returned by the software. This is usually an

18 error.

Field 5 Start Flag A/N 1 M Report a ‘Y’. This field is no longer used.

Field 6 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the

Version 5.5 FOR OFFICIAL USE ONLY - 36 -

3 Registration Format 2.0 (Legacy - for reference only)

Registration Format 2.0 has been included in this document for reference only. The RF-ITV server will no longer support this format in the future. All future development of applications should be using Registration Format 3.0.

3.1 Overview

This previous standard was used to register a Write/Read Station to the RF-ITV System server.

It was only used to register or reregister the station with the RF-ITV System server.

A re-registration message should only be sent to the RF-ITV server whenever configuration or

POC information has changed.

NOTES:

Do not send a registration message every time a Write message is sent to the RF-ITV server.

Whenever a field is optional, DO NOT put spaces between the pipes (vertical bars).

Example: “R4|||FA|”

3.2 Registration Record Types

Record Type Description Mandatory/Optional Frequency

R1 Registration Record #1 Mandatory 1

R2 Registration Record #2 Mandatory 1

R3 Registration Record #3 Mandatory 1

R4 Registration Record #4 Mandatory 1

R5 Registration Record #5 Mandatory 1

R6 Registration Record #6 Mandatory 1

R7 Registration Record #7 Mandatory 1

R8 Registration Record #8 Mandatory 1

R9 Registration Record #9 Mandatory 1

RD DODAAC Association Record.

Optional 0 to Many

V Format Version Record Optional 1

Version 5.5 FOR OFFICIAL USE ONLY - 37 -

Example Field Data Unit Registration File:

R1|WAINWRIGHT|R|1|0706251802|75|

R2|JOHN.DOE|907 353 3075 935300007|DC|

R3|JOHN.DOE@US.ARMY.MIL|8B|

R4|01:00:00||8F|

R5|192.192.192.244|WAIN223A0RFIDR5|tips|D0|

R6|x86|Windows XP 5.1|49|

R7|TIPS-Read 3.7.1.52|||0E|

R8|43665|WAINWRIGHTR5|WAINWRIGHT AK UNIT MARSHALLING AREA|A8|

R9|43665|645025N|1473730W|||00:00:20|D1|

RD|43665||12|

Example Coalition Shared Registration File:

V|01.00|3D|

R1|AA5746|R||0705100654|95|

R2|||F8|

R3||7D|

R4|||FA|

R5||||77|

R6|||FC|

R7|CMS 1.0|||0B|

R8|51825|READER_51825|D26-WHSE KABUL|35|

R9|51825|343155N|0691119E||||KXM000||9F|

Version 5.5 FOR OFFICIAL USE ONLY - 38 -

3.3 Registration “R1” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R1 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 DEVICE LOCATION A/N 20 M The Device Location consists of two segments, the Location

Segment and the Military Suffix segment. This Device Location field is used by the RF-ITV server to sort and organize the RFID sites for reporting purposes.

Location Segment consists of fifteen characters form the name of the military installation or city location (for commercial or OCONUS sites). Do not include prefixes such as Fort, Camp, Navel Base, et cetera. (i.e., Fort

Bragg should be BRAGG). Additionally, spaces and/or periods between names will not be used. (i.e. San

Antonio should be SANANTONIO).

The Military Suffix Segment consists of five (5) characters describing the type of military installation where the device is located. For example, the following military installations, Air Force Base, Air Base, Arsenal, Air National Guard Base, Army Airfield and Navy Air

Station should be abbreviated as “AFB”, “AB”, “ARS”, “ANGB”, “AAF”, and “NAS”. For instance, Charleston AFB would be listed as “CHARLESTONAFB”.

Fixed Data | 1 M Field Delimiter

Field 3 STATION_FUNCTION A 1 M Function the Station is performing:

R = READ

W = Write

Fixed Data | 1 M Field Delimiter

Field 4 COMMUNICATION

MODE

A 1 M RF-ITV Server Communication Mode Code : Reference the following table

Version 5.5 FOR OFFICIAL USE ONLY - 39 -

Fixed Data | 1 M Field Delimiter

Field 5 REGISTRATION

DATE/TIME

N 10 M Date of registration: YYMMDDHHMI

Must be in GMT.

Fixed Data | 1 M Field Delimiter

Field 6 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Fixed Data LF 1 M LineFeed ASCII Character (Decimal 10)

3.3.1 RF-ITV Server Communication Mode Table

Communication Device Protocol Comm Mode Code

Standalone N/A A

LAN FTP L

HTTPS 1

SFTP 4

Modem via Satellite-InmarsatC Email S

Modem via Satellite-InmarsatM FTP T

HTTPS 3

Modem via Satellite-Iridium FTP 5

HTTPS 6

Modem via Cell Phone FTP 7

HTTPS 8

Modem via Unknown Device FTP Y

HTTPS Z

Version 5.5 FOR OFFICIAL USE ONLY - 40 -

3.4 Registration “R2” Record Format

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R2 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 POC NAME A/N 30 O Name of the Point Of Contact for the station

Fixed Data | 1 M Field Delimiter

Field 3 POC PHONE NUMBER A/N 30 O POC Phone number

Fixed Data | 1 M Field Delimiter

Field 4 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 41 -

3.5 Registration “R3” Record Format

RF Tag

Number

Field Name

Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R3 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 POC EMAIL ADDRESS A/N 50 O POC Email address

Fixed Data | 1 M Field Delimiter

Field 3 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 42 -

3.6 Registration “R4” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R4 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 SITE_UPLOAD_SCHEDU

LE

A/N 8 O Frequency that the station will upload data to the RF-ITV

National Server.

Format HH:MM:SS where "HH" is a 24 hour clock

NOTE: For registration of a Write Station, leave no space between the vertical bars

Fixed Data | 1 M Field Delimiter

Field 3 RF_RELAY_CHANNEL A/N 10 O Channel ID that the wireless network uses.

Fixed Data | 1 M Field Delimiter

Field 4 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 43 -

3.7 Registration “R5” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R5 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 STATION IP ADDRESS A/N 15 O Internet IP address assigned to the station computer.

Fixed Data | 1 M Field Delimiter

Field 3 STATION COMPUTER

NAME

A/N 30 O Usually assigned when the operating system is installed

Fixed Data | 1 M Field Delimiter

Field 4 USER LOGIN NAME A/N 10 O Operating system login name for Field Data Unit (Station).

Fixed Data | 1 M Field Delimiter

Field 5 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 44 -

3.8 Registration “R6” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R6 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 STATION COMPUTER

ARCHITECTURE

A/N 10 O Computer Processor Name/Type

Fixed Data | 1 M Field Delimiter

Field 3 STATION O/S NAME

AND VERSION

A/N 15 O Operating system name, version, and patch ID

(e.g. Win XP, W2000 SP2)

Fixed Data | 1 M Field Delimiter

Field 4 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 45 -

3.9 Registration “R7” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R7 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 ITV CLIENT SOFTWARE

VERSION AND NAME

A/N 30 M Name and version ID of the ITV Client Software installed on the station

Fixed Data | 1 M Field Delimiter

Field 3 TOTAL MEMORY N 12 O Total physical memory of the station in bytes

Fixed Data | 1 M Field Delimiter

Field 4 TOTAL MEMORY

AVAILABLE

N 12 O Available ("free") memory of the station in bytes

Fixed Data | 1 M Field Delimiter

Field 5 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 46 -

3.10 Registration “R8” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R8 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 RF_DEVICE _ID A/N 32 M Serial number of the Vendor Device ID. Tag docking stations will precede the serial number with a “T”. If the Tag Docking Station Serial Number equals “904110100”, then the device_id will be “T904110100”.

654 Docking Cables will be registered just like the Tag Docking

Stations. If the Serial Number equals 0255205040077, then the station will be registered as T0255205040077

Field 3 DEVICE NAME

(Alias: SITE NAME)

A/N 20 M The Device Name consists of two segments, the Location Segment and the Suffix segment. The Location Segment is similar to the Location Segment portion of the “Device

Location” element defined in Table 2.1.3..

Location Segment consists of sixteen (16) characters from the name of the military installation or city location. This information should contain a significant part of the Device Location information defined in

Table 2.1.3.

Suffix Segment consists of a maximum of four (4) characters. The first character is a Function Type designator consisting of a single letter, R or W. All devices will be designated as either a read or write station. The letter ‘R’ designates a read device and the letter ‘W’ will designate a write device. The next part of the Suffix segment is the Sequence Number. The Sequence Number is a number assigned to differentiate each device from another device with the

Version 5.5 FOR OFFICIAL USE ONLY - 47 -same Location Segment and Function Type (R or W).

The assigned Sequence Number should start with “1” and increment by “1” for each device at that location.

o If a site has several RF read interrogators, they may be registered using the last three digits of the device Number, as long as that number is not already utilized. (e.g.

BRAGGR123, BRAGGGR234, etc.)

o If the site has multiple write sites, they may be registered using the last three digits of the device number, as long as that number is not already utilized (e.g. LEJEUNEW234, LEJEUNEW156, etc.).

Fixed Data | 1 M Field Delimiter

Field 4 DEVICE DESCRIPTION

(Alias: SITE

DESCRIPTION)

A/N 64 M Long description of the RF Device being registered.

The following information must be included in the order described below.

1. Use the Device Location with the appropriate spaces included, prefixes removed, and suffixes abbreviated.

Fort Bragg would be BRAGG; Camp Lejeune would be

LEJEUNE; Charleston AFB would be CHARLESTON

AFB; and Camp Arifjan would be ARIFJAN, etc.

2. For US sites/locations, use the state abbreviation for the device location (e.g. NC for North Carolina, SC for

South Carolina). For non-US sites/locations use the country code for the device location (e.g. KS for Korea, GM for Germany and JA for Japan). Country codes are available on the RF-ITV National Server.

3. Use a free text description of the device’s function

(e.g. ALL AMERICAN CONVOY EXIT; ASP TRUCK

GATE; LOG CENTER ARV/DPT; PIER 8 EAST, PIER 8

BUILDING XXXX). This segment may include information as specified in other directives (e.g. 89Y

DOCK 5 SARSS to show the RIC, function and system type).

Version 5.5 FOR OFFICIAL USE ONLY - 48 -

4. System designator is mandatory and should be included as the last part of the description field.

Examples are SARSS, SAAS, TCAIMS, GATES, CMOS and AMS.

5. Use “EEDSK’ for temporary sites using an Early Entry

Deployment Support Kit.

6. Use “HHI” for sites using hand held interrogators to either read or write tag information that will be sent to the RF-ITV National Server.

7. Use “PDK” for temporary sites using a Portable Deployment Kit.

8. Use “MOBILE” for mobile devices (a device used in a mobile configuration and not an EEDSK, HHI, or PDK).

Fixed Data | 1 M Field Delimiter

Field 5 CHECK_SUM A/N 2 M Last two characters of a hex sum of all the characters in the record, including the field delimiters for the check-sum

Version 5.5 FOR OFFICIAL USE ONLY - 49 -

3.11 Registration “R9” Record Format

RF Tag

Field Number

Field Name Fixed Data

Data Type

Max

Len

IR/DD

Required Element

Comments

Field 1 RECORD_TYPE_ID R9 A/N 2 M Record Identifier

Fixed Data | 1 M Field Delimiter

Field 2 RF_DEVICE _ID…