APT Subsystem: Objectives

APT Subsystem
Chapter 5
This chapter is designed to provide the student with the

knowledge of BSC APT subsystems.
OBJECTIVES:
Upon completion of this chapter the student will be able to:
• name the subsystems in APT-210 09

• name the most important block groups in the subsystems
• understand diagrams describing block interaction
CME 20/CMS 40 BSC Operation & Maintenance
t io
e n na
lly
t
In
Bl n
a
k
EN/LZT 123 3330 R1B

5 APT Subsystem
5 APT Subsystem
Table of Contents
Topic Page
GENERAL..........................................................................................167
RADIO CONTROL SUBSYSTEM (RCS)...........................................168

BG-CELL.....................................................................................................................168
BG-TRH ......................................................................................................................168
BG-CPR ......................................................................................................................169
BG-RCQS ...................................................................................................................169
RADIO OPERATION & MAINTENANCE SUBSYSTEM (ROS) ........170

BG-BSSAP..................................................................................................................170
BG-ABIS .....................................................................................................................171
BG-RECTRA...............................................................................................................171
BG-SUPP....................................................................................................................172
BG-TRANSM ..............................................................................................................172
BG-TRXT ....................................................................................................................173
TRANSCEIVER ADMINISTRATION SUBSYSTEM (TAS)................173

TAS-C FUNCTIONS .......................................................Error! Bookmark not defined.
LINK HANDLING SUBSYSTEM (LHS) .............................................173
STATISTIC AND TRAFFIC MEASUREMENT SUBSYSTEM ...........174

STS FUNCTIONS .......................................................................................................175
DATA FLOW IN STS ..................................................................................................176
MEASUREMENT DATABASE....................................................................................177
MEASUREMENT REPORT GENERATOR ................................................................189
MEASUREMENT REPORT FILE OUTPUT, STANDARD FORMAT .........................191
MEASUREMENT REPORT TIMETABLE...................................................................192
OPERATIONAL INSTRUCTIONS ..............................................................................193
GUIDELINE.................................................................................................................195
EN/LZT 123 3330 R1B –i–

BASIC INTERNAL CALL HANDLING...............................................202

PAGING ......................................................................................................................203
IMMEDIATE ASSIGNMENT .......................................................................................203
ASSIGNMENT ............................................................................................................205
HANDOVER ON A DEDICATED SIGNALING CHANNEL .........................................215
CLEAR OF A TRAFFIC CHANNEL ............................................................................215
CLEAR OF A DEDICATED SIGNALING CHANNEL..................................................216
– ii – EN/LZT 123 3330 R1B

5 APT Subsystem
GENERAL
This module describes the source system APT 210 09 which is
used in BSC. APT is divided into subsystems in accordance with
the AXE 10 hierarchical structure and handles traffic and
associated operation and maintenance functions. Each
subsystem is divided into a number of function blocks with each
block consisting of a number of function units, hardware or
software. Subsystem grouping has taken into account the desire
to minimize the number of subsystems affected by existing and
future functional requirements. Systems in service can be
reconfigured to accommodate new requirements by adding or
modifying blocks in the various subsystems without reallocating
loaded blocks. Each block can be replaced in an exchange while
the switch continues processing.
APT hardware handles simple routine functions whereas the

more complex functions are dealt with by the software. Software
is stored and executed in the control system APZ. This applies
to regional, support, and central software. Regional software
performs routine, high-capacity requirement functions (handled
by the Regional Processor Subsystem (RPS) in APZ). Central
software performs complex executive functions of the lower
frequency (handled by the Central Processor Subsystem (CPS)
in APZ). Support software performs input and output of data and
programs (handled by the Support Processor Subsystem (SPS)
in APZ).
The BSC consists of seven APT subsystems and an APZ.

Function blocks in the CCS subsystem and Group Switching
Subsystem (GSS) are not described in this module because they
are part of the general AXE subsystems.
RCS
ROS GSS TAS CCS
STS LHS
APT
Figure 5-1. APT subsystems
EN/LZT 123 3330 R1B – 167 –

RADIO CONTROL SUBSYSTEM (RCS)

The RCS controls the radio network, performs connection
control and controls the signaling terminal towards the BTS. It is
divided into four block groups with each block group holding a
number of functionally related blocks. The block groups are:
BG - CPR BG - CELL BG - TRH BG - RCQS
RCS
Figure 5-2. Logical structure of the RCS
BG-CELL
BG-CELL handles administration of the radio network, system
information, configuration of cells in the network and traffic
handling of logical channels. It also handles the BTS terminated
part of level 3 messages between the BSC and BTS.
BG-TRH
BG-TRH owns the hardware Transceiver Handler Board
(TRHB) and is responsible for setting up a semi-permanent
connection between the TRH device and the A-bis ETC through
the GS. Because the TRHB is connected to the GS it must be
treated as a Switching Network Terminal (SNT). Each 64-
kbps link connected to a TRH device is associated with a TRH
device individual. Devices are allocated as physical connections
for level 2 signaling between the BSC and BTSs. The level 2
protocol used is LAPD which is slightly modified for use in the
GSM specified mobile telephony system.
– 168 – EN/LZT 123 3330 R1B

5 APT Subsystem
BG-TRH handles multiplexing of level 3 messages towards the

BTS or MS and level 3 message distribution from the BTS or
MS. Messages received on a logical channel containing the
message element “Channel Number” are forwarded to BG-
CELL. Some counters for the Traffic and Event Measurement
function in the RCS are implemented in BG-TRH. All other
blocks in BG-TRH consist of CP software only. The RP
software units are located in the type of regional processor
called Regional Processor type Device (RPD). The RP units
are further structured below the unit level into processes and
modules.
BG-CPR
All blocks in BG-CPR consist of CP software only. BG-CPR
owns the connections (both signaling and traffic) between the
MS, BSC, and MSC. Within these blocks most of the GSM
signaling towards the MS and MSC is handled according to
GSM recommendations 04.08, 08.08 and 08.58 respectively.
The block group also handles the speech and data connections as
well as data for established signaling and traffic connections.
The events in the function Traffic and Event Measurement in the
Radio Network appear mainly in BG-CPR.
BG-RCQS
BG-RCQS performs radio connection quality supervision on the
logical channels and contains functions for spotting undefined
neighboring cells. BG-RCQS consists of a data storing block
and a number of command receiving blocks for RCQS specific
cell and BSC data. Some of the counters for Traffic and
Measurement are also implemented.
EN/LZT 123 3330 R1B – 169 –

RADIO OPERATION & MAINTENANCE SUBSYSTEM (ROS)

The ROS controls the transmission interfaces to the MSC and
BTS and provides operation and maintenance functions for the
BSC. The ROS is divided into three block groups with each
block group holding a number of functionally related blocks
within the RCS. The block groups are:
BG - BSSAP BG - ABIS BG - RECTRA BG - SUPP BG - TRANSM BG - TRXT
ROS
Figure 5-3. Logical structure of ROS.
BG-BSSAP
BG-BSSAP is responsible for the A-interface which handles the
trunk of the A-interface. This includes interfacing the SCCP
layer in CCS, distributing messages to/from CCS, and providing
for transmissions to the MSC. BG-BSSAP is the owner of the
speech/data path (DIP) to the MSC. The subfunction block
RALT manages the main part of the Handling of RALT Devices
function in the BSC. RALT informs the MSC of all manual or
automatic blocked A-interface devices in the BSC. RALT also
manages part in the following functions:
• Administration of Circuit Identity Code in BSC

• Administration of Device Data
• Administration of Exchange Data for Pre-Post Service
• Connection Release
• Blocking Supervision
• Seizure Supervision
– 170 – EN/LZT 123 3330 R1B

5 APT Subsystem
The subfunction block ET handles the main parts of the EM/CM

