(((QNRF Interim Report)))

Project No.: NPRP 4 – 347 – 2 – 127

Project title: “A Context Aware Framework for Optimized Resource Management in

Fourth Generation Wireless Systems”

Report title: OPNET Modeler Introductory Report + LTE Simulations

1. Introduction:

Network simulation is an important methodology in network research field and OPNET Modeler
is a very useful tool for network modeling and simulation. OPNET Modeler is generally used by
researchers, protocol designers, university teachers and students in the field of electronic
engineering, computer science, management information systems, and related disciplines. The
friendly design of its graphical user interface (GUI) makes it nice and easy to start with.
However, the complexity of OPNET Modeler and lack of useful support material make it
difficult for many users to fully make use of its benefits. The Modeler’s library offers more than
400 out-of-the-box protocols and vendor device models including IPv6, TCP/UDP, UMTS,
VoIP/Video/FTP/HTTP/Email, WiMAX, LTE, WLAN (a/b/g/n) and so on, to support accurate
event-driven simulation scenarios.

2. Wireless Design in OPNET

OPNET Modeler presents its capabilities in the form of distinct environments called editors.
Each editor allows users to set of related functions within a window that is contained in the
overall graphical environment. The main editors in OPNET are the following:
 The project editor, which reflects the network domain, constitutes network topology and
configures nodes and links. The results of interest are chosen in the project domain and
can be viewed after running the simulation.
 The node editor generates models of nodes by identifying internal structures and
capabilities of specific device of architecture.
 The process editor develops models of decision-making processes representing
protocols, algorithms, resource managers, operating systems, and so on.
The above-mentioned three editors are the main components of the OPNET Modeler. Figure 1
shows the interaction between the three editors' domains. There are other editors like link editor,
path editor and other more shipped with a software package. Besides the three main editors,
simulation sequence editor is used to design and run sequences of simulations, each potentially
configured with different inputs and/or outputs. Also, demand editor is used to create and edit
traffic demand objects which represent IP layer traffic.

Figure 1: OPNET modeler components

Adopted from: http://www.riverbed.com/products-solutions/products/network-performance-

management/network-planning-simulation/Network-Simulation.html
 3. OPNET Essential Skills – Quick Start

As a Guidance from OPNET modeler documentation and based on our experience with the
software, we provide this section as a quick start for new users. When creating a new network
model, a new project and scenario must be created first. A project is a group of related scenarios
that each explores different aspects of the network design. Projects can contain multiple
scenarios. Once project is created, the Startup Wizard is seen to set up a new scenario.

3.1 Creating a Project

