testing syndicate (tdlits) -...

Jan 05

TACTICAL DATA LINK INTEROPERABILITYTACTICAL DATA LINK INTEROPERABILITY

NATO INTEROPERABILITY NATO INTEROPERABILITY REQUIREMENTS, TESTING AND SUPPORT REQUIREMENTS, TESTING AND SUPPORT WORKING GROUP (IRTS WG)WORKING GROUP (IRTS WG)

TESTING SYNDICATE TESTING SYNDICATE (TDLITS)(TDLITS)

NATO/EAPC UNCLASSIFIEDReleasable for Internet Transmission

Jan 05

NATO Tactical Data LinkNATO Tactical Data LinkInteroperability TestingInteroperability Testing

(NTDLIOTs)(NTDLIOTs)

Issue 1 – 28 Jan 05Issue 1 – 28 Jan 05

Prepared for the IDLS UK Chapter Meeting - 1 February 2005Prepared for the IDLS UK Chapter Meeting - 1 February 2005

by the TDLITS Secretary, Jon R Milloby the TDLITS Secretary, Jon R MilloIA5Con4IA5Con4

Jan 05

ContentsContents

■ Through Life Interoperability Planning (TULIP)■ STANAG 5602■ NATO TDL IO Testing Syndicate:

■ History■ Members■ NATO TDL IO Tests■ Testing Cycle■ Results

■ UK Link Interoperability Network (LION)■ Way Ahead:

■ Protocols (TCP/IP)■ Bearer (CFBLNet?)

■ Lessons Learned

Jan 05

Tactical Data LinkTactical Data LinkThrough Life Interoperability Planning Through Life Interoperability Planning

(TULIP) (TULIP) andand

The Standard Interface for The Standard Interface for Multiple Platform Link Evaluation Multiple Platform Link Evaluation

(SIMPLE) - STANAG 5602(SIMPLE) - STANAG 5602

Jan 05

IntroductionIntroduction

■ To determine TDL Interoperability (IO) it is necessary

to carry out IO TestingIO Testing

■ This can be undertaken at 3 levels

■ Through paper analysis

■ Through interconnection of platform rigs or simulatorsThrough interconnection of platform rigs or simulators

■ Through live trials

Jan 05

TDL IO Testing within TDL TULIPTDL IO Testing within TDL TULIP

National TDL StandardsDocumentation

InteroperabilityRequirements

DTDL- IRS Part I Multi-Link

Single Link(L11, L16, L22)

SID

IOM

IOAs

IOM Database

Platform Implementation Difference Document

Platform IO Requirement

Platform Operational Specification

General Health Check

Targeted Testing

Multi-Platform IO Trials

Implementation

Test Indices

Integration Testing

Problem Reports

Trials

Exercises

Operations

FEEDBACK

FEEDBACK

FEEDBACK

FEEDBACK

National & International

Technical Review

Network Designers

Front Line

Operational

International

Operational Planners

E-3D UKAEW

UKFighter etc

IDF/IORNo:

1.1.1

PIR/IER Matrix

Specification

Platform Implementation

IO Testing & Assessment

Jan 05

TDL IO Testing within the CADMID CycleTDL IO Testing within the CADMID Cycle

Concept

Initial Gate

Assessment Demonstration

Main Gate

In ServiceManufacture

In Service DateContract Let

IO Evaluation

PIR/IER

PIDD/PRDD

P-SLIRS/PRS

IOM Entry

TDL Stds Changes

DCP/DLCP Platform Impact Assessment

PRDD/PIDD Maintenance

Testing/Operations

Problems

USERS!Acquisition Staff

Capability Manager & Requirements Manager

Services Users

Disposal

Integration

Development

In-Service

Modification

Operational

Requiremen

t

ProjectDefinition

In-Service Use

Accep

tance

Standards,IOAs & IOEs

Jan 05

SIMPLE Development (1)SIMPLE Development (1)

■ In order to conduct TDL IO testing by interconnecting

ground rigs of all types (e.g. simulation, integration

facilities etc.), a common standard was required

■ STANAG 5602 was developed to:■ Define a single interface standard to support TDL IO testing by

supporting the interconnection of rigs of all kinds

■ Utilise existing commercial and international standards to

minimise life cycle costs

■ Provide the connection of SIMPLE compliant rigs to support other

activities, such as training

Jan 05


■ Technical approach agreed at the (then) Ad Hoc Working Group (AHWG) on NATO Common Interoperability Standards (NCIS) Testing in Feb 96

■ Decision was to:■ Not create a totally new protocol■ Utilise the US Navy SPAWAR GATEWAY protocols with minor

modifications and additions■ Use IEEE Distributed Interactive Simulation (DIS)

■ Issue 1 of the Standard technical approval granted in Feb 97 and the SIMPLE Project Team established under the (then) NATO Interoperability Environment Testing Working Group (NIETWG)

