<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The Evaluation of Performance in Flow Label and Non Flow Label Approach Based on IPv6 Technology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ariana Bejleri</string-name>
          <email>arianabejleri@yahoo.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Igli Tafaj</string-name>
          <email>itafaj@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ermal Beqiri</string-name>
          <email>ermalfr@yahoo.fr</email>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Julian Fejzaj</string-name>
          <email>Julian.fejzaj@fshn.edu.al</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>BCI'12, September 16-20, 2012, Novi Sad, Serbia.</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aleksander Biberaj</string-name>
          <email>a.biberaj@yahoo.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Copyright © 2012 by the paper's authors. Copying permitted only for private and</institution>
          ,
          <addr-line>academic purposes. This volume is published and copyrighted by its editors., Local Proceedings also appeared in ISBN 978-86-7031-200-5</addr-line>
          ,
          <institution>Faculty of Sciences, University of Novi Sad.</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Polytechnic University of Tirana, Faculty of Information Technology, Computer Engineering Department</institution>
          ,
          <addr-line>Tirana</addr-line>
          ,
          <country country="AL">Albania</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Polytechnic University of Tirana, Faculty of Information Technology, Electronic and Telecommunication Engineering, Department</institution>
          ,
          <addr-line>Tirana</addr-line>
          ,
          <country country="AL">Albania</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Tirana University, Faculty of Natural Sciences, Department of Computer Science</institution>
          ,
          <addr-line>Tirana</addr-line>
          ,
          <country country="AL">Albania</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Tirana University, Mathematics &amp; Statistics &amp; Applied, Informatics Department</institution>
          ,
          <addr-line>Tirana</addr-line>
          ,
          <country country="AL">Albania</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper, we want to evaluate the performance of two broadcasters with Flow label and Non flow label approach. Experimentally we have presented that the throughput utilization for each broadcaster with Flow Label approach which is implemented in MPLS Routing Technology is 89,95%. This result is better than Non Flow Label approach which is evaluated at 92,77%. The aim of this paper is to present that MPLS Routers performance is better than IP routers especially in Throughput Utilization, Low Level of Drop Packet Rate and time delay. The second technology is implemented in IP routing. Experimentally we have generated some video stream packets between 2 broadcasters with an arrange of router nodes. Experiments are performed by using ns-2 simulator.</p>
      </abstract>
      <kwd-group>
        <kwd>MPLS technology</kwd>
        <kwd>IP routing technology</kwd>
        <kwd>throughput</kwd>
        <kwd>flow-label approach</kwd>
        <kwd>ns-2 simulator</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        As we know IPv6 is a recent technology of communication and it
gives a lot of improvements compared to IPv4 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. These
improvements based on features upgraded by the Internet
Engineering Task Force (IETF), for example, the increase of the
address space from 32 bits to 128 bits or the increase of some
significant QoS conditions. By using the recent multimedia
applications technologies [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], internet providers, companies,
subscribers and the researchers will take some benefits. The
Internet Protocol (IP) is considered to be a best effort service, so
in the future, the TV broadcasters will use the IP address for
communication. In other words, there will be a convergence of the
broadcast network with the IP to form the Internet Protocol
Television (multimedia with IP) under the recent development.
There are built some policies based on flow-labels to manage the
routing of the packets (channels) to the nodes (subscribers)during
the transmission with IP-multimedia approach.
For example, a broadcaster can tend to utilize the full bandwidth
from the network manager, but meanwhile the network manager
asks fairness in distributing packets to the remaining broadcasters
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. As it know throughput is one of the important feature of
QoS Routing, because the management of throughput offers a
better QoS performance. It is interesting to mention that IPv6 not
only overcomes the shortcoming problems in the IPv4, but also it
takes the benefits in Quality of service (QoS). QoS in IPv6 plays
an important role in the Stream Model Approach between
broadcasters [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] the packet’s traffic on channel is
organized without flow label technology. Flow label technology
means that instead of router nodes (fig 1) based on IP routing we
can use MPLS routers. MPLS technology has some advantages,
but the most one is speed routing. Based on some executed tests
we can present that bandwidth utilization is another good feature
compared with IP routers technology.
      </p>
      <p>The objective of this paper is to highlight our simulation results
in terms of two attributes which are the Throughput and Time
Computation Performance based on IPv6 technology with flow
label packets technology in Multi-channel Stream Approach.
Than we want to compare the results of our simulation with
nonflow label packets technology in Multi-channel Stream Approach.
The rest of the paper is organized as follows: section 2 briefly
discusses the comparison between MPLS and IP routing section 3
presents the experimental analysis and results, in section 4 are
given some conclusions and future works and finally are
presented the references.</p>
    </sec>
    <sec id="sec-2">
      <title>2. COMPARISON BETWEEN MPLS</title>
    </sec>
    <sec id="sec-3">
      <title>ROUTING AND IP ROUTING</title>
      <p>1. IP routing uses hop-by-hop destination-only forwarding
