qualnet 4.5 cellular model library - ucsbebelding/courses/284/qualnet/...2 qualnet 4.5 cellular...

QualNet 4.5Cellular Model Library

February 2008

Scalable Network Technologies, Inc.6701 Center Drive West, Suite 520

Los Angeles, CA 90045

Phone: 310-338-3318 Fax: 310-338-7213

http://www.scalable-networks.com http://www.qualnet.com

Copyright Information

© 2008 Scalable Network Technologies, Inc. All rights reserved.

QualNet is a registered trademark of Scalable Network Technologies, Inc.

All other trademarks and trade names used are property of their respective companies.

Scalable Network Technologies, Inc.6701 Center Drive West, Suite 520Los Angeles, CA 90045Phone: 310-338-3318Fax: 310-338-7213http://www.scalable-networks.comhttp://www.qualnet.com

ii QualNet 4.5 Cellular Model Library

Table of Contents

Abstract Cellular ......................................................................................................... 1Global System for Mobile Communications (GSM) Model ....................................... 22User Behavior Model ................................................................................................ 31

QualNet 4.5 Cellular Model Library iii

iv QualNet 4.5 Cellular Model Library

Abstract Cellular

Abstract CellularIn the Abstract Cellular Model, a single base station serves a circular service area that is divided into multiple sectors, each of which is allocated with a certain amount of bandwidth. For each base station, several control channels are defined, as well. A large number of base stations cover the simulated area and they are connected to a hub, the switch center, with wired links. The hub routes the control and data messages to/from the base stations. An aggregated node emulates the services originated or destined to nodes outside the simulated area. A gateway connects to all the BSs and the aggregated node. With help from HLR, the gateway routes the information flows between MSs or between MS and the aggregated node. See Figure 1

FIGURE 1. Abstract Cellular Architecture

A mobile station, supporting various types of services, selects and associates the optimal base station and updates its location to the VLR at the hub to facilitate the call setup process. At a user’s request, a mobile station sends channel requests to the associated base station with other necessary information. The base station(s) and the switch center build up the connection with the called party either in or outside the simulation area by allocating channel resources to both communication parties, if needed. The resources are released when communication is over. A mobile station also initiates handover when signal strength from the associated base station diminishes. Communication between mobile stations and base stations is over the air via radio transmission. Base stations can carry out call admission control, and congestion control by monitoring the run-time resource usage and accepting or rejecting the call.

5

6

4 Mobile station

Base station

Hub/switch center

Aggregated node

Simulation area

VLR

2

1

3

7

8

9

10

11

Gateway

HLR

QualNet 4.5 Cellular Model Library 1

Command Line ConfigurationTo simulate an abstract cellular system in QualNet, users must plan the network layout, including deciding on the following:

• Number of Base Stations• Number of channels available to each BS (at least one channel pair for the control channels needs to

be allotted per BS)• Location of BS’s to provide coverage in the intended area.

In addition, you must configure the cellular nodes to make the simulation work. Using the configuration file, supply the simulator with the basic information on the cellular nodes, including their node IDs, addresses, node types, location, mobility patterns, and other simulation related parameters, (for example, simulation time and random generation seed). In addition, you must configure the specific properties of each type of cellular node. Note that, to enable the abstract cellular model, you specify the protocols employed at the network layer, the MAC layer, and the physical layer to be cellular-related protocols.

A cellular system will include mobile stations (MS), base stations (BS), switch centers (SC), gateway nodes (G), and an aggregated node (AN). Be sure to have at least one LS, one SC and one Gateway. Table 1 shows the basic cellular node parameters:

If you choose Mobile Station, there will be no further configuration parameters.

TABLE 1. Basic Cellular Node Parameters

Parameter Description[NodeId]CELLUALR-NODE-TYPE CELLULAR-XXXX Specifies the cellular node type. The possible node

types are:

Mobile Station (MS)

Base Station (BS)

Switch Center (SC)

Gateway

Aggregated Node

#XXXX could be MS, BS, SC, GATEWAY, AGGREGATED-NODE

The default value is CELLULAR-MS.

CELLULAR-ABSTRACT-OPTIMIZATION-LEVEL <MEDIUM/LOW>

Specifies the Optimization Level of the Model. The default value is LOW.

[NodeId] CELLULAR-ABSTRACT-MOVEMENT-THRESHOLD <distance>

Specifies the Signal Measurement Update Threshold in Optimization Mode 'Medium'. Its value is 0 for nodes that are not MS.

CELLULAR-STATISTICS YES|NO Enables the abstract cellular statistics.

2 QualNet 4.5 Cellular Model Library

Abstract Cellular

If you choose Base Station, the list of parameters shown in Table 2 is displayed.

TABLE 2. Base Station Parameters

Parameter Description[NodeId] CELLULAR-BS-CELL-ID <CellId> Specifies the cell identity. Cell Id is the identifier for each

cell cover by a BS and it is unique in each location area. The default value is Node Id.

[NodeId] CELLULAR-BS-LAC <LocationAreaCode> Specifies the location area code. Each location area in a cellular system has its unique location area code. An MS could be covered by multiple BSs (may belong to different location area) at the same time. Such information (LAC, Cell-Id) can be used to determine the right MSC and right BS. The default value is Node Id.

[BSNodeId] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-UPLINK {CHANNEL ID}

Specifies the uplink control channel. The channel index of the channel needs to be specified here. The default value is 0.

[BSNodeId] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-DOWNLINK {CHANNEL ID}

Specifies the downlink control channel. The channel index of the channel needs to be specified here. The default value is 1.

[NodeId] CELLULAR-ABSTRACT-BS-NUMBER-SECTOR <Number>

Specifies the number of sectors per Cell. The value should be more than 0. The default value is 6.

[NodeId] ABSTRACT-CELLULAR-BS-SECTOR-BANDWIDTH [SectorId]<bandwidth allocated>

Specifies the bandwidth allocation in each BS sector in Kbps. This parameter appears multiple times (once for each sector). The default value is 2048 Kbps.

[NodeId] CELLULAR-ABSTRACT-BS-SERVICE {XXXX}

Specifies the available services at BS. Possible values are VOICE and/or DATA. The default value is VOICE.

[NodeId] CELLULAR-ABSTRACT-BS-ADMISSION-CONTROL-POLICY [POLICY]

Specifies the call admission control policy. It could be either NONE or THRESHOLD-BASED.

NONE: No CAC is employed.

THRESHOLD-BASED: M out of N resource requests will be rejected.

The default value is NONE.

[NodeId]CELLULAR-ABSTRACT-BS-CONGESTION-CONTROL-POLICY [POLICY]

Specifies the congestion control policy. Possible options are NONE and ROUND-ROBIN. The default value is NONE.

[BSNodeId] CELLULAR-ABSTRACT-BS-CONTROL-INFORMATION-INTERVAL <Interval>

Specifies the control information broadcast interval. The control channel periodically broadcasts the location and other system information of the BS (UNIT MS). The default value is 20 MS.

[BSNodeId] CELLULAR-BS-ASSOCIATE-SC [SCNodeId]

Specifies the node Id of the associated Switch Center. This is a mandatory parameter. The default value is 1.


If you choose Threshold-based call admission control, the parameters shown in Table 3 are displayed.

If you choose Round Robin congestion control, the parameters shown in Table 4 are displayed.

If you choose Switch Center, the parameters shown in Table 5 are displayed.

Note: All these parameters are mandatory

TABLE 3. Threshold-based Parameters

Parameter DescriptionTHRESHOLD-BASED-CAC-PARAM-N <Integer> Specifies the threshold-based CAC parameter N

M out of N resource requests will be rejected. N - M (threshold), N (Maximum), N > M. The default value is 4.

THRESHOLD-BASED-CAC-PARAM-M <Integer> Specifies the threshold-based CAC parameter M.

M out of N resource requests will be rejected. N - M (threshold), N (Maximum), N > M. The default value is 1.

TABLE 4. Round Robin Congestion Control Parameters

Parameter DescriptionROUND-ROBIN-CONGESTION-CONTROL-DURATION <Time>

Specifies the length of the each control epoch. The default value is 200 MS

ROUND-ROBIN-CONGESTION-CONTROL-ACCESS-CLASS <Integer>

Specifies the number of access classes. The default value is 10.

ROUND-ROBIN-CONGESTION-CONTROL-REFRAIN-PROBABILITY <Probability>

Specifies the probability of request refrained from transmission. The value of <Probability> should be one of 0.25, 0.5, or 0.75. The default value is 0.25.

TABLE 5. Switch Center Parameters

Parameter Description[SC NodeId] CELLULAR-SC-LAC-LIST {lac list} The LAC list helps gateway and HLR to route call. An

SC can contain multiple LAC and in one LAC there could be multiple BSs. But only one LAC can present in one SC.

[SC NodeId] CELLULAR-SC-CONTROL-BS {BSIds} Specifies the base stations controlled by the SC. A comma-separated list of BS node Ids is provided.

