2006 Euro Simulation Interoperability Workshop

1
2006 Euro SimulationInteroperability Workshop

• Link 11/11B Product Development Group (Link
  11/11B PDG)
• Joe Sorroche

2
Link 11/11B PDG Euro 06 SIW Agenda

• Tuesday Afternoon, Room 201 1400 - 1730
• 1400 1415 Introduction, Opening Comments (Joe
  Sorroche)
• 1915 1445 Link 11/11B
• Review Meeting Minutes from Spring SIW 2006
• Goals
•   Present Draft Schedule
• 1445 1530 TADIL TALES II Link 11/11B
  Discussion
• 1530 1600 Break for Tea
• 1600 1700 TADIL TALES II Link 11/11B
  Discussion
• 1700 1730 Review Action Items
• 1730 Adjourn

3
Introduction, Opening Comments

• Welcome to Link 11/11B PDG
• Link 11/11B PDG Officers
• Chair Mr. Joe Sorroche
• Vice Chair Mr. Joe Zehnle
• Secretary Dr. Rob Byers
• TAD Mr. Mark McCall
• Drafting Group
• Number of Drafting Groups
• DIS Group, HLA Group, General Requirements Group
• Editor Dr. Rob Byers
• Assistant Editor - Mary Christopher
• Assistant Editor Graham Shanks

4
Meeting Minutes Review

• Spring 2006 SIW Link 11/11B Meeting Minutes
  Review
• Discussions included
• How to model Link 11/11B
• Levels of Fidelity 2
• Legacy Data Link Is it worth the effort? YES!
• TADIL TALES II/IIB Paper/Presentation
• Who attended presentation or read paper?
• Thoughts/Comments

5
Link 11/11B Goals

• Create SISO Standard using Link 16 SISO Standard
  as guide
• DIS and HLA technical solution
• HLA BOM similar to Link 16 BOM
• Provide implementation and usage information
• Provide materials to understand usage of the
  standard
• Provide guidance for eventual incorporation into
  IEEE standards
• Essentially follow Link 16 Development Plan

6
Link 11/11B Draft Schedule

• Spring 2006 SIW
• Presented TADIL TALES II/IIB, First Draft
• Discussed, modified, and worked on DIS and HLA
  templates
• Euro 2006 SIW
• Present TADIL TALES II/IIB, Second Draft
• Continue TADIL TALES II/IIB Modifications
• Solicit input from European community
• Fall 2006 SIW
• Present TADIL TALES II/IIB, Third Draft
• Continue TADIL TALES II/IIB Modifications
• Schedule Ongoing Telecons as required

7
General Requirements

• All Link 11/11B messages shall be bit encoded in
  accordance with Mil-Std-6011C
• The first 4 bits of the Link 11/11B tactical
  message contain the message label. The rest of
  the bits are defined by size and description
  fields specific to the message, for a total of 48
  bits of tactical information
• Link 11 formatted message consists of two 30-bit
  frames
• Each frame contains 24 bits of data along with 6
  Hamming Error Detection and Correction (EDAC)
  bits
• Link 11B formatted message consists of 72 bits,
  containing eight groups of 9 bits each.
• The start and check groups use 18 bits while each
  of the six data groups uses 1 bit each to precede
  the 8 information bits

8
General Requirements

• All Transmission modulation parameters shall be
  filled in
• Systems shall transmit data upon receipt of a
  roll call message from the NCS. During the
  remainder of the time, the PU shall receive
  reports from other members
• The types of transmissions that shall occur
  during Roll Call are
• NCS Call Up (Interrogation)
• Picket Reply
• NCS report

9
General Requirements

• The Short Broadcast shall be a single data
  transmission to all members of the net by a
  station that may be acting as a Picket Unit or
  NCS
• The Broadcast net mode shall consist of a
  continuous series of Short Broadcast messages
  contained in one Signal PDU
• Need to set message size and count limits
• To simulate the two frames of dead time required,
  each Signal PDU shall
• Contain the series of Short Broadcast messages,
  wait for a period of two updates, then shall
  transmit another Signal PDU containing a series
  of Short Broadcast messages.
• For HLA, the message transmission shall pause for
  a time that is defined as dead time

