FYP Thesis

University of Engineering & Technology Peshawar (Mardan Campus)
B.Sc Final Year Project REPORT

Project Title
Performance Analysis of MPLS in UMTS
Group Members
Naeem Ullah Syed Imran Muhammad Tayyab 07MDTLC0287 07MDTLC0277 07MDTLC0270
Project Advisor
Dr. Akhtar Hussain Khalil
Department of Telecommunication Engineering Session 2007 - 2011
Page 1
IN THE NAME OF ALLAH, THE MOST BENEFICIENT, THE MOST MERCIFUL
Page 2
Project Supervisor
Name: Dr. Akhtar H. Khalil Signature:
Final Year Project Coordinator

Name: Engr; Imad Ali Signature:
Head of Department
Name: Dr. Shahbaz Khan Signature:
Page 3
Certificate of Originality
This is to certify that we are responsible for the work submitted in this project report, that the work is our own except as specified in acknowledgments, references or in footnotes, and that neither the thesis nor the original work contained therein has been submitted to this or any other institution for a final year project evaluation. Project members names and signatures
Naeem Ullah Muhammad Tayyab Syed Imran Hussain Shah
Signature: .. Signature: .. Signature: ..
Date: ..........................
Page 4
ACKNOWLEDGMENT
We would like to thank Allah for making our effort into a reality. Then we would like to thank our parents for their support and prayers. We owe special thanks to our supervisor Dr. Akhtar Hussain Khalil for his guidance and support throughout the project. We would also like to thank to Dr. Shahbaz Khan for his guidance.
Page 5
Dedicated to Our parents and our family
Page 6
ABSTRACT
Multiprotocol Label Switching (MPLS) is an emerging technology which ensures the reliable delivery of the Internet services with high transmission speed and lower delays. The key feature of MPLS is its Traffic Engineering (TE) which is used for effectively managing the networks for efficient utilization of network resources. Due to lower network delay, efficient forwarding mechanism, scalability and predictable performance of the services provided by MPLS technology makes it more suitable for implementing real-time applications such as Voice and video.
In this work we have used the above approach is used for achieving the above performance in UMTS to reduce the jitter, voice packet delay variation and voice packet end to end delay. In this thesis the simulation is done in OPNET simulator 14.0, first comparing the simple scenario of conventional IP network and other MPLS scenario in conventional networking. We have also compared simple UMTS scenario and MPLS scenario in UMTS.
Keywords: MPLS (Multi Protocol Label Switching), TE (Traffic Engineering), UMTS (Universal Mobile Telecommunication System) and OPNET (Optimized Network Engineering Tool).
Page 7
ACRONYMS MPLS TE TCP/IP IPv4 LER LSR LSP LDP FEC VoIP QoS IETF RTP RTTP CR-LDP CR-LSP RSVP OSPF LIB VPN IS-IS BGP 2.5G 3G AAL2 AAL5 ATM AUC CN CDMA CS PS DES EDGE EIR Multiprotocol Label Switching Traffic Engineering Transmission Control Protocol/ Internet Protocol Internet Protocol version 4 Label Edge Router Label Switching Router Label Switch Path Label Distribution Protocol Forward Equivalence Class Voice over Internet Protocol Quality of Service Internet Engineering Task Force Real Time Protocol Real Time Transport Protocol Constraint Based Label Distribution Protocol Constraint Based Label Switch Path Resource Reservation Protocol Open Shortest Path First Label Information Base Virtual Private Network Intermediate system to intermediate system Border Gateway Protocol 2.5 Generation 3rd Generation ATM Adaption Layer 2 ATM Adaption Layer 5 Asynchronous Transfer Mode Authentication Center Core Network Code Division Multiple Access Circuit Switch Packet Switch Discrete Event Simulation Enhanced Data Rate for GPRS Evolution Equipment Information Register
Page 8
Email FACH FDD FSM FTP GERAN GGSN GLR GMM GPRS GSM VLSI GTP HLR HTTP ID ISDN IMSI IMEI IMT 2000 IP IPV4 IPV6 ITU Kbps LTE MSC MSISDN N/A OSI OPNET PDP PLMN TMSI PPP QoS RAM
Electronic Mail Fast Associated Control Channel Frequency Division Duplex Finite State Machine File Transfer Protocol GSM/EDGE Radio Access Network Gateway GPRS Support Node Gateway Location Register Global Multimedia Mobility General Packet Radio Service Global System for Mobile Communication Very Large Scale Integration GPRS Tunneling Protocol Home Location Register Hyper Text Transfer Protocol Identity Integrated Service Digital Networks International Mobile Subscriber Identity International Mobile Station Equipment Identity International Mobile Telecommunication 2000 Internet Protocol Internet Protocol Version 4 Internet Protocol version 6 International Telecommunication Union Kilo Bits Per Second Long Term Evolution Main Switching Center Mobile Station Integrated Service Digital Network Not Applicable Open System Interaction Optimized Network Evaluation Tool Packet Data Protocol Public Line Mobile Network Temporary Mobile Subscriber Identity Point to Point Protocol Quality of Service Radio Access Mode
Page 9
RAN RT SGSN TDD TE UE UMTS USIM VOIP WCDMA WLAN WWW
Radio Network Controller Real Time Serving GPRS Support Node Time Division Duplex Terminal Equipment User Equipment Universal Mobile Telecommunication System User Subscriber Identity Module Voice Over Internet Protocol Wide Code Multiple Access Wireless Local Area Network World Wide Web
Page 10
Table of Contents
ACKNOWLEDGMENT.................................................................................................................... 5 ABSTRACT ....................................................................................................................................... 7 Chapter # 1 ....................................................................................................................................... 16 Introduction ...................................................................................................................................... 16 1.1 Background ............................................................................................................................... 16 1.1.1 Software used: .................................................................................................................... 16 1.2 Motivation ................................................................................................................................. 17 1.3 MPLS ........................................................................................................................................ 17 1.4 3G (third generation of mobile telephony) .............................................................................. 18 1.5 Information about upcoming chapters ...................................................................................... 18 Chapter # 2 ....................................................................................................................................... 20 Multi Protocol Label Switching ....................................................................................................... 20 2 .1 Introduction to MPLS .............................................................................................................. 20 Figure 2.1 Layer Formats of MPLS ................................................................................................. 21 2.2 History...................................................................................................................................... 21 2.3 HOW MPLS Work? .................................................................................................................. 22 Figure 2.2 MPLS header .................................................................................................................. 22 Figure 2.4 MPLS table ..................................................................................................................... 23 2.4 HOW MPLS Paths are established? ........................................................................................ 25 Figure 2.5 MPLS LSP ...................................................................................................................... 25 2.5 Comparison of MPLS and IP .................................................................................................... 25 2.6 Signaling protocol of MPLS .................................................................................................... 26 2.7 MPLS fast rerouting ................................................................................................................. 28 2.8 MPLS versus Frame Relay Performance................................................................................. 29 2.9 MPLS versus ATM performance ............................................................................................. 29 2.10 MPLS Application ................................................................................................................... 30 Chapter # 3 ....................................................................................................................................... 32 OPNET Modeler 14.0 .................................................................................................................... 32 3.1 Network Simulator Selection .................................................................................................... 32 3.2 Why OPNET? ........................................................................................................................... 32 3.3 What is OPNET?....................................................................................................................... 33 Figure 3.6 OPNET ........................................................................................................................... 34 3.3.1 OPNET Modeler ............................................................................................................... 34 Performance Analysis of MPLS in UMTS Page 11
Figure 3.7 MODELS ........................................................................................................................ 35 Figure 3.8 Editor .............................................................................................................................. 36 3.3.1.1 The Network Layer ................................................................................................... 36 3.3.1.2 The Node Layer ......................................................................................................... 37 Figure 3.10 Node Layer ................................................................................................................... 37 3.3.1.3 3.4 The Process Layer ................................................................................................... 37 Figure 3.11 Process Layer................................................................................................................ 38 Main features ....................................................................................................................... 38 3.4.1 Project Editor .................................................................................................................... 39 Figure 3.12 project Editor ................................................................................................................ 40 3.4.2 The Node Editor ............................................................................................................... 40 3.4.3 3.4.4 3.4.5 The process Model Editor ............................................................................................... 41 The Link Model Editor ................................................................................................... 41 The Path Editor ............................................................................................................... 42 Figure 3.14 Process Model Editor ................................................................................................... 41 Figure 3.15 link Model Editor ......................................................................................................... 41 Figure 3.16 Path Editor .................................................................................................................... 42 3.4.6 The packet format Editor .................................................................................................... 42 3.4.7 The Probe Editor .............................................................................................................. 43 3.4.8 The simulation Sequence Editor ...................................................................................... 43 Figure 3.19 simulation sequence Editor........................................................................................... 44 3.4.9 The Analysis Tool ............................................................................................................... 44 Figure 3.20 Analysis Editor ............................................................................................................. 44 3.4.10 the project Editor Work Space ......................................................................................... 44 Figure 3.21 Project Editor Work space ............................................................................................ 45 3.4.11 The Menu Bar ................................................................................................................ 45 Figure 3.22 Menu bar ....................................................................................................................... 45 3.4.12 Buttons ........................................................................................................................... 45 Figure 3.23 Buttons .......................................................................................................................... 45 3.5 How to make a scenario in OPNET: ..................................................................................... 46 Chapter # 4 ....................................................................................................................................... 47 Performance Analysis of MPLS in conventional IP Network ......................................................... 47 4.1 Introduction .............................................................................................................................. 47 4.2 OPNET implementation.......................................................................................................... 47 Page 12
Figure 4.24 OPNET ......................................................................................................................... 48 Figure 4.25 New Project .................................................................................................................. 48 4.2.1 IP Architecture .................................................................................................................... 49 Figure 4.27 IP architecture ............................................................................................................... 49 4.2.2 MPLS architecture .............................................................................................................. 50 Figure 4.28 MPLS Architecture ....................................................................................................... 50 4.3 comparing Graphs and result ................................................................................................. 51 4.3.1 Voice application Table .................................................................................................... 51 Table 4.1 IP Global statistic ............................................................................................................ 52 Table 4.2 IP Node statistic .............................................................................................................. 52 Table 4.3 MPLS Global statistic ..................................................................................................... 52 4.3.1.2 Graphs ......................................................................................................................... 52 Graph 4.1 Voice jitter ...................................................................................................................... 53 Graph 4.3 Voice packet end to end delay ........................................................................................ 54 4.3.2.1 Table ............................................................................................................................ 54 Figure 4.29 FTP scenario ................................................................................................................. 54 Table 4.5 FTP Global statistic in MPLS .......................................................................................... 55 4.3.2.2 Graphs .......................................................................................................................... 55 Graph 4.5 FTP Traffic Received in bytes/second ........................................................................... 56 Graph 4.9 FTP Download Response ............................................................................................... 58 4.4 conclusions ................................................................................................................................ 58 Chapter # 5 ....................................................................................................................................... 59 Universal Mobile Telecommunication System ................................................................................ 59 5.1 Background ............................................................................................................................... 59 5.2 UMTS Architecture ............................................................................................................... 60 Figure 5.30 UMTS Architecture ...................................................................................................... 60 5.2.1 Core Network ........................................................................................................................ 61 5.2.2 UMTS Terrestrial Radio Access Network (UTRAN) ........................................................ 62 5.2.3 User Equipment (UE) ......................................................................................................... 63 5.3 Quality of Service (QoS) .......................................................................................................... 64 5.3.1 UMTS QoS Classes ......................................................................................................... 64 5.3.1.1 Conversational Class .................................................................................................... 65 5.3.1.2 Streaming class: ........................................................................................................... 66 5.3.1.3 Interactive class ............................................................................................................ 66 Performance Analysis of MPLS in UMTS Page 13
5.3.1.4 Background Class ....................................................................................................... 67 Table 5.6 QoS classes table ............................................................................................................. 68 Chapter # 6 ....................................................................................................................................... 69 Performance Analysis of MPLS in 3G Network ............................................................................. 69 6.1 OPNET implementation............................................................................................................. 69 Figure 6.32 UMTS Scenario ............................................................................................................ 70 6.2 Comparing Graphs and result .................................................................................................. 71 6.2.1 VOICE APPLICATION ..................................................................................................... 71 6.2.1.1 Table ........................................................................................................................... 71 Table 6.7 Global Statistic of IP in UMTS........................................................................................ 71 Table 6.8 Node Statistic of IP in UMTS .......................................................................................... 71 Table 6.9 Global Statistic of MPLS in UMTS ................................................................................. 72 Table 6.10 Node Statistic of MPLS in UMTS ................................................................................. 72 6.2.1.2 Graphs ......................................................................................................................... 72 Graph 6.10 Voice Jitter in UMTS .................................................................................................... 73 Graph 6.11 Voice Packet Delay Variation in UMTS ..................................................................... 73 Graph 6.12 Packet End to End Delay in UMTS ............................................................................. 74 6.2.2 FTP application ............................................................................................................. 74 6.2.2.1 Table ............................................................................................................................ 74 Figure6.33 FTP scenario .................................................................................................................. 74 Table 6.11 IP FTP Global Statistic in UMTS .................................................................................. 75 Table 6.11 MPLS FTP Global Statistic in UMTS ........................................................................... 75 6.2.2.2 Graphs ......................................................................................................................... 75 Graph 6.12 FTP Download Response in UMTS ............................................................................. 76 Table 6.15 Traffic Received packets/second in UMTS ................................................................... 77 Table 6.17 Traffic Send packets/second in UMTS .......................................................................... 78 .3 conclusions ................................................................................................................................... 78 Chapter #7 ........................................................................................................................................ 79 Conclusion and Future Work ........................................................................................................... 79 7.1 Conclusion ................................................................................................................................. 79 7.2 Future work ................................................................................................................................ 79 7.2.1 Convergence in NGN .......................................................................................................... 79 Figure 7.34 NGN Architecture ........................................................................................................ 80 Figure 7.35 convergence of different world Network ..................................................................... 80 Performance Analysis of MPLS in UMTS Page 14
7.2.2 GMPLS (Generalized Multi Protocol Label Switching) .................................................... 81 Figure 7.37 Future GMPLS ............................................................................................................. 81 References: ....................................................................................................................................... 82
Page 15
Chapter # 1 Introduction
1.1 Background Nowadays communication and communication technology changing every day, the customers satisfaction decrease. But as the time pass; the customers became unhappy with the available services of network. The main point here comes up, to satisfy our customers and increase our network performance by taking the QoS (Quality of Service). That quality of service is provided that meet the customers satisfaction. MPLS (Multi protocol Label Switching) is a new switching technology work on a short fixed label of 20 bits. The total forwarding and routing is based on this label in the core of network. The main application of MPLS to IP network is to provide QoS for Real Time Communication such as voice over IP or video. The theme of our project is to provide QoS to clients. In QoS, the main factor is the delay. In order to reduce the delay factor in real time communication. We will design and implement the MPLS and IP scenario, first their performance is cheeked in simple conventional IP network.
Further above approach is applied to 3G (third Generation) or UMTS (Universal Mobile Telecommunication System)
1.1.1 Software used: One way to laboratory components into an introductory networking course is with simulations. Network simulation allows students to examine problems with much less work and of much larger scope than are possible with experiments on real hardware. An invaluable tool in this case is the OPNET simulator. OPNET is the software that offers Performance Analysis of MPLS in UMTS Page 16
tools for modeling, design, simulation and analysis etc. OPNET can simulate a wide variety of different networks which are linked to each other. This is the most effective solution for students to demonstrate the behavior of different networks and protocols. [1] The OPNETs discrete event engine for network simulations is the fastest and most scalable commercially available solution.
1.2 Motivation Our main motivation to our project arises from last summer, when we take course of networking e.g. CCNA. From there our interest towards networking sites is developed and we decide to take FYP in IP site. Then we meet people who are the master in networking, they guide us to do some like this QoS in networking sites, because QoS will be main issue in the future. Thats why we select the MPLS approach to UMTS to provide QoS. Secondly our project advisor guides us that it is not necessary to do whole new thing in FYP rather do rather research or study based project. The advantage of this project is to know more about IP, MPLS, history, background, architecture and its future. The world is coming more toward IP, so it will be very helpful to us in the future.
1.3 MPLS Multiprotocol Label Switching, an IETF initiative that integrates Layer 2 information about network links (bandwidth, latency, utilization) into Layer 3 (IP) within a particular autonomous system--or ISP--in order to simplify and improve IP-packet exchange. MPLS gives network operators a great deal of flexibility to divert and route traffic around link failures, congestion, and bottlenecks. From a QoS standpoint, ISPs will better be able to manage different kinds of data streams based on priority and service plan. For instance, those who subscribe to a premium service plan, or those who receive a lot of streaming media or high-bandwidth content can see minimal latency and packet loss. When packets enter a MPLS-based network, Label Edge Routers (LERs) give them a label (identifier). These labels not only contain information Performance Analysis of MPLS in UMTS Page 17
based on the routing table entry (i.e., destination, bandwidth, delay, and other metrics), but also refer to the IP header field (source IP address), Layer 4 socket number information, and differentiated service. Once this classification is complete and mapped, different packets are assigned to corresponding Labeled Switch Paths (LSPs), where Label Switch Routers (LSRs) place outgoing labels on the packets. With these LSPs, network operators can divert and route traffic based on data-stream type and Internet-access customer. [1]
1.4 3G (third generation of mobile telephony) 3G refers to the third generation of mobile telephony (that is, cellular) technology. The third generation, as the name suggests, follows two earlier generations. 1. 2. 1G 2G
The International Telecommunications Union (ITU) defined the third generation (3G) of mobile telephony standards IMT-2000 to facilitate growth, increase bandwidth, and support more diverse applications. For example, GSM could deliver not only voice, but also circuit-switched data at speeds up to 14.4 Kbps. But to support mobile multimedia applications, 3G had to deliver packet-switched data with better spectral efficiency, at far greater speeds. [2]
1.5 Information about upcoming chapters The first chapter in the book is about introduction to the project, its objective and the software used. This chapter also includes the summary of whole thesis. The second chapter includes information and details about MPLS background, architecture and operation in IP network. The third chapter of this book tells about OPNET, its models, layers that are nodes, process and network models and layers, its advantages and feature. OPNET also contains editors that are project editor, node editor, process editor, link editor, path editor, packet Performance Analysis of MPLS in UMTS Page 18
format editor, probe editor and simulation sequence editor. Then we have discussed that why we used this software instead of others. In the fourth chapter, designation, implementation of MPLS and IP is done in conventional IP Network. Taking their comparison and analysis graphs. The fifth chapter includes information and details about 3G background, architecture, and its core network. In the sixth chapter, the designation and implementation of MPLS and IP in 3G is done. Performance analysis is checked and takes the graphs. The seventh chapter includes application, practical implementation, conclusion and future work.
Page 19
Chapter # 2 Multi Protocol Label Switching
2 .1 Introduction to MPLS Multiprotocol label switching is a mechanism in high performance telecommunication networks which carries and direct from one network node to the next with the help of labels. MPLS make it easy to create Virtual Links between distant nodes. It can encapsulate packet of various network protocols. MPLS is highly scalable, protocol agnostic, data carrying mechanism. In an MPLS network, data packet is assigned labels. Packet forwarding decisions are made solely on the contents of this label, without the need to examine the packet itself. This allows one to create end to end circuits across any type of transport. The primary benefit is to eliminate dependence on a particular Data Link Layer technology, such as ATM, Frame Relay, SONET or Ethernet, and eliminate the need for multiple layer 2 networks to satisfy different types of traffic. MPLS belongs to the family of packet switched networks.
MPLS operates at an OSI Model layer that is generally considered to lie between traditional definitions of layer 2 (Data link layer) and layer 3 (Network layer), and thus is often referred to as layer 2.5 protocol. It was designed to provide a unified data carrying service for both circuit based clients and packet switching clients which provide a datagram service model. It can be used to carry many different kinds of traffic, including IP packets, as well as native ATM, SONET, and Ethernet frames.
A number of different technologies were previously deployed with essentially identical goals, such as Frame Relay and ATM. MPLS technologies have evolved with the strengths and weaknesses of ATM in mind. Many network engineers agree that ATM should be replaced with a protocol that requires less overhead, while providing connection oriented
Page 20
service for variable length frames. MPLS is currently replacing some of these technologies in the future, thus aligning these technologies with current and future technology needs.
In particular, MPLS dispense with the cell switching and signaling protocol baggage of ATM. MPLS recognizes that small ATM cells are not need in the core of modern networks, since optical networks are so fast that even full length 1500 byte packets dont incur significant real time queuing delays. [3]
Figure 2.1 Layer Formats of MPLS 2.2 History MPLS was originally proposed by a group of Engineers from Ipsilon Networks, but their IP switching technology, which was defined only to work over ATM, did not achieve market dominance. Cisco system, introduced a related proposal, not restricted to ATM transmission, called Tag Switching. It was a Cisco proprietary proposal, and was renamed Label Switching. It was handed over the IETF for open standardization. The IETF work involved proposals from other vendors, and development of a consensus protocol that combined features from several vendors work. One original motivation was to allow the creation of simple high speed switches, since for a significant length of time it was impossible to forward IP packets entirely in hardware. However, advances in VLSI have made such devices possible. Therefore the advantages of MPLS primarily revolve around the ability to support multiple service models and perform traffic management. MPLS also offers a robust recovery framework that goes beyond the simple protection rings of Synchronous optical Networking (SONET/SDH). [4]
Page 21
2.3 HOW MPLS Work? MPLS works by prefixing packets with an MPLS header, containing one or more Labels. This is called a Label stack.
Figure 2.2 MPLS header Each label stack entry contains four fields: A 20 bit label value. A 3 bit Traffic Class for QoS(quality of service ) priority(experimental) and ECN(Explicit congestion Notification). A 1 bit bottom of stack flag. If this is set, it signifies that the current label is the last in the stack. An 8 it TTL (time to live) field.
These MPLS labeled packets are switched after a label lookup/switch instead of a lookup into the IP table. As mentioned above, when MPLS was conceived, label lookup and Label switching were faster than a Routing table or RIB (Routing Information Base) lookup.
Figure 2.3 MPLS Architecture Performance Analysis of MPLS in UMTS Page 22
The entry and exit points of an MPLS network are called Label edge routers (LER), which respectively, push an MPLS label onto an incoming packet and POP it off the outgoing packet. Routers that perform routing based on the label are called Label Swapping (LSR). In some applications, the packet presented to the LER already may have a label, so that the new LER pushes a second label onto the packet. Labels are distributed between LERs and LSRs using the Label Distribution Protocol (LDP). Label switch Router in an MPLS Network regularly exchange label and reach ability information with each other using standardized procedures in order to build a complete picture of the network they can then use to forward packets. Label Switch Paths (LSPs) are established by the network Operator for a variety of purposes, LSPs is as create network based IP virtual private networks or to route traffic along specified Paths through the network. In many respects, LSPs are not different from PVCs in ATM or Frame Relay networks, except that they are not dependent on a particular Layer 2 technology.
Figure 2.4 MPLS table
In the specific context of an MPLS based virtual private network (VPN), LSRs that function as ingress and/or egress routers to theVPN are often called PE (provider Edge) routers. Devices that function only as transit routers are similarly called P (provider) routers. When an unlabeled packet enters the ingress router and needs to be passed on to an MPLS tunnel, the router first determines the
Page 23
Forwarding Equivalence Class (FEC) the packet should be in, and then inserts one or more labels in the packets newly created MPLS Header. The packet is then passed on to the next hop router for this tunnel.
When a labeled packet is received by an MPLS router, the topmost label is examined. Based on the contents of the label a swap, push (Impose) or POP (dispose) operation can be performed on the packets label stack. Routers can have prebuilt lookup tables that tell them which kind of operation to do based on the topmost label of the incoming packet so they can process the packet very quickly.
1.
In a swap operation the label is swapped with a new label, and the packet is forward along the associated with the new label.
2. In a push operation a new label is pushed on top of the existing label, effectively encapsulating the packet in another layer of MPLS. This allows hierarchical routing of MPLS packets. This is notably used by MPLS VPNs. 3. In a pop operation the label is removed from the packet, which may reveal an inner label below. This process is called decapsulation. If the popped label was the last on the label stack, the packet leaves the MPLS tunnel. This is usually done by the egress router.
During these operations, the contents of the packet below the MPLS Label stack are not examined. Indeed transit routers typically need only to examine the topmost label on the stack. The forwarding of the packet is done based on the contents of the labels, which allows Protocol independent packet forwarding that does not need to look at a protocol dependent routing table and avoids the expensive IP Longest prefix match at each hop.
At the egress router, when the last label has been popped, only the payload remains. This can be an IP packet, or any of a number of other kinds of payload packet. The egress router must therefore have routing information for the packets payload, since it must forward it without the help of label lookup tables. An MPLS transit router has no such requirement. MPLS can make use
Page 24
of existing ATM network or frame relay infrastructure, as its labeled flows can be mapped to ATM or Frame Relay virtual circuit identifiers, and vice versa. [5]
2.4 HOW MPLS Paths are established? There are two standardized protocols for managing MPLS paths: 1. LDP (Label Distribution Protocol) 2. RSVP-TE (Resource Reservation Protocol), an extension version of RSVP
An MPLS header does not identify the type of data carried inside the MPLS path. If one wants to carry two different types of traffic between the same two routers, with different treatment by the core routers for each type, one has to establish a separate MPLS path for each type of traffic. [6]
Figure 2.5 MPLS LSP 2.5 Comparison of MPLS and IP
MPLS cannot be compared to IP as a separate entity because it works in conjunction with IP and IPs IGP routing protocols. MPLS LSPs provide dynamic, transparent virtual networks with support for traffic engineering, the ability to transport layer 3(IP) VPN with overlapping address spaces, and support for layer 2 pseudowire using pseudowire Emulation Edge to Edge (PWE3) that are capable of transporting a variety of transport Performance Analysis of MPLS in UMTS Page 25
payload (IPv4, IPv6, ATM, Frame Relay,etc). MPLS capable devices are referred to as LSRs. LSR devices provide traffic engineering function can be defined using Explicit hop by hop configuration Dynamically routed by constrained shortest path first (CSPF) algorithm or Configured as a loose route that avoid a particular IP or that is partly explicit and partly dynamic.
In a pure IP network, the shortest path to a destination is chosen even when it becomes more congested. Meanwhile, in an IP network With MPLS Traffic engineering CSPF routing, constraints such as the RSVP bandwidth of the traversed links can be considered, such That the shortest path with available bandwidth will be chosen. MPLS Traffic Engineering relies upon the use of TE extensions to OSPF or IS-IS and RSVP. Besides the constraint of RSVP bandwidth, users can also define their own constraint by specifying link Attributes and special requirements for tunnels to route (or not to route) over links with certain attributes. [7]
2.6 Signaling protocol of MPLS The following are the signaling protocol used in MPLS network as
1. LDP (label Distribution Protocol) 2. CR LDP (Constraint Based LDP) 3. RSVP TE (Resource Reservation Protocol Traffic Engineering)
1. LDP In the MPLS (Multi Protocol Label Switching) 2 label switching routers (LSR) must agree on the meaning of the labels used to forward traffic between and through them. LDP (Label Distribution Protocol) is a new protocol that defines a set of procedures and messages by which one LSR (Label Switched Router) informs another of the label bindings it has made.
Page 26
The LSR uses this protocol to establish label switched paths through a network by mapping network layer routing information directly to data-link layer switched paths. These LSPs may have an endpoint at a directly attached neighbor (like IP hop-by-hop forwarding), or may have an endpoint at a network egress node, enabling switching via all intermediary nodes. A FEC (Forwarding Equivalence Class) is associated with each LSP created. This FEC specifies which packets are mapped to that LSP. Two LSRs (Label Switched Routers) which use LDP to exchange label mapping information are known as LDP peers and they have an LDP session between them. In a single session, each peer is able to learn about the others label mappings, in other words, the protocol is bi-directional. There are 4 sorts of LDP messages: 1. Discovery messages 2. Session messages 3. Advertisement messages 4. Notification messages. Using discovery messages, the LSRs announce their presence in the network by sending Hello messages periodically. This hello message is transmitted as a UDP packet. When a new session must be established, the hello message is sent over TCP. Apart from the Discovery message; all other messages are sent over TCP. The notification messages signal errors and other events of interest. There are 2 kinds of notification messages: 1. Error notifications; these signal fatal errors and cause termination of the session 2. Advisory notifications; these are used to pass on LSR information about the LDP session or the status of some previous message received from the peer. 2. CR-LDP CR-LDP (constraint-based LDP) contains extensions for LDP to extend its capabilities.
Page 27
This allows extending the information used to setup paths beyond what is available for the routing protocol 3. RSVP-TE The RSVP protocol defines a session as a data flow with a particular destination and transport-layer protocol. However, when RSVP and MPLS are combined, a flow or session can be defined with greater flexibility and generality. The ingress node of an LSP (Label Switched Path) uses a number of methods to determine which packets are assigned a particular label. Once a label is assigned to a set of packets, the label effectively defines the flow through the LSP. We refer to such an LSP as an LSP tunnel because the traffic through it is opaque to intermediate nodes along the label switched path. New RSVP Session, Sender and Filter Specific objects, called LSP Tunnel IPv4 and LSP Tunnel IPv6 have been defined to support the LSP tunnel feature. The semantics of these objects, from the perspective of a node along the label switched path, is that traffic belonging to the LSP tunnel is identified solely on the basis of packets arriving from the "previous hop" (PHOP) with the particular label value(s) assigned by this node to upstream senders to the session. In fact, the IPv4 (v6) that appears in the object name only denotes that the destination address is an IPv4 (v6) address. When referring to these objects generically, the qualifier LSP Tunnel is used. In some applications it is useful to associate sets of LSP tunnels. This can be useful during reroute operations or in spreading a traffic trunk over multiple paths. In the traffic engineering application, such sets are called traffic engineered tunnels (TE tunnels). To enable the identification and association of such LSP tunnels, two identifiers are carried. A tunnel ID is part of the Session object. The Session object uniquely defines a traffic engineered tunnel. The Sender and Filter Spec objects carry an LSP ID. The Sender (or Filter Spec) object, together with the Session object, uniquely identifies an LSP tunnel. [8]
2.7 MPLS fast rerouting In the event of a network element failure when recovery mechanisms are employed at the IP layer, restoration may take several second Performance Analysis of MPLS in UMTS which may be acceptable for real time Page 28
application such as VOIP. In contrast, MPLS local protection meets the requirements of real time application with recovery times comparable to those of SONET rings of than 50 ms.[9]
2.8 MPLS versus Frame Relay Performance Frame Relay aimed to make more efficient use of existing physical resources, which allow for the under provisioning of data service by Telecommunications Companies( Telcos ) to their customers, as clients were unlikely to be utilizing a data service 100 percent of the time. In more recent years, frame relay has acquired a bad reputation in some markets because of excessive bandwidth overbooking by these Telcos. Tecos often sell frame relay to businesses looking for a cheaper alternative to dedicated lines; its use in different geographic areas depended greatly on governmental and telecommunication companies policies.[10]
2.9
MPLS versus ATM performance While the underlying protocols and technologies are different, both MPLS and ATM provide a connection oriented service for transporting data across computer networks. In both technologies, connections are signaled between end points, connection state is maintained at each node in the path, and encapsulated techniques are used to carry data across the connection. Excluding difference in the signaling protocols (RSVP/LDP) for MPLS and PNNI (Private Network to Network Interface for ATM) these still remain significant differences in the behavior of the technologies.
The most significant difference is in the transport and encapsulation methods. MPLS is able to work with variable length packets while ATM transports fixed length (byte) cells. Packets must be segmented, transported and re-assembled over an ATM network using an adaption layer, adds significant complexity and overhead to the data stream. MPLS, on the other hand, simply adds a label to the head of each packet and transmits it on the network. Differences exist, as well, in the nature of the connections. An MPLS connection (LSP) is unidirectional allowing data flow in only one direction between two endpoints. Performance Analysis of MPLS in UMTS Page 29
Establishing two way communications between end points require a pair of LSPs to be established. Because 2 LSPs are required for connectivity, data flowing in the forward direction may use a different path from data flowing in the reverse direction. Both ATM and MPLS support tunneling of connections inside connections. MPLS uses label stacking to accomplish this while ATM uses virtual paths. MPLS can stack multiple labels to from tunnels within tunnels. The ATM virtual path indicator (VPI) and virtual indicator (VCI) are both carried together in the cell header, limiting ATM to a single level of tunneling. []
The biggest single advantage that MPLS has over ATM is that it was designed from that the start to be complementary to IP. Modern routers are able to support both MPLS and IP natively across a common interface allowing network operators great flexibility in the network design and operation. ATM is incompatibilities with IP require complex adaption, making it comparatively less suitable for todays predominantly IP networks.
2.10
MPLS Application MPLS addresses todays network backbone requirements effectively by providing a standard based solution that accomplishes the following: [11]
Improve packet forwarding performance in the network o MPLS enhance and simplifies packet forwarding through routers using layer 2 switching model o MPLS is simple, which allow easy implementation o MPLS increases network performance
Support QoS and CoS for service differentiation o MPLS uses traffic engineering path setup and achieve service level guarantees. o MPLS provide constraint based and explicit path setup.
Page 30
Support network scalability Integrate IP and ATM in the network o MPLS provides a bridge between access IP and core ATM. Builds interoperable networks o MPLS facilitates IP- over synchronous optical network (SONET) integration in optical switching.
Page 31
Chapter # 3
OPNET Modeler 14.0