[SC NodeId] CELLULAR-SC-CONNECT-GATEWAY <gateway id>

Specifies the SC-Gateway relationship.


Abstract Cellular

If you choose Gateway Node, the parameters shown in Table 6 are displayed.

If you choose Aggregated Node type, the parameter shown in Table 7 is displayed.

Configuring Network LayerNETWORK-PROTOCOL CELLULAR-LAYER3CELLULAR-LAYER3-PROTOCOL ABSTRACT-LAYER3

Configuring MAC LayerMAC-PROTOCOL CELLULAR-MACCELLULAR-MAC-PROTOCOL ABSTRACT-MAC

Enabling StatisticsCELLULAR-STATISTICS <YES/NO>

Configuring ApplicationsAbstract cellular applications are defined in the application file. A valid abstract cellular application consists of the applications:

• Source and destination• Service type (for example, VOICE, VIDEO-PHONE, TEXT-MAIL)• Start time and duration• Bandwidth requirement.

An item in the application file follows this syntax with the keyword CELLULAR-ABSTRACT-APP.

TABLE 6. Gateway Parameters

Parameter Description[Gateway NodeId] CELLULAR-GATEWAY-CONNECT-SC {SC id list}

Specifies the switch centers connected to the gateway. Multiple SCs can be connected to one gateway. This is a mandatory parameter.

[Gateway NodeId] CELLULAR-GATEWAY-CONNECT-AGGREGATED-NODE <node id>

Specifies the aggregated node connected to the gateway. This is a mandatory parameter.

TABLE 7. Aggregated Node Parameter

Parameter Description[AN NodeId] CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY <node id>

Specifies the gateway connected to the aggregated node. The node Id of the gateway should be specified. This is a mandatory parameter.


CELLULAR-ABSTRACT-APP <Calling-MS-NodeId> <Called-MS-NodeId> <Call StartTime> <Call Duration> <Service Type> <Bandwidth Requirement in Unit of Kbps>. For example, CELLULAR-ABSTRACT-APP 36 99 390S 196S VOICE 13.000000

Table 8 shows the Cellular Abstract Application parameters.

Sample ScenarioIn the following, a sample scenario (as shown in Figure 2) with 10 MS, 1 BS, 1 SC, 1 Gateway and 1 Aggregated Node deployed in an area of 1500m*1500m, is presented to illustrate these major configuration parameters. Here, only those cellular-related parameters are presented, and for those parameters common to other models, readers are referred to the sample configuration file.

TABLE 8. Cellular Abstract Application Parameters

Parameter DescriptionSource Specifies the node Id of calling MS. This is a mandatory

parameter.

Destination Specifies the node Id of called MS. This is a mandatory parameter.

Call Start Time Specifies the start time of the call. It should be more than 0. This is a mandatory parameter.

Call Duration Specifies the duration of the call. This is a mandatory parameter.

Service Type Specifies the service type. It can be one of: VOICE, VIDEOPHONE, TEXT-MAIL, PICTURE-MAIL, ANIMATION-MAIL, and WEB. This is a mandatory parameter. The default value is VOICE.

Bandwidth Required Specifies the bandwidth required for service in Kbps. This is a mandatory parameter.


Abstract Cellular

FIGURE 2. Sample Simulator Configuration

Network Deployment and OrganizationIn this scenario, 10 MSs communicate with 1 BSs via a radio interface, and BS connects to the SC, the SC connects to the gateway, and the gateway connects to the aggregated node, all via wired links. Thus network organization including the subnet and the links for this scenario would be as follows, in which the subnet consists of all the MSs and BSs to form a wireless subnet, and the wired link connects cellular nodes to form a wired backbone for the cellular system. Please refer to the QualNet 4.5 User’s Guide for more detailed information about the definitions of SUBNET and LINK.

While there is no specification of the deployment of MSs, the deployment of BSs, and the SC and the gateway (especially the BSs), should be carefully designed to fully cover the area. Here, we assume BSs are regularly deployed in the field and the node position information is stored in a .nodes file. In this example, the node position information is included in the configuration as follows, in which MSs are randomly deployed in the field while the rest of the cellular nodes are deployed to the position as specified in the default nodes file. Please refer to the QualNet 4.5 User’s Guide for more detailed information on node placement.

Command Line ConfigurationThe network deployment or planning also includes the allocation of physical radio channels. Here we assume each BS needs a pair radio channels with different frequency to function as downlink and uplink control channel, respectively. Thus, 2 radio channels need to be defined as follows.


# Channel properties

#SYNTAX:# PROPAGATION-CHANNEL-FREQUENCY[channel index] <frequency> #USAGE PROPAGATION-CHANNEL-FREQUENCY[0] 890.0e6PROPAGATION-CHANNEL-FREQUENCY[1] 935.0e6

Here, only the channel frequency and the channel index are defined, and other channel-related parameters are omitted. See the QualNet 4.5 User’s Guide to choose the appropriate options for other parameters such propagation limit, propagation loss mode, fading mode, and the correct settings of channel listenable mask and channel listening mask.

Basic Cellular Node Properties • Node Type - The first property of a cellular node is its node type. Currently there are five different node

types defined in this Abstract Cellular Model, including mobile station (MS), base station (BS), switch center (SC), gateway node (GN) and aggregated node. Each node could have only one of these types and it is specified in the following format with the keyword CELLULAR-NODE-TYPE.

#[nodeID] CELLULAR-NODE-TYPE CELLULAR-XXXX# XXXX could be MS, BS, SC, GATEWAY, AGGREGATED-NODE#Usage [1] CELLULAR-NODE-TYPE CELLULAR-MS[2 thru 10] CELLULAR-NODE-TYPE CELLULAR-MS[11] CELLULAR-NODE-TYPE CELLULAR-BS[12] CELLULAR-NODE-TYPE CELLULAR-SC[13] CELLULAR-NODE-TYPE CELLULAR-GATEWAY[14] CELLULAR-NODE-TYPE CELLULAR-AGGREGATED-NODE

• Protocol Type - To enable the abstract cellular model, specify the protocols employed at the network layer, the MAC layer and the PHY layer to be cellular-related protocols.In the network layer, choose CELLULAR-LAYER3 as the network protocol and ABSTRACT-LAYER3 as the underlying cellular layer3 protocol.

NETWORK-PROTOCOL CELLULAR-LAYER3CELLULAR-LAYER3-PROTOCOL ABSTRACT-LAYER3

In the MAC layer, choose CELLULAR-MAC as MAC protocol and ABSTRACT-MAC as the underlying cellular MAC protocol. Though GSM-MAC, UMTS-MAC and other cellular protocols are on their way, currently ABSTRACT-MAC is the only choice in this release. Use this SYNTAX to enable the Abstract Cellular MAC protocol.

#SYNTAX # MAC-PROTOCOL <mac protocol>#Usage MAC-PROTOCOL CELLULAR-MAC

#SYNTAX # CELLULAR-MAC-PROTOCOL <detailed cellular mac protocol>#it is ABSTRACT-MAC, the only choice currently#UsageCELLULAR-MAC-PROTOCOL ABSTRAC-MAC


Abstract Cellular

In the PHY layer, now only PHY-ABSTRACT is supported. Please refer to the QualNet 4.5 User’s Guide for more detail on the usage of PHY-ABSTRACT model.

• Optimization level -Optimization level used in the simulation. When the optimization level is medium, some of the control messages such as system information, are abstracted out. To enable this optimization, configure two more parameters:

#CELLULAR-ABSTRACT-OPTIMIZATION-LEVEL LOWCELLULAR-ABSTRACT-OPTIMIZATION-LEVEL MEDIUM

Only LOW and MEDIUM are supported at this time. The LOW option disables the optimization, while the MEDIUM option enables optimization.

CELLULAR-ABSTRACT-MOVEMENT-THRESHOLD 1.0

These parameters specify how long a distance MS moves to report a signal measurement when optimization is used.

• Statistics - You can specify whether to collect the simulation statistics related to the abstract cellular model. The keyword CELLULAR-STATISTICS is used to turn on/off this option.

#SYNTAX# CELLULAR-STATISTICS <YES/NO>#Usage CELLULAR-STATISTICS YES

Special Node Properties for Base StationAs mentioned earlier, there are quite a few unique properties for a BS, and in the following these properties are presented.

• Cell ID - Each BS has a cell ID, which is unique in a location area. To configure the cell id, users should use the following syntax. The keyword CELLULAR-BS-CELL-ID is used to specify the cell id of each BS.

#SYNTAX#[NodeId] CELLULAR-BS-CELL-ID <cellId> #Usage [11] CELLULAR-BS-CELL-ID 1

• Location Area Code - Each BS belongs to a certain area which is indexed by the location’s area code. In one location area, there may be multiple BSs. The keyword CELLULAR-BS-LAC is used to specify the location area code.

#SYNTAX#[NodeId] CELLULAR-BS-LAC <location area code>#Usage[11] CELLULAR-BS-LAC 1

