iDEN System Integration

Major Project Report

Submitted in partial fulfillment of the requirements

For the degree of

Master of Technology
In
Electronics & Communication Engineering
(Communication Engineering)

By

Dharsandia Tanvi Dineshbhai

(09MECC04)

Department of Electronics & Communication Engineering

Institute of Technology
Nirma University
Ahmedabad-382 481
Dec 2010
 ii

iDEN System Integration

Major Project Reprot

Submitted in partial fulfillment of the requirements

For the degree of

Master of Technology
In
Electronics & Communication Engineering
(Communication Engineering)

By

Dharsandia Tanvi Dineshbhai

(09MECC04)

Under the Guidance of

Dr. D. K. Kothari

Department of Electronics & Communication Engineering

Institute of Technology
Nirma University
Ahmedabad-382 481
Dec 2010
 iii

Declaration

This is to certify that

i) The thesis comprises my original work towards the degree of Master of Technology
in Communication Engineering at Nirma University and has not been submitted
elsewhere for a degree.

ii) Due acknowledgement has been made in the text to all other material used.

Dharsandia Tanvi Dineshbahi

 iv

Certificate
This is to certify that the Major Project entitled iDEN System Integration
submitted by Dharsandia Tanvi Dineshbhai(09MECC04), towards the partial
fulfillment of the requirements for the degree of Master of Technology in Communi-
cation Engineering of Nirma University, Ahmedabad is the record of work carried out
by her under our supervision and guidance. In our opinion, the submitted work has
reached a level required for being accepted for examination. The results embodied
in this major project, to the best of our knowledge, havent been submitted to any
other university or institution for award of any degree or diploma.

Date: Place: Ahmedabad

Guide HOD

(Dr. D. K. Kothari) (Prof. A. S. Ranade)

Professor, EC Professor, EC

Director

(Dr K Kotecha)
Director, IT, NU
 v

Abstract

Integrated Digital Enhanced Netwok (iDEN) system is a wireless techonolgy, orig-

inally designed by Motorola and used with the Sprint/Nextel service in U.S. It is
the land-mobile radio communication network that integrates several communication
services into one platform. Using just one pocket-sized digital handset, it integrates
the functionality of digital cellular (Interconnect) service, digital two-way radio (Dis-
patch) and an always connected internet browser (Packet Data) service into a single
platform. Interconnect service is very similar to the cellular service. Users have capa-
bility to freely roam to any connected system and maintain full telephone interconnect
capability, including circuit-switched data and short message service. Dispatch ser-
vice allows groups of users or individuals to communicate quickly and easily with each
other at the same time. Packet data provides connectionless services. User can access
the internet or a company intranet, pick up and send faxes and email by connecting
the iDEN terminal to the computer. Different network elements are going to be tested
in Motorola. So, as a part of system testing, Dispatch Application Processor (DAP)
has been tested with the testing tool CTHA. Different scripting languages have been
used for testing the DAP.
 vi

Acknowledgements

I would like to express my gratitude and sincere thanks to Prof. A. S. Ranade Head
of Electrical Engineering Department and Dr. D. K. Kothari Coordinator M.Tech
Communication Engineering program for allowing me to undertake this thesis work
and for his guidelines during the review process.
I am deeply indebted to my thesis supervisors Dr. D. K. Kothari and Mr.
Varadarajulu Kolamala, Project Manager Motorola for their constant guidance and
motivation. I also wish to thank V Chetan, Vasundhara Leena, Rai Papu, S Sin-
duja and Surajan Reshma for their help and support. Without their experience and
insights, it would have been very difficult to do quality work.
I wish to thank my friends of my class for their delightful company which kept me
in good humor throughout the year.
Last, but not the least, no words are enough to acknowledge constant support and
sacrifices of my family members because of whom I am able to complete the degree
program successfully.

- Dharsandia Tanvi Dineshbhai

09MECC04
Contents

Declaration iii

Certificate iv

Abstract v

Acknowledgements vi

List of Figures x

1 Introduction 1
1.1 iDEN Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 iDEN Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Interconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.2 Dispatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.3 Packet Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 System Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.1 Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.2 Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3.3 Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.4 Urban . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.5 Service Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.6 Location Area . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.7 Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 iDEN Key Technologies . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.1 Vector Summed Excited Linear Prediction (VSELP) . . . . . 5
1.4.2 Time Division Multiple Access (TDMA) . . . . . . . . . . . . 5
1.5 Thesis Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 System Network Elements 7

2.1 Radio Access Network Elements . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.2 Enhanced Based Transceiver System (EBTS) . . . . . . . . . . 7
2.1.3 Digital Cross Connect Switch (DCS) . . . . . . . . . . . . . . 8

vii
CONTENTS viii

2.2 Interconnect Network Elements . . . . . . . . . . . . . . . . . . . . . 9

2.2.1 iDEN Base Site Controller (iBSC) . . . . . . . . . . . . . . . . 10
2.2.2 Mobile Switching Center (MSC) . . . . . . . . . . . . . . . . . 10
2.2.3 Home Location Register (HLR) . . . . . . . . . . . . . . . . . 10
2.2.4 Visitor Location Register (VLR) . . . . . . . . . . . . . . . . . 10
2.2.5 Short Message Service (SMS) . . . . . . . . . . . . . . . . . . 11
2.2.6 Voice Mail System (VMS) . . . . . . . . . . . . . . . . . . . . 11
2.2.7 Interworking Function (IWF) . . . . . . . . . . . . . . . . . . 11
2.3 Dispatch Network Elements . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.1 Dispatch Application Processor (DAP) . . . . . . . . . . . . . 11
2.3.2 Dispatch Visitor Location Register (D-VLR) . . . . . . . . . . 14
2.3.3 Metro Packet Switch (MPS) . . . . . . . . . . . . . . . . . . . 14
2.3.4 Advanced Packet Duplicator (APD) . . . . . . . . . . . . . . . 14
2.3.5 iDEN Dispatch Access Controller (iDAC) . . . . . . . . . . . . 14
2.3.6 iDEN Surveillance Gateway (iSG) . . . . . . . . . . . . . . . . 15
2.4 Packet Data Network Elements . . . . . . . . . . . . . . . . . . . . . 15
2.4.1 Mobile Data Gateway (MDG) . . . . . . . . . . . . . . . . . . 15
2.4.2 iDEN Home Location Register (iHLR) . . . . . . . . . . . . . 15
2.4.3 Billing Accumulator (BA) . . . . . . . . . . . . . . . . . . . . 16
2.4.4 Home Agent (HA) . . . . . . . . . . . . . . . . . . . . . . . . 16
2.5 Operation and Maintenance Center (OMC) . . . . . . . . . . . . . . . 16
2.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Interconnect Call Processing 17

3.1 Interconnect Architecture . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.1 Establish Radio Link . . . . . . . . . . . . . . . . . . . . . . . 18
3.1.2 Route digital voice packets . . . . . . . . . . . . . . . . . . . . 18
3.1.3 VSELP/Mobis - PCM/SS7 conversion . . . . . . . . . . . . . 18
3.1.4 Other network routing . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Interconnect call procedure . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2.1 Inbound Call Initiation . . . . . . . . . . . . . . . . . . . . . . 19
3.2.2 Outbound Call Initiation . . . . . . . . . . . . . . . . . . . . . 20
3.3 Interconnect call types . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3.1 Mobile to other network (PSTN) . . . . . . . . . . . . . . . . 21
3.3.2 Other Network (PSTN) to Mobile . . . . . . . . . . . . . . . . 21
3.3.3 Mobile to Mobile . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4 Interconnect Calling Features . . . . . . . . . . . . . . . . . . . . . . 22
3.4.1 Call Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4.2 Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4.3 Call Hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.4 No Answer Transfer . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4.5 Busy Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
CONTENTS ix