From the File menu, choose New.
Select Project and click OK.
Name the project <Project_Name> scenario <Scenario_Name>.
Click OK.
Click Next in the Startup Wizard.
3.2 Creating Scenario
In the scenario Wizard dialog, the following can be identified:
Initial Topology
Network Scale
Specify Size
Model Family
Review Check
3.3 Creating Network Topologies
There are three ways to create network topologies as follow:
Importing the topology.
Placing each individual node from the object palette into the workspace.
Creating a new network topology is by using the Rapid Configuration feature.
3.4 Creating Network Topologies Rapid Configuration Feature
Rapid Configuration allows selecting a network topology, the types of nodes within the network,
and the links connecting the nodes. To create the first floor network using Rapid Configuration:
From the Topology menu, choose the Rapid Configuration menu item.
Select Star from the list of available configurations, and then click OK.
3.5 Adding Components
Assuming that the general network topology has been constructed, it might be needed to add a a
new components, say a server. The second method of creating network objects can be used
which is dragging them from the object palette into the workspace.
If it is not already open, open the object palette by clicking on the Object Palette
action button.
Find the object in the palette and drag it into the workspace.
If additional copies of this model is needed, right-click to turn off node creation.
To link components, a link is drawn, connecting the two objects, then Right-click to
turn off link creation.
3.6 Editing Attributes
The properties of objects can be changed such as hubs, switches, work station,
eNodes, UEs, etc. by editing the attributes.
Right click on the object is desired to be edited.
Choose Edit attributes.
3.7 Statistics
There are two types of statistics:
Statistics that are collected from individual nodes in a network (object statistics).
Statistics that are collected for the entire network as a whole (global statistics).
Global statistics are used to gather information about the network as a whole. They
are averaged values of the object statistics. For example, the delay for the entire
network can be found by collecting the global Delay statistic.
User has to specify the statistics to be collected before simulation from DES Menu.
3.8 Run the Simulation
After you have specified the network, traffic, statistics to be collected and saved the project, you
are ready to run your simulation.
To run a simulation:
For first time, you need to configure the simulation, duration, random seed and so on.
From the DES Menu, choose Configure\run Discreet Event Simulation.
Instead, you can press “Ctrl+R” in the Keyboard
Type can specify the duration of simulation in the “Duration” box.
Type can specify the random seed in the “Seed” box.
 Type can specify the Values per statistic (e.t., the resolution of the simulations, how often
it is collected) in the “Values per statistic” box.
Once the simulation is configured, you want to run with the current configurations,
choose “Run Discreet Event Simulation” from DES Menu.
Instead, you can press “shift+ Ctrl+R” in the keyboard.
While the simulation is running, a window appears showing the simulation’s progress
(progress bar).
Warning: do not try to interact with the simulator while simulation is running, it might
halt the simulation and cause loss of data since you have only one license.
Only one simulation can run at the time per license.
3.9 View Results
The results can be viewed after the simulation is finished
To view existing results, go to DES Menu> Result> View Results
Statistics (results) can be exported to spreadsheet files (excel files) and be organized
further for better presentation (MATLAB can be used) since OPNET modeler does
not offer a very flexible presentations of the results.
3.10 Debugging
A good debugging tool is the Simulation Log. You can check for warnings and errors.
Click on DES Menu> Result> Open Simulation Log.
Live Debagging can be made for advanced user using the OPNET Simulation
Debugger (ODB) and should be set before running the simulation by checking the
box in the simulation configuration screen.

4. LTE model in OPNET

The current version of OPNET Modeler (17.5) supports Rel. 8 of the 3GPP standard. Radio,
transport and end-to-end protocols of the LTE have been designed and implemented according to
the 3GPP Rel. 8 specification. OPNET Modeler provides an easy, flexible and comprehensive
simulation platform along with many predefined kernel functions and standard node models.
Almost all LTE basic features are available in the LTE model such as EPS Bearer Definitions,
Service Data Flow Classification, MBMS, Packet Data Convergence Protocol (PDCP), Radio
Link Control (RLC), MAC, PHY (Frequency division multiplexing (FDD) v and Time division
multiplexing (TDD) Schemes), HARQ, Channel Quality Indicator (CQI), Link Rate Adaptation,
EPS Session Management (ESM), EPS Mobility Management (EMM), Admission Control,
eNodeB Failure and Recovery Support.

The LTE model in OPNET also adapts the extendable modularized approach providing high
flexibility of supporting different scenarios and system configurations. In addition to that, the
LTE model greatly benefits from the usage of the powerful statistical evaluations tool along with
the GUI provided by the OPNET simulation environment. The basic LTE architecture in OPNET
contains 3 main nodes, namely, UE, eNodeB and Evolve Packet Core (EPC). The data flows
across the eNodeB and LTE core network between the UE and Server. In the downlink direction,
the data is passed from the EPC to eNodeB through backhaul connection or GPRS Tunnelling
Protocol (GTP) tunnels and from the eNodeB to the UE via the radio bearers and, as shown in
Figure 2.

In OPNET Modeler, EPC is represented by a single node performing all the EPC-related
functionalities, therefore, Mobility Management Entity (MME), PDN, and Serving Gateway
(SGW) functionalities are impeded in the EPC node. Three processes (Non-Access Stratum or
NAS, Access Stratum or AS, S1) coordinate the connection and interface management between
the UE and eNodeB and between the eNodeB and EPC as shown in Figure 3.

Figure 2: Data traffic flow in LTE networks.

NAS layer is the highest stratum of the control plane between UE and EPC (MME) at the radio
interface. NAS protocol provides the support of mobility of the UE and session management
procedures. Session management procedures are initiated to establish and maintain IP
connectivity between the UE and PDN Gateway. It performs EPS bearer management,
Authentication, PLMN selection, and security control. The protocol specifications are described
in 3GPP TS 24.301.

Figure 3: LTE process models main tasks