paradigm. When forwarding IP packets, each router in the
path has to look up the packet's destination IP address in the
IP routing table and forward the packet to the next-hop
router [8].
2. MPLS uses a variety of protocols to establish Label Switched
Paths (LSP) across the network. LSPs are almost like Frame
Relay or Asynchronous Transfer Mode (ATM) permanent
virtual circuit (PVC), with two major differences: they are
unidirectional and they can merge (all LSPs toward the same
egress router could merge somewhere in the network).
3. MPLS is faster than IP routing because it is based on label.
4. MPLS is in 2,5 OSI Layer and IP is in 2 OSI Layer.</p>
    </sec>
    <sec id="sec-4">
      <title>3. EXPERIMENTAL ANALYSIS DESIGN</title>
    </sec>
    <sec id="sec-5">
      <title>AND RESULTS</title>
      <p>In this section, we want to test the Throughput and Time Delay
based on IPv6 technology with non flow label packets technology
and flow label packets technology in Multi-channel Stream
Approach. As we presented above we have used IPv6 technology
because it offers more flexibility and QoS features than IPv4</p>
    </sec>
    <sec id="sec-6">
      <title>3.1 Experimental Analysis</title>
      <p>
        In the Multi - Stream Approach we have tested up to 10 nodes for
2 broadcasters as end-users. We have used ns2 simulator since it
is considered to be powerful, efficient and flexible for simulation.
The 10 nodes were tested sequentially starting from 1 node, 2
nodes, 3 nodes, … , 10 nodes, respectively. We have simulated for
both broadcasters Video Stream Packets with 1.4 KB packet
length, Rate Video Stream is 1.5 MB/sec and Bandwidth is 5 MB.
Network topology is BUS. In NS2 simulator we configure RIP
version 2 Routing Policy. We have choosen approximately
characteristics with real environment [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>The maximum Video Packet supported by Maximum
Transmission Units (MTUs), which include the Maximum
Segment Size (MSS) plus the 40-byte header, within TCP/IP
traffic. We'd like video packets (which include a smaller header,
apparently) to be around 1400 bytes to fit within acceptable limits
and eliminate the possibility of broken packets.</p>
      <p>Initially, the first broadcaster generate video stream packets to
second one by httperf tool. In the first broadcaster we have
installed client machine and in the second one we have installed
server machine. In server machine we have built Apache Web
Server. So the client is sending video packet request by using http
protocol to the server machine. On the other hand second
broadcaster can generate http video request to the first one. At this
moment client machine is transform in server machine and vice
versa. Thus at the same time one machine will utilized as client
and server by installed Apache Web Server (Apache2 on
CENTOS 5.5 OS)
For every experimental phase (by 2, 3 ,4 …10 nodes), we have
calculated the throughput , then we have compared the throughput
of the nodes into both broadcasters. Previously we have
performed experiments with router nodes which are based on IP
technology (non flow label technique). We have repeated this
experiment with MPLS routers (flow label technique).</p>
      <p>Node 1</p>
      <p>Node 4
Node 2</p>
      <p>Node 3</p>
      <p>As it look from figure 1 two broadcaster generate video-stream
packets at the same time. All these packets are routing on these
nodes based on RIP v2 policy.</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] the throughput for a determined broadcaster and the number
of nodes is calculated as in the following equation:
      </p>
      <p>Throughput =</p>
      <p>Num(SBW ) − Num(RBW )</p>
      <p>Num(SBW )
×100%
(1)
Throughput: The amount of the non-lost received bandwidth.
Num. (SBW): The amount of the bandwidth provided by the
network manager. Packets should be sent to all nodes of the
determined broadcaster.</p>
      <p>Num. (RBW): The amount of the bandwidth that is received from
the determined broadcaster. This amount should get different
value than SBW, because some packets have to lost during
routing.</p>
    </sec>
    <sec id="sec-7">
      <title>3.2 Simulation Results</title>
      <p>In order to evaluate our method, the main attribute is the
Throughput between the nodes and their broadcasters. We did
compare the throughput behavior of each broadcaster with their
nodes starting from 1 node and increasing the size to 10 nodes,
based on IP routing protocol. The experiment presents that the
total throughput for the 2 broadcasters with 10 nodes with IP
routing technology is 92.77% . If we use the Non-Flow Label
Technique which means that we can replace the IP routers with
MPLS routers, with the same policy routing (RIP) with 2
broadcasters which generate the same packet traffic, the total
throughput utilization for each broadcaster is decrease to 89,95%.
This means that one broadcaster can use the same number of
video stream packet generated with smaller utilization bandwidth.
All router nodes in figure 1 are configured with IPv6 address. The
total number of packets generated from each broadcaster is 1000.
As it looks from table 1 and table 2, if the number of nodes is
increased the total throughput utilization for each broadcaster is
decreased linearly. The number of dropped packets increased
linearly if the number of nodes increased too (table 3,4). Each
node can introduce drop packets (the reason are buffer,
architecture of routers etc). In this paper we compared the
percentage of dropped packets and time delay between 2
technologies, non-flow labels packet and flow labels packet as it
shows in table 3-6.
We have presented graphically, throughput utilization and time
delay (figure 2 and figure 3) based on the flow-label technology.
In figure 3 time delay increases linearly when the number of
nodes increased too, because each router nodes introduce a slight
delay. In figure 2 throughput utilization is decreased when the
numbers of nodes is increased. As we mentioned above the reason
is increasing of data rate lost for each node. We have a sensitive
reduction of throughput utilization, between node 4 and node 6.
This was happen because in those nodes the ratio of drop packets
is bigger than 3 nodes. After 6 nodes the drops of packet are
stabilized.</p>
    </sec>
    <sec id="sec-8">
      <title>4. CONCLUSIONS AND DISCUSSIONS</title>
      <p>1. As it look from table 3 and table 4 the drop packets rate are