4 Dispatch Call Processing 24

4.1 Dispatch User Organization . . . . . . . . . . . . . . . . . . . . . . . 24
4.1.1 Fleet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1.2 Talkgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1.3 Fleet Member . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Dispatch Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2.1 Establish Radio Link . . . . . . . . . . . . . . . . . . . . . . . 26
4.2.2 Route digital voice packets . . . . . . . . . . . . . . . . . . . . 26
4.2.3 Duplicate packets . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3 Dispatch Call Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.4 Dispatch Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.1 Private Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.4.2 Group Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.4.3 Call Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.4.4 MS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.4.5 Emergency Call . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5 Packet Data Subsystem 35

5.1 Mobile Data Gateway (MDG) . . . . . . . . . . . . . . . . . . . . . . 35
5.2 Billing Accumulator (BA) . . . . . . . . . . . . . . . . . . . . . . . . 37
5.3 Packet Data Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.3.1 Dispatch Registration . . . . . . . . . . . . . . . . . . . . . . . 37
5.3.2 Packet Data Registration . . . . . . . . . . . . . . . . . . . . . 38
5.3.3 Mobile-IP Registration . . . . . . . . . . . . . . . . . . . . . . 39
5.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6 DAP Testing 41
6.1 Testing Using Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.2 Testing Using Automation Tool . . . . . . . . . . . . . . . . . . . . . 43
6.2.1 CTHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.2.2 Test Case Development . . . . . . . . . . . . . . . . . . . . . . 44
6.2.3 Normal Call Scenario . . . . . . . . . . . . . . . . . . . . . . . 46
6.2.4 Reconnection Request . . . . . . . . . . . . . . . . . . . . . . 46
6.2.5 Different Bandwidth Allocation . . . . . . . . . . . . . . . . . 46
6.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7 Conclusion and Future Work 48

7.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.2 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

References 50
List of Figures

1.1 Voice Packet Interleaving[1] . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 iDEN Network Infrastucture[1] . . . . . . . . . . . . . . . . . . . . . . 8

2.2 Interconnect Network Elements . . . . . . . . . . . . . . . . . . . . . 9
2.3 Dispatch Network Elements . . . . . . . . . . . . . . . . . . . . . . . 12

3.1 Interconnect Call Flow[1] . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1 Intra-DAP Private Call Flow[6] . . . . . . . . . . . . . . . . . . . . . 29

4.2 Inter-DAP Private Call Flow[6] . . . . . . . . . . . . . . . . . . . . . 30
4.3 Inter-Urban Private Call Flow[6] . . . . . . . . . . . . . . . . . . . . . 31
4.4 Group Call Flow[6] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5.1 Packet Data Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.2 Dispatch Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.3 Packet Data Registration . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.4 Mobile-IP Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6.1 Lab Monitor Flow Chart . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.2 DAP connection with CTHA . . . . . . . . . . . . . . . . . . . . . . . 44
6.3 Registration of MS[6] . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

x
Chapter 1

Introduction

The demand of wireless communication has grown as people have become more mo-
bile. Also, users were looking for a services offered by a single provider. The outgrowth
of the wireless communications market has produced vast opportunities to enhance
and improve the communications between individuals. In order to meet this growing
rate it is essential to optimize Radio Frequency (RF) spectral resources and provide
ever-increasing services.
As a part of ongoing efforts to support the outgrowth in wireless communication,
iDEN (Integrated Digital Enhanced Network) technology was developed by Motorola
Inc. in 1994. It is a highly innovative, cutting-edge system of technologies to create an
ideal, complete wireless communication system for todays fast-paced, busy lifestyle.
Advanced capabilities bring together the features of dispatch radio, full-duplex tele-
phone interconnect, short messaging service and data transmission.

1.1 iDEN Overview

iDEN is a telecommunication system which combines the digital dispatch and digital
interconnect into a single system. To support the increase in wireless services while
making best use of available resources, the iDEN system capitalizes on the fact that
communications can be:

1
CHAPTER 1. INTRODUCTION 2

Half-duplex : where one user is transmitting (talking) and other users are re-
ceiving (listening)

Full-duplex : where there is an open bi-directional link that allows full two-way
communication

Many times communication does not require a full-duplex link. Messaging, paging,
some forms of data communication and structured voice communication are or can
effectively operate in half-duplex mode. Traditional telephone conversations and more
intensive data links require full-duplex operation. By utilizing both full and half-
duplex operations, iDEN allows much of the voice traffic to be run in half-duplex
mode while providing full-duplex functionality when required.

1.2 iDEN Features

iDEN network provides many services and features to its subscribers and users. These
services and features are provided through three main services: Interconnect, Dispatch
and Packet Data.

1.2.1 Interconnect

This digital cellular service is used if call is made across the land-line network. So, it
provides basic mobile-mobile, mobile-land and land-mobile as well as supplementary
services. It is full duplex service that means user can talk and listen at a time.

1.2.2 Dispatch

It is a service which allows groups of users to communicate easily and quickly with
each other at a same time. Users can communicate one on one or in group. Dispatch
service is half duplex that means user can either talk or listen at a time.
CHAPTER 1. INTRODUCTION 3

1.2.3 Packet Data

The iDEN packet data is a data-internetworking network that is integrated with the
existing wireless iDEN system. It is designed to enable computers that currently
exchange data through wired networks to exchange data via the wireless Radio Fre-
quency (RF) medium. The packet data subsystem supplys Internet Protocol (IP)-
based network to their subscribers to access either the Internet or their own networks.

1.3 System Organization

To support the growing need for emerging telecommunication services, iDEN system
is organized into different levels or areas. These areas are based on geographical areas
of decreasing size. These areas are described in the following setions.

1.3.1 Global

Global refers to the worldwide, multi-provider, Public Telephone Switched Network

(PSTN). The telephone services available worldwide may be accessed from the iDEN
system using Interconnect calling. When the iDEN system uses the PSTN (Intercon-
nect) system, the rules and procedures of the PSTN are used.

1.3.2 Region

A region is a large geographic area that is usually associated with more than one
market or more than one urban area. A single service provider supplies services
by regions. A service provider may have adjacent or overlapping markets that can
be linked to provide contiguous service across the areas. Regions are covered by
Interconnect and Dispatch calling.
CHAPTER 1. INTRODUCTION 4

1.3.3 Domain

A domain is an optional logical division of a region. The intent is to subdivide the

region into smaller areas based on expected usage patterns. There can be up to 50
domains assigned per region. Each domain may contain up to 254 service areas.

1.3.4 Urban

The iDEN system is divided into large geographical areas known as urbans. In most
cases, an urban is centered on a large city.

1.3.5 Service Area

A service area is formed by logically combining the contiguous coverage areas of one
or more Dispatch Location Areas (DLAs). The SA is used with the dispatch group
calls to target the area of the iDEN system thereby reducing the resources required
for that call.

1.3.6 Location Area