In this example, only one BS is in each location area.• Control Channels - For each BS at least a pair of channels should be allocated for the control purpose,

one for uplink control channel and one for downlink control channel. Keywords CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-UPLINK and CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-DOWNLINK are used to define these two channels respectively.


#SYNTAX#[NodeId] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-UPLINK {CHANNEL ID}#[NodeId] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-DOWNLINK {CHANNEL ID}#Usage # BS 1 [11] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-UPLINK 0[11] CELLULAR-ABSTRACT-BS-CONTROL-CHANNEL-DOWNLINK 1

Note: These channel indexes match those defined in the Network Deployment and Organization section, earlier in this book.

• Number of Sectors - A BS may be divided into multiple sectors and the number of sectors in this BS is specified by the keyword CELLULAR-ABSTRACT-BS-NUMBER-SECTOR.

# SYNTAX#[NodeId] CELLULAR-ABSTRACT-BS-NUMBER-SECTOR <number>#Usage[11] CELLULAR-ABSTRACT-BS-NUMBER-SECTOR 6

In this example, each BS is divided into 6 sectors.• Bandwidth Allocation in Each BS - A certain amount of bandwidth is allocated to each sector of each

BS, and such allocation is specified by the keyword ABSTRACT-CELLULAR-BS-SECTOR-BANDWIDTH.

#SYNTAX#[NodeId] ABSTRACT-CELLULAR-BS-SECTOR-BANDWIDTH[SectorId]<bandwidth allocated> #Unit: Kbps#Usage

In the above example, each sector of each BS is allocated with 2480 Kbps of bandwidth for use.• Service Supported at each BS - Each BS may support a certain number of service types, and such

services are specified by using keyword CELLULAR-ABSTRACT-BS-SERVICE. Currently, two types of services are defined in this model, which are VOICE and DATA.

#SYNTAX#[NodeId] CELLULAR-ABSTRACT-BS-SERVICE {XXXX }#XXXX could be VOICE and/ or DATA#Usage

• Control Information Broadcast Interval - To keep MS informed of the existence of services provided by BSs, BSs periodically broadcast their system information at certain intervals and this interval is specified by the keyword CELLULAR-ABSTRACT-BS-CONTROL-INFORMATION-INTERVAL.

#SYNTAX#[NodeId] CELLULAR-ABSTRACT-BS-CONTROL-INFORMATION-INTERVAL <interval>#Usage

• BS Control Policy - BS may employ call admission control and congestion control to support QoS, and the policy is specified by the keywords CELLULAR-ABSTRACT-BS-ADMISSON-CONTROL-POLICY and CELLULAR-ABSTRACT-BS-CONGESTION-CONTROL-POLICY, respectively.


Abstract Cellular

#SYNTAX# call admission control policy#[NodeId] CELLULAR-ABSTRACT-BS-ADMISSON-CONTROL-POLICY [POLICY]#Usage[11] CELLULAR-ABSTRACT-BS-ADMISSION-CONTROL-POLICY THRESHOLD-BASED

#congestion control policy#[NodeId] CELLULAR-ABSTRACT-BS-CONGESTION-CONTROL-POLICY [POLICY][11] CELLULAR-ABSTRACT-BS-CONGESTION-CONTROL-POLICY PROBABILISTIC

Currently, only THRESHOLD-BASED call admission control is supported, and no congestion control is included in this release.

Special Node Properties for Switch Center• Location Area Code List - Each SC may control over multiple location area, and this information is kept

in the location area list to help SC route information flow between BSs possibly belonging to different location area. The location area code list is specified by keyword CELLULAR-SC-LAC-LIST.

#SYNTAX#[NodeId] CELLULAR-SC-LAC-LIST {Lac Code}#Usage[512] CELLULAR-SC-LAC-LIST {1}

Interconnection Between Cellular Nodes In the above sections, only properties of each type of cellular node are defined, and users still need to specify the interconnection relationship between these cellular nodes. This information is used to facilitate routing.

• Interconnection between BS and SC - The interconnection between BS and SC is specified by two keywords: CELLULAR-SC-CONTROL-BS and CELLULAR-BS-ASSOCIATE-SC.For a SC, the keyword CELLULAR-SC-CONTROL-BS is used to specify which BSs are connected to this SC:

#Syntax# [NodeId] CELLULAR-SC-CONTROL-BS {BS Ids} #Usage[12] CELLULAR-SC-CONTROL-BS {11}

In this example, all the BSs are connected to this SC. For a BS, the keyword CELLULAR-BS-ASSOCIATE-SC is used to specify which SC this BS has a connection.

#SYNTAX#BS #[NodeId] CELLULAR-BS-ASSOCIATE-SC <SC Id> #Usage[11] CELLULAR-BS-ASSOCIATE-SC 12

This interconnection relationship between BS and SC should be made mutually-consistent.


• Interconnection between SC and Gateway Node - The interconnection between SC and gateway is specified by two keywords: CELLULAR-SC-CONNECT-GATEWAY and CELLULAR-GATEWAY-CONNECT-SC. For a SC, the keyword CELLULAR-GATEWAY-CONNECT-SC is used to specify the gateway it connects to.

#SYNTAX #[NodeId] CELLULAR-SC-CONNECT-GATEWAY <Gateway Id> #Usage[12] CELLULAR-SC-CONNECT-GATEWAY 13

For a gateway, multiple SCs can connect to this gateway, and the keyword CELLULAR-SC-CONNECT-GATEWAY, followed by a list of SC, is used to specify such connection relationship.

#SYNTAX#[NodeId] CELLULAR-GATEWAY-CONNECT-SC {SC Id List}#Usage [13] CELLULAR-GATEWAY-CONNECT-SC {12}

This interconnection relationship between SC and gateway should be made mutually consistent.• Interconnection between Gateway and Aggregated Node - The interconnection between gateway node

and aggregated node is specified by two keywords: CELLULAR-GATEWAY-CONNECT-AGGREGATED-NODE and CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY.For a gateway node, the keyword CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY is used to specify the aggregated node it connects to.

#[NodeId] CELLULAR-GATEWAY-CONNECT-AGGREGATED-NODE <NodeId>#Usage[13] CELLULAR-GATEWAY-CONNECT-AGGREGATED-NODE 14

For an aggregated node, the keyword CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY is used to specify the gateway it connects to.

#SYNTAX#[NodeId] CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY <NodeId>#Usage[14] CELLULAR-AGGREGATED-NODE-CONNECT-GATEWAY 13

This interconnection relationship between the gateway node and aggregated node should be made mutually-consistent.

Configure the Cellular ApplicationsIn QualNet, the application profile is specified by the keyword APP-CONFIG-FILE in the configuration file.

#SYNTAX#APP-CONFIG-FILE <file name>#UsageAPP-CONFIG-FILE ./app1.app

For the cellular model, the abstract cellular applications are defined in the application file. A valid abstract cellular application consists of the application's source and destination, its service type (VOICE, VIDEO-


Abstract Cellular

PHONE, TEXT-MAIL and so on, as defined in the QualNet 4.5 User’s Guide), application start time and its duration, and its bandwidth requirement. An application item in the application file follows this syntax with the keyword CELLULAR-ABSTRACT-APP.

#SYNTAX# CELLULAR-ABSTRACT-APP <Calling-MS-NodeId> <Called-MS-NodeId> <Call StartTime> <Call Duration> <service type> <bandwidth requirement in Kbps unit>#UsageCELLULAR-ABSTRACT-APP 1 8 51S 176S VIDEO-PHONE 160.000000CELLULAR-ABSTRACT-APP 3 9 390S 196S VOICE 13.000000CELLULAR-ABSTRACT-APP 5 3 270S 30S ANIMATION-MAIL 112.000000

Note: The aggregated node could be source or destination, as well.

GUI ConfigurationThe above described simulator configurations can be done in the QualNet GUI too. Here, we describe how to configure those parameters in the QualNet Scenario Designer GUI.

Enabling Cellular Layer3Go to Hierarchy (x) > Nodes > host(x) > Node configurations > Network Protocol > Network Protocol. From the configurable property window, set Network Protocol to Cellular Layer3 as shown in Figure 3.

FIGURE 3. Selecting Cellular Layer3

Enabling Base StationGo to Hierarchy (x) > Node configurations > Network Protocol > Network Protocol > Cellular Node Type. From the configurable property window, set the Cellular Node Type to BS, as shown in Figure 4.


FIGURE 4. Enabling Base Stations

Enabling Cellular MAC ProtocolGo to Hierarchy (x) > Nodes > host(x) > > Node configurations > MAC Protocol > MAC Protocol. From the configurable property window, set MAC Protocol to Cellular MAC as shown in Figure 5.

FIGURE 5. Selecting Cellular MAC

Configuring Cellular Application PropertiesGo to Connections > CELLULAR-ABSTRACT-APP (x) > (y). From the configurable property window, configure the properties as shown in Figure 6.


Abstract Cellular

FIGURE 6. Setting Up a Cellular Application Between Two Nodes