The Optimized Network Engineering Tool (OPNET) is a commercial simulation product of the MIL3 Company of Arlington VA. It employs a Discrete Event Simulation approach that allows large numbers of closely spaced events is a sizable network to be represented accurately and efficiently.
The OPNET software is a modular suite able to simulate entire networks up to several dozen nodes. This includes all layers of the OSI reference mode, from physical links up to application demands. Its primary function, according to OPNETs website is the support of network planning groups and application developers. [12]
3.1 Network Simulator Selection Network simulator is used to effectively integrate laboratory components and to build different networks on laboratory level without significantly increasing the workload of man. The main features for network simulator selection are: Ability to simulate a wide range of networking technologies Ease of use Free or low cost Higher simulation performance
3.2 Why OPNET? There are various simulation experiment environments. We focus on allowing the same code to run in simulation and on live network.
Page 32
OPNET and NS2 are the two most popular network simulators, targeting a wider range of networks and protocols. NS2 is an open source network simulator. NS2 is widely used for network research in academia. NS2 is also free ware. However, NS2 is more difficult o learns and lacks of user interface. It requires the users to learn and use non standard scripting interfaces such as TCL. It takes a significant amount of time to get OPNET Simulator familiar with NS2. OPNET is the best network simulator for the following reasons: OPNET is much easier to use than NS2. It provides a very convenient Graphic User Interface (GUI). OPNET can be used to model the entire network, including its routers, switches, protocols, servers, and the individual application they support. A large range of communication systems from a single LAN to global inter- works can be supported. OPNET software (with model source code) is available for FREE to the academic research and teaching community. Students can download and install IT Guru Academic Edition at home. The OPNETs discrete event engine for network simulations is the fastest and most scalable commercially available solution. It usually take just a few minutes to complete simulations []
3.3 What is OPNET? OPNET project consist of easily created and compared scenarios. For such scenario, different data and network topologies can be analyzed. OPNET offers up to four simulation models: Discrete Event Simulation (DES) Flow analysis ACE Quick predict Hybrid Simulation Performance Analysis of MPLS in UMTS Page 33
In our project, due to the license restrictions, only DES is examined, the other simulation types were not available. DES is a packet based simulation, and therefore best suited for researching protocol behavior and application performance.
Figure 3.6 OPNET 3.3.1 OPNET Modeler Opnet provides four editors to develop a representation of a system being modeled. These editors, the Network, Node, Process, and Parameter Editors, are organized in a hierarchical fashion, as seen in figure. Each level of the hierarchy describes different aspects of the complete model being simulated. Models developed at one level of the hierarchy are used by models at next higher level. This leads to a highly flexible simulation environment where generic models can be developed and used in many different scenarios.
Page 34
Figure 3.7 MODELS
For network research and development used primarily to design and study network technologies, ranging from communications protocols to network equipment and systems. Modeler is the only package to supply the model library and library extensions with open source code.
Features of OPNET Modeler include: Integrate Debugger to validate simulation behavior or track problems. Tools to display simulation results, plotting and analyzing time series, histogram, probability functions, parametric curves and confidence intervals. Support to export to spread sheets. Hybrid simulations improve performance by combining discrete events simulation with analytical modeling Runtime environment to deliver proprietary protocol and device models to end users, running simulations and working at the network level only. Hierarchical network models, complex network topologies can be managed with unlimited sub network nesting Windows NT, Windows 2000 and UNIX supported
Page 35
The OPNET Modeler network view is arranged in hierarchical layers that directly depict the structure of networks, equipments and protocols. Each layer is edited and controlled with a dedicated editor.
Figure 3.8 Editor
3.3.1.1 The Network Layer The Network Editor graphically represents the topology of a communications network. Network consists of Node and link objects, configurable via dial boxes. Objects of node and link models can be created or selected from the OPNET library. The Network Editor provides geographical context, with the physical characteristics reflected appropriately in the network simulation.
Figure 3.9 Network Layer
Page 36
3.3.1.2 The Node Layer The Node Editor captures the architecture of a network device or system by depicting the flow of data between functional elements, called Modules. Each module can generate, send and receive packets from other modules to perform its function within the node. Modules typically represent applications, protocol layers, algorithms and physical resources, such as buffers, ports and buses. Modules are assigned process models to achieve any required behavior
Figure 3.10 Node Layer
3.3.1.3
The Process Layer The process Editor uses a finite state machine approach to support specification, at any
level of detail of protocols, resources, applications, algorithms and queuing policies. State and transitions graphically define the progression of a process in response to events. Each state of a process model contains C/C++ code, supported by a library of functions designed for protocol programming.
Page 37
FSM can define private state variables and can make calls to code in user provided libraries. FSMs are dynamic and can be spawned during simulation in response to specific events. Dynamic FSMs simplify specification of protocols that manages a scalable number of resources or session, such as TCP or ATM. The user can developed entirely new process models or use the models in OPNET Technologies Model library as a starting point.
Figure 3.11 Process Layer
3.4
Main features OPNET inherently has three main functions: Modeling Simulation & Analysis
For modeling, it provides intuitive graphical environment to create all kinds of models of protocols. Performance Analysis of MPLS in UMTS Page 38
For simulation, it uses 3 different advanced simulations technologies and can be used to address a wide range of studies. For Analysis, the simulation result and data can be analyzed and displayed very easily. User friendly graphs, charts, statistics and even animation can be generated by OPNET for users convenience. According to the OPNET whitepaper, OPNETs detailed features include: Fast discrete event simulation engine Lot of component library with source code Object oriented modeling Hierarchical modeling environment Scalable wireless simulation support 32 bit and 64 bit graphical user interface Customizable wire modeling Discrete Event, Hybrid and Analytical simulation Grid computing support Integrated, GUI based debugging and analysis Open interface for integrating external component libraries
3.4.1
Project Editor The staging area for creating a network simulation is the Project Editor. This is used to
create a network model using models from standard library, collect statistics about the network, run the simulation and view the results. Using specialized editors accessible from the Project Editor via File >> New one can create node and process models, build packet formats and
create filters and parameters.
Page 39
Figure 3.12 project Editor 3.4.2 The Node Editor The Node Editor is used to create models of nodes. The node models are then used to create node instances within networks in the project Editor. Internally, OPNET node models have a modular structure. You define a node by connecting various modules with packet streams and statistics wires. The connections between modules allow packets and status information to be exchange between modules. Each module placed in a node serves a specific purpose, such as generating packets, queuing packets, processing packets, or transmitting and receiving packets.
Figure 3.13 Node Editor Performance Analysis of MPLS in UMTS Page 40
3.4.3
The process Model Editor To create process models which control the underlying functionality of the node models created in the Node Editor one can use the process editor. Process models are represented by finite state machines (FSM) and are created with icons that represent states and line that representation transitions between states. Operations performed in each state or for a transition are described in embedded C/C++ code blocks.
Figure 3.14 Process Model Editor 3.4.4 The Link Model Editor This editor enables for the possibility to create new types of link objects. Each new type of link can have different attributes interfaces and representation. Specific comments and keywords for easy recognition are also possible.
Figure 3.15 link Model Editor
Page 41
3.4.5
The Path Editor The path Editor is used to create new path objects that define a traffic route. Any protocol model that uses logical connections or virtual circuits such as MPLS, ATM, Frame Relay etc can use paths to route traffic.
Figure 3.16 Path Editor 3.4.6 The packet format Editor By making of this editor it is possible to define the internal structure of packets as a set of fields. A packet format contains one or more fields, represented in the editor as colored rectangular boxes. The size of the box is proportional to the number of bits specified as the fields size.
Figure 3.17 packet format Editor Performance Analysis of MPLS in UMTS Page 42
3.4.7 The Probe Editor This editor is used to specify the statistics to be collected. By using different probes there are several different types of statistics that can be collected, including global statistics, link statistics, node statistics, attribute statistics, and several types of animation statistics. It is mentioned that similar possibilities for collecting statistics are also available under the project Editor. These are however not as powerful as the probe Editor.
Figure 3.18 probe Editor 3.4.8 The simulation Sequence Editor In the simulation Sequence Editor additional simulation constrains can be specified. Simulation sequences are represented by simulation icons, which contain a set of attributes that control the simulations run time characteristics.
Page 43
Figure 3.19 simulation sequence Editor
3.4.9 The Analysis Tool The Analysis Tool has several useful additional features like for instance one can create scalar graphics for parametric studies, define templates for statistical data, create analysis configurations to save and view later, etc.
Figure 3.20 Analysis Editor 3.4.10 the project Editor Work Space There are several areas in the project Editor Window that are important for building an executing a model.
Page 44
Figure 3.21 Project Editor Work space
3.4.11
The Menu Bar Each editor has its own menu bar. The menu bar shown below appears in the
project.
Figure 3.22 Menu bar 3.4.12 Buttons Several of the more commonly used menu bar can also be activated through buttons. Each editor has its own set of buttons. The buttons shown below appear in the project Editor.
Figure 3.23 Buttons Performance Analysis of MPLS in UMTS Page 45
3.5
How to make a scenario in OPNET: OPNET is a network simulation package which is relatively easy to use and learn. It
allows user to use point to point and click to create and configure simple or sophisticated network systems, and conduct simulations to study and analyze the systems performance.
OPNET Modeler has additional functionality that allows the user to modify existing system components and create new ones, A user working typical OPNET simulation proceeds to complete the following steps:
1. Follow the configuration Wizard instructions to create a new project and a first simulation scenario. 2. Point and click to configure the first simulation scenario: Create the network topology Select and configure the relevant applications
o Create the user profiles to specify how the configured application are used by end systems o Deploy application by associating user profiles with the end system o Configure non default parameters of the relevant protocols o Specify the statistics to be collected during simulation o Configure scenario parameter such as simulation duration, random number generator seed etc. 3. Create a copy of the first scenario and modify the values of simulation parameters as needed. 4. Execute the simulation for all scenarios. 5. Analyze the graphs and values of the collected simulation statistics. 6. Repeat step 2 through 5 until the result is valid.
Page 46
Chapter # 4
Performance Analysis of MPLS in conventional IP Network
4.1 Introduction To provide the QoS, to the conventional IP Network by reducing the delay factor in Interactive services. The one which are very delay sensitive and causes a lot of information to lost. To avoid such thing the new switching approach is used, called the MPLS (Multi Protocol Label Switching) approach. In this part, we describe implementation of an IP and MPLS in conventional Network. Here we have implemented three different scenarios. The following applications compared in these scenarios are:
FTP application Voice application
4.2
OPNET implementation To implement the above scenario in OPNET simulator, we have followed some steps which are given below: Step 1
Open OPNET 14.0 modeler Go to file and select new project Give any name to it Then select create empty scenario Select the scenario whether OFFICE, CAMPUS, WORLD etc. we select campus scenario. You will get a workspace along with an object palette According to our project requirement we have done the above as:
Page 47
Figure 4.24 OPNET
Figure 4.25 New Project Step 2
Go to object palette
Figure 4.26 Object Palette Performance Analysis of MPLS in UMTS Page 48
Select the following equipments and drag them into the workspace one by one The equipments list is given below: 1. Profile configuration 2. Application configuration 3. IP router Ethernet2_slip8_gtwy 4. Workstation (ppp_wkstn) 5. Link (ppp DS3)
Step 3 We have assigned the following attributes to the nodes collected so far. Jitter Packet Delay Variation Packet end to end Delay For IP Network Connect all the nodes via DS3 links Assign proper IP address Assign proper interface to all nodes Apply the routing protocol e.g. RIP, IGRP Select application and profiles and service we are using Select some statistics we want to analyze 4.2.1 IP Architecture
Figure 4.27 IP architecture
Page 49
For MPLS
Select the following components 1. LER (label Edge router ) 2. LSR (label switch router ) 3. Application Config 4. Profile Config 5. LINK (PPP DS3)
For MPLS network We have assigned the following attributes to the nodes collected so far. Connect all the nodes via DS3 link Apply MPLS signaling protocol Select application and profile and services we are using Select some statistics we want to analyze 4.2.2 MPLS architecture
Figure 4.28 MPLS Architecture Step 4 Then we simulate the scenario and viewed the result i.e. graphs
Page 50
4.3 comparing Graphs and result 4.3.1 VOICE APPLICATION The following tables show voice application for seed values of 128. The table show minimum, maximum and average values for different application i.e. jitter, packet delay variation, traffic received and sent etc. we are comparing these application in different scenarios.
Jitter: When two consecutive packets leave the source node with time simple t1 and t2 and are played back at the destination node at time t3 and t4 then jitter= (t4-t3) - (t2-t1). Negative jitter indicates that the time difference between the packets at the destination node less than at the source node. Voice packet delay variation: Variation among end to end delays for voice packets received by the node End to end delay for a voice: The total voice packets delay, called analog to analog or mouth to ear delay = network delay + encoding delay +decoding delay+ compression delay + decompression delay. Network delay is the time at which the sender node gives the packet to RTP to the time the receiver got it from RTP. 4.3.1.1 Tables These are the values of simulation of Voice application of IP and MPLS in conventional Network.
Page 51
Table 4.1 IP Global statistic
Table 4.2 IP Node statistic
Table 4.3 MPLS Global statistic 4.3.1.2 Graphs: Comparing through graphs
Page 52
This graph show that the jitter, as we already discussed, is the inter packet variation which is greater in IP graph as compared to MPLS graph below the IP graph. The horizontal show the simulation time of the scenario while the vertical show the jitter for both scenarios The max value of jitter in IP as, 750s The max value of jitter in MPLS as, 15s
Graph 4.1 Voice jitter
This graph shows the Voice packet Delay variation in IP and MPLS scenario. The max value of packet delay occur in IP is, 200ms The max value of packet delay occur in MPLS is, 17s
Graph 4.2 Voice packet delay variation
Page 53
The graph shows the voice packet end to end delay in second. As from the graph, it is clear that the end to end delay of the IP is more than MPLS Max end to end delay for IP is, 1.4s Max end to end delay for MPLS is, 70ms As it is clear that more processing, compression, network delay etc, in IP than in MPLS
Graph 4.3 Voice packet end to end delay 4.3.2.1 FTP application This is same scenario like voice, but for FTP server is taken
Figure 4.29 FTP scenario FTP tables This is the FTP application table after simulating the FTP scenario of IP and MPLS
Page 54
Table 4.4 FTP Global statistic in IP
Table 4.5 FTP Global statistic in MPLS
4.3.2.2 Comparing through graphs The graph shows the FTP download response for IP and MPLS scenario The download response for IP is less than MPLS The max download response for IP is, 8.8ms The max download response for MPLS is, 9.5ms
Graph 4.4 FTP Download Response Performance Analysis of MPLS in UMTS Page 55
The graph show the FTP traffic received in IP and MPLS in terms of bytes per second It is clear from the graph that there is greater amount of FTP traffic received in MPLS as compared to IP The max amount of traffic in IP is, 300 bytes The max amount of traffic in MPLS is 350 bytes
Graph 4.5 FTP Traffic Received in bytes/second
This is the same graph as above graph but here the unit of traffic received is packet per second The same case here greater amount of FTP packets receive in MPLS than IP The max amount packet received in IP is, 10.2packet/ms The max amount packet received in MPLS is, 12.5packet/ms
Graph 4.6 FTP Traffic Received in packets/second
Page 56
This graph show the same result like the traffic received in terms of bytes per second but here the traffic send Max amount of traffic send in IP is, 300 bytes/s Max amount of traffic send in MPLS is, 350bytes/s
Graph 4.7 FTP Traffic Send in bytes/second
This is the same graph as above graph but here the unit of traffic send is packet per second The same case here greater amount of FTP packets send in MPLS than IP The max amount packet send in IP is, 10.2packet/ms The max amount packet send in MPLS is, 12.5packet/ms
Graph 4.8 FTP Traffic Send packets/second
Page 57
The graph shows the upload response for both IP and MPLS As it is clear from the graph that the upload response of the MPLS is greater than the IP Network The max upload response for IP is, 8.7s The max upload response for MPLS is, 9ms
Graph 4.9 FTP Download Response
4.4 conclusions We observed from above graphs that by applying MPLS to the core of conventional IP Network the delay factor is reduced. And this way, they provide fast communication and QoS.
Page 58
Chapter # 5
Universal Mobile Telecommunication System
5.1 Background UMTS stands for Universal Mobile Telecommunication System. The UMTS network is a wireless 3G (third generation) network that provides high bandwidth voice and data service to users of mobile devices. 3G is a category of digital cellular radio systems developed under the standard IMT -2000(International Mobile Telecommunication-2000)
The UMTS network is also called 3GSM (Global System for Mobile communications) because it evolved from that system. The air interface for the UMTS network is based on WCDMA (wideband code Division Multiple Access) and includes the HSPA (High Speed Packet Access) specification. The internet protocol was based on GPRS (General Packet Radio Service), which evolved into EDGE (Enhanced Data rates for Global Evolution), which were considered 2.5G standards.
The 3G systems were created with the intention of allowing users to have global mobility with services including internet, data, messaging, paging, and telephony. The idea was to provide consistent service to roaming mobile customers anywhere in the world. A combination of terrestrial based wireless services and satellite transmissions were designed to provide this availability.
There are several ways in which the UMTS network differs from prior systems. One way is that previously, cellular systems were mainly circuit switched, while UMTS is packet switched. It also has higher bandwidth than previous systems.
Page 59
The services provided by UMTS have different Quality of Service (QOS) target data rates. These are 144 kbps (kilo bytes per second) for satellite use and outdoor rural use, 384 kbps for use in outdoor in urban environments; and 2048 kbps for indoor use and outdoor use that is low range. There are four specified classes of service. The conversational class includes voice services, video gaming, and video telephony. The streaming class includes multimedia, webcasting, and video on demand. The interactive class includes web browsing, accessing, data bases, and network gaming, while the background class includes email, downloading, and SMS (Short Message Service) messaging. [13]
5.2
UMTS Architecture A UMTS network consists of three interacting domains Core Network (CN) UMTS Terrestrial Radio Access Network (UTRAN) User Equipment (UE)
Figure 5.30 UMTS Architecture The main function of the core network is to provide switching, routing and transit for user traffic. Core Network also contains the data base and network management functions. The basic Core Network architecture for UMTS is based on GSM network with GPRS. All equipment has to be modified for UMTS operation and services. The UTRAN provides the Performance Analysis of MPLS in UMTS Page 60
air interface access for User Equipment. Base Station is referred as Node B and control equipment for Node Bs is called Radio Network Controller (RNC). []
It is necessary for a network to know the approximate location in order to be able to page user equipment. Here is the list of system areas from largest to smallest. UMTS systems(including satellite) Public Land Mobile Network (PLMN) MSC/VLR or SGSN Location Area Routing Area (PS domain) UTRAN Registration Area( PS domain) Cell Sub cell
5.2.1 Core Network The core network is divided in circuit switched and packet switched domains. Some of the circuit switched elements are Mobile services Switching Center (MSC), Visitor Location register (VLR) and Gateway MSC. Packet switched elements are serving GPRS support Node (SGSN) And Gateway GPRS Support Node (GGSN). Some network elements, like EIR, HLR, VLR and AUC are shared by both domains.
Figure 5.31 3G architecture
Page 61
The Architecture of the Core Network may change when new services and features are introduced. Number portability Database (NPDB) will be used to enable user to change the network while keeping their old phone number. Gateway Location Register (GLR) may be used to optimize the subscriber handling between network boundaries. MSC, VLR and SGSN can merge to become a UMTS MSC. [] 5.2.2 UMTS Terrestrial Radio Access Network (UTRAN) Wide band CDMA technology was selected for UTRAN air interface. UMTS WCDMA is a Direct Sequence CDMA system where user data is multiplied with quasi random bits derived from WCDMA Spreading codes. In UMTS, in addition to channelization, codes are used for synchronization scrambling. WCDMA has two basic modes of operation: 1. Frequency Division Duplex (FDD) 2. Time Division Duplex (TDD) The functions of Node B are: Air interface Transmission/Reception Modulation/Demodulation CDMA physical channel coding Micro Diversity Error Handling Closed loop power control
The functions of RNC are: Radio Resource Control Admission Control Channel Allocation Power Control Settings Handover Control Macro Diversity Ciphering Segmentation/Reassembly Broadcast Signaling Open loop power control Page 62
5.2.3 User Equipment (UE) The UMTS standard does not restrict functionality of the User Equipment in any way. Terminals work as an interface counterpart for Node B and have many different type identities. Most of these UMTS identity types are taken directly from GSM specification. [] International Mobile Subscriber Identity (IMSI) Temporary Mobile subscriber identity (TMSI) Packet temporary Mobile subscriber Identity (P-TMSI) Temporary Logical Link Identity (TLLI) Mobile station ISDN (MSISDN) International Mobile station Equipment identity (IMEI) International Mobile Station Equipment Identity and Software Number (IMEISN)
UMTS user equipment can operate in one of three modes of operation: PS/CS mode of operation: The UE is attached to both the PS domain and CS domain and the UE is capable of simultaneously operating PS service and CS services. PS mode of operation: The UE is attached to the PS domain only and may only operate services of the PS domain. However, this does not prevent CS like services to be offered over the PS domain (like VOIP). CS mode of operation: The UE is attached to the CS domain only and may only operate services of the CS domain. UMTS IC card has same physical characteristics as GSM SIM card. It has several functions: Support of one User Service Identity Module (USIM) application Support of one or more profile on the USIM. Update USIM specific information over the air Security functions User authentication Optional inclusion of payment methods Optional secure downloading of new applications Page 63
5.3 Quality of Service (QoS) Network Services are considered end to end, this means from a Terminal Equipment (TE) to another TE. An end to end service may have certain Quality of service (QoS) which is provided for the user of a network service. It is the user that whether he is satisfied with the provided QoS or not.
5.3.1 UMTS QoS Classes When defining the UMTS QoS Classes, also referred to as traffic classes, the restrictions and limitations of the air interface have to be taken into account. It is not reasonable to define complex mechanisms as have been in fixed networks due to different error characteristics of the air interface. The QoS mechanisms provided in the cellular networks have to be robust and capable of providing reasonable QoS resolution. There are four different QoS classes: Conversational class Streaming class Interactive class Background class
The main distinguishing factor between these QoS classes is how delay sensitive the traffic is: conversational class is meant for traffic which is very delay sensitive while Background class is the most delay insensitive traffic class. Conversational and streaming classes are mainly intended to be used to carry real time traffic flows. The main divider between them is how delay sensitive the traffic is conversational real time services, like video telephony, are the most delay sensitive applications and those data streams should be carried in conversational class. Interactive class and Background are mainly meant to be used by traditional internet applications like WWW, Email, Telnet, FTP and News. Due to looser delay requirements, compare to conversational and streaming classes, both provide better error rate by means of channel coding and retransmission. The main difference between interactive and Background class is that interactive class is mainly used by interactive applications, e.g. Performance Analysis of MPLS in UMTS Page 64
Interactive Email or interactive Web browsing, while Background class is meant for background traffic, e.g. background download of Emails or background file downloading. Responsiveness of the interactive applications is ensured by separating interactive and background applications. Traffic in the interactive class has higher priority in scheduling than Background class traffic, so background applications use transmission resources only when interactive applications do not need them. This is very important in wireless environment where the bandwidth is low compared to fixed networks. []
5.3.1.1 Conversational Class This class is used for the most delay sensitive traffic. Speech (voice) is the most common example of conversational class. Video games and video telephony are other examples. These services should be transmitted like that real time connections transmitted over the radio link. There will be no buffering and must require the guaranteed bit rate. The most well known use of this scheme is telephony speech (e.g. GSM). But with internet and multimedia a number of new applications will require this scheme, for example voice over IP and video over conferencing tools. Real time conversation is always performed between groups of end users. This is the only scheme where the required characteristics are strictly given by human perception. Real time conversation scheme is characterized by that the transfer time shall be low because of the conversational nature and at the same time that the time relation (variation) between information entities of the stream shall be preserved in the same way as for real time streams. The maximum transfer delay is given by the human perception of audio and video conversation. Therefore the limit for acceptable transfer delay is very strict, as failure to provide low enough transfer delay will result in unacceptable lack of quality. The transfer delay requirement is therefore both significantly lower and more rigorous than the round trip delay of the interactive traffic case.[]
Real time conversation- fundamental characteristics for QoS: Preserve time relation(variation ) between information entities of the stream Conversational pattern (rigid and low delay).
Page 65
5.3.1.2 Streaming class: In this class service are also transmitted same as real time connection. The delay is little bit variable and buffering is allowed in this class. Streaming multimedia is an example application, which is used as a rebuild technique that makes it to become visible as a steady and continuous stream. Bit rate is also guaranteed in this class. When the user is looking at (listening to) real time video (audio) the scheme of real time streams applies. The real time data flow is always aiming at a live (human) destination. It is a one way transport. This scheme is one of the newcomers in data communication, raising a number of new requirements in both telecommunications and data communication systems. It is characterized by that the time relations (variation) between information entities (i.e. samples, packets) within a flow shall be preserved, although it does not have any requirements on low transfer delay. The delay variation of the end to end flow shall be limited, to preserve the time relation (variation) between information entities of the stream. But as the stream acceptable delay variation over the transmission media is given by the capability of the time alignment function of the application. Acceptable delay variation is how much greater than the delay variation given by the limits of human perception.[] Real time streams fundamental characteristics for QoS: Preserve time relation (variation) between information entities of the stream.
5.3.1.3 Interactive class For data communication interactive class is used, such as interactive network games and web browsing, the delay is reasonably variable here. There is no guaranteed of the bit rate for the services in this class when the end user, that is either a machine or a human, is online requesting data from remote equipment (e.g. a server, this scheme applies). Examples of human interaction with the remote equipment are: web browsing, data base, server access. Example of machine interaction with the remote equipment is: polling for measurement records and automatic data base enquiries (tele machine).
Interactive traffic is the other classical data communication scheme that on an overall level is characterized by the request response pattern of the end user. At the message there is an Performance Analysis of MPLS in UMTS Page 66
entity expecting the message within a certain time. Round trip delay time is therefore one of the key attributes. Another characteristic is that the content of the packet shall be transparently transferred (with low bit error rate). [] Interactive traffic fundamental characteristics for QoS: Request response pattern Preserve payload content
5.3.1.4 Background Class This class tolerates the top delay and background. In this class downloading from internet is an example of service. Buffering is essential but there is no guarantee of the bit rate. Background traffic is one of the standard data communication schemes that are largely characterized by the fact that the destination will not expect the data within a certain amount of time. Therefore it is more or less insensitive about the delivery time. There is another characteristic that the packet content does not need to be clearly transferred. Transmitted data must have to be received error free. When the end user, that typically is a computer, sends and receives data files in the background, this scheme applies. Examples are background delivery of Email, SMS and download of data bases and reception of measurement records. Background traffic is one of the classical data communication schemes that on an overall level is characterized by that the destination is not expecting the data within a certain time. The scheme is thus more or less delivery time insensitive. Another characteristic is that the content of the packets shall be transparently transferred (with low bit rate). [] Background traffic fundamental characteristics for QoS:
The destination in not expecting the data within a certain time Preserve payload content
Page 67
Traffic class
Conversational class Conversational RT
Streaming class Streaming RT
Interactive class Interactive best effort
Background class Background best effort
Fundamental characteristics
Preserve time relation (variation ) between information entities of the stream
Preserve time relation(variation ) between information entities of the stream
Request response pattern
Destination is not expecting the data within a
Preserve payload content
certain time
Preserve payload content
Conversational pattern (stringent and low delay ) Example of the application voice Streaming video Web browsing Background download of emails
Table 5.6 QoS classes table
Page 68
Chapter # 6
Performance Analysis of MPLS in 3G Network To provide the QoS, to the UMTS Network by reducing the delay factor in Interactive services. The one which are very delay sensitive and causes a lot of information to lost. To avoid such thing the new switching approach is used, called the MPLS (Multi Protocol Label Switching) approach. This approach is applied to the core of UMTS Network. In this part, we describe implementation of an IP and MPLS in UMTS Network. Here we have implemented three different scenarios. The following applications compared in these scenarios are: Voice application FTP application
6.1 OPNET implementation To implement the above scenario in OPNET simulator, we have followed some steps which are given below: Step 1
Open OPNET 14.0 modeler Go to file and select new project Give any name to it Then select create empty scenario Select the scenario whether OFFICE, CAMPUS, WORLD etc. we select campus scenario. You will get a workspace along with an object palette
Step 2
Go to object palette Select the following equipments and drag them into the workspace one by one The equipments list is given below: 1. Profile configuration 2. Application configuration Page 69
3. IP router Ethernet2_slip8_gtwy 4. Workstation (ppp_wkstn) 5. Link (ppp DS3) Step 3 We have assigned the following attributes to the nodes collected so far. For simple UMTS Network Connect all the nodes via DS3 links Assign proper IP address Assign proper interface to all nodes Apply the routing protocol e.g. RIP, IGRP Select application and profiles and service we are using Select some statistics we want to analyze
UMTS Architecture
Figure 6.32 UMTS Scenario For MPLS network We have assigned the following attributes to the nodes collected so far. Connect the core element through DS3 and side elements through ATM OC3 Apply MPLS signaling protocol Select application and profile and services we are using Select some statistics we want to analyze
Step 4
Page 70
Then we simulate the scenario and viewed the result i.e. graphs
6.2 Comparing Graphs and result 6.2.1 VOICE APPLICATION Jitter: Voice packet delay variation: End to end delay for a voice:
6.2.1.1 This is the voice application table after simulation of simple UMTS and applied UMTS Network
Table 6.7 Global Statistic of IP in UMTS
Table 6.8 Node Statistic of IP in UMTS
Page 71
Table 6.9 Global Statistic of MPLS in UMTS
Table 6.10 Node Statistic of MPLS in UMTS
6.2.1.2 Graphs: Comparing through graphs
Page 72
The graph shows the voice jitter in UMTS scenario The voice jitter in simple UMTS Network is greater than in MPLS based UMTS scenario The max value of jitter in simple UMTS Network is, 400ms The max value of jitter in MPLS based UMTS is, 52.5ms
Graph 6.10 Voice Jitter in UMTS
The graph shows the voice packet delay variation in simple UMTS and MPLS based UMTS Network As it is clear from the graph that the packet delay variation is greater in simple UMTS than MPLS based UMTS Network The max value of packet delay variation in simple UMTS Network is, 225ms The max value of packet delay variation in MPLS based Network is, 17s
Graph 6.11 Voice Packet Delay Variation in UMTS
Page 73
The graph shows the voice packet end to end delay for simple UMTS and MPLS based UMTS Network It is clear that the end to end delay for Simple UMTS network is greater than MPLS based UMTS Network. This is due to the encoding delay, processing delay and Network delay etc. The max value of end to end delay for simple UMTS network is, 20s The max value of end to end delay for MPLS based network is, 3s
Graph 6.12 Packet End to End Delay in UMTS
6.2.2 6.2.2.1
FTP application FTP scenario
Figure6.33 FTP scenario
Page 74
This is the FTP application table after the simulation of FTP scenario
Table 6.11 IP FTP Global Statistic in UMTS
Table 6.11 MPLS FTP Global Statistic in UMTS
6.2.2.2 Comparing through graphs
Page 75
The graph shows the FTP download response for simple and MPLS based UMTS Network. As it is clear from the graph that the download response for MPLS based UMTS is greater than for simple UMTS network The max download response for simple UMTS network is, 45s The max download response for MPLS UMTS network is, 64s
Graph 6.12 FTP Download Response in UMTS
The graph shows the FTP traffic received in terms of bytes per second in simple and MPLS based Network It is clear from the graph that greater amount of traffic received in MPLS based network than in simple UMTS network The max value of traffic received for simple UMTS network is, 3000 bytes The max value of traffic received for MPLS based UMTS network is, 3400 bytes Graph 6.13 FTP Traffic Received in UMTS
Page 76
The graph shows that traffic received in terms of packet per second The max value for simple UMTS network is, 125packet/ms The max value for MPLS based UMTS network is, 140 packet/ms
Table 6.15 Traffic Received packets/second in UMTS
The graph shows the FTP traffic send in terms of bytes per second in simple and MPLS based Network It is clear from the graph that greater amount of traffic send in MPLS based network than in simple UMTS network The max value of traffic send for simple UMTS network is, 3400/s bytes The max value of traffic send for MPLS based UMTS network is, 4000 bytes/s
Table 6.16 Traffic Received bytes/second in UMTS
Page 77
The graph shows that traffic send in terms of packet per second The max value for simple UMTS network is, 275/ms The max value for MPLS based UMTS network is, 500 packet/ms
Table 6.17 Traffic Send packets/second in UMTS
.3 conclusions
We observed from above graph that by applying MPLS to the core of 3G Networks, the delay factor is reduced. And this way, they provide fast communication and QoS.
Page 78
Chapter #7
Conclusion and Future Work Our project is based on providing QoS by reducing the delay factor
7.1 Conclusion Thus it is concluded, that to provide QoS to customers and clients. The MPLS approach is best suitable in IP core of conventional Network. It is clear from the above graphs, that they provide high performance by reducing jitter variation, packet delay variation and packet end to end delay. This all because, that MPLS works on a short fixed label of 20 bits, while that of IP address is 32 bits which is greater value than MPLS header or frame. Due to this MPLS overhead is less as compared to IP address used by router for routing the data across packet data network. The same approach when we applied to UMTS core network. As the cores is running on IP, so to apply MPLS to the core of UMTS Network gives us better result and reduce jitter variation, packet delay variation and packet end to end delay and increase the performance of traffic send and received. The main reasons here, as already told that there is less overhead produced in MPLS and forwarding occur in MPLS domain at faster speed.
7.2 Future work 7.2.1 Convergence in NGN In the future, IP/MPLS will provide convergence between different types of networks. MPLS technology as innovative foundation to NGN Technology is evolving to facilitate convergence and service creation Page 79
Figure 7.34 NGN Architecture
Figure 7.35 convergence of different world Network
Figure 7.36 view of different service with the core
Page 80
7.2.2 GMPLS (Generalized Multi Protocol Label Switching) This is arising due to the application of MPLS to the Optical Network, converge different network and provide different type of services with low cost and fast forwarding.
Figure 7.37 Future GMPLS
Page 81
References:
[1] http://www.webopedia.com/TERM/M/MPLS.html [2] http://searchtelecom.techtarget.com/definition/3G [3] http://www.networkperformancedaily.com/2006/11/routers_hold_the_key_to_mpls_n_1.html [4] Y. Rekhter et al., Tag switching architecture overview, Proc. IEEE 82 (December, 1997), 19731983. V. Sharma; F. Hellstrand (February 2003), RFC 3469: Framework for Multi-Protocol Label Switching (MPLS)-based Recovery, IETF [5] B. Thomas; E. Gray (January 2001), RFC 3037: LDP Applicability, IETF, http://www.ietf.org/rfc/rfc3037.txt E. Rosen; Y. Rekhter (February 2006), RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), IETF [6] E. Rosen; Y. Rekhter (February 2006), RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs), IETF, http://tools.ietf.org/html/rfc4364 L. Andersson; I. Minei; B. Thomas (October 2007), RFC 5036: LDP Specification, IETF, http://tools.ietf.org/html/rfc5036 D. Awduche; L. Berger; D. Gan; T. Li; V. Srinivasan; G. Swallow (December 2001), RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels, IETF, http://tools.ietf.org/html/rfc3209 Y. Rekhter; E. Rosen (May 2001), RFC 3107: Carrying Label Information in BGP-4, IETF, http://tools.ietf.org/html/rfc3107 Y. Rekhter; R. Aggarwal (January 2007), RFC 4781: Graceful Restart Mechanism for BGP with MPLS, IETF [7] S. Bryant; P. Pate (March 2005), RFC 3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture, IETF Aslam et al. (2005-02-02), NPP: A Facility Based Computation Framework for Restoration Routing Using Aggregate Link Usage Information, QoS-IP 2005 : quality of service in multiservice IP network, http://cat.inist.fr/?aModele=afficheN&cpsidt=16546516, retrieved 200610-27. Raza et al., Online routing of bandwidth guaranteed paths with local restoration using optimized aggregate usage information, IEEE-ICC 2005, http://ieeexplore.ieee.org/iel5/9996/32109/01494347.pdf, retrieved 2006-10-27. Li Li et al., Routing bandwidth guaranteed paths with local restoration in label switched networks, IEEE Journal on Selected Areas in Communications, http://ieeexplore.ieee.org/iel5/49/30289/01391048.pdf?tp=&arnumber=1391048&isnumber=30289 , retrieved 2006-10-27. Kodialam et al., Dynamic Routing of Locally Restorable Bandwidth Guaranteed Tunnels using Aggregated Link Usage Information, IEEE Infocom. pp. 376385. 2001, http://ieeexplore.ieee.org/iel5/7321/19793/00916720.pdf, retrieved 2006-10-27. [8] http://www.protocols.com/pbook/mpls.htm [9] R. Aggarwal; D. Papadimitriou; S. Yasukawa (May 2007), RFC 4875: Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), IETF [10] "AT&T Frame Relay and IP-Enabled Frame Relay Service (Product Advisor)", Research and Markets, June 2007. Performance Analysis of MPLS in UMTS Page 82
[11] [12] [13]
blinky-lights.org/networking/mpls.pdf From thesis of Performance analysis of IPv4 and IPv6 From thesis of Performance analysis of UMTS Handover using OPNET
[Related reference links below] en.wikipedia.org/wiki/Multiprotocol_Label_Switching bnrg.eecs.berkeley.edu/~randy/Courses/CS294.S02/MPLS.ppt en.wikipedia.org/wiki/Multiprotocol_Label_Switching www.seeren.org/.../AdoptingAnEvolutionApproach-Mark%20Vanderhaege... www.slideshare.net/Sarah17/ngn-and-mpls - United States https://learningnetwork.cisco.com/.../cdccont_0900aecd80419... - United States www.mpls.jp/2005/presentations/051122_01.pdf www.ciscopress.com ... Network Technology General Networking blinky-lights.org/networking/mpls.pdf http://www.cisco.com/en/US/products/ps6557/prod_presentation_list.html http://docs.google.com/viewer?a=v&q=cache:0SBN47yhoAgJ:wallu.pagespersoorange.fr/MPLSoverview.pdf+MPLS+.PDF&hl=en&gl=pk&pid=bl&srcid=ADGEEShSs5Oz3cGmAiGYy rMDju4isw4l9n6xQNrmBeu_nWYnQWNRsi8VfCNBu9TBdElytNfMBhK7FaJEqMPGkE 41wkyRSZUaGNWCi57eu9F73FRAm1Rd2YGAY6DZcYJbv7hPjMZTUllG&sig=AHIEt bQhhhBn6xhsRP8DiWd0L0vor8xGpQ en.wikipedia.org/.../Universal_Mobile_Telecommunications_System www.comp.brad.ac.uk/het-net/HET-NETs04/CameraPapers/P38.pdf http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1285947 www.alcatel-lucent.com/.../DocumentStreamerServlet?...MPLS... www.telecomlab.oulu.fi/kurssit/521365A...ja.../Opnet_esittely_07.pdf opnetsimulation.com/wp-content/uploads/2011/.../OPNET-simulation-01.p... www.cs.ucy.ac.cy/.../An%20all-... http://www.protocols.com/pbook/mpls.htm http://www.umtsworld.com/technology/overview.htm
Page 83
Page 84