A location area is a logical geographical area that is based on the current location of
a SU. Each SU contains Location Area Identifiers (LAIs) used by the location area
to locate the SU for paging and call setup. The Interconnect Location Areas (ILAs)
are usually larger than Dispatch Location Areas (DLAs).

1.3.7 Cell

A cell is an area serviced by the RF propagation pattern of the antennas and a radio
of a remote tower (cell site). An EBTS (Enhanced Based Tranceiver System) may be
configured to support one or more cells. A site with one cell is known as an omni-
directional site. A site with two or more cells is known as a sectored site. Sectored
sites typically have three cells.
CHAPTER 1. INTRODUCTION 5

1.4 iDEN Key Technologies

iDEN places more users in a given spectral space compared to analog cellular and
two-way radio systems by using speech compression and Time Division Multiple Ac-
cess(TDMA). It operates on 25kHz channel and supports either three or six intercon-
nect users (phone users) per channel and either six or twelve dispatch users (push-to-
talk user) per channel.

1.4.1 Vector Summed Excited Linear Prediction (VSELP)

iDEN uses voice coder called VSELP which digitally encodes voice using a com-
pression program that changes large segments of voice into smaller segments called
packets. This increases channel efficiency by decreasing the amount of time it takes
to transmit one conversation. The voice can be compressed using two ways:

6:1 Compression: 90ms voice is compressed in 15ms voice. so it gives better

spectrum usage.

3:1 Compression: In this compression two time slots are used instead of one.
This allows 45ms voice compressed in 15ms time slots, improving overall richness
and tone of the interconnect call.

1.4.2 Time Division Multiple Access (TDMA)

TDMA allows more then one user to multiplex on a given carrier. In iDEN system
voice packets are compressed into smaller segments using VSELP. So, several segments
can be placed on the same radio frequency or channel using TDMA. The 6:1 interleave
is used for Dispatch call and 3:1 interleave is used for Interconnect call. Figure 1.1
shows the voice packet interleaving for inteconnect and dispatch service.
CHAPTER 1. INTRODUCTION 6

Figure 1.1: Voice Packet Interleaving[1]

1.5 Thesis Organization

The rest of the thesis is organized as follows.

Chapter 2, describes the different iDEN network elements which are used in three
main services: Interconnect, Dispatch and Packet Data.

In Chapter 3 the Interconnect call flow processing and different types of call flows
has been described. Dispatch call types and call flows has been described in Chapter 4.

Chapter 5, describes the packet data subsystem. The packet data registration
process and and packet data call flow has been explained in this chapter.

Different types of tools and testing methods has been explained in chapter 6. How
the tools are used for testing the system network elements has been explained in this
chapter.

Finally, in chapter 7 concluding remarks and scope for future work is presented.
Chapter 2

System Network Elements

iDEN system consists of different network elements that supports interconnect, dis-
patch and packet data services. Some of the network elements share its functionalities
and capabilities among all three services which are specified in Radio Access Network
while other elements are specific to either interconnect, dispatch or packet data ser-
vices. The iDEN network infrastucture is shown in Figure 2.1.

2.1 Radio Access Network Elements

2.1.1 Mobile Station (MS)

The Mobile Station is a end-user interface to the network. It provides the subscriber
physical access to the iDEN system. A Mobile Station can be a phone, modem, pager,
mobile transceiver or similar device that is registered and compatible with the iDEN
system. It is also know as Subscriber Unit (SU).

2.1.2 Enhanced Based Transceiver System (EBTS)

EBTS provides the radio frequency link between land network and MSs. It contains
radio equipments and the control equipments. It has an integrated Site Controller
(iSC), one or more Base Radios (BR) and RF distribution system (RFDS). The BR

7
CHAPTER 2. SYSTEM NETWORK ELEMENTS 8

Figure 2.1: iDEN Network Infrastucture[1]

is responsible for control signaling and user voice/data. iSC performs all control and
synchronization functions for the EBTS. It is also called as Access Control Gate-
way(ACG). The RFDS connects the base radio to RF antennas.

2.1.3 Digital Cross Connect Switch (DCS)

The Digital Cross Connect Switch (DCS) is a standard programmable telephone in-
dustry device that provides a transport system within the iDEN network. It is the
central connecting point for all T1 and E1 links in iDEN network and is used to sepa-
rate the information on the T1 or E1 links and route the data to the correct network
element. For Interconnect calls, the DCS cross connects interconnect voice packets
to the BSC/iBSC. The BSC/iBSC coordinates the movement of packets between the
DCS and MSC. For Dispatch calls, the DCS connects dispatch voice packets to the
CHAPTER 2. SYSTEM NETWORK ELEMENTS 9

MPS. The MPS coordinates the movement of voice packets between EBTS and APD.

2.2 Interconnect Network Elements

Figure 2.2 shows the different network elements used in the interconnect system.

Figure 2.2: Interconnect Network Elements

CHAPTER 2. SYSTEM NETWORK ELEMENTS 10

2.2.1 iDEN Base Site Controller (iBSC)

iDEN base site controller manages and controls call processing and routes the inter-
connect data between EBTS sites and other network. By function, iBSC divided in
two shelves. Those are:

Base Site Controller- Control Processor (BSC-CP): It controls the radio

site and performs call routing and protocols translations. EBTS is connected
to the Mobile Switching Center (MSC) using BSC-CP.

Base Site Controller- Transcoder (BSC-XCDR): It converts the voice

packets used in radio link in to the Pulse Code Modulation (PCM) used by
local and interconnect public switch telephone network (PSTN).

2.2.2 Mobile Switching Center (MSC)

The Mobile Switching Center is a GSM based mobile telephone switch which provides
the interconnect services. It switches the voice and signaling traffic between iDEN
and PSTN. It also keeps track of mobile location for correct routing and billing
information.

2.2.3 Home Location Register (HLR)

It is a database of providing permanent storage of the MS subscriber records. Database

includes MS IDs and services, authentication information, location and roaming in-
formation and restriction. There is always one HLR per iDEN system.

2.2.4 Visitor Location Register (VLR)

It is a database of active visiting subscribers located in the MSC. It is always inte-

grated with the MSC and it can access the HLR to download subscriber information
when mobile is roaming.
CHAPTER 2. SYSTEM NETWORK ELEMENTS 11

2.2.5 Short Message Service (SMS)

It is the service center that accepts, stores and delivers messages up to 140 characters
to the target MS from the MSC.

2.2.6 Voice Mail System (VMS)

It enables user to receive voice mail. If the incoming call can not be completed then
the voice mail system allows the caller MS to leave the voice announcement for the
called MS.

2.2.7 Interworking Function (IWF)

The Interworking Function provides the circuit switched data services to iDEN sub-
scribers. So, it provides data rate adaption between iDEN system and land networks
which includes PSTN and Packet data network. This service enables subscribers to
connect a laptop, computer and fax device directly to their mobile subscriber unit.

2.3 Dispatch Network Elements

Figure 2.3 shows the different network elements used in the dispatch system and
packet data subsystem.

2.3.1 Dispatch Application Processor (DAP)

The Dispatch Application Processor (DAP) is responsible for the overall control and
coordination of dispatch communication service. It also maintains and tracks the
subscriber mobility and provisioning information for dispatch services.

DAP Architecture

DAP Architecture contains the DAP core module and the three objects Mobile
Application Part (MAP), Common Controller Platform (CCP) and Common
CHAPTER 2. SYSTEM NETWORK ELEMENTS 12

Agent (CA) provide services to the core[5].