similarity for both methods (flow label and non-flow label).
This is because both routers have the same buffers, so it
doesn’t affect the performance of drop packets routing.
2. If we compare table 5 and table 6 the difference of time is
visible. This is because MPLS routers characterized from a
fast routing technology. The reason is routing packet which
are based on labels, not in IP. This is an important feature of
the best throughput utilization in flow label technology,
descripted in table 2 compared with non-flow label
technology in table 1.</p>
      <p>In the future we will increase the number of broadcasters and
routers. Also we will generate the dynamic length of video
stream packets in order to evaluate the throughput utilization
performance and time delay in WAN.</p>
    </sec>
    <sec id="sec-9">
      <title>5. REFERENCES</title>
      <p>[8]
http://searchtelecom.techtarget.com/answer/What-is-thedifference-between-MPLS-and-normal-IP</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Almadi</surname>
            <given-names>M.A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Idrus</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ramadass</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Budiarto</surname>
            <given-names>R</given-names>
          </string-name>
          , “
          <article-title>A Proposed Model for Policy-Based Routing Rules in the IPv6 Offering QoS for IPTV Broadcasting</article-title>
          ,”
          <source>International Journal of Computer Science and Network Security</source>
          ,
          <string-name>
            <surname>IJCSNS</surname>
          </string-name>
          , VOL.
          <volume>8</volume>
          No.
          <issue>3</issue>
          ,
          <year>March 2004</year>
          , pp.
          <fpage>163</fpage>
          -
          <lpage>173</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Cho</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luckie</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huffaker</surname>
            <given-names>B</given-names>
          </string-name>
          , “
          <article-title>Identifying IPv6 Network Problems in the Dual-Stack World”</article-title>
          <source>In Proceedings of the Annual Conference of the Special Interest Group on Data Communication, SIGCOMM'04</source>
          ,
          <string-name>
            <surname>Portland</surname>
          </string-name>
          , Oregon, USA,
          <volume>30</volume>
          <fpage>August</fpage>
          - 3
          <source>September</source>
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Liang</surname>
            ,
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            <given-names>Z</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nahrstedt</surname>
            <given-names>K.. “</given-names>
          </string-name>
          <article-title>A Framework for Future Internet-Based TV Broadcasting,”</article-title>
          <source>In Proceedings of the International World Wide Web Conference, multimedia with IP Workshop</source>
          , Edinburgh, Scotland, United Kingdom,
          <year>2006</year>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Pezaros</surname>
            <given-names>DP</given-names>
          </string-name>
          and. Hutchison D. “
          <article-title>Quality of Service Assurance for the next Generation Internet,”</article-title>
          <source>In Proceedings of the 2nd Postgraduate Symposium in Networking, Telecommunications and Broadcasting (PGNet'01)</source>
          , Liverpool,
          <string-name>
            <surname>UK</surname>
          </string-name>
          , June 18-19,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Pezaros</surname>
            <given-names>D.P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hutchison</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gardner R.D</surname>
          </string-name>
          ,
          <string-name>
            <surname>Garcia F.J and Sventek</surname>
            <given-names>J.S</given-names>
          </string-name>
          , “
          <article-title>Inline Measurements: A Native Measurement Technique for IPv6 Networks,”</article-title>
          <source>In Proceedings of the International Conference of the IEEE for Networking and Communication</source>
          , pp.
          <fpage>105</fpage>
          -
          <lpage>110</lpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Silva</surname>
            <given-names>J. S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Duarte</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Veiga</surname>
            <given-names>N</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Boavida</surname>
            <given-names>F</given-names>
          </string-name>
          ,”
          <article-title>MEDIA - An approach to an efficient integration of IPv6 and ATM multicast environments</article-title>
          ,” [Online]. Available: http://cisuc.dei.uc.pt/dlfile.php?fn=171_pub_SaSilva.pdf&amp;ge
          <source>t=1&amp;idp=171&amp;ext= April</source>
          <volume>12</volume>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Zhiwei</surname>
            <given-names>Y</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guizhong</surname>
            <given-names>L</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rui</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qing</surname>
            <given-names>Zh</given-names>
          </string-name>
          , Xiaoming Ch, Lishui Ch. ”School of Electronics and Information Engineering Xi'an Jiaotong University,
          <source>Xi'an, China</source>
          <volume>710049</volume>
          ,
          <string-name>
            <surname>“</surname>
            <given-names>A Simulation</given-names>
          </string-name>
          <string-name>
            <surname>Mechanism for Video Delivery Researches</surname>
          </string-name>
          ,
          <year>2009</year>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>