Browse Prior Art Database

END-TO-END MULTICAST TRAFFIC REDUNDANCY IN NETWORKS

IP.com Disclosure Number: IPCOM000248110D
Publication Date: 2016-Oct-26
Document File: 8 page(s) / 485K

Publishing Venue

The IP.com Prior Art Database

Related People

Nagendra Kumar Nainar: AUTHOR [+4]

Abstract

Presented herein are methods and systems relating to end-to-end (E2E) multicast traffic redundancy in professional media networks, information-centric networks (ICN), and content-centric networks (CCN). One objective is to bind the path computation capability of a Path Computation Element (PCE) to a multipoint data distribution (e.g., multicast traffic) over both existing and new technologies (e.g., Protocol Independent Multicast (PIM), MultiPoint Label Distribution Protocol (mLDP), Bit Index Explicit Replication (BIER), etc.). Also provided is an E2E disjointed path and maximum redundancy for media traffic (e.g., video) using multicast. A designated router (DR) and a backup DR for a local area network (LAN) queries the server for disjointed paths toward a source by sending a request with a LAN identification (ID), which is used by the server to calculate a disjointed path and stream details.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 23% of the total text.

Page 01 of 8

END-TO-END MULTICAST TRAFFIC REDUNDANCY IN NETWORKS

AUTHORS:

Nagendra Kumar Nainar Rajiv Asati
Carlos M. Pignataro

Richard Furr

CISCO SYSTEMS, INC.

ABSTRACT

    Presented herein are methods and systems relating to end-to-end (E2E) multicast traffic redundancy in professional media networks, information-centric networks (ICN), and content-centric networks (CCN). One objective is to bind the path computation capability of a Path Computation Element (PCE) to a multipoint data distribution (e.g., multicast traffic) over both existing and new technologies (e.g., Protocol Independent Multicast (PIM), MultiPoint Label Distribution Protocol (mLDP), Bit Index Explicit Replication (BIER), etc.). Also provided is an E2E disjointed path and maximum redundancy for media traffic (e.g., video) using multicast. A designated router (DR) and a backup DR for a local area network (LAN) queries the server for disjointed paths toward a source by sending a request with a LAN identification (ID), which is used by the server to calculate a disjointed path and stream details.

DETAILED DESCRIPTION

     In professional media networks, information-centric networks (ICN), and content-centric networks (CCN), multicast plays a key role in delivering video and other media traffic to multiple receivers. Such traffic is known to be a service-level agreement (SLA) constraint in terms of packet loss, jitter, and delay. Currently, multicast-only fast reroute (MoFRR) helps to achieve the resiliency for such multicast traffic. MoFRR for multicast traffic is useful in Internet Protocol (IP)/PIM network environments, to a

Copyright 2016 Cisco Systems, Inc.

1


Page 02 of 8

certain extent. However, this does not guarantee E2E redundancy to alleviate any loss/delay along the path, including the last-hop router (LHR).

Figure 1

    As illustrated in Figure 1 above, fate sharing is an ongoing problem. For example, E2E traffic suffers failure if one of the Ingress/First-Hop-Router (R1), transit R2, or Egress/Last-Hop-Router (R4) fails or faces intermittent drops/delays.

    With the introduction of Software Defined Networking (SDN), operators are interesting in controlling the traffic path from a central intelligence point. Methods presented herein leverage this concept and help achieve traffic protection by creating an E2E disjointed path for primary and backup video traffic. These methods provide the following protections:

Transit Path Protection


LHR protection
First-Hop Router (FHR) protection

Copyright 2016 Cisco Systems, Inc.

2


Page 03 of 8

Figure 2

    For each PIM-enabled LAN, the PIM selects a DR that is responsible for building the tree toward a relying party (RP)/source and registering the RP/source. As illustrated in Figure 2, R4 acts as the DR (i.e., the primary LHR) and builds the tree towards R1 connecting the source. Leveraging the centralized intelligence and PCE enables this method to be useful in scenarios in which the cloud is PIM, mLDP, or BIER based.

    The primary LHR sends a path-q...