Figure 2.3: Dispatch Network Elements

MAP is used to communicate between VLRs (DAP) and iHLR. It is imple-

mented in the MAVT task on the DAP and MAHT task on the iHLR. CCP
allows the application to be platform independent. So it provides an interface
between hardware/OS and the application. Thus, it provides common function-
alities for multiple applications. CA is implemented in the different network
elements of iDEN system to provide the network management. It provides the
interface between Operation and Maintenance Center (OMC) and the DAP. So,
the whole the iDEN system management is carried out by OMC and the various
CA residing on each NE.

DAP Core Architecture Modules

DAP core contains the seven architecture modules (AM) those are:
CHAPTER 2. SYSTEM NETWORK ELEMENTS 13

Account and Performance Management (APM-AM): It is used for

creating the billing information and generates the report regarding the
information. It consists of AMPT task to perform the operation.

System Control Management (SCM-AM): It controls the manage-

ment functionalities for DAP initialization and interface. To do this it
consists of SAMT, SMTT and CDDT tasks.

Configuration and State Management (CSM-AM): It provides the

integrated managements of system configuration information such as hang
timer and wait for location response period in the DAP. It also pro-
vides DAPs link state management functionalities. It consists of CFMT,
GDMT, DLMT, NSMT and WDMT tasks to do the management.

Call Processing Management (CPM-AM): It provides the overall call

control to start and maintain the voice call between MSs. It also provides
the MS tracking and paging for packet data call. To do this it consists of
four tasks: CPMT, MBMT, RRRT and SDGT.

Database Management (DBM AM): It provides the managements of

the DAP fleet or subscriber database objects. It also manages the shared
memory segments that contain the information of subscriber surveillance.
For this management it consists of LRAT, MBDT, VLRT and SPMT tasks.

Resource Management (RSM-AM): It tracks the state of external

devices such as PD (Packet Duplicator) and MDG (Mobile Data Gateway)
which DAP utilizes as servers. It consists of MRMT, P2MT, IRMT and
DRMT tasks for the tracking.

Availability Management (AVM-AM): It tracks the DAPs overall

usages. To do this it consists of DURT task.
CHAPTER 2. SYSTEM NETWORK ELEMENTS 14

2.3.2 Dispatch Visitor Location Register (D-VLR)

It is a dynamic database located in the DAP. It tracks the MS location and status
through out the iDEN region network.

2.3.3 Metro Packet Switch (MPS)

The Metro Packet Switch is responsible for switching and routing voice packet for
dispatch calls. In the case of group calls, the MPS routes the packets to and from
the Advanced Packet Duplicator (APD) to the appropriate destination.

2.3.4 Advanced Packet Duplicator (APD)

The APD provides the duplication and routing of voice packets for the Legacy iDEN
network. When a Dispatch call is initiated, the DAP sends the APD a routing table
that contains all of the targeted subscriber IDs and EBTS sites associated with each
mobile subscriber. When a Dispatch voice packet is received, the APD looks up the
call ID in the routing table and performs the necessary duplication and routing. The
APD after receiving voice packets from one site on a call, then duplicates and routes
them to the other sites on the call. Packets are transferred between the APD and
packet switches through four High-Speed Serial Interface (HSSI).

2.3.5 iDEN Dispatch Access Controller (iDAC)

The iDAC provides the routing of voice for Inter-Urban Dispatch calls across different
Urbans. The iDAC communicates with DAPs, APDs and the OMC in the same
Urban, and with remote iDACs in other Urbans. An iDEN subscriber in one Urban
area can make a Dispatch call to another iDEN subscriber in another Urban.
CHAPTER 2. SYSTEM NETWORK ELEMENTS 15

2.3.6 iDEN Surveillance Gateway (iSG)

The iSG provides law enforcement surveillance capability for the iDEN Dispatch and
Packet Data subsystems. When provisioning surveillance in the iDEN network, each
Urban has one or more pairs of iSG for redundancy. The iSG utilizes the iDEN net-
work to retrieve surveillance information, and forwards it to the appropriate Law En-
forcement Agency (LEA) where it is recorded in a Law Enforcement Monitor (LEM).
The LEM connects to the iSG through the TCP/IP network, and the surveillance
information is transmitted to the LEM.The iSG also maintains a list of which IMSI
subjects are under surveillance and what type of surveillance is being conducted.

2.4 Packet Data Network Elements

The iDEN packet data service is the subset of the dispatch subsystem. So, some of
the network elements such as DAP, APD and MPS are used in both Dispatch service
and Packet Data Service. So, the functionality of all three elements are same in both
services. The key network elements for the packet data network are described follow
and as shown in Figure 2.3.

2.4.1 Mobile Data Gateway (MDG)

MDG is an interface gateway between the iDEN network and the Internet. It helps
the subscriber to route the data packets to and from the Internet.

2.4.2 iDEN Home Location Register (iHLR)

The iHLR is the new database specifically designs for the packet data subsystem. It
is used for the transmission of the packet data. It also tracks packet data registered
MS through out the regional and national network.
CHAPTER 2. SYSTEM NETWORK ELEMENTS 16

2.4.3 Billing Accumulator (BA)

The Billing Accumulator collects the billing information for the packet data service
and generates the billing records as and when required.

2.4.4 Home Agent (HA)

Home Agent helps to route the packed data from the Internet to the correct MDG
for delivery to the correct subscriber unit. The details of all the network elements of
packet data subsystem has been explained in chapter 5.

2.5 Operation and Maintenance Center (OMC)

The Operations and Maintenance Center (OMC) is the network element management
subsystem that establishes, maintains, collects information about the network, and
presents it to the system operator. This data is used primarily to support the daily
operation of the network radio system elements and to provide the system operator
with valid information for future planning decisions. As the complexity and control
requirements of the iDEN system and its relationship to other systems increases, the
need for control and monitoring equipment also increases. It monitors all the network
elements the DAP, EBTS, BSC and any new devices added in the system.

2.6 Summary
The different network elements which are used in three different services of the iDEN
system has been explained. The network elements which are used in all three service
are explained in section 2.1. In section 2.2 the network elements used in Interconnect
system has been expained. Network elemts for Dispatch and Pachet Data system has
been explained in section 2.3 and section 2.4 respectively.
Chapter 3

Interconnect Call Processing

Interconnect calls are voice communication that utilized other provider networks.
The other networks may be either land-based or wireless. To use interconnect calling,
iDEN system must be configured for interface to the telephony network. Intercon-
nect service is based on ISDN and GSM technologies, offers high quality digital, full
duplex communication and wide verity of features such as caller ID, call forwarding,
voice mail etc. The iDEN system allows a MS to travel freely throughout the iDEN
regional network originating or receiving interconnect calls. The system tracks the
MSs location and routes calls to it. This chapter describes the fundamentals of the
Interconnect Call Processing.

3.1 Interconnect Architecture

The architecture of the interconnect system is shown in Figure 2.2 which shows the
major network elements involved in the interconnect calling. The MS sends and re-
ceives voice data. The EBTS converts the radio link to the land link and discriminates
between Interconnect and Dispatch calls. The BSC routes interconnect packets be-
tween the EBTS and MSC. The MSC determines services and location information.
It also controls and routes the calls to other providers. Following are the major steps
in an interconnect call processing.

17
CHAPTER 3. INTERCONNECT CALL PROCESSING 18

3.1.1 Establish Radio Link