10
General Requirements

• Transmitter/Signal PDU pairs shall be sent for
• Roll Call
• Short Broadcast messages
• For Broadcast Messages, Transmitter PDUs shall be
  required with the first Broadcast Signal PDU
• Subsequent Transmitter PDUs from the same PU are
  not required, until the last Signal PDU is sent,
  then a Transmitter PDU shall be sent indicating
  transmission end
• All systems shall have some representation of
  periodic clock time

11
Link 11/11B Transmitter PDU

• Complies with the IEEE 1278.1 1995 standard
• Adds 5 modulation fields for Link 11/11B specific
  parameters
• Shall be sent at the beginning of a transmission,
  followed by a signal PDU, as per 1278.11995
• Shall include all of the standard information
  regarding transmission power, antenna pattern,
  antenna location
• Radio Entity Type shall be set to 22 (Proposed
  Enumeration) for Link 11/11B Radio

12
Link 11/11B Transmitter PDU

• The Frequency shall be set to 4 MHz for Link 11,
  and 8 KHz for Link 11B
• The Transmit Frequency Bandwidth shall be set to
  28 KHz for Link 11 HF, 175KHz for Link 11 UHF
• For Link 11B, the frequency bandwidth shall be
  set to 16 KHz
• The Modulation parameter fields shall be set to
• 1 (Amplitude) for Major Modulation
• 11 (proposed) for Dual Side Band, Suppressed
  Carrier
• 9 (proposed) for system

13
Link 11/11B Transmitter PDU

• The Crypto System field shall be a 16 bit
  enumeration, yet to be defined by the Link 11/11B
  PDG
• The Crypto Key ID field shall be a 16 bit
  unsigned integer, yet to be defined by the Link
  11/11B PDG
• Length of Modulation parameters shall be set to 5.

14
Link 11/11B Transmitter PDU

• For the Link 11/11B Transmitter PDU, five
  modulation fields have been added to the
  Transmitter PDU
• Record Type For Link 11, set 1, For Link 11B,
  set to 2
• Fidelity Level Level 0 for message exchange
  only, Level 1 to model polling, Link 11/11B
  network
• Link 11/11B Terminal Mode No Statement 0 For
  NCS 1 For Participant Unit - 2
• Data Terminal Set Indicator
• Mode of Operation

15
Link 11/11B Transmitter PDU

• Transmitter PDU Modulation Fields (cont)
• Data Terminal Set Indicator Shall indicate the
  message state of the Link 11/11B Terminal
• 0 No Statement
• 1- Transmit
• 2 Receive
• 3 - Net Busy
• 4 - Transmit Data Error
• 5 - Receive Data Error
• 6 - Code Error
• 7 - Synchronization Complete

16
Link 11/11B Transmitter PDU

• Transmitter PDU Modulation Fields (cont)
• Mode of Operation
• 0 No Statement
• 1 - Net Sync
• 2 Net Test
• 3 Roll Call
• 4 Short Broadcast
• 5 - Broadcast

17
Link 11/11B Transmitter PDU
18
Link 11/11B Signal PDU

• Complies with the IEEE 1278.1 1995 standard
• The variable length data field is specific to the
  use of Link 11/11B emulation.
• Each signal PDU contains data for one PU.
• Data of one message type identifier per PDU
• Encoding Scheme
• Bits 0-13 number of Link 11/11B messages
• Bits 14-15 1 (Raw binary data)
• TDL Type 8 for Link 11, 4 for Link 11 B

19
Link 11/11B Signal PDU Specific Fields

• Message Sub Type This field shall identify the
  following sub message types 0Intermediate,
  1Interrogate Message, 2Start Code, 3Picket
  Stop Code, 4Control Stop Code.
• All Fs in this field shall indicate wild card
  statement, for fidelity level zero
• Picket Number Participating Unit Source Number
  of any Link 11/11B unit in any mode of operation.
  
• For Interrogate Messages, the PU Number shall be
  the identification of the unit being polled
• For all other Sub-Types, the PU Number shall
  identify the originating PU

20
Link 11/11B Signal PDU Specific Fields

• Word Count Number of 16 bit words of Message
  Data in increments of 4