Enabling Cellular StatisticsGo to ConfigSettings > Statistics > Statistics. From the configurable property window, enable cellular statistics as shown in Figure 7.

FIGURE 7. Enabling Cellular Statistics


Statistics

Application Layer StatisticsTable 9 shows the Application Layer Statistics.

TABLE 9. Application Layer Statistics - MS/Aggregated Node

Statistic DescriptionNumber of application requests sent to layer 3 Total number originating application requests sent to

layer 3.

Number of application requests received from layer 3 Total number of terminating application requests received from layer 3.

Number of application requests accepted Total number of application requests accepted by the node.

Number of application requests rejected Total number of application requests rejected.

Number of application requests rejected (cause: System Busy)

Total number of application requests rejected (cause: System Busy).

Number of application requests rejected (cause: Network not Found)

Total number of application requests rejected (cause: Network Not Found).

Number of application requests rejected (cause: Too Many Active App)

Total number of application requests rejected (cause: Too Many Active Applications).

Number of application requests rejected (cause: Unknown User)

Total number of application requests rejected (cause: Unknown User).

Number of application requests rejected (cause: User Power Off)

Total number of application requests rejected (cause: User Power Off).

Number of application requests rejected (cause: User Busy)

Total number of application requests rejected (cause: User Busy).

Number of application requests rejected (cause: Unsupported Service)

Total number of application requests rejected (cause: Unsupported Service).

Number of application requests rejected (cause: User Unreachable)

Total number of application requests rejected (cause: User Unreachable)

Number of applications successfully ended Total number of applications successfully ended.

Number of origin applications successfully ended Total number of origin applications successfully ended.

Number of terminating applications successfully ended Total number of terminating applications successfully ended.

Total number of applications dropped Total number of applications dropped.

Number of origin applications dropped Total number of originating applications dropped.

Number of origin applications dropped (cause: Handover Failure)

Total number of applications dropped (cause: Handover Failure).

Number of origin applications dropped (cause: Self PowerOff)

Total number of originating applications dropped (Cause: Self PowerOff).

Number of origin applications dropped (cause: Remote PowerOff)

Total number of originating applications dropped (Cause: Remote PowerOff).

Number of terminating applications dropped Total number of terminating applications dropped.


Abstract Cellular

Cellular Layer 3 StatisticsTables 10 through 14 show the Cellular Layer 3 Statistics.

Number of terminating applications dropped (cause: Handover Failure)

Total number of terminating applications dropped (Cause: Handover Failure).

Number of terminating applications dropped (cause: Self PowerOff)

Total number of terminating applications dropped (Cause: Self PowerOff).

Number of terminating applications dropped (cause: Remote PowerOff)

Total number of terminating applications dropped (Cause: Remote PowerOff).

TABLE 10. Cellular Layer 3 Statistics - MS

Statistics DescriptionGeneral

Number of system information received from BSs Total number of system information messages received from BSs.

Number of measurement reports received from MAC Total number of measurement reports rec’d from MAC.

Cell Selection/Reselection Attach/DetachNumber of cell selection (attach) performed Total number of cell selections (attached) performed.

Number of cell reselection performed Total number of cell reselections performed.

Location UpdateNumber of location update attempt Total number of location update attempts made.

Number of location update request sent to SC Total number of location update requests sent to SC.

Average number of location update request Sent Per Attempt

Average number of location update requests sent per location update attempt.

Number of location update succeeded Total number of location updates succeeded.

Number of location update request failed Total number of location update requests failed.

Number of location update failed Total number of location updates failed.

Channel RequestNumber of channel request attempt made Total number of channel request attempts made.

Number of channel request sent Total number of channel requests sent.

Number of immediate assignment received Total number of immediate assignments received.

Number of immediate assignment rejection received Total number of immediate assignment rejections received.

Number of channel requests succeeded Total number of successful channel requests.

Number of channel requests failed Total number of unsuccessful channel requests.

Average number of channel requests sent per attempt Average number of channel requests sent per channel request attempt.

CM ServiceNumber of CM service requests sent Total number of CM service requests sent.

TABLE 9. Application Layer Statistics - MS/Aggregated Node (Continued)

Statistic Description


Number of CM service requests accepted Total number of CM service requests accepted.

Number of CM service requests rejected Total number of CM service requests rejected.

PagingNumber of page requests received Total number of page requests received.

Number of page response sent Total number of page responses sent.

HandoverNumber of handover required sent to BS Total number of handovers required sent to BS.

Number of radio interface handover received from BS Total number of radio interface handovers received from BS.

Number of radio interface handover complete sent to BS

Total number of radio interface handover complete messages sent to BS.

Number of handover required rejects received from BS Total number of handover failures received from BS.

Call ManagementNumber of voice call originated at MS Total number of voice calls originated at MS.

Number of voice call terminated at MS Total number of voice calls terminated at MS.

Number of data call originated at MS Total number of data calls originated at MS.

Number of data call terminated at MS Total number of data calls terminated at MS.

Network - ApplicationNumber of start call request received from application Total number of start call request messages received

from application.

Number of end call request received from application Total number of end call request messages received from application.

Number of call reject messages sent to application Total number of call reject messages sent to application.

Number of call dropped messages sent to application Total number of call dropped messages sent to application.

TABLE 11. Cellular Layer 3 Statistics - Base Station

Statistics DescriptionSystem Information

Number of system information broadcast Total number system information messages broadcast.

Channel RequestNumber of channel request received from MS Total number of channel requests received from MS.

Number of immediate assignment sent to MS Total number of immediate assignments sent to MS.

Number of immediate assignment reject sent to MS Total number immediate assignment rejects sent to MS.

CM ServiceNumber of CM service reject by BS sent to MS (cause: unsupported service)

Total number of CM service rejects by BS sent to MS (cause: unsupported service).

Page

TABLE 10. Cellular Layer 3 Statistics - MS (Continued)

Statistics Description


Abstract Cellular

Number of paging messages received from SC Total number of paging messages received from SC.

Number of page request sent to MS Total number of page requests sent to MS.

Number of page response received from MS Total number of page responses received from MS.

HandoverNumber of MS initiated handover required messages received from MS

Total number of MS initiated handover required messages received from MS.

Number of MS initiated handover required messages forwarded to SC

Total number of MS initiated handover required messages forwarded to SC.

Number of handover request received from SC Total number of handover requests received from SC.

Number of handover request acknowledgement sent to SC

Total number of handover request acknowledgements sent to SC.

Number of handover failure sent to SC Total number handover commands received from SC.

Number of MS initiated handover required reject received from SC

Total number of MS initiated handover required rejects received from SC.

Number of MS initiated handover required reject forward to MS

Total number of MS initiated handover required rejects forwarded to MS.

Number of handover command received from SC Total number handover commands received from SC.

Number of radio interface handover command sent to MS

Total number of radio interface handover commands sent to MS.

Number of radio interface handover complete received from MS

Total number of radio interface handover complete messages received from MS.

Number of handover complete sent to SC Total number of handover complete messages received sent to SC.

TABLE 12. Cellular Layer 3 Statistics - Switch Center

Statistics DescriptionLocation update

Number of location update requests received Total number of location update requests received.

Number of location update accept sent Total number of location update acceptances sent.

Number of location update rejects sent Total number of location update rejections sent.

Number of MAPD update location sent to HLR Total number of MAPD update locations sent to HLR.

Number of MAPD cancel location received from HLR Total number of MAPD cancel locations received from HLR.

CM ServiceNumber of CM service requests received Total number of CM service requests received.

Number of CM service accept Total number of CM service acceptances sent.

PageNumber of paging sent to BS Total number of paging messages sent to BS.

Number of page response received Total number of paging responses received.

Handovers

TABLE 11. Cellular Layer 3 Statistics - Base Station (Continued)



Number of handover required received Total number of handover requireds received.

Number of intraCell (InterSector) handover required received

Total number of intraCell (InterSector) handover requireds received.

Number of InterCell-IntraSC handover required received

Total number of interCell-intraSC handover requireds received.

Number of interSC handover required received Total number of interSC handover requireds received.

Number of handover request sent to BS Total number of handover requests sent to BS.

Number of handover request acknowledgement received from BS

Total number of handover request acknowledgements received from BS.

Number of handover request failure received from BS Total number of handover request failures received from BS.

Number of handover required reject sent to BS. Total number of handover required rejects sent to BS.

Number of handover command sent to BS Total number of handover commands sent to BS.

Number of handover complete received from BS Total number of handover complete messages received from BS.

TABLE 13. Cellular Layer 3 Statistics - Gateway

Statistics DescriptionLocation Update

Number of MAPD update location received from VLR Total number of MAPD update location received from VLR.

Number of MAPD cancel location sent to VLR Total number of MAPD cancel location sent to VLR.

Call ManagementNumber of interSc MO-MT voice calls handled Total number of interSC MO-MT voice calls handled.

Number of interSc MO-MT data calls handled Total number of interSC MO-MT data calls handled.