The radio link is the on-air connection. This is a coordinated effort between the MS,
EBTS, BSC and MSC. The RF subsystem analyzes the MS broadcast and determines
the EBTS to host the call. The BSC routes the call setup information to MSC. The
MSC queries the HLR and VLR to determine location access, authentication and
service availability. The EBTS establishes and maintains the radio link. This includes
coordination of handoff to another EBTS if the MSs location indicates another EBTS
has better radio link quality.

3.1.2 Route digital voice packets

Once the radio link is established, the EBTS discriminates between a dispatch call
and an interconnect call. The DCS will cross-connect interconnect voice packets to
iBSC. The iBSC coordinates the movement of packets between the DCS and MSC.
iBSC re-routes calls to another EBTS on handoff. Control of the link between iBSC
and MS use the Mobis protocol. Control of the iBSC/XCDR complex and the MSC
link uses SS7 routing and messaging.

3.1.3 VSELP/Mobis - PCM/SS7 conversion

The VSLEP compression at the MS is converted to standardize PCM for use on

other networks by the iBSC/XCDR. The iBSC is also the bridge between the Mobis
protocol link and the PCM SS7 link.

3.1.4 Other network routing

Once the radio link is established, the connection request is processed by the MSC
databases for other provider network routing. The MSC uses SS7 routing, messaging
and trunking to cross connect the voice data packets to the appropriate other provider
network.
CHAPTER 3. INTERCONNECT CALL PROCESSING 19

3.2 Interconnect call procedure

The basic steps involved in a telephone interconnect can be summarized by the
following and it is more fully illustrated in Figure 3.1.

Figure 3.1: Interconnect Call Flow[1]

3.2.1 Inbound Call Initiation

When the call is originated from MS to PSTN then its called a inbound call. The
inbound call is from iDEN network to other network. Following steps show how
inbound call established.

Send Random Access Protocol (RAP) on primary control channel

Mobile gets dedicated control channel assigned

Authentication (optional)
CHAPTER 3. INTERCONNECT CALL PROCESSING 20

Call setup transaction

Get assigned to a traffic channel

Voice conversation

Call termination request on associated control channel

Channel released

3.2.2 Outbound Call Initiation

When the call is originated from the other then iDEN network then its called a
outbound call. The outbound call is from PSTN to MS of iDEN network. Outbound
call initiation steps has been shown below[4].

Locate MS by last known Inteconnect Location Area(ILA)

Page MS on primary control channel of all sites of ILA.

RAP on primary control channel

Get dedicated control channel assigned

Authentication (optional)

Call setup transaction

Get assigned to a traffic channel

Voice conversation

Call termination request on associated control channel

Channel released
CHAPTER 3. INTERCONNECT CALL PROCESSING 21

3.3 Interconnect call types

Mobile Stations on the iDEN system can complete Interconnect Call with other
providers networks in three basic ways:

3.3.1 Mobile to other network (PSTN)

MS sends a service request to the EBTS when the call is initiated. The EBTS/iBSC/
HLR identifies an interconnect call and routes the request to the MSC through the
iBSC. When MSC receives the service request, it queries the HLR and VLR for service
access, service availability and MS authentication. When authentication of MS is
complete, the iBSC cross connects the RF channel to the land-based circuit as soon
as it is assigned by MSC. The MSC assigns the trunk according to the provisioning
of the networks. The MSC then connects the iBSC land circuit to the PSTN trunk.
When the connection to the PSTN is complete, the remote PSTN will request that
the local MSC transmit the dialed digits for the call. The remote PSTN will verify
the service. The MSC will send a connect message to the MS that allows the MS to
receive and transmit voice frames.

3.3.2 Other Network (PSTN) to Mobile

When an incoming call is received at MSC in SS7 protocol, a channel to the remote
PSTN is allocated and the dialed number is received by MSC. The MSC will query
the HLR and VLR database to verify the dialed number. The MSC will locate the MS
using the Interconnect Location Area(ILA) in the VLR to page the MS. The ILA is
used by iBSC to route the call to the most likely set of EBTSs. The MSC will wait for
the MS to respond to the page. If the MS or resources are unavailable, the MSC will
generate the appropriate status return to the remote PSTN (busy or out-of-service).
If the MS and resources are available, the MSC will connect the external trunk to
the controlling iBSC. The iBSC will connect the PCM/SS7 link with the appropriate
EBTS. The EBTS will establish the radio link, allocate a radio channel and transmit
CHAPTER 3. INTERCONNECT CALL PROCESSING 22

a hail (ring the phone). When the user responds, the iBSC/XCDR converts the PCM
voice packets to the VSLEP packets used by the radio link. The DCS and iBSC
completes the cross connect between the radio link and the other provider land-line
to complete connection of the call.

3.3.3 Mobile to Mobile

Mobile to mobile calls are set up in the same manner as a mobile to land calls. The
MSC call routing and translation tables recognize that the call can be completed
within the iDEN system and a iBSC to iBSC connection via the MSC switching
matrix is established. This arrangement allows transcoder by-pass to operate and
thus reduce audio delay between the MS involved in the call.

3.4 Interconnect Calling Features

3.4.1 Call Waiting

Call waiting works just the same way as available in home telephone. When Call
waiting is activated, a subscriber engaged on a call will hear an alert tone and see
a visual display indicating that there is an another call waiting. The user has the
option of choosing the new call or staying with the current call.

3.4.2 Call Forwarding

Call forwarding allows a call initially sent to a subscriber to be redirected to a different

subscriber. Unconditional Forward All Calls means simply that all calls sent to that
subscriber will be forwarded.
CHAPTER 3. INTERCONNECT CALL PROCESSING 23

3.4.3 Call Hold

Call hold allows the mobile user to place an active call on hold and originate another
call, retrieve a currently held call or answer a call being held in the call waiting mode.

3.4.4 No Answer Transfer

Two forms of No Answer Transfer are provided: not available and no reply. Call
forwarding on a not available condition occurs when the MS does not answer the
page from the MSC. In this instance, the call is forwarded to the number designated
as the forward-to number. Call Forwarding No Reply occurs when the MS unit is
available but the user opts not to answer the call. This feature provides a forward-to
directory number to which the calling partys call is rerouted.

3.4.5 Busy Transfer

Busy transfer forwards an incoming call to another directory number when the user
is engaged on another call. The ability of the user to originate calls is not affected
while this feature is active.

3.5 Summary
At the starting introduction of interconnect call processing has been given. In section
3.1 major call processing steps of the interconnect system has been explained. The
call procedure from mobile to PSTN has been explained in section 3.2. Interconnect
call types and features are explained in section 3.3 and section 3.4 respectively.
Chapter 4

Dispatch Call Processing

Dispatch calls are voice communication that use the half-duplex Push-To-Talk (PTT)
form of communication. This type of call does not use other provider networks except
as transport facilities. Some iDEN systems are implemented as dispatch only. As
dispatch only, the interconnect portion of the system is not installed and cannot be
used. So, Dispatch is the radio service that allows two-way communication between
users using the same system. Based on two-way trunking, dispatch allows groups of
users or individuals to communicate quickly and easily with each other at the same
time. Users can communicate one-on-one or in larger groups like conference setting.

4.1 Dispatch User Organization

Dispatch services differ from the interconnect service. It is designed to support the
business communication needs of work in groups who need to communicate directly or
in with the whole groups. So, to achieve this requirement dispatch users are organized
differently from interconnect which has been described in following subsections.