The radio access protocols in the E-UTRAN access stratum comprise of various functionalities:
RRM, traffic management, IP header compression, MME selection, encryption of user data
streams, user plane data routing toward the SGW, location management, handover management,
Radio channel coding, bandwidth status report, CQI measurement and RACH procedures. The
protocol specifications are described in 3GPP TS 23.110. S1 interface, between eNodeB and
EPC, performs the following functions: Interface to the physical medium, frame delineation, line
clock extraction, layer 1 alarms extraction and generation and transmission quality control. The
protocol specifications are described in 3GPP TS 36.411 and 3GPP TS 36.410.

In the OPNET node domain, there are LTE attributes that can be set in each type of nodes.
ENodeB and UE nodes share most of the attributes. However, there are some specific attributes
for each node. For example, modulation and coding index, EPS bearer configuration are
available in the UE node but not in the eNodeB. On the other hand, eNodeB includes some
attributes that are not specified in the UE node such as Channel Bandwidth. Figure 4 offers a
snapshot of the UE node parameters.

Figure 4: LTE parameters in OPNET.

 5. Simulation Scenarios (LTE Performance Analysis)

This Section provides an adequate analysis for LTE throughput and affecting parameters on it.
Effects of duplexing scheme (FDD vs. TDD), Modulation and Coding Scheme (MCS), Channel
Bandwidth, behavior of the different Bearer's type (Guarantee Bit Rate (GBR) or non-GBR) and
the impact of multiple users’ access on the throughput performance are presented One UE is
configured with one type of traffic and in default bearer mode in order to study the upper limit of
the throughout. For another set of the scenarios, one UE is configured with multiple Quality of
Service (QoS) Class Identifier (QCI) and Multiple UEs with multiple QCI to study the effects of
QCI type and number of users on the network performance. The default parameters unless stated
where used otherwise. Figure 5 shows the simulation setup in OPNET. The dashed blue line
represents the traffic flow direction between the server and the UE. The actual traffic flows
through the EPC or the solid lines, which are configured as 1 Gbit/s Ethernet duplex links. Our
study focuses on the radio interface between the eNodeB and the UE.

Figure 5: LTE simulation setup

The following Sections represent study cases and discussion of the different scenarios. Scenarios
in Sections 5.1 to 5.3 are based on single UE and single eNodeB and the Scenario in Sections 5.4
and 5.5 contains many users and one eNodeB. FDD transmission mode is used throughout the
simulation except for one scenario where FDD and TDD are compared. The results obtained are
analyzed and sub-conclusions are attained from each case study.

5.1 Effects of channel bandwidth

Figure 6 show the maximum throughput of the uplink and downlink direction for FDD LTE
using one eNodeB and one UE. The UE is placed at the distance where the best MCS index = 28
can be supported. There is no interference as there is only one base station in this setup. The
maximum number of Resource Blocks (RBs), occupied bandwidth and bandwidth efficiency for
each bandwidth are given in the Table 1.

Table 1: No. of RB and bandwidth efficiency

Bandwidth (MHz) 1.4 3 5 10 15 20

No. of RB 6 15 25 50 75 100
Actual Bandwidth 1.08 2.7 4.5 9 13.5 18
Bandwidth efficiency 77% 90% 90% 90% 90% 90%

The occupied bandwidth refers to the bandwidth that is actually occupied by the RBs. For
instance, for the 1.4 MHz case, there are 6 RBs with 180 KHz each hence, the actual bandwidth
is 6x180 KHz (1.08 MHz). Bandwidth utilization is equal to the ratio between the actual
bandwidth and the allocated bandwidth. From Figure 6, It is observed that the throughput
performance is in proportional with the channel bandwidth except for the 1.4 MHz case. Here,
the downlink direction experiences slightly lower throughput than the uplink. This is largely due
to the synchronization signals and broadcast signals which are sent at the downlink direction.
Hence over the narrow 1.4 MHz bandwidth channel, the relative overhead becomes
comparatively higher. This is due to the difference in the allocation of control signaling resource.
In our simulation Physical Uplink Control Channel (PUCCH) occupies 28 REs (for all channel
bandwidths) while Physical Downlink Control Channel (PDCCH) is set to one symbol (7REs).
This reduces the uplink physical data rate by 10.6% as compared with the downlink physical data
rate. In addition, SRS occupies up to 12 REs while Reference Signal occupies 8 REs of which
two are included in PDCCH. From Figure 6, it can be deduced that the 2x10 MHz FDD licensees
in Malaysia, can only expect up to 43.2 Mbps IP layer throughput at the downlink and 37.7 Mbps
at the uplink using SISO or MISO configuration. The only 2x20 MHz license recipient can enjoy
up to 88.5 Mbps and 79.3 Mbps at the downlink and uplink respectively, which is more than
double of the 2x10 MHz recipients.