Number of MS to aggregated node voice calls handled Total number of MS to aggregated node voice calls handled.

Number of MS to aggregated node data calls handled Total number of MS to aggregated node data calls handled.

Number of aggregated node to MS voice calls handled Total number of aggregated node to MS voice calls handled.

Number of aggregated node to MS data calls handled Total number of aggregated node to MS data calls handled.

TABLE 12. Cellular Layer 3 Statistics - Switch Center (Continued) (Continued)



Abstract Cellular

MAC Layer StatisticsTable 15 shows the MAC Layer Statistics.

TABLE 14. Cellular Layer 3 Statistics - Aggregated Node

Statistics DescriptionCall Management

Number of aggregated node to MS voice call initiated Total number of aggregated node to MS voice calls initiated.

Number of MS to aggregated node voice call received Total number of MS to aggregated node voice calls received.

Number of aggregated node to MS data call initiated Total number of aggregated node to MS data calls initiated.

Number of MS to aggregated node data call received Total number of MS to aggregated node data calls received.

Network-ApplicationNumber of start call request received from application Total number of start call requests received from

application.

Number of end call request received from application Total number of end call requests received from application.

Number of call reject msg sent to application Total number of call reject messages sent to application.

Number of call dropped msg sent to application Total number of call dropped messages sent to application.

TABLE 15. MAC Layer Statistics

Statistics DescriptionNumber of packets sent on downlink control channel Total number of packets sent on downlink control

channel, only meaningful at base stations.

Number of packets received on downlink control channel

Total number of packets received on downlink control channel, only meaningful at mobile stations.

Number of packets sent on uplink control channel Total number of packets transmitted on uplink control channel, only meaningful at mobile stations.

Number of packets received on uplink control channel Total number of packets received on uplink control channel, only meaningful at base stations.

Number of packets sent on traffic channel Total number of packets transmitted on traffic channel.

Number of packets received on traffic channel Total number of packets received on traffic channel.


Global System for Mobile Communications (GSM) ModelThe QualNet GSM model allows calls between Mobile Stations over the radio interface. Features include:

• Configuration of MSC, multiple Base Stations, and multiple Mobile Stations• Standard band is supported (900 MHz Mobile Stations and Base Stations)• Cell selection and re-selection• Dynamic channel assignment and release• Location updating• Call setup and tear-down• Handover (intra-MSC and inter-cell/Base Station).

GSM ArchitectureThe GSM model requires three node types be defined:

• Mobile Station - MS• Base Station - BS• Mobile Switching Center - MSC

The radio/air/'Um' interface between MSs and BSs is specified as shown in the physical layer section and in the GSM-NODE-CONFIG-FILE. The 'A' interface between BSs and MSC are wired point-to-point links for which a default route file must be specified. The GSM model supports multiple BS's and one MSC.

The MSs can be located anywhere and can have any desired motion. The BSs and MSC cannot be mobile. The BSs need to be placed so that they covered the desired area. The MSs mobility can be random or based on a trace file. The MSC and BSs are placed in fixed locations, with no mobility, while the MS's can be placed at specific locations initially. The current GSM model allows multiple MSs, multiple BSs and a single MSC in any scenario.

The MSC is connected to each BS via one-to-one links and any routing protocol (the Bellman Ford routing protocol is preferable) is used to route packets between them. The current model uses an IP-based stack for messaging between the MSC and the BSs.

You must consider the following when creating a new GSM scenario:

1. Add multiple wireless channels for BSs.2. The listening channel mask should be zero for all MSs.3. All BSs must be connected with a wireless subnet.4. All BSs must be connected with MSC through any point to point connection or wireless networks.5. Configured neighboring BSs information for each BS.6. All MSs must listen each broadcast channels. Like [MS node id] GSM-CONTROL-CHANNEL

[Broadcast channel information]7. Use GSM link to establish the call between to MSs.8. Set GSM protocol at network layer, MAC layer and physical layer for each BS and MS.9. MSC needs only GSM Layer3 protocol at the network layer.


Global System for Mobile Communications (GSM) Model

Command Line ConfigurationTo simulate a GSM system in QualNet you must plan the network layout. A user must determine the node type of each node, as well as the logical connectivity among these nodes, and configure each node according to its node type. For example, the location of each node, the mobility pattern of nodes, and, especially, the configuration of a BS, involves making decisions about the following:

• Number of Base Stations• Number of channels available to each BS (at least one channel pair for the control channels needs to

be allotted per BS)• Location of BSs to provide coverage in the intended area.

In Figure 8 below, nodes 1 through 6 are Mobile Stations (MS), 7 and 8 are Base Stations (BS), and node 9 is a Mobile Switch Center (MSC). The MS nodes are placed in a random fashion in the covered area and move as specified in the mobility trace file. The BS nodes are placed to cover the desired area and are fixed in location, as is the MSC. The BS's are connected via wired LINKs to the MSC and a default route file needs to be specified to ensure messaging between them is sent on the correct interface. The scenario is briefly illustrated below:

FIGURE 8. Simulating a GSM System

All PHYSICAL and MAC layer parameters of GSM are specified in the main configuration file. An additional configuration file is used for layer 3 parameters.


Table 16 shows the GSM configuration parameters.

See the following for some general configurations common to all types of nodes and how they are specified:

• Node Type# Node specific setup[1 thru 6] GSM-NODE-TYPE GSM-MS[7 thru 8] GSM-NODE-TYPE GSM-BS[9] GSM-NODE-TYPE GSM-MSC

• Mobility# MS's are mobile.[1 thru 6] MOBILITY TRACEMOBILITY-TRACE-FILE mobility-file-of-MS# BS's and MSC are stationary[7 thru 9] MOBILITY NONE

• Node PlacementThe MSs can be located anywhere and can have any desired mobility. The BSs need to be placed so that they cover the desired area.

NODE-POSITION FILENODE-POSITION-FILE .gsm-placement.nodes[1 thru 6] MOBILITY TRACE

Note: The NODE-POSITION-FILE is used for both initial node placement and can also be used for FILE based mobility traces.

• NETWORK/MAC protocol

TABLE 16. GSM Parameters

Configuration Parameter DescriptionGSM-STATISTICS YES | NO Specifies printing of GSM statistics. YES prints the GSM

statistics into a .stat file. The default value is NO.

GSM-NODE-CONFIG-FILE Specifies the name / absolute path of .gsm file. This parameter is mandatory.

GSM-NODE-TYPE [GSM-MS | GSM-BS | GSM-MSC] Specifies the GSM node type. The default value is GSM-MS.

GSM-CONTROL-CHANNEL Specifies the GSM control channel list. This parameter is mandatory.

PHY-GSM-DATA-RATE Specifies the data transmission rate. The default value is 270833.

PHY-GSM-TX-POWER Specifies the node transmitting power. The default value is 15.0 dBm.

PHY-GSM-RX-SENSITIVITY Specifies the reception sensitivity for the node. The default value is -91.0 dBm.

PHY-GSM-RX-THRESHOLD Specifies the minimum reception threshold to accept packets. The default value is -92.0 dBm.



[1 thru 8] MAC-PROTOCOL GSM#Node 9 is the MSC. It has no GSM MAC related functionality.

# All nodes in the GSM simulation are configured to use GSM Layer3[1 thru 9] NETWORK-PROTOCOL GSM-LAYER3# Routes need to be setup explicitly between BS & MSCDEFAULT-ROUTE YESDEFAULT-ROUTE-FILE default-route-file

Node specific properties can be specified using the GSM Layer 3 config file as follows:GSM-NODE-CONFIG-FILE ./gsm-node-config.gsm

Any node that has GSM-LAYER3 will also have the IP stack.• Statistics

GSM Layer 3 statistics can be enabled by setting the following parameter. If it is set to NO, then statistics will be disabled.

GSM-STATISTICS YES | NO

Specific configurations for MS and BS are illustrated as follows

1. Um Interface (MS-BS)To configure the Um Interface, define the radio channels used in the simulation and then specify the channel allocation in the GSM system, as well as GSM-related physical properties.

# Carrier frequencies for GSM 900: # 890 - 915 MHz: mobile transmit, base receive;# 935 - 960 MHz: base transmit, mobile receive# See GSM 05.05 for more information.# n is the ARFCN number (0 < n < 124 for GSM 900)# Channels should be created in pairs using the following rules.# DownLink FREQUENCY = 890MHz + 0.2*n# UpLink = DownLink + 45 MHzPROPAGATION-CHANNEL-FREQUENCY[0] 890.0e6 PROPAGATION-CHANNEL-FREQUENCY[1] 935.0e6 PROPAGATION-CHANNEL-FREQUENCY[2] 890.2e6 PROPAGATION-CHANNEL-FREQUENCY[3] 935.2e6 PROPAGATION-CHANNEL-FREQUENCY[4] 890.4e6 PROPAGATION-CHANNEL-FREQUENCY[5] 935.4e6 PROPAGATION-CHANNEL-FREQUENCY[6] 890.6e6 PROPAGATION-CHANNEL-FREQUENCY[7] 935.6e6