Handling in SNT Owning Blocks and Maintenance of Switching
Network Terminal functions. It also plays an important part in
the administration of SNT in BSC and fault and quality
supervision of the DIP functions. ET owns the ETCs (HW).
The subfunction block DIPST handles the main part of the fault
supervision, quality supervision and administration of DIP
functions. RABDI handles the main part of the BSSAP Message
Distribution function and also plays an important part in the
Administration of Destination Point Code and Network
Indicator functions.
BG-ABIS
BG-ABIS is responsible for the A-bis interface which handles
trunks of the A-bis interface. BG-ABIS owns the speech/data
path (DIP) to the BTS. The subfunction block RBLT handles the
main part of the Handling of RBLT Devices function in the BSC
and also plays an important part in the Administration of Device
Data and Administration of Exchange Data for Pre-Post Service
functions. Trunk devices are provided for signaling connections
to the TRUs (LAPD connections) and for speech/data
connections (for subscribers).
The subfunction block ET handles the main part of the EM/CM

Handling in SNT Owning Blocks and Maintenance of Switching
Network Terminal functions. ET also plays an important part in
the Administration of SNT in BSC, Fault Supervision of the
DIP, and Quality Supervision of DIP functions. ET owns the
ETCs (HW). DIPST handles the main parts of fault supervision,
quality supervision and adminstration of DIP functions.
BG-RECTRA
BG-RECTRA handles recording and tracing functions for the
BSC.
EN/LZT 123 3330 R1B – 171 –

BG-SUPP
BG-SUPP provides support and service to the different
subsystems in the BSC. These functions include:
• Processor and Exchange Input Load Measurement

• Load Control
• Exchange Input Load Observation
• Exchange Input Load Supervision
• Processor Load Observation
• Reading of Processor
• Exchange Input Load
• Handling command access for cell and radio network data
and BSC Unique Function Codes
• Translation Functions
• Semipermanent Connections
• Time Table
BG-TRANSM
BG-TRANSM handles commands for SNT, DIP, and device
functions for the BSC. These functions include:
• DIP Administration
• DIP Fault Supervision
• DIP Quality Supervision
• Exchange Data for Pre-Post Service Administration
• Manual Blocking and Deblocking of Devices
• Blocking Supervision of Devices
• Reading of Device State Information
• Circuit Identity Code in BSC Administration
• Administration of Destination Point Code and Network
Indicator in BSC
• Device Data Administration
• Access Function
• Command access for exchange data
– 172 – EN/LZT 123 3330 R1B

5 APT Subsystem
• SNT Administration
• Switching Network Terminal Maintenance
BG-TRXT
BG-TRXT handles the main parts of the TRXT function,
Common Administration and Maintenance. This includes:
• Supervision of Transceivers
• Administration and Supervision for Periodic Tests and
Automatic Supervision
• Common Administration and Maintenance
TRANSCEIVER ADMINISTRATION SUBSYSTEM (TAS)

TAS is structured into eight functional parts called Sets of Parts
(SoP). These SoPs include the following:
RCS ROS
TAS
A C C D L S T T
D O O A O U E R
M M N T A P S A
F A D T
Figure 5-4. Interfaces between TAS and other subsystems.
Administration of Managed Objects (ADM)
ADM handles the commands that bring MOs into operation. It

starts by defining MOs, bringing them into service and finally
manually deblocking the them.
BTS Communication (COM)
COM establishes and maintains communication with the BTS.

It includes establishment and recovery of signaling and speech
and data links towards the BTS. It also handles the sending and
receiving of O&M Layer 3 messages towards the BTS.
EN/LZT 123 3330 R1B – 173 –

Configuration (CONF)
CONF matches the configuration requirements provided by RCS

to the available equipment and then maintains and updates this
configuration based on configuration requirement changes
and/or equipment status changes.
Data and Structure Handling (DATA)
DATA is the central part of TAS. It acts as a coordinator within

the susbsystem. It handles priorities between different activities
and controls the different dependencies between MOs. In
addition, it coordinates start/restart and recovery of MOs. All
data concerning MOs is stored and maintained by one MO data
owner per MO type.
BTS Loading (LOAD)
LOAD performs the loading of software packages from the BSC

to the BTS. It handles the upload of software from the I/O
system in the BSC and performs software file transfer to the
BTS. It also performs reset and restart of MOs.
Supervision and Alarm Handling (SUP)
SUP supervises the status of the BTS by acting on BTS related

faults and the various link and device faults. It also coordinates
generation of and stopping of BTS equipment alarms and BTS
external alarms.
Test and Verification (TEST)
TEST performs manual or automatic tests of MOs. During the

recovery process, TEST verifies the status of the BTS. It also
handles various status and fault information printouts.
Transcoder Handling (TRA)
TRA handles the operation and maintenance of the transcoder

hardware. This consists of an SNT and device owner blocks plus
two separate blocks for transcoder specific alarm handling and
commands for manipulating transcoder data.
– 174 – EN/LZT 123 3330 R1B

5 APT Subsystem
LINK HANDLING SUBSYSTEM (LHS)

LHS handles the connections between the BSC and the BTS.
The hardware for LHS is located at the BTS site. It operates as
one or more radio selectors, each controlled by an EMRP which
is connected to the CP via a STR-STC signaling link.
The PCM links from the BSC terminates at the ETC boards in
LHS and the physical connections from the BTS terminates in
Radio Transceiver Terminals (RTT). Up to 10 ETBs and
RTTs can be connected to one radio selector. Each radio selector
includes a Time Switch (TSW) which works as a Digital Cross
Connect (DCC) with semiperminanent connections. Thus the
different 64 kbit/s connections on the PCM links from the BSC
to the transceivers can be reconfigured by means of the TSW.
The radio interface line terminals, Signaling Terminal

Regional (STR), Extension Module Regional Processor
(EMRP) together with the radio selectors, make up the
Transmission Radio Interface (TRI). Each TRI can handle
one I/O terminal and up to 32 external alarms. The terminal can
be used for operations and maintenance functions within the
BSS. The TRI is implemented in central and regional software
and hardware. Besides the main digital cross connector function,
the TRI also contains administrative functions for configuration
and maintenance. The TRI is automatically supervised and when
a serious fault is detected the faulty equipment is isolated and
taken out of service.
STATISTIC AND TRAFFIC MEASUREMENT SUBSYSTEM

STS is implemented through software in the SP and designed as
a box for introduction in any source system using APZ 211 or
APZ 212. It encompasses functions for live traffic observation
and traffic measurements. STS functions can be specified and
scheduled through the use of commands. Since the SP handles
all functions for STS, a CP-SP dialogue must be initiated before
using SP commands. The path building command IMLIT is used
for that purpose.
Traffic handling blocks contain counters for the collection of

traffic events. These counters are updated concurrently with the
traffic process. They are scanned periodically by STS which
processes the values and compiles the results for output. Statistic
and traffic measurements are tools for:
EN/LZT 123 3330 R1B – 175 –

• Network planning
• Dimensioning of entities (exchanges), routes and cells
• Providing traffic prognoses and traffic handling capability.
• Supervision and trouble shooting
STS FUNCTIONS
Measurement Data base: Administrates transfer of traffic and
measurement counters to the database at the time specified by
user command. Collection of data is started or stopped by
command.
Measurement Report Generator: A report program in which

the user can specify alphanumeric reports by means of
commands. It generates one or several reports according to a
given specification.
Measurement Report File Output, Standard Format:

Produces file output reports according to a given specification.
Measurement Report Time Table: Used to schedule reports.

The desired report, measurement object, and time schedule are
set by command.
Measurement Object Group Handler: Provides logical

grouping of objects.
– 176 – EN/LZT 123 3330 R1B

5 APT Subsystem
DATA FLOW IN STS

Figure 5-5 illustrates the flow of data in STS:
1. Counters in the traffic and maintenance system are read at

predefined intervals and values are inserted and stored in the
measurement database.
2. Report time table calls report program for production of
reports.
3. Report generator reads data from the measurement database
and generates reports.
Counters in the traffic system
Counters for traffic and Dynamic counters Accumulated level

maintenance objects counters
(peg and level counters)
Measurement data base (DB)

