Price: $3,999.00
Length: 4 Days
Print Friendly, PDF & Email

Joint Range Extension Applications Protocol Training, JREAP Training Bootcamp

Joint Range Extension Applications Protocol Training, JREAP Training Bootcamp, is a 4-day JREAP course covering details of JREAP-A or Announced Token Passing protocol for half-duplex communications, JREAP-B or synchronous or asynchronous point-to-point mode of the JREAP, and JREAP-C using the Internet Protocol (IP) in conjunction with UDP or TCP. Participants of JREAP Training bootcamp will also learn about the foundation of Joint Range Extension (JRE) concept and how the Internet Protocol (IP) technologies utilized for transfer and transport  tactical data using integration of Data Links networks and tactical IP networking. JREAP training bootcamp provides knowledge of system capabilities and limitations, system foundation, engineering, operation, performance, qualification and optimization of JREAP systems. For over 30 years TONEX has supported land, air and maritime military operations, defense organizations and government agencies around the world to deliver situational awareness consulting and training and enhanced operating effectiveness of mission critical SATCOM, UHF, VHF, TDL, Link 11/16/22, VMF, SADIL, and JREAP systems.  Our team of skilled instructors, consultants and  JREAP experts assist participants on all aspects of the JREAP lifecycle processes. In accordance with DoD Instruction 4630.8, it is DoD policy that all Joint and combined operations be supported by compatible, interoperable, and integrated Command, Control, Communications, and Intelligence (C3I) systems.

Learning Objectives

Upon completion of the JREAP training, the participants will be able to:

  • Explain the basic principles and concepts of JRE and JREAP
  • List related JREAP standards and benefits
  • Describe the history and background of variety of JREAP systems
  • Describe the key concepts, features and mechanisms behind JREAP operation
  • Illustrate potential JREAP deployment scenarios
  • Describe JREAP standards, requirements and operational models
  • List the basic principles of JREAP A, B and C procedures and methods
  • Explain the basics of JREAP systems engineering and product life cycles
  • Explain the JREAP process and Interoperability testing methodology
  • Perform testing and certification policies, methods, tools, and procedures applied to JREAP and other related TDLs.

Who Should Attend

  • TDL and JREAP Technical Managers
  • TDL and JREAP Engineers and Technicians
  • TDL and JREAP Project Managers
  • Network Engineers
  • TDL  and JREAP Analysts
  • JREAP  Cybersecurity Professionals
  • JREAP Operational Test Staff

Highlights of JREAP Training Bootcamp:

  • Position the activities in the complete JREAP system certification, verification and validation process
  • Use testing terminology in a JREAP  system (JREAP A, B and C)
  • Use risk to drive the validation efforts
  • Make decisions on how to test JREAP systems for defects more efficient
  • Plan appropriate (risk-based) techniques to find JREAP defects
  • Plan appropriate (risk-based) functional testing techniques
  • Choose appropriate tests for acceptance, that is, compliance to requirements
  • Manage JREAP A, B and C test data and information
  • Manage JREAP A, B and C testing requirements and test failures
  • Document the TDL test plans (activities, resources, risks)
  • Use Interoperability Test and Evaluation and Requirements Transformation (iSMART) for JREAP

Course Agenda

Introduction to JREAP

  • Basic Principles of TDL Systems
  • Principles behind Joint Range Extension Applications Protocol (JREAP)
  • Interoperability Standard for the Joint Range Extension Applications Protocol (JREAP)
  • JREAP MIL-STD-3011
  • NATO Standardization Agreement (STANAG) 5518
  • JREAP and Tactical Data Links (TDLs)
  • JREAP and Tactical Data Messages Transmission
  • Joint Range Extension Applications Protocol (“JREAP”) Versions and Protocols
  • JREAP A, B and C
  • JREAP and Satellite Links

Traditional J-Series BLOS

  • JREAP and Requirements for Exchange Tactical Data BLOS (beyond line of sight)
  • Situational Awareness, Planning, and Decision Making
  • Early BLOS Link 16 Efforts
  • Limited Interoperability
  • Satellite TADIL-J or STJ
  • UHF SATCOM
  • Navy UHF DAMA
  • Serial-J
  • SHF SATCOM
  • Legacy and Point-to-Point
  • Socket J and Legacy IP Interfaces

Development of Joint Range Extension (JRE)

  • Application Protocols (JREAP)
  • MIL-STD 3011and STANAG 5518 Organization
  • Applicable Specs
  • JRE and JREAP A, B and C Definitions, Terms, and Acronyms
  • JREAP General Requirements
  • Appendices A, B, and C
  • JREAP A, B and C Detailed Requirements
  • Technical Review of Appendices A, B, and C
  • Joint Range Extension (JRE)
  • JRE Application Protocol (JREAP)
  • MIL-STD 3011 Appendix A Token Passing
  • UHF SATCOM
  • Appendix B Point-To-Point: Phone Lines/PSTN
  • SHF SATCOM
  • Appendix C IP / UDP
  • SIPRNET/ EHF

JRE Use Cases

  • Extend range of existing TDLs like Link 16
  • Connect Distant Nodes/Systems
  • Join Disparate TDL Networks
  • Backup Link Capability
  • Network Load Balancing
  • Cost-effective connection to non-TDL platform
  • Remote Picture and Imaging

