MOSPF

Multicast Open Shortest Path First

Protocol →
Introduced in Rel-8

MOSPF is a multicast routing protocol extension to OSPF used within 3GPP packet-switched networks for IP multicast group management and distribution tree calculation to enable efficient multicast traffic delivery.

Category
Protocol
Introduced
Rel-8
Where
Core Network › Legacy Core
Specifications
1 specs
MOSPF Description Purpose Related Detected Changes Specifications

Description

Multicast Open Shortest Path First (MOSPF) is an extension of the Open Shortest Path First (OSPF) unicast routing protocol, defined by the IETF and incorporated into 3GPP specifications for use in packet-switched domains. It operates as a link-state multicast routing protocol. In MOSPF, routers exchange group membership information via a new type of Link State Advertisement (LSA), the group-membership-LSA. This allows each router in an OSPF area to build a complete picture of the multicast group membership and the network topology. Using this information, a router can compute a shortest-path tree on-demand for each source and multicast group pair (S, G). The tree is rooted at the source and spans out to all routers that have local members of the group, using Dijkstra's algorithm applied to the topology database.

The protocol's operation is tightly integrated with the underlying OSPF unicast routing. Routers must be MOSPF-capable to participate in multicast routing. A Designated Router (DR) on a multi-access network segment is responsible for originating group-membership-LSAs on behalf of local group members reported via the Internet Group Management Protocol (IGMP). These LSAs are flooded throughout the OSPF area, ensuring all routers have synchronized multicast topology information. When a packet for a multicast group arrives at a router, and the router has no cached tree for that (S, G) pair, it performs the Dijkstra calculation to determine the outgoing interfaces for forwarding. This calculation uses the regular OSPF link-state database, augmented with the group membership information.

Within the 3GPP architecture, MOSPF is referenced in the context of the Packet Data Network Gateway (P-GW) and the core IP transport network. Its role is to facilitate efficient multicast service delivery, such as IP Multimedia Subsystem (IMS) multicast services or content distribution, across the operator's IP backbone. It provides a mechanism for building multicast distribution trees without relying on flooding or reverse path forwarding (RPF) checks based on unicast routing tables alone. However, its scalability is limited to within a single OSPF area because the group-membership-LSAs are not flooded into other areas; inter-area multicast requires other mechanisms.

Purpose & Motivation

MOSPF was developed to address the need for efficient, topology-aware multicast routing within autonomous systems, specifically those using OSPF as their Interior Gateway Protocol (IGP). Prior to protocols like MOSPF, multicast often relied on simpler but less efficient methods like flooding or Distance Vector Multicast Routing Protocol (DVMRP), which could lead to suboptimal paths and traffic loops. The integration of multicast routing with the reliable, fast-converging link-state principles of OSPF was a significant motivation.

In the 3GPP context, as mobile networks evolved to support rich packet-switched services like multimedia broadcasting and group communications, efficient core network multicast became essential. MOSPF provided a standardized method for operators using OSPF in their backbone to natively support IP multicast, enabling services like Multimedia Broadcast Multicast Service (MBMS) to be transported efficiently from content sources to multiple base stations or directly to user equipment. It solved the problem of calculating optimal multicast distribution trees based on the actual network topology and group membership, reducing redundant traffic and improving bandwidth utilization compared to unicast replication or naive multicast flooding approaches.

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the enhancements for the MOSPF function were not explicitly detailed in the provided grounding context. The listed Change Requests indicate work was done to provide clarification for the MBMS session start procedure and to implement a correction for QoS modification in the MBMS Update Request. The technical scope of these updates pertains to MBMS control and data delivery mechanisms, involving interfaces like SGmb and Sgi-mb between the BM-SC and MBMS GW.

  • Clarification for MBMS session start procedure TS 29.061CR0499
  • Correction for QoS modification in MBMS Update Request TS 29.061CR0496
Rel-18 1 change

In Release 18, the MOSPF function was enhanced to integrate with the P-GW's packet handling capabilities, specifically concerning the setting of the DSCP (Differentiated Services Code Point) for traffic management. This update leverages the P-GW's role as an IP router at the Sgi reference point, utilizing its existing context for IP-CAN sessions to apply appropriate DSCP markings to multicast traffic flows. The change ensures multicast data forwarding aligns with the differentiated services model within the packet domain's interworking with external IP networks.

Explore further

Broader topics and technologies where MOSPF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 29.061 vj00 Packet Domain Interworking for PLMN Rel-19