90
Uplink
80 Downlink

70
LTE Throughput (Mbps)

60

50

40

30

20

10

1.4MHz 3MHz 5MHz 10MHz 15MHz 20MHz

Bandwidth
Figure 6: Effects of channel bandwidth on throughput (FDD, MCS=28,1UE,1eNodeB)

5.2 Effects of TDD -FDD

LTE supports both paired and unpaired spectrum through TDD-LTE. TDD-LTE is different from
FDD-LTE in terms of frame structure, scheduling, HARQ processes and ACK/NACK procedure.
3GPP has specified a special subframe that allows switching between downlink and uplink
transmission. The special subframe contains Downlink Pilot Time Slot (DwPTS), Guard Period
(GP), and Uplink Pilot Time Slot (UpPTS). GP is required to guarantee that uplink and downlink
transmissions do not collide, but larger GP means lesser capacity. For long distances, larger GP
is necessary to accommodate larger propagation times. Figure 7 shows a comparison between 10
MHz FDD-LTE and 20 MHz TDD-LTE and between 5 MHz FDD-LTE and 10 MHz TDD-LTE.
The simulation results show that TDD has lower throughput compared to FDD due to the
difference in frame structure especially the subframe.
 50
TDD
FDD

LTE Throughput (Mbps)

40

30

20

10

10 TDD 5 FDD 20 TDD 10 FDD

Bandwidth (MHz)
Figure 7: Effects of FDD and TDD on throughput

5.3 Effects of MCS index

LTE eNodeB supports 29 different MCSs with index ranging from 0 to 28. Each MCS is mapped
to what is known as transport block size index ITBS ranging from 0 to 26 (3GPP, 2012). ITBS
and RBs determine the transport block size, in bits, that can be transmitted within on TTI hence;
the data rate and throughput can be calculated. In the downlink direction, MCS with the index 0 -
9 are modulated using QPSK, index 10 - 16 are 16QAM and the rest are 64QAM. The difference
between each MCS of the same modulation type is the coding rates which are presented in Table
2 as follows:

Table 2: MCS indexes and coding rates

MCS Coding MCS Coding MCS Coding MCS Coding
Index Rate Index Rate Index Rate Index Rate
0 0.16667 8 0.6 16 0.63333 24 0.75556
1 0.2 9 0.66667 17 0.42222 25 0.8
2 0.23333 10 0.33333 18 0.48889 26 0.84444
3 0.26667 11 0.35 19 0.5 27 0.88889
4 0.33333 12 0.41667 20 0.55556 28 1
5 0.4 13 0.48333 21 0.6
6 0.4667 14 0.51667 22 0.64444
7 0.53333 15 0.58333 23 0.71111
Each of the LTE scalable supported bandwidth can support number of transport block up to a
certain number (the maximum) as shown in Table 1. In our simulation, the maximum number of
block size (100 RBs) was used with 20 MHz bandwidth.

In this scenario, investigation on the maximum data rate that each MCS index can support using
20 MHz channel and error free channel is carried out. As shown in Figure 8, the performance is
quite linear for the different MCSs except for MCS 28 which has a relatively higher data rate due
to the use of uncoded transmission (coding rate is of 1). MCS 9 and 10, which are modulated
QPSK and 16QAM respectively have the same throughput as they are mapped to the same TBS
(ITBS =9). The same goes with MCS 16 and 17.

90

80

70
LTE Throughput (Mbps)

60

50

40

30

20

10

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
LTE MCS index

Figure 8: Effects of MCS index on throughput (20 MHz, FDD)

5.4 GBR and non-GBR Bearers.