FYP Thesis

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FYP Thesis

Uploaded by

Copyright:

Available Formats

University of Engineering & Technology Peshawar (Mardan Campus)

B.Sc Final Year Project REPORT

Performance Analysis of MPLS in UMTS

Department of Telecommunication Engineering Session 2007 - 2011

Performance Analysis of MPLS in UMTS

IN THE NAME OF ALLAH, THE MOST BENEFICIENT, THE MOST MERCIFUL

Performance Analysis of MPLS in UMTS

Final Year Project Coordinator

Performance Analysis of MPLS in UMTS

Naeem Ullah Muhammad Tayyab Syed Imran Hussain Shah

Signature: .. Signature: .. Signature: ..

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Dedicated to Our parents and our family

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

RAN RT SGSN TDD TE UE UMTS USIM VOIP WCDMA WLAN WWW

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Chapter # 2 Multi Protocol Label Switching

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Figure 2.3 MPLS Architecture Performance Analysis of MPLS in UMTS Page 22

Figure 2.4 MPLS table

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Figure 2.5 MPLS LSP 2.5 Comparison of MPLS and IP

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

OPNET Modeler 14.0

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Figure 3.7 MODELS

Performance Analysis of MPLS in UMTS

Figure 3.8 Editor

Figure 3.9 Network Layer

Performance Analysis of MPLS in UMTS

Figure 3.10 Node Layer

Performance Analysis of MPLS in UMTS

Figure 3.11 Process Layer

create filters and parameters.

Performance Analysis of MPLS in UMTS

Figure 3.13 Node Editor Performance Analysis of MPLS in UMTS Page 40

Figure 3.15 link Model Editor

Performance Analysis of MPLS in UMTS

Performance Analysis of MPLS in UMTS

Figure 3.19 simulation sequence Editor

Performance Analysis of MPLS in UMTS

Figure 3.21 Project Editor Work space

Figure 3.23 Buttons Performance Analysis of MPLS in UMTS Page 45

Performance Analysis of MPLS in UMTS

FTP application Voice application

Performance Analysis of MPLS in UMTS

Figure 4.24 OPNET

Figure 4.25 New Project Step 2

Figure 4.26 Object Palette Performance Analysis of MPLS in UMTS Page 48

Figure 4.27 IP architecture