24
CHAPTER 4. DISPATCH CALL PROCESSING 25

4.1.1 Fleet

Fleet is the highest level of dispatch user organization. Fleets consist of larger number
of dispatch user that can communicate with each other individually of in group. Each
fleet is assigned a fleet ID unique to that specific group.

4.1.2 Talkgroup

Talkgroup is next level of dispatch user organization. These are the functional groups
within a fleet. It is identify by talkgroup identifier. Fleet members are authorized to
use the specific talkgroups that are relevant to their job needs. Fleet members can be
switched between the talkgroups but, can communicate only one talkgroup at a time.
One fleet member is always the dispatcher and it is the member of all talkgroups.
Others members are organized based on functions, tasks and other relevant methods.

4.1.3 Fleet Member

Each subscriber unit has an ID called fleet member identifier which is the lowest level
of the user organization. This ID is used to target the specific subscriber within that
fleet. Individual calls between the fleet members are always half duplex. When an
individual call is placed, the individual fleet member ID is displayed.

4.2 Dispatch Architecture

The architecture of the dispatch system is shown in Figure 2.3 which shows the
major network elements involved in the dispatch calling. The MS sends, receives
voice and displays data. The EBTS converts the radio link to the land network link
and discriminates between Dispatch, Packet Data and Interconnect calls. The MPS
routes dispatch call voice packets and packet data. The DAP determines service
availability and location information. The APD duplicates voice packet that need
CHAPTER 4. DISPATCH CALL PROCESSING 26

to be sent to multiple MSs in group calling. The following are the major steps in a
typical dispatch call

4.2.1 Establish Radio Link

The radio link is the on-air connection. The radio link is a coordinated effort between
the MS, EBTS, MPS and DAP. The EBTS/DCS/MPS complex routes the call setup
information to the DAP. The DAP queries the D-HLR and D-VLR to determine
service access, authentication, and service availability. The EBTS establishes and
maintains the radio link on the RF control channels.

4.2.2 Route digital voice packets

Once the radio link is established, the EBTS discriminates between an interconnect
call and a dispatch call. The DCS will cross-connect dispatch voice packets to the
MPS. The MPS coordinates the movement of packets between the EBTS and DAP.
The MPS re-routes calls to another EBTS if the MS reconnects. If more than one
called MS is involved (group call) the MPS routes the voice packet to the DAP and
Packet Duplicator to be copied. The copied packets are routed to the appropriate
EBTS as determined by the call type.

4.2.3 Duplicate packets

For Dispatch group calls the VSELP voice packets are routed to the Packet Duplicator
where they are copied and applied to the appropriated link by the MPS. The DAP
controls call routing and coordinates the services. The MPS handles the timing and
routing of the voice packets.

4.3 Dispatch Call Procedure

The various steps of dispatch call are summarized as follow:
CHAPTER 4. DISPATCH CALL PROCESSING 27

a. Dispatch call is requested via PTT activation. The call request packet is routed
to the DAP. The DAP recognizes the MS units group affiliation and tracks the
group members current location areas.

b. The DAP sends location requests to each group members location area to obtain
current sector/cell location.

c. The MS units in the group respond with current sector/cell location.

d. The DAP instructs the originating EBTS and the PD with packet routing in-
formation for all group members.

e. Call voice packets are received by the PD, replicated and distributed to the
groups end nodes.

4.4 Dispatch Call Types

4.4.1 Private Call

The private call allows private conversation between two individuals. So, it is one-to-
one call. To make a private call user has to select the fleet member ID of the target
member which is stored in the unit. Other members of the fleet and group are not
involved in conversation. The initiating MS select the target fleet member ID and
press the talk button on the unit. The request for the service is send over the radio
link control channel to EBTS then to DAP.
During call setup, DAP validates initiating MS, the request and the target MS
(Authentication). After validation, DAP sends location request to target MS. If the
recourses are not available of the two sides then call is queued. If the recourses are
available and the target is available then a call establishment indicates to the initiator
that the target has been located and is ready for the call. The target MS activates
the audio. The initiating MS fleet member ID is sent to the target MS and will be
displayed on the target MS unit if it is programmed for that.
CHAPTER 4. DISPATCH CALL PROCESSING 28

During the conversation hang time is provided. After each transmission, a Fixed
Network Equipment (FNE) maintains the call for the hang time to allow either user
time to respond. If at any time during the process, the MS (initiating or target) does
not respond then the FNE disconnect the channel and tears down the call. The call
hang timer is reset by each new transmission. There are three types of Private Call.

Intra-DAP Private Call: In this type of calls, only one DAP is involved for
sending the page request to target MS and controlling both MSs. Figure 4.1
shows the call flow for Intra-DAP private call.
CHAPTER 4. DISPATCH CALL PROCESSING 29

Figure 4.1: Intra-DAP Private Call Flow[6]

Inter-DAP Private Call: In this type of calls, more then one DAP is involved.
One is the targets DAP and another is originators DAP. The targets DAP
is only responsible for the target MS and forwarding registration renewals to
the originators DAP who is then responsible for controlling the call, including
paging the target MS. Figure 4.2 shows the call flow for Intra-DAP private call.

Inter-Urban Private Call: In this type of calls, an originators DAP and the
targets DAP work in tandem to setup and manage the call. Figure 4.3 shows
the call flow for Intra-DAP private call.
CHAPTER 4. DISPATCH CALL PROCESSING 30

Figure 4.2: Inter-DAP Private Call Flow[6]

4.4.2 Group Calls

Dispatch group calls allow MSs which are members of the predefined groups to com-
municate with each other using half-duplex mode. Only members of the groups can
participate in the call and any authorized member can be participate the call. The
call can be setup without all group members being available. Any group member can
leave the group at any time.
Once the group calls request come the FNE first dispatch location area of the
member and then send the page request to the members of that location area. Once
CHAPTER 4. DISPATCH CALL PROCESSING 31

Figure 4.3: Inter-Urban Private Call Flow[6]

MS responds to the page, only those cells with active MSs will have voice channels
assigned. After each transmission, FNE maintains the call for predefine hang time. If
the hang time expires, the channels are disconnects and the call is torn down. Figure
4.4 shows the sequence diagram of the group call.
There are three variations of Dispatch Group Calls which define the extent of the
area coverage of the call, they include:

Wide Area: A Wide Area Group call is routed to all active Talkgroup members
in every service area. Cells that do not contain any Talkgroup members are not
CHAPTER 4. DISPATCH CALL PROCESSING 32

Figure 4.4: Group Call Flow[6]

activated.

Local Service Area: A Local Service Area Group Call is routed to all active
Talkgroup members in the same service area. Associated dispatch stations,
regardless of their location, are included in the call.

Selected Service Area: A Selective Service Area Call is routed to all active
Talkgroup members in the selected service area that the call initiator selected.
CHAPTER 4. DISPATCH CALL PROCESSING 33

4.4.3 Call Alert

A call alert is dispatch call request. It allows caller to leave visual and audible call
alert to unattended subscriber unit so the operator sees that they have a call when
they return. All iDEN subscriber units are capable of sending and receiving call alert.
An MS(caller) initiates a call alert through the user interface by manually switch-
ing in call alert mode and then entering the target MS(called) Fleet Member ID.
The MS receives an acknowledgement(ACK) if the request is successfully delivered.
This feature display and store the initiating MS Fleet Member ID on the receiving
MS. This is used for the call back procedure. There is no need to enter the Fleet
Member ID by the receiving MS in order to respond the call alert. It can either do
the call back or clear the ID from the MS memory.