Jan 05


■ Edition 1:■ Ratified & Promulgated by Director MAS/NAS on 8 May 01

■ Edition 1 Amendment 1:■ Ratified and Promulgated by Director MAS/NAS on 21 Mar 02

■ Edition 2:■ Currently awaiting Ratification

■ Edition 2 Amendment 1:■ The STANAG will be amended when there are 10 or more

SCPs agreed to Section F of the Supplement (early 05)■ Draft Edition 3:

■ Specifies the restructuring of the STANAG to incorporate TCP/IP (Mandatory) and UDP/IP (Optional) protocols for a Wide Area Network (WAN)

■ NATO Effective Date (NED) – 1 Sep 06

Jan 05

STANAG 5602 LimitationsSTANAG 5602 Limitations

■ STANAG 5602 has the following limitations:■ Time of Arrival (TOA) information is not transferred over WAN■ MIDS/JTIDS Round Trip Timing (RTT) cannot be supported:

■ Data is available to allow SIMPLE Nodes to derive this information

■ Messages from a real terminal connected to the WAN will not be retransmitted to other rigs in the same timeslots:

■ Although other characteristics such as Network Participation Group (NPG) for MIDS/JTIDS are retained

■ Receipt Compliance (R/C) processing is dependant upon the level of Terminal emulation implemented by the SIMPLE converter

■ Terminal related functions are not supported for IO Testing, e.g.:■ Relative Navigation■ Time Slot Management, etc.

Jan 05

The NATO Tactical Data Link The NATO Tactical Data Link Interoperability Testing Syndicate Interoperability Testing Syndicate

(TDLITS)(TDLITS)

Jan 05

TDLITS OverviewTDLITS Overview

■ The NATO Tactical Data Link Interoperability Testing

Syndicate (TDLITS) has been conducting TDL IO

Testing since Apr 99

■ The TDLITS:

■ Is now a Syndicate of the Interoperability Requirements,

Testing and Support Working Group (IRTS WG) - SC/2-WG/5

■ Is responsible for maintaining the common standard to enable

the interconnection of TDL integration rigs and simulators -

SIMPLE STANAG 5602

■ Conducts major NATO-wide TDL IO Tests twice a year

Jan 05

TDLITS MembersTDLITS Members

■ The TDLITS currently has representatives from the following NATO nations and organisations:

■ France■ Germany■ Hungary■ Iceland■ Italy■ NATO:

■ NAEW&C FC and Component■ NAPMA■ NC3A■ NPC

■ Norway■ Spain■ UK (also provides Chairman and Secretary)■ US

Jan 05

NATO TDL IO TestsNATO TDL IO Tests

■ Major NTDLIOTs are conducted biannually:■ Normally in Apr and Oct

■ Each NTDLIOT:■ Lasts 5 days■ Involves around 25 participating platforms (some Passive)■ May be Single Link or Multi Link with Data Forwading

■ Various organisations take on individual responsibilities:■ US Joint Interoperability Test Command (JITC) produces Test

Serials and acts as Test Director■ NC3A, the Hague, acts as European Voice Hub

Jan 05

NATO TDL IO Tests Conducted to DateNATO TDL IO Tests Conducted to Date

■ 11 NTDLIOTs successfully conducted so far:■ Apr 99 Apr 99 SIMPLE Demonstration and IO Test■ Apr 00 Apr 00 MILLO■ Oct 00 Oct 00 DARIO■ Apr 01 Apr 01 FEINGOLD■ Oct 01 Oct 01 BOUWMANS■ Apr 02 Apr 02 CHERNY■ Nov 02 Nov 02 HEWIG■ May 03 May 03 PAPOT■ Nov 03Nov 03 ATCHISON■ Apr 04 Apr 04 UPTON■ Nov 04Nov 04 FRANK HAY

■ Future NTDLIOTs planned for:■ Apr 05Apr 05 RENNER ■ Oct 05Oct 05 ANDERSON

Jan 05

NATO TDL Testing CycleNATO TDL Testing Cycle

IO ISSUES

(IOIs)

IO A

SSES

SMEN

TS (I

OAs)

IN T

HE IO

MATR

IX (I

OM)

PLATFORM FIXES SOFTWARE

TEST

PLANNING

MEETING

NTDLIOT

CONDUCTED

NTDLIOT REVIEW MEETING(SNAPE)

1.NTDLIOTs are

normally held in Apr and Oct each year

2. The SNAPE analyses the results of each NTDLIOT,

validates new IOIs and closes IOIs which have been

‘fixed’

3. Where necessary, an IOA is raised to

inform the Operational Community of the

effect of the underlying IOI

4. Platform corrects underlying problem in

Host or SIMPLE Converter Software

5. Platform informs Planning Meeting that the