• Interrogate Messages contain no M-Series messages
  so this value shall be set to zero
• For Fidelity Level zero, all Fs shall be filled
  into this field indicating a wild card value

21
Link 11/11B Signal PDU Specific Fields

• Sequence Number Counter that each NCS/PKT DTS
  increments for every Signal PDU message it
  generates on the DIS WAN
• This shall be used at the NTDS application to
  determine transmit/receive of Link-11 messages
  and monitoring of any missing data
• In the event of missing data the operator would
  be notified, but the current data shall be
  delivered as usual
• Upon reaching a value of 255 the counter shall
  roll over back to zero on the next message
  transmitted
• For Fidelity Level zero, all Fs shall be filled
  into this field indicating a wild card value.

22
Link 11/11B Signal PDU Specific Fields

• Message Type Identifier Indicates message as
• Net Test
• Roll Call
• Picket Reply
• Short Broadcast
• Broadcast
• 24 bits of padding

23
Link 11/11B Signal PDU Specific Fields

• Net Cycle Time 64 bit field that contains the
  time required for the NCS to complete a polling
  sequence of all PUs
• The integer part is in the first 32 bits and the
  fraction part in the last 32 bits
• For Fidelity Level 1, all Fs (4294967295) shall
  be entered into this field, indicating a wildcard
  (No Statement).
• Message Data Link 11 11B contain 48 bits of
  tactical data. Link 11 is two 30 bit frames and
  Link 11B is a 72 bit frame. Messages shall be
  read in as 32 bit arrays
• Padding (if needed) to increase total PDU size to
  a multiple of 32 bits

24
Link 11/11B Signal PDU
25
Link 11/11B Signal PDU
26
Link 11/11B Signal PDU
Link 11 Message Format
Link 11 B Message Format
27
Link 11/11B HLA BOM

• The Link 11/11B BOM is designed for integration
  within the Federation Object Model (FOM) of the
  HLA federation
• The Link 11/11B BOM assumes that
• The parent FOM contains all current DIS
  Transmitter PDU PDU records (not those associated
  with the PDU header) in accordance with IEEE
  1278.1a as part of its object class hierarchy
• The parent FOM contains all current DIS Signal
  PDU PDU records (not those associated with the
  PDU header) in accordance with IEEE 1278.1a as
  part of its interaction class hierarchy

28
Object Class Data Approach

• The Link 11/11B BOM first draft, defines no new
  object classes
• The BOM defines a single complex data type
  (Link11TransmitterStruct) that corresponds to the
  modulation parameters in the DIS Transmitter PDU
• An attribute of this complex data type should be
  added to the object class in the parent FOM
  corresponding to the DIS Transmitter PDU
• Modulation parameters of the Transmitter PDU
  should map to the fields of the
  Link11TransmitterStruct complex data type
  attribute

29
Object Class Data Approach

• Parent object class fields should also be
  modified such that they refer to the
  corresponding Transmitter PDU fields
• For a RPR FOM implementation, it is suggested
  that an attribute of the Link11TransmitterStruct
  complex data type should be added to the
  RadioTransmitter object class

30
Interaction Class Data Approach

• The Link 11/11B interactions are added to the
  family of interactions that, in which, a
  hierarchy of the BOMs base class, the
  TDLBinaryRadioSignal interaction
• TDLBinaryRadioSignal is an empty class, and
  contains no parameters, and is neither
  publishable nor subscribable

31
Questions?
32
Backup Slides

• kenneth.kingston
• Both Link 11 11B contain 48 bits of tactical
  data. Link 11 is formatted as two 30 bit frames
  and Link 11B is a 72 bit frame.
• Link 11 Additional field data
• 1) Frame data rate fast (75 per sec) or slow
  (45.45 per sec)
• 2) Extended timeout value Length of extended
  time as set on the DTS. For normal operation with
  no extended timeout a PU has to respond within
  93.31mS (fast mode) or 154mS (slow mode). So for
  testing on a distributed IP network we use
  extended timeouts.
• For Link 11B Comm rate 1200bps or 2400bps

kenneth.kingston Short broadcast - manually
initiated (DTS is required) Same with Broadcast
net. JITC never tests these modes. Normal mode is
Roll Call.