Scribd
Upload
61 views6 pages

IPTV Channel Addition Issues and Way Forward

PTCL is expanding its IPTV service capacity and adding new channels. Some legacy network devices have limited bandwidth, so simply adding all new streams could overload them. Two solutions are proposed: 1) Upgrade devices to have more bandwidth or 2) Selectively block certain streams from being continuously sent to problematic devices, instead sending only requested streams to avoid overloading uplinks. Blocking specific streams can be done through IGMP policies while still allowing customers to view those channels upon request. This achieves the goal of protecting device uplinks without degrading the viewing experience.

Uploaded by

muhammad farooq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
61 views6 pages

IPTV Channel Addition Issues and Way Forward

PTCL is expanding its IPTV service capacity and adding new channels. Some legacy network devices have limited bandwidth, so simply adding all new streams could overload them. Two solutions are proposed: 1) Upgrade devices to have more bandwidth or 2) Selectively block certain streams from being continuously sent to problematic devices, instead sending only requested streams to avoid overloading uplinks. Blocking specific streams can be done through IGMP policies while still allowing customers to view those channels upon request. This achieves the goal of protecting device uplinks without degrading the viewing experience.

Uploaded by

muhammad farooq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Static Join blocking,

IPTV Channels Addition Challenges, and proposed


IP Planning way forward
Table of Contents
1. Background:.......................................................................................................................................................... 2
2. Problem Statement: ............................................................................................................................................ 2
3. Possible Solution:................................................................................................................................................. 2
3.1 Blocking Stream from Static join................................................................................................................ 2
PIM......................................................................................................................................................................... 3
IGMP ...................................................................................................................................................................... 4
Static Join Stream Blocking .................................................................................................................................. 4
4. Annexure A: .......................................................................................................................................................... 5
1. Background:
In 2022, PTCL initiated a project to enhance its IPTV services by expanding the subscriber
capacity by 50,000 and adding 50 SD and 50 HD channels. This addition will supplement the
existing setup of 150 SD and 10 HD channels, resulting in a total of 260 channels (200 SD, 60
HD).

2. Problem Statement:
To provide a seamless customer experience with reduced channel switching time, all Metro
node multicast interface (TrunkNo.3999) are configured with static join.
While this configuration enhances customer satisfaction, it also results in the continuous
availability of all streams on the MSAGs, consuming their uplink bandwidth.

The induction of these additional channels will result in an additional 600 Mbps of multicast
traffic within the network. However, certain PTCL legacy Access devices (MSAGs) have limited
available uplink bandwidth[Annex A]. Consequently, adding new multicast streams to these
nodes will negatively impact all the services they provide.

3. Possible Solution:
To address this issue, two potential solutions have been identified:
1. Expand the uplinks of the problematic nodes or upgrade the nodes themselves. This
would involve increasing the bandwidth capacity of the affected MSAGs to
accommodate the increased multicast traffic.
2. Instead of transmitting all streams to these MSAGs, selectively send only the selected
streams which do not overwhelm available bandwidth.

Note: as swapping/ upgrading legacy nodes is slow and gradual process therefore solution 2 as briefed below
can be used for the inter

3.1 Blocking Stream from Static join

Implementing Policies on Metro node interfaces connected with problematic nodes can prevent
Access nodes to join certain Multicast streams by blocking though policy.
Even though this will block the unwanted stream and protect the MSAG’s uplink, this will also
introduce a problem to showing blank screen on TV for all the channels which has been blocked
if IGMP request could not reach the router. This might impact the user experience.

Below section explains the how the multicast is handled in core network now and how we can
prevent certain streams from reaching MSAG,

PIM
In PTCL network, PIM-SSM has been used and set SSM address range to 239.194.0.0/16 &
232.0.0.0/8, also hello timer has been set to 10S.
Corresponding configuration is as following:
acl name ACL_SSM_RANGE basic
rule 10 permit source 239.194.0.0 0.0.255.255
rule 20 permit source 232.0.0.0 0.255.255.255
##
pim
ssm-policy acl-name ACL_SSM_RANGE
timer hello 10
#
interface eth-trunk10
pim sm
#

IGMP
In PTCL IP network, IGMPv2 and SSM-Mapping has been used to support PIM-SSM.
Corresponding configuration is as following:
igmp
ssm-mapping 239.194.0.0 255.255.255.0 182.176.51.201
ssm-mapping 239.194.2.0 255.255.255.0 182.176.51.201
#
acl number 2102
description IGMP join control for SD and HD both
rule 5 permit source 239.194.0.0 0.0.0.255
rule 10 permit source 239.194.2.0 0.0.0.255
#
interface Eth-Trunk6
pim sm
igmp enable
igmp group-policy 2102
igmp ssm-mapping enable
igmp static-group 239.194.0.0 inc-step-mask 0.0.0.1 number 256 source
182.176.151.41
igmp static-group 239.194.0.0 inc-step-mask 0.0.0.1 number 256 source
182.176.151.44
#

Static Join Stream Blocking


To achieve the target of blocking specific channels stream to be sent on access side by static join,
it is required to remove those channel group addresses from multicast static join group range
under the interface. Corresponding configuration is as below

igmp
ssm-mapping 239.194.0.0 255.255.255.0 182.176.51.201
ssm-mapping 239.194.2.0 255.255.255.0 182.176.51.201
#
acl number 2102
description IGMP join control for SD and HD both
rule 5 permit source 239.194.0.0 0.0.0.255
rule 10 permit source 239.194.2.0 0.0.0.255
#
interface Eth-Trunk6
pim sm
igmp enable
igmp group-policy 2102
igmp ssm-mapping enable
igmp static-group 239.194.0.0 inc-step-mask 0.0.0.1 number 100 source
182.176.151.41
igmp static-group 239.194.0.110 inc-step-mask 0.0.0.1 number 20 source
182.176.151.41 //The channels with IP address range from 239.194.0.100 to
239.194.0.109 will only be pushed after customer request.
#

Once done, channels stream whose group addresses have been removed will only be sent to
access side after receiving an igmp join request. The remaining channels stream will be sent
continuously.

Note: Based on the available bandwidth on each problematic MSAG, configure the multicast
join settings accordingly. The list of channels for each site will be provided by the commercial
team.

4. Annexure A:

No Feasibile MSAG
details.xlsx

You might also like