IOI is fixed and ready for re-test

Operational Operational

CommunityCommunity

6. IOI is re-tested and, if fixed, closed

along with any associated

IOA

Jan 05

NATO TDL IO Test ResultsNATO TDL IO Test Results

■ Bottom Line:■ Platforms participate in NTDLIOTs■ IO disconnects are discovered between participating platforms■ Analysis pinpoints the causes of the disconnects■ IOIs and IOAs are used to document these■ Platforms agree to take remedial action■ Once fixed, the disconnects are re-tested■ If successful, applicable IOIs and IOAs are closed

■ Overall Platform TDL IO is improved■ NTDLIOTs bring Added Value to the entire TDL

Community, including Planners, Operators and Technicians■ NTDLIOT Results (post NTDLIOT 04-02):

■ 429 IOIs discovered during 11 NTDLIOTs■ 74 NATO IOAs raised

Jan 05

Some Actual Results from NTDLIOTs (1)Some Actual Results from NTDLIOTs (1)

❴ IOI 0204J:■ ‘Platform X did not implement the J12.4 Control message to

terminate control of a controlled unit’■ Raised from the Oct 02 NTDLIOT■ Associated IOA raised – NA019■ Platform X subsequently changed implementation■ Re-tested in May 03 NTDLIOT – fixed■ IOI 0204J and IOA NA019 both closed at the Apr 04 SNAPE

❵ IOI 0286J:■ ‘Platform Y did not implement LOCK ON Value in J12.6 Target

Sorting messages. All messages received with this value were discarded’

■ Raised from the Apr 02 NTDLIOT■ Associated IOA raised – NA039■ Platform Y subsequently changed implementation■ Re-tested in the May 04 NTDLIOT – fixed■ IOI 0286J and IOA NA039 both closed at the Apr 04 SNAPE

Jan 05

Further Actual Results from NTDLIOTs (2)Further Actual Results from NTDLIOTs (2)

� IOI 0157J:■ ‘Platform Z was unable to transmit FORCE TELL or EMERGENCY

on own PPLI’ (also applied to 3 other platforms)■ Raised from the Oct 00 NTDLIOT■ Associated IOA raised – NA031 – against 3 other similar types■ Platform Z subsequently changed implementation■ Re-tested in Nov 03 NTDLIOT – fixed in Platform Z■ IOI 0157J closed at the Nov 03 SNAPE and NA031 amended to

remove Platform Z� IOI 0376J:

■ ‘C2 Platform A does not set ENV/CAT in a J7.6 Filter Implementation Request’

■ Raised from the Nov 03 NTDLIOT■ Associated IOA raised – NA069■ Platform A has yet to change implementation■ IOI 0376J and IOA NA069 remain open

Jan 05

Example NTDLIOT - Apr 04 ObjectivesExample NTDLIOT - Apr 04 Objectives

■ To test IO Issues from previous NTDLIOTs■ To evaluate how each system implements the Link 11/16

messages in the following areas:■ Air, Surface, and Subsurface Tracks■ Identification Conflict/Resolution■ IFF/SIF ■ Data Update Requests■ Special Codes

■ Control of F-3 fighters, including:■ Achievement full digital control■ Assignment of missions■ Receipt of fighter sensor data/fighter engagement status

information ■ Exchange of Land (Ground) data ■ Free Text messages■ J13.2 Specific Types

Jan 05

Example NTDLIOT - Apr 04 ParticipantsExample NTDLIOT - Apr 04 Participants

Link 16

Link 11

CV/LHD

E-3D

F-3 Tornado

E-3A

E-3F

JIMES

SPAWAR - SD

DLS

F-3 SIM

LION CSF

C2M SIMCDG

NPC

GBADOC

F123

JSTARS

NC3A

Active

Passive

Monitor only

Jan 05

Current UK LION PlatformsCurrent UK LION Platforms

E3-D Rig (RAF Waddington)

RIU RIU F3 (Frimley)

LBTS (Portsdown) – T42/CVS

RIU

SKASaC (Crawley)

InternationalConnection

SpareConnections

Central Simulation Facility

RIU = Rig Interface Unit

L11/16

UK Tanker RIU

L11/16

L16

L16

L16 RIU

Jan 05

UK LION Future PlatformsUK LION Future Platforms

■ Eurofighter Typhoon■ Nimrod MRA4■ ASTOR■ TJF■ ASTUTE■ T45■ Current UK policy mandates that future UK platform

rigs must be SIMPLE compliant■ LION also has growth potential to accommodate

additional data links e.g. Link 22, IDM, SDL etc.

Jan 05

Types of UK LION TestsTypes of UK LION Tests

■ UK Link Interoperability Network (LION)■ 3 Types of LION Tests:

■ System Wide Checks:■ Multiple UK rigs establishing general IO, providing a