# All channels must be listenable by every node using the radio interface.[1 thru 9] PHY-LISTENABLE-CHANNEL-MASK 11111111[1 thru 9] PHY-LISTENING-CHANNEL-MASK 00000000# MS’s stored BCCH channel list[1 thru 6] GSM-CONTROL-CHANNEL [0 4]# BS 1[7] GSM-CONTROL-CHANNEL [0]# BS 2 [8] GSM-CONTROL-CHANNEL [4]# For all MS’s and BS’s[1 thru 8] PHY-MODEL PHY-GSM# GSM PHY characteristicsPHY-GSM-DATA-RATE 270833#


# PHY-GSM-TX-POWER: Initial phy transmission power (in dBm)# See GSM 05.05, GSM Text Chapter 6## BS: TRX Power Class 5 in GSM 900: 20W (43dBm) to (<40) W (46 dBm)[7 thru 8] PHY-GSM-TX-POWER 20.0# MS: For Class 4 MS in GSM 900: Max power = 2W (33 dBm)[1 thru 6] PHY-GSM-TX-POWER 20.0## PHY-GSM-RX-SENSITIVITY: sensitivity of the phy (in dBm)# See GSM 05.05 Section 6#PHY-GSM-RX-SENSITIVITY -110.0# RXLEV_ACCESS_MIN in GSM 05.08PHY-GSM-RX-THRESHOLD -90.0

In the following, we break down each of these configuration parameters• Channel Allocation

The current GSM model in QualNet uses the 900MHz band. Each operational BS should be allocated an even number of channels, a minimum of 4. The channels are allocated to a BS in pairs: downlink-uplink. The BSs downlink control channel (C0) is specified in the main configuration file and the entire channel range is provided in the GSM-NODE-CONFIG-FILE. The following parameters are specified in the main configuration file (.config), unless noted otherwise.Downlink frequency = 890MHz + 0.2 * nUplink frequency = Downlink + 45MHz

where n = the channel instance number.PROPAGATION-CHANNEL-FREQUENCY

• Channel Listening MaskFor each channel created, a binary flag is added to the following two parameters:PHY-LISTENABLE-CHANNEL-MASK 1111 (during entire simulation)PHY-LISTENING-CHANNEL-MASK 0000 (at initialization)

The LISTENABLE parameter specifies which channels the nodes will be listening to during the entire simulation. The LISTENING parameter specifies which channels the nodes will be listening to at initialization. The nodes are not listening to any particular channel since this will be set based on the rest of the configuration and dynamic channel assignment during the simulation.

• Control ChannelsEach BS uses the first (lowest even numbered) channel allocated to it as the downlink control channel (C0). The MSs are configured to listen to the downlink control channels used by all the BSs in the scenario. # Specify all downlink control channels for MS's[1 thru 6] GSM-CONTROL-CHANNEL [0 4]

# BS 1 downlink channel[7] GSM-CONTROL-CHANNEL [0]# BS 2 downlink channel[8] GSM-CONTROL-CHANNEL [4]



• Other Physical Layer ParametersThe following physical layer parameters are also applicable to the GSM model:PHY-GSM-TX-POWER 20.0PHY-GSM-RX-THRESHOLD -90.0PHY-RX-MODEL BER-BASEDPHY-RX-BER-TABLE-FILE data/modulation/gmsk Gaussian Minimum Shift Keying; Wireless physical layer model for modulation / coding..ber

All MS and BS should define a GSM Um interface. For example,SUBNET N8-192.0.0.0 {1 thru 8 } 566.83 762.38 0.0[ N8-192.0.0.0 ] PHY-MODEL PHY-GSM

2. “A” Interface Link Between Each BS and the MSC# BS Node 7 and MSC Node 9LINK N2-3.0 {7,9}[N2-3.0] LINK-PHY-TYPE WIRED[N2-3.0] LINK-BANDWIDTH 1544000[N2-3.0] LINK-PROPAGATION-DELAY 1MS# BS Node 8 and MSC Node 9LINK N2-4.0 {8,9}[N2-4.0] LINK-PHY-TYPE WIRED[N2-4.0] LINK-BANDWIDTH 1544000[N2-4.0] LINK-PROPAGATION-DELAY 1MS# Any node that has GSM-LAYER3 will also be have the IP stack

3. GSM Node configuration fileThe GSM node configuration file defines the special layer 3 GSM properties of MS/BS/MSC. For example, LAC and cell ID of a BS, or relationship between BSs and MSC.

# GSM Layer 3 configuration for each node is specified in a separate file# using the parameter GSM-NODE-CONFIG-FILE in the main configuration file.GSM-NODE-CONFIG-FILE gsm-node-file# The GSM-NODE-CONFIG-FILE has the following format# Layer 3 parameters# General format of parameters in this file:# <Node-Type> <NodeId> <Other node type specific parameters># Mobile Station (MS)## GSM-MS [NodeId]GSM-MS 1GSM-MS 2GSM-MS 3GSM-MS 4GSM-MS 5GSM-MS 6## Base Station (BS)# GSM-BS [NodeId] [LAC] [CellId] [ChannelRange] [MSC NodeId] [Neigh.BS Info]# Note: [ChannelRange] has the control channel index as the first one.# [Neigh.BS Info] is a variable list (max 6) of triads of the form:# "BcchChannel-Lac-CellIdenity" with no space between '-' symbols.# Channels should be allocated to each BS in pairs (downlink, uplink). The# first pair is used as a control channel, the rest are used for allocating# to MS's.


GSM-BS 7 1 1 0-3 9 4-1-2GSM-BS 8 1 2 4-7 9 0-1-1# Mobile Switching Center (MSC)## GSM-MSC [Nodeid] [Linked BSInfo]# Note: [Linked BSInfo] is of the form:# "BSNodeId-LAC-CellIdentity" with no space between '-' symbols.GSM-MSC 9 7-1-1 8-1-2

4. GSM Calls setting in .app file# The GSM calls are specified in the application file with following format# Applications file# GSM <Calling-MS-NodeId> <Called-MS-NodeId> <Call StartTime> <Call Duration>GSM 6 5 14S 460SGSM 3 1 400S 120SGSM 2 4 70S 150SGSM 6 5 500S 70S

GSM Layer 3 Statistics

Table 17 shows the GSM layer 3 MS Statistics.

TABLE 17. GSM Layer 3 Statistics - Mobile Station (MS)

Statistics DescriptionNumber of traffic packets sent to BS. Total number of traffic packets sent to BS.

Number of traffic packets received from BS.

Total number of traffic packets received from BS.

Number of times channel request sent to BS.

Total number of times channel requests sent to BS.

Number of times channel request attempts failed.

Total number of times channel requests attempts failed.

Number of times channel assignment received from BS.

Total number of times channel assignments received from BS.

Number of times channel release packets received from BS.

Total number of times channel release packets received from BS.

Number of times location update request packets sent to BS.

Total number of times location updates request packets sent to BS.

Number of times location update accept packets received from BS.

Total number of times location updates accept packets received from BS.

Number of calls initiated on MS. Total number of calls initiated on MS.

Number of calls received from other MS.

Total number of calls received from other MS.

Number of calls connected on MS. Total number of calls connected on MS.

Number of calls completed on MS. Total number of calls completed on MS.

Number of times handovers performed on MS.

Total number of times handovers performed on MS.



Table 18 shows the GSM layer 3 BS statistics

Table 19 shows the GSM Layer 3 MSC statistics

TABLE 18. GSM Layer 3 Statistics - Base Station (BS)

Statistics DescriptionNumber of traffic packets sent to air interference.

Total number of traffic packets sent to air interference.

Number of traffic packets received from air interference

Total number of traffic packets received from air interference

Number of times channel request received form MSs.

Total number of times channel requests received form MSs.

Number of times channel assignment attempts failed.

Total number of times channel assignment attempts failed.

Number of times channel assigned to MSs.

Total number of times channel assigned to MSs.

Number of times channel released on BS.

Total number of times channel released on BS.

Number of times channel seized due to timer T3101 expiration.

Total number of times channel seized due to timer T3101 expiration.

Number of paging request sent on air interference.

Total number of paging requests sent on air interference.

Number of times location updated packets received from MSs.

Total number of times location updated packets received from MSs.

Number of times channel measurement report received from MSs.

Total number of times channel measurement reports received from MSs.

Number of times handover completed on incoming MSs.

Total number of times handover completed on incoming MSs.

Number of times handover attempts packets received from MSs.

Total number of times handover attempts packets received from MSs.

Number of handover completed on MSs.

Total number of handover completed on MSs.

Number of times handover request failed.

Total number of times handover requests failed.

TABLE 19. GSM Layer 3 Statistics - Mobile Switching Center (MSC)

Statistics DescriptionNumber of times location update request received from BSs.

Total number of times location update requests received from BSs.

Number of times calls initiation request received.

Total number of times calls initiation requests received.

