Print Friendly, PDF & Email

JREAP Training, Joint Range Extension Applications Protocol Training Bootcamp

JREAP Training, Joint Range Extension Applications Protocol Training Bootcamp is a 4-day comprehensive JREAP training covering JREAP A, B and C.

For detailed course agenda, CLICK HERE.

JREAP is based on  U.S. Military Standard (MIL-STD) 3011 and NATO Standardization Agreement (STANAG) 5518, “Interoperability Standard for the Joint Range Extension Applications Protocol (JREAP)”.

JREAP as an application protocol. enables the transmission of tactical data link messages over media that was not originally designed for TDLs including satellite links, Point to Point and modern and legacy IP Networks.

JREAP A uses an Announced Token Passing protocol for half-duplex communications. JREAP-A protocol may be used when several terminals share the same JRE media and take turns transmitting or in a broadcast situation when one transmits and the rest receive.

JREAP B is a synchronous or asynchronous point-to-point (p2p) mode of the JREAP. This Joint Range Extension Applications Protocol mode is similar in design to the Half-Duplex Announced Token Passing protocol used by JREAP A.

JREAP C  makes use of the Internet Protocol (IP) in conjunction with either the UDP or TCP. Both IPv4 and IPv6 with features such as Unicast, Multicast and Anycast can be used.

JREAP manages communications of the tactical data over long distances without degradation to the message format or content. By reformatting the messages, the tactical data can be transmitted Beyond Line-of Sight (BLOS).

MIL-STD-3011 defines the  protocols and message structures for the transmission and reception of pre-formatted messages over communications media other than those for which these messages were designed.

Link 16 is a  LOS high capacity, jam-resistant tactical data link with unique transmissions characteristics, protocols, conventions, and message formats defined by MIL-STD-6016. The range of Link 16 can be extended by the use of application protocols that enable the limitations of LOS radio communications to be overcome for the purposes of transmitting and receiving pre-formatted messages.  The application protocol , Joint Range Extension Application Protocol (JREAP) provide the BLOS capability for Link 16 based tactical operation.

Joint Range Extension Application Protocol (JREAP) enables the transmission of tactical data link messages over media that was not  originally planned or designed for TDLs. Supported communication media are:

  • Satellite communications
  • JREAP A
  • Point-to-Point
  • JREAP B
  • IP Networks
  • JREAP C

JREAP (Join range application protocol) is used for the  BLOS transmission and reception of tactical digital data over communications media not designed for those specialized data formats.

JREAP communication modes include  half-duplex, full-duplex or IP . The JREAP protocol can be used in the communication systems confirming to OSI model or other  communication systems .

JREAP provides capabilities such as:

  • Extending the range – limited tactical networks
  • Reducing the loading on stressed network,
  • Backup communication system,
  • providing a connection to a platform that may not be equipped with the specialized communications equipment for that TDL

JREAP protocol communication modes include:

  • Full stack layer that consists from Message group headers and Transmission block headers ,
  • Application layer – messages are encapsulated with application layer header and transported using Commercial Off-the-Shelf(COTS) transport layer – over IP protocol.

The JREAP standard defines the message  structure of the data that is created by a Joint  Range Extension (JRE) Processor.

The JREAP standard was developed to reduce reliance on service unique protocols  such as:

  • Satellite TADIL J (STJ), TDL J, Serial J, Super High Frequency Satellite Communications (SHF SATCOM), and Socket J that provided the ability for units to  share information beyond the line of sight capabilities of radio frequency (RF) based  communication systems.
  • JREAP-A uses a token passing protocol over half-duplex communication channels to send and receive Tactical Data Link messages. JREAP-A implements the full-stack  header and uses a token passing protocol, where one unit is allocated a particular  period of time to transmit data while all other units listen and receive the data.
  • JREAP-A is commonly used over 25kHz Ultra High Frequency (UHF) Demand Assigned Multiple Access (DAMA)/Time Division Multiple Access (TDMA),  Extremely High Frequency (EHF) Low-Data Rate (LDR), and 5/25kHz UHF Non-  DAMA SATCOM systems. These communication links are multi-participant satellite  communication networks.
  • JREAP-B is used in synchronous or asynchronous point-to-point communications. JREAP-B is commonly used with full-duplex serial data communications carried by  protocols such as TIA/EIA RS-232 and RS-422 and implements the full-stack header  of the JREAP protocol. These communication networks can be local, or they can use  long haul transmission media such as secure telephone circuits.
  • JREAP-C is an implementation of the JREAP protocol that transmits Tactical Data Link messages over Internet Protocol networks such as Secret Internet Protocol  Router Network (SIPRNET).
  • JREAP-C differs from JREAP-A and JREAP-B by implementing the application header instead of the full stack header. This is  done because the error detection and correction, and addressing is not necessary  as they are handled by the lower layers of the stack. This permits fast and reliable  transmission of messages over a network.

JREAP Training Bootcamp covers many topics including:

  • Joint Range Extension (JRE) of Link 16 and other tactical data links (TDLs)
  • Joint Tactical Information Distribution System (JTIDS)
  • Multifunctional Information Distribution System (MIDS)
  • To overcome the line-of-sight (LOS) limitations of radio terminals
  • Joint Range Extension Application Protocol (JREAP)
  • The Open System Interconnection (OSI) layered structure
  • JRE Processor
  • Joint Range Extension Application Protocol – Appendix C (JREAP-A)
    Half-Duplex Announced Token Passing
  • Joint Range Extension Application Protocol – Appendix C (JREAP-B)
    Full-Duplex Synchronous and Asynchronous Point-to-Point
  • Joint Range Extension Application Protocol – Appendix C (JREAP-C)
  • The IP-based beyond line of site (BLOS) transmission protocol for Link 16
  • Internet Protocol (IP) (User Datagram Protocol (UDP) Unicast and Multicast, and Transmission Control Protocol (TCP))
  • JRE Interoperability
  • JRE System Testing
  • JREAP and Tactical Data System Certification
JRE for example provides multi-point, interoperable, Beyond-Line-of-Sight (BLOS) Link-16 connectivity between Link-16 networks. JRE can utilize multiple Link-16 message transport protocols and the adaptation to various communication media. The protocols can be incorporated into both legacy and developing modern systems:
  • JREAP A – UHF DAMA
  •  PRC-117F, PSC-5, ARC-210, WSC-3
  • JREAP B – Serial
  • STE, STU
  • JREAP C – Ethernet
  • SIPRNET, NIPRNET

MIL-STD-3011 defines a generalized application protocol, designated as the Joint Range Extension Applications Protocol (JREAP), enabling tactical data to be transmitted over digital media and networks not originally designed for tactical data exchange.

Formatted tactical digital messages are embedded inside of JREAP messages as data fields within available commercial and Government protocol including satellites and terrestrial links. Specialized management messages are also provided to transport data not contained in the formatted messages, in order to support TDL-unique functions. Capabilities are provided that include:

  • Extending the range-limited tactical networks to beyond LOS while reducing their dependence upon relay platforms
  • Reducing the loading on stressed networks
  • Providing backup communications in the event of the loss of the normal link
  • Providing a connection to a platform that may not be equipped with the specialized communications equipment for that TDL.

For media that do not support OSI network and transport layers, the JREAP provides network and transport layer functionality. For media supporting OSI network and transport layers, the JREAP is encapsulated within those layers. JREAP software can be integrated into a host system or into a standalone processor. The appropriate interface terminals are required at each end of any JREAP alternate media link.

JREAP Communication Protocol examples:

  • MIL-STD 3011, Appendix A
  • UHF DAMA
  • Network controller
  • Network participant
  • Network broadcast
  • Network listener
  • MIL-STD 3011, Appendix B Point-to-Point
  • Synchronous (RS-422/449)
  • Asynchronous (RS-232)
  • MIL-STD 3011, Appendix C
  • Ethernet
  • TCP/IP Server
  • TCP/IP Client
  • UDP/IP Unicast
  • MIL-STD 1553B
  • 1553 Bus Protocol
  • 1553 IP
  • Satellite TADIL-J (STJ)
  • UHF DAMA
  • S-TADIL-J Gateway Controller (STGC)
  • S-TADIL-J Gateway Scheduler (STGS)
  • S-TADIL-J Gateway Unit (STGU)
  • Serial-J, MTDS
  • Asynchronous (RS-232)
  • SIMPLE-J, Serial
  • Asynchronous (RS-232)
  • SIMPLE-J Ethernet
  • TCP/IP Server
  • TCP/IP Client
  • MTC Ethernet
  • TCP/IP Server
  • TCP/IP Client
  • MTDS Ethernet
  • TCP/IP Server
  • TCP/IP Client
  • Situation Awareness Data Link (SADL)
  • 11x
  • 11xy
  • Link-16 Terminal
  • MIDS LVT-1 (Ethernet)
  • MIDS LVT-2 (Ethernet)
  • MIDS LVT-2 (X.25)
  • MIDS LVT-11 IP
  • MIDS LVT-3 (1553)
  • USN E-2 (1553)
  • USAF E-8 (1553)
  • USAF F-15 (1553)
  • USAF MCE (1553)
  • USMC MCE (1553)
  • US Army 2M (X.25)

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.