Collection and storage of data during 2 hours
(48 hours for accumulated 24 hour data)
DB user interface
Object group handler
Report generator Report file output
Report Time Table
Report Output
Specify Alphanumerical Specify File
Reports Report
Figure 5-5. Data flow in STS
EN/LZT 123 3330 R1B – 177 –

MEASUREMENT DATA BASE

Collection Of Counters: Counters are regularly collected and
transferred to the measurement Data Base (DB) every 5 or 15
minutes, as defined by the user. Collected counter values are
stored in the DB and saved for two hours. Additionally, the DB
contains summations of data for the current and previous 24
hour periods.
Counters for Traffic and Maintenance Objects

Event Counters show accumulated number of events.
Level Counters show counter values at a specific moment in

time.
Counters in DB
Peg Counters show accumulated number of events or
accumulated value of a counter.
Status Counters show counter value at a specific moment.
Event counters are stored in the DB as peg counters. Level

counters are stored in the DB as:
• STs - show level at a specific moment, i.e. a snapshot

• Accumulated level counter (peg counter)
• Number of accumulations counter (peg counter)
Event Counters Level Counters
Accumulated Level
Counters
Number of
Accumulations
Peg Counters Status Counters
Figure 5-6. Traffic and maintenance counters transferred to DB

counters
– 178 – EN/LZT 123 3330 R1B

5 APT Subsystem
Transformation is performed by a regular scanning of level

counters, where scanning results are added to the accumulation
counter. The number of the accumulations counter is
incremented by 1 per scanning. Additionally, there are programs
for dynamic counter handling for study objects that do not
correspond to traffic or maintenance objects, such as subscriber
groups or study sets.
Measurement Database Administration: In the DB,

measurement objects have been divided into object types. An
object type is a type of equipment, e.g. a cell. A command is
used to list object types in the system. The number of objects per
object type must be configured in the DB. It corresponds to a
unique set of counters which are measurable units within the
equipment. An object is the individual within the object type.
IMLIT:SPG=0;
:SDDOP:OBJTYP=CELLTCH&CELLCCH&NCELL&TG&TRXC&LAPD,AREA=OPER;
STATISTIC DATA
DATA BASE CONFIGURATION SURVEY
RECORDING ON AREA
OPER
OBJTYPE INCL NOBJ BRP CHANGEABLE NPOS
CELLTCH YES 100 15 YES 12
CELLCCH YES 100 15 YES 8
NCELLREL YES 100 15 YES 2
TG YES 100 15 YES 1
TRXC YES 100 15 YES 16
LAPD YES 100 15 YES 7
Figure 5-7. DB configuration for BSC object types
EN/LZT 123 3330 R1B – 179 –

IMLIT:SPG=0;
:SDDOP:OBJTYP=CELLTCH,AREA=OPER;LIST;
STATISTIC DATA
DATA BASE CONFIGURATION DETAILED
RECORDING ON AREA
OPER
OBJTYPE INCL NOBJ BRP CHANGEABLE NPOS
CELLTCH YES 200 15 YES 12
CNTNAME CNTTYPE CNTDES
TCALLS PC CALL ATTEMPT COUNTER
TCONGS PC CONGESTION COUNTER
TTRALACC PC TRAFFIC LEVEL ACCUMULATOR
TNSCAN PC NO OF ACC OF TRAFFIC LEVEL COUNTER
TNDROP PC NUMBER OF DROPPED CONNECTIONS
TNUCHCNT ST NUMBER OF DEFINED CHANNELS
TAVAACC PC AVAILABLE CHANNEL ACCUMULATOR
TAVASCAN PC NO OF ACC OF AVAILABLE CHANNELS COUNTER
Figure 5-8. Some of the counters included in object type

CELLTCH
Files in the DB: To read and write data, the DB requires a