4.4.4 MS Status

This feature permits the transmission of the MS status to any other selected MS unit.
It allows the delivery of MS stats code (an 8-bit number) from one MS to other. MS
status feature is similar to call alert feature. Both are initiated through the same user
interface. Like call alert an acknowledgment is received to the MS when MS status
is successfully delivered or if failed then it returns with failure reason. The difference
between call alert and the MS status is on sending and receiving capability such as:

A call alert can be activated as send, receive or neither of them by MS.

A MS status can be activated just for send, just receive, both or neither of
them.

4.4.5 Emergency Call

An emergency call is the special case of a wide area dispatch group call. It has the
highest priority. It allows user to have priority access to iDEN resources in case
of emergency. An Emergency Call is used to alert all members of the group of an
CHAPTER 4. DISPATCH CALL PROCESSING 34

emergency initiated by a user. An emergency call is handled before any other call and
is intended to announce and open a line of communication in a dangerous situation.
The process of the emergency call is same as the dispatch group call. An Emergency
Call can also be terminated at any time by the initiator or another user with an MS
provisioned override the status.

4.5 Summary
Section 4.1 desribes the how the users are organized in case of dispatch service. In
section 4.2, major steps of dispatch call flow has been explained. The call procedure
steps has been explained in section 4.3. Dispatch call types has been brifely described
in section 4.4.
Chapter 5

Packet Data Subsystem

Packet data in iDEN network is a non voice communication service which helps the
subscriber unit to directly connect itself with an intranet, internet, extranet, Inter-
net and Virtual Private Network (VPN). The packet data system allows the service
providers to become a point-of-presence for the mobile users on the Internet. A point-
of-presence is an interface between the subscriber unit and any other communication
unit; in this case it is the Internet. [2] The infrastructure used by the packet data
subsystem is same as that used by the dispatch subsystem. If a subscriber has ac-
tivated the facility for packet data and if it is authorized for this service, then that
subscriber unit can send or receive packet data. Figure 5.1 shows the important net-
work elements of the Packet Data Subsystem of iDEN Network. [3]. The following
sections descride the network elements that are used for the functioning of the packet
data service.

5.1 Mobile Data Gateway (MDG)

The Mobile Data Gateway is the interface to the Internet and World Wide Web for
the iDEN system during the packet data operation. The MDG has the three major
functions during the packet data operation:

Gateway: It provides the secure networking routing, switching and network

35
CHAPTER 5. PACKET DATA SUBSYSTEM 36

Figure 5.1: Packet Data Subsystem

masking functions.

Home Agent: The MDG stores the Internet Protocol (IP) address of the MSs
in a Home Agent database. IP addresses are used to identify and route the data
packet through MS during packet data operation. So that the MDG works in
conjunction with the HA router to receive the forwarded packets from the home
address and distributes these packets to the MS.

Foreign Agent: It is used when the MS is in roaming. During the roaming

Foreign Agent will contact the HA and obtain the authentication, identification,
CHAPTER 5. PACKET DATA SUBSYSTEM 37

services and permission information of the MS. The MDG receives operational
information from the OMC and subscriber information from the iDEN Home
Location Register (iHLR) from the DAP.

5.2 Billing Accumulator (BA)

The main function of the BA is to:

Collect and store billing records that are produced by the MDG.

Provide an avenue for the stored billing records to be transferred to an outside

billing center.

Similar to call data records from the MSC, this information is used by the service
provider to gather usage (time and/or data transferred) and similar account informa-
tion. There are two Billing Accumulators in the Packet Data subsystem.One is the
primary BA and other is the secondary BA. Data is sent to the Primary BA, which
mirrors the billing data to the Secondary BA.If the Primary BA becomes unavailable,
the Secondary BA takes over.

5.3 Packet Data Call Flow

5.3.1 Dispatch Registration

Packet Data is subsystem of the dispatch service. So, In order to activate packet
data service, dispatch registration is required which is shown in figure 5.2. The
registration request forwared to all DAPs. All DAPs check for the IMSI (International
Mobile Subscriber Identity) of the MS in their DVLRs. Only one DAP will have that
subscriber IMSI. Only this DAP will send the registration response to the MS. Other
DAPs will reject the request which is shown in fugure 5.2
CHAPTER 5. PACKET DATA SUBSYSTEM 38

Figure 5.2: Dispatch Registration

5.3.2 Packet Data Registration

After the MS successfully dispatch registered, the pachet data registration can take
palce. The pachet data registration is shown in figure 5.3. When the packet data

Figure 5.3: Packet Data Registration

registration request sends to serving DAP, the DAP chooses a MDG to serve the
subscriber unit. DAP round robins over the available MDGs in order to distribute
CHAPTER 5. PACKET DATA SUBSYSTEM 39

the load. After that MDG send the successful status to the DAP and it will be
forwared to the MS which is shown in figure 5.3.

5.3.3 Mobile-IP Registration

In the wireless network for routing and forwarding the packet data the Internet Pro-
tocol (IP) is used. In iDEN system each subscriber has its own IP address. iDEN
system supports the Mobile IP standards that means the data can be send to other
network without changing the IP address when the mobile is roaming. So, for that
mobile IP registration is required which is shown in figure 5.4. MDG manages the

Figure 5.4: Mobile-IP Registration

overall process of Mobile IP. MDG forwareds the registration request to Home Agent
(HA). HA authenticates the subscriber based on received infromation from the MDG.
It creats the binding between subscriber IP and the COA(Care-or-Address), the IP
CHAPTER 5. PACKET DATA SUBSYSTEM 40

address of for and forwared the registration accept massege to the DAP. DAP will
forwared the message to the MS which is shown in figure 5.4. After doing registra-
tion the packet data can be send to the subscriber. Messages across the Internet are
addressed to the MDG. The MDG re-addresses the data to the specific MS. Data for
MSs that the MDG serves is accepted and the Internet Routing Information Protocol
(RIP) is removed and the data is re-assigned to the mobile IP address used by the
iDEN system.

5.4 Summary
This chapter explains the basics of the packet data subsystem of the iDEN network.
The introductory portion of the chapter explains the major network elements of this
subsystem. The sections 5.3 explain the packet data call flows and different registra-
tion process required in packet data.
Chapter 6

DAP Testing

Any system must be tested in different network environment before it is going to

be used. By doing the testing, one can know the capabilities and limitations of the
system. The different scripting languages and the test tools are used for testing the
system. Motorola, Bangalore mostly working on the dispatch service of the iDEN
system. So, the different network elements of the dispatch service are tested and
integrated under the System Integration and System Testing (SIST) team. DAP is
the most important network element in dispatch service. So, the DAP has been tested
using test cases. Test case means A set of conditions which are used for testing and
validating the different network elements which are going to be used in the system.
Test cases can be developed using the scripting tools or automation tools which is
explained in the following sections.

6.1 Testing Using Scripting

The testing of the network elements can be done using different scripting languages.
Mostly Unix and Perl are used for the testing. In this type of testing the script will
be written either in perl or unix and it will be run on particular machine which is
connected to the element which is going to be tested. As a part of the scripting,
we have written a script in unix and perl for Lab Monitoring. This lab monitor will