Number of calls connected. Total number of calls connected.

Number of calls completed successfully.

Total number of calls completed successfully.


MAC Layer Statistics

Table 20 shows the MAC layer MS statistics.

PHY Layer StatisticsTable 21 shows the PHY layer statistics.

Number of handover required messages received from BSs.

Total number of handover required messages received from BSs.

Number of handover completed successfully.

Total number of handover completed successfully.

Number of times handover request failed

Total number of times handover requests failed

Number of traffic packets transferred. Total number of traffic packets transferred.

TABLE 20. MAC Layer Statistics - Mobile Station (MS)

Statistics DescriptionNumber of times MS selected cell. Total number of times MS selected cell.

Number of times MS failed to select any cell.

Total number of times MS failed to select any cell.

Number of times MS tried to reselect another cell.

Total number of times MS tried to reselect another cell.

TABLE 21. PHY Layer Statistics

Statistics DescriptionNumber of signals transmitted on physical layer.

Total number of signals transmitted on physical layer.

Number of signals received from the physical layer and forwarded to the MAC layer.

Total number of signals received from the physical layer and forwarded to the MAC layer.

TABLE 19. GSM Layer 3 Statistics - Mobile Switching Center (MSC)



User Behavior Model

User Behavior Model In real network scenarios, the behaviors of network nodes may vary a lot based on their types and attributes. For example, some people may tend to use multimedia applications more often than others. Some may have longer phone calls than others. Such characteristics are referred to as user behaviors. In a network simulation, the traffic patterns and mobility patterns are affected significantly by user behaviors and environment factors. In this effort, we are targeting modeling the user behaviors in QualNet simulator. We mainly consider adding attributes to nodes and realizing traffic patterns based on related user attributes (i.e., traffic patterns specified for the user).

In this implementation, user attributes mainly include basic attributes such as age, sex, and traffic patterns. A user profile will be used to describe the characteristics of a user using some distributions. It will also refer to some traffic patterns to describe the characteristics of traffic flows generated by a user. The description of the traffic patterns are put in one or multiple traffic pattern definition files.

The traffic flows generated by user behavior model will send feedbacks about its status (rejected, dropped, or successfully finished) to the user behavior model. The user behavior model will then calculate a user dissatisfaction degree based on such feedbacks. This degree is intended to reflect users’ perception of the service quality. In addition to this, for rejected or dropped flows, the user behavior model will perform proper retries indicated by the traffic pattern.

Traffic patterns can be affected by many user attributes and environment factors. One of the requirements is to generate traffic, based on arbitrary distributions. QualNet already provides APIs for both common random distribution functions, as well as user-defined random distributions.

Command Line ConfigurationUser attributes are configured via user profiles. A user profile describes a type of user by indicating their attributes and traffic pattern. Users can define multiple user profiles, each with different characteristics. These user profiles can be defined in one or more user profile files. Then, the profiles can be assigned to nodes in the main configuration file of QualNet. If a default status is defined, this traffic pattern is used either when a user status is undefined or, when it is not listed in the user profile.

User Profile ParametersTable 22 shows the parameters available in the User Behavior Model:

TABLE 22. User Behavior Model Parameters - User Profile

Parameters DescriptionUSER-PROFILE-FILE[index] <filename>

Specifies the files that contain one or more user profiles. For example:

USER-PROFILE-FILE myprofile.pf

or

USER-PROFILE-FILE[1] myprofile1.pf USER-PROFILE-FILE[2] myprofile2.pf


Each user profile must be defined in the user profile file in following the format:

USER-PROFILE <profile-name>AGE <distribution>SEX <distribution><traffic-description1><traffic-description2><traffic-description3>

Where:<profile-name> is a unique string identifies the name of the profile. <distribution> indicates the distribution for generating a random number. The format of the <distribution> needs to follow the format defined by the random number generation module. The general format is <distribution-name> <parameter-list> <min-value>, <max-value>. For example, the following means uniform distribution between 15 and 30.

UNI 15, 30

The <distribution-name> is the name of a distribution. It could be the name of a custom arbitrary distribution defined by users. Pre-implemented common distributions are UNI (uniform distribution), DET (deterministic distribution), EXP (exponential distribution).

<traffic-description>

The traffic description gives the relation between the user profile and the traffic pattern. The format of the <traffic-description> is as given in example below

[NodeId] USER-PROFILE <profile-name> Assigns a user profile to one or more nodes. For example:

[1 thru 20] USER-PROFILE young

[NodeId] USER-STATUS[index] <user-status-name>

[NodeId] USER-STATUS-START-TIME[index]

<start-time>

Specifies a user status and its start time. For example:

USER-STATUS before-fireworks USER-STATUS-START-TIME 0S

Configuring at Node Level assigns a user status to one or more nodes. In this way, you can have different sets of nodes experiencing different statuses at the same time. For example, you can have a set of nodes watching a fireworks show while others watch a movie.

[1 thru 10] USER-STATUS[0] before-fireworks

[1 thru 10] USER-STATUS-START-TIME[0] 0S

[1 thru 10] USER-STATUS[1] during-fireworks


[11 thru 20] USER-STATUS[0] start-movie


Note that all of the user statuses for a node should be listed in chronological order with respect to the index.

TABLE 22. User Behavior Model Parameters - User Profile (Continued)

Parameters Description


User Behavior Model

USER-STATUS before-fireworksTRAFFIC-PATTERN active

USER-STATUS during-fireworksTRAFFIC-PATTERN inactive

Traffic Pattern ParametersA traffic pattern depicts the characteristics of how to generate traffic. Traffic patterns are defined in one or multiple traffic pattern files. These traffic patterns are referred to in user profiles. Thus, there is no need to explicitly assign traffic patterns to a node in the main configuration file. However, users still need to specify the traffic pattern files in the main configuration file. Table 23 shows the traffic pattern parameters for the User Behavior model.

Each traffic pattern must be defined in the traffic pattern file in following the format.

TRAFFIC-PATTERN <pattern-name>NUM-APP-TYPES <number>MAX-NUM-APPS <distribution>ARRIVAL-INTERVAL <distribution><traffic-pattern-description1><traffic-pattern-description2>…

Where:<pattern-name> is a unique string that identifies the traffic pattern. This name is referred to by the user profile file to describe traffic generated by the user. The parameter NUM-APP-TYPES indicates the number of application types used to generate traffic in the particular pattern. MAX-NUM-APPS indicates the maximum number of applications a node can have at any time. ARRIVAL-INTERVAL defines the interval for generating a new application. The <traffic-pattern-description> describes the characteristics of traffic that will be generated by the application. The number of appearances of <traffic-pattern-description> is defined by parameter NUM-APP-TYPES. The format of one <traffic-pattern-description> is shown below:

PROBABILITY <prob-value>RETRY-PROBABILITY <prob-value>RETRY-INTERVAL <distribution>MAX-NUM-RETRIES <int-value><traffic-generator-description>

Where:PROBABILLITY indicates the probability with which a particular <traffic-description> will be selected to generate the application traffic. RETRY-PROBABILITY indicates the probability of retries if the

TABLE 23. User Behavior Traffic Pattern Parameters

Parameters DescriptionTRAFFIC-PATTERN-FILE[index] <traffic-pattern-file> Specifies traffic pattern files to be included in this

scenario. TRAFFIC-PATTERN-FILE mytraffic.tf

Multiple traffic pattern files are specified:

TRAFFIC-PATTERN-FILE[1] mytraffic1.tf

TRAFFIC-PATTERN-FILE[2] mytraffic2.tf


application is rejected or dropped. RETRY-INTERVAL indicates the delay before retry of the application. MAX-NUM-RETRIES indicate the maximum number of retries that can be performed. The order in which the parameter appears is important. The parser generated for the traffic pattern file is order sensitive and omitting or changing the order would result in syntax error in the file.<traffic-generator-description> indicates how a QualNet traffic generator will be configured to generate the real traffic. The <traffic-generator-description> format is similar to the format in the .app file of existing QualNet. The only difference being the source node ID and starting time are omitted in the definition. If an application requires end time, it is replaced as duration in the <traffic-generator-description>. The parameters required by original QualNet application will be depicted using a distribution in <traffic-generator-description>. An example of a <traffic-generator-description> is given below:

CELLULAR-ABSTRACT-APP UNI 1,20 EXP 100S …

This example means the QualNet application CELLULAR-ABSTRACT-APP will be used to generate traffic. Its source node ID is current node. Destination node is uniform distribution between nodes 1 to 20 including nodes 1 and 20. Its starting time is decided by previous parameter <ARRIVAL-INTERVAL> of the traffic pattern. Its duration is decided by exponential distribution with average time as 100S. In a situation where the QualNet application requires an end time instead of duration, the end time is then the starting time, plus duration.

Custom Arbitrary Distributions ConfigurationIn the above user profile and traffic pattern configurations, in places where a random distribution is required, you can also configure custom arbitrary distributions, in addition to common distributions. Custom arbitrary distribution is the capability provided by the QualNet random number module, so its configuration is not described here in detail.