number of files to be defined in FMS. They are predefined in
EXCHVOLUME. Configuration data for files is found in the
application information for the file owning the function blocks.
INMCT:SPG=0;
:INFIP:VOL=EXCHVOLUME;
FILE TABLE
FILE FCLASS
SPTRANOBJECT SPL (Used to store object table)
SPTRANTABLE SPL (Used to store translation table)
STCPDUMP CMP (Used to store copied data from CP)
STDB24HFILE SPL (Accumulation of 24-hour reports)
STDBADMFILE SPL (Used to store administrative data)
STDBRCFILE SPL (Used to store counters)
STFIOPADM SPL (Used to store support data)
STFIOPFIL1 CMP (Contains measurement reports)
STMPFILE SPL (Stores measurement program data)
STOBJTYPE CMP (Used to store object type data)
STOGHFILE SPL (Used to store object group data)
STRECPARFILE SPL (Used to store object group data
STREPSPFILE SPL (Used to store support data)
STSTART SPL (Used to store support data)
STTRANF1 CMP (Contains data for object types)
Figure 5-9. Files in STS
– 180 – EN/LZT 123 3330 R1B

5 APT Subsystem
Translation: The translation function is used to connect

counter(s) for an object or individual to an external name used in
the STS reports. This function provides users with the capability
to translate one or more objects for a report containing selected
objects. Updates of translation tables are completed
automatically every 24 hours and manually when necessary, via
command SDDTI (Updating of translation tables).
Counters in the DB Used by the BSC For Traffic and Event

Measurements in the Radio Network:
Object Type CELLTCH (Traffic Channels per Cell):
Type Counter name Description

PC TCALLS Call attempt counter
PC TCONGS Congestion counter
PC TTRALACC Traffic level accumulator
PC TNSCAN Number of accumulations of traffic

level counter
PC TNDROP Number of dropped connection
ST TNUCHCNT Number of defined channels
PC TAVAACC Available channel accumulator
PC TAVASCAN Number of accumulations of

available channels counter
PC TASSAL Assignment attempts for all MS

power classes
PC TASSMS5 Assignment attempts for MS power

class 5
PC TCASSALL Assignment attempts congested for

all MS power classes
PC TCASSMS5 Assignment attempts congested for

MS power class 5
EN/LZT 123 3330 R1B – 181 –

Object Type NCELLREL (Neighboring Cell Relation):

PC HOVERCNT Number of handover attempt to
neighboring cell
PC HOVERSUC Number of successful handovers to

neighboring cell
– 182 – EN/LZT 123 3330 R1B

5 APT Subsystem
Object Type TG (Transceiver Group):

PC INTERCNT Intermittent faults
Object Type CELLSDCCH and RANDOMACC (Control

Channels per Cell):

PC CCALLS Call attempt counter
PC CCONGS Congestion counter
ST CTRALCNT Traffic level counter
PC CNDROP Number of dropped connection
PC CNROCNT Number of random accesses
ST CNUCHCNT Number of defined channels
PC CAVAACC Available channel accumulator
PC CAVASCAN Number of accumulations of

available channels counter
Object type LAPD (Link Access Procedure for D-channel):
PC CBADFRAME Number of received bad frames
PC CTRIFRAME Number of TX LAPD info frames
PC CRECIFRAME Number of RX LAPD info frames
PC CRETRANSM Number of retransmissions
PC COVERLOAD Number of link overloads
PC CLINKFAIL Number of link failures
PC CPROCOLERR Number of link protocol errors
EN/LZT 123 3330 R1B – 183 –

Object Type TRXC (Transceiver Controller):
PC CONERRCNT0 Abnormally terminated connections
PC CONCNT0 Connection set up attempts
– 184 – EN/LZT 123 3330 R1B

5 APT Subsystem
Object Type IDLECH (Idle Channels):
PC NOACC Number of accumulations
PC ITOSIB1 Accumulated number of idle TCHs

in Overlaid Subcell in Interference
Band 1

Band 2

Band 3

Band 4

Band 5
PC ITUSIB1 Accumulated number of idle TCHs

in Underlaid Subcell in Interference
Band 1

inUnderlaid Subcell in Interference
Band 2

Band 3

Band 4

Band 5
EN/LZT 123 3330 R1B – 185 –

Object Type BSC (Counters per BSC)
PC BSCCUMMS Cumulative number of MS sessions

in the BSC
ST BSCMAXMS Number of ongoing MS sessions in

the BSC
PC DCSCUMMS Cumulative number of MS sessions

in the BSC in DCS 1800 system
ST DCSMAXMS Number of ongoing MS sessions in

the BSC in DCS 1800 system
PC GSMCUMMS Cumulative number of MS sessions

in the BSC in GSM system
ST GSMMAXMS Number of ongoing MS sessions in

the BSC in GSM system
Object Type RNDACCEXT (Random Access per Cell

Extended)
PC RACALR1 Number of random accesses, Call

reestablishment. TCH/H was in use,
and the network sets the NECI bit to
1.
PC RACALR2 Number of random accesses, Call

reestablishment TCH/H+TCH/H was
in use, and the network sets the
NECI bit to 1.
PC RAAPAG1 Number of random accesses, Answer

to paging. Channel needed = TCH/F
MS capability = Dual rate
PC RAAPAG2 Number of random accesses, Answer

to paging. Channel needed = TCH/H
or TCH/F MS capability = Dual rate
PC RAAPOPS Number of random accesses, Answer

to paging or other procedures that
can be completed with an SDCCH.
– 186 – EN/LZT 123 3330 R1B

5 APT Subsystem
PC RAORSPE Number of random accesses,

Originating speech call from dual-
rate MS when TCH/ H is sufficient
and the network sets the NECI bit to
1.
PC RAORDAT Number of random accesses,

Originating data call from dual-rate
MS when TCH/H is sufficient and
the network sets the NECI bit to 1.
Object Type CELLEVENT (Channel Change per Cell)
PC HOAATOL Handover attempts to overlaid

subcell.
PC HOSUCOL Number of Successful handover

attempts to overlaid subcell.
PC HOAATUL Handover attempts to underlaid

subcell.
PC HOSUCUL Number of Successful handover

attempts to underlaid subcell.
PC HOINUQA Number of intra cell handover

attempts at bad uplink quality.
PC HOINDQA Number of intra cell handover

attempts at bad downlink quality.
PC HOINSUC Number of successful intra cell

handovers.
PC DISNORM Normal disconnection
PC DISBQA Disconnection at bad radio link

quality
PC DISBSS Disconnection at bad signal strength
PC DISETA Disconnection at excessive TA
EN/LZT 123 3330 R1B – 187 –

PC HOINBQA Number of intra cell handover

attempts at bad quality in both links.
PC HOINBOCH Number of unsuccessful intra cell

handover attempts, MS back on old
channel.
PC LSTIME Accumulated time for load sharing

in seconds.
PC TIME Total Time in seconds.
PC HOATTLS Handover attempts due to cell load

sharing.
PC HOSUCLS Successful handovers due to cell

load sharing.
PC HOATTBL Handover attempts due to operation

and maintenance intervention.
PC HOSUCBL Successful handovers due to

operation and maintenance
intervention.
Object Group Handler: The object group handler simplifies

the report specification and provides tools for more structured
reports. It enables the logical grouping of objects (object groups
not single objects) will be included in report specifications.
Single objects can then be represented one by one. It is also
possible to present sums of an object group.
SDOGI:OBJGRP=1,OBJTYPE=NCELLREL,OBJ=CELL1
&CELL2&CELL3,OGNAME=CITY,ADD=NO;
– 188 – EN/LZT 123 3330 R1B

5 APT Subsystem
Heading Heading
Adminfo Adminfo
Recorded data Heading
Recorded data
Heading
Recorded data
Figure 5-10. Single and Combined report
MEASUREMENT REPORT GENERATOR

The measurement report generator is a report program in which
users can specify alphanumeric reports via user commands. This
function processes, produces, and prints readable reports. A
number of specifications can be defined.
Definition of recording parameters: The recording parameter is

given a name, and a formula is specified. The name is used in
the report as a column identifier of counter value(s). A
maximum of seven characters are allowed. The formula
specifies how the counter values are to be used. It may contain a
single counter or a mathematical relation between counters and
constants expressed in Reversed Polish Notation.
Operands in the formula are:
• Counters (within same object type)

• Constants (integer 0 - 65535)
• Period Length (measured interval in minutes)
EN/LZT 123 3330 R1B – 189 –

Allowed operators are:
+ for addition
- for subtraction
* for multiplication
/ for division
Report definition: Two types of reports can be specified by

command. They are single reports and combined reports. A
single report is assigned a name and specifies the recording
parameters that should be included. It contains data from one
object type. A single report can also contain one or several
object groups. A combined report is assigned a name and is a
combination of different single reports.
SDRPI:OBJTYPE=NCELLREL,RECPNM=PERSUC,FMU
LA="HOVERSUC,100*HOVERCNT/";
SDRSI:RPTID=101,OBJTYPE=NCELLREL,RECPNM=PE
RSUC,HEADING="PSHTNC",OBJGRP=1;
SDRCI:RPTID=201,SRTID=101&102,HEADING="COMB
INED";
General data record
Object type record
Object record
Object record
Object type record
Object record
Object record
Figure 5-11. File report
– 190 – EN/LZT 123 3330 R1B

5 APT Subsystem
MEASUREMENT REPORT FILE OUTPUT, STANDARD FORMAT

This function handles report file output. Data files containing
reports can be transferred to a data link or magnetic tape.
Transfers are managed by the File Process Utility (FPU). Data
in the reports can be manually interpreted by means of
STFIOPFILE printout description or post-processed. Every
report specification has a separate file for outputs. These files
are divided into two types of subfiles.
Demand Report Output Subfile: There is only space for one

report output at a time in the subfile. The next demand report
printout is stored in the same subfile. This means that after each
demand report printout, the user must check the subfile to see if
there is another report there.
Periodical Produced Report Output Subfile(s): This type of

subfile contains report printouts transferred to a file by means of
a report timetable. The subfile contains a number of reports
produced during one time interval. The subfile collection
interval is set by command with a default value of 1 hour. The
subfile is closed when a subfile collection interval is complete.
FPU is informed when the subfile is ready for post processing
after which a new subfile is opened.
INFII:FILE=TEST,VOL=EXCHVOLUME,RLENGTH=20
48,SIZE=20,EXP=20,TYPE=SEQ,FCLASS=CMP;
SDFOI:RPTID=37,FILE=TEST,OBJTYPE=NCELLREL;
SDFSC:FILE=TEST,INTM=15;
EN/LZT 123 3330 R1B – 191 –

MEASUREMENT REPORT TIMETABLE

The timetable function administrates time schedules that control
when measurements on specified recording objects are to be
made. This function enables the staff to order:
• periodical measurements according to intervals specified in

the time schedule
• reports immediately
Measuring Program (MP): This is used for administration of

periodical measurements. MP is identified by a user assigned
number. Different MPs are independent of each other. Several
MPs can be defined to run on the same time schedule and
perform registration on the same objects. 256-Mbps are
available by default.
Time Schedule: The time schedule indicates when a report is to

be printed. It also provides the collection interval that
determines when data collection is to be performed. The time
schedule is defined by starting date, starting time, stop time, and
collection interval.
The smallest unit in the schedule is the Basic Recording Period

(BRP). That is, the collection interval must be equal to or a
multiple of the BRP. The first output occurs at the starting date
and time and contains collected data from the preceding
measurement interval. The following reports are output at the
starting date and time plus n * collection interval. Collection
continues until the stop date and time are reached or a
termination command is entered.
SDTDP:RPTID=101,OBJTYPE=NCELLREL,INT=30;
(Immediate report)
SDTPI:MP=1,RPTID=101,INT=24,TIME=1200;(Time
scheduled report)
– 192 – EN/LZT 123 3330 R1B

5 APT Subsystem
OPERATIONAL INSTRUCTIONS
Statistic data, measurement database administration:
• Installation of the measurement database

• Changes in measurement database administration
• Request printout of measurement database characteristics
• Start collection of statistic data
• Stop collection of statistic data
• Update translation tables
Statistic data, report generator administration:
• Definition of single reports

• Definition of combined reports
• Removal of report specification
• Print out of report specification
• Removal of recording parameter specification
• Print out of recording parameter specification
• Change of single report specification
• Change of combined report specification
Statistic data, file output standard format, report

administration:
• Initiate file output report specification

• Remove file output report specification
• Print file output report specification
• Change file output subfile output collection interval
• Print file output subfile output collection interval
EN/LZT 123 3330 R1B – 193 –

Statistic data, report measurement administration:
• Start of measurement
• Stop of measurement
• Print out of defined measurement
• Request of immediate measurement results
Statistic data, object group handler administration:
• Definition of an object group

• Removal of an object group
• Print out of an object group specification
• Print out of object group identities
• Change of objects in an object group
Statistic administration in BSC, traffic measurement on cells:
• Define a report for traffic measurements on cells

• Generate reports for traffic measurement on cells
• Generate file output for traffic measurement on cells
Statistic administration in BSC, handover measurement:
• Define a report for handover measurement

• Generate reports for handover measurement
• Generate file output for handover measurement
Statistic administration in BSC, dropped connections

measurement:
• Define a report for dropped connections measurements

• Generate reports for dropped connections measurement
• Generate file output for dropped connections measurement
– 194 – EN/LZT 123 3330 R1B

5 APT Subsystem
Statistic administration in BSC, BTS equipment disturbances:
• Define a report for BTS equipment disturbances

• Generate reports for BTS equipment disturbances
• Generate file output for BTS equipment disturbances
Statistic administration in BSC, random access measurement:
• Define a report for random access measurement

• Generate reports for random access measurement
• Generate file output for random access measurement
Statistic administration in BSC, LAPD link measurements:
• Define a report for LAPD link measurements

• Generate reports for LAPD link measurements
• Generate file output for LAPD link measurements
GUIDELINE
Measurement Data base Administration:

Action: Start data configuration session. Initiate transfer of
initial data to correction area.
IMLIT:SPG=0;
SDDOI;
Result: EXECUTED
Action: Request survey printout of database characteristics from

correction area.
SDDOP: OBJTYPE = ALL, AREA = CORR;
Result: Statistic Database Configuration Survey
Action: Define object types for measurement.

SDDOC: OBJTYPE=CELLTCH, INCL=YES,
BRP=15,NOBJ=1200;
Result: EXECUTED
EN/LZT 123 3330 R1B – 195 –

Action: Terminate configuration session.

SDDOE: EXEC;
Result: ORDERED
Action: Release terminal and wait for answer printout.

Result: STATISTIC DATA MEASUREMENT DATABASE
CONFIGURED
Comment: Data base will be configured and data in
correction area will be switched to operating area. To leave
session without changes, use parameter QUIT.
Action: Check data defined in data base.

IMLIT:SPG=0;
SDDOP:OBJTYPE=ALL,AREA=OPER;
Result: STATISTIC DATABASE CONFIGURATION
SURVEY.
Action: Initiate collection of statistic counters.
SDDCI;
Result: EXECUTED
Comment: Statistic counters are copied from CP to SP.

Collection interval is set in a data base for each object type,
parameter BRP.
Object Group Handler Administration:

Action: Print all defined object group identities.
SDOIP;
Result: STATISTIC DATA OBJECT GROUP
IDENTITIES
Action: Define object group and connect object.

SDOGI:OBJGRP=16,OBJTYPE=CELLTCH,
OGNAME=’’TEST’’,OBJ=CELL1,ADD=NO;
Result: EXECUTED
Comment: If all objects in an object group are to be
presented together, parameter ADD is to be set to YES. If
ADD is set to NO, objects are presented individually.
– 196 – EN/LZT 123 3330 R1B

5 APT Subsystem
Action: Connect more objects to an object group.

SDOGC:OBJGRP=16,OBJTYPE=CELLTCH,OBJ=CE
LL2;
Result: EXECUTED
Comment: Only objects belonging to same object type can
be defined in an object group. Objects can be deleted by
using parameter DOBJ=obj.
Action: Check defined object group.
SDOGP:OBJGRP=16;
Result: STATISTIC DATA OBJECT GROUP
SPECIFICATION
Action: UPDATE TRANSLATION TABLES.

SDDTI;
Result: ORDERED
Action: Release terminal and wait for answer printout.

Result: STATISTIC DATA TRANSLATION TABLES
UPDATED
Comment: Translation tables are updated automatically
every 24 hours.
Report Generator Administration:
Single Reports
Action: Print out counters for object type.
IMLIT:SPG=0;
SDDOP:OBJTYPE=CELLTCH, AREA=OPER, LIST;
Result: STATISTIC DATABASE CONFIGURATION
DETAILED
EN/LZT 123 3330 R1B – 197 –

Action: Define recording parameters.

SDRPI:RECPNM=NUBAVA,OBJTYPE=CELLTCH,
FMULA=’’TCALLS’’;
SDRPI:RECPNM=SENBA,OBJTYPE=CELLTCH,
FMULA=’’TCALLS,TCONGS+’’;
SDRPI:RECPNM=OVIBA,OBJTYPE=CELLTCH,
FMULA=’’TCALLS, TCONGS*TNDROP/’’;
Result: EXECUTED
Action: Check the defined recording parameters.

SDRPP:RECPNM=ALL,OBJTYPE=objtype,
DETAILED;
Result: STATISTIC DATA RECORDING PARAMETER
SPECIFICATION
Action: Define a single report.

SDRSI:RPTID=(101-
357),HEADING=’’heading’’,OBJTYPE=objtype,
RECPNM=recpnm,OBJGRP=objgrp;
Result: EXECUTED
Action: Check defined report.
SDRRP:RPTID=rptid,DETAILED;
Result: STATISTIC DATA SINGLE REPORT

SPECIFICATION
Combined Reports
Action: Define a combined report.
SDRCI:RPTID=rptid,SRTID=srtid,HEADING=’’heading’’;
Result: EXECUTED
Comment: A combined report is created from two or more
single reports.
Action: Check the defined report.

SDRRP:RPTID=rptid, DETAILED;
Result: STATISTIC DATA COMBINED REPORT
SPECIFICATION
– 198 – EN/LZT 123 3330 R1B

5 APT Subsystem
File Output Standard Format, Report Administration:

Action: Define a report for file output.
SDFOI:RPTID=(37-
100),FILE=stfiopfile,OBJTYPE=objtype;
Result: EXECUTED
Comment: Output of all counters for a specified object type
will be performed on the specified file.
Action: Define interval for generation of new subfiles.

SDFSC:FILE=stfiopfile, INTH=inth;
Result: EXECUTED
Comment: A new subfile will be generated after INTH
hours. Parameter INTM is used if the interval for
generation is specified in minutes.
Report Measurement Administration:
Time Scheduled Reports

Action: Define a measuring program.
SDTPI:MP=mp,RPTID=rptid,INT=int,TIME=time,DA
TE=day,REP=rep,IO=io;
Result: EXECUTED
Comment: Output of report with identity RPTID is

performed on the I/O specified. The first report is generated
at the date and time specified and will include data from the
given interval. Measurements must be started one interval
before the given date and time. Output of the report will be
done rep times with one interval between them. REP* INT
must not exceed 24 hours. Definitions of reports for file
output are performed in the same manner. Parameter I/O
should be omitted.
Action: Print all defined measuring programs.

SDTIP;
Result: STATISTIC DATA MEASURING PROGRAM
IDENTITIES
EN/LZT 123 3330 R1B – 199 –

Action: Check defined measuring programs.

SDTPP:MP=mp, DETAILED;
Result: STATISTIC DATA MEASURING PROGRAM
SPECIFICATION
Demand Reports
Action: Reports can be demanded at any time by command.
SDTDP:RPTID=rptid, INT=int, IO=io;
Result: STATISTIC DATA REPORT
Comment: Output of a report with identity RPTID will be

performed immediately on specified I/O. Data will be
included for the interval specified. Measurement must be
started at least one interval before the command is given.
Output to file is performed in the same way, but parameter
I/O is omitted. Demand output to file is stored in subfile
stfiopfile-DEMAND. Parameter INT can have the following
values: 5= 5min, 15 = 15min, 30 = 30min, 1 = 1h, 2 = 2h,
24 = 24h.
Deactivate Measurement Program:

Action: Deactivate measurement program.
SDTPE:MP=mp, TIME=time, DATE=date;
Result: EXECUTED
Comment: If date and time is not specified, the measuring
program will be deactivated immediately.
Delete Measurement Program:

Action: Delete measurement program.
SDTPE:MP=mp, MPE;
Result: EXECUTED
– 200 – EN/LZT 123 3330 R1B

5 APT Subsystem
Demand Report:
Action: Delete a combined or single report by command.
SDRRE:RPTID=rptid;
Result: EXECUTED
Remove Recording Parameter:

Action: Remove recording parameter with command.
SDRPE:RECPNM=recpnm, OBJTYPE=objtype;
Result: EXECUTED
Delete Object Groups:

Action: Delete an object group by command.
SDOGE:OBJGRP=objgrp;
Result: EXECUTED
Stop Collection Of Statistic Counters:

Action: Collection of statistic counters are stopped by
command.
SDDCE;
Result: EXECUTED
EN/LZT 123 3330 R1B – 201 –

BASIC INTERNAL CALL HANDLING

Basic internal call handling for the BSS is shown in Figure 5-12.
This section provides an overview of how different steps in the
processes are handled by APT. Locating is not included in the
figure although it takes part in all steps except paging.
Interaction between procedures is not described. Two important
cases are handover on a dedicated signaling channel interacting
with ASSIGNMENT or with cipher mode control. When
ASSIGNMENT interacts with handover on a signaling channel,
handover is performed first. When handover on a dedicated
signaling channel interacts with cipher mode control, cipher
mode setting is performed first.
Call to MS Call from MS
PAGING
IMMEDATE ASSIGNMENT
ASSIGNMENT
HANDOVER
CLEAR
Figure 5-12. Basic Internal Call Handling
– 202 – EN/LZT 123 3330 R1B

5 APT Subsystem
PAGING
Paging is the procedure used when initiating a call to a MS. The
procedure is initiated with a paging message received in the
RCS from the MSC via the CCS. The RCS checks and validates
the message and then checks with the ROS to see if enough
processor capacity is available for execution. If not, the paging
message is discarded. Otherwise, a check is performed to see if
paging is to be performed in all cells for the BSS or just for
those belonging to a specific location area. A Paging Command
is then sent to those base stations in which paging is to be
performed. The base stations then send paging information over
their paging channels to the MSs.
BSC
MSC CCS ROS RCS BTS MS
Paging Message
Capacity Check
Paging Command
Paging Information
Figure 5-13. BSC procedures for paging
IMMEDIATE ASSIGNMENT
Immediate assignment is initiated by information received on
the RACH in the BTS. The BTS sends the GSM-08.58 Channel
Required message to the RCS. The maximum permitted timing
advance is collected and compared with the Access Delay value
in the Channel Required message to ensure the MS is within the
allowed range. If the reason for the immediate assignment is not
a paging response, the RCS checks with the ROS to ensure
enough processor capacity is available for the execution of the
procedure. If the reason for the random access is a paging
response, processing capacity will already have been requested.
EN/LZT 123 3330 R1B – 203 –

The RCS allocates a signaling only channel in the relevant cell

and then activates the appropriate channel for signaling. The
RCS then informs the BTS with the GSM-08.58 Channel
Activation message. When the channel has been activated in the
BTS, the GSM-08.58 Channel Activation Acknowledge
message is returned to the RCS. The RCS seizes a MS-
individual and sends the GSM-08.58 Immediate Assign
Command message containing the GSM-04.08 Immediate
Assignment message towards the BTS, which in turn sends the
GSM-04.08 Immediate Assignment message to the MS. This
message instructs the MS to switch to the allocated signaling
channel. When the BTS and MS are in contact over the channel,
the GSM-08.58 Establish Indication message (including Layer 3
message) is sent from the BTS to the RCS. The RCS activates
Radio Connection Quality Supervision in the TRH. This signal
starts the locating function on the SDCCH and also initiates the
power control algorithm.
The RCS establishes a link with the MSC by sending the GSM-
08.06 Sccp Connection Request message, including the GSM-
08.08 Complete Layer 3 Information message.
When a connection with MSC is established, the GSM-08.06

message Sccp Connection Confirm is returned.
BSC
MSC CCS ROS RCS BTS MS
Random access info
Channel Required
Get max timing advance
Check of capacity
Allocation of channel
Channel Activation
Channel Activation Ack.
Seize MS-ind
Imm Assign Command (IA)
Setup link
Establish Indication
Start Call Supervision
SCCP Connection Request
SCCP Connection Confirm
Figure 5-14. BSC procedures for immediate assignment
– 204 – EN/LZT 123 3330 R1B

5 APT Subsystem
ASSIGNMENT
This procedure is initiated by the MSC which sends a GSM-
08.08 Assignment Request message to the RCS via the CCS and
the ROS. Subfunctions in the RCS request a list of candidates
from the locating function. The list is evaluated and depending
on the result, one of three assignments is started:
• Assignment to Serving Cell

• Assignment to another cell in the same BSC
• Assignment to an External cell
Assignment to Serving Cell: The RCS identifies where an
individual is seized and seizes the appropriate device in the ROS
as specified by CIC in the GSM-08.08 Assignment Request
message from the MSC. The RCS then allocates a channel and
collects the TA value and calculated MS power level. The GSM-
08.58 Channel Activation message is then sent to the BTS and
the BTS responds by sending a GSM-08.58 Channel Activation
Acknowledge message. The RCS then sets up a path through the
GSS for the traffic connection.
RCS Subfunctions determine that the MS may disappear from

the old channel. As a result, a disconnect is not initiated due to
missing Measurement Reports before sending GSM-04.08
Assignment Command message to the BTS and on to the MS.
This message tells the MS to switch to the new channel.
When the MS has switched to the new channel the GSM-08.58

Establish Indication message is sent from the BTS to the RCS.
The GSM-04.08 Assignment Complete message is then sent to
the RCS via the BTS. The result is disseminated and a request is
made to transfer old locating data to be used in the start of Call
Supervision. Call Supervision for the old channel is stopped and
Call Supervision for the new channel started. The old channel is
released and acknowledged and the GSM-08.58 RF Channel
Release message is sent to the BTS. The BTS responds by
sending a GSM-08.58 RF Channel Release Ack. message. The
RCS checks that the channel was released and that the
assignment succeeded. The RCS sends GSM-08.08 Assignment
Complete message to the MSC.
EN/LZT 123 3330 R1B – 205 –

BSC
MSC CCS ROS RCS GSS BTS MS
Assignment Request
Request candidate list
Seize device
Allocate channel
Collecting Timing Advance
Channel Activation
Channel Activation Ack
Setup path in GS
Inform that MS may disappear

Assignment Command
Setup link
Assignment Complete
Inform about result
Stop call supervision for old channel
Start call supervision for new channel
Release channel
RF channel release
RF channel release ack
Assignment succeeded
5 Assignment Complete
Figure 5-15. BSC procedures for assignment to serving cell
Assignment to Another Cell in the Same BSC: The RCS

seizes the appropriate device in the ROS from the MSC and
allocates a new traffic channel, as specified by CIC in the GSM-
08.08 Assignment Request message. Channel information is
verified and the GSM-08.58 CHANNEL ACTIVATION
Message is sent to the BTS and the BTS responds by sending a
GSM-08.58 Channel Activation Acknowledge message. The
RCS sets up a path through the GSS for traffic connection.
RCS Subfunctions determine that the MS may disappear from

the old channel, so that a disconnect is not initiated due to
missing Measurement Reports. After this, the GSM-04.08
Handover Command message is sent to the MS via the BTS.
The MS receives this message and switches to the new channel.
When the BTS is in contact with the MS it sends GSM-08.58
Handover Detection message back to the RCS.
– 206 – EN/LZT 123 3330 R1B

5 APT Subsystem
BSC
Assignment Request
Seize device
Allocate new channel

Channel Activation
Setup path in GS

Handover Command
Handover Access Burst
Handover Detection
Get Max Timing Advance
Handover complete
Inform about result
Release channel
RF channel release
Handover succeeded
Assignment Complete
Figure 5-16. BSC procedures for assignment to another cell in

the same BSC
The maximum permitted TA value is identified and compared to

the Access Delay value in GSM-08.58 Handover Detection
message to ensure that the MS is within the allowed range. After
the connection between the new BTS and MS is established, the
GSM-08.58 Establish Indication message is sent to the RCS
from the BTS and the GSM-04.08 Handover Complete message
is sent from the MS.
RCS subfunctions are then informed about the result and receive
a request to transfer old locating data to be used in starting Call
Supervision. Call Supervision for the old channel is stopped and
Call Supervision for the new channel is started. The RCS sends
the GSM-08.58 RF Channel Release message to the BTS which
responds by sending a GSM-08.58 RF Channel Release Ack.
message. The RCS checks that the channel was released and that
the handover succeeded. The RCS sends a GSM-08.08
Assignment Complete message to the MSC.
EN/LZT 123 3330 R1B – 207 –

Assignment to an External Cell (In Originating BSC): The

RCS sends the GSM-08.08 Handover Required message to the
MSC. This tells the MSC which cell the handover is to be made
to. The new channel is selected in the target BSC and the MSC
sends the GSM-08.08 Handover Command message to the RCS.
RCS subfunctions determine that the MS may disappear from
the old channel, so that a disconnect is not initiated due to
missing Measurement Reports. The RCS then sends GSM-04.08
Handover Command message to the MS telling it to switch to a
new channel. The MS establishes contact with the new channel
in the target BSC.
To clear the old connection, the MSC sends the GSM-08.08

Clear Command message with handover cause “successful
handover” to the RCS. The RCS changes the link and sends the
GSM-08.08 Clear Complete message to the MSC. The RCS
stops Call Supervision for the old channel and orders the release
of the old channel. The GSM-08.58 RF Channel Release
message is sent to the BTS which responds by sending a GSM-
08.58 RF Channel Release Ack. message. When the GSM-08.06
SCCP Released message is received from the MSC, GSM-08.06
SCCP Release Complete message is returned by the CCS and an
indication that SCCP is disconnected is sent to the RCS.
Assignment to an External Cell (In Target BSC): BSC

procedures in the target BSC for external handover on
assignment are identical to those for a handover on a traffic
channel BSC interwork in Target BSC for Inter BSC Handover
on TCH.
– 208 – EN/LZT 123 3330 R1B

5 APT Subsystem
BSC
Assignment Request
Handover Required
New channel selected in target BSC. See figure 14.
Handover Command
Handover command to MS
MS in contact with new channel in target BSC. See figure 14.
Clear Command
Handover succeeded
Clear Complete
Release channel
RF channel release
SCCP Released
SCCP Release complete
SCCP connection released

497
Figure 5-17. BSC procedures in assignment to external cell

(originating BSC)
Handover on a TCH: There are four possible types of

handovers on a TCH that can be initiated in a BSC:
• Intra BSC, intra cell handover

• Intra BSC, inter cell handover
• Inter BSC handover, originating BSC
• Inter BSC handover, target BSC
The first three are initiated from the locating function in the
RCS. Inter BSC handover, target BSC is initiated when GSM-
08.08 Handover Request message is received from MSC.
Intra BSC, Intra Cell Handover on a TCH: The RCS

identifies when an individual is seized and allocates a traffic
channel. On channel allocation, RCS subfunctions transfer
information about the channel, the value for TA, and the
calculated MS power level. The GSM-08.58 message Channel
Activation is sent to the BTS which responds with the GSM-
08.58 Channel Activation Acknowledge message.
EN/LZT 123 3330 R1B – 209 –

The RCS determines that the channel change is in progress and

that the MS may disappear, so no disconnect is initiated due to
missing Measurement Reports. The GSM-04.08 Assignment
Command message is then sent to the MS through the BTS
telling the MS to switch to the new channel.
When the MS has switched to the new channel, the GSM-08.58

Establish Indication message is sent from the BTS back to the
RCS. The RCS releases the old path through the GSS and sets
up a new path for a traffic connection. The GSM-04.08
Assignment Complete message is then sent from the MS to the
RCS. Subfunctions of the RCS transfer the old locating data to
be used in start of Call Supervision.
The RCS stops Call Supervision for the old channel and starts
Call Supervision for the new channel, and then releases the old
channel. The GSM-08.58 RF Channel Release message is then
sent to the BTS which responds by sending a GSM-08.58 RF
Channel Release Ack. message. RCS Subfunctions determine
that the channel is released and verify the result of the handover.
Internal links are changed and acknowledged. The GSM-08.08
Handover Performed message is sent to the MSC via the ROS
and CCS.
BSC
Handover initiate
Allocate channel
Collect timing advance
Channel activation
Channel activation ack
Assignment command
Setup link
Establish indication (new channel)
Change path in GS
Assignment complete
Inform about result
Release channel
RF channel release
Handover succeeded
Handover performed
Figure 5-18. BSC procedures for Intra BSC, intra cell handover
on TCH.
– 210 – EN/LZT 123 3330 R1B

5 APT Subsystem
Intra BSC, Inter Cell Handover on a TCH: The RCS

identifies where an individual is seized and allocates a new
traffic channel. The GSM-08.58 Channel Activation message is
then sent to the BTS which responds with the GSM-08.58
Channel Activation Acknowledge message. The RCS checks
that the channel change is in progress and that the MS may
disappear so that no disconnect is initiated due to missing
Measurement Reports. The GSM-04.08 Handover Command
message is then sent to the MS.
When the BTS receives a handover access burst from the MS, it
sends the GSM-08.58 Handover Detection message to the RCS.
The maximum permitted TA is collected from the RCS which
compares it with the Access Delay value in the GSM-08.58
Handover Detection message to ensure that the MS is within the
allowed range. The RCS releases the old path through the GSS
and sets up a new path for the traffic connection. When the
connection between the new BTS and MS is established, the
GSM-08.58 Establish Indication message is sent to the RCS.
The GSM-04.08 Handover Complete message is then sent from
the MS to the RCS. RCS Subfunctions analyzes the result of the
handover and requests a transfer of old locating data to be used
to start Call Supervision. Stop Call Supervision for the old
channel and start Call Supervision for the new channel is then
initiated and the old channel is released.
The RCS sends the GSM-08.58 RF Channel Release message to

the BTS which responds by sending a GSM-08.58 RF Channel
Release Ack. message. The RCS identifies that the channel is
released and that the handover is completed. Internal links are
changed and acknowledge and the RCS sends the GSM-08.08
Handover Performed message to the MSC via the ROS and
CCS.
EN/LZT 123 3330 R1B – 211 –

BSC
Handover initiate
Allocate channel
Channel activation
Channel activation ack
Handover command
Handover access burst
Handover detection
Get max timing advance
Change path in GS
Setup link
Establish indication
Handover complete
Inform about result
Release channel
RF channel release
Handover succeeded
Handover performed
Figure 5-19. BSC procedures for Intra BSC, inter cell handover
on TCH
Inter BSC Handover, Originating BSC: The RCS identifies

where an individual is seized and sends the GSM-08.08
Handover Required message to the MSC. This tells the MSC
which cell the handover is to be made to. In addition, a new
channel is selected in the target BSC. The MSC then sends the
GSM-08.08 Handover Command message, including the GSM-
04.08 Handover Command message, to the RCS. RCS
Subfunctions identify that a channel change is in progress and
that the MS may disappear, so no disconnect is initiated due to
missing Measurement Reports. The RCS sends the GSM-04.08
Handover Command message to the MS telling it to switch to a
new channel after which the MS establishes contact with the
new channel in the target BSC. To clear the old connection the
MSC sends the GSM-08.08 Clear Command message to the
RCS. The RCS verifies that the handover is complete and
changes internal links.
– 212 – EN/LZT 123 3330 R1B

5 APT Subsystem
The RCS releases the RALT device and sends the GSM-08.08
Clear Complete message to the MSC. The path in the GSS is
released and stop Call Supervision for the old channel is
initiated. The old channel is released and the GSM-08.58 RF
Channel Release message is sent to the BTS, which responds by
sending a GSM-08.58 RF Channel Release Ack. message. When
the GSM-08.06 SCCP Released message is received from the
MSC, the GSM-08.06 SCCP Release Complete message is
returned by CCS and an indication that SCCP is disconnected is
sent to the RCS. The RCS then sends a notification to the ROS
and the CCS that SCCP signaling connection is released.
BSC
Handover Initiate
Handover Required
New channel selected in target BSC. See figure 14.
Handover Command
Handover command to MS
MS in contact with new channel in target BSC. See figure 14.
Clear Command
Handover succeeded
Release device
Clear Complete
Release old path in GS
Release channel
RF channel release
SCCP Released
SCCP Release complete

00
Figure 5-20. BSC procedures in Originating BSC for Inter BSC

handover on TCH
Inter BSC Handover, Target BSC: The RCS identifies where

an individual is seized, seizes the appropriate RALT device, and
allocates a new traffic channel. The GSM-08.58 Channel
Activation message is then sent to the BTS which responds by
sending a GSM-08.58 Channel Activation Acknowledge
message. The RCS sets up the path through the GSS and sends
the GSM-08.08 Handover Request Acknowledge message,
including the GSM-04.08 Handover Command message, to the
MSC. In turn, the MSC sends the GSM-08.08 Handover
EN/LZT 123 3330 R1B – 213 –

Command message to the originating BSC which is then passed

on to the old BTS and then the MS.
When the new BTS receives the handover access burst from the
MS, it sends a GSM-08.58 Handover Detection message to the
RCS. The RCS sends a GSM-08.08 Handover Detect message to
the MSC to tell it to switch the path through its GSS. When the
connection between the BTS and MS is established, the GSM-
08.58 Establish Indication message is sent from the BTS. When
RCS receives the GSM-04.08 Handover Complete message
from the MS, start Call Supervision of the new channel is
initiated. RCS Subfunctions verify that the handover is
completed and identify which RALT device was previously
seized. Internal links are changed. The GSM-08.08 Handover
Complete message is sent to the MSC.
BSC
Handover request
Seize device
Allocate channel
Channel Activation
Setup path in GS
Handover request ack

Handover command is sent to originating BSC. See figure 15
Handover Access Burst
Handover Detection
Handover Detect
Setup link
Handover complete
Handover succeeded
Handover Complete
Figure 5-21. BSC procedures in Target BSC for Inter BSC

handover on TCH
– 214 – EN/LZT 123 3330 R1B

5 APT Subsystem
HANDOVER ON A DEDICATED SIGNALING CHANNEL

Handover on a SDCCH or TCH signaling connection is almost
identical to handover on a traffic channel except that the locating
evaluation is started on SDCCH or TCH signaling connection
and some messages indicate signaling only. Furthermore, there
is no GS handling.
CLEAR OF A TRAFFIC CHANNEL

Clear is initiated by the MSC sending the GSM-08.08 Clear
Command message to the RCS which releases the seized device
in RALT. The GSM-08.08 Clear Complete message is then sent
back to the MSC. The RCS releases the path in the GSS and
sends the GSM-04.08 Channel Release message to the MS and
the GSM-08.58 Deactivate SACCH message to the BTS. The
BTS responds by sending a GSM-08.58 Release Indication
message. The RCS stops channel Call Supervision and releases
the old channel. The GSM-08.58 RF Channel Release message
is sent to the BTS which responds with the GSM-08.58 RF
Channel Release Ack. message. When the GSM-08.06 SCCP
Released message is received from the MSC, the GSM-08.06
SCCP Release Complete message is returned by the CCS and an
indication that SCCP is disconnected is sent forward to the RCS.
The RCS sends an indication that the SCCP signaling
connection is released.
EN/LZT 123 3330 R1B – 215 –

BSC
Clear command
Release device
Clear complete
Release path in GS
Channel release
Deactivate SACCH
Release indication
Stop call supervision for channel
Release channel
RF channel release
SCCP released
SCCP release complete
Figure 5-22. BSC procedures for clear of a traffic channel
CLEAR OF A DEDICATED SIGNALING CHANNEL

Clearing a SDCCH or TCH signaling connection is almost
identical to Clearing a traffic channel except that some messages
indicate signaling only. Furthermore, there is no handling of the
GS or RALT devices.
– 216 – EN/LZT 123 3330 R1B

APT Subsystem: Objectives

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

APT Subsystem: Objectives

Hochgeladen von

Copyright:

Verfügbare Formate

APT Subsystem

This chapter is designed to provide the student with the

• name the subsystems in APT-210 09

EN/LZT 123 3330 R1B

RADIO CONTROL SUBSYSTEM (RCS)...........................................168

RADIO OPERATION & MAINTENANCE SUBSYSTEM (ROS) ........170

TRANSCEIVER ADMINISTRATION SUBSYSTEM (TAS)................173

LINK HANDLING SUBSYSTEM (LHS) .............................................173

STATISTIC AND TRAFFIC MEASUREMENT SUBSYSTEM ...........174

EN/LZT 123 3330 R1B –i–

BASIC INTERNAL CALL HANDLING...............................................202

– ii – EN/LZT 123 3330 R1B

APT hardware handles simple routine functions whereas the

The BSC consists of seven APT subsystems and an APZ.

ROS GSS TAS CCS

Figure 5-1. APT subsystems

EN/LZT 123 3330 R1B – 167 –

RADIO CONTROL SUBSYSTEM (RCS)

BG - CPR BG - CELL BG - TRH BG - RCQS

Figure 5-2. Logical structure of the RCS

– 168 – EN/LZT 123 3330 R1B

BG-TRH handles multiplexing of level 3 messages towards the

EN/LZT 123 3330 R1B – 169 –

RADIO OPERATION & MAINTENANCE SUBSYSTEM (ROS)

BG - BSSAP BG - ABIS BG - RECTRA BG - SUPP BG - TRANSM BG - TRXT

Figure 5-3. Logical structure of ROS.

• Administration of Circuit Identity Code in BSC

– 170 – EN/LZT 123 3330 R1B

The subfunction block ET handles the main parts of the EM/CM

The subfunction block ET handles the main part of the EM/CM

EN/LZT 123 3330 R1B – 171 –

• Processor and Exchange Input Load Measurement

– 172 – EN/LZT 123 3330 R1B

TRANSCEIVER ADMINISTRATION SUBSYSTEM (TAS)

Figure 5-4. Interfaces between TAS and other subsystems.

Administration of Managed Objects (ADM)

ADM handles the commands that bring MOs into operation. It

BTS Communication (COM)

COM establishes and maintains communication with the BTS.

EN/LZT 123 3330 R1B – 173 –

CONF matches the configuration requirements provided by RCS

Data and Structure Handling (DATA)

DATA is the central part of TAS. It acts as a coordinator within

BTS Loading (LOAD)

LOAD performs the loading of software packages from the BSC

Supervision and Alarm Handling (SUP)

SUP supervises the status of the BTS by acting on BTS related

Test and Verification (TEST)

TEST performs manual or automatic tests of MOs. During the

Transcoder Handling (TRA)

TRA handles the operation and maintenance of the transcoder

– 174 – EN/LZT 123 3330 R1B

LINK HANDLING SUBSYSTEM (LHS)

The radio interface line terminals, Signaling Terminal

STATISTIC AND TRAFFIC MEASUREMENT SUBSYSTEM

Traffic handling blocks contain counters for the collection of

EN/LZT 123 3330 R1B – 175 –

Measurement Report Generator: A report program in which

Measurement Report File Output, Standard Format:

Measurement Report Time Table: Used to schedule reports.

Measurement Object Group Handler: Provides logical

– 176 – EN/LZT 123 3330 R1B

DATA FLOW IN STS