41
CHAPTER 6. DAP TESTING 42

check the current status of different machines situated in the lab. It is one kind of
request response technique.The process of lab monitoring shown in figure 6.1.

Figure 6.1: Lab Monitor Flow Chart

The script has been written in such a way that it first asks the IP address of
the desired machine. When the user enters the IP address local machine connects
with desired machine and it asks for login. After login, test case runs on desired
machines and machine responds to the test case. The response gets received by the
local machines. The received information which contains the status of the desired
machine has been displayed on the XML format on local machine. To make the
process user friendly, XML output file merge with GUI. Thus, user can able to view
the status of machine from web-browser. So, like this way the system can be tested
using scripting.
CHAPTER 6. DAP TESTING 43

6.2 Testing Using Automation Tool

For reliable product, testing tool should be flexible, shorter cycle time and hardware
independent. Automation tool is define as A tool which has the predefine set of
functions and commands using which the response of the different network elements
under certain condition can be tested. In automation tool, we have learned CTHA
(Componentized Test Harness Architecture) which is specially designed for testing the
functionalities of DAP by box testing team of Motorola. The details of the CTHA
tool is described in the following subsection.

6.2.1 CTHA

CTHA is a platform that allows user to compose and send messages in various format
to the DUT (Device Under Test). It also provides content and sequence validation of
responses from the DUT. CTHA is GUI (Graphic User Interface) based tool and all
the script are written in Java. CTHA provides real and simulated network elements
such as DAP, iVPU, ACG, MDG, iSG and the set of library messages by which
network elements talk to each other. CTHA includes batch mode execution which
execute multiple scripts on a single click. The same message can be run multiple times
by puting it in to loop. Also, CTHA supports inteleveing which runs the messages
in any order those are interleved. CTHA has the four browsers using which user can
creat the test case. Those are:

File Browser The file browser contains the list of files such as configration
files, log files and script file. So, it is used for finding the files.

Device Browser The device browser contains the real and simulated network
elements. So, at the time of test case development the elements are selected
from this browser.

Message Browser This browser Includes a user-customizable template mes-

sage for the inclusion of any combination of message elements.
CHAPTER 6. DAP TESTING 44

Message Element Browser This browser includes the configration informa-

tion about all the network elements.

In DAP Testing, all the devices except DAP are simulated in CTHA. Figure 6.2
shows how the real DAP is connected with the CTHA and other elements. CTHA,
iHLR Simulator and OMC simulator are runnning in different sun machines which
are known as Hammers. GPA is known as Gcom Protocol Application. It contains
the simulated ACGs which are connected with DAP using UDP and with hammers
(CTHA, iHLRsim and OMCsim) using TCP.

Figure 6.2: DAP connection with CTHA

As explained earlier that in CTHA test cases are created which are used for testing
DAP. The following subsection describes how the test cases are created in CTHA using
the example of validation of originator which is shown in Figure 6.3.

6.2.2 Test Case Development

For creating the test case, first select the network elements from the device browser
which includes real DAP, simulated DAP, simulated ACG and simulated iVPU and
place them in scenario editor. As explained in the call flow that for the validation,
the originator MS first sends the registration request to the originator DAP which
CHAPTER 6. DAP TESTING 45

is the real DAP. So, pick the registration request message from the message browser
and draw from simulated ACG to real DAP. This message contains the information
about the MS like IMSI of MS, location area identifier, fleet ID etc. In response to
this message the user is expecting the authentication request message from the DAP
as described in the call flow. So, pick the authentication request message from the

Figure 6.3: Registration of MS[6]

message browser and draw from real DAP to simulated ACG. If DAP sends the same
message as per the user expectaion then we can say that the DAP is working properly
otherwise there is a problem in DAP. So like this way the test cases are created in
CTHA by using the different types of messages. For the three types of call scenario
the test cases has been designed. which has been detalied describe in the following
subsections.
CHAPTER 6. DAP TESTING 46

6.2.3 Normal Call Scenario

The test case for the normal call scenario has been designed in such a way that it
contains the same call flow which has been explained in the chapter 4. Test case
contains the registration of MS, paging request, trasfer of audio packets and the
target release messages.

6.2.4 Reconnection Request

If the call is going on either in inter-DAP or Intra-DAP and the MS is roaming from
one cell to another cell in the same urban area then MS may lost the connection. At
that time MS sends the pc reconnect request to the ACG for establishing the call
again. ACG converts this request to registration renewal request and forward to the
originator DAP if the call is for intra-DAP. If the call is for inter-DAP then ACG
sends the registration renewal request to target DAP and target DAP forward the
reconnect request to the originator DAP. Test case for this reconnect call scenario has
been created and tested in CTHA.

6.2.5 Different Bandwidth Allocation

iDEN supports the different types of bandwidths which includes standard 800Mhz
band called primary band and extended 800Mhz band. As per the band allocation,
three types of test case have been created.

In this test case originator DAP has allocated extended 800 MHz band and also
MS has allocated the extended 800MHz. Then MS sends the pc request info
message to originator DAP with band allocation type extended 800MHz. As
originator DAP has the same band type it sends page request with the band
allocation type extended 800MHz. Hence, the private call starts successfully.

In this test case originator DAP has allocated extended 800 MHz band and MS
has allocated the primary 800MHz. Then MS sends the pc request info message
CHAPTER 6. DAP TESTING 47

to originator DAP with band allocation type primary 800MHz. As originator

DAP supports the primary 800MHz band because it has the extended 800MHz.
So, originator DAP sends page request and the private call starts successfully.

In this test case originator DAP has allocated primary 800 MHz band and
MS has allocated the extended 800MHz. Then MS sends the pc request info
message to originator DAP with band allocation type extended 800MHz. As
originator DAP supports the primary 800MHz band it sends page request with
band allocation type primary 800MHz So, MS change its band type and sends
the pc page response with band allocation type primary 800MHz. Hence, the
private call starts successfully.

6.3 Summary
The testing tool of DAP has been explained. The scripting tool has been explained in
section 6.1. The automation tool has been explained in section 6.2. Automation tool
CTHA has been explained in subsection 6.2.1. How the test case created in CTHA
has been explained in subsection 6.2.2.
Chapter 7

Conclusion and Future Work

7.1 Conclusion
The aim of this is to give brief overview of the new wireless technology, iDEN which
is a Motorola complete communications system that users can hold in their hand.
Interconnnect, dispatch and packet data services show how iDEN system differ from
the other wireless technologies. DAP testing shows how the network elements has
been tested using the different tools and scripting languages.

48
CHAPTER 7. CONCLUSION AND FUTURE WORK 49

7.2 Future Work

In Future, more testcases can be developed for network elements testing. Different
types of tools can be learned. Using these tools the packet data network elemnts and
the call flows will be tested.
References

[1] Motorola Inc., iDEN Technical Overview, August, 1996.

[2] Motorola Inc., iDEN System Overview and Functional Description, System Re-
lease 18.0, August, 2010.

[3] Motorola Inc., iDEN System Overview and Functional Description, System Re-
lease 17.0, September, 2008.

[4] Motorola Inc., iDEN System Overview and Functional Description, System Re-
lease 16.0, October, 2007.

[5] Motorola Inc., iDEN Tandem DAP Software Architecture, System Release 13.0,
November, 2009.

[6] Motorola Inc., Call Scenarios for Dispatch Calls, May, 2004.

50