Skip to content
NATO Edge 26 - 17–19 November 2026 - Izmir - Stand G19 Book a meeting at our stand
AOC Türkiye: Dominating the Spectrum - 26–27 November 2026 - Ankara Book a meeting at the event
Data streams of light converging at a single hub

02 Connect Multi-Tactical Data Link Processor

Mil-DLP

Brings Together Different Tactical Data Links Within a Common Data Structure

Mil-DLP is a Data Link Processor developed in Türkiye by MilSOFT, which processes various tactical data link protocols used on naval, air and land platforms within a single system.

It processes information from various tactical data link standards, such as Link 11, Link 16, Link 22, JREAP and VMF, converts it into a common data model, and makes it available for use by platform systems.

  • NATO STANAG 5511 - 5516 - 5522 - 5616

How It Works

A four-stage process spanning from various tactical data sources to a common data model

Illustrative flow - 01 / 04

Tactical data linksTarget systemsMil-DLPReceiveProcessConvertLink 11Link 16Link 22JREAPVMFCommondatamodelMission systemC2 system
  1. It receives messages from supported tactical data link protocols such as Link 11, Link 16, Link 22, JREAP and VMF.

  2. It decodes the unique message structure of each protocol and processes the tactical information it contains.

  3. It converts data from different protocols into a common data model, making it usable by platform systems.

  4. It transmits the processed data to the mission and command-and-control systems and, when required, forwards it to other data links (data forwarding).

Collect. Process. Convert. Transfer to the required system.

Problem

Platforms located within the same operational area do not always use the same data link standard

In modern operational environments, it is of critical importance that naval, air and land platforms are able to share tactical information in a timely manner and contribute to a common operational picture.

Platforms developed in different eras may use different tactical data link standards. Whilst one platform may communicate via Link 16, another may only support Link 11; in newer systems, different standards such as Link 22 may come into play.

In this scenario, the requirement is not limited to simply establishing communication between platforms.

As each data link protocol has its own unique message structure and processing logic, the use of multiple standards within the same operational network complicates the integration process.

Establishing a separate processing infrastructure for each protocol requires the development of different software components, the execution of integrations on a case-by-case basis, the harmonisation of message structures, and the management of increased testing and maintenance processes.

This requirement becomes particularly evident in scenarios where platforms of different generations or coalition elements operate together within the same operational environment.

The real requirement is not to set up a separate processing infrastructure for each tactical data link, but to bring together different protocols within a common and manageable layer

Solution

To manage different tactical data link protocols within a common processing layer

The multi-data-link approach is based on the processing of tactical information from different links within a single system.

Location, identity or status information transmitted from a platform is processed independently of the data-link protocol used and converted into a common data model that can be utilised by the relevant platform systems.

This reduces the need for mission systems to manage the technical structure of each data-link protocol separately.

The ability to manage multiple protocols within the same processing layer supports the interoperability of different generations of platforms, existing systems and new capabilities within a common operational environment.

When a new data link standard or message type needs to be incorporated into the system, it is possible to extend the existing architecture rather than having to rebuild the entire integration architecture from scratch.

Different links. Different message structures. A common tactical data processing layer.

Product

What is Mil-DLP?

Mil-DLP is a Data Link Processor solution developed in Türkiye by MilSOFT to process different tactical data link protocols within a single system.

It can process the Link 11, Link 16, Link 22, JREAP and VMF tactical data link standards simultaneously; it converts the tactical information received from these protocols into a common data model and makes it available for use by platform systems.

This reduces the need for mission systems to manage the technical details specific to each data link protocol separately.

Mil-DLP is not merely a component that receives and relays incoming data. It is a tactical data processing layer that performs the tasks of receiving, processing, converting and transferring information obtained from different links to the relevant systems.

Depending on platform requirements, specific data links or the message types associated with these links can be enabled or disabled. This enables the product to be adapted to different mission and platform configurations.

Its open architecture, developed in accordance with the OACE standard, facilitates the addition of new links to the system or adaptation to changes in existing message structures.

Mil-DLP supports the sharing of tactical information across platforms by processing information from different tactical data link standards within a common data model

