MONP

MC service Off-Network Protocol

Protocol →
Introduced in Rel-13

MONP is the set of protocols that enables direct device-to-device communication for Mission Critical services when user equipment is outside of network coverage.

Category
Protocol
Introduced
Rel-13
Where
Services › IMS
Specifications
5 specs
MONP Description Purpose Detected Changes Specifications

Description

The MC service Off-Network Protocol (MONP) is a comprehensive protocol suite standardized by 3GPP for enabling Mission Critical (MC) services in off-network conditions. It is specified across multiple technical specifications, including TS 24.281 (MCPTT off-network), TS 24.282 (MCData off-network), TS 24.379 (MCVideo off-network), and the associated conformance test specs TS 36.579 and 37.579. MONP allows Mission Critical User Equipment (MC UEs) to establish direct device-to-device (D2D) communication links using Proximity Services (ProSe) when they are not served by a 3GPP network (e.g., in remote areas, during network failures, or inside buildings with no coverage). The protocol stack operates over the PC5 reference point, the direct interface between UEs defined for ProSe. MONP encompasses several layers and functions: it defines discovery mechanisms for UEs to find each other and form groups off-network, session management for setting up and tearing down group calls (e.g., MCPTT calls), floor control for managing talker permission, security protocols for authentication and encryption of the direct link, and media plane protocols for transporting voice, data, or video. A key architectural concept is the Off-Network UE, which can autonomously function as a client, and in some configurations, certain UEs can take on limited network-like roles (e.g., for relaying or managing discovery) to extend the communication range or organize the group. MONP is tightly integrated with the on-network MC service architecture; a UE can seamlessly transition between on-network and off-network modes based on availability. The protocols ensure that critical features like group management, emergency calls, and security are maintained even without infrastructure.

Purpose & Motivation

MONP was created to fulfill a critical requirement for public safety and mission-critical professional users: reliable communication must be available even when the cellular network is damaged, overloaded, or simply not present. Traditional cellular services are entirely dependent on network infrastructure (base stations, core network). In disaster scenarios like earthquakes, fires, or terrorist attacks, this infrastructure can fail. MONP solves this problem by standardizing a direct mode of operation using D2D technology. It addresses the limitations of previous proprietary solutions (like traditional walkie-talkies) by providing a standardized, interoperable, and feature-rich off-network protocol that integrates seamlessly with the broader 3GPP Mission Critical services ecosystem (MCPTT, MCData, MCVideo). This allows first responders from different agencies or using equipment from different vendors to communicate directly. The motivation stems from lessons learned from major incidents where communication breakdowns occurred. By providing a standardized off-network protocol, 3GPP enables the development of ruggedized UE that can operate in both infrastructure-based and direct modes, ensuring communication resilience, which is a non-negotiable requirement for public safety organizations worldwide.

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 2 changes

In Release 15, the MONP (MC service Off-Network Protocol) function was newly introduced to define the transport of MCVideo messages for off-network group calls, private calls, and video push. Specifically, it introduced the MONP MCVIDEO MESSAGE CARRIER message, sent as a UDP message to a multicast or local IP address on port 8809, as the standardized payload format. The release also included subsequent fixes to resolve issues with the encoding of Information Elements (IEs) in MONP messages for both MCVideo and MCData services.

  • Fix issues with encoding of IEs in MONP messages for MCVideo TS 24.281CR0046
  • Fix issues with encoding of IEs in MONP messages for MCData TS 24.282CR0050
Rel-16 2 changes

In Release 16, the MONP function was enhanced to explicitly support off-network MCData and MCVideo services, as indicated by the new CR titles. The technical specifications detail the use of MONP MCVIDEO MESSAGE CARRIER messages, sent via UDP on port 8809 to either multicast or unicast IP addresses, to facilitate group calls, private calls, and video push. Furthermore, the release included necessary corrections and resolved editorial notes to clarify the protocol's operation and message handling procedures.

  • Resolving editor's notes on MONP port TS 24.379CR0474
  • Specification of MONP messages to support off-network MCData and MCVideo TS 24.379CR0612
Rel-17 2 changes

In Release 17, the MONP function was updated with specific corrections and clarifications, primarily addressing the missing UDP port number definition for message transport. The release explicitly defined that MONP MCVideo messages for group calls, private calls, and Video Push must be sent and received on UDP port 8809. Furthermore, it reinforced procedures for handling unexpected MONP messages by mandating they be discarded when received in an unspecified state.

  • Corrections for MONP TS 24.281CR0123
  • Missing MONP message transport port number and other corrections TS 24.282CR0218

Explore further

Broader topics and technologies where MONP plays a role.

Defining Specifications

3GPP specifications that define or reference MONP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 24.281 vj40 MCVideo Signalling Control Specification Rel-19
TS 24.282 vj50 MCData Signalling Control Protocols Rel-19
TS 24.379 vj50 Mission Critical Push To Talk (MCPTT) call control Rel-19
TS 36.579 3GPP TR 36.579 Rel-13
TS 37.579 vi40 Mission Critical services conformance testing Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.