GUI Configuration

Enable User Behavior Model Go to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. From the configurable property window, set Enable User behavior modeling? to Yes as shown in Figure 9.


User Behavior Model

FIGURE 9. Enabling User Behavior Model

Configuring User ProfileGo to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. Set User Profile File, as shown in Figure 10.


FIGURE 10. Configuring User Profile

Configure User StatusGo to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. Set User Status, as shown in Figure 11.


User Behavior Model

FIGURE 11. Configuring User Status

Configure User Status Start TimeGo to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. Set User Status Start Time, as shown in Figure 12.


FIGURE 12. Configuring User Status Start Time

Configure Traffic Pattern FileGo to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. Specify Traffic Pattern File, as shown in Figure 13.


User Behavior Model

FIGURE 13. Configuring Traffic Pattern File

Configure Arbitrary Distribution FileGo to ConfigSettings > User behavior model > User behavior model > Enable User behavior modeling?. Specify Arbitrary Distribution File as shown in Figure 14.


FIGURE 14. Configuring Arbitrary Distribution File

Adding Another Instance of the ParameterTo add another User Profile File, User Status, User Status Start Time or Traffic Pattern File, right click on the parameter and select Add another, as shown in Figure 15.


User Behavior Model

FIGURE 15. Adding Another Instance of the Parameter

Sample ScenarioThis section describes the way in which a user can easily create a simple scenario and run it using QualNet.

Scenario Description - This sample is a User Behavior Model in a scenario that contains 30 nodes defined as Mobile Stations (MS), 2 Base Stations (BS), 1 Switch Center (SC), 1 Gateway and 1 Aggregated Node. The User Behavior Model, and the Arbitrary Distribution Model are integrated in this sample scenario.

Topology - The topology is similar to any cellular scenario with 30 MS placed around 2 BS. The BS are controlled by a SC. A Gateway is placed between the Aggregated Node and Switch Center to establish connection.

Command Line Configuration1. Comment out the APP-CONFIG-FILE (we recommend not using the application file if the traffic is only

generated by the user-behavior model).2. For each of the 30 nodes we now need to provide user profiles and traffic pattern files. In the sections

below, default.pf is defined, which has three user-profiles: young, middle, and old. You must assign the nodes to one of these profiles. Assign the first 10 nodes to the young profile, the next 10 to the old, and the last 10 nodes to the middle.


[1 thru 10] USER-PROFILE young[11 thru 20] USER-PROFILE old[21 thru 30] USER-PROFILE middle

3. Add the default.pf file to the scenario. USER-PROFILE-FILE ./default.pf

Contents of sample USER-PROFILE FILE (default.pf)

USER-PROFILE youngAGE UNI 10, 30SEX UNI 0,1USER-STATUS before-fireworksTRAFFIC-PATTERN activeUSER-STATUS during-fireworksTRAFFIC-PATTERN inactiveUSER-STATUS after-fireworksTRAFFIC-PATTERN very-activeUSER-STATUS defaultTRAFFIC-PATTERN active

USER-PROFILE middleAGE UNI 31, 50 SEX UNI 0,1USER-STATUS before-fireworksTRAFFIC-PATTERN mediumUSER-STATUS during-fireworksTRAFFIC-PATTERN inactiveUSER-STATUS after-fireworksTRAFFIC-PATTERN active

USER-PROFILE oldAGE UNI 51, 100 SEX UNI 0,1USER-STATUS after-fireworksTRAFFIC-PATTERN medium

4. Every user profile has a USER-STATUS keyword. This keyword is defined in the main configuration file. In the default.pf file, four statuses are defined: default, before-fireworks, after-fireworks, and during fireworks. You must set this parameter in the configuration file. This is an optional parameter, and if not specified, the default values are used.

USER-STATUS[0] before-fireworksUSER-STATUS-START-TIME[0] 0SUSER-STATUS[1] during-fireworksUSER-STATUS-START-TIME[1] 600SUSER-STATUS[2] after-fireworksUSER-STATUS-START-TIME[2] 900S

5. Add the traffic pattern file to get the traffic for the above mentioned users. This is the same file that we have defined above. The file has three patterns: active, inactive, and medium.

TRAFFIC-PATTERN-FILE ./default.tf


User Behavior Model

Contents of sample TRAFFIC-PATTERN FILE (default.tf)

TRAFFIC-PATTERN activeNUM-APP-TYPES 2MAX-NUM-APPS DET 4ARRIVAL-INTERVAL EXP 5MPROBABILITY 0.8RETRY-PROBABILITY 0.5RETRY-INTERVAL mydistMAX-NUM-RETRIES 5CELLULAR-ABSTRACT-APP UNI 1, 20 EXP 100S DET 23 DET 13PROBABILITY 0.2RETRY-PROBABILITY 0.1RETRY-INTERVAL EXP(5M)MAX-NUM-RETRIES 2CELLULAR-ABSTRACT-APP UNI 11, 15 EXP 50S DET 1 DET 13

TRAFFIC-PATTERN mediumNUM-APP-TYPES 1MAX-NUM-APPS DET 1ARRIVAL-INTERVAL EXP 15MPROBABILITY 0.5RETRY-PROBABILITY 0.8RETRY-INTERVAL EXP 12MMAX-NUM-RETRIES 2CELLULAR-ABSTRACT-APP UNI 1, 20 EXP 100S DET 3 DET 13

TRAFFIC-PATTERN inactiveNUM-APP-TYPES 1MAX-NUM-APPS DET 4ARRIVAL-INTERVAL EXP 5MPROBABILITY 0.1RETRY-PROBABILITY 0.2RETRY-INTERVAL EXP 2MMAX-NUM-RETRIES 1

6. Since the distributions in the traffic pattern files are custom user distributions, you must add the Arbitrary Distribution file in the scenario.

ARBITRARY-DISTRIBUTION-FILE ./default.dist

Contents of sample ARBITRARY DISTRIBUTION FILE (default.dst)

ARBITRARY-DISTRIBUTION mydistNUM-POINTS 47 0.23 0.39 0.411 0.1

In the above example, probability distribution called "mydist" is defined. This distribution returns 7 with probability 0.2, or 3 with probability 0.3, or 9 with probability 0.4, or 11 with probability 0.10. It is always assumed that X and Y values are floating-point numbers. The X and Y values entered do not need to be normalized (the sum of them is equal to 1). While reading the distribution, QualNet will normalize the data.


GUI Configuration1. For nodes 1 to 30 (MS), go to Hierarchy (x) > Default Device Properties > Node configurations

> User behavior model > Enable User behavior modeling?. From the configurable property window, set Enable User behavior modeling? to Yes and specify the User Profile file.

2. For nodes 1 to 30, Hierarchy (x) > Node configurations > User behavior model > Enable User behavior modeling?. Set Enable User behavior modeling?. From the configurable property window, specify User Status and User Status Start Time.

3. Also set ConfigSettings > the User behavior model > User behavior model > Enable User behavior modeling? Set User Profile File, User Status, User Status Start Time, and specify the Traffic Pattern File, and specify the Arbitrary Distribution File (if any) for Nodes 1 to 30.

4. Set the properties of nodes 31-32 (BS). Go to Hierarchy (x) > Nodes > host31 > Node configurations > Network Protocol > Network Protocol > Cellular Node Type. Set Cellular Node Type as BS. From the configurable property window, specify other parameters of the BS. Similarly, repeat the step for host32.

5. Set host33 as switching center (SC) and configure the corresponding properties. Go to Hierarchy (x) > Nodes > host33 > Node configurations > Network Protocol > Network Protocol > Cellular Node Type. Set Cellular Node Type as MSC.

6. Set host34 as Gateway and configure the corresponding properties. Go to Hierarchy (x) > Nodes > host34 > Node configurations > Network Protocol > Network Protocol > Cellular Node Type. Set Cellular Node Type as Gateway.

7. Set host35 as aggregated node and configure the corresponding properties. Go to Hierarchy (x) > Nodes > host35 > Node configurations > Network Protocol > Network Protocol > Cellular Node Type. Set Cellular Node Type as Aggregated Node.

At this point, the scenario has successfully integrated the user behavior model, and arbitrary distribution file.

StatisticsTable 24 shows the statistics available in the user behavior model.

Note: An application could be rejected, or dropped multiple times.

TABLE 24. User Behavior Model Statistics

Statistic DescriptionAverage Dissatisfaction The dissatisfaction degree is computed by finding the number of calls

completed, rejected, and the number of calls made.

Applications Generated Total number of applications the user has tried to start.

Applications Successfully Finished Total number of applications that finished successfully.

Applications Rejected Total number of applications which have been rejected.

Applications Dropped Total number of application sessions that have been dropped.

Retries Total number of retry attempts made.

Average Retries per App Average number of retry attempts made for an application.


qualnet 4.5 cellular model library - ucsbebelding/courses/284/qualnet/...2 qualnet 4.5 cellular...

Documents