LTE scheduler follows certain rules when scheduling the traffics of different bearers. Generally
signalling bearers have higher priority over data bearers. GBR bearers have priority over non-
GBR bearers. One exception is that non-GBR bearers with a QCI of "5" have higher priority
over GBR bearers. In order to demonstrate the effects without having to populate the model with
too many UEs, we use 3 MHz channel bandwidth instead of the 10 or 20 MHz which provide
maximum throughput of 6.5 Mbps. In our scenario, there are three types of bearers carrying IP
traffic flows of 5 Mbps between the server and the UE in the downlink direction as shown in
Figure 5. Here, the GBR traffic is using QCI=1 while QCI=5 is assigned for the signalling of
non-GBR bearer. The default bearer, which is non-GBR, is using QCI=9.

Figure 9 shows that the UE started to receive traffic via the non-GBR default bearer at 5 Mbps.
At 150 seconds, the Server starts transmitting via GBR bearer (QCI=1) at 5 Mbps. The resources
are first allocated to the GBR bearer, and the remaining is allocated to non-GBR bearer. The UE
receives ~5 Mbps via the GBR bearer and 1.5 Mbps via default bearer. At 180 seconds, the
Server starts transmitting 5 Mbps traffic via non-GBR Bearer with QCI=5, which is normally
used to carry signalling traffic. It can be observed that the resources are reserved for the bearer of
QCI 5 first, and the rest is used to serve the GBR and the non-GBR. Since the resources are not
enough to serve both bearers, the GBR hence carries ~ 1.7 Mbps and the non-GBR carries no
traffic.

bits/sec

time

Figure 9: GBR and non-GBR bearers (One UE)

Next, a similar scenario is studied but this time the traffics flow between the Server and three
UEs. It can be observed that Figure 9 and Figure 10 produce almost same results. The results
show that bearers remain the means for providing traffic QoS differentiation regardless of
whether there is only one UE or multiple UEs. Through these mechanisms, future LTE operators
can provide differentiated services to their subscribers.

bits/sec

time

Figure 10: GBR and non-GBR bearers (Multiple UEs)

5.5 Effects of multiple users

In this scenario, the number of users was varied with the same QoS, all users are using the
default bearer and hence, scheduling overhead is minimal. Since the bearers are all non-GBR and
have the same QCI, they are serviced using a fair scheduling scheme; where the resources are
shared equally among UEs. It is important to note that without a scheduling mechanism in place,
each user has the capability to saturate the capacity of the LTE cell.

In this scenario, we pumped gradually increasing traffic between the Server and the UEs to find
the maximum cell throughput and for each number of UEs configurations. From Figure Error!
No text of specified style in document.11 it can be observed that when varying the number of UEs
between one and five, the maximum LTE system throughput decreases from 9.28 Mbps to 8.89
Mbps. However, subsequent increment in terms of the number of users (up to 100 UEs) does not
degrade the maximum system throughput much further. The throughput decreases from 8.89
Mbps, in the case of having 10 UEs, to 8.72 Mbps, in the case of having 100 UEs. Depending on
the target number of subscribers load per cell, the future LTE operators therefore need to take
into consideration that the maximum system throughput will need to be discounted by around 6%
in actual deployment due to the need to support multiple users.

9.6
Efficiency Throughput
100%
9.4
LTE Cell Throughput (Mbps)

95%

Multiple Users Efficiency

9.2
90%

9.0
85%

8.8
80%

8.6 75%

8.4 70%
1 2 3 4 5 10 25 50 70 100
Number of Users
Figure Error! No text of specified style in document.11: Effects of multiple Users

6. Conclusion

This report represents an overview of the capabilities of the OPNET Modeler focusing on the
LTE simulation design. Section 3 provides a quick start for new users; creating a new project,
creating scenario, running simulation, viewing results and so on.

In the report, simulation of LTE technology was performed in order to verify the simulator and
to provide good insights of the LTE performances. Section 5 is considered a good study of the
LTE technology; even it was not very detailed. The throughput was used as the performance
metric in our analysis. We tested the different parameters affecting it such as effects of duplexing
scheme (FDD vs. TDD), MCS, Channel Bandwidth, behavior of the different Bearer's type
(GBR or non-GBR) and the impact of multiple users’ access.