MIL-STD 3011 and STANAG 5518 Organization

  • Applicable Documents
  • Definitions, Terms, and Acronyms
  • General Requirements
  • Detailed Requirements
  • Appendices A, B, and C
  • Primary Capabilities of JREAP
  • Extending the range-limited tactical networks
  • Beyond LOS
  • Role of Relay platforms
  • Reducing the loading on stressed networks
  • Providing backup communications
  • Loss of the normal link

JREAP Protocols and Messages

  • Open System Interconnect (OSI)
  • JREAP Data Formats
  • Structure of the JREAP Data Stream
  • Message Extrapolation
  • JREAP Headers
  • JREAP Protocols Mapped to OSI 7-Layer Stack
  • JREAP Application Messages
  • JREAP Data Messages
  • JREAP Management Messages
  • JREAP “Message Group” Layer for JREAP A and JREAP B
  • JREAP “Transmission Block” Layer for JREAP A and JREAP B
  • Message Group Header
  • Application Header
  • Messages
  • JREAP-C Messages
  • J-Series
  • JREAP Management Messages
  • Management Message Sub Header
  • Message Retransmissions
  • Minimum Implementation
  • Link Monitoring

JREAP Design and Systems Engineering

  • JREAP System Survey
  • Joint Range Extension (JRE)
  • JRE Processor Hardware
  • JRE the Application Protocol (AP)
  • JREAP Principles in MIL-STD-3011
  • JRE Application Protocol (AP)
  • JREAP Technical Details
  • Life-Cycle Building Blocks for JREAP Systems
  • JREAP Concept Development
  • Requirements Engineering
  • JREAP System Architecture
  • JREAP System Design and Development
  • JREAP A, B and C Systems Integration
  • JREAP Test and Evaluation
  • JREAP Test and Evaluation Strategies
  • JREAP Verification and Validation
  • Implementation, O & M, and Transition
  • JREAP Certification and Accreditation Strategies
  • JRE Requirements and Design
  • JRE Processors
  • JTIDS Zones
  • TCP/IP Networks
  • JRE Capabilities
  • JRE Verification and Validation (V&V)
  • JRE Testing

JREAP Communications Protocols

  • JREAP A, B and C
  • Protocol Descriptions
  • JREAP Communication Requirements and Capabilities
  • Half-Duplex Token Passing Protocol
  • Full-Duplex Synchronous or Asynchronous Point-to-Point Connection
  • Description
  • Requirements
  • Capabilities
  • Encapsulation Over Internet Protocol (IP)
  • Description
  • Requirements
  • Capabilities

JREAP-A

  • Token Passing Protocol
  • UHF and EHF SATCOM
  • Half-Duplex Announced Token Passing Protocol
  • 25-kHz UHF TDMA/DAMA SATCOM (MIL-STD-188-183)
  • EHF LDR Forced Mode Network Operations (MIL-STD-188-1582)
  • 5- and 25-kHz UHF non-DAMA SATCOM (MIL-STD-188-181)
  • JREAP A Satellite Access
  • JREAP A Considerations
  • Satellite Access Request/Authorization
  • Participation and Data Rate
  • Terminal Base Address
  • Encryption Keys (orderwire & data)
  • Network Roles
  • OPTASK LINK Inputs

JREAP-B

  • Full Duplex Solution
  • Synchronous or Asynchronous Point-to-Point Connection
  • UHF and EHF LDR (Low Data Rates)
  • JRE Processor
  • Crypto Components
  • Media Interfaces
  • JREAP B Considerations
  • Connection Type
  • Crypto Device drive crypto used
  • Throughput and Circuit Planning
  • Backup Links and Data Loops

JREAP-C

  • IP Communications
  • Application Headers
  • TCP vs. UDP
  • TCP and UDP Similarities and Differences
  • TCP (Transmission Control Protocol)
  • UDP (User Datagram Protocol)
  • Encapsulation over Internet Protocol (IP)
  • Unicast and Multicast IP
  • Anycast in IPv6
  • LAN/WAN Protocols
  • L1 Physical Media Protocols
  • JREAP C Considerations
  • Group Address: JGROUP
  • Port Number: JPORT

Message Types for JRE

  • J-Series Messages
  • Free Text Messages
  • VMF Messages
  • Link 22 Messages
  • Common Message Format (CMF) Integrated Broadcast
  • Service (IBS) Message

JREAP Management Messages

  • the JRE Link active and notify the JRE processors of
  • their peers
  • JREAP Management Messages include:
  • Round-Trip-Time Delay Message
  • Operator-to-Operator Messages
  • Filter Messages
  • Latency Threshold Messages
  • Acknowledgement Messages
  • Echo Messages
  • The Filter Management
  • Filter Management Message Subtypes
  • Processing Rules
  • Retransmission timeouts
  • PPLI (Indirect PPLI)

Improvements to JREAP

  • Migration to IPv6
  • IPv6 Tunneling
  • Role of MPLS
  • MPLS VPNs
  • IP Network Management and Operations
  • Security and Firewalls
  • Cybersecurity Considerations
  • SNMPv3
  • Configuration and Fault Management
  • Network Performance
  • Network Delay, Jitter and Bandwidth Management
  • IP Network Admin Coordination
  • Server and Client Access
  • Timeliness
  • Throughput
  • OPTASK LINK and JREAP
  • Baselines include JREAP sets
  • Network Time Standards (NTP)

 

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.