system health check opportunity to build confidence in IO of new/modified platforms

■ Focused Tests:■ Selected rigs investigating/isolating specific IO Issues■ Ties in closely with live and paper based testing (IOEs)■ Responding to operational (real world) feedback, JPEG

reports and other problem tracking mechanisms such as IOAs from the IOM

■ International Tests:■ NATO-wide testing■ Nationally driven discrete testing (e.g. 1 vs. 2 or 1 vs. 3)

Jan 05

Joint & Multi-National Interoperability Assurance NetworkJoint & Multi-National Interoperability Assurance Network

Other DFTSservices BT Cellstream

RAFRAFWaddingtonWaddingtonLSRCLSRC

LBTSLBTS

AEGIS TrialDe-risking

Dec 03Successful

Connects to GD Oakdale

E3

Nimrod

LION

T23 SIF

T42 SIF

T45 MISC

CVF ?

UK CEC

RNCSS

LION

ASTOR

RAFCCIS

LSRC - RAF

Waddington Trial

De-risking

Connects to Strategic Ranges

LBTS-LSRC TrialDe-risking

May 04Successful

Full Network Integration

TrialDe-risking

GBADISTAR ?

AWC

ARTDARTD

Connects to US

Connects to NC3A

Connects to NITEWorks / Industry

DFTS/BT FHB

Service

JMNIAN

DCSA Access Node

Multiservice Access Switch

ISDN2/TacISD

N IP

VoiceVideoData

CATAPAN

BT Access Node

IP

Voice

Video

Data

CATAPAN

DCSA Access Node

ISDN2/TacISDN

IP

VoiceVideoData

CATAPAN

DCSA Access Node


ISDN2/TacISDN

IP

VoiceVideoData

CATAPAN

DCSA Network Management

Node

CFBLNet

DII

JOCS ?

JSF

X21/V11


Multiservice Access SwitchGATE

CORMORANT

BISAsBOWMAN

Ptarmigan

CIP

FALCON

SKYNET 5

SKYNET 4 Emulator

CLANSMAN

LBTSLBTS

Jan 05

Way AheadWay Ahead

■ STANAG 5602 Edition 3 has been restructured to

incorporate TCP/IP protocols for a Wide Area Network

■ The TDLITS:■ Plans to start using TCP/IP (instead of Bi-synchronous)

protocols w.e.f. NTDLIOT 06-02

■ Is considering using the Combined Federated Battle Lab

Network (CFBLNet) as the bearer for future NTDLIOTs (instead

of the current Point to Point ISDN connections)

■ Is currently developing a migration plan for the above 2 steps

Jan 05

Combined Federated Battle Lab Network (1) Combined Federated Battle Lab Network (1)

■ The CFBLNet was established by the NATO

Consultation, Command and Control Board (NC3B) in

2001:■ No single nation owns the CFBLNet infrastructure■ Each member nation is responsible for the funding and

maintenance of its own systems, which hook into the backbone

at a defined Point-of-Presence (POP)■ Each country is responsible for funding its own experiments■ The Advanced Information Technology Services-Joint Program

Office (AITS-JPO) in Arlington, Virginia (US) maintains day-to-

day control of the network and co-ordinates activities on the

network

Jan 05

384KBISDN

(Backup)10MB

15MB

45MB

10MB

2 MB

2 MB

1MB

5MB

--

34MB

1.5 MB

6 MB variableCTDC

Tunneys Pasture

CAPortsdown West

UKIT Zentrum der

Bundeswehr Euskirchen

GE

Centre d'Electronique de l'Armement (CELAR)

Bruz

FR

NDLO/CISKolsås

NO

JISA WellingtonNZ

AITS-JPOArlington, VA

US

DSTO FernhillCanberra

AU

NC3AHague, NL

NATO

ACTNorfolk, VA

NATO

RAF Molesworth, UK

Wahiawa, US

Primary JWIDLillehammer, NO

NATO

2 MB

EUCOMStuttgart, GE

US

? MB

USFKYongsan, Korea

US

? MB

6 MB

At 3 May, 2004

Combined Federated Battle Lab Network (2)Combined Federated Battle Lab Network (2)

Jan 05

NATO TDL IO TestsNATO TDL IO Tests - Lessons Learned - Lessons Learned

■ Connecting Rigs together:■ Achives a cost effective solution

■ Can de-risk subsequent live trials, exercises and operations

■ NATO nations and organisations are using NTDLIOTs as the primary method of TDL IO Testing

■ NTDLIOTs are used to:■ Conduct testing which would otherwise not be possible, by any

other means, without assembling difficult-to-secure international assets

■ Identify and correct any TDL IO Issues

■ Address operational IOIs

■ Improve overall TDL IO

Jan 05

TDLITSTDLITS

Questions?Questions?

testing syndicate (tdlits) -...

Documents