Capabilities

  • Multiple Tactical Data Links

    It processes the Link 11, Link 16, Link 22, JREAP and VMF protocols simultaneously within the same system.

  • Cross-Protocol Data Processing

    It converts tactical information from different data link formats into a common data model.

  • Data Forwarding Between Data Links

    It forwards tactical data between Link 11, Link 16 and Link 22 networks. Platforms using different data links share the same tactical picture.

  • Flexible Configuration

    It allows links and message types to be enabled or disabled as required by the platform.

  • Platform-Independent Architecture

    The logic behind data link processing has been decoupled from platform, operating system and hardware dependencies.

  • Open and Extensible Architecture

    Its architecture, based on the OACE standard, can be adapted to new link and message requirements.

  • Developed in Türkiye

    Development in Türkiye allows for customisation and ensures supply independence.

The Difference

Why Mil-DLP?

Interoperability should not require all platforms to use the same data link standard

Mil-DLP provides a common data processing layer that supports the concurrent use of different tactical data link standards within the same operational environment.

  • Multi-protocol management

    Different tactical data feeds can be processed simultaneously within the same system.

  • Common data model

    Protocol-specific information is converted into a common structure that platform systems can utilise.

  • Flexible configuration

    The required links and message types can be configured in line with the platform’s requirements.

  • Modernisation-ready

    Interoperability between different generations of platforms within the same operational network is supported.

  • Extensible architecture

    New link and message requirements can be accommodated whilst maintaining the existing architecture.

  • Engineered in Türkiye

    It offers technical control and customisation options for critical data link processing capabilities.

The key distinction of Mil-DLP is not merely that it supports multiple tactical data links; it is that it brings together the information from these protocols within a common and manageable data structure

Use Cases

Mil-DLP is used in C5ISR systems and platform integrations where multiple tactical data link standards need to be used together within the same operational environment.

  • Naval Platforms

    It supports the processing of information from various tactical data links on naval platforms and its transmission to the relevant mission systems.

  • Air Platforms

    It enables airborne platforms to share tactical information—such as position, identity and status—via various data link systems.

  • Land Systems

    It can be used as a data processing layer in the integration of land-based platforms and command and control systems with multi-tactical data link infrastructures.

  • Coalition Operations

    It supports the sharing of tactical information between platforms belonging to different forces and using different data link standards.

  • Modernisation Projects

    By enabling platforms of different generations to operate together within the same operational network, it facilitates the integration of existing systems with new tactical data link capabilities.

A platform that supports only Link 11 and a platform that uses Link 16 operate in the same tactical network thanks to data forwarding.

Technical Architecture

Core function
The collection, processing and conversion of information from different tactical data link protocols into a common data model
Supported data links
Link 11, Link 16, Link 22, JREAP and VMF
Processing structure
Multi-source and concurrent tactical data link processing
Configuration
Enable/disable at link and message type level
Architectural approach
An open and extensible architecture based on the OACE standard
Portability
Operates independently of the platform, operating system and hardware
Integration
Standalone operation, integration into a mission computer, or integration with existing command and control systems
Development model
Developed in Türkiye by MilSOFT and customised to meet project requirements

Who Is It For?

  • Decision-maker

    It supports the management of different tactical data link standards via a common infrastructure and the shared use of existing platform investments.

  • Systems Architect / Integrator

    Rather than developing separate processing structures for each data link, it enables integration via a common architecture.

  • Development Team

    It facilitates the controlled integration of new link and message requirements into the existing architecture.

  • Modernisation Team

    It supports the interoperability of different-generation platforms within the same operational network.

  • Organisation

    It provides technical control over a customisable tactical data link processing infrastructure developed in Türkiye.

An engineer wearing headphones, seated at a console in front of a wall of maps and radar screens

Next Step

Different platforms may not use the same data link standard, but they must contribute to the common operational picture with the same level of accuracy

In tactical data link integration, the requirement is not limited to simply transferring messages from one platform to another.

Information from different protocols must be processed correctly, converted into a common data model, and made available for use by the relevant mission systems.

Mil-DLP supports the sharing of tactical information between platforms of different generations and for different missions by processing the Link 11, Link 16, Link 22, JREAP and VMF protocols within the same system. Thanks to its open and extensible architecture, it can be adapted to changing platform and mission requirements.

Different protocols. A common data structure. Seamless sharing of tactical information.

Please contact MilSOFT’s experts to assess how Mil-DLP can be integrated into your existing or new platform architecture.