# Design of an IPTV Multicast System for Internet Backbone Networks

Authors: T. H. Szymanski; D. Gilbert
Journal: International Journal of Digital Multimedia Broadcasting
 (2010)

---

## Abstract

The design of an IPTV multicast system for the Internet backbone network is presented and explored through extensive simulations. In the proposed system, a resource reservation algorithm such as RSVP, IntServ, or DiffServ is used to reserve resources (i.e., bandwidth and buffer space) in each router in an IP multicast tree. Each router uses an Input-Queued, Output-Queued, or Crosspoint-Queued switch architecture with unity speedup. A recently proposedRecursive Fair Stochastic Matrix Decomposition algorithm used to compute near-perfect transmission schedules for each IP router. The IPTV traffic is shaped at the sources using Application-Specific Token Bucker Traffic Shapers, to limit the burstiness of incoming network traffic. The IPTV traffic is shaped at the destinations using Application-Specific Playback Queues, to remove residual network jitter and reconstruct the original bursty IPTV video streams at each destination. All IPTV traffic flows are regenerated at the destinations with essentially zero delay jitter and essentially-perfect QoS. The destination nodes deliver the IPTV streams to the ultimate end users using the same IPTV multicast system over a regional Metropolitan Area Network. It is shown that all IPTV traffic is delivered with essentially-perfect end-to-end QoS, with deterministic bounds on the maximum delay and jitter on each video frame. Detailed simulations of an IPTV distribution system, multicasting several hundred high-definition IPTV video streams over several essentially saturated IP backbone networks are presented.


---

## Body

## 1. Introduction

Multimedia traffic such as IPTV and video-on-demand represent a rapidly growing segment of the total Internet traffic. According to Cisco [1, 2], global Internet traffic is nearly doubling every 2 years, and global capacity will have to increase 75 times over the decade 2002–2012 to keep up with the demand. Furthermore, video-based traffic such as IPTV [3] will represent 90% of global network loads in 2012. The US Federal Communication Commission (FCC) has required that all TV broadcasts occur in digital format in 2009, and the growing fraction of multimedia traffic threatens to overwhelm the current Internet infrastructure.  According to [4], “The United States will not be the first country to complete the transition to digital television… Luxembourg, the Netherlands, Finland, Andorra, Sweden, and Switzerland have all completed their transitions, utilizing the Digital Video Broadcasting—Terrestrial (DVB-T) standard. Transitions are now under way in more than 35 other countries." According to Cisco [5]: “With the deployment of these new IPTV services, existing network infrastructures will be pushed to their limits.” The congestion problems are already visible: “Video is clogging the internet. How we choose to unclog it will have far-reaching implications” [6]. Recognizing the problems, the US National Science Foundation initiated a major project called “Global Initiative for Network Investigations” (GENI), which is open to a complete “clean slate” redesign of Internet if necessary, in an attempt to address the problems [7, 8]. In summary, new technologies which support the efficient multicasting and broadcasting of multimedia services such as IPTV are essential.In this paper, the design of an IPTV multicast system for Internet backbone networks is presented and explored through extensive simulations. An IPTV multicast system was first proposed in [9] based upon a theoretical foundation established in [10, 11]. Extensive simulations where presented for an 8-node multicast tree in [9], however the design or simulation of a multicast system for a real IP network topology was not presented.In this paper, the design of a realistic IPTV multicast system for several real backbone IP networks described in [12] is presented. Exhaustive simulations confirm that the system can deliver several hundred IPTV packet streams over the Internet backbone networks with essentially zero delay jitter, essentially zero packet loss rate, and essentially-perfect end-to-end QoS for every provisioned multicast tree. In the proposed system, a resource-reservation algorithm such as RSVP, IntServ, or DiffServ is used to reserve resources such as buffer space and transmission capacity in each multicast router in each multicast tree. Each IP router then uses a recently proposed Recursive Fair Stochastic Matrix Decompositionscheduling algorithm [9, 10] to schedule the IPTV traffic streams through the router while meeting rigorous QoS guarantees, under the constraint of unity speedup.Internet routers can use three basic switch architectures, theInput-Queued (IQ) switch, the Output-Queued (OQ) switch, or the Combined Input and Crosspoint Queued  (CIXQ) switch. OQ switches can achieve optimal throughput but they require an internal speedup of O(N), which renders them impractical for large sizes. Combined Input and Output Queued (CIOQ) switches have also been proposed. These switches can also achieve 100% throughput, but they also require a speedup typically by a factor of 2 or 4, which is difficult to realize and which increases costs. CIXQ switches can also achieve 100% throughput with simpler scheduling algorithms, but they require many crosspoint queues in the switching matrix which increase costs. To minimize costs, many high capacity routers exploit some form of Input Queueing. Figure 1 illustrates a packet-switched IP router using an N×NInput-Queued (IQ) switch architecture. Each input port has N “Virtual Output Queues” (VOQs), and the switch has a total of N2VOQs. Figure 2 illustrates a packet-switched IP multicast tree, which consists of a tree of packet-switched IP routers as shown in Figure 1.Figure 1
IQ switch.Figure 2
2. IPTV Multicast tree.Many IP routers exploit a fixed-sized cell switching architecture. Variable-sized IP packets containing video data arrive at the input ports. Each IP packet is disassembled into small fixed-sized cells, which are stored in the appropriateVOQ at the input side of the switch. Typical cells can be between 64 and 256 bytes in length. At each input port j, each VOQ(j,k) stores cells destined for output port k. The fixed-sized cells are scheduled for transmission across the switch in a series of time slots. The variable-sized IP packets are reconstructed at the output side of the router and are then transmitted to the next router in the multicast tree. In each time slot, a scheduling algorithm is used to compute a set of up to N cells to transfer across an IQ switch, subject to two constraints: (1) each input port transmits at most 1 cell from its N VOQs, and (2) each output port receives at most 1 cell from any VOQ.  The set of cells to transmit per time slot can be represented as a permutation.Scheduling for IQ switches is known to be a difficult problem [13–27]. The difficulty is compounded when Quality-of-Service (QoS) constraints are added to the scheduling problem. It is has been shown that effective IPTV delivery requires low jitter [28–30]. The selection of a set of N cells to transfer per time-slot in an IQ switch is equivalent to finding a matching in a bipartite graph. Assuming link rates of 40 or 160 Gbps, the durations of a time-slot for a 64-byte cell are 12.8 and 3.2 nanoseconds, respectively. Therefore, schedulers for IQ switches must compute new bipartite graph matchings very quickly, typically at rates of 100–300 million matchings per second. Existing switch schedulers can be classified into two classes: (1) “Dynamic schedulers” which compute new bipartite matchings in every time-slot without any a priori knowledge of the long-term traffic demands on the switch, and (2) “Guaranteed-Rate (GR) schedulers” which periodically compute a sequence of F matchings to be used in F consecutive time slots called a “scheduling frame”. The schedules can be reused repeatedly, and the schedule is recomputed when the long-term traffic demands of the switch are modified.It is known that dynamic schedulers for IQ switches can achieve 100% throughput, if aMaximum Weight Matching (MWM) algorithm is used to compute the matching for each time-slot, where the largest queues receive preferential service [13]. However, the MWM algorithm has complexity O(N3) work per time-slot and is considered intractable for use in real IP routers [13]. Therefore, existing dynamic schedulers typically use sub optimal heuristic schedulers, such as Parallel Iterative Matching or iSLIP [14]. However, due to the severe time constraints all heuristic schedulers have sub optimal throughput efficiencies and exhibit significant delay and jitter at high loads. The iSLIP algorithm used in the Cisco 1200 series routers is an iterative heuristic scheduler which can achieve throughput efficiencies as high as 80% for non uniform traffic patterns. However, the average queuing delay per cell can approach several thousand time slots at high loads, and the delay jitter can be equally high.In this paper, a recently proposedRecursive Fair Stochastic Matrix Decompositionalgorithm is used to schedule multicast IPTV traffic in each router in an IP multicast tree in a fully saturated IP network, and the performance is examined through extensive simulations. A resource-reservation protocol such as RSVP, IntServ, or DiffServ is used to maintain a traffic rate matrix for each IP router. (We note that while DiffServ does not use explicit resource reservation, DiffServ does use class-based weighted fair queueing, which effectively reserves bandwidth for each Diffserv traffic class.) Each traffic rate matrix is doubly sub stochastic or stochastic, and specifies the guaranteed traffic rates between every pair of Input-Output (IO) ports of the router. The traffic matrix in each router can then be mathematically decomposed to yield a sequence of bipartite graph matchings or permutations. Each matching configures the switch for one time-slot, and the sequence of matchings is guaranteed to deliver the IPTV stream through the IP router while providing rigorous QoS guarantees, under the constraint of unity speedup.TheRecursive Fair Stochastic Matrix Decomposition (RFSMD) algorithm proposed in [10] converts an admissible traffic rate matrix for a router into a quantized (integer) matrix with integer-valued elements, assuming a scheduling frame of length F time slots. The algorithm then recursively partitions the quantized matrix in a recursive and relatively fair manner, yielding a sequence of permutation matrices, also called permutations. The resulting sequence of permutations forms a “frame transmission schedule”, for transmitting cells through the packet-switched IP router. The sequence of permutations in a frame transmission schedule can be repeatedly reused, as long as the traffic rate matrix remains unchanged. When the traffic rate matrix is updated by the RSVP, IntServ, or DiffServ algorithm, the frame transmission schedule can be recomputed. The RFSMD algorithm, along with appropriate traffic shaping at the sources, rigorously guarantees that every provisioned traffic flow achieves near-minimal delay and jitter and essentially-perfect end-to-end QoS, for all networks loads up to 100%. By “essentially-perfect QoS”, we mean that every provisioned traffic flow can be delivered with zero packet loss rate, nearminimal end-to-end delay and zero network-introduced delay jitter. Theoretical bounds on the delay, jitter and QoS are presented in [10, 11] and are summarized in Section 4 of this paper. In this paper, we apply the RFSMD scheduling algorithm to the problem of multicasting real IPTV traffic through multicast trees in several real IP backbone networks, to explore the feasibility of large-scale IPTV multicasting in IP networks.Section2 describes video traffic model. Section 3 describes some prior guaranteed-rate scheduling algorithms. Section 4 describes the low-jitter RFSMD scheduling algorithm in more depth. Section 5 describes the IP backbone networks and the IPTV multicast trees, and presents detailed simulation statistics. Section 6 contains concluding remarks.


## 2. Video Traffic Model

Cisco Systems estimates that several hundred video channels requiring up to 1 Gbps bandwidth may be distributed over the IP backbone to support emerging IPTV applications [5]. To gather realistic data for our simulations, a high-definition video stream entitled “BBC Blue Planet” available at the University of Arizona [31] website was processed. The video stream includes  61 K video frames which arrive at the rate of 24 video frames/sec. The minimum, mean, and maximum video frame sizes are 81, 21 K, 495 K bytes respectively, illustrating a very bursty behaviour.We assume these video frames are disassembled into fixed-sized 64-byte cells before transmission into the IP multicast tree. These video frame sizes correspond to a mean of 328 cells per video frame, with a minimum and maximum of 2 and 7,735 cells per video frame, respectively. The single video stream has a compression ratio of 151, with a mean bit rate of about 4 Mbps, and a peak bit rate of 95 Mbps. To simplify the terminology, define this data to represent a single “video channel”. A“video stream” consists of the aggregation of 1 or more video channels.The Arizona website [31] provides video frame size statistics for a few high-definition video channels. In this paper, we assume 100 high-definition video channels are to be multicast in each multicast tree, each with a 4 Mbps average rate, for an aggregate stream traffic rate of approximately. 404 Mbps. To achieve the statistics for the 100 video channels used in our network simulations, the data for the video “BBC Blue Planet” was reused in a circular manner, with a randomly selected starting video frame for each channel.Table1 lists some properties of the single video channel and several aggregated video traffic streams. In Table 1, the ratio of the peak-to-mean rates is an indication of the burstiness of the traffic. The single channel has a peak-to-mean ratio of 23.5, indicating a high degree of burstiness. Referring to Table 1, the aggregated stream of 100 channels has an aggregate data rate of 404 Mbps, with a peak rate of 700 Mbps. The ratio of peak-to-mean rates is 1.73, indicating a considerable reduction in burstiness.Table 1
Statistics on aggregated traffic.
ChannelsMean Rate(Mbps)Max RateMax/MeanStandard Deviation10% extra cap delay (sec)14.049523.56.6897.11040.41654.082145.41004047001.73694.35Figure3 illustrates visually the effect of aggregation of multiple video channels on the burstiness of the aggregated video stream. Figure 3 illustrates the instantaneous normalized bandwidth versus time for the same aggregated streams. The mean rate of each stream has been normalized to 1, and the reduction in burstiness when many video channels are aggregated is evident.Figure 3
Burstiness of aggregated traffic.Assume that video frames for any one video channel arrive at the root of a multicast tree at the fixed rate of 24 video frames per second. The arrival rate of video frames for the aggregated stream of 100 channels is therefore 2,400 video frames per second. The arriving traffic is quite bursty, as shown in Figure3.In this paper, we assume anApplication-Specific Token Bucket Traffic Shaper (ASTS)module [9, 11] is used at the source to smoothen incoming bursty IPTV traffic to conform to an appropriate mean traffic rate with bounded burstiness. Cells are allowed to depart the ASTS at the maximum rate of 440 Mbps, when cells are available. The ASTS will introduce an application-specific delay at the source which is independent of the network. Referring to Figure 2, assume that the 100 video channels are available at the root of each IP multicast tree for distribution. The aggregated stream of 100 channels has an average data rate of 404 Mbps, and each IP multicast tree must be provisioned to support this traffic. In this paper, we assume that each IP multicast tree is provisioned such that the average data rate of the aggregated video stream consumes 90% of the provisioned tree link capacity, thereby providing 10% excess bandwidth for bursts. Therefore, each IP multicast tree must be provisioned to support about 440 Mbps of guaranteed rate traffic on every link in the tree. Given the line rate of 40 Gbps, the use of 64-byte cells, and a scheduling frame of length F=1K, then each time-slot reservation represents a bandwidth of approximately 40 Mbps. Therefore, a guaranteed rate of 440 Mbps requires the reservation of 11 cells per scheduling frame, or about 1% of the line rate. However, each backbone network has multiple IPTV multicast trees, between 9 and 16 trees in our simulations, so the fraction of multicast traffic on each link will be typically between 4% and 7% of the link capacity in our models. When bursts of cells arrive at the ASTS module, these cells will be temporarily stored, and will be released into the network at an average rate of 400 Mbps and a maximum data rate of 440 Mbps.Referring to Figure2, the router no.1 is the root of a multicast tree and implements a 1-to-3 multicasting of the cells. There are many nodes in an IP multicast tree, distributing content to potentially millions of end-users (i.e., households). Each destination node of the multicast tree has an Application-Specific Playback Queue (ASPQ) [9, 11] which receives the fixed-sized cells corresponding to the aggregated video stream. The purpose of the ASPQ is to filter out residual network-introduced jitter and reconstruct the original bursty video frames. The destination nodes in an Internet backbone network may represent a Central Office in a city. The Central Office node must deliver the IPTV streams to the ultimate end-users, which are the residential homes or mobile phones, and so forth, over a regional Metropolitan Area Network. The delivery of the IPTV traffic over the regional Metropolitan Area Network can use the same IPTV multicast design described in this paper. Therefore, bursty IPTV traffic flows can be delivered to the ultimate end-users in a hierarchical manner, with essentially zero delay jitter, with essentially zero packet loss rates and with essentially-perfect end-to-end QoS.IP networks typically transmit variable-sized IP packets. Packets are typically disassembled into fixed-sized cells at the input size of each IP router, and IP packets are reassembled at the output size of the IP router, before they are transmitted to the next IP router. The use of variable-sized IP packets typically leads to delays associated with disassembling and reassembling IP packets in each IP router. In this paper, we assume an IP/MPLS technology, where all IP packets carrying video data have a fixed size, for example 64 bytes, 1024 bytes, or 1500 bytes. IP packets are disassembled once at the ingress router and reassembled once at the egress router of an MPLS domain. This assumption eliminates the need to repeatedly disassemble and re-assemble variable-sized IP packets at each IP router within one domain, and removes the packet reassembly delay in each IP router. However, the main results hold even if large fixed-sized packets are used (i.e., 1500 bytes), or if variable size packets are used. In this case, the packet reassembly delay must be added to each router. The important point is that all variable queueing delays and jitter have been removed.


## 3. Prior Guaranteed-Rate Scheduling Algorithms

Several schemes have been proposed for scheduling guaranteed-rate (GR) traffic through an IQ packet switch, which are briefly reviewed. All of the schemes discussed in this section assume that every router maintains a traffic rate matrix, which specifies the requested traffic rates between all IO pairs in the router.In the Birkoff von-Neuman (BVN) scheme proposed in [17, 18], a doubly stochastic traffic rate matrix is decomposed into a sequence of permutation matrices and associated weights. Each matrix represents a switch configuration, that is, a matching or permutation of input ports onto output ports. These matrices are then scheduled to appear in proportion to their weights using the GPS or WFQ algorithm, to determine the sequence of switch configurations which meet the GR traffic requirements. Each switch configuration is used to configure the packet switch for one time-slot. Best-Effort IP traffic can then use any switching capacity not used by GR traffic. The BVN decomposition can achieve 100% throughput through a router, that is, it does not introduce “speedup” at any router, However, the BVN decomposition has a time complexity of O(N4.5) in a serial processor and is generally considered too slow for use in real-time packet-switched IP routers.An algorithm to schedule traffic through an IQ packet-switched IP router, while attempting to minimize the“service lag” amongst multiple competing IP flows and to minimize the speedup, was developed at MIT [16]. A doubly stochastic traffic rate matrix is first quantized to contain integer values and then is decomposed into a series of permutation matrices and associated weights, which then must be scheduled. With speedup S=1+sN between 1 and 2, the maximum service lag (defined ahead) over all IO pairs is bounded by O((N/4)(S/(S-1))) time slots. According to [16]; “with a fairly large class of schedulers a maximum service lag ofO(N2)is unavoidable for input queued switches. To our knowledge, no scheduler which overcomes thisO(N2)has been developed so far. For many rate matrices, it is not always possible to find certain points in time for which the service lag is small over all IO pairs simultaneously."A greedy scheduling algorithm which attempts to  minimize the delay jitter amongst simultaneous competing IP flows through an IQ packet switch was developed at Bell Labs [19, 20]. The traffic demand is specified in an N×N traffic rate matrix. The low-jitter GR traffic is constrained to be a relatively small fraction of the total traffic. The delay and jitter minimization problem is first formulated as an integer programming problem. The traffic rate matrix must be decomposed into a set of permutation matrices and associated weights, such that each traffic flow is supported by exactly one permutation in the set. This matrix decomposition problem was shown to be NP-HARD. They then formulate a greedy low-jitter decomposition with complexity O(N3) time. The resulting schedule requires a worst-case speedup of O(log N), which renders it costly in practice. Hard analytic bounds on the jitter were not available.A heuristic scheduling algorithm for scheduling packets in an IQ switch was developed at the UCR [21]. The algorithm attempts to decompose an admissible integer traffic rate matrix into the sum of integer matrices, where the maximum row or column sums of the matrices represent a decreasing geometric sequence. The authors establish a jitter bound which grows as the switch size N increases, and identify an open problem “to determine the minimum speedup required to provide hard guarantees, and whether such guarantees are possible at all” [21].In summary, there is a considerable body of recent research into mathematical scheduling algorithms based upon the decomposition of traffic rate matrices. Unfortunately, tractable scheduling algorithms which achieve stability within the capacity region or which achieve bounded delays or jitter under the constraint of unity speedup, in one IP/MPLS router or a network of IP/MPLS routers, are unknown.


## 4. The Recursive Fair Stochastic Matrix Decomposition Algorithm

AnN×M packet switch has N input and M output ports, and an associated traffic rate matrix. Each input port j for 0≤j<N has M Virtual Output Queues, one for each output port k, 0≤k<M. The guaranteed-rate traffic requirements for an N×N packet switch can specified in a doubly sub stochastic or stochastic traffic rate matrix Λ:(1)Λ=(λ0,0λ0,1⋯λ0,N-1λ1,0λ1,1⋯λ1,N-1⋯⋯λN-1,0λN-1,1⋯λN-1,N-1),∑i=0N-1λi,j≤1,∑j=0N-1λi,j≤1.Each elementj,k represents the fraction of the transmission line rate reserved for guaranteed-rate traffic between IO pair (j,k). The transmission of cells through the switch is governed by the frame transmission schedule, also called a “frame schedule”. In an 8×8 crossbar switch with F=128 time slots per frame, the minimum allotment of bandwidth is 1/F=0.78% of the line rate, which reserves one time-slot per frame on a recurring basis. Define a new quantized traffic rate matrix R where each traffic rate is expressed as an integer number times the minimum quota of reservable bandwidth:(2)R=(R0,0R0,1⋯R0,N-1R1,0R1,1⋯R1,N-1⋯⋯RN-1,0RN-1,1⋯RN-1,N-1),∑i=0N-1Ri,j≤F,∑j=oN-1Ri,j≤F.Consider two classic underlying theories from the field of graph theory and combinatorial mathematics, summarized in [10, 16–21]. Theorem 1 states that any integer matrix with a maximum row or column sum of F can be expressed as the sum of F permutation matrices. Theorem 2 states that any doubly sub stochastic or stochastic matrix can be decomposed into a convex set of permutations matrices and weights. All of the matrix decomposition algorithms reviewed in Section 3 attempt to exploit the above 2 theorems. They all are based upon the decomposition of a given traffic rate matrix into a convex set of constituent permutation matrices and associated weights, such that the weighted sum of the permutation matrices equals the original traffic rate matrix. Unfortunately, problems in combinatorial mathematics are difficult to solve efficiently, due to the large number of combinations that must be considered in any solution. As shown in Section 3, the problem of scheduling traffic to achieve zero jitter in minimum time is NP-HARD. All the algorithms reviewed in Section 3 (except for the BVN algorithm) require the introduction of “speedup” to the switches to achieve a decomposition, which limits their practical applicability. The BVN decomposition does not require a speedup, but its complexity is O(N4.5) on a serial processor, which is considered intractable given that current Internet routers must compute decompositions at the rates of 100–300 million permutation matrices per second.TheRecursive Fair Stochastic Matrix Decomposition algorithm presented in [10] is an efficient deterministic algorithm to decompose an admissible traffic rate matrix into a sum of permutation matrices under the constraint of unity speedup. Let P(M,F) denote the problem of scheduling an admissible quantized traffic rate matrix M into a scheduling frame of length F time slots, as shown in Figure 5. In particular, an integer matrix M with a maximum row or column sum of F must be partitioned into two integer matrices M1 and M2, each with a maximum row or column sum of F/2. More specifically, the scheduling problem P(M,F) must be recursively decomposed into 2 smaller scheduling problems P(M1,F/2) and P(M2,F/2), such that the integer matrices M1+M2=M, where M1 and M2 are admissible integer traffic rate matrices, and for all j and k where 0≤j≤N and 0≤k≤N, then M1(j,k)≤M2(j,k)+c and M2(j,k)≤M1(j,k)+c for c=1. This step of partitioning an integer matrix into 2 integer matrices is a problem in combinatorial mathematics.  The RFSMD algorithm achieves the decomposition by transforming one combinatorial problem into another combinatorial problem with a recently proposed solution. In particular, the problem of decomposing an integer matrix relatively fairly into 2 integer matrices is transformed into the problem of routing permutations in a rearrangeably nonblocking switching network [10]. An efficient algorithm for the combinatorial problem of routing permutations in rearrangeable networks was proposed in [10].The recursive nature of the RFSMD algorithm yields a very efficient decomposition. The decomposition of anN×N integer matrix with a maximum row or column sum of F can be accomplished in O(NFlog (NF)) time. The decomposition yields F permutations or bipartite graph matchings, which can configure the switch for F time slots. The computational complexity for each computed permutation of N elements is therefore O(Nlog (NF)) time on a serial processor, which is near optimal.The RFSMD algorithm also partitions each matrixM relatively fairly, so that the two smaller matrices M1 and M2 differ by at most 1 in any position. As a result, the traffic in the original scheduling problem is scheduled relatively fairly over the 2 smaller scheduling problems. This relatively fair recursive partitioning leads to a bound on the maximum jitter for any traffic flow, and a bound for the maximum normalized service lead or maximum normalized service lag for any scheduled traffic flow (these terms are formally defined in the next paragraphs). The bounded normalize service lead/lag can be used to create bounds on the end-to-end QoS for every scheduled traffic flow, as will be shown ahead.One step in the decomposition for a 4×4 matrix operating at 99.2% load with unity speedup is shown in (3). Given an N×N switch and a fixed scheduling frame length F, the RFSMD matrix decomposition algorithm [10] bounds the normalized service lead and service lag for the aggregated traffic leaving any node to ≤k·IIDT time slots for constant K, where IIDT represents the “Ideal Interdeparture Time” for cells belonging to the aggregated traffic leaving an edge. Furthermore, the bound applies to all individual competing traffic flows traversing each edge, provided that cells are selected for service within each VOQ according to a GPS scheduling algorithm
(3)[106222326345177216303326459232183147282352211178]=[5311116317288108152163230116917414117610589]+[5311116317389108151163229116927314117610689].Each smaller scheduling problem contains approximately one half of the original time-slot reservation requests, and has as smaller scheduling frame of lengthF/2 time slots to realize these reservation requests, as shown in Figure 5. Repeated application of the relatively fair recursive partitioning results in a sequence of partial or full permutation matrices which determine the IQ switch configurations, called the frame transmission schedule. Due to the relatively fair recursive partitioning, the service a traffic flow receives in each half of the frame schedule will be relatively fair, and the delay jitter will be relatively small.Several of the following definitions from [10] will be useful to interpret the simulation results to be presented in Section 6.Definition 1.
A “Frame transmission schedule” of length F is a sequence of partial or full permutation matrices (or vectors) which define the crossbar switch configurations for F time slots within a scheduling frame. Given a line rate L, the frame length F is determined by the desired minimum quota of reservable bandwidth =L/F. To set the minimum quota of reservable bandwidth to  ≤1% of L, set F≥100,that is, F=128.Definition 2.
The “Ideal Interdeparture Time” denoted IIDT(i,j) of cells in a GR flow between IO pair (i,j) with quantized rate R(i,j) time-slot reservations in a frame of length F, given a line rate L in bytes/sec and fixed-sized cells of C bytes, is given by: IIDT(i,j)=F/R(i,j) time slots, each of duration (C/L) sec. (The subscripts will be suppressed when possible.)Definition 3.
The “Ideal Service Time” (ST) of cell 0≤c≤R(i,j) in a GR flow between IO pair (i,j) with an Ideal Interdeparture Time  of IIDT(i,j) is given by ST=j*IIDT(i,j) time slots.Definition 4.
The “Received Service” of a flow with quantized guaranteed rate R(i,j) at time-slot t within a frame of length F, denoted Sij(t), equals the number of permutation matrices in time slots 1…t, where 1≤t≤F, in which input port i  is matched to output port j.Definition 5.
The “Service Lag” of a flow between input port i and output port j, at time-slot t within a frame of length F, denoted Lij(t), equals the difference between the requested quantized GR prorated by t/F, and the received service at time-slot t, that is, Lij(t)=Sij(t)-(t/F)Rij(t). A positive Service Lag denotes the case where the received service is less than the requested service, that is, a cell arrives later than its ideal service time. A negative Service Lag is a Service Lead, where the received service exceeds the requested service, that is, a cell arrive sooner than its ideal service time. The normalized service lead/lag for a flow f equals the service lead/lag for flow f divided by the IIDT for flow f.Consider a discrete time queueing model, where time is normalized for all flows and is expressed in terms of the IIDT for each flow. The following notations presented in [11] are used. The cumulative arrival curve of a traffic flow f is said to conform to T(λ,β,δ), denoted, Af : T(λ,β,δ) if the average cell arrival rate is λ cells/sec, the burst arrival rate is ≤βλ cells/sec, and the maximum normalized service lead/lag is δ. A similar notation is used for cumulative departures and cumulative service. In any IP router, the cumulative departure curve for f is said to “track” the cumulative service curve for f when cell departures are constrained by the scheduled service opportunities. This situation occurs when flow f has queued cells at VOQ(j,k).The following four theorems were established in [11]. Assume each traffic flow is admitted to an IP/MPLS network subject to an Application-Specific Token-Bucket Traffic Shaper Queue (ASSQ), and has a maximum normalized service lead/lag of K cells. The traffic rate matrix for each router is updated by a resource reservation protocol such as RSVP, IntServ, or DiffServ. Each IP  router is scheduled using the proposed RFSMD algorithm with a maximum normalized service lead/lag of K cells. We assume fixed size cells, with any reasonable cell size, however similar bounds apply for the case of variable-sized IP packet.Theorem 1.
Given a flowf  traversing VOQ(j,k)  over an interval t∈[0,τ], with arrivals Af : T(ϕ(f),β,K), with service Sf : T(ϕ(f)β,K) and Q(0)≤O(K), then Q(t)≤O(K).Theorem 2.
When all queues in all intermediate nodes have reached steady state, the maximum end-to-end queueing delay of a GR flow traversingH routers is O(KH)·IIDT time slots.Theorem 3.
In the steady state, the departures of traffic flowf at any IQ router along an end-to-end path of H routers are constrained by the scheduling opportunities, and will exhibit a maximum normalized service lead/lag of K, that is, Sf : T(ϕ(f)β,K). The normalized service lead/lag of a flow is not cumulative when traversing multiple routers.Theorem 4.
A traffic flow which traverses H  IQ routers along an end-to-end path can be delivered to the end-user with zero network-introduced delay jitter, when a playback buffer of size 4 K  cells is employed, that is,Sf : T(ϕ(f)β,K).According to Theorem4, a bursty IPTV traffic flow which traverses H IQ routers along an end-to-end path can be delivered to the end-user with zero  network-introduced delay jitter, when an appropriately-sized Application-Specific Token-Bucket Traffic Shaper Queue and Application-Specific Playback Queue are used, as described in Section 3.Theorem1 states that the number of cells buffered for any flow in any router in any network is limited to a small number for all loads up to 100%. Theorem 2 states that all end-to-end traffic flows will never experience any congestion, excessive delay or throughput degradation. Every end-to-end flow experiences a small but effectively negligible queueing delay at each router compared to current router technologies. Theorem 3 states that the normalized service lead/lag is not cumulative when traversing multiple routers in any network. Theorem 4 states that every end-to-end traffic flow can be delivered at every destination router with essentially-perfect end-to-end Quality of Service. In particular, a bursty IPTV traffic flow transmitted through an IP network using the RFSMD scheduling algorithm can be perfectly regenerated at every destination route, with zero packet loss rate and zero delay jitter. These 4 theorems demonstrate that traffic flows can be scheduled to achieve essentially-perfect end-to-end QoS in any Internet topology for all loads up to 100%. The simulation results reported in Section 6 will demonstrate these 4 theorems.


## 5. Backbone Topologies

TheSurvivable Network Design Library (SNDlib) is a library of telecommunication network designs [12]. The library contains data for 22 IP backbone networks and several optimization problems for each network. The SNDlib provides a series of real IP network topologies appropriate for reproducible case studies. In this paper, simulation results for three of the SDNlib networks are presented. We have followed the node placement and link assignments described by SNDlib, although we have made our own assumptions about the IPTV broadcast tree construction, session demands, and link capacities.We selected the NOBEL-EU, GERMANY50, and the NORWAY network models from [12], as shown in Figure 6. The NOBEL-EU network covers Europe and has 28 nodes and 41 edges. It is a reference network originating from the European project NOBEL, where a detailed cost model was developed for various kinds of SDH and WDM equipment [12]. The GERMANY50 has 50 nodes and 88 edges provided by T-Systems International AG, and is an extension of the NOBEL-GERMANY network. The NORWAY network has 27 nodes and 51 edges and represents a backbone network from Norway.We developed several heavily loaded IPTVtraffic specifications for each network. In each traffic specification, one-third of the highest degree nodes are selected as roots of the IPTV multicast trees. For example, in the NOBEL-EU network with 28 nodes there are 9 multicast trees, each broadcasting 100 IPTV traffic streams. To generate each traffic specification, a 2-step process was used. In the first step, the IPTV multicast trees where routed into the network. N/3 nodes with the highest degrees were selected as roots for the N/3 trees. Each multicast tree was then routed to every other node in the network, using a shortest distance spanning tree computed using Dijkstra’s algorithm. Many links in the network, especially those in the center of the topology, carry traffic from each of the all N/3 multicast trees. In the second step, background traffic was added in an iterative manner between randomly selected pairs of nodes, to essentially saturate the network. In our traffic specifications, we achieve link loads of approx. 99%.  In each iteration, a random pair of nodes was selected, and a shortest delay path between the nodes was computed using an OSPF routing algorithm. A traffic rate was selected for the flow to nearly saturate the end-to-end path, and the flow would be confirmed. As the network load approaches 100%, it becomes increasingly difficult to route any additional flows, as all links approach saturation. Therefore, in the last iteration, multiple 1-hop traffic flows are added between neighboring nodes to effectively saturate the network, so that every link has a load of approximately 99%. Referring to Figure 4, the link loads used in our 3 network simulations are 99.2%, 99.2%, and 98.6%.Figure 4
Average link loads.Figure 5
Recursive problem P(M,F) of scheduling of matrix M into a scheduling frame with F time slots.Three network topologies, each showing three typical multicast trees.  Bold nodes are the roots of IPTV multicast trees.
(a)(b)(c)Each traffic specification represents an extremely heavy load, not likely to be encountered in practice. A resource reservation protocol such as RSVP, IntServ, or DiffServ was then used to reserve buffer space and bandwidth along each router and link in the network. These reservations result in the creation of an admissible traffic rate matrix for every router in the network. The traffic rate matrices for each router where then scheduled using the RFSMD algorithm. The network was then simulated, to gather statistics on the end-to-end QoS for every traffic flow, including IPTV multicast traffic and background traffic.Numerous traffic specifications were generated, routed and simulated for the three selected network topologies. Figure6 illustrates typical multicast trees in the 3 topologies examined in this paper, that is, the NOBEL-EU, NORWAY, and the GERMANY50 topologies. All of network simulations indicated essentially identical results, so we present the detailed simulations of one traffic specification over two networks, the NOBEL-EU and GERMANY50 networks. The NOBEL-EU network has 28 nodes, 41 links, and 9 IPTV multicast trees, each multicasting 100 IPTV channels to all other nodes. The selected traffic specification results in 321 traffic flows in the NOBEL-EU network, with an average distance of 5 hops and a maximum distance of 14 hops. The average link load is about 99%. The GERMANY50 network has 50 nodes, 88 links, and 16 IPTV multicast trees, each multicasting 100 IPTV channels to all other nodes. The selected traffic specification results in 693 traffic flows in the GERMANY50 topology, with an average distance of 5 hops and a maximum distance of 18 hops.The roots of the IPTV multicast trees are illustrated as a bold circle in Figure6. The IPTV multicast trees are routed according to Dijkstra’s shortest path algorithm. As a result, links near the center of the network will tend to carry more IPTV traffic than those near the edge. Each multicast tree for a given source node is not unique, since in many cases each tree has several equal length shortest paths from which to select an edge. In our traffic specifications, a typical link will devote between 4% and 7% of its allocated bandwidth of 40 Gbps to IPTV multicast data, with a maximum of 20%. The remaining bandwidth is used for background traffic between randomly selected pairs of nodes.


## 6. Results of IPTV Multicasting

Assume an IP/MPLS backbone network with 40 Gbps links, with a scheduling frame lengthF=1.024 (where 1 Gbps denotes 230 bps and 1 Mbps denotes 220 bps). The minimum quota of reservable bandwidth is one time-slot reservation per scheduling frame, or equivalently 4 Mbps. The provisioned GR rate of 440 Mbps per multicast tree established in Section 2 requires 11 time-slot reservations per scheduling frame. Each IP router in Figure 6 must reserve and schedule 11 cell transmissions per scheduling frame between the appropriate IO pairs, per IPTV multicast tree. In our traffic specifications, every incoming and outgoing link in each IP router is essentially saturated with additional background traffic. Given this worst-case load, the IP routers should find it challenging to schedule the traffic to meet QoS guarantees.The performance of the IP multicast trees in each IP backbone network was evaluated using a discrete-event simulator written in the C programming language, with over 20,000 lines of code. The simulator was written with the help of four graduate students, with funding provided by the Ontario Centers of Excellence. (Several independent simulators were actually written, to verify the experimental results.) The simulations were run on a large cluster-based supercomputing system in the Dept. of ECE at McMaster University, with 160 dual processing nodes running the LINUX operating system. Each dual-processor node has a clock rate of 1-2 GHz and between 1-2 GB of memory. A central dispatcher assigns tasks to processors to exploit parallelism.Figure7 illustrates the end-to-end delay (lifetime) PDF for (a) background traffic and (b) for multicast traffic in the GERMANY50 topology. Recall that there are 693 end-to-end paths and 16 IPTV multicast trees in this traffic specification. The multicast trees were routed first in the network using Dijkstra’s shortest path algorithm, and therefore they have relatively low path lengths. The end-to-end delay for multicast traffic shown in Figure 7(b) varies from 1 IIDT up to about 9 IIDT. The background traffic is point-to-point, and was routed along shortest-delay paths using the OSPF routing algorithm. The shortest-delay paths generally do not equal the shortest-hop paths, and as a result the background traffic tends to be routed along longer paths. The end-to-end delays for background traffic shown in Figure 7(a) varies from about 1 IIDT up to 40 IIDT, indicating that some paths are very long.PDF of End-to-End Delay for Germany50 topology.
(a)(b)Figure8 illustrates the jitter of the traffic along each end-to-end path, for both background traffic and multicast traffic. The jitter along one path is defined as the deviation of each cell’s delay along that path, relative to the mean value of the delay along a path. Figures 8(a) and 8(b) apply to the NOBEL-EU topology with 321 end-to-end paths. Figures 8(c) and 8(d) apply to the GERMANY50 topology with 693 end-to-end paths. Observe that 99% of all traffic flows arrive with less than 3 IIDTs of jitter, and 100% of all traffic flows arrive with less than 4 IIDTs of jitter. Observe from Figure 8 that the jitter for all point-to-point traffic and all multicast traffic is small and bounded by 4 IIDT, and the bound is network independent. These experimental results are consistent with the 4 theorems summarized in this paper. In [10], Theorems 5 and 8 establish that all jitter is bounded by 4 IIDT. Therefore, the experimental results in Figure 8 are perfectly consistent with the theorems in [10, 11].PDF of Delay Jitter. (a) and (b): Nobel-EU  topology. (c) and (d): Germany50 topology.
(a)(b)(c)(d)Figure9 illustrates the PDF for the distribution of the number of cells queued in each IP router in the GERMANY50 topology, for background traffic and multicast traffic. There are 3,465 individual plots in Figure 9, equal to 693 end-to-end paths passing through 5 routers on average. The number of cells queued per traffic flow in each router is small, less than 2 cells on average per multicast output port. No router buffers more than 7 cells per flow per unicast output, as shown in Figure 9(a). No router buffers more than 3 cells per aggregated flow per multicast output port, as shown in Figure 9(b). The multicast cells are stored in a multicast queue, which is separate from the VOQs in each router. Figure 9 indicates that the cells move at a relatively consistent rate through the IP network. These experimental results are consistent with the 4 theorems summarized in this paper. In particular, Theorem  1 in [11] establishes that all queue sizes are bounded by a small number of cells (16 cells for these networks). Therefore, the experimental results in Figure 9 are perfectly consistent with the theorems in [10, 11]. The amount of memory required for buffering is several orders of magnitude lower when compared to traditional IP routers, as the next section will demonstrate.PDF for number of queued cells per traffic flow per router for Germany50 topology. (a) for background traffic. (b) for multicast traffic.
(a)(b)Figure10 illustrates the end-to-end delay for the IPTV multicast traffic, as a function of the excess bandwidth selected for each multicast tree. Recall that in our traffic specifications, an excess bandwidth of 10% was provisioned for every IPTV multicast tree. The excess bandwidth determines the end-to-end delay. According to Figure 10, an excess bandwidth of 10% yields an end-to-end queueing delay of about 3 seconds on each IPTV multicast tree. The Application Specific Playback Queue at each destination node has reconstructed the original bursty IPTV video frames, filtered out the residual network jitter and made all 100 video streams available at each destination IP router in the multicast tree with essentially zero delay jitter and essentially-perfect end-to-end QoS.Figure 10
Plot of end-to-end delay versus excess bandwidth for multicast traffic.


### 6.1. Buffer Sizing in IP Routers

In this section, we explore the issue of memory requirements in Internet routers. One well-established design rule for buffer sizing in IP networks using TCP flow-control is called the “classical buffer rule”, also called the “bandwidth-delay-product” buffer rule [31]. This design rule states that each link in each IP router requires a buffer of B=O(C·T) bits, where C is the link capacity and T is the round-trip time of the flows traversing the link [31]. According to data in [31], a 40 Gbps link handling TCP flows with a round-trip time of 250 millisec requires a buffer size B about five million IP packets per link. Each IP packet may contain up to 1500 bytes (or equivalently 24 fixed-sized cells). Therefore, each link buffer may require up to 7.5 Gigabytes of memory per link. A 16×16 router may require about 120 Gigabytes of high-speed memory. This large buffer size is partially due to the use of the traditional TCP flow-control protocol, which introduces a large jitter into the traffic flows, which in turn necessitates the use of large buffers. The large buffer size is also partially due to the use of sub optimal heuristic schedulers, which introduce a large and potentially unbounded jitter at every router, which in turn necessitates the use of large buffers.A “small buffer rule” was proposed in [32], where B=O(C·T/N), and where N is the number of long-lived TCP flows traversing the router. With the same parameters reported above, the buffer size B can be reduced to about fifty thousand IP packets [32]. Therefore, each link buffer may require up to 75 Megabytes of memory per link. A 16×16 router may require about 1.2 Gigabytes of high-speed memory.More recently, [33] proposed a  “tiny buffer rule” where B=O(logW), where W is the maximum TCP congestion window size. With the same parameters, [33] suggests that average buffer sizes of between 20–50 IP packets or equivalently about 30,000–75,000 bytes of memory may suffice if 3 important conditions can be met; (a) the jitter of incoming traffic at the source node is sufficiently small, (b) the IP routers introduce a sufficiently small jitter, and (c) 10–15% of the throughput is sacrificed. The paper in [33] however did not propose a low-jitter scheduling algorithm, which is in itself a major theoretical unsolved problem as Section 3 illustrates. Furthermore, [32, 34] have argued that small buffers may cause significant losses, instability or performance degradation at the application layer.Our theorems in [10, 11] and our exhaustive simulations indicate that network memory requirements can be several orders of magnitude smaller than those in current IP routers, when a low-jitter scheduling algorithm with a bounded normalized service lead/lag is used, as established in Theorems 1–4. In our IP multicast system, each IP router needs to buffer on average about 2 cells (128 bytes) per flow per router to guarantee 100% throughput and essentially-perfect end-to-end QoS for all provisioned traffic flows, even at 100% network loads. In comparison, existing IP routers using the combination of heuristic schedulers, TCP flow control, and the classic bandwidth-delay-product buffer-sizing rule require buffers of about 5 million IP packets per link at 40 Gbps to achieve high throughput, without providing any rigorous QoS guarantees. The RFSMD algorithm and Theorems 1–4 allow for reductions in buffer sizes by several orders of magnitude compared to the existing IP multicast technology, while simultaneously meeting rigorous QoS constraints.


## 6.1. Buffer Sizing in IP Routers

In this section, we explore the issue of memory requirements in Internet routers. One well-established design rule for buffer sizing in IP networks using TCP flow-control is called the “classical buffer rule”, also called the “bandwidth-delay-product” buffer rule [31]. This design rule states that each link in each IP router requires a buffer of B=O(C·T) bits, where C is the link capacity and T is the round-trip time of the flows traversing the link [31]. According to data in [31], a 40 Gbps link handling TCP flows with a round-trip time of 250 millisec requires a buffer size B about five million IP packets per link. Each IP packet may contain up to 1500 bytes (or equivalently 24 fixed-sized cells). Therefore, each link buffer may require up to 7.5 Gigabytes of memory per link. A 16×16 router may require about 120 Gigabytes of high-speed memory. This large buffer size is partially due to the use of the traditional TCP flow-control protocol, which introduces a large jitter into the traffic flows, which in turn necessitates the use of large buffers. The large buffer size is also partially due to the use of sub optimal heuristic schedulers, which introduce a large and potentially unbounded jitter at every router, which in turn necessitates the use of large buffers.A “small buffer rule” was proposed in [32], where B=O(C·T/N), and where N is the number of long-lived TCP flows traversing the router. With the same parameters reported above, the buffer size B can be reduced to about fifty thousand IP packets [32]. Therefore, each link buffer may require up to 75 Megabytes of memory per link. A 16×16 router may require about 1.2 Gigabytes of high-speed memory.More recently, [33] proposed a  “tiny buffer rule” where B=O(logW), where W is the maximum TCP congestion window size. With the same parameters, [33] suggests that average buffer sizes of between 20–50 IP packets or equivalently about 30,000–75,000 bytes of memory may suffice if 3 important conditions can be met; (a) the jitter of incoming traffic at the source node is sufficiently small, (b) the IP routers introduce a sufficiently small jitter, and (c) 10–15% of the throughput is sacrificed. The paper in [33] however did not propose a low-jitter scheduling algorithm, which is in itself a major theoretical unsolved problem as Section 3 illustrates. Furthermore, [32, 34] have argued that small buffers may cause significant losses, instability or performance degradation at the application layer.Our theorems in [10, 11] and our exhaustive simulations indicate that network memory requirements can be several orders of magnitude smaller than those in current IP routers, when a low-jitter scheduling algorithm with a bounded normalized service lead/lag is used, as established in Theorems 1–4. In our IP multicast system, each IP router needs to buffer on average about 2 cells (128 bytes) per flow per router to guarantee 100% throughput and essentially-perfect end-to-end QoS for all provisioned traffic flows, even at 100% network loads. In comparison, existing IP routers using the combination of heuristic schedulers, TCP flow control, and the classic bandwidth-delay-product buffer-sizing rule require buffers of about 5 million IP packets per link at 40 Gbps to achieve high throughput, without providing any rigorous QoS guarantees. The RFSMD algorithm and Theorems 1–4 allow for reductions in buffer sizes by several orders of magnitude compared to the existing IP multicast technology, while simultaneously meeting rigorous QoS constraints.


## 7. Conclusions

The design of an IPTV multicast system for packet-switched Internet backbone networks has been presented.   Three real IP backbone network topologies, the NOBEL-EU European topology, and the GERMANY50 and the NORWAY topologies, were used to illustrate the design. Multiple IPTV multicast tees were provisioned into each network, each carrying 100 IPTV channels. Additional background traffic was added between nodes to essentially fully saturate each network. Every link operates at loads of approximately 99%. A resource reservation algorithm was used to reserve resources for each ITPV multicast tree in the network. A recently proposedRecursive Fair Stochastic Matrix Decomposition algorithm was used to compute near-perfect low-jitter transmission schedules for each packet-switched IP router in each multicast tree. The low-jitter schedules remove most of the cell delay jitter associated with the sub optimal dynamic scheduling algorithms used in existing IP routers and minimize the amount of buffering required in the IP routers. Extensive simulations indicate that large-scale IPTV multicasting can be supported. The IPTV traffic is delivered to every destination node with near-minimal delays, near-minimal jitter, zero packet loss rates, and essentially-perfect end-to-end QoS, as confirmed by theory. Our extensive simulations indicate that each IP router typically buffers less than 2 cells (about 128 bytes) of video data per traffic flow per router, several orders of magnitude less buffering than current IP routers require. The multicast technology is also applicable to other multimedia streams over the Internet, including VOIP, Video-on-Demand, Telemedicine, and Telerobotic control over IP. The application of the technology to deliver telerobotic control systems over saturated Internet backbone networks is described in [35].



---

*Source: 169140-2010-06-13.xml*