IPTV Over MPLS Using MVPN – Reliance Jio Scenario

-

 

Insight:

IPTV over MPLS backbone using MVPN (Multicast VPN) is a key solution for service providers to deliver high quality, scalable multicast content – live TV, video on demand, streaming media – to a geographically dispersed subscriber base. In this architecture, each IPTV customer is put into a dedicated VRF (Virtual Routing and Forwarding instance), so traffic is isolated and multi-tenant. The IPTV multicast streams, typically sourced from a central headend, are sent via multicast groups (e.g. 239.1.1.1 for Aaj Tak, 239.1.1.2 for Star Sports) using PIM-SM (Protocol Independent Multicast Sparse Mode) within the customer’s VPN. These multicast routes are then signaled across the MPLS core using BGP with the MCAST-VPN SAFI (Subsequent Address Family Identifier 129) feature of Next-Generation MVPN (NG-MVPN). On the transport side, the multicast traffic is encapsulated and transported across the MPLS backbone using mLDP (Multipoint LDP) or RSVP-TE to form a P2MP (Point-to-Multipoint) Label Switched Path, not GRE tunnels used in legacy Rosen MVPN. PE routers dynamically create Default MDTs (Multicast Distribution Trees) when the first receiver joins, so minimal bandwidth is used across the provider core. When the multicast traffic for a specific group reaches a certain threshold, a Data MDT is created to handle that high bandwidth stream separately and more efficiently. Interfaces facing CE routers are configured with PIM and IGMP to allow subscriber devices, like set-top boxes, to send IGMP join requests and get the desired content. This integration of unicast MPLS VPN and multicast delivery means IPTV services scale linearly, are high quality and isolated for each customer, so service providers can offer premium media services over their MPLS networks.


Scenario: Reliance Jio wants to Deliver IPTV services (live TV channels) from a central video source (headend) to subscribers across various cities using an MPLS backbone while preserving scalability, efficiency, and VPN isolation. 




In an MVPN over an MPLS backbone IPTV service delivery architecture, each component plays a part in efficient and scalable multicast video distribution. The Headend (also known as the video source) is where live TV channels and video content are ingested, encoded and streamed into the network as multicast traffic. This content is first sent to the Provider Edge (PE) routers which are the entry and exit points for customer traffic into the MPLS network. These PE routers are multicast aware and participate in MVPN using PIM, BGP with MCAST-VPN SAFI and MPLS signaling like mLDP or RSVP-TE to distribute multicast streams across the provider network. In the MPLS core the traffic is forwarded by Provider (P) routers which are label switching routers that transport traffic at high speed but are unaware of VPN or multicast routing. Closer to the end user the Customer Edge (CE) routers reside in the ISP’s access layer and interface with subscribers. These routers receive multicast streams from the PE and send them to subscriber devices. Finally, the Set-Top Boxes (STBs) in subscribers’ homes are the endpoints that request and consume the IPTV channels. These devices use IGMP to join multicast groups for specific channels and get real time TV content with minimal latency and efficient bandwidth usage. This hierarchical design separates the responsibilities and allows IPTV services to scale across large geographic areas while maintaining multicast isolation and quality of service.

 

Here VRF name: Jio_IPTV

Multicast Group: 239.1.1.1

Head-end PE router: PE1

Remote PE router: PE2

Routing protocols for CE-PE: PIM-SM

Transport in MPLS core: m-LDP


=====================================

Configuration Steps ---

Configuration: PE1 at Headend

1. Define the VRF

vrf JioIPTV

  rd 100:1

  address-family ipv4 unicast

    route-target export 100:1

    route-target import 100:1

  !

  address-family ipv4 multicast

    mdt default 239.1.1.1

    mdt default 239.1.1.2

    mdt default 239.1.1.3

    mdt default 239.1.1.4

    mdt data 239.1.1.1 0.0.0.255 threshold 1

    mdt data 239.1.1.2 0.0.0.255 threshold 1

    mdt data 239.1.1.3 0.0.0.255 threshold 1

    mdt data 239.1.1.4 0.0.0.255 threshold 1

    mdt auto-discovery pim

    mdt preference 1

  !

 2. Multicast Routing Inside VRF

router pim

  vrf JioIPTV

    rp-address 8.8.8.8

 

3. Enable BGP MVPN SAFI (Address Family Identifier)

router bgp 100

  address-family vpnv4 unicast

    neighbor 10.10.10.2 activate

    neighbor 10.10.10.2 send-community both

  !

  address-family ipv4 mdt

    neighbor 10.10.10.2 activate

  !

  address-family ipv4 mvpn

    neighbor 10.10.10.2 activate

 

4. Configure Interface in VRF

interface GigabitEthernet0/0

  vrf JioIPTV

  ip address 192.168.1.1 255.255.255.0

  ip pim sparse-mode

 

===================================== 

Configuration: PE2 at Subscriber site

1. Define the VRF

vrf JioIPTV

  rd 100:1

  address-family ipv4 unicast

    route-target export 100:1

    route-target import 100:1

  !

  address-family ipv4 multicast

    mdt default 239.1.1.1

    mdt default 239.1.1.2

    mdt default 239.1.1.3

    mdt default 239.1.1.4

    mdt data 239.1.1.1 0.0.0.255 threshold 1

    mdt data 239.1.1.2 0.0.0.255 threshold 1

    mdt data 239.1.1.3 0.0.0.255 threshold 1

    mdt data 239.1.1.4 0.0.0.255 threshold 1

    mdt auto-discovery pim

    mdt preference 1

  !

2. Multicast Routing Inside VRF

router pim

  vrf JioIPTV

    rp-address 8.8.8.8

 

3. Enable BGP MVPN SAFI (Address Family Identifier)

 router bgp 100

  address-family vpnv4 unicast

    neighbor 10.10.10.1 activate

    neighbor 10.10.10.1 send-community both

  !

  address-family ipv4 mdt

    neighbor 10.10.10.1 activate

  !

  address-family ipv4 mvpn

    neighbor 10.10.10.1 activate

 

4. Configure Interface in VRF

interface GigabitEthernet0/1

  vrf JioIPTV

  ip address 192.168.1.10 255.255.255.0

  ip pim sparse-mode

 

 

Configuration On CE router

 ip multicast-routing

interface GigabitEthernet0/0

  ip address 192.168.2.1 255.255.255.0

  ip pim sparse-mode

  ip igmp version 3

===================================================================

Note: The multicast group address 239.255.1.1 is just an example for the Default MDT (Multicast Distribution Tree) in a specific VRF (Virtual Routing and Forwarding instance). In real world networks each customer or VRF should have its own unique MDT default address to keep their multicast traffic separate. This way ISP prevent traffic from one customer to reach another and keep it isolated. For example, Jio have two IPTV customers you would configure 239.255.1.1 for Customer 1 and 239.255.2.1 for Customer 2. These addresses are from the administratively scoped multicast range (239.0.0.0/8) which is for internal or private multicast use within a service provider’s network. This way you keep customers separate and multicast traffic flows only where it’s supposed to.


Conclusion:

Using IPTV over MPLS backbone with MVPN gives service providers like Reliance Jio a robust, scalable and efficient way to deliver high quality multicast services like live TV, video on demand, streaming content to a large customer base. Each customer is placed in a dedicated VRF so complete traffic isolation and multi-tenant environment is ensured. Multicast streams from central headend are distributed using PIM-SM and managed over the MPLS network with BGP signaling (SAFI 129) and mLDP for label-based forwarding. Default MDTs for control and low bandwidth traffic and Data MDTs for high bandwidth optimization ensures bandwidth efficiency and reduces unnecessary replication across the core. Proper configuration of PIM, IGMP, unique MDT group addresses per VRF ensures multicast traffic reaches only the intended subscribers through CE routers and STBs. Overall, this architecture gives Jio a premium IPTV experience with network efficiency, scalability and service isolation over the MPLS infrastructure.


Comments

Post a Comment

Popular posts from this blog

Configuring NNI Interface Policies and Container Integration in Nokia SR and Juniper AG Networks

-
Image
 Objective: - This blog aims to give a comprehensive overview of the process for integrating containerized network services in a multi-vendor setting, specifically using Nokia Service Routers (SR) and Juniper Aggregation Routers (AG). It emphasizes the importance of NNI interface policies for facilitating smooth communication between different network segments and provides guidance on configuring management interfaces and routing to optimize connectivity and traffic flow. The goal of this guide is to help network engineers implement scalable and interoperable solutions while making complex network operations easier to manage. Scenario :- In Vodafone ISP, Pune location 2 SR non-production devices need to be launched in production. Router R1 acts as a primary and Router R2 acts as a secondary back up router. Both routers aggregate traffic combines at uplink Nasik Aggregate router. This uplink is connected with IXR router at Mumbai location. To automate process flow AWS containers are...
Read more

Designing a Secure Multi-VPC Architecture with AWS Transit Gateway and IGW

-
Image
 Preface In an AWS cloud Proof of Concept (PoC), Transit Gateway (TGW) and Internet Gateway (IGW) are key to secure, scalable and efficient communication between different VPCs and external networks. Transit Gateway (TGW) is a central routing hub where multiple VPCs can communicate without the complexity of multiple VPC peering connections. It simplifies network management, scales and enforces security policies through route tables to control traffic between connected VPCs. Internet Gateway (IGW) is required for outbound and inbound internet access for resources in public subnets. It allows public facing workloads like web servers and APIs to talk to external services while keeping private subnets secure through NAT Gateways . Together TGW and IGW provide a structured and controlled networking environment, so critical workloads are secure, isolated when needed and connected efficiently in a multi-VPC architecture. POC  The proposed Proof of Concept (PoC) focuses on estab...
Read more

AI in NOC: A New Era for Capacity Planning and Network Management

-
Image
   Introduction :- Predicting router interface traffic in modern network management is critical to achieve optimal network performance, resource allocation, and proactively eliminate bottlenecks. This case study suggests using machine learning on network datasets to develop a model that predicts an actual router’s interface traffic versus an ideal router’s traffic. By evaluating historical data of network traffic and utilizing well-established machine learning API-based algorithms like Neural Networks, Decision Trees, and Ensemble Methods, this analysis reviews the formation possibilities of a strong prediction model with grand accuracy. At the end of the study, this paper reviews multiple factors and features related to the traffic in the interface such as the hour in the day, the day’s sequence in the week, the network protocol, the application, and the structure of the network. Additionally, it explores the machine learning algorithms to compare the accuracy of the ML model...
Read more