tdl test gen.pptx

Overview Network Description Document • An NDD contains: – Network Name – Introduction/Assumptions – Network Description • • • • • Platform Functional Description Connectivity matrix Timeline COMSEC cross reference table Unit pulse density calculations – Network Ops Management – Appendices • Pl...

Overview Network Description Document • An NDD contains: – Network Name – Introduction/Assumptions – Network Description • • • • • Platform Functional Description Connectivity matrix Timeline COMSEC cross reference table Unit pulse density calculations – Network Ops Management – Appendices • Platform Loads Section 3 Platform Functional Description • Lists each platform type that time slots have been allocated for in the network • Specifies quantity of each platform • Details the NPG participation for each platform type (Tx or Rx) • Identifies designed track capacity for each surveillance platform • Does not assume track updates Section 4 Network Operations Management • Guidance required to properly employ and operate the Link 16 network • Supplements JICO duties prescribed by CJCSM 3115.01 (JDN Ops) and CJCSM 6120.01 (JMTOP) Platform ID • Platform ID is a functional description of what the unit is, its role, or capability ID Sets • ID Set refers to a platforms ID in an OPTASK link message or a system that uses load files. Platform ID vs ID Set • It is important to always refer to the NDD when determining what load file to choose based on the Platform ID or ID Set. • They may look similar, but it can create confusion and will result in using the wrong load file. Connectivity Matrix • The connectivity matrix summarizes unit participation • Programming and execution • Access methodology • Dedicated, Contention, TSR • Multi-net, Stacked net, Slot re-use Access Terminology • Dedicated • A hard transmit assignment • Unit will transmit if it has data to send • Default is receive • Contention Pools • A probabilistic transmit assignment • Units transmit in a few timeslots within a larger pool • Number of timeslots used is determined by the Contention Access Code Access Terminology • TSR Pools • A pseudo-random transmit assignment • Units trade some of the timeslots in their assignments • Number of timeslots traded is based upon aggregate demand • On the fly re-programming without a new IDL Surveillance Option Pools • Requestors of a network design may require the flexibility to reallocate time slots. • Option pools are a set number of time slots for various NPGs that can be divided amongst multiple units. Surveillance Option Pools • Requestors of a network design may require the flexibility to reallocate time slots. • Option pools are a set number of time slots for various NPGs that can be divided amongst multiple units. Access Techniques • Stacked net • Within the same timeslot, multiple units performing the same function on different hopping patterns • Net numbers are operator selectable • Multi-net • Within the same timeslot, multiple units performing different functions on different hopping patterns • Net numbers are programmed in the load • May also be accomplished by programming a different TSEC variable Access Techniques (Continued) • Slot reuse • Within the same timeslot, multiple units transmitting on the same hopping pattern • Dedicated access, same net number, same TSEC variable • Geographic separation • Overlays • A hybrid of stacked and multi-net • Allows multiple platforms with different programming requirements to use the same slot block assignment • Allows efficient allocation of timeslots Platform Participation More Specifically • Types of assignments • T indicates transmit assignment • Terminal defaults to receive if it has nothing to transmit • R indicates receive assignment • T/R indicates transmit and receive • Dedicated assignment – typically used for C2 PPLI • More than one unit has received allocations in the same slot group, each unit has their own coordinated transmit assignment • Each unit will receive when not transmitting Matrix • TheConnectivity Connectivity Matrix depicts all the timeslots • However, each JTIDS/MIDS terminal executes its own timeslots • All timeslots have: • • • • • • • Index number Timeslot type Message category Access type Net number TSEC/MSEC CVLLs Packing limit Summary B-0 T NPG Access D Net # 0 TSEC CVLL MSEC CVLL Packing Limit P2DP 7 1 Surveillance Option Pools • Platforms share the same option pool number Surveillance Option Pools • Each platform must have a different sequence number. JREAP B • JREAP B is a secure synchronous or asynchronous point-to-point serial data interface used to exchange information in a fullduplex data transparent mode (1 phone to another) DIV TOC JAOC vIPr vIPr JREAP B Protocols • Full Duplex Synchronous Point-to-Point (RS-422) • Full Duplex Asynchronous Point-to-Point (RS-232) JREAP JREAP is a generalized application protocol enabling tactical data to be transmitted over digital media and networks not originally designed for tactical data exchange. JREAP is designed to provide the following capabilities: 1. extending the range-limited tactical networks to beyond LOS 2. reducing the loading on stressed networks 3. providing backup communications in the event of the loss of the normal link and 4. providing a connection to a platform that may not be equipped with the specialized communications equipment for that TDL. JRE Nodes The JREAP is designed to support the networking of two or more JRE Processor nodes for the purpose of passing selected data from one node to any other node(s), via JRE media. The JREAP contains many management and monitoring features for maintaining required communication capabilities between JRE nodes. JREAP Structure • The stream of data transmitted by a JRE Processor using the JREAP consists of a series of headers, each followed by data defined by the header, as shown below • At the beginning of the header, a header type field will determine if the data is a Full Stack (JREAP-A/B) or Application layer data stream.(JREAP-C) JREAP Stacks JREAP is designed to be used either with communications systems that conform to the OSI model, as well as “legacy” communications systems that do not conform to the OSI layered model. Two separate protocol stack variations are used, Full Stack and Application Layer: • Full stack that provides Message Group headers and Transmission Block headers (JREAP A & B) • Encapsulation with an Application Layer header and transported using a Commercial Off-the-Shelf (COTS) transport layer. (JREAP-C) Full Stack For JREAP-A & B the stack enable legacy functionality such as error detection and message sequencing. This type of JREAP usage is referred to as “Full Stack”. To provide for better efficiency, the necessary fields are divided among two header groups, the Transmission Block Header and the Message Group Header. Application Layer For JREAP-C, the stack is designed for use over media utilizing TCP and UDP, that provide OSI transport layer functionality. This eliminate the need for a transmission block layer. The format is used to add the overhead data specific to that message within the first few bytes of the message format that also packs the message(s) (e.g. J-Series, VMF, etc.) being forwarded. Retransmission Timeouts A JRE processor can be asked for an acknowledgement of various messages transmitted. If an ACK is not received, the JRE processor may be required to retransmit the message. The table below shows the limit when the JRE processor will stop retransmitting messages based on the Round Trip Timing between JRE processors. JREAP Messages As mentioned previously, JREAP will process multiple types/series of messages: • • • • • • Management Messages J-Series Messages J-Series Text Messages J-Series Text Messages (uncoded)(images, files) K-Series Messages F & F-J Series Messages J-Series Msg Processing Link 16 terminals are required to construct and transmit the appropriate J2.x Precise Participant Location and Identification (PPLI) message within their local Link 16 net. This would also be true for a JRE Processor with an associated Link 16 terminal. If a JRE Processor is required to construct its own PPLI message in order to be reported on a Link 16 network, it shall do so using a J2.0 message. (Indirect Interface Unit PPLI) JREAP Intrusion Detection JREAP contains three features at the application level to support detection of intrusion events. 1. Each transmission packet is using unique assigned IU numbers 2. Each JRE Processor is using a coordinated time standard in each transmission packet (DVT) 3. Each JREAP transmission packet requires a sequence number. All transmission packet for each IU arrive sequentially at the application level. Out of sequence message are discarded. JREAP-C Application Layer As seen earlier, JREAP-C Application Layer is encapsulated and transmitted using IP unicast and Multicast via TCP and UDP protocols. JREAP-C via UDP • For connection via UDP, JREAP Application Blocks may be packed into a UDP Datagram. • UDP Datagram maybe sent using unicast or multicast. UDP data transmission are performed between a pair of peers in a connectionless mode. • Each JRE Processor sends datagrams to a specific peer address. Each JRE Processor opens a port and listens for arriving datagrams. There is no explicit IP connection between a pair of JRE Processors which means there is no guarantee of data exchange integrity like TCP. JREAP-C via TCP • For connection via TCP/IP, JREAP Application Blocks are sent one after each other sequentially. • TCP operations are performed between a client and a server in a connection-oriented mode. The server listens for connections on a given port number and clients may connect to that port number. • TCP connections uses a “handshake” to acknowledge each packet had been received. This ensure data exchange integrity. TCP vs UDP Application • Within TDLWAN and CAF networks, TCP/IP connection are normally the recommended connection protocol. This ensure data integrity between JRE processors. • Due to issues using Satellites and other mediums for JREAP-C, if a connection is known to be less than stable, UDP is recommended to be used. • If UDP is used, certain IERs need to be considered. If Command & Control, Surveillance or PPLI messages are needed for target engagement, UDP might not be the best protocol to be considered. Enclaves The DND/CAF is using multiple Network Enclaves at different level of encryption and classifications to exchange JREAP-C. The most commonly used enclaves are: • CNET • CSNI • TDLWAN • CFXNET (multiple classifications) • NSWAN • Pegasus (FVEY) Cross-Domain Solutions Data exchange between networks need to be secured, especially when it comes to networks with different classifications. Cross-Domain Solutions(CDS) are used and customised with certain products and equipment depending which connection need to be made. • Examples of Cross Domain Solutions and equipment: • NORAD IEG between CSNI and SIPRNET • RCAF CANICELINK connection between TDLWAN and NSWAN • General Dynamics TACDS modules for deployed solutions Cross-Domain Solutions Data exchange between networks need to be secured, especially when it comes to networks with different classifications. Cross-Domain Solutions(CDS) are used and customised with certain products and equipment depending which connection need to be made. • Examples of Cross Domain Solutions and equipment: • NORAD IEG between CSNI and SIPRNET • RCAF CANICELINK connection between TDLWAN and NSWAN • General Dynamics TACDS modules for deployed solutions Firewall / Filters Even if a Cross-Domain Solution is implemented, often a firewall and specific filters will be used between units. JREAP Messages Filters can be implemented at the JRE Processor directly or via separate firewalls. Certain products can implement JREAP message integrity checks to make sure each message is compliant to the set standard. • Examples of Firewalls used: • TDLWAN to CSNI Palo Alto Firewall • Firewall in the Halifax Class Frigates.