GPRSP 60 V 5

Database planning
handbook for GPRS
SBS BR 6.0
GPRS Parameter Description
Issued by the
Mobile Networks Division
Hofmannstrasse 51
81359 Mnchen
SIEMENS AG 2002
The reproduction, transmission or use of this document or its contents

is not permitted without express written authority. Offenders will be
liable for damages. All rights, including rights created by patent grant
or registration of a utility model or design, are reserved. Technical
modifications possible. Technical specifications and features are
binding only in so far as they are specifically and expressly agreed
upon in a written contract.
1-183
Mr.M.Kaufmann
Author:
Martin Kaufmann
Department: ICM N OP ML CP 41
Review:
Jochen Gross
Release:
BR6.0
Date:
October. 2002
Proprietary data, company confidential.

All rights reserved.
Note:
This document is not official and is meant to be a quick reference,
training or background document for Siemens staff working on
the SBS database planning.
No guarantees for correctness of the contents!
The author will appreciate any comments for corrections or
improvements.
2-183
Mr.M.Kaufmann
Register contents:
1
Fundamentals of GPRS___________________________________________________5
Interfaces_______________________________________________________________6
2.1
Abis interface________________________________________________________________7
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.2
Gb interface________________________________________________________________33
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
3
3.1
Channel Configuration Overview______________________________________________51
4.1
4.2
Packet Common Control Channel PCCCH___________________________________________52

Packet Broadcast Control Channel (PBCCH) downlink only___________________________54
Packet Data Traffic Channels (PDTCH)_____________________________________________54
Packet Dedicated Control Channels________________________________________________55
Channel structure for PDCH______________________________________________________55
Channel Organisation in a Cell____________________________________________________57
Control Channel Configuration________________________________________________58

3.2.1
3.2.2
Physical Layer Protocol__________________________________________________________35

Network Service________________________________________________________________40
BSSGP Protocol________________________________________________________________49
Quality-of-Service______________________________________________________________50
Logical Link Control Functionality_________________________________________________50
Subnetwork Dependent Convergence Functionality____________________________________50
Channel Configuration__________________________________________________51
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.2
Temporary block flow (TBF)______________________________________________________10

TBF establishment initiated by MS on PCCCH_______________________________________12
TBF establishment initiated by the network on PCCCH________________________________19
Multiplexing MSs on the same PDCH______________________________________________21
Acknowledged mode for RLC/MAC operation________________________________________24
Unacknowledge mode for RLC/ MAC operation______________________________________31
Packet Common Control Channel__________________________________________________58

Packet Dedicated Control Channel_________________________________________________58
Logical Functions_______________________________________________________59
Network Access Control Functions_____________________________________________59
Mobility Management Functions_______________________________________________60
4.2.1
4.2.2
Mobility Management States______________________________________________________60

Location Management Procedure__________________________________________________61
4.3
Packet Timing Advance Feature________________________________________________61
4.4
System Information Management______________________________________________63
SBS Modifications______________________________________________________64
5.1
HW/SW Changes___________________________________________________________64
5.2
Operational sequence to configure a BSC for GPRS_______________________________67
5.3
HW/ SW Restrictions in the GPRS release_______________________________________68
6
6.1
Design of Radio cells____________________________________________________69

Cell (Re-) Selection__________________________________________________________69
6.1.1
6.1.2
6.1.3
GPRS Path loss criterion C1______________________________________________________70

Signal level threshold criterion C31________________________________________________71
Cell ranking criterion C32________________________________________________________73
3-183
Mr.M.Kaufmann
6.1.4
6.1.5
6.1.6
6.1.7
7
7.1
The MS shall make a cell reselection if:_____________________________________________74

Abnormal cell reselection________________________________________________________78
Network controlled reselection____________________________________________________79
Measurements reporting_________________________________________________________79
GPRS features BR5.5____________________________________________________80

Power Control______________________________________________________________80
7.1.1
7.1.2
7.1.3
MS output power_______________________________________________________________80
Measurements at MS side________________________________________________________81
BTS output power______________________________________________________________84
7.2
QoS (Quality of service)______________________________________________________84
7.3
Channel Coding_____________________________________________________________86
7.4
Timeslot Combining_________________________________________________________87
7.5
GPRS support on CCCH & PCCH_____________________________________________87
7.6
Discontinuous Reception (DRX)_______________________________________________88

7.6.1
7.6.2
DRX (Paging) on CCCH_________________________________________________________88

DRX (Paging) on PCCCH________________________________________________________89
8 GPRS BR 5.5 implementation aims__________________________________________90

9
Object Structure, SBS Parameter List_______________________________________91
10
Relevant GSM specifications______________________________________________98
11
GPRS features BR6.0___________________________________________________99
12
Abbreviations_________________________________________________________102
13
Appendix A___________________________________________________________104
14
Appendix B___________________________________________________________105
15
Appendix C (database example)___________________________________________106
16
Appendix D (command manual)_________________________________________125
11.1 Horizontalallocation ___________________________________________________________99

11.2 Transfer on non BCCH
TRX____________________________________________________100
4-183
Mr.M.Kaufmann
Fundamentals of GPRS
The General Packet Radio Service (GPRS) allows the packet data
transmission in GSM networks.
Up to now, the GSM network works in circuit switched connection mode,
that means, that the network gives the customer the exclusive use of a
certain amount of bandwidth for the duration of the requirement.
The connection is set up on demand and released when the caller ends
the connection.
Circuit switched connections are provided by the present GSM architecture
for speech and data services. Data transmission with bandwidth higher
than 9.6 kbit/s is reached by combining more radio channel to a specific
user with the feature High Speed Circuit Switched Data (HSCSD) principle.
If a user has nothing to send, which is typical of bursty data transmission,
the resource is wasted since is not available for other users. In other
words the circuit switched connection does not provide an efficient way to
support data traffic.
GPRS is introduced to support applications requiring bursty data
transfer.
In order to optimise the use of the network and radio resources,
GPRS uses a packet oriented technique to transfer high-speed
and low-speed data and signalling in an efficient manner.
New GPRS radio channels are defined, and the allocation of these
channels is flexible: From 1 to 8 radio interface timeslots can be allocated
per TDMA frame. Timeslots are shared by the active users, and uplink and
downlink channels are allocated separately.
The radio interface resources can be shared dynamically between speech
and data services as a function of service load and operator preferences.
Generally the packet network establishes a logical connection between
users but does not guarantee immediate access to the transmission
network: When more than one user try to access at the same
transmission resource at the same time, the network has to schedule the
access keeping some users in wait queue.
The common part between the GSM and GPRS networks is the radio
resources.
5-183
Mr.M.Kaufmann
Interfaces
The following picture gives a network overview over the GPRS architecture
and interfaces.
SMS-GMSC
SMS-IWMSC
SM-SC
C
Gd
MSC/VLR
HLR
D
Gs
Gr
Gb
MS
BSS
Um
SGSN
Gn
SGSN
Gc
Gi
PDN
GGSN
Gn
Gp
TE
Gf
EIR
GGSN
Other PLMN
Signalling Interface
Signalling and Data Transfer Interface
Figure 1
GPRS architecture, interfaces
SGSN =
GGSN =
Serving GPRS Support Node

Gateway GPRS Support Node
New interfaces and network elements are defined in the network. In the
new network architecture speech and data transmission with switched
connections are still controlled by the MSC (A interface). The GPRS
services are controlled by the Serving GPRS Support Node (SGSN), which
is a new network node specific for the GPRS network.
6-183
Mr.M.Kaufmann
Concerning the network elements in GR 1.0 the SGSN and GGSN are one
physical node. That means the following Interfaces are not supported in
GR1.0:
Gn-Interface between SGSN and GGSN

Gp-Interface from/to other PLMN
Gd-Interface to SMS-C
Gf-Interface to EIR
Gs-Interface to MSC/VLR
Gc-Interface to HLR
Abis interface
On the Abis interface between BSC and BTSE, GPRS data and Radio Link
Control (RLC) / Media Access Control (MAC) associated signalling
information are transferred via 16 kbit/s channels.
LLC
transmission
to SGSN
LLC
RLC
MAC
RLC
MAC
GSM RF
GSM RF
MS
L1bis
GSM RF
BTSE
BSC
Abis
Um
Figure 2 Protocol stack for data transmission in GPRS

GPRS supports the protocol stack specified in GSM Rec. 03.60.
The lower layers carry out the following functions:
GSM RF
The GSM RF is the physical radio channel used to transfer

packet data.
MAC
The Medium Access Control provides the access to the

physical radio resources. It is responsible for the physical
allocation of a packet data channels (PDTCH).
7-183
Mr.M.Kaufmann
RLC
The Radio Link Control layer provides a reliable link over the
air interface that fits the block structure of the physical
channel. Therefore it segments and re-assembles the LLC
frames. Additionally, it performs a sub-multiplexing to
support more than one MS by one physical channel and the
channel combining to provide up to eight physical channels
to one MS.
LLC
The Logical Link Control layer provides a logical connection

between MS and SGSN even if no physical connection is
established. The physical connection is set up by RLC/MAC
layer when there is data to transmit.
The mapping of different Layers is shown in the next figure:
LLC
Frames
RLC
Blocks
FH
BH Info F.
Information Field
BCS
BH
Info F.
BCS
FCS
BH
Radio Block
Normal B
Normal B
Normal B
Normal B
LLC
Layer
RLC/ MAC
Layer
Physical
Layer
Normal B = Normal Burst (1 TDMA frame)
Figure 3
FH = Frame Header
FCS = Frame Check Sequence
BH = Block Header
BCS = Block Check Sequence
transmission and reception data flow in GPRS
LLC frames (the logical connection between MS and SGSN) are variable in
length.
They will be hacked into packets and will be filled in RLC/MAC blocks. The
lenght of the RLC/MAC blocks (also called PCU frames) is fixed (320 bit).
How much the PCU frames will be filled with data is dependent on which
Coding Scheme is used.
8-183
Mr.M.Kaufmann
For example using CS-2, the PCU frame is completely filled with data,
using CS-1 the PCU frame is only partly filled with data and the rest stays
empty.
The decision to take which Coding Scheme can be read out of the
RLC/MAC block header.
Each PCU frame carriers one Radio Block. One Radio Block (RLC/MAC
Block) will be transmitted on the Air Interface via 4 Normal Bursts. These
Bursts belong to the same 52-Multiframe.
For GPRS, there exists two types of Radio Blocks: a Radio Block for data
transfer and for control messages (see figure 4).
There are two different Radio block structures:
Radio Block structure for data transfer:

Radio Block
MAC header
RLC header
RLC data
BCS
RLC data field contains octets from one or more LLC PDUs
The Block Check Sequence (BCS) is used for error detection.
Radio Block structure for control message:

Radio Block
MAC header
Figure 4
RLC/ MAC control message
BCS
Radio block: RLC/MAC Blocks
To ensure the right transmission order of RLC/MAC blocks, there is a Block

Sequence Number in each RLC/MAC block header.
The PCU frames (see Figure 6) which are transferred every 20 ms, via the
Abis are an extension of the known TRAU frames, defined in GSM 08.60
but they are not standardised by GSM.
9-183
Mr.M.Kaufmann
Within the control bits of the PCU frame the follwing information is
available:
Description
Bit C1
Uplink
0 : correct received frame
1 : erronous received or idle frame
Downlink
0 : non idle frame
1 : idle frame
Bit C2
0 : Coding Scheme 1
1 : Coding Scheme 2
0 : Coding Scheme 1
1 : Coding Scheme 2
Bits C3 - C8
RX_LEV
C3 : Parity - Pattern of the FN

( P0, P1,P2,P3 )
transmitted successive over 4
blocks
C4 : control of reception mode
0 : reception of NB
1 : reception of AB
C5 - C8 : power control
Bits C9 - C11
RX_QUAL
Uplink State Flag
Bit C12
spare
spare
Bits C13, C14
0 0 : no timing adjustment
0 1 : advance 250s
1 0 : delay 250s
1 1 : spare
both bits are used to perform

timing adjustment
Figure 5 C-bits of PCU frame
10-183
Mr.M.Kaufmann
Bit number
Octet no.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
1
0
0
1
C8
1
D11
1
D26
1
D41
1
D56
1
D71
1
D86
1
D101
1
D116
1
D131
1
D146
1
D161
1
D176
1
D191
1
D206
1
D221
1
D236
1
D251
1
D266
0
0
C1
C9
D4
D12
D19
D27
D34
D42
D49
D57
D64
D72
D79
D87
D94
D102
D109
D117
D124
D132
D139
D147
D154
D162
D169
D177
D184
D192
D199
D207
D214
D222
D229
D237
D244
D252
D259
D267
3
0
0
C2
C10
D5
D13
D20
D28
D35
D43
D50
D58
D65
D73
D80
D88
D95
D103
D110
D118
D125
D133
D140
D148
D155
D163
D170
D178
D185
D193
D200
D208
D215
D223
D230
D238
D245
D253
D260
D268
4
0
0
C3
C11
D6
D14
D21
D29
D36
D44
D51
D59
D66
D74
D81
D89
D96
D104
D111
D119
D126
D134
D141
D149
D156
D164
D171
D179
D186
D194
D201
D209
D216
D224
D231
D239
D246
D254
D261
D269
5
0
0
C4
C12
D7
D15
D22
D30
D37
D45
D52
D60
D67
D75
D82
D90
D97
D105
D112
D120
D127
D135
D142
D150
D157
D165
D172
D180
D187
D195
D202
D210
D217
D225
D232
D240
D247
D255
D262
D270
6
0
0
C5
D1
D8
D16
D23
D31
D38
D46
D53
D61
D68
D76
D83
D91
D98
D106
D113
D121
D128
D136
D143
D151
D158
D166
D173
D181
D188
D196
D203
D211
D218
D226
D233
D241
D248
D256
D263
D271
7
0
0
C6
D2
D9
D17
D24
D32
D39
D47
D54
D62
D69
D77
D84
D92
D99
D107
D114
D122
D129
D137
D144
D152
D159
D167
D174
D182
D189
D197
D204
D212
D219
D227
D234
D242
D249
D257
D264
C13
8
0
0
C7
D3
D10
D18
D25
D33
D40
D48
D55
D63
D70
D78
D85
D93
D100
D108
D115
D123
D130
D138
D145
D153
D160
D168
D175
D183
D190
D198
D205
D213
D220
D228
D235
D243
D250
D258
D265
C14
Figure 6 Standard PCU Frame

The databits D1 D271 of the PCU frame will be transferred within the
RLC/ MAC blocks.
Temporary block flow (TBF)
The MAC provides the establishment of a Temporary Block Flow (TBF),

which is a physical connection between one specific MS and the network
to support the unidirectional transfer of LLC Packet Data Units on packet
data physical channels.
The TBF is an allocated radio resource on one or more PDCHs and
comprise a number of RLC/MAC blocks carrying one or more LLC PDUs.
A TBF to/from the MS is maintained only for the duration of the data
transfer.
11-183
Mr.M.Kaufmann
Object/
Package
PCU
DB Name
Range
T3141
1 to 30 sec.
Meaning
This timer is started at network

side after TBF is setup and sent
Default: 5 sec. in the DL as a part of IMM_ASS
message and stopped after
successful contention
resolution.
Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The
TFI is assigned in a resource assignment message and will be stored in the
first octet of the RLC/ MAC block.
The TBF is identified by the TFI together with,
in case of a RLC data block:
The direction (UL or DL) in which the RLC data block is sent,
in case of a RLC/MAC control message:
The direction (UL or DL) in which the RLC/MAC control message is sent
and the message type.
The importance of the TFI can be understood when considering the
multiplexing of more MSs on the same PDCH (see chapter 2.1.4).
The TBF can be initiated by either the MS or the network (see next
chapter).
12-183
Mr.M.Kaufmann
TBF establishment initiated by MS on PCCCH
The purpose of the packet access procedure is to establish a TBF.

Whether a MS is authorised to do random access for request of a GPRS
service is dependent on the MS priority class defined on SIM card (as
higher the MS priority class, as more the network should take care of the
transmission quality).
Object/
Package
PTPPKF
DB Name
Range
Meaning
GPATH
PKANA,
PKAAP1PKAAP4,
Default=
PKAAP4
This parameter indicates whether

or not a mobile station of a certain
priority class is authorised to do a
random access for request of a
GPRS service.
GPRS Priority
ACCESS THR
Range:
PKANA
PKAAP1
PKAAP2
PKAAP3
PKAAP4
Value:
packet
packet
packet
packet
packet
access
access
access
access
access
is
is
is
is
is
not allowed in the cell

allowed for Priority Class
1
1 to 2
1 to 3
1 to 4
The MS shall initiate a packet access procedure by scheduling the sending

of PACKET CHANNEL REQUEST messages on the PRACH (Packet Random
Access Channel) corresponding to its PCCCH_GROUP and simultaneously
leaving the packet idle mode.
The PACKET CHANNEL REQUEST messages contains parameters required
to indicate the MS demand of radio resource and an indication of the type
of access.
The MS can access the GPRS network by using an 8-bit or 11-bit access
bursts on PDCH. The decision which access burst to use is done by the
network
with
sending
the
System
Information
Parameter:
Access_Burst_Type.
13-183
Mr.M.Kaufmann
Object/
Package
DB Name
Range
Meaning
PTPPKF
ABUTYP
ACBU8BIT,
ACBU11BIT,
This parameter indicates the type

of access burst used on uplink
PDCH.
Access_Burst_
Type
Default:
ACBU8BIT
See GSM 5.02

The 8-bit access on PRACH or RACH is used in case of PAGING
RESPONSE, CELL UPDATE, MM PROCEDURE and in all cases that the MS
requires to send no more information than the MS class and priority.
The 11-bit access on PRACH is used in all cases described for 8-bit
access but with additional information to be carried in the access phase,
e.g. an enhanced random reference number leading to less probability of
MS collision, when trying to establish an uplink TBF.
TBF establishment initiated by MS on PCCCH can use either the One

Phase Access or the Two Phase Access (with an additional Packet
Resource Assignment, see Fig. 7).
Note: It is also possible to establish a TBF initiated by MS on
CCCH!
TBF establishment initiated by MS on CCCH (see GSM 04.08 chapter
3.5.2) can also use either the One Phase Access (Fig. 8) or the Two
Phase Access (with an additional Packet Resource Assignment).
One phase access can be used for data like signalling messages were a
few blocks on one Timeslot are sufficient. Single block access is used for
messages that fit in one RLC/MAC block.
Two phase access has to be used when the Mobile requests more then 1
Timeslot or if it wants to use RLC unacknowledge mode.
a) With 1 phase access the Mobile can automatically requests only one
Timeslot.
b) 2 phase access means that the Mobile requests one single block in
Uplink. In this single block the Mobile can transfer a "Packet Resource
Request", requesting one or more Timeslots.
14-183
Mr.M.Kaufmann
The Mobile shall request 1 phase access if the purpose of the

access is to send a Paging Response, Cell Update, Signalling
Message for GPRS Mobility Managment (e.g. Attach Request) or
GPRS Session Managment (e.g. activate PDP context request).
The Mobile shall request single block access if it has to transmit only
one RLC/MAC control message like "Packet downlink Ack/Nack" or
"Packet measurement report".
-
If the Mobile has to transmit data in RLC unacknowledge mode, it

shall request single block access and attempt a 2 phase access. In
the following "Packet Resource Request" the Mobile shall indicate
RLC unacknowledged mode.
In one phase access the RLC mode defaults to acknowledged mode.
If the Mobile has to transmit data in RLC acknowledged mode it can
either request one phase access or two phase access e.g. if it needs
more timeslots.
The BSC is the master. Even if the Mobile requested one phase access the
BSC can force the Mobile to two phase access by assigning only a single
block in the IMMEDIATE Assignment.
MS
MS
BSS
BSS
Packet Channel Request
(Access type = two phase)
PRACH
Packet Uplink Assignment

(Single Block Allocation)
PAGCH
Packet Resource Request
PACCH
PACCH
RLC Data Block
PDTCH
SGSN
SGSN
Reassembling
RLC LLC
LLC
RLC Data Block
PDTCH
Packet Uplink Ack/Nack
PACCH
RLC Data Block
PDTCH
15-183
Mr.M.Kaufmann
Figure 7 Two Phase Access with Packet Control Channel (PCCCH)
MS
MS
BSS
Channel Request
(Access type = one phase)
RACH
Immediate Assignment
AGCH
RLC Data Block
PDTCH
SGSN
SGSN
Reassembling
RLC LLC
LLC
RLC Data Block
PDTCH
PACCH
RLC Data Block
PDTCH
Figure 8 One Phase Access with Control Channel CCCH

Object/
Package
PTPPKF
DB Name
Range
Meaning
GTXINT
0..15
This parameter defines the number

of slots to spread transmission of
the random access on PRACH
channel, but only if PCCCH is
used.
As higher the number of slots, as
lower is the probability of collision
of 2 MS when using PRACH.
If no PCCCH is configured, then
RACH is used automatically.
Default: 3
Range:
0
1
Value:
3 slots used to spread transmission
16-183
Mr.M.Kaufmann
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Object/
Package
PTPPKF
DB Name
Range
Meaning
GS
0..9
This parameter is used for the

calculation of the number of slots
between two successive Channel
request messages on PRACH
channel
Default: 8
Range:
0
1
2
3
4
5
6
7
8
9
Value
GS = 12
GS = 15
GS = 20
GS = 30
GS = 41
GS = 55
GS = 76
GS = 109
GS = 163
GS = 217
If there is no response to the PACKET CHANNEL REQUEST within a predefined time period, the MS initiates a retry.
Object/
Package
PTPPKF
DB Name
Range
Meaning
RAARET
TRUE
FALSE
If set to FALSE, this parameter

indicates that random access retry
17-183
Mr.M.Kaufmann
Random Access
Retry
Default:
TRUE
to another cell is not allowed. If the

field is set to TRUE, it indicates that
random access retry to other cell is
allowed.
When the MS initiates a packet access procedure and receives a Packet

Access Reject from the network, the MS has to wait until it receives the
Packet Uplink Assignment message or a timer in the MS (T3172) expires
and the MS returns to packet idle mode.
Caddie table handling for the PTPPKF object:
1. Open the PTPPKF table in the Editor window.
2. Fill in all project specific PTPPKF parameter values additionally to the
default PTPPKF values, which can be used from the standart table.
Each BTS, which should support GPRS must be filled with a separate
PTPPKF line in the PTPPKF table.
18-183
Mr.M.Kaufmann
19-183
Mr.M.Kaufmann
Object/
Package
PCU
DB Name
Range
T3172
0..255
Timer on MS
side
Start T3172:
Meaning
Wait for Packet Uplink Assignment

after Packet Access Reject
Default: 5sec. message has been received.
Start T3172
On receipt of a
Packet Access
reject message
Stop T3172:
Stop T3172
When On receipt of
a Packet Uplink
Assignment
message
T3172 Expired
Action at expiry:
Packet access in the
cell no longer
prohibited
Figure 9 Timer 3172 on MS side

After the MS has made a Packet Channel Request to the network, the
network responds on PAGCH (Packet Access Grant Channel) or AGCH and
sends a Packet Uplink Assignment to the MS including the USF for that
particular MS.
An Uplink state flag USF sent from the Packet Control Unit (PCU) is
included in the header of each RLC/MAC block on a downlink PDCH.
20-183
Mr.M.Kaufmann
Uplink Packet Transfer
The MS monitors the USFs on the allocated PDCHs and transmits Radio
Blocks on those, which currently bear the USF value reserved for the
usage of the MS.
TBF establishment initiated by the network on PCCCH

Packet Paging
Paging for GPRS are performed on Routing Area instead ones of

standard GSM that are done on Location Area. The routing Area
information element consists out of MCC (Mobile Country code), MNC
(Mobile network code), LAC (Location Area code) and RAC (Routing Area
Code) GSM 04.08 chapter 10.5.5.15.
The network initiates packet transfer to an MS that is in Standby-state by
sending a Packet Paging Request on the downlink PPCH (Packet Paging
Channel) or PCH. The MS responds to the Packet Paging Request by
initiating a procedure for paging response. After the Packet Paging
response, the mobility management-state of the MS is in Ready-state.
MS
MS
BSS
BSS
SGSN
Paging_PS
Packet Paging
PPCH

RLC (TLLI)
PRACH
PAGCH
PDTCH
LLC
LLC
Packet Downlink Assignment
PACCH
RLC Data Block
PDTCH
RLC Data Block
.
Segmentation
LLC RLC
PDTCH
Packet Downlink Ack/Nack
PACCH
RLC Data Block
PDTCH
21-183
Mr.M.Kaufmann
Figure 10
Packet Paging with GPRS Control Channels
Three network operation modes for paging procedures are defined:

Mode
I
II
III
Circuit
Paging GPRS Paging Channel
Channel
Packet Paging Channel Packet Paging Channel
standby)
CCCH Paging Channel
CCCH Paging Channel
standby)
Packet Data Channel 1) Not Applicable 2)
ready)
CCCH Paging Channel
CCCH Paging Channel
standby)
CCCH Paging Channel
Packet Paging Channel
standby)
CCCH Paging Channel
CCCH Paging Channel
standby)
(GPRS
MS
(GPRS
MS
(GPRS MS
(GPRS
MS
(GPRS
MS
(GPRS
MS
1) In GPRS MM ready state (TBF is set up): If MS receives now a signalling

for a circuit switched incoming call. Then circuit switched Paging can be
done via Packet Data Channel (PACCH)
2) In GPRS MM ready state (no TBF is set up or e.g. an UL TBF exists and
the network wants to establish a DL TBF), the network does not carry out
the paging procedure in order to establish TBF, it simply sends IMMEDIATE
ASSIGNMENT message in the MSs paging subgroup. In this way it
eliminates lots of extra messages (packet paging request and paging
response since the purpose of this two messages is only to locate the
exact cell location of the MS while in the Ready state the SGSN knows the
MS by cell).
Paging in GSM MM ready state is only to initiate circuit swich
service while MS is packet attached (Class A&B Mobile), since the SGSN
have more exact location info of MS.
General: If in GPRS MM ready state (TBF is set-up): another Packet
service request comes in, the network will notify the other party the MS as
busy. Its up to the network to decide if it wants to hold or simply rejects
the request. The MS will only request one TBF in Uplink.
It is unclear, how the network reacts when it has to download data from
different sources. But depending on it's capability a Mobile can activate
several PDP contexts, that means different applications might run in
parallel.
22-183
Mr.M.Kaufmann
Comment to Mode I: A MS needs only to monitor one Paging Channel.

GPRS MS will always be paged via SGSN, nevertheless whether a circuit
switched service or a GPRS service shall be set up (Gs Interface has to
exist).
Comment to Mode II: A MS needs only to monitor the CCCH paging
channel, but that circuit-switched paging continues on this paging channel
even if the MS has been assigned a packet data channel.
Comment to Mode III: A MS that wants to receive pages for both circuitswitched and packet-switched services shall monitor both paging channels
if the packet paging channel is allocated in the cell.
In NMO II and NMO III CS-paging will be sent from the MSC via SS7 link to
the BSC and GPRS paging will be sent from SGSN via Gb-interface to the
BSC.
Object/
Package
DB Name
PCU
NMO
Range
NMO_1
NMO_2
Network mode of NMO_3
operation
Default:
NMO_2
Meaning
Network mode of operation
For proper operation the mode
of operation should be the
same in each cell of a routing
area.
Downlink Packet Transfer

Transmission of a packet to an MS in the Ready state is initiated by the
network using the Packet downlink Assignment message (see figure 11).
In case there is PCCCH allocated in the cell, Packet Downlink Assignment
is transmitted on PAGCH, otherwise on AGCH.
The Packet Downlink Assignment message includes the list of PDCHs that
will be used for downlink transfer, the timing Advance, the TFI and Power
Control information is also included.
The network sends the Radio blocks belonging to one TBF on downlink on
the assigned downlink channels.
Multiplexing MSs on the same PDCH
UPLINK
23-183
Mr.M.Kaufmann
After the MS has made a Packet Channel Request to the network, the
network sends a Packet Uplink Assignment to the MS inclulding the USF
for that particular MS.
An Uplink state flag (USF) sent from the Packet Control Unit (PCU) is
included in the header of each RLC/MAC block on a downlink PDCH.
The MS monitors the USFs on the allocated PDCHs and transmits Radio
Blocks on those which currently bear the USF value reserved for the usage
of the MS.
The USF flag is used by the network to control the multiplexing of
different MS on uplink PDCH (to prevent collision on uplink channel).
24-183
Mr.M.Kaufmann
Object/
Package
PCU
PCU
DB Name
Range
N3101
9..255
Meaning
The network will increment counter

N3101 for each USF for which no
= Counter on
Default: 10
data is received from the MS. In
the network side
case the threshold of N3101 is
reached, the communication with
the associated MS is broken.
When the network after setting
USF, receives a valid data block
from the MS it will reset counter
N3101.
T3169
1 to 30 sec.
This timer defines the waiting time
for reuse of the TFI and USF after
= Timer used on Default: 1 sec. the thresholds N3101(see above)
the network side
or N3103 (see chapter 2.1.5) are
reached.
N3101 = e.g. 2
N3101 + 1 = 3
NW sends USF
N3101 + 1 = 4 =
threshold ->
communication with
MS is broken
NW sends USF
NW has no data
received from MS
=>Timer T3169 Starts

NW has no data
received from MS
T3169 expired, now reuse of TFI,

USF
Figure 11 Reuse of TFI,USF in UL Packet Transfer
25-183
Mr.M.Kaufmann
N3101 = e.g. 2
N3101 + 1 = 3
NW sends USF
NW sends USF
NW has no data
received from MS
NW has received
data from MS
N3101 => Reset to 0
Figure 12 NW receives data from MS

DOWNLINK
Multiplexing the Radio Blocks destined for different MSs on the same
PDCH downlink is enabled with an identifier, TFI, included in each Radio
Block.
The network initiates packet transfer to an MS that is in Standby state by
sending a Packet Paging Request on the downlink PPCH (Packet Paging
Channel) or PCH.
The MS answers with a Packet channel Request on PRACH to the network.
The network sends a Packet downlink assignment on PAGCH to the MS
including the TFI.
From there on the MS monitors all TFI on the allocated PDCH, as soon as it
detects its own TFI, it knows that the Radio Block received is the Radio
Block for that particular MS.
The TFI is assigned in a resource assignment message and will be stored
in the first octet of the RLC/MAC block.
26-183
Mr.M.Kaufmann
Acknowledged mode for RLC/MAC operation
The transfer of RLC data blocks in the RLC acknowledged mode uses
retransmissions of RLC data blocks. The transmitting side numbers the
RLC data blocks via the block sequence number (BSN). The BSN is used
for retransmission and for reassembly. The receiving side sends PACKET
Ack./ Nack messages in order to request retransmission of RLC data
blocks.
The decision wether to use Acknowledged or Unacknowledged Mode on
upper layers depends on the applications used (e.g. access on internet
normaly with unacknowledged mode).
Uplink Temporary Block flow/ Release of Uplink TBF
The MS shall transmit an RLC/MAC block in each assigned uplink data

block. The network shall send PACKET UPLINK ACK/NACK messages when
needed.
MS
MS
BSS
RACH
Immediate Assignment
AGCH
RLC Data Block
PDTCH
Channel Request
(Access type = one phase)
SGSN
Reassembling
RLC LLC
LLC
PDTCH
PACCH
RLC Data Block
PDTCH
RLC Data Block
RLC Data Block (CV=0)
PDTCH
LLC
(Final Ack = 1)
PACCH
Packet Control Acknowledge
PACCH
27-183
Mr.M.Kaufmann
Figure 13 Uplink Temporary Block Flow (One Phase Access)

There is a timer T3182, used on the MS side to define when to stop
waiting for temporary Packet Uplink Ack./Nack. After the last RLC data
block has been sent for the current send window or for the entire
Temporary Block Flow.
28-183
Mr.M.Kaufmann
Object/
Package
PTPPKF
PTPPKF
PTPPKF
N3102 = 0
DB Name
Range
Meaning
PKTNDEC
0..7
See GSM 4.60
Default:2

of decrement for counter N3102
performed if the T3182 expires
without reception packet Uplink
ACK/NACK. It is used for RLC layer
at MS side.
PKTNINC
0..7
See GSM 4.60
Default:2
PKTNMA
0..7
See GSM 4.60
Default: 4

of increment for counter N3102
performed after receiving packet UL
ACK/NACK. It is used for RLC layer
at MS side.
This parameter defines the
maximum value for counter N3102.
If N3102 reach 0 or less than 0, a
RLC abnormal release shall be
performed.
N3102 = 0 + PKTNINC
N3102 = 2 + PKTNINC
N3102 = 0 + 2
N3102 = 2 + 2
T3182 starts
when RLC/MAC
block was sent
from MS to NW
N3102 = PAKTNMA
N3102 = e.g. 20
T3182 starts
...
For the next increment of

N3102,
N3102 will remain at
PAKTNMA!
T3182 stops
with receiving
UL Ack /Nack
from NW
T3182 expires
without UL Ack.
/Nack.from NW
T3182 expires
without UL Ack. /Nack.from NW
Figure 14 MS receiving UL Ack./Nack within TBF

29-183
Mr.M.Kaufmann
N3102 = e.g. 4
N3102 = 4 - PKTNDEC
N3102 = 2 - PKTNDEC
N3102 = 4 - 2
N3102 = 2 - 2 = 0
T3182 starts
when RLC/MAC
block was sent
from MS to NW
N3102 = 0
T3182 starts
T3182 expires
when no UL Ack.
/Nack. is received
from NW
MS shall perform an
abnormal release,
return to the CCCH
or PCCCH and
initiate establishment
of new uplink TBF.
T3182 expires
when no UL Ack. /Nack. is received from NW
Figure 15 MS not receiving UL Ack./Nack within the TBF

If PAKTNDEC or PAKTNINC or PAKTNMA are set to zero the N3103 counter
shall be disabled by the MS.
If the network has received all RLC data blocks when it detects the end of
the TBF, it shall send the Packet UPLINK ACK/NACK message with the Final
Ack Indicator bit set to 1. Include a valid RRBP field in the RLC/MAC
control block header and clear counter N3103.
The RRBP value specifies a single uplink block in which the MS shall
transmit either a Packet control acknowledgement message or a PACCH
block to the network.
The relative reserved block period (RRBP) field is defined within the
header field of the RLC/MAC block structure.
If the NW has not received all of the RLC data blocks when it detects the
end of the TBF, it shall send a PACKET UPLINK ACK/NACK message to the
MS and if necessary allocate sufficient uplink resources for the MS to
retransmit the required RLC data blocks.
Within the final packet uplink acknowledge, all not correctly received
blocks are listed. For each MS priority level 1 to 4 (defined on SIM card)
the maximum number of retransmission allowed for each faulty block is
defined by GMANRETS.
30-183
Mr.M.Kaufmann
Object/
Package
PTPPKF
DB Name
Range
Meaning
GMANRETS
0..3.,0..3,0..3, This parameter indicates for each

0..3
priority level 1 to 4 the maximum
number of retransmission allowed
Priority level P1: highest
Priority level P4: lowest
For each priority level P1 to P4 the following table should be applied:

P1
P2
P3
P4
1
2
4
7
retransmission
retransmission
retransmission
retransmission
allowed
allowed
allowed
allowed
If the Packet UPLINK ACK/NACK message has the Final Ack Indicator bit set
to 1, the MS shall transmit the PACKET CONTROL ACKNOWLEDGEMENT
message and release the TBF.
When the NW receives the PACKET CONTROL ACKNOWLEDGEMENT
message in the radio block indicated by the RRBP field, it may reuse the
TFI and USF resources.
Object/
Package
PTPPKF
DB Name
Range
Meaning
CACKTYP
0..1
This parameter indicates the format

of the PACKET CONTROL
ACKNOWLEDGEMENT the MS
shall transmit when polled:
0 = PACKET CONTRL ACK format
is four access bursts
1 = PACKET CONTRL ACK format
is RLC/MAC control block
Control Ack Type Default: 0
31-183
Mr.M.Kaufmann
PCU
N3103
1..255
Counter on
Network side
Default: 10
N3103 = e.g. 3
N3103 + 1 = 4
NW waits for
Packet Control
Ack.
This parameter implements the

threshold for not received PACKET
CONTROL ACK as answer of the
PACKET UPLINK ACK/NACK. In
case this threshold is reached, the
communication with the associated
MS is broken.
N3103 + 1 = 5 =
threshold ->
communication with
MS is broken
Retransmission
Packet UL
Ack/Nack
NW has not
received a Packet
Control Ack in
the scheduled
block
=>Timer T3169 Starts

No packet control Ack. Received,
Timer T3169 Starts
T3169 expired, now reuse of TFI,

USF
Figure 16 NW receives no Packet Control Ack.

Note: N3103 is reset when transmitting the final PACKET UL ACK/NACK
messages within a TBF (final Ack indicator set to 1)
The RLC timer T3198 is an array of 64 timers used by the MS to control
when it will accept a NACK for an RLC data block.
Object/
Package
PTPPKF
DB Name
Range
Meaning
BSCDVMA
1..15
See GSM 4.60
Default: 15
This parameter represents the

value of timer T3198, at MS side,
expressed in number of RLC blocks
32-183
Mr.M.Kaufmann
DL Temporary Block flow/ Release of a Downlink TBF

The MS receives RLC/MAC blocks on the assigned downlink PDCHs. On
each assigned PDCH, the MS shall in the RLC header identify the TFI and
decode the RLC data blocks intended for the MS.
MS
MS
BSS
SGSN
Paging_PS
Packet Paging
PPCH
PRACH
PAGCH
RLC (TLLI)
PDTCH
LLC
PACCH
RLC Data Block
PDTCH
Packet Downlink Assignment
PDTCH
PACCH
RLC Data Block
PDTCH
RLC Data Block
Segmentation
LLC RLC
LLC
RLC Data Block (FBI = 1)
PDTCH

(Final Ack = 1)
PACCH
Figure 17 DL Temporary Block flow/ Release of a DL TBF

The NW initiates release of a downlink TBF by sending an RLC data block
with the Final Block Indicator (FBI) set to the value 1 and with a valid
RRBP field. The NW shall start timer T3191.
The timer T3191 is used on the network side to define when the current
assignment is surely invalid on the MS side so that the TFI can be reused.
Its value is network dependent.
33-183
Mr.M.Kaufmann
Start T3191:
Start T3191
When NW sends last RLC data

block with FBI = 1 to MS
Stop T3191:
If NW receives a Packet DL
Ack./ Nack. M essage before
T3191 expires
If retransmission
required, then NW
retransmitts
neccessary RLC data
blocks
Stop T3191
If no retransmission
required, NW shall stop
timer T3191 and start
T3193, when T3193
expires, NW shall release
TBF.
T3191
Expired, NW
release TBF
Figure 18 Timer T3191 on network side, defines TFI reuse

Object/
Package
PCU
PCU
DB Name
Range
T3191
1 to 30 sec.
On network side

for reuse of the TFI and USF after
Default: 5 sec. having sent the last RLC block
T3193
1 to 42
Default = 4
PCU
Meaning
N3105
1..255
Counter on
Network side
Default: 10
34-183

for reuse of TFI after reception of
the final Packet Downlink
Ack./Nack. from the MS.
This parameter implements the
threshold for not received
RLC/MAC control message from
the MS after sending a RRBP field
on downlink. If this threshold is
reached, the communication with
the associated MS is broken
Mr.M.Kaufmann
N3105 = e.g. 3
N3105 + 1 = 4
NW sends RRBP
filed in the DL
RLC data block
NW sends RRBP
filed in the DL
RLC data block
Value N3105 max

is network
dependent, then
communication
with associated MS
is broken
NW has not
received a valid
RLC/MAC
control message
from MS
NW has received a valid
RLC/MAC control message
from MS
=>N3105 Reset
Figure 19 NW receives RLC/MAC control messages

Unacknowledge mode for RLC/ MAC operation
The transfer of RLC Data Blocks in the unacknowledged mode is controlled

by the numbering of the RLC Data Blocks within one Temporary Block Flow
and does not include retransmission.
The receiving side extracts user data from the received RLC Data Blocks
and attempts to preserve the user information length by replacing missing
RLC Data Blocks by dummy bits.
Only on the end of the TBF there is a single Ack/Nack message sent which
includes the blocks which where not received correctly,
Object/
Package
PCU
DB Name
Range
Meaning
NRLCMAX
20..64
N_RLC_MAX
Default:20
When N_RLC_MAX Uplink RLC

Block are received, one PACKET
UPLINK ACK/NACK is sent in
unacknowledge mode
35-183
Mr.M.Kaufmann
After the end of a Temporary Block Flow, the MS is able to release the
connection between MS and BSC with the Control Acknowledge message
(on PACCH).
Medium Access modes
There are two Medium Access Modes:

Dynamic allocation or Fixed allocation. With GR1.0 only Dynamic
allocation access mode is supported.
Dynamic Allocation
The Packet Uplink Assignment message includes the list of PDCHs and the
corresponding USF value per PDCH. A unique TFI is allocated and is
thereafter included in each RLC Data and Control Block related to that
TBF.
Dynamic allocation is characterised by that the MS monitors the USFs on
the allocated PDCHs and transmits Radio blocks on those, which currently
bear the USF value reserved for the usage of the MS.
Fixed Allocation
Fixed allocation is characterised by fixed allocation of radio blocks and
PDCHs in the assignment message without an assigned USF.
36-183
Mr.M.Kaufmann
Caddie table handling for the PCU object:

1. Open the PCU table in the Editor window.
2. Fill in all project specific PCU parameter values additionally to the
default PCU values, which can be used from the standart table.
37-183
Mr.M.Kaufmann
Gb interface
The Gb interface is connecting the BSS-BSC to the SGSN transferring
signalling information and user data. Several BSS-BSCs may be interfaced
to one SGSN on the Gb interface. A user is allocated resources upon
activity (i.e. when data is either sent or received), however the resources
are reallocated when the activity ends. This approach is different to the Ainterface where a user is dedicated a resource throughout the call
irrespective of activity.
SNDCP
RLC BSSGP
BSSGP
MAC
NS
NS
New TRAU
frame
L1
L1
BSC/PCU
GTP
LLC
LLC Relay
Gb
L2
L1
SGSN
Figure 20 The Gb Interface

The various layers realise the following functions:
L1
GSM 08.14 specifies Layer 1 of the Gb interface. Frame Relay
(FR) will be used for phase 1 GPRS.
Network
38-183
Mr.M.Kaufmann
Service
The Network Service (NS) performs transport of NS Service

Data Units (SDU) between the SGSN and BSS. The Gb
interface is based on FR as specified in GSM 08.16. FR
supports high rate data transmission with low delay. Frames of
different sizes may be transmitted. FR performs congestion
control and error detection, however error correction is not
supported.
BSSGP
Primary functions of the Base Station Subsystem GPRS

protocol (BSSGP) are providing connection-less link between
the SGSN and BSS (layer 2 level), providing tools for bidirectional control of the data flow and handling paging
requests from the SGSN to the BSS.
LLC
The Logical Link Control layer (LLC) provides logical links

between an MS and a corresponding SGSN. The transport of
both data and signalling is supported.
SNDCP
SubNetwork Dependent Convergence Protocol (SNDCP)

supports a direct peer to peer (i.e. point-to-point)
communication between an MS and a SGSN. User data is
transported from a network layer protocol, e.g. IP or X.25.
The NS layer of the Gb interface is split into a Network Service Control

part and a Sub Network Service part as indicated in figure 21. The Service
Control part is independent from the physical realisation of the network,
whereas the Sub-Network Service entity is the Frame Relay.
LLC Relay
RLC
BSSGP
Network Service
Layer
Network Service
Control
MAC
Sub Network Service

FRAME RELAY
Network Service
Control
L1
PCU
Figure 21 Frame Relay realisation on the Gb interface.

Physical Layer Protocol
The Gb Physical layer is specified in GSM 08.14. Depending from the
configuration of E1 (PCM30) or T1 (PCM24) a channel can be:
39-183
Mr.M.Kaufmann
Unchannelized, i.e. the entire E1/T1 line is considered as a channel (i.e.

the whole bit stream).
Fractional, i.e. only a part of the bit stream is defined as a channel. The
channel may contain groupings of adjacent and/or spaced time slots. In
figure 22 the fractional channel contains adjacent TSs only.
Channelized, i.e. the E1/T1 line contains multiple channels where a
channel may contain a subset of adjacent and/or spaced time slots.
(I.e. the bit stream contains different channels).
The three approaches are illustrated in figure 22. The TSs are numbered 0
to 31. TS0 is used for synchronisation purposes.
TS 31
3
1
3
0
2
9
2
8
Unchannelized ("1 stream")

2
7
1
7
1
6
1
5
1
2
1
1
1
0
1 0
5 4
3 2
1 0
1 0
Fractional (1 stream, defined number of timeslots )

3 3 2
1 0 9
2
8
2
7
2
4
2 2
3 2
1 1
7 6
1
5
1
2
1 1
1 0
9 8
7 6
Channelized (groups single timeslots together )

3
1
3
0
2
9
2
8
2
7
2
4
2
3
2
2
1
7
1
6
1
5
stream 1
1
2
1
1
1
0
stream 2
Figure 22 Channel time slot allocations.

Realisation of the Physical Layer
In principle four types of configurations are possible in connecting the
GPRS entities on the Gb interface:
1. A direct line (e.g. PCM30) is connecting the PCU and SGSN. (Static and
permanent physical point-to-point).
2. Through FR network.
40-183
Mr.M.Kaufmann
3. Nailed Up Connection (NUC) through MSC via FR. Dependent from the
configuration (i.e. number of GSM channels) any spare DIU ports may
be used for NUC. There may be 31x64kbit/s Permanent Virtual
Connections (PVC) on one port in the case of an E1 line.
4. NUC through MSC.
SGSN
Network
Router
BSC
Transit
Network
Gb
SGSN
FR - Network
Network
Router
MSC
Network
Router
Gb
Gb
BSC
BSC
Figure 23 Various approaches in connecting a BSC to SGSN
41-183
Mr.M.Kaufmann
Object
PCMG
PCMA
DB name Range
PCML
Meaning
This attribute identifies the LICD
number, the CIRCUIT number
and the TRUNK (A or B) to which
the PCM line is connected (i.e.
QTLP).
CRC
TRUE, FALSE,
This attribute indicates if CRC-4
Default = FALSE
signal handling for PCM 30 line
or CRC-6 signal handling for
PCM 24 line is Enabled on
PCMG line. Values are FALSE or
TRUE.
CODE
AMI, HDB3, Default =
This attribute selects the line
HDB3
transmission code to be provided
on the line. Values are AMI or
HDB3.
NUA
TRUE, FALSE, Default = This attribute enables or
FALSE
disables handling of not urgent
alarms on PCMG line.
BER
0 = up to 10-3 BER value Bit Error Rate indicates the
1 = 10-3 .. 10-4 BER
threshold that, if exceeded, the
value
line must be put in Disabled.
2 = 10-4 .. 10-5 BER
value Default value: 0
BAF
0 .. 255, Default = 0
This attribute defines frame
alignment bits that can be set by
operator.
LOWBER 0 = 10-3 Bit Error Rate Lower Bit Error Rate. This
(BER) value
attribute is relevant only for
1 = 10-4 BER value
PCM24 lines
2 = 10-5 BER value
3 = 10-6 BER value
4 = 10-7 BER value
5 = 10-8 BER value
6 = 10-9 BER value
Default value: 3
REMAL
0 = CCITT
Remote alarm type. This
1 = Bellcore
attribute is relevant only for
Default value:0
PCM24 lines
PCMA
PCMA-line number on the Ainterface.
0..8
0..3
No FR equipment is used when connecting the BSC to the SGSN via a

direct line (either PCM30 or PCM24 connected to the BSC line interface
42-183
Mr.M.Kaufmann
card). In this case the time slots may be unchannelized, fractional and
channelized dependent from the configuration of the PVC. A special case
is when using channelized mode where the different channels belong to
different destinations. In this case the traffic must be separated between
the end users of the PVC. A PVC is an end-to-end connection through the
FR network.
When using a PCM30 line the MSC can be used in separating the traffic to
different destinations. (A total maximum rate of 2 Mbit/s is possible on the
PCM30 line). It is emphasized that in this case the carrier must be divided
into single 64 Kbit/s channels since a Siemens MSC does not permit
switching more than one time slot synchronously. Generally if NUC
through a Siemens MSC is used on the Gb interface, then only one time
slot of E1 (or T1) can be used. (It is not possible to re-assemble
information on the FR layer when the time slots are not bit-synchronous).
Although it is impossible to use a PVC over more than one time slot it is
possible to provide higher bandwidth by creating more PVCs for a
connection (i.e. multiple PVCs of one TS each). Theoretically the
maximum number of PVCs per GSN is 65536.
A FR network supports unchannelized, fractional and channelized time
slots and FR switching.
43-183
Mr.M.Kaufmann
Caddie table handling for the PCMG object:

1. Open the PCMG table in the Editor window.
2. Fill in all project specific PCMG parameter values additionally to
the default PCMG values, which can be used from the standart
table.
44-183
Mr.M.Kaufmann
Network Service
The Network Service layer is specified in GSM 08.16. The NS layer
provides a reliable connection within the FR network. Referring to figure
21 the NS SDUs coming from the BSSGP layer are transported between NS
entities of the BSC/PCU and SGSN. A virtual connection on the BSSGP
layer (BVC) corresponds to one or more NS Virtual Connections (NSVC)
permitting a load sharing function between NSVCs. Error detection is
performed, however error recovery is supported by the upper layers. As
previously explained the NS layer is split into a Network Service Control
part and a Sub Network Service part.
NS Sub Network Service
The NSVC provides end-to-end communication between the BSC/PCU and
SGSN irrespective of the exact configuration of the Gb interface. The
NSVC is identified by a NSVC Identifier (NSVCI). Referring to figure 24
there is a set of principles that apply to the Gb FR network:
The physical link is the Frame Relay bearer channel. (Allocated TSs
in either a direct line or a FR network).
The FR PVC provides an end-to-end connection through the FR
network. The Network Service Virtual Link (NSVL) is the local link in
one end, i.e at the User Network Interface (UNI) of the FR PVC.
45-183
Mr.M.Kaufmann
The Data Link Connections (DLC) defines the entry point to the FR
network. A DLC is identified with a DLC Identifier (DLCI).
The Network Service Virtual Link Identifier (NSVLI) is the DLCI
together with the bearer channel identifier. A physical link supports
one or more NSVLs which again is identified by a NSVLI.
The NSVC is the FR PVC.
NSVL at BSS side End-to-end
NSVC
NSVL at SGSN side
SGSN
BSC
PCU
FR
Network
DLCI
BSS side
DLCI SGSN side

(Entry point into FR
network)
Figure 24 Gb interface with a Frame Relay network

Generally the DLCIs of the NSVC are different on the BSS side and on
the SGSN side. The configuration of the FR Network is a network provider
responsibility. The interconnections must be established at subscription
time.
The creation of a NSVC may be as follows (Ref figure 25):
Database Object:
NSVC-0
Parameters for NSVC-0:

network
(Defining the end-to-end connection

between the SGSN and the BSC/PCU)
NSVCI=5
(Internal identifier of the FR
connecting each side of the network)

NSVLI=0-111 (FR object 0, DLCI 111. Local
connection at
BSC/PCU side. Similarly a NSVL must
be
defined at the SGSN side)
46-183
Mr.M.Kaufmann
End-to-end NSVC
(NSVCI=5)
BSC
BSC
Intermediate
transmission
network
NSVL at BSS side

NSVLI=0-111 (FR object 0, DLCI 111)
SGSN
SGSN
NSVL at SGSN side
Figure 25: Creation of a NSVC in the database.

Examples of configuration commands in the GPRS database are given in
Appendix A. The database commands specify each of the physical Gb
realisations shown in figure 23.
When a physical link is used in connecting a BSS and SGSN the NSVCI
must have the same value at the SGSN side and BSS side.
Object
NSVC
DB name
NSVCI
NSVLI
Range
Meaning
0..65535 This parameter represents the common
identification of the virtual connection
between SGSN and BSS
0..31
This attribute defines the association of
16..991
the FR-DLCI and the FRL. Two levels of
identification are provided for this
attribute: the first one is the FRL and the
second one DLCI .
The mapping of the DLCI parameter is as follows:

0
In channel signalling
1-15
Reserved
16-511
Available for user information
512-991
Available for user information
NS-SDUs are transmitted across the Gb interface by means of Packet Data
Units (PDU).
Object
FRL
DB name
GLK
Range
Meaning
PCMA_0..143, This attribute with the value PCMA_X or
PCMG_0..11 PCMG_X define the type of a line and the
number of the line for the connection between
SGSN and PCU. Mixed configurations A-int or
47-183
Mr.M.Kaufmann
GTS
1..31
PCUN
0..5
G-int are admitted. This means that it is

possible to create some FRL links on the
PCMA interface and some other on the PCMG
This attribute defines the 64 kbit/s time slot
(maximum 31 time slots) reserved for this
specific FRL. Either the A- interface or Ginterface is specified with the parameter GLK.
Definition to which PCU number the FRL is
connected
Additional parameters related to FRL are described in succeeding

sections.
Adressing
As stated before the NSVC provides end-to-end connection between the
BSS and SGSN irrespective of the configuration of the Gb interface. Due to
load sharing more than one NSVC may be configured to transfer the traffic
between two entities. The NSVC Group groups together the NSVCs that
provide communication between the same entities. The Network Service
Entity Identifier (NSEI) has been introduced to identify the groups of
NSVCs. The NSEI has an end-to-end significance across the Gb interface.
A BVC is supported by one group of NSVCs. However a group of NSVCs
supports one or more BVCs. A BVC is used to transport NS SDUs between
NS users.
Each BVC is identified by a BVC Identifier (BVCI) which has an end-to-end
significance across the Gb interface. The BVCI together with the NSEI
uniquely identifies a BVC within an SGSN. The BVCI and NSEI are used on
the NS Service Access Point (NS-SAP) for layer-to-layer communication.
Object
PCU
DB name
NSEI
Range
0..65534
Meaning
NSEI represents the PCU area identification.
The attribute can be set only if the object PCU
is in Locked state.
48-183
Mr.M.Kaufmann
Core Functionality
Only PVCs are implemented on the Gb interface. L1 (the Physical layer)
must be permanently active, while a channel must be established at
subscription time. Core functions of the NS Sub Network Service include
data link functions which are required for routing and relaying. However
most functions associated with sequencing, error detections, error
recovery and flow control are excluded. Figure 26 illustrates the format of
the frames across the FR. The FR structure is defined in ITU-T Q.922.
Referring to figure 26 the core functions include:
Delimiting, alignment and transparency using the Flag field.
Multiplexing/de-multiplexing using the Address field.
Error detection (to some extent) using the Frame Check Sequence
(FCS) field.
Congestion control using the Forward Explicit Congestion Notification
(FECN), Backward Explicit Congestion Notification (BECN) and Discard
Eligibility (DE) fields.
Flag
Address
Field
Upper DLCI
Lower DLCI
FE
CN
Octet 1
CR
EA
0
EA
1
Octet 2
BE
DE
CN
Octet 3
Octet 4
Frame Relay
Information
Field
.
Octet n-3
Flag
FCS
Octet n-2
FCS
Octet n-1
Octet n
Figure 26 FR Structure
Congestion control is a joint responsibility of the network and the end
users. The network may monitor the degree of congestion, whereas the
end users are in the best position to control congestion by limiting the
traffic flow. The Network generates congestion notification to the source
end user and/or the destination end user by means of:
FECN in forward direction.
BECN with reverse traffic.
It is emphasised that congestion control by means of FECN and BECN is
not realised in release GR1.0 of the BSC/PCU. These bits are set to 0
according to GSM 08.16.
49-183
Mr.M.Kaufmann
Object
FRL
DB name
TCONG
Range
1..30
Meaning
TCONG specifies the observation window for
the congestion detection. If the number of
frames coming from the SGSN indicating
congestion is equal or greater than the
number of frames indicating no congestion
within the specified window size, the
congestion state is notified to upper layers.
TCONGs range is from 1 to 30 seconds,
Default value is 10.
TCONOFF
0,10..30
Time Congestion Off: Specifies the window for

congestion abatement. After a congestion
notification, no other notifications are foreseen
for the time configured by this parameter. This
parameter is needed to provide a hysteresis
time in order to ensure that the traffic
reduction at mobile station can be effective.
TCONOFFs range is from 10 to 30 seconds
(with step 1); 0 means no hysteresis time
used. (Default value :20)
PVC Connection Status Procedures

A set of PVC connection status procedures are supported:
Periodic polling: used in acquiring general status of the network. The
polling interval is defined by the T391 timer. Every T391 seconds the
user equipment sends a STATUS ENQUIRY message to the network.
(Optionally the Network may initiate the polling procedure).
Link integrity verification: used in determining the in-channel signalling
link DLCI-0. Establishing and releasing a logical connection is
accomplished by exchanging messages via DLCI-0. The Link Integrity
verification procedure is required since DLCI-0 contains unnumbered
information (UI) frames at Level 2.
Reporting new PVCs: used to notify users of newly added permanent
virtual circuits.
Reporting the availability of a PVC: used to determine changes in
status of configured PVCs.
50-183
Mr.M.Kaufmann
Object
FRL
DB name
T391
Range
0..60
N391
1..255
N392
1..255
N393
1..255
Meaning
The timer represent the link integrity
verification repetition.(Default value 10 sec.)
N391 represents the polling cycle. It means
that after N expirations of T391 a STATUS
ENQUIRY requiring a full status shall be sent
to SGSN. (Default value 6)
N392 represents the error threshold on the
polling procedure (based on N391 counter)
used to put the FRL Disabled.(Default value3 )
N392 represents the error observation
window. If threshold N392 is reached on N393
* T391 timer, the links are set into Disabled
state. If the threshold is not reached the
counters are restarted. (Default value is 4)
The Link Integrity Verification procedure is visualised in figure 27. The PCU
issues a Status_Enquiry command and starts immediately the T391 timer.
The network may respond with a full status message if a PVC status is
changed or if new PVCs are added. Optionally the PCU may issue a Full
Status_Enquiry every N391 times the T391 has expired (i.e. a
Status_enquiry has been issued N391 times).
PCU
Start of
Timer T391
SGSN
Status inquiry
Status
Expiration of
Timer T391
Status inquiry
Status
Figure 27 Sub Network Link Integrity Verification

51-183
Mr.M.Kaufmann
Caddie table handling for the FRL_NSVC object:

1. Open the FRL_NSVC table in the Editor window. This is a combined
table for the FRL- and NSVC-objects.
2. Fill in all project specific FRL_NSVC parameter values additionally to the
default FRL_NSVC values, which can be used from the standart table.
52-183
Mr.M.Kaufmann
NS Network Service Control
The Network Service Control takes care of the end-to-end NSVCs

communication between a PCU and SGSN. Functionality includes:
NS SDU transmission: The NS SDUs are transmitted on the NSVCs. A
NS SDU is encapsulated into a NS Control PDU which again is
encapsulated into a Sub Network Service PDU.
Load Sharing: The load sharing function distributes the NS SDU traffic
among the available NSVCs. A Link Selector Parameter (LSP) is used by
the NS control to select among unblocked NSVCs of the addressed BVC
when sending the NS SDU.
NSVC management: A blocking and an unblocking procedure are used
in organising the NS traffic. Additionally a reset procedure and a test
procedure are used in the management of a NSVC.
Object
PCU
DB name
TNSVCBLK
Range Meaning
1..10
This timer defines the waiting time for
NSVC block/unblock procedure. After a
NSVC block/unblock message is sent, the
PCU wait TNSVCBLK seconds, for
acknowledge. (Default value 3 sec.)
NNSVCBLKR 1..254 This parameter specifies the maximum
number of retry performed in the NSVC
block procedure. If the SGSN does not
answer to block procedure, the procedure
shall be retried for NNSVCBLKR times.
(Default value 3)
NNSVCUBLR 1..254 This parameter specifies the maximum
unblock procedure. If the SGSN does not
answer to the unblock procedure, the
procedure shall be retried for
NNSVCUBLR times. The value 0 assumes
that the procedure is repeated infinite
times. (Default value 3)
TNSVCR
1..10
NSVC reset procedure. After a NSVC
reset message is sent, the PCU waits
TNSVCR seconds for acknowledge.
(Default value 3 sec.)
NNSVCRR
1..254 This parameter specifies the maximum
53-183
Mr.M.Kaufmann
TNSVCTST
1..60
TNSVCPTST
1..10
NNSVCTSTR 1..30
NBVCBR
1..30
NBVCUR
1..30
NBVCRR
1..30
T1
2..29
T2
2..119
TF1
2..9
reset procedure before generating any

alarm. If the SGSN does not answer to the
reset procedure, the procedure shall be
retried infinitely but after NRSET times an
O&M alarm shall be notified. (Default 10)
This timer defines the periodicity of the
NSVC test procedure. The test message
is sent to the SGSN when NSVC is
available every TNSVCTST times.
(Default value is 30 sec.)
NSVC test procedure. If after
TNSVCPTST sec. no answer to the test
procedure is received, the test procedure
shall be retried. (Default value is 3 sec.)
This parameter defines the number of
consecutive retries performed forthe test
procedure before declaring link not
available. (Default value 10)
Number of BVC Block Retries: this
parameter, used in BVCI block procedure,
indicates the number of repetitions of the
block procedure, in case of a not
answering SGSN, before sending an O&M
alarm. (Default value 3)
Number of BVC Unblock Retries: this
parameter, used in the BVCI unblock
procedure, indicates the number of
repetition of the unblock procedure, in
case of a not answering SGSN, before
sending an O&M alarm. (Default value 3)
Number of BVC Reset Retries: this
parameter, used in the BVCI reset
procedure, indicates the number of
repetition of the reset procedure, in case
of a not answering SGSN, before sending
an O&M alarm. (Default value 3)
This timer defines the waiting time forthe
BVCI block/unblock procedure. After a
BVCI block/unblock message is sent, the
PCU waits T1 seconds, for acknowledge.
(Default value is 10 sec.)
This timer defines the waiting time for the
BVCI reset procedure. After a BVCI reset
message is sent, the PCU waits T2
seconds, for acknowledge. (Default value
is 10 sec.)
This timer defines the time for capacity
reporting period used in flow control
54-183
Mr.M.Kaufmann
algorithm. It corresponds to the C timer

reported in the GSM 8.18
recommendation. (Default value is 5 sec.,
extremes excluded)
BSSGP Protocol
The Gb allows many users to be multiplexed over a common physical
resource. Both GPRS signalling and user data may be sent on the same
physical resource. The primary functions of the BSSGP include:
Downlink direction: connect a SGSN to a BSS with radio related
information which is used by the RLC/MAC function.
Uplink direction: connect a BSS to a SGSN with radio related
information which is derived from the RLC/MAC function.
Provide functionality to enable a SGSN and BSS to perform
management control functions.
BSSGP service model, service primitives, procedures and PDU formats are
specified in GSM 08.18. Referring to the Service model in figure 28 the
following functions are implemented:
BSSGP: Control the transfer of LLC frames between the SGSN and MS
across the Gb interface.
RL: The Relay (RL) controls the transfer of LLC frames between the
RLC/MAC and BSSGP.
GMM: GPRS Mobility Management (GMM) is responsible for functions
related to mobility management between and SGSN and BSS.
NM: Network Management (NM) is responsible for functions related to
the management of the BSS and SGSN across Gb.
Relay
GSM 03.64
RLC/
MAC
MAC
GMM
RL
NM
GMM
NM
BSS GP
Network Service
55-183
Mr.M.Kaufmann
Figure 28 BSSGP Service Model
56-183
Mr.M.Kaufmann
BSSGP Virtual Connection

A BVC provides a communication path between BSSGP user entities. Each
BVC is used in transporting BSSGP PDUs. Each BVC is identified by a BVCI
which has end-to-end significance across the Gb interface. A BVCI is
unique within a SGSN.
Quality-of-Service
Quality-of-Service (QoS) profiles are described in GSM 03.60. For an uplink
data transfer the QoS profile is communicated by the MS as priority
information. For a downlink transfer the BSSGP provides the means to
transfer the QoS profile together with the downlink LLC PDU from The
SGSN to the MS.
In GR1.0 only Best effort QoS will be supported. This means the PCU
scheduler will queue the MS requests without considering the QoS
attributes.
Logical Link Control Functionality

The LLC layer provides logical links between the MS and the SGSN. The
LLC supports:
Service primitives for transferring SNDCP PDUs between the SNDC
layer and the LLC layer. (See chapter 5 for more information).
Procedures for transferring logical link PDUs between the MS and
SGSN.
Procedures for detection and recovery of lost and corrupted logical link
PDUs.
Procedures for flow control of logical link PDUs between the MS and
SGSN.
Procedures for ciphering of logical link PDUs.
For more information on the LLC it is referred to GSM 03.60.
Subnetwork Dependent Convergence Functionality
The SNDCP is used as a direct peer-to-peer communication between the
MS and SGSN. User data from a network layer protocol like IP or X.25 is
transported. The SNDCP transfers data transparently for the user, and
main functions are:
57-183
Mr.M.Kaufmann
Data compression/decompression (both user data and protocol control

information).
Segmentation and Re-assembly of PDU packets.
Multiplexing of PDPs.
For more information on the SNDCP it is referred to GSM 03.60.
Channel Configuration
Channel Configuration Overview
For GPRS three types of Packet Data Channel have to be considered:
PCCCH (Packet Common Control Channel)

PBCCH (Packet Broadcast Control Channel)
PDTCH (Packet Data Traffic Channel)
At the creation of a GPRS channel (PBCCH, PCCCH, PDTCH) the GSUP flag
of the related TRX should be already set to TRUE.
This new parameter GSUP indicates if the GPRS service is supported or
not.
All the traffic channels subordinate to a TRX with GSUP set to TRUE must
have the same TSC.
If the TRX have the GSUP set to TRUE, single TCHs must have the same
FHSYID and MAIO. If one or more CCCH have already been equipped, the
channels cannot hop (i.e. FHSYID attribute must be 0).
On the BCCH TRX the operator can create no more than 5 GPRS
channels.
The obligation that the maximum number of GPRS channels per TRX is 5
is now valid only for the BCCH TRX. For all others TRXs this rule is
suppressed because it is possible to have up to 8 GPRS channels per TRX.
The parameter GMANPRES and GMANPAL of the object PTPPKF are
deleted in BR 6.0. The parameter GMANPAL is more or less substituted by
a
new
parameter
called
GPDPDTCHA
(GprsPercentageofDynamicPDTCHAvailable). See Chapter GPRS features
BR6.0.
58-183
Mr.M.Kaufmann
The parameter GMAPERTCHRES substitutes the GMANPRES and allows to

reserve timeslots for GPRS in a procentual way.
Different packet data logical channels (up to 16) can be multiplexed on
the downlink on the same physical data channel (i.e. PDCH).
Different packet data logical channels (up to 7) can be multiplexed on the
uplink on the same physical data channel, (i.e. PDCH).
But in total only up to 16 different packet data logical channels (UL and
DL) can be multiplexed on the same physical channel.
59-183
Mr.M.Kaufmann
Object/
Package
PTPPKF
DB Name
Range
Meaning
GMANMSAL
Field 1:
1..7 Default:7
This parameter indicates the

maximum of MSs that can be
multiplexed within one PDCH.
Field 2:
1..16
Default:16
Further Descriptions see below.
GMANMSAL is composed by two fields:

the first field indicates the maximum number of MS that can be multiplexed on
one PDCH in Uplink direction (1..7)
the second one indicates the maximum number of MS that can be multiplexed
on one PDCH in Downlink direction (1..16)
Packet Common Control Channel PCCCH
The physical channel may not be reserved for user traffic only, but some
blocks may be chosen for common control signalling.
Common control signalling, which is required by GPRS, is carried either on
PCCCH, (when allocated) or on CCCH.
The PCCCH channels must be created on the BCCH-TRX only.
PCCCH comprises logical channels for common control signalling used for
packet data as described in the following and is only allowed to be
created on the BCCH figure 29.
60-183
Mr.M.Kaufmann
UL
Packet Random
Access Channel
PRACH
DL
PPCH
Packet
Common
Control Channel
PCCCH
Packet Paging
Channel
DL
Packet Access
Grant Channel
PAGCH
DL
Packet Notification
Channel
PNCH
Figure 29
to initiate UplinkTransfer, Request

allocation of one or more
PDTCHs
to page an MS prior to
Downlink-Transfer
resource allocation
(PDTCH) in packet
transfer establishment
phase
Notification for a group of
MS for PtM Multicast.
(Not supported in GPRS
1.0 )
Packet common control channels
61-183
Mr.M.Kaufmann
Packet Broadcast Control Channel (PBCCH) downlink only
PBCCH broadcasts packet data specific System Information, used by the

MS to access the network.
If PBCCH is not allocated, the packet data specific information is broadcast
on BCCH.
The PBCCH can only be created on the BCCH.
Packet Data Traffic Channels (PDTCH)
PDTCH is allocated for data transfer. It is temporarily dedicated to one MS

or to a group of MSs.
In the multislot operation, one MS may use multiple PDTCHs in parallel for
individual packet transfer. All packet data traffic channels are unidirectional, either uplink (PDTCH/U) or downlink (PDTCH/D).
All the traffic channels subordinate to a TRX with GSUP set to TRUE must
must have the same TSC (trainings sequence code).
The GSUP can be set to TRUE only if the related PTPPKF is already
equipped
Object/
Package
TRX
DB Name
Range
Meaning
GSUP
0..1
This attribute indicates if the GPRS

service is supported or not.
(These PDTCHs can be configured
as TCH_F as well as TCH_F/H )
False/True
ADJC
GSUP
0..1
False/True
PCU
TEMPCH
1..254 sec.
Timer Empty
Channel
Default: 45
sec.
62-183

service is supported or not.
(These PDTCHs have to be
configured as full rate)
Specifies the time for releasing
PDTCH if no activities are done.
This timer should prevent a faster
PDTCH channel allocation/ release
that can increase TDPC load
Mr.M.Kaufmann
Packet Dedicated Control Channels
Packet Dedicated Control channels, dedicated to a given MS, comprises

the channels, described in the following figure 30.
Signalling
information for
one MS e.g.
Packet Associated
Control Channel
Acknowledgemen
ts, PowerControl,
Ressource(Re)Assignment
PACCH
Packet Dedicated
Control Channels
Packet Timing
advance
Control Channel
UL/ DL
Estimation and
updates of timing
advance for one
MS
PTCCH
Figure 30
Packet Dedicated Control Channel
Channel structure for PDCH
The physical channel dedicated to packet data traffic is called a Packet

Data Channel (PDCH).
Packet data channels uses 52-multiframe structure, which consists of 52
TDMA frames, divided into 12 blocks (of 4 frames), 2 idle frames and 2
frames used for PTCCH Packet Timing advance Control Channel, see figure
31.
52 TDMA Frames
B0
B1
B2
B3
B4
B5
B6
B7
X = Idle Frame (for Interference measurements)

B0 .. B11 = Radio Blocks
63-183
B8
B9
B10
B11
T = Frame used for PTTCH
Mr.M.Kaufmann
Figure 31
52-multiframe structure
The information sent on a 52-multiframe belongs to one timeslot on a

BCCH-TRX.
Any of the TS of the BCCH-TRX can be configured fix as a PBCCH TS. That
means, that the first block (B0) of these PDCH multiframe is used as
PBCCH. If required, up to 3 more blocks on the same PDCH can be used as
additional PBCCH.
Any additional PDCH containing PCCCH is indicated on PBCCH. The total
number of PBCCH blocks on this PDCH is indicated in the first PBCCH block
by means of the BSPBBLK parameter (from 1 to 4).
Object/
Package
PTPPKF
DB Name
Range
Meaning
BSPBBLK
bsPbcchBlocks
0..3
Indicates the number of blocks

allocated to the PBCCH in the
multiframe
Default: 1
Range:
0
1
2
3
Meaning:
Block B0 used for PBCCH
Block B0, B6 used for PBCCH
Block B0, B6, B3 used for PBCCH
Block B0, B6, B3, B9 used for PBCCH
On any PDCH with PCCCH (with or without PBCCH), the next up to 12

blocks are used for PAGCH, PNCH, PDTCH or PACCH in the downlink.
Object/
Package
PTPPKF
DB Name
Range
Meaning
BPAGCHR
0..12

reserved for PAGCH, PDTCH and
PACCH for the 52 frames
multiframe case.
See GSM 5.02

Default: 7
The BPAGCHR field is optional and if not included it shall be interpreted as the
default value of 0 blocks reserved for PAGCH, PDTCH and PACCH. If included,
the field is coded according to the following table:
64-183
Mr.M.Kaufmann
Range:
0
1
.....
12
Meaning:
0 blocks reserved for PAGCH, PDTCH and PACCH
1blocks reserved for PAGCH, PDTCH and PACCH
The remaining blocks in the ordered list are used for PPCH, PAGCH, PNCH,
PDTCH or PACCH in the downlink.
On an uplink PDCH that contains PCCCH, all blocks in the multiframe can
be used as PRACH, PDTCH or PACCH.
Object/
Package
PTPPKF
DB Name
Range
Meaning
BPRACHR
BsPrachBlocks
Reserved
0..12

reserved in a fixed way to the
PRACH channel on any PDCH
carrying PCCCH and PBCCH
(only for 52 type PCCCH)
Default: 4
See GSM 5.02

Range:
0
1
2
....
12
Meaning:
No block reserved for PRACH (default)
Block B0 reserved for PRACH
Block B0, B6 reserved for PRACH
Block B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11
reserved for PRACH
Channel Organisation in a Cell
A cell supporting GPRS may allocate resources on one or several physical

channels in order to support the GPRS traffic. Those physical channels (i.e.
PDCHs), shared by the GPRS MSs, are taken from the common pool of
physical channels available in the cell. The allocation of the physical
channels to circuit switched services and GPRS is done dynamically
according to the capacity on demand, e.g. unused channels can be
allocated as PDCHs to increase the overall quality of service for GPRS or
upon resource demand for other services with higher priority, deallocation of PDCHs can take place.
65-183
Mr.M.Kaufmann
The resource allocation/deallocation is driven by the PPCU software.

Moreover the new BR 6.0 feature Service dependend channel allocation
allows an operator defined distribution between speech and data traffic.
This establish the possibility to distinguish between data and speech
channel
allocation. The channel indication depends on the free resources at the
time a channel is required.
66-183
Mr.M.Kaufmann
Channel Organisation in a Cell

In SBS GR1.0 the following channel combinations per timeslot are allowed:
-
PBCCH + PCCCH + PDTCH + PACCH + PTCCH

PCCCH + PDTCH + PACCH + PTCCH
PDTCH + PACCH + PTCCH
Where PCCCH = PPCH + PRACH + PAGCH + PNCH

The decision, when to take which combination is a question of resources.
If the operator has enough resources it is recommendable to use a PBCCH
beside the BCCH e.g. the cell re-selection process will be much faster than
without PBCCH.
Control Channel Configuration

Packet Common Control Channel
When PCCCH is allocated in a cell, all GPRS attached MSs camp on it.
PCCCH can be allocated either as a result of the increased demand for
packet data transfers or whenever there is enough available physical
channels in a cell (to increase the quality of service).The information
about PCCCH is broadcast on BCCH.
When no PCCCH is allocated in a cell, all GPRS attached MSs camp on the
CCCH.
The parameter GCCH of the Channel package is not existing in BR 6.0
anymore.
It is substituted by the new parameter GDCH, which is used to control if
the channel is enabled or not to carry control informations for GPRS.
Object/
Package
CHANNEL
DB Name
Range
Meaning
GDCH
1 ... 3
GPRSPBCCH,
GPRSPCCCH,
PDTCH
Is used to control if the channel is enabled

or not to carry contrl. inform. for GPRS
Packet Dedicated Control Channel
Packet Associated Control Channel (PACCH) conveys signalling information

related to a given MS. The signalling information includes e.g.
acknowledgements and power control information.
67-183
Mr.M.Kaufmann
PACCH also carries resource assignment and reassignment messages,

comprising the assignment of a capacity for PDTCH and for further
occurrences of PACCH. The PACCH shares resources with PDTCHs, that are
currently assignoed to one MS.
Additionally, an MS that is currently involved in packet transfer, can be
paged for circuit switched services on PACCH.
Object/
Package
PTPPKF
DB Name
Range
Meaning
BPAGCHR
0..12
See GSM 5.02
Default: 7

reserved for PAGCH, PDTCH and
PACCH for the 52 frames
multiframe case.
The BPAGCHR field is optional and if not included it shall be interpreted as the
default value of 7 blocks reserved for PAGCH, PDTCH and PACCH. If included,
the field is coded according to the following table:
Range:
0
1
.....
12
Meaning:
0 blocks reserved for PAGCH, PDTCH and PACCH
Each PDCH is able to carry control information for GPRS:
Logical Functions
Network Access Control Functions
On the air interface the cell structure organisation remains the same as in
the actual implementation.
Additional identifier is introduced to group the cells supporting GPRS
service in the Location Area (LA). This information is named Routing
Area (RA) and is a sub entity of the Location Area, it is a more precise
description of the current position of the GPRS-MS.
One LA can include more than one RA.
Object/
Package
DB Name
Range
68-183
Meaning
Mr.M.Kaufmann
PTPPKF
RACODE
Routing Area
Code
0..255
This attribute represents the

identification of the RA which group
cells supporting GPRS
PTPPKF
RACOL
Routing area
Colour
0..7
This attribute is used by the MS to

identify the specific routing area.
Default: 0
Since the RA can be smaller than LA, and its numbering is not unique in
the network but it is unique in the LA, RACOL is used to choose the right
RA when the MS is listening to different LA containing routing area with
the same code. The RA colour code for neighbour LA must be set different
by network planning.
The mobile allowed to access GPRS service receive the information about
the service in the System Information on BCCH channel. System
Information 3 and 4 have to be modified in order to insert parameters for
GPRS. New System Information 13, 14, 15 have to be sent on the air
interface carrying all parameter for GPRS network access.
Mobility Management Functions

Mobility Management functions are used to know about the actual point of
presence of a MS in its home PLMN or visited PLMN.
Mobility Management States
The Mobility Management (MM) activities related to a GPRS subscriber are

characterised by one of three different MM states.
Idle State
A MS in Idle state is detached concerning GPRS. Only GPRS subscriptions
data are available in the HLR. No other information are available in other
network entities such as SGSN and GGSN.
The MS has to watch the BCCH, to determine the cells supporting GPRS
service. Doing so, the GPRS MS is able to make PLMN and cell selection
procedures.
To leave the Idle State, the MS has to run through the attach procedure.
After successfully attach procedure the MS is in the Ready state.
Ready State
69-183
Mr.M.Kaufmann
In Ready state the SGSN knows the Routing Area RA and the actual cell of
the GPRS-MS. If the GPRS-MS is changing the cell, the SGSN gets
informed.
Therefore no paging is necessary. The downlink packet data transfer is
enabled. The ready status does not mean, that a physical connection is
established between the SGSN and MS. Only in ready state SGSN and MS
are able to transfer data packets. MS and SGSN are leaving the Ready
state after a certain time period and enter the Standby state.
MS and SGSN are leaving the Ready state after a ready release procedure
and enter then the Idle state.
Standby State
In Standby state the GPRS-MS is attached to the GPRS network. The
GPRS-MS and the SGSN keep up a mobility management context.
The MS watches the broadcast channel to determine the cells which are
supporting GPRS and to get informed about Paging Channel PCH and
Paging requests.
The SGSN knows the Routing area of each MS.
The GPRS-MS informs the SGSN about Routing area changes and responds
on Paging Requests.
To enter into the Ready state, a SGSN has to page a MS or the MS has to
initiate a data transfer (PDU transmission).
After a certain period in standby state the MS is entering the Idle State.
Location Management Procedure
The PLMN shall provide information for the MS to be able to:

- detect when it has entered a new cell or a new RA
- determine when to perform periodic RA updates
The MS detects that a new cell has been entered by comparing the cells
identity with the cell identity stored in the MS MM context. The MS detects
that a new RA has been entered by periodically comparing the RAI stored
in its MM context with that received from the new cell.
If the MS enters a new PLMN, the MS shall either perform a routing area
update, or enter IDLE state.
Packet Timing Advance Feature

The Timing Advance procedure, supported with BR5.5, is used to derive
the correct value for timing advance that the MS has to use for the
uplink transmission of radio blocks.
70-183
Mr.M.Kaufmann
Initial timing advance estimation (GSM 03.64)

The initial timing advance estimation is made by the BTS on the first
RACH carrying the Packet Channel Request.
The estimation is sent to the BSC-PCU, which notifies back to the MS the
information in the Packet Resource/ Immediate Assignment
message.
This timing advance value shall be used by the MS for the uplink
transmissions until the continuous timing advance update provides a new
value.
Continuous timing advance estimation (GSM 03.64)
In the Packet Resource/ Immediate Assignment message an Timing
Advance Index (TAI) is assigned to the MS, so that a Continuous Timing
Advance Update mechanism to compute the timing advance value can be
performed with the only intervention of the BTS.
TAI specifies the PTCCH sub-channel (these are the idle frames in the 52Multiframe) used by the MS.
On uplink the MS shall send in the assigned PTCCH access burst, which is
used by the network to derive the timing advance.
The network analyses the received access burst and determines new
timing advance values for all MSs performing the continuous timing
advance update procedure on that PDCH.
The new timing advance values shall be sent via a downlink signalling
message (TA-message) on PTCCH/D.
Every second PDCH multiframe starts a downlink TA-message.
(PTCCH/U and PTCCH/D Structure can be found in GSM 05.02 Clause7
Table 6)
71-183
Mr.M.Kaufmann
52 multiframe number
n
B0
B1
TAI=0
B2
TAI=1
B3
B4
B5
B6
B7
B8
TA msg 1
n+1
TAI=2
B0
B1
B2
B4
B5
B6
B7
B8
B1
B2
B4
B5
B6
B7
B8
B1
B2
B4
B5
13
B6
B7
B8
B1
B2
24
B4
B5
25
B6
B7
B8
B1
B2
28
B11
10
B9
B10
B11
11
14
B9
B10
B11
15
20
B9
B10
B11
27
B9
B10
B11
31
TA msg 4
TAI=14
B0
B10
TAI=13
B3
TA msg 4
n+7
B9
TA msg 2
TAI=12
B0
TAI=7
B3
TA msg 2
...
n+6
12
TA msg 2
TAI=6
B0
B11
TAI=5
B3
TA msg 2
n+3
B10
TA msg 1
TAI=4
B0
B9
TAI=3
B3
TA msg 1
n+2
2
TA msg 1
TAI=15
B3
B4
B5
29
TA msg 4
B6
B7
B8
30
TA msg 4
=PACCH
TA msg: downlink message broadcasting: timing advance info for all MSs
The relationship between MS, TAI and position in uplink and downlink messages is fixed and does not require the
knowledge of the identity of the MS by the BTS.
Figure Packet Timing Advance
72-183
Mr.M.Kaufmann
System Information Management

System information messages are regularly broadcast by the network on
BCCH and busy TCH.
With help of the system information the MS is able to decide whether and
how it may gain access to the network via the current cell.
If a PBCCH channel is allocated in the cell, then new GPRS needed System
Information called Packet System Information (PSI) shall be
broadcasted on the PBCCH.
There exist Packet System Information: PSI 1, PSI 2, PSI 3, PSI 4, PSI 5, PSI
13 (see GSM 04.60)
For example PSI 1 message is sent by the network on the PBCCH or
PACCH giving information for Cell selection, for control of the PRACH, for
description of the control channel and optional global power control
parameters.
For example PSI 2 message is sent by the network on the PBCCH or
PACCH giving information of reference frequency lists, mobile allocations
and PCCCH channel descriptions applicable for packet access in the cell.
For example PSI13 message is sent by the network on PACCH providing
the MS with GPRS cell specific access-related information (e.g. Page Mode,
RAC, NCO, GPRS Power Control Parameters...). The information in this
message shall be the same as provided in the SI13 message on BCCH.
Object/
Package
PTPPKF
DB Name
Range
Meaning
T3192
0..7
This value plus one must be

multiplied by 500 msec. To obtain
the real value used in PSI
messages
Default: 0
PCU
T3193
Greater than
T3192
1..42
PCU
T3195
0...255
PTPPKF
T3166-68
0..7
Default: 4

the real value
0
1
Default: 1 sec. 2
16
Default: 7
73-183
PSI Count High Rate = 1

....

the real value used in PSI
Mr.M.Kaufmann
messages
SBS Modifications
HW/SW Changes
In order to introduce the GPRS service in SBS BSS, a new unit the PCU is
designed for the BSC to support packet data interworking between Gb
interface and Abis interface.
The functionality of the PCU is supported by Channel Codec Units CCUs.
Which are implemented in the BTS. The CCU functionality will be added to
the present BTS functionalities by Software Download.
BTS
BSC
CCU
CCU
A-bis
Figure 26
P
C
U
SGSN
Gb
New GPRS HW and SW in BTS and BSC
The PCU is responsible for:
Channel Access Control functions, e.g. access requests and grants;

PDCH scheduling functions for uplink and downlink data transfer;
Radio Channel Management functions, e.g. power control,
congestion control, broadcast control information, etc;
PDCH RLC ARQ functions, including buffering and re-transmission
of RLC blocks;
LLC layer PDU segmentation into RLC blocks for downlink
transmission;
RLC layer PDU re-assembly into LLC blocks for uplink transmission;
BSSGP protocol provides PCUSGSN communication in terms of
BVCI (BSSGP Virtual Connection Identifier);
Network Service functions provides PCUSGSN communication in
terms of Virtual Channel (NSVC, Network Service Virtual
Channel).
74-183
Mr.M.Kaufmann
The functions inside the CCU are:
Channel coding functions, including FEC and interleaving;

Radio channel measurement functions, including received quality
level, received signal level and information related to timing
advance;
Continuous Timing Advance.
With BR 6.0 new hardware boards are introduced for the BSC.
It consists of the replacement of existing boards with new PIN compatible
boards.
PPXX (General Purpose Peripheral Processor) replaces the previous
PPLD and PPCC boards. This new board increases the GPRS channels
up to 256 PDTCH per board and eliminates the impact of LAPD
channel capacity by using Packet Data Traffic Channels. With the
maximum amount of 6 PPXX boards for GPRS 1536 PDTCH are
achived. The data throughput is increased to 24 MB/s.
SNAP (Switching Network Advance Performance) replaces the
previous SN16. It increases the number of switching capacity up to
72 PCM lines.
The hardware implementation per PCU is realised by adding the following
boards to the BSC:
two boards of the PPCUs (Peripheral Packet Control Unit) if the
NTWCARD is NTWSN16/64
PPXU (same number as PCU) if the NTWCARD is NTWSNAP.
One of the PPCU card is providing service while the other one is in cold
standby. One BSC is able to have up to six PCUs.
In case of more than one PCUs, the Packet Traffic is divided between the
PCUs. For the PDTCH with n PPXX boards the PDTCH load is shared
through the load sharing mechanism.
In case of card failure an additional PPXX board guarantee the bandwidth,
if required.
If the NTWCARD is NTWSN16/64:
For one or two PPCUs of the first PCU 0, the rack position of PPLD 11 and
12 as well as PPLD 13 and 14 must be removed.
For one or two PPCUs of the second PCU 1, the rack position of PPLD 7
and 8 as well as PPLD 9 and 10 must be removed.
75-183
Mr.M.Kaufmann
For each PCU four PPLD cards have to be removed, independend of one or
two PPCU cards.
If the NTWCARD is NTWSNAP:
Creating one PCU (PCU 0) with executing the command create PCU 0.
This operation automatically creates the object PPXU.
It must be noted, that one PPXU board is necessary per PCU.
76-183
Mr.M.Kaufmann
The PPXU boards are inserted in BSC rack in place of some PPLD with the
following correspondence (NTWSNAP):
PPXU:0 in place of PPLD:4
PPXU:3 in place of PPLD: 9
Each PCU is able to handle a maximum of 256 PDT (Packet data terminal)
in BR 6.0.
The PDT functional object is used internally to represent the 16 kbit/s
terminal of connection reserved on the internal 2 Mbit/s for each channel
allocated on the Um interface (PDTCH, PBCCH, PCCCH). This object is not
visible and manageable by the operator.
The PCU can be considered enabled when one super-ordinate PPCU is
Providing Service.
All attributes that are common for all subordinated objects
(FRL,NSVC,PTPPKF) are inserted on PCU object in order to avoid duplicated
data.
The configuration of the PPCU parameters has to be done via the PCU.
Parameter for PCU
Object/
Package
PCU
DB Name
Range
Meaning
PCUN
0..5
Specifies the PCU number to which

the PTPPKF is connected
There are defined three new Mobile classes to support GPRS

GPRS Mobile Classes (GSM 03.60)
Class A
MS can support GPRS and circuit switched services simultaneously
Class B
MS can listen to both pagings (GPRS and circuit switched) and can
then choose which service to support
Class C
MS will run GPRS service or cicuit switched (switch manually)
Only Class B and C are supported in GR 1.0.

77-183
Mr.M.Kaufmann
Operational sequence to configure a BSC for GPRS

The sequence of operation to configure a BSC for GPRS service is
summarised in the next sections.
Create PCU
In order to create a PCU, some PPLD must be deleted.
In particular:
when NTWCARD=NTWSN16/64
To create one PCU (PCU 0):
delete PPLD from 11 to 14 (if present);
create PCU 0.
This operation automatically creates the objects PPCU 0 and
PPCU 1.
To create two PCU (PCU-0 and PCU-1):
create PCU 0;
create PCU 1.
This operation automatically creates the objects PPCU 0, PPCU 1,
PPCU 2 and PPCU 3.
when NTWCARD=NTWSNAP
To create one PCU (PCU 0):
create PCU 0.
This operation automatically creates the object PPXU 0
It must be note that the PPXU are 6 in total.
The command of creating a PCU requires different parameter to be set. In
particular the number of PDT and number of FRL must be set.
See Appendix B
Create FRL
Two cases must be considered:
1) if the link to SGSN is realised by PCMA (i.e. via MSC), it is possible to
create the Frame Relay Link (FRL) directly without any other operations;
2) if the link to SGSN is realised by PCM GPRS (PCMG), the PCMG object
must be created; after that is is possible to create the Frame Relay Link
(FRL).
See Appendix A
78-183
Mr.M.Kaufmann
Create NSVC
With the creation of this object, the virtual connection to the SGSN is
created.
Each BSSGP Virtual Connection (BVC) is used to transport Network Service
Signaling Data Units (NS SDU) between users. Each BVC is supported by
one group of NSVCs. Each group of NSVCs supports one or more BVCs.
The Network Service (NS) entity maps between BVC and the related NSVC
group.
See Appendix A
Create PTPPKF
There must be created as many Point to Point Packet Functions (PTPPKF)
as required for the GPRS service. Note that the creation of this object is
possible only if a BTS is already created.
At least one PCU instance must already exist, at least one NSVC must be
created.
The mapping between BVC and NSVC must be done at the PTPPKF
creation.
(The PTPPKF cannot be deleted if there is a subordinate TRX with GSUP
set to TRUE.)
See Appendix B
HW/ SW Restrictions in the GPRS release
A BSC fully equipped is able to have up to 8 PPXX boards.

2 PPXL boards are used for LAPD & SS7. (248 LAPD + CCS7 links
with 8 CCS7 max.)
GPRS physical channel (PDTCH) per PPXU: 256 (1536 PDTCH with 6
PPXU)
72 PCM ports for PCMS, PCMB and PCMG
max. MSs per GPRS channel: 16 (limited by TAI identifier)
max. Uplink MS connection: 7 (limited by USF Identifier)
max. Downlink MS connection: 16 (limited by TAI identifier)
max user rate: theoretically 93,8 kbps ( 7 x 13,4 kbps with CS-2)
79-183
Mr.M.Kaufmann
Design of Radio cells

Cell (Re-) Selection
No Handover functionality is foreseen in GPRS: the MS which moves
across cells selects the best cell following cell (re)selection criteria. If the
MS is involved in data transfer, packets may be lost during cell reselection. Upper layers will then recognise the inconsistency, discard the
frame and ask for a retransmission.
Optionally it is possible to run a procedure which is called `Network
Controlled Cell-Reselection (see chapter 6.1.6) and is not foreseen for
BR5.5.
Cell (Re-) Selection applies to GPRS MSs in Standby and Ready states; Cell
Re-Selection is performed by the MS, except for class A MS while in a
circuit switched connection.
The new cell re-selection criteria C31 and C32 are performed if a
PBCCH is allocated and should help to make the cell planning for GPRS
as similar to the existing network planning.
If GPRS is only supported on BCCH the existing C2 cell re-selection
shall be used.
Overview how the cell selection criteria for using BCCH and PBCCH can be
related:
BCCH
C1(as in GSM)
C2 (as in GSM)
PBCCH
C1 see chapter 6.1.1
C31
C32
C1 is just an assessment of the field strengths (on uplink and on

downlink). If a PBCCH is used, the C1 criterion is calculated by the same
formula (as in GSM) but with a separate parameter set, which is
transmitted on the PBCCH, PSI message, (e.g. GPRS_RXLEV_ACCESS_MIN
and GPRS_MS_TXPWR_MAX_CCH).
With this seperate parameter set it is possible for the network operator to
configure the cells different for GPRS and non-GPRS. Please consider that
80-183
Mr.M.Kaufmann
on PBCCH the network has the chance to indicate in a BA(GPRS)-List a

different set of neighbour cells than for non-GPRS.
C31 can be used for hierarchical cell structures. The advantage is that
C31 uses also a priority mechanism.
It is necessary to introduce C31 into GPRS, as the cell re-selection has to
be done by the MS. The MS need to get information of the neighbour cells
(e.g. in which layer the neighbour cells are laying, and which priority the
neighbour cells have), to decide about cell re-selection.
(For speech the Handover desicion is done by the BTS, so there is no
additional information for the cell itself necessary).
C32 is similar to the C2.
C2 (for GSM only) contains in addition to C1 an offset (to make a cell
better or worse than another) and a temporary offset, which is used to
make the cell worse during the first x seconds (i.e. the MS must "see" that
cell for that period of time before it may re-select it; this can be used for
preventing some cells for re-selection by a fast driving MS).
GPRS Path loss criterion C1
The path loss criterion C1 is a minimum signal level criterion for GPRS
cell selection and cell reselection is defined by:
C1 = RLA_P GPRS_RXLEV_ACCESS_MIN Max( 0, GPRS_MS_TXPWR_MAX_CCH
P)
RLA_P
received average BCCH (PBCCH) on MS
The MS shall measure the received signal level on the PBCCH carriers of
the serving cell and the surrounding cells and calculate the received
level average RLA_P for each carrier. The cells to be monitored for cell
reselection are defined in the BA (BCCH Allocation)(GPRS) list, which is
broadcast on PBCCH, At least 5 received signal level measurement
samples are required for a valid RLA_P.
RLA_P = 1/5 * (GPRS_RXLEV1 + GPRS_RXLEV2 + ...+ GPRS_RXLEV5)
P
Power Class of MS
GPRS_RXLEV_ACCESS_MIN see window
GPRS_MS_TXPWR_MAX_CCH
see window
81-183
Mr.M.Kaufmann
Object/
Package
PTPPKF
PTPPKF
DB Name
Range
Meaning
GRXLAMI
GPRS_
RxLev_ACCESS
Min
GMSTXPMAC
GPRS_MS_
TXPWR_MAX_
CCH
0..63
Defines the minimum received

level, at mobile station side,
required for access to the cell
Default:6
0..31
Default: 2
Defines the maximum power level

that can be used, at MS side in the
cell
The path loss criterion is satisfied if C1>0.

This means that the minimum allowed received downlink level to access the
network has to be above a threshold (GPRS_RXLEV_ACCESS_MIN).
To ensure a sufficient uplink received level even for MS of low transmit power
level P, the C1 criteria works as following:
If P < GPRS_MS_TXPWR_MAX_CCH
C1 = RLA_P GPRS_RXLEV_ACCESS_MIN (GPRS_MS_TXPWR_MAX_CCH P)
If P > GPRS_MS_TXPWR_MAX_CCH
C1 = RLA_P GPRS_RXLEV_ACCESS_MIN
Beside the C1 radio criterion there are some other criterions for a cell to
be suitable:
1.
2.
3.
Cell must be part of the selected PLMN

Cell must be configured for GPRS
Cell is not barred
Signal level threshold criterion C31
The signal level threshold criterion parameter C31 for hierarchical cell
structures (HSC) is used to determine whether prioritised hierarchical
GPRS and LSA cell reselection shall apply and is defined by:
82-183
Mr.M.Kaufmann
C31(s) = RLA_P(s) HCS_THR(s)
(serving cell)
If PRIORITY_CLASS(n) = PRIORITY_CLASS(s):
(neighbour cell)
C31(n) = RLA_P(n) HCS_THR(n)

If PRIORITY_CLASS(n) PRIORITY_CLASS(s):
(neighbour cell)
And T GPRS_PENALTY_TIME:
C31(n) = RLA_P(n) HCS_THR(n) GPRS_TEMPORARY_OFFSET(n)
And T > GPRS_PENALTY_TIME:
C31(n) = RLA_P(n) HCS_THR(n)
RLA_P is the received level average on MS.
Where HCS_THR is the signal threshold for applying HCS GPRS and LSA
reselection.
Object/
Package
PTPPKF
DB Name
Range
Meaning
GHCSTH
0..31
GprsHierarchical
Cell Structure
Threshold
Stepsize:2dB
Default:10
This attribute indicates the signal

strength threshold used in HCS cell
reselection procedure.
0 means 110dB
31 means 48dB
PTPPKF
GHCSPC
0..7
gprs
GprsHierarchical
Cell Structure
Default:3
Priority Class
This attribute represent the

hierarchy Cell Structure priority for
cell reselection purpose.
HCS_THR is broadcast on PBCCH of the serving cell.

The timer T is started in the MS for each cell in the list of the 6 strongest
neighbour cells as soon as it is placed on the list. T is reset to 0 if the cell
is removed from the list.
PRIORITY_CLASS is sent on PSI on PBCCH.
83-183
Mr.M.Kaufmann
PENALTY_TIME
applies.
Object/
Package
PTPPKF
PTPPKF
is the duration
for
which GPRS_TEMPORARY_OFFSET
DB Name
Range
Meaning
GPENTIME
GprsPenality
Time
0..31
This attribute gives the duration for

which the
GPRS_TEMPORARY_OFFSET is
applied in cell reselection
procedure.
GTEMPOFF
GprsTemporary
Offset
0..7
Default:0
Applies a negative offset to C31 for

the duration of GPRS
Stepsize:10dB PENALTY_TIME.
Default:1
(Value 7 means infinity )
GPRS_TEMPORARY_OFFSET applies a negative offset to C31 for the

duration of GPRS_PENALTY_TIME after the timer T has started for that cell.
Cell ranking criterion C32
The cell ranking criterion parameter C32 is used to select cells among
those with the same priority and is defined by:
C32(s) = C1(s)
see chapter 6.1.1
If PRIORITY_CLASS(n) PRIORITY_CLASS(s):
C32(n) = C1(n) + GPRS_RESELECT_OFFSET(n)
If PRIORITY_CLASS(n) = PRIORITY_CLASS(s ):
And T GPRS_PENALTY_TIME:
GPRS_TEMPORARY_OFFSET(n)
And T > GPRS_PENALTY_TIME:
84-183
Mr.M.Kaufmann

PRIORITY_CLASS is sent on PSI on PBCCH.
GPRS_RESELECT_OFFSET = positive offset increases priority of cell in the
list of the strongest neighbour cells.
Object/
Package
PTPPKF
DB Name
Range
Meaning
GRESOFF
GprsReselect
Offset
0..31
This attribute specifies to MS the

positive or negative offset and
hystereses to be applied to GPRS
RESELECTION CRITERION.
Default: 16
MORE INFORMATION SEE

BELOW THE BOX
0 =
1 =
2 =
3 =
4 =
5 =
6 =
7 =
8 =
9 =
10 =
-52
-48
-44
-40
-36
-32
-28
-24
-20
-16
-12
11
12
13
14
15
16
17
18
19
20
21
=
=
=
=
=
=
=
=
=
=
=
-10
-8
-6
-4
-2
0
2
4
6
8
10
22
23
24
25
26
=
=
=
=
=
12
16
20
24
28
27
28
29
30
31
=
=
=
=
=
32
36
40
44
48
The Timer T, GPRS_PENALTY_TIME, GPRS_TEMPORARY_OFFSET are

discribed in chapter x.x
GPRS_TEMPORARY_OFFSET applies a negative offset to C32 for the
duration of GPRS_PENALTY_TIME after the timer T has started for that cell.
GPRS_RESELECT_OFFSET, PRIORITY_CLASS, GPRS_TEMPORARY_OFFSET
and GPRS_PENALTY_TIME are broadcast on PBCCH of the serving cell.
The MS shall make a cell reselection if:
85-183
Mr.M.Kaufmann
C1 (GPRS serving cell) < 0 for a period of 5 seconds
MS detects DL Signalling failure (e.g. no paging possible)
Cell becomes barred

GPRS serving cell and GPRS neighbour cells configured with BCCH
C2 criteria is switched on
C2 (GPRS serving cell) < C2 (suitable GPRS neighbour cell)

If the suitable neighbour cell is in the same location area for a
period of 5sec
C2(GPRS serv. cell) + CELL_Reselect_Hystereses < C2 (suit. GPRS
neigh.cell)
If the suitable neighbour cell is in another location area for a period
of 5 sec.
C2 criteria is not switched on
C1 (GPRS serving cell) < C1 (suitable GPRS neighbour cell)
If the suitable neighbour cell is in the same location area for a
period of 5sec
C1(GPRS serv. Cell) + CELL_RESELECT_HYST < C1 (suit. GPRS
neigh.cell)
If the suitable neighbour cell is in another location area for a period
of 5 sec.
GPRS serving cell and GPRS neighbour cells configured with PBCCH
First of all the C31 criterion for the serving cell and all neighbour cells will
be calculated.
86-183
Mr.M.Kaufmann
If Parameter C31_HYST is set and MS is in MM ready state:

The GPRS_CELL_RESELECT_HYSTERESIS shall be subtracted from the C31
value for the neighbour cell!
Under all this cells you have to find the best cell, therefore it is checked:
If there are cells which fulfil that C31 is 0, then only the cells with
the highest LSA priority are taken into account for further calculations. If
there is only one cell with the highest LSA priority, then this cell will be
the best cell to make cell reselection on.
Location Service Area (LSA) priority of the SoLSA feature is defined by the
list of LSAs for the subscriber stored on the SIM. LSA priority shall only be
considered by MS supporting SoLSA feature.
If there are no or more cells with the highest LSA priority, then for these
cells the PRIORITY_CLASS is checked. If there is only one cell with the
highest PRIORITY_CLASS, then this cell will be the best cell to make cell
reselection on.
If there are more cells with the highest PRIORITY_CLASS,then for this cells
the C32 (C1 criterion comes here into account!) criterion will be
calculated. The cell with the highest C32 criterion will be the best cell to
make cell reselection on.
Following hysteresis value shall be subtracted form the C32 value for the
neighbour cells:
in standby state, if the new cell is the same routing area: 0
in ready state, if the new cell is in the same routing area:
GPRS_CELL_RESELECT_HYSTERESIS (to delay a cell re-selection, as a
TBF might be interrupted)
in standby or ready state, if the new cell is in a different routing
area:
RA_RESELECT_HYSTERESIS (to delay a cell re-selection, as routing
area changes will produce a lot of extra signalling)
in case of a cell re-selection occurred within the previous 15
seconds: 5dB
GPRS_CELL_RESELECT_HYSTERESIS,C31_HYST
and
RA_RESELECT_HYSTERESIS are broadcast on PBCCH of the serving cell
Note:
if
the
parameter
C32_Qual
is
set,
positive
GPRS_RESELECT_OFFSET values shall only applied to the neighbour
with the highest RLA_P value of those cells for which C32 is compared
above.
87-183
Mr.M.Kaufmann
If there are no cells which fulfill that C31 is 0. then the C32
criterion will be calculated for all cells. The cell with the highest C32
criterion will be the best cell to make cell reselection on.
Following hysteresis value shall be subtracted form the C32 value for the
neighbour cells:
in standby state, if the new cell is the same routing area: 0
in ready state, if the new cell is in the same routing area:
GPRS_CELL_RESELECT_HYSTERESIS (to delay a cell re-selection, as a
TBF might be interrupted)
in standby or ready state, if the new cell is in a different routing
area:
RA_RESELECT_HYSTERESIS (to delay a cell re-selection, as routing
area changes will produce a lot of extra signalling)
in case of a cell re-selection occurred within the previous 15
seconds: 5dB
GPRS_CELL_RESELECT_HYSTERESIS,C31_HYST
and
RA_RESELECT_HYSTERESIS are broadcast on PBCCH of the serving cell
Note:
if
the
parameter
C32_Qual
is
set,
positive
GPRS_RESELECT_OFFSET values shall only applied to the neighbour
with the highest RLA_P value of those cells for which C32 is compared
above.
Cell re-selection for any other reason (see GSM 03.22) shall take place
immediately, but the cell that the MS was camped on shall not be
returned to within 5 seconds, if another suitable cell can be found. If valid
RLA_P values are not available, the MS shall wait until these values are
available and then perform the cell re-selection if it is required.
The MS may accelerate the measurement procedure within the
requirements (in GSM 05.08 subclause 10.1.1) to minimise the cell
reselection delay.
If no suitable cell is found within 10 seconds, the cell selection algorithm
of GSM 03.22 shall be performed. Since information concerning a number
of channels is already known to the MS, it may assign high priority to
measurements on the strongest carriers from which it has not previously
made attempts to obtain BCCH information and omit repeated
measurements on the known ones.
88-183
Mr.M.Kaufmann
List, containing serving cell and all neighbours:
Cell C
Cell D
Cell B
RANKING CRITERIA:
(4)Highest C32
(3)Highest Priority
(2)Highest LSA
Cell: A (e.g. serving cell)
Cell E
(2) Highest C32
(1) C31 0
(1) C31 0
Ranking List
Figure X: Cell Ranking for GPRS when a PBCCH is configured

If the parameter C32_QUAL is set, GPRS_RESELECT_OFFSET values
shall only be applied to the neighbour cell with the highest RLA_P value
of those cells for which C32 is compared above.
Object/
Package
PTPPKF
DB Name
Range
Meaning
C32QUAL
C32 Qualifier
TRUE
FALSE
If C32_QUAL is set, positive

GPRS_RESELECT_OFFSET
values shall only be applied to the
neighbour cell with the highest RLA
value of those cells for which C32
is compared
Default:False
PRIORITY_CLASS and C32_QUAL are broadcast on the PBCCH of the serving cell.
89-183
Mr.M.Kaufmann
If the parameter C31_HYST is set, GPRS_CELL_RESELECT_HYSTERESIS

shall also be subtracted from the C31 value for the neighbour cells.
DB Name
Range
Meaning
GCELLRESH
0..7
GprsCell
Reselect
Hysteresis
Stepsize:2dB
Default: 2
This attribute indicates the

additional hysteresis which applies
in cell for same routing area.
0 means 0dB
7 means 14dB
PTPPKF
C31H
C31Hysteresis
0 false
1 true
Default: 1

reselect hysteresis shall be applied
to the C31 criterion.
PTPPKF
RARESH
0..7
Routing Area
Reselect
Hysteresis
Stepsize:2dB
Default:2
This attribute indicates the

additional hysteresis to be applied
when MS is selecting a cell in a
new routing area.
0 means 0dB
7 means 14dB
Object/
Package
PTPPKF
GPRS Cell Reselect Hysteresis, C31Hysteresis, RA Reselest Hysteresis are

broadcast on the PBCCH.
Abnormal cell reselection
In the event of abnormal release with cell reselection when PBCCH exists,
an abnormal cell reselection based on GPRS BCCH Allocation (BA) list shall
be attempted.
Object/
Package
PTPPKF
DB Name
Range
Meaning
TRESEL
0..7
T_Resel
Default:0
If the MS has performed an

abnormal release with cell
reselection from this cell, the MS is
not allowed to reselect this cell for
T_RESEL seconds if another cell is
available.
90-183
Mr.M.Kaufmann
Range:
0
1
2
3
4
5
6
7
Meaning:
5 sec.
10 sec.
15 sec.
20 sec.
30 sec.
60 sec.
120 sec.
300 sec.
Network controlled reselection
The network may request measurement reports form the MS and control
its
cell
reselection.
This
is
indicated
by
the
parameter
NETWORK_CONTROL_ORDER.
Object/
Package
PTPPKF
DB Name
Range
Meaning
NTWCOR
NC0-NC2
Network Control
Order
Default: NC0
This parameter reported in SI13,

PSI1 and PSI5, informs the MS
about the control of cell reselection.
NC0: MS controlled cell reselection, no measurement reporting

NC1: MS controlled cell reselection, MS sends measurement report
NC2: NTW controlled cell reselection, MS sends measurement report
In the first implementation only NC0 and NC1 will be implemented.
The parameter NETWORK_CONTROL_ORDER is broadcast on PBCCH.
Measurements reporting
When ordered to send measurements reports, the MS shall continuously

monitor all carriers in BS(GRPS) or as indicated by the parameter
NC_FREQUENCY_LIST (this list adds/deletes frequencies to the GPRS BCCH
Allocation (BA) list both for cell re-selection and for measurement reports)
and the PBCCH carrier of the serving cell.
91-183
Mr.M.Kaufmann
For each carrier, the measured received signal level (RXLEV) shall be
average of the received signal level measurement samples in dBm taken
on that carrier within the reporting period.
After each reporting period, the MS shall send a measurement report to
BSS.
GPRS features
Power Control
Power Control is employed to minimise the transmit power required by the
MS or BSS whilst maintaining the quality of the radio links. By minimising
the transmit power levels, interference to co-channel users is reduced.
For the uplink, the MS shall follow a flexible power control algorithm,
which the network can optimise through a set of parameters. It can be
used for both open loop and closed loop power control (description in GSM
05.08 Annex B). In BR 5.5 only open loop control will be supported.
For the downlink, the power control is performed in the BTS. Therefore,
there is no need so specify the actual algorithm, but information about
the downlink performance is needed. Therefore the MSs have to transfer
Channel Quality reports to the BTS. Power control is not applicable to
point-to-multipoint multicast service.
Power Control is a mandatory feature for the MS, while it is
optional for the network.
MS output power
The MS shall calculate the RF output power value, PCH, to be used on

each individual uplink PDCH assigned to the MS:
Pch = min( 0 - ch - * (Cn + 48), PMAX)
Where
0
=39 dBm for GSM900
=36 dBm for DCS 1800
ch
is an MS and channel specific power control parameter, sent to the

MS in a control message, for BR5.5 this parameter will be set fixed
to 3 = 6dB
= ALPHA, is a system parameter, broadcast on PBCCH or optionally

sent to MS in a control message (see GSM 04.60)
92-183
Mr.M.Kaufmann
GAM = defines the 'gamma' value applied in the power control algorithm.
The value can be set from 0 dB to 62 dB in steps of 2 dB. The
range is for GAM is from 0 ... 31, Default = 3.
Object/
Package
PTPPKF
DB Name
Range
Meaning
ALPHA
0..10
Stepsize: 0,1
Default: 3
Indicates the ALPHA value applied

in the power control algorithm
0 = 0,0
10 = 1,0
PTPPKF
GAM
0..31
unit 2dB
Default: 3
Adjustment of the Gamma value of

the PC
Cn
is the normalised received signal level at the MS defined in
chapter 7.1.2.1
PMAX is the maximum allowed output power in the cell=
GPRS_MS_TXPWR_MAX_CCH if PBCCH exists otherwise
MS_TXPWR_MAX_CCH (broadcasts on BCCH or PBCCH)
When the MS receives new ch or values, the MS shall use the new
value to update Pch .
The MS shall use the same output power on all four bursts within one
radio block.
When accessing a cell on the PRACH or RACH and before receiving the first
power control parameters during packet transfer on PDCH, the MS shall
use the output power defined by PMAX.
The open loop control is achieved by setting = 1 and keeping ch
constant; with this method the MS output power is based on the received
signal strenght assuming the same path loss in uplink and downlink.
For closed loop control the output power is commanded by the network
based on signal measurements made in the BTS in a similar way as for
the cicuit switched connection.
The quality based control method, which is based on interference level
measurements at the BTS and that can be used in combination with any
of the two methods, is not for release BR5.5.
Measurements at MS side
93-183
Mr.M.Kaufmann
A procedure is implemented in the MS to monitor periodically the

downlink Rx signal level and quality from its serving sell.
There is an attribute PCMECH which indicates where the MS shall
measure the received power level on the downlink for purpose of the
uplink power control.
Object/
Package
PTPPKF
Range:
0
1
DB Name
Range
Meaning
PCMECH
PowerControl_
MEAS_CHAN
0..1
Indicates where the mobile station

shall measure the received power
level on the downlink for the
purpose of the uplink power control
Default:0
Meaning:
downlink measurements for power control shall be made on
BCCH
downlink measurements for power control shall be made on
PDCH
Packet idle mode
In packet idle mode, the MS shall measure the signal strength of

the PCCCH or, if PCCCH not existing, the BCCH.
The MS shall derive the normalised received signal level C in the power
control equation in the following way:
C block n = SS block n + Pb
SS block n = mean of the received signal level of the four normal bursts
that compose a block
Pb
= the BTS output power reduction used on the channel on

which the measurements are performed (relative to the output
power used on BCCH (or PBCCH if present))
Object/
Package
DB Name
Range
94-183
Meaning
Mr.M.Kaufmann
PTPPKF
PRPBCCH
0..15
Default:0
Range:
0
1
2
15
...
This attribute indicates the power

reduction value used by the BTS on
PBCCH blocks, relative to the
output power used on BCCH.
Meaning:
0dB
2 dB
4 dB
-30 dB
Finally, the C block n values are filtered with a running average filter, so
that C block n becomes Cn. Whereby the parameter TAVGW indicates the
signal strength filter period for power control in packet idle mode. TAVGW
is broadcast on the PBCCH or, if PBCCH not exists, on BCCH.
Object/
Package
PTPPKF
DB Name
Range
Meaning
TAVGW
T_AVG_W
0..25

strength filter period for power
control in packet idle mode
Default: 15
Packet transfer mode
In packet transfer mode, the MS shall measure the signal strength on

BCCH carrier of the serving cell as made for cell reselection procedure.
The measurements shall be filtered with a running average filter creating
Cn as running received level average filter. Whereby the parameter
TAVGT indicates the signal strength filter period for power control in
packet transfer mode. TAVGT is broadcast on the PBCCH or, if PBCCH not
exists, on BCCH.
Object/
Package
PTPPKF
DB Name
Range
Meaning
TAVGT
T_AVG_T
0..25

strength filter period for power
control in packet transfer mode
Default: 5
95-183
Mr.M.Kaufmann
Derivation of Channel Quality report
The channel quality is measured as the interference signal level

during the idle frames of the multiframe, when the serving cell is not
transmitting.
In packet transfer mode, the MS shall measure the interference signal
strength of all eight channels (slots) on the same carrier as the assigned
PDCHs.
The Ms shall make these measurements during the search frames and
PTCCH frames.
The measured interference shall be averaged in a running average filter.
For each channel, the MS shall perform at least NAVGI measurements
before valid running average filter values can be determined.
Object/
Package
PTPPKF
DB Name
Range
Meaning
NAVGI
N_AVG_I
0..15
This attribute represent an

interfering signal strength filter
constant for power control
Default:10
NAVGI is broadcast on PBCCH or, if not exists, on BCCH.

In packet idle mode, the MS shall measure the interference signal strength
on certain channels which are indicated on the PBCCH or, if PBCCH not
exist, on BCCH.
The interference measurement shall be made and averaged in the same
way as for packet transfer mode.
BTS output power
The BTS shall use constant power on those PDCH radio blocks which
contain PBCCH or which may contain PPCH.
This power may be lower than the output power used on BCCH. The
difference shall be broadcast on PBCCH.
On the other PDCH radio blocks, downlink power control may be used.
Thus, a procedure may be implemented in the network to control the
power of the downlink transmission based on the Channel Quality report.
The network shall ensure that the output power is sufficient for the MS .
96-183
Mr.M.Kaufmann
QoS (Quality of service)

The GPRS subscriber profile is a description of the services allowed for the
subscriber. It contains the description of the used Packet Data Protocol
PDP. For each PDP there are parameter such as QoS (Quality of Service)
parameter available.
Dependent on the data to be sent, the requirements for transmission
quality can be different. GPRS adapts to this requirements, as it is possible
to vary the QoS over a large value of attributes.
Currently there are five different attributes specified within QoS:
- precedence class
- delay class
- reliability class
- peak throughput class
- mean throughput class
Precedence class
The precedence class indicates the relative importance of maintaining the
service commitments.
There are three different classes defined for the packets, so that case of
limited resources/congestion it will be clear which packet has the highest
priority.
-1
high priority
-2
normal priority
-3
low priority
Delay class
Four different delay classes can be used. A PLMN may not support all of
them, however class 4 has to be supported, which is the best effort class.
Delay class specifies the maximum delay concerning the data packets
through the whole GPRS-network. Delay due to external networks is not
considered.
In GR1.0 (BR 5.5) only best effort class is supported.
Reliability class
The reliability class defines error rates for five different reliability classes.
Reliability in terms of data loss, data delivery out of sequence, duplicate
data delivery and probability of corrupted data.
Class 1 ensures highest and class 5 lowest reliability. Signalling shall be
transferred with reliability class 3.
Peak and mean throughput class
Gives the expected peak and mean throughput classes for
transmission of data through the GPRS network:
Peak throughput class 1-> 9
8kbit/sec -> 2048 kbit/sec
Mean throughput class 1 -> 19
class 1= best effort
97-183
the
Mr.M.Kaufmann
111kbit/s
class 2 = 0,22 bit/s .....class 19 =
During the QoS profile negotiation between the MS and the network, it is
possible for the mobile to request a value for each of the QoS attributes;
the network shall always attempt to provide adequate resources to
support the negotiated QoS profile.
The PCU, taking into account the available radio resources and the
multislot capabilities of the MS, decides if and how the requested QoS
may be satisfied.
This means that the core algorithm of the PCU, will try to satisfy the
requested QoS by acting on many factors, for example changing Coding
Scheme on the air interface (CS-2 has more transfer capacity than CS-1),
allocating more radio resources (capacity on demand), reshuffling
subscribers in the available PDCHs according to the MS multislot
capabilities, delay of the subscriber according to the subscriber priority
etc..
In the first phase of GPRS only Best effort will be supported.
This means that the PCU main scheduler shall queue the MSs requests
without taking into consideration the QoS attributes. It will be matter of
further design to decide which attributes, if any, have to be taken into
account.
98-183
Mr.M.Kaufmann
Channel Coding
Four coding schemes, CS-1 to CS-4 are defined for GPRS packet data
traffic channels.
For BR5.5 and BR 6.0 only coding schemes CS-1 and CS-2 will be
supported.
(This is due to the fact, that the transport capacity on the used Abis
interface is limited to 16 kbit/sec with the current network architecture).
Scheme
Code
rate
Radio
block
Coded
bits
Puncture Data
Redun
d bits
rate kb/s dancy
CS-1
CS-2
CS-3
CS-4
1/2
2/3
3/4
1
181
268
312
428
456
588
676
456
0
132
220
-
9.05
13,4
15,6
21,4
high
middle
low
no
For BR5.5 there will not be a dynamic up/and downgrade between

coding schemes. CS1 or CS2 will only used statically.
The parameter INICSCH describes with which coding scheme the
transmission of user data will take place.
Object/
Package
PTPPKF
DB Name
Range
Meaning
INICSCH
Initial_Coding
Scheme
CS -1
CS-2
Indicates the coding scheme to be

used when the packet transfer
starts
Default: CS-2
For all GPRS packet control channels besides Packet Random Access
Channel (PRACH) and Packet Timing Advance Control Channel on Uplink
(PTCCH/U), coding scheme CS-1 is always used automatically by the PCU.
99-183
Mr.M.Kaufmann
Timeslot Combining
Timeslot Combining (Multislot Configuration) to support high data rates.
A GPRS-multislot configuration consists of multiple packet switched traffic
channels together with associated control channels, allocated to the same
MS.
The rules for PDTCH allocation in multislot configuration are:
- same frequency hopping law (only Base Band Hopping)
- same training sequence code
- time slot number adjacent
- maximum 7 timeslots allocated per mobile station
The firsts two rules have to be followed in configuration phase that means
all TCH on BCCH carrier must have the same hopping law and the same
training sequence code. In case of a cell supporting Base Band Hopping, if
the BCCH TRX has the GSUP set to TRUE and one or more CCCH already
been equipped in the cell the MOBALLOC list cannot contain the BCCH
frequency.
The third law shall be followed dynamically for time slot selection. If from
PCU comes a request for a new PDCH, it should be tried to allocate a new
PDCH adjacent to the previous one.
In case of no free time slots adjacent to the busy one, and the adjacent
time slots are in stable state of call and there is at least one free channel
in the cell, a forced intracell handover shall be initiated in order to move
the call camped in the adjacent time slot to another one.
In case a Circuit Switch call (MOC or MTC) is coming in the cell with no free
channel, the BSC first tries to move incoming call to another cell with
directed retry procedure.
If the directed retry fails a pre-emption of GPRS channel shall be started.
The PCU chooses the channel to be returned to CS trying to keep active all
TBF downgrading their throughput.
In case the channel is requested for an Handover procedure and no
channels are free the BSC first starts to allocate the MS in adjacent cell
100-183
Mr.M.Kaufmann
eventually reported in the condition for intercell Handover. If this

procedure fails one channel allocated to GPRS is freed.
GPRS support on CCCH & PCCH

With the introduction of GPRS there were implemented new logical and
physical channels on the Um interface. The functionality of this new
packet oriented channels is similar to the ones of the GSM traffic.
The common control channel for GPRS are logically structured in the same
way as the CCCHs for GSM. Therefore the GPRS Common Control Channel
Signalling information can be realised via the existing CCCHs (as shared
CCCHs) or via PCCCHs (see also chapter 3.1.1).
When no PCCCH is used, then some of the GPRS signalling (the channel
request and channel activate acknowledge from BTS) will be supported by
LAPD-channel! All other signalling will be done via PACCH which are
transmitted within the PDCHs.
If PCCCH is used then signalling goes via PCCCH and PACCH.
As soon as the GPRS traffic exceeds a certain level it is recommended to
allocate a PCCCH in order to keep the signalling traffic of non GPRS
services low.
Discontinuous Reception (DRX)

For downlink packet transfer the delay of transmission of Paging
Messages and Direct Assignments has significant influence on the
packet delay and in particular on the radio access delay. The reason
for that delay is the organisation of the paging channel in combination
with DRX.
For optimisation reasons the MS indicates to the network to which
additional paging groups it listens, which allows an acceptable
access delay and/or the acceptable battery consumption and/or
the needed QoS of the application. So the BSS can shorten the waiting
time for Paging messages according to the capabilities of the MS. The
mechanism is defined for paging on PCCCH as well as on CCCH.
An MS can choose to use DRX or not (this is indicated in the Classmark)
and select a reduced sleep mode period indicated by the parameter
SPLIT_PG_CYCLE during PDP context activation. All information is stored
in the SGSN during GPRS MS has established a PDP context.
101-183
Mr.M.Kaufmann
DRX (Paging) on CCCH
The network internal message flow is following:

1. The SGSN, which has the knowledge about the usage of DRX, sends a
paging message to all PCUs which are located in the right Routing Area.
This message include a information whether DRX is used or not. And
additionally if the enhanced DRX mechanism is used a parameter
SPLIT_PG_CYCLE or another parameter which indicates that the existing
DRX mechanism shall be supported by the network.
2. The PCU forwards the Packet Paging Request message combined with
the requested paging parameters over the internal interface to the BSC.
3. The BSC calculates the right paging group and forwards per LAPD
connection the Packet Paging Request messages to the paging queues
inside the BTS. Additionally the BSC evaluates all needed DRX
parameters, which have to be broadcasted on BCCH.
4. The BTS queues all Packet Paging Request messages and sends them in
order first in first out on the PCHs in the CCCH multiframe.
DRX (Paging) on PCCCH
The network internal message flow is following:

1. The SGSN, which has the knowledge about the usage of DRX, sends a
paging message to all PCUs which are located in the right Routing Area.
This messages include a information whether DRX is used or not and
additionally if the enhanced DRX mechanism is used a parameter
SPLIT_PG_CYCLE.
2. The PCU calculates the right paging group and adds all Packet Paging
Request messages on its paging group queues. Additionally the PCU
evaluates all needed DRX parameters which have to be broadcasted on
PBCCH.
3. The PCU includes the Packet Paging Request messages into RLC/MAC
blocks and schedules the messages into the PDCH multiframes, which
contains PCCCH. The RLC/MAC blocks are transferred via TRAU frames to
the BTS, which transmits the Packet Request message immediately
Negotiation of the DRX parameters is per MS. The MS sends the DRX
parameter information element to the network, in order to indicate
whether the MS uses DRX or not. What the DRX parameter information
element contains is described in (GSM04.08 chapter 10.5.5.6).
-
Non DRX timer

A conditional parameter for MSs using DRX to determine the time
period within non-DRX mode after leaving the Transfer state. The
102-183
Mr.M.Kaufmann
support of this feature is optional on the network side and the

information about the maximum supported value for the timer in the
cell is broadcast on PBCCH.
Object/
Package
PTPPKF
0
1
2
3
4
5
6
7
DB Name
Range
Meaning
DRXTMA
0..7
DRX_TIMER_
MAX
Default: 7
This parameter indicates the

maximum value allowed for the MS
to request for Non-DRX mode after
packet transfer mode (upper limit
for the MS timer T3194)
No Non-DRX mode after packet transfer mode

Max. 1 sec. Non-DRX mode after packet transfer mode
Max. 2 sec
Max. 4 sec
Max. 8 sec
Max 16 sec
Max 32 sec
Max. 64 sec
GPRS BR 6.0 implementation aims
PCU Integration in BSC
Only point to point services supported, no PTMTP
GPRS shall be supported on CCCH and PCCCH
PCCCH shall be mapped on one or several physical channels

according to a 52-multiframe
Gb interface: 1 BSC with up to 6 PCUs can provide up to 378 FRL

and up to 378 NSVCs
Coding scheme CS1 or CS2 (statically) on PDTCH, the maximum

data rate is bounded to the CS2 upper limit of 13,4 kbps
The master-slave and Capacity on Demand concept shall be

supported
103-183
Mr.M.Kaufmann
Limited QoS on Radio Interface: Coding Scheme statically assigned

at call setup. Only Best effort is supported.
Timeslot combining to support MS multislot classes 1 up to 29 (max.

7 TS)
MS autonomous cell re-selection, no optional measurement reports
New cell re-selection criteria C31 and C32 for hierarchical cell
structures
No support of extended cells
Support of Base Band Frequency hopping
Continuous timing advance procedures shall be supported
Uplink Power Control
DRX: on CCCH existing DRX mechanism shall be used, on PCCCH

new defined DRX mechanism shall be supported
Support of 8-bit or 11-bit uplink access
Only USF controlled uplink data traffic, no extended USF or fixed

assignment mechanisms
Object Structure, SBS Parameter List BR6.0

Object
Parameter
Range
Short-Description
FRL
FRLN
0 .. 377
Frame Relay Number
FRL
PCUN
0 .. 5
FRL
GLK-PCMLINE
A,G (PCMx)
FRL
GLK-PCMNUM
PCMA: 0 - 143,
PCMG: 0 15
FRL
GTS-1 GTS-31
1..31
This attribute defines which PCU number is connected to the FRL

PCU greater than 1 are only allowed with Networkcard NTWSNAP
object identifies the PCMA or PCMG link which carries the FRL PCMLINE Type
this attribute with value PCMA-x or PCMG-x define the type of line
and the number of the line used for the connection between SGSN
and PCU. Mixed configuration A-int or G-int are admitted. This means
that its possible create some FRL link on PCMA interface and some
other on PCMG. Validity range : PCMA-x or PCMG-x
this attribute defines the 64 kbit/s time slot (with maximum 16 time
slot) reserved for this specific FRL either A int or G int as specified
with parameter GLK
104-183
Mr.M.Kaufmann
FRL
T391
1 .. 60, Default = 10
this Timer represent the link integrity verification repetition.

It can assume values from 1 to 60 seconds
FRL
N391
1 .. 255, Default = 6
FRL
N392
1 .. 255, Default = 3
Represents the polling cycle. It means, that after N expirations of

T391 a STATUS ENQUIRY requiring a full status shall be sent to
SGSN.
represent the error threshold on polling procedure (based on N391
counter) used to put the FRL Disabled.
FRL
N393
1 .. 255, Default = 4
represent the error observation window. If threshold N392 is reached

on N393 * T391 timer, the links are put in Disabled state. If the
threshold is not, reached the counters are restarted.
FRL
TCONG
1 .. 30, Default = 10
TCONG specifies the observation window for the congestion

detection. If the number of frames coming from the SGSN indicating
congestion is equal or greater than the number of frames indicating
no congestion within the specified window size, the congestion state
is notified to upper layers. TCONGs range is from 1 to 30 seconds,
default value is 10.
FRL
TCONOFF
0, 10 .. 30, Default = 20
FRL
FRSTD
0= ITU, 1 = ANSI, 2 =
LMI, Default = ITU
FRL-NSVC
NSVCN
0..377
FRL-NSVC
NSVCI
0..65535
this parameter represents the common identification of the virtual

connection between SGSN and BSS
FRL-NSVC
NSVLI-DLCI
0...377
16..991
1023
PTPPKF
ACTIVE
I, A
(Network Service Virtual Link Identifier): this attribute defines the

association of the FR-DLCI and the FRL. Two levels of identification
are provided for this attribute: the first one is the FRL and the second
one DLCI .
Field empty, means A
PTPPKF
BTSMN
0..199
BTSMN
PTPPKF
BTSN
0..23
BTSN
PTPPKF
RACODE
0 .. 255
(Routing Area Code): this attribute represents the identification of the

RA which belongs this cell.
PTPPKF
RACOL
0 .. 7
PTPPKF
BSCDVMA
1 .. 15, Default = 15
(Routing Area Colour): this attribute is used by the mobile to identifies

the specific routing area. Due to the fact that the RACODE can be
smaller than LA and its numbering is not unique in the network but its
unique in the LA, this parameter is used to choose the right RA when
the mobile is listening different LA containing routing area with the
same code. The RA colour for the neighbour LA must be set different
by network planning.
(BS_CV_MAX, see GSM 04.60): this parameter represents the value
of timer T3198, at MS side, expressed in number of RLC blocks.
PTPPKF
PKTNDEC
0 .. 7, Default = 2
(PAN_DEC - see GSM 04.60): this parameter defines the number of

decrement for counter N3102 performed if the T3182 expires without
reception packet uplink ACK/NACK. Its used for RLC layer at MS
side.
PTPPKF
PKTNINC
0 .. 7, Default = 2
(PAN_INC - see GSM 04.60): this parameter defines the number of

increment for counter N3102 performed after receiving packet uplink
ACK/NACK. Its used for RLC layer at MS side.
PTPPKF
PKTNMA
0 .. 7, Default = 4
(PAN_MAX (see GSM 04.60)): this parameter defines the maximum

value for counter N3102. If N3102 exceeds PKTNMA or N3102 reach
0 or less than 0, a RLC abnormal release shall be performed.
specifies the window for congestion abatement. After a congestion

notification, no other notifications are foreseen for the time configured
in this parameter. This timer is needed to provide a hysteresis time in
order to ensure that the traffic reduction at mobile station can be
effective. TCONOFFs range is from 10 to 30 seconds (with step 1);
plus 0 value,0 means no hysteresis time used.
OPTIONAL Parameter, Specifies the Frame Relay Standard used.
Number of NSVC
105-183
Mr.M.Kaufmann
PTPPKF
GRXLAMI
0 .. 63, Default = 6
(GPRS_RX_LEV_ACC_MIN): this parameter defines the minimum

received level, at mobile station side, required for the access to the
cell. This parameter is used to evaluate the path loss criterion
parameter C31
PTPPKF
GMSTXPMAC
0 .. 31, Default = 2
(GPRS_MS_TXPWR_MAX_CCH): this parameter defines the

maximum power level that can be used, at mobile station side, in the
cell. The valid values are the same defined for MSTXPWMX attribute
of BTS object.
PTPPKF
ABUTYP
ACBU8BIT,ACBU11BIT, (ACCESS_BURST_TYPE): this parameter with range ACBU8BIT (0)

Default = ACBU8BIT
to ACBU11BIT (1), default ACBU8BIT, indicates the type of access
burst used on uplink PDCH. The value ACBU8BIT means 8 bits
access burst shall be used by mobile station and ACBU11BIT means
11 bits access burst shall be used by mobile station (see GSM 05.02)
PTPPKF
RAARET
TRUE, FALSE, Default =

TRUE
(RANDOM_ACCESS_RETRY): this parameter indicates if set =

FALSE that random access retry to another cell is not allowed. If the
field is set = TRUE indicates that random access retry to other cell is
allowed.
PTPPKF
GPATH
PKANA, PKAAP1 PKAAP4, Default =

PKAAP4
(GPRS_PRIORITY_ACCESS_THR): this parameter indicates

whether or not a mobile station of a certain priority class is authorised
to do a random access for request of a GPRS service. The field is
coded according to the following table:
PKANA 0 0 0 packet access is not allowed in the cell;
PKAAP1 0 1 1 packet access is allowed for Priority class 1;
PKAAP2 1 0 0 packet access is allowed for Priority class 1 to 2;
PTPPKF
GTXINT
0..15, Default = 3
(TX_INT) this parameter defines the number of slots to spread

transmission of the random access on PRACH channel. The
field is coded according to the following table:
0 0 0 0 3 slots used to spread transmission;
PTPPKF
GS
0 .. 9, Default = 8
this parameter is a parameter used for calculation of number of slots

between two successive Channel request messages on PRACH
channel. The field is coded according to the following table:
0 0 0 0 S = 12
0 0 0 1 S = 15
0 0 1 0 S = 20
0 0 1 1 S = 30
0 1 0 0 S = 41
0 1 0 1 S = 55
0 1 1 0 S = 76
0 1 1 1 S = 109
1 0 0 0 S = 163
1 0 0 1 S = 217
All other values reserved.
106-183
Mr.M.Kaufmann
PTPPKF
GMANRETS
(0..3)-(0..3)-(0..3)-(0..3)
Default: (2)-(2)-(2)-(2)
(GPRS_MAX_RETRANS): this parameter indicates for each priority

level 1 to 4 the maximum number of retransmission allowed. P1: Max
retransmission for priority 1
P2: Max retransmission for priority 2;
Priority 1 represents the highest priority. For each Px parameter the
following table should be applied:
0 0 1 retransmission allowed;
1 1 7 retransmission allowed.
PTPPKF
GMANMSAL
1 .. 7 , Default = 7
1 .. 16, Default = 16
PTPPKF
T3168
0..7, Default = 7
(GPRS_MAX_MS_ALLOCATED): this parameter indicates the

maximum number of MSs that can be multiplexed within one PDCH.
It is composed by two fields: the first indicates the maximum number
of MS that can be multiplexed on one PDCH in Uplink direction
(range is from 1 to 7, Default is 7), the second one indicates the
maximum number of MS that can be multiplexed on one PDCH in
Downlink direction (the range is from 1 to 16, Default is 16).
This value plus one must be multiplied by 500 msec. To obtain the
real value used in PSI
PTPPKF
T3192
0..7, Default = 0
This attribute defines a timer used in the PSI messages.
PTPPKF
INICSCH
CS-1, CS-2,
Default = CS-2
(INITIAL_CODING_SCHEME): this parameter indicates the coding

scheme to be used when the packet transfer starts. The possible
values are CS1 and CS2.
PTPPKF
NTWCOR
NC0, NC1,
Default = NCO 0
PTPPKF
GTEMPOFF
0 .. 7, Default = 1
(NetworK Control Order):this parameter reported in SI 13, PSI 1 and

PSI 5, informs the mobile about the control of cell reselection. Values
can be:
NC0: value 0 MS controlled cell reselection, no meas reporting;
NC1: value 1 MS controlled cell reselection, MS sends meas report;
in the first implementation only NC0 and NC1 will be considered.
(GPRS_TEMPORARY_OFFSET) this attribute applies a negative
offset to C31 for the duration of GPRS_PENALTY_TIME. The value
7 means infinity and the step between 1 to 7 means 10 dB for each
one step.
PTPPKF
GPENTIME
0 .. 31, Default = 0
(GPRS_PENALTY_TIME) this attribute gives the duration for which

the GPRS TEMPORARY OFFSET is applied in cell reselection
procedure. The meaning of the value are the same as described in
PENTIME attribute of BTS object.
PTPPKF
GRESOFF
0 .. 31, Default = 16
(GPRS_RESELECT_OFFSET) this attribute specifies to mobile

station the positive or negative offset and hysteresis to be applied to
GPRS RESELECTION CRITERON. The step value represents 2 dB
and 4dB step; 0 means -52 dB, 31 means +48 dB.
PTPPKF
GCELLRESH
0 .. 7, Default = 2
PTPPKF
C31H
PTPPKF
C32QUAL
PTPPKF
TRESEL
(GPRS_CELL_RESELECT_HYSTERESIS) this attribute indicates

the additional hysteresis which applies in cell for same routing area.
The step value represent 2 dB step; 0 means 0 dB, 7 means 14 dB.
Default =2,
(C31_HYSTERESIS) this attribute indicates if the GPRS reselect
TRUE
hysteresis shall be applied to the C31 criterion. The value 0 means
false while 1 means true,
TRUE .. FALSE, Default =
(C32_QUALIFIER) default FALSE. If C32_QUAL is set, positive
False
GPRS_RESELECT_OFFSET values shall only be applied to the
neighbour cell with the highest RLA value of those cells for which
C32 is compared.
0 .. 7, Default = 0
(T_RESEL) default 0. If the MS has performed an abnormal release

with cell reselection from this cell, the MS is not allowed to reselect
this cell for T_RESEL seconds if another cell is available.
0x00 5 seconds
0x01 10 seconds
0x02 15 seconds
0x03 20 seconds
0x04 30 seconds
0x05 60 seconds
0x06 120 seconds
0x07 300 seconds
107-183
Mr.M.Kaufmann
PTPPKF
RARESH
0 .. 7, Default = 2
(RA_RESELECT_HYSTERESIS) this attribute indicates the

additional histeresis to be applied when the mobile is selecting a cell
in a new routing area. The step value represent 2 dB step; 0 means 0
dB, 7 means 14 dB.,
(GPRS_HCS_THR) this attribute indicates the signal strength
threshold used in HCS cell reselection procedure. The step value
represent 2 dB step; 0 means -110 dB, 31 means -48 dB.
(GPRS_HCS_PRIORITY_CLASS) this attribute represent the
hierarchy Cell Structure priority for cell reselection purpose.
(for power control algorithm at MS) this attribute indicates the ALPHA
value applied in the power control algorithm. The step value represent
0.1 step; 0 means 0.1, 10 means 1.0.,
(T_AVG_W) this attribute indicates the signal strength filter period for
power control in packet idle mode.
PTPPKF
GHCSTH
0 .. 31, Default = 10
PTPPKF
GHCSPC
0 .. 7, Default = 3
PTPPKF
ALPHA
0 .. 10, Default = 3
PTPPKF
TAVGW
0 .. 25, Default = 15
PTPPKF
TAVGT
0 .. 25, Default = 5
PTPPKF
PRPBCCH
0 .. 15, Default = 0
PTPPKF
PCMECH
PTPPKF
NAVGI
PTPPKF
BSPBBLK
PTPPKF
BPAGCHR
0 .. 12, Default = 7
(BS_PAG_BLKS_RES) this parameter indicates the number of

blocks reserved for PAGCH, PDTCH and PACCH for the 52 frames
multiframe case. (See GSM 05.02). The field is optional and if not
included it shall be interpreted as the default value of 0 blocks
reserved for PAGCH, PDTCH and PACCH. If included, the field is
coded according to the following table:
0 0 0 0 0 blocks reserved for PAGCH, PDTCH and PACCH;
0 0 0 1 1 blocks reserved for PAGCH, PDTCH and PACCH;

1 1 0 0 12 blocks reserved for PAGCH, PDTCH and PACCH.
PTPPKF
BPRACHR
0 .. 12, Default = 4
(BS_PRACH_BLKS): this parameter indicates the number of blocks

reserved in a fixed way to the PRACH channel on any PDCH carrying
PCCCH and PBCCH (Only for 52 type PCCCH) (See GSM 05.02).
The parameter is coded according to the following table:
0 0 0 0 No block reserved for PRACH (default)
0 0 0 1 Block B0 reserved for PRACH
0 0 1 0 Block B0, B6 reserved for PRACH
0 0 1 1 Block B0, B6, B3 reserved for PRACH
0 1 0 0 Block B0, B6, B3, B9 reserved for PRACH
0 1 0 1 Block B0, B6, B3, B9, B1 reserved for PRACH
0 1 1 0 Block B0, B6, B3, B9, B1, B7 reserved for PRACH
0 1 1 1 Block B0, B6, B3, B9, B1, B7, B4 reserved for PRACH
1 0 0 0 Block B0, B6, B3, B9, B1, B7, B4, B10 reserved for PRACH
1 0 0 1 Block B0, B6, B3, B9, B1, B7, B4, B10, B2 reserved for
PRACH
1 0 1 0 Block B0, B6, B3, B9, B1, B7, B4, B10, B2, B8 reserved for
PRACH
1 0 1 1 Block B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5 reserved
for PRACH
1 1 0 0 Block B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11
reserved for PRACH
(T_AVG_T) this attribute indicates the signal strength filter period for
power control in packet transfer mode.
(PB) this attribute indicates the power reduction value used by the
BTS on PBCCH blocks, relative to the output power used on BCCH.
MEABCCH, MEAPDTCH, (PC_MEAS_CHAN) this attribute indicates where the mobile station
Default = MEABCCH
shall measure the received power level on the downlink for the
purpose of the uplink power control. The meanings of the value are:
MEABCCH downlink measurements for power control shall be made
on
BCCH;
MEAPDTCH downlink measurements for power control shall be
made on
PDCH.
0 .. 15, Default = 10
(N_AVG_I) this attribute represent an interfering signal strength filter
constant for power control 2(k/2), k = 0, 1, , 15.
0 .. 3, Default = 1
(BS_PBCCH_BLKS) this parameter indicates the number of blocks
allocated to the PBCCH in the multiframe. The field is coded
according to the following table:
0 0 Block B0 used for PBCCH;
0 1 Block B0, B6 used for PBCCH;
1 0 Block B0, B6, B3 used for PBCCH;
1 1 Block B0, B6, B3, B9 used for PBCCH.
108-183
Mr.M.Kaufmann
PTPPKF
DRXTMA
0 .. 7, Default = 7
PTPPKF
CACKTYP
0 .. 1, Default = 0
PTPPKF
GAM
0..31; Default = 3
PTPPKF
GASTRTH-HV
0...100; Default = 10
(DRX_TIMER_MAX) this parameter indicates the maximum value

allowed for the mobile station to request for Non-DRX mode after
packet transfer mode (upper limit for the mobile station timer T3194).
0 0 0 No Non-DRX mode after packet transfer mode
0 0 1 Max. 1 sec. Non-DRX mode after packet transfer mode
0 1 0 Max. 2 sec.
0 1 1 Max. 4 sec.
1 0 0 Max. 8 sec.
1 0 1 Max. 16 sec.
1 1 0 Max. 32 sec.
1 1 1 Max. 64 sec.
(CONTROL_ACK_TYPE): this parameter indicates the format of the
PACKET_CONTROL_ACKNOWLEDGEMENT the MS shall
transmit when polled.
0 PACKET CONTROL ACKNOWLEDGEMENT format is four
access bursts
1 PACKET CONTROL ACKNOWLEDGEMENT format is RLC/MAC
control block
This parameter defines the 'gamma' value applied in the power
control algorithm. The value can be set from 0 dB to 62 dB in steps of
2 dB.
Defines the percentage of idle channel in the cell in order to trigger
the switch between horizontal and vertical allocation.
Defines the percentage of idle channel in the cell in order to trigger
the switch between vertical and horizontal allocation.
It indicates the percentage of available channels dynamically
dedicated by the system to GPRS traffic.
0=UMDB98, 1=UMDB94,
2=UMDB90, 3=UMDB86,
4=UMDB82, 5=UMDB78,
6=UMDB74, 7=ALWAYS,
8=OMDB78, 9=OMDB74,
10=OMDB70, 11=OMDB66,
12=OMDB62, 13=OMDB58,
14=OMDB54, 15=NEVER
0=ALWAYS, 1=MDB28,
2=MDB24, 3=MDB20,
4=MDB16, 5=MDB12,
6=MDB08, 7=MDB04, 8=DB00,
9=DB04, 10=DB08, 11=DB12,
12=DB16, 13=DB20, 14=DB24,
15=DB28
GPRS max number of TCH
reserved.
PTPPKF
GASTRTH-VH
0...100; Default = 20
PTPPKF
GPDPDTCHA
0...100; Default = 30
PTPPKF
QSRHPRI
0..15; Default = 0
PTPPKF
FDDGQO
0..15; Default = 0
PTPPKF
GMAPERTCHRES
0..100 Default = 0
PCMG
PCMGN
0..15
PCMG number of the Gb-interface
PCMG
PCML
this attribute identifies the LICD number, the CIRCUIT number and
the TRUNK (A or B) to which the PCM line is connected.
PCMG
CRC
0 .. 8
0 .. 3
A, B
TRUE
PCMG
CODE
AMI, HDB3, Default =

HDB3
this attribute indicates if CRC-4 signal handling for PCM 30 line or

CRC-6 signal handling for PCM 24 line is Enabled on PCMG line.
Values are FALSE or TRUE
this attribute selects the line transmission code to be provided on the
line. Value are AMI or HDB3.
PCMG
NUA

FALSE
this attribute enables or disables handling of not urgent alarms on

PCMG line.
PCMG
BER
E10_3, E10_4,E10_5
Default:E10_3
(Bit Error Rate) this attribute indicates the threshold that, if exceeded,
the line must be put in Disabled.
PCMG
BAF
0 .. 255, Default = 0
this attribute defines frame alignment bits that can be set by operator.
PCMG
LOWBER
PCMG
REMAL
PCU
PCUN
0=E10_3, 1=E10_4,
2=E10_5, 3=E10_6,
4=E10_7, 5=E10_8,
6=E10_9, Default:3
0 = CCITT
1 = Bellcore
Default value:0
0...5
Lower Bit Error Rate. This attribute is relevant only for PCM24 lines
Remote alarm type. This attribute is relevant only for PCM24 lines
109-183
Number of PCU card
Mr.M.Kaufmann
PCU
NMO
PCU
NSEI
NMO_1,NMO_2,NMO_3,
Default = NMO_2
0 .. 65534
Network mode of operation (I, II and III)
PCU
TNSVCBLK
1 .. 10, Default = 3
PCU
NNSVCBLKR
1 .. 254, Default = 3
this parameter specifies the maximum number of retry performed in

the NSVC block procedure. If the SGSN does not answer to block
procedure, the procedure shall be retried for NNSVCBLKR times.
The value 0 assumes that the procedure is repeated infinite times.
PCU
NNSVCUBLR
1 .. 254, Default = 3
PCU
TNSVCR
1 .. 10, Default = 3
PCU
NNSVCRR
1 .. 254, Default = 10
PCU
TNSVCTST
10 .. 60, Default = 30

the NSVC block procedure. If the SGSN does not answer to unblock
procedure, the procedure shall be retried for NNSVCUBLR times.
The value 0 assumes that the procedure is repeated infinite times.
this timer defines the waiting time for NSVC reset procedure. After a
NSVC reset message sent, the PCU wait TNSVCR seconds for
acknowledge.
the NSVC reset procedure before generating any alarm. If the SGSN
does not answer to reset procedure, the procedure shall be retried
infinitely but after NNSVCRR times an O&M alarm shall be notified.
The value 0 assumes that no alarms are notified.
this timer defines the periodicity of the NSVC test procedure. The test
message are sent to SGSN when NSVC is available every
TNSVCTST times.
PCU
TNSVCPTST
1 .. 10, Default = 3
PCU
NNSVCTSTR
1 .. 30, Default = 10
PCU
NBVCBR
1 .. 30, Default = 3
PCU
NBVCUR
1 .. 30, Default = 3
PCU
NBVCRR
1 .. 30, Default = 3
PCU
T1
2 .. 29, Default = 10
PCU
T2
2 .. 119, Default = 10
PCU
TF1
2 .. 9, Default = 5
PCU
N3101
9 .. 255, Default = 10
PCU
N3103
1 .. 255, Default = 10
PCU
N3105
1 .. 255, Default = 10
PCU
NRLCMAX
20 .. 64, Default = 20
PCU
T3141
1 .. 30, Default = 5
(Network Service Element Identifier): this parameter represents the

PCU area identification. This attribute can be set only if the object
PCU is in Locked state.
this timer defines the waiting time for NSVC block/unblock procedure.
After a NSVC block/unblock message sent, the PCU wait
TNSVCBLK seconds, for acknowledge.
this timer defines the waiting time for NSVC test procedure. If after
TNSVCPTST sec. no answer to test procedure are received, the test
procedure shall be retried.
this parameter defines the number of consecutive retry performed for
test procedure before declaring link not available.
(Number of BVC Block Retries): this parameter used in BVCI block
procedure, indicates the number of repetition of block procedure, in
case of a not answering SGSN, before sending an O&M alarm.
(Number of BVC Unblock Retries): this parameter used in BVCI
unblock procedure, indicates the number of repetition of unblock
procedure, in case of a not answering SGSN, before sending an
O&M alarm.
(Number of BVC Reset Retries): this parameter used in BVCI reset
procedure, indicates the number of repetition of reset procedure, in
case of a not answering SGSN, before sending an O&M alarm.
this timer defines the waiting time for BVCI block/unblock procedure.
After a BVCI block/unblock message sent, the PCU wait T1 seconds,
for acknowledge.
this timer defines the waiting time for BVCI reset procedure. After a
BVCI reset message sent, the PCU wait T2 seconds, for
acknowledge.
this timer defines the time for capacity reporting period used in flow
control algorithm. It corresponds to the C timer reported in the GSM
8.18 recommendation.
this parameter implements the threshold for non valid data error
coming by mobile station after having sent USF. In case this
threshold is reached, the communication with the associated MS is
broken.
this parameter implements the threshold for not received PACKET
CONTROL ACK as answer of the PACKET UPLINK ACK/NACK. In
case this threshold is reached, the communication with the
associated MS is broken.
This parameter implements the threshold for not received RLC/MAC
control message from the MS after sending a RRBP field on
downlink. If this threshold is reached, the communication with the
associated MS is broken
(N_RLC_MAX): when N_RLC_MAX Uplink RLC Block are received,
one PACKET UPLINK ACK/NACK is sent in unacknowledge mode
This timer is started when a tbf is assigned with an immedate
assignment during a packet access procedure; it is stopped when the
110-183
Mr.M.Kaufmann
ms has correctly seized the tbf

PCU
T3169
1 .. 30, Default = 1
This timer (default 5 sec.) defines the waiting time for reuse TFI and
USF after the thresholds N3101 and N3103 are reached.
This attribute defines a timer used in Packet Access Reject
PCU
T3172
0 .. 255, Default = 5
PCU
T3191
1 .. 30, Default = 5
PCU
T3193
1 .. 42, Default = 4
PCU
T3195
0 .. 255, Default = 1
PCU
TEMPCH
PCU
THPROXT
PCU
TIMEDTBFREL
ADJC
ACTIVE
I, A
ADJC
BTSM
0..199
BTSM
ADJC
BTSN
0..23
BTSN
ADJC
GSUP

FALSE
This attributes indicates if the GPRS service is supported or not.
ADJC
GTEMPOFF
0 .. 7, Default = 1
This attribute applies a negative offset to C31 for the duration of

GPRS_PENALITY_TIME.
ADJC
GPENTIME
0 .. 31, Default = 0
ADJC
GRESOFF
0 .. 31, Default = 16
This attribute gives the duration for which the

GPRS_TEMPORARY_OFFSET is applied in cell reselection
procedure.
This attribute specifies to mobile station the positive or negative offset
and hysteresis to be applied to GPRS RESELECTION CRITERIA.
ADJC
GHCSTH
0..31; Default = 10
ADJC
GHCSPC
0 .. 7, Default = 3
Chan
ACTIVE
I, A
(GPRS_HIERARCHYCAL_CELL_STRUCTURE_THRESHOLD)
this attribute
This attribute represent the hierarchy Cell Structure priority for cell
reselection purpose.
Chan
GDCH
TRX
ACTIVE
GPRSPBCCH=1,
GPRSPCCH=2,
RPDTCH=3
I,A
It is used to adjust if the channel is enabled to carry control

informations on the BCCH TRX or if a static PDTCH should be
assigned
TRX
GSUP
0,1 (False,True)
It indicates if the TRX support the GPRS service or not.
this timer defines the waiting time for reuse TFI and USF after having
sent the last RLC block.
Greater than T3192.: this value plus one must be multiplied by 500
msec. to obtain the real value
0x00 PSI Count High Rate = 1

0x01 PSI Count High Rate = 2
0x0f PSI Count High Rate = 16

1 .. 254, Default = 90
(Timer Empty Channel): this timer specifies the time for releasing
PDTCH if no activities are done. This timer should prevent a faster
PDTCH channel allocation/release that can increase TDPC load.
THPROXT1, THPROXT2, (Threshold Proximity Timer): this parameter implements 3 thresholds
THPROXT3
for TH-proximity evaluation. The first threshold range is from 10
Default=500-50-550
msec. to 999 msec., the second threshold range is from 1 sec. to 100
sec., the third threshold range is from 101 sec. to 1000 sec..
0..49 (100msec stepsize) Time delay TBF release. This attribute is used to delay the release of
Default: 15
a DL Temporary Block Flow (TBF).
Relevant GSM specifications

GSM 10.60 gives a complete list of Recommendations impacted by GPRS.
111-183
Mr.M.Kaufmann
Stage 1:
Stage 2:
02.60
General GPRS Overview
03.60
General System
Description and
Network
Architecture
New
Stage 3:
Modifie
d
present
Stage 3:
04.60
RLC/MAC
Radio
Protocol
03.61
Point to
Multipoint Multicast
04.64
LLC
04.65
SNDCP
07.60
User
Interworki
ng
09.61
External
Network
Interworki
ng
08.14
Gb Layer 1
08.18
BSSGP
The Gb
Interface
10.17
Charging
in GPRS
08.16
Gb
Network
Service
05.xx
(.01,.02,.0
3,.05,.08,.
10)
Radio
Interface
08.58 & .
60
Abis and
TRAU
frame
changes
04.08
MAC, RLC
Layer 3
Mobility
Managem
ent
04.03
to.07
GPRS,
system
and
scheduling
informatio
n
11.11
SIM
additions
11.2X
BSS Test
New
Cipherin
g:
03.64
Radio
Architecture
Description
Stage 0
Lawful
Interception
03.62
Point to
Multipoint Group Call
04.61
PTM-M
Services
04.62
PTM-G
Services
09.60
Gn & Gp
Interfaces
09.18
Layer 3
09.16
Gs Layer 2
09.02
Gr and Gd
additions
to MAP
03.20
and others
Security
aspects
03.22
Idle Mode
procedures
11.10,
TBR-19
MS Test
12.xx
O&M
additions
01.61
Ciphering Requirements
112-183
SAGE
Algorithm
Mr.M.Kaufmann
113-183
Mr.M.Kaufmann
GPRS features BR6.0

Horizontal allocation
In BR 5.5 only the BCCH TRX were used for GPRS with the vertical
allocation for the use of GPRS channels. This was done through
multiplexing the maximum number of TBF per PDCH.
The parameter GMANMSAL controlles this for uplink (UL=7) and downlink
(DL=16)
The new feature horizontal allocation changes this behaviour through
the allocation strategy from vertical allocation (VA) to horizontal allocation
(HA).
The HA strategy is intented to distribute the incoming GPRS calls on all
available PDCH of the specific TRX. Through this behaviour not too much
slots are multiplexed on the same PDCH, which increases the transfer
throughput for all the involved mobiles.
In BR 6.0 the BSC will autonomously switch between VA and HA (and vice
versa)
in relation to the percentage of idle channel in the cell.
The aim is to use the HA when the cell is not much loaded.
Also in VA the BSC tries to improve the allocation algorithm through
distributing the
mobiles over different radio channels (before BR 6.0 all mobiles would be
multiplexed over the same TS). This is called then flat distribution.
The GMANPAL parameter is removed in BR 6.0. Two new attributes are
introduced instead.
The first parameter, GPDPDTCHA, indicates the percentage of available
dynamical PDTCH channels (on TRXs in service where GPRS is supported
with GSUP=true). It is used to define the maximum number of dynamic
GPRS channels.
The second new parameter, GASTRTH (composed by two fields), is used
to define the threshold from VA to HA (and vice versa).
This attribute represents the minimum number of idle PDCH to activate
HA (per cell). It has to be intended as a percentage of free PDCH referred
to the number of available channels (TCH and PDCH), except the static
assigned PDTCH, in the whole cell.
When the threshold is reached the BSC switches its strategy from the
vertical to horizontal allocation (and vice versa).
The thresholdIdleChanHV field of the GASTRTH has to be lower than the
thresholdIdleChanVH field.
114-183
Mr.M.Kaufmann
Object/
Package
PTPPKF
DB Name
Range
Meaning
GPDPDTCHA
0..100
PTPPKF
GASTRTH(nHV) 0..100
PTPPKF
GASTRTH(nVH) 0..100
GprsPercentageOfDyna
micPDTCHAvailable
Default = 30
GprsAllocationStrategy
Threshold for the
percentage of idle TS to
pass from horizontal to
vertical allocation
Default = 10
GprsAllocationStrategy
Threshold for the
percentage of idle TS to
pass from vertical to
horizontal allocation
Default = 20
Transfer on non BCCH TRX

In BR 5.5 it was only possible to use the BCCH TRX for GPRS. The need for
a higher number of PDCHs lead to a customer defined TRX planning for
GPRS.
This is realised with the new parameter GSUP (GPRS supported) of each of
the TRX object. It enables/disables the GPRS service on the TRX.
Object/
Package
TRX
DB Name
Range
Meaning
GSUP
True/False
enables/disables the
GPRS service on the
TRX
Constraints:
1.Correspondent PTPPKF created
2.Multislot constraints for TSC and FH
All TS of the TRX with same
TSC
FHSY
MAIO
HSN
3.Complete cell area
Concentric cells
GSM DCS mixed cells with common BCCH
4.PBCCH and PCCCH on BCCH TRX only (PDTCH on any TRX)
115-183
Mr.M.Kaufmann
116-183
Mr.M.Kaufmann
Channel search algorithm:

1.Consider TRX with GSUP=TRUE
2.Consider Service Dependent Channel Allocation
3.Consider Horizontal/Vertical Allocation policy
4.Situation of reserved channels
5.Few other precedences
Last thing: Downgrade of incoming GPRS calls
Power Issues:
It is suggested to choose TRXs with good signal quality.
Planning Aspects:
1. CAPACITY ASPECTS
higher number of PDCHs
increased signalling (LAPD)
2. QoS ASPECTS
power control issues: interference with power controlled CS TCHs
3. COVERAGE ASPECTS
concentric and GSM/DCS cells
Interdependencies with other features:
1.Constraints:
Frequency Hopping Management
Concentric & Common BCCH cells planning
2.Data channels allocation strategies:
Service Dependent Channel Allocation (FRS 0457)
Horizontal vs Vertical Allocation (FRS 0503)
3.Capacity issues:
High Capacity BSC (FRS 0397)
Multiple Abis LAPD Link (FRS 0308)
117-183
Mr.M.Kaufmann
Abbreviations
BCCH
BSC
BSS
BSSGP
BTS
BVC
BVCI
BECN
BER
BSSGP
BVC
BVCI
CCCH
CIR
CS
DE
DLCI
DRX
FCS
FEC
FECN
FRL
GGSN
GMM
GPRS
HLR
HSCSD
IP
LA
LAPD
LLC
MAC
MM
MOC
MS
MSC
MTC
NS
NSEI
NSVC
NSVCI
NSVL
NSVLI
Broadcast Conrol Channel

Base Station Controller
Base Station System
Base Station System GPRS Protocol
Base Transceiver Station
BSSGP Virtual Connection
BSSGP Virtual Connection Identifier
Backward Explicit Congestion Notification
Bit Error Rate
Base Station System GPRS Protocol
Base Station System GPRS Protocol Virtual
Connection
BVC Identifier
Common Control Channel
Committed Information Rate
Coding Scheme
Discard Eligibility Indicator
Data Link Connection Identifier
Discontinuous Reception
Frame Check Sequence
Foreward Error Correction
Forward Explicit Congestion Notification
Frame Relay Link
Gateway GPRS Support Node
GPRS Mobility Management
General Packet Radio System
Home Location Register
High Speed Circuit Switched Data
Internet Protocol
Location Area
Link Access Procedure on the D-channel
Logical Link Control
Media Access Control
Mobility Management
Mobile Originated Call
Mobile Station
Mobile Switching Center
Mobile Terminated Call
Network Service
Network Service Entity Identifier
Network Service Virtual Connection
Network Service Virtual Connection Identifier
Network Service Virtual Link
Network Service Virtual Link Identifier
118-183
Mr.M.Kaufmann
NUA
NUC
PACCH
PAGCH
PBCCH
PCCCH
PCU
PDP
PDT
PDU
PDTCH
PLMN
PNCH
PPCH
PRACH
PSI
PTPPKF
PVC
QoS
RA
RAI
RACH
RACODE
RACOL
RF
RL
RLC
RRBP
SAP
SDU
SGSN
SNDCP
TBF
TFI
TRAU
TSC
UI
UNI
USF
VLR
Not Urgent Alarm

Nailed Up Connection
Packet Associated Control Channel
Packet Access Grant Channel
Packet Broadchast Control Channel
Packet Common Control Channel
Packet Control Unit
Packet Data Protocoll
Packet Data Terminal
Packet Data Unit
Packet Data Traffic Channel
Public Land Mobile Network
Packet Notification Channel
Packet Paging Channel
Packet Random Access Channel
Packet System Information
Point to Point Packet Function
Permanent Virtual Connector
Quality of Service
Routing Area
Routing Area Identity
Random Access Channel
Routing Area Code
Routing Area Colour
Radio Frequency
Relay
Radio Link Control
Relative Reserved Block Period
Service Access Point
Service Data Unit
Serving GPRS Support Node
SubNetwork Dependent Convergence
Protocol
Temporary Block Flow
Temporary Block Flow Identifier
Transcoding and Rate Adaption Unit
Training Sequence Code
Unnumbered Information
User Network Interface
Uplink State Flag
Visitor Location Register
119-183
Mr.M.Kaufmann
Appendix A
The Gb interface may be realised as a:
1. A direct line.
2. Through FR network.
3. Nailed Up Connection through MSC via FR network.
4. NUC through MSC.
SGSN
Network
Router
BSC
Transit
Network
Gb
Network
Router
MSC
SGSN
Network
Router
Gb
Gb
BSC
BSC
The PCM30 (or PCM24) links, supported by the line interface cards of the
BSC are the bearer of the FR links. There are only two options to establish
a FR link in the BSS database:
1. via PCMA (i.e. via MSC).
2. via PCMG (i.e. direct connection).
In the BSS database the Gb interface is created in the same way whether
there is a direct line or intermediate transmission network (FR network)
between the BSC PCU and SGSN. Both realisations are identical from the
BSC PCU point of view. Other configurations must be realised by the
transmission network (no concern of BSC PCU).
Typical commands of a GPRS database are as follows:
Creation of a PCMA link (i.e. via MSC):
CREATE PCMA:NAME=BSC:0/pcma:0,PCMT=0-0,CRC=TRUE,CODE=HDB3,
NUA=FALSE,BER=E10_3,BAF=0,HCICN=0,LOWBER=E10_6;
CREATE
FRL:NAME=BSC:0/frl:0,PCUN=0,GLK=PCMA:0,GTS=1,T391=10,N391=6,
N392=3,N393=4,TCONG=10,TCONOFF=20;
120-183
Mr.M.Kaufmann
CREATE NSVC:NAME=BSC:0/nsvc:0,NSVCI=501,NSVLI=0-151;
Creation of a PCMG link (i.e. direct connection):

CREATE PCMG:NAME=BSC:0/pcmg:0,PCML=1-1-TRUNKA,
CRC=TRUE,CODE=HDB3,NUA=TRUE,BER=E10_3,BAF=0,LOWBER=E10_6;
CREATE
FRL:NAME=BSC:0/frl:1,PCUN=0,GLK=PCMG:0,GTS=1&2&3&4,T391=10,
N391=6,N392=3,N393=4,TCONG=10,TCONOFF=20;
Appendix B
Creation of PCU:
CREATE
PCU:NAME=BSC:0/pcu:0,NMO=NMO_2,NSEI=5,TNSVCBLK=3,NNSVCBLKR=
3
,NNSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30,TNSVCPTST=3,
NNSVCTSTR=10,NBVCBR=3,NBVCUR=3,NBVCRR=3,T1=10,T2=10,TF1=5,
N3101=10,N3103=10,N3105=10,NRLCMAX=20,T3141=5,T3169=5,T3172
=5
,T3191=5,T3193=4,T3195=5,TEMPCH=90,THPROXT=25-50-550;
Creation of PTPPKF:
CREATE PTPPKF:NAME=BSC:0/ptppkf:0,RACODE=31,RACOL=5,
BSCDVMA=15,PKTNDEC=2,PKTNINC=7,PKTNMA=7,GRXLAMI=63,
GMSTXPMAC=31,ABUTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKANA,
GTXINT=10,GS=9,GMANRETS=1-2-3-3,GMANPAL=7,GMANMSAL=7- 16,
121-183
Mr.M.Kaufmann
T3166_68=7,T3192=0,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1,
GPENTIME=0,GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE,
TRESEL=0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15,
TAVGT=5,PRPBCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1,
BPAGCHR=7,BPRACHR=0,DRXTMA=7,CACKTYP=0;
Appendix C (database example)

SET MEL:NAME=MEL:0,MELID=3;
SET BSC:NAME=BSC:0,NETWTYPE=GSMPCS,T3122=5,ERRACT=NOFILTERNOFILTER-FERMAINT-NOFILTERNOFILTER,ENCALSUP=NOENCR,MAXNCELL=6,MSCV=PHASE2CCEFR,OVLST
THR=9500,OVLENTHR=8500,BSCOVLH=TRUE,BTSOVLH=TRUE,MSCOVLH
=TRUE,EISDCCHHO=ENABLE,ENFORCHO=ENABLE,NTWCARD=NTWSN16,A
MONTH=ENABLED(30)-ENABLED(60)ENABLED(90),ASMONTH=ENABLED(30)-ENABLED(60)ENABLED(90),SPENLAW=A_LAW,PCMTYPE=PCM30,EFRSUPP=TRUE,CICFM
=GSM,MSCPOOL=FALSE,HRSPEECH=TRUE,SPEED145=TRUE,ENHSCSD=F
ALSE,ENFOIAHO=FALSE,HOSYNC=NONSYNC,ASUBENCAP=FALSE,ASUBISAT
=FALSE,AISAT=FALSE,EPREHSCSD=DISABLED,MAFIRACHO=2,MADGRLV=2
,NOTFACCH=ALWAYS,DLAPDOVL=TRUE,MEDAFUST=015,MEDAFUPE=UPPE_1H,MASCLOGFS=3,IMSIFSIZ=30,CFS=1,ALRMSEVBT
S=CRITICAL,ALRMSEVBTSM=MAJOR,ALRMSEVCBCL=MAJOR,ALRMSEVLPDL
M=MAJOR,ALRMSEVLPDLR=MAJOR,ALRMSEVLPDLS=MAJOR,ALRMSEVOMAL
=MAJOR,ALRMSEVPCMA=MAJOR,ALRMSEVPCMB=MAJOR,ALRMSEVPCMS=
MAJOR,ALRMSEVTRAU=CRITICAL,ALRMSEVTRX=MAJOR,ALRMSEVPCU=CRI
TICAL,ALRMSEVFRL=MINOR,ALRMSEVNSVC=MINOR,ALRMSEVPTPPKF=MAJ
OR,ALRMSEVPCMG=MAJOR,BSCT1=HLFSEC-12,BSCT3=HLFSEC50,BSCT4=HLFSEC-60,BSCT7=HLFSEC-60,BSCT8=HLFSEC80,BSCT10=HLFSEC-12,BSCT11=HLFSEC-16,BSCT13=HLFSEC50,BSCT17=HLFSEC-20,BSCT18=HLFSEC-60,BSCT19=HLFSEC12,BSCT20=HLFSEC-12,BSCTQHO=HLFSEC120,TCBCSI=0,TRACEMR=TRUE,TRACEMG=1,TRFCT=20,EPA=FALSE,CBCP
H=PH2_CBC,TGUARDTCHSD=SEC00,CPOLICY=NO_PREFERENCE,DGRSTRG
Y=NO_DOWNGRADE,CITASUP=FALSE,LCSNSSC=FALSE,LCSMONTH=ENABL
ED(30)-ENABLED(60)-ENABLED(90);
SET
BSCE:NAME=BSCE:0,ALRMSEVDISK=MAJOR,ALRMSEVDK40=MAJOR,ALRMS
EVEPWR=MAJOR,ALRMSEVIXLT=MAJOR,ALRMSEVLICD=MINOR,ALRMSEVLI
CDS=MINOR,ALRMSEVMEMT=MAJOR,ALRMSEVMPCC=MAJOR,ALRMSEVNT
W=MAJOR,ALRMSEVPPCC=MAJOR,ALRMSEVPPLD=MINOR,ALRMSEVPWRD
122-183
Mr.M.Kaufmann
=MAJOR,ALRMSEVSYNC=MAJOR,ALRMSEVSYNE=MAJOR,ALRMSEVTDPC=M
AJOR,ALRMSEVX25A=MAJOR,ALRMSEVX25D=MAJOR,ALRMSEVPPCU=MINO
R,ALRMSEVPPXL=MAJOR,ALRMSEVPPXU=MINOR;
CREATE EPWR:NAME=EPWR:0;
CREATE EPWR:NAME=EPWR:1;
CREATE LICDS:NAME=LICDS:0;
CREATE LICDS:NAME=LICDS:1;
CREATE
LICD:NAME=LICD:0,ALARMT1=20,ALARMT2=2,ALARMT3=1,ALACOUNT=3
2;
CREATE
LICD:NAME=LICD:1,ALARMT1=200,ALARMT2=10,ALARMT3=1,ALACOUNT
=32;
CREATE
=32;
CREATE
=32;
CREATE
=32;
CREATE
=32;
CREATE PPLD:NAME=PPLD:0;
CREATE
PCU:NAME=PCU:0,NMO=NMO_3,NSEI=78,TNSVCBLK=3,NNSVCBLKR=3,N
NSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30,TNSVCPTST=3,NN
SVCTSTR=10,NBVCBR=3,NBVCUR=3,NBVCRR=3,T1=10,T2=10,TF1=5,N3
101=20,N3103=10,N3105=10,NRLCMAX=20,T3141=5,T3169=1,T3172=
5,T3191=5,T3193=5,T3195=1,TEMPCH=30,THPROXT=500-50-550;
CREATE
PCU:NAME=PCU:1,NMO=NMO_3,NSEI=79,TNSVCBLK=3,NNSVCBLKR=3,N
NSVCUBLR=3,TNSVCR=3,NNSVCRR=10,TNSVCTST=30,TNSVCPTST=3,NN
SVCTSTR=10,NBVCBR=3,NBVCUR=3,NBVCRR=3,T1=10,T2=10,TF1=5,N3
101=20,N3103=10,N3105=10,NRLCMAX=20,T3141=5,T3169=1,T3172=
5,T3191=5,T3193=5,T3195=1,TEMPCH=30,THPROXT=500-50-550;
CREATE PCMB:NAME=PCMB:0,PCML=12,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=255,LREDUNEQ=
DUPLEX,L1CTS=TSL_28SSL_0,LOWBER=E10_3,REMAL=<NULL>,WMOD=DOUBLE_TRUNK;
123-183
Mr.M.Kaufmann
CREATE PCMB:NAME=PCMB:3,PCML=10,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=255,LREDUNEQ=
SIMPLEXA,L1CTS=<NULL>,LOWBER=E10_9,REMAL=<NULL>,WMOD=DO
UBLE_TRUNK;
CREATE PCMB:NAME=PCMB:33,PCML=01,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=0,LREDUNEQ=SI
MPLEXA,L1CTS=<NULL>,LOWBER=E10_3,REMAL=<NULL>,WMOD=DOUB
LE_TRUNK;
CREATE PCMS:NAME=PCMS:0,PCML=00,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=255,LREDUNEQ=
SIMPLEXA,LOWBER=E10_3,REMAL=<NULL>,WMOD=DOUBLE_TRUNK;
CREATE TRAU:NAME=TRAU:0,PCMSN=0,TSYNC=400,EXPSWV="02-06-0101-00-22_01-1214",ALLCRIT=NOT_COMPATIBLE_WITH_CROSSCONNECT,SALUNAME="TRAU
BOCA001",TEI=0,ETFO=FALSE;
CREATE LPDLS:NAME=TRAU:0/LPDLS:0,ASUBCH=0-3,LAPDPOOL=0;
CREATE PCMA:NAME=PCMA:0,PCMT=00,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=255,HCICN=0,LO
WBER=E10_3,REMAL=<NULL>,DEFPOOLTYP=POOL_NOTDEF;
SET
TSLA:NAME=PCMA:0/TSLA:1,VOLUL=12,VOLDL=12,POOLTYP=POOL_NOTD
EF;
SET
EF;
SET
EF;
SET
EF;
SET
EF;
SET
EF;
SET
EF;
SET
EF;
SET
EF;
124-183
Mr.M.Kaufmann
SET
TSLA:NAME=PCMA:0/TSLA:10,VOLUL=12,VOLDL=12,POOLTYP=POOL_NOT
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
125-183
Mr.M.Kaufmann
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
SET
DEF;
CREATE PCMG:NAME=PCMG:0,PCML=1-1TRUNKA,CRC=TRUE,CODE=HDB3,NUA=FALSE,BER=E10_3,BAF=0,LOWBE
R=E10_3,REMAL=<NULL>;
CREATE
FRL:NAME=FRL:0,PCUN=0,GLK=PCMG:0,GTS=1&2&3&4,T391=10,N391=
6,N392=3,N393=4,TCONG=10,TCONOFF=20,FRSTD=ITU;
CREATE
FRL:NAME=FRL:1,PCUN=1,GLK=PCMA:0,GTS=31,T391=10,N391=6,N392
=3,N393=4,TCONG=10,TCONOFF=20,FRSTD=ITU;
CREATE NSVC:NAME=NSVC:0,NSVCI=1780,NSVLI=0-780;
CREATE NSVC:NAME=NSVC:1,NSVCI=1790,NSVLI=1-790;
CREATE BTSM:NAME=BTSM:0,EXPSWV="01-01-14-00-12-00_02-0124",SHLAPDIT=15,OMLAPDRT=30,EMT1=1,EMT2=1,SALUNAME="BTSMBO
CA000",PCMCON0=PCMB_0-PORT_0,PCMCON1=PCMB_33PORT_2,FLAPDOVLTH=80-70,SLAPDOVLTH=9080,LAPDOVLT=10,TEI=0,LPDLMSAT=FALSE;
CREATE LPDLM:NAME=BTSM:0/LPDLM:0,ABISCH=0-1-0,LAPDPOOL=1;
CREATE LPDLM:NAME=BTSM:0/LPDLM:1,ABISCH=33-1-0,LAPDPOOL=2;
CREATE BTS:NAME=BTSM:0/BTS:0,CELLGLID="555"-"10"-2040020401,BSIC=00,PLMNP=255,CELLRESH=2,MSTXPMAXGSM=<NULL>,MSTXPMAXDCS=<
NULL>,MSTXPMAXPCS=31,RXLEVAMI=6,RDLNKTO=7,RACHBT=127,RACHL
AS=204,TCCCHLDI=100,PCCCHLDI=255,FACCHQ=5,CELLTYP=STDCELL,SY
SID=PCS1900,BCCHFREQ=512,CALLF01=517,CALLF02=522,CALLF03=52
7,CALLF04=800,CALLF05=802,CALLF06=804,CALLF07=806,CALLF08=80
8,CALLF09=810,CALLF10=<NULL>,CALLF11=<NULL>,CALLF12=<NULL>
126-183
Mr.M.Kaufmann
,CALLF13=<NULL>,CALLF14=<NULL>,CALLF15=<NULL>,CALLF16=<NU
LL>,CALLF17=<NULL>,CALLF18=<NULL>,CALLF19=<NULL>,CALLF20=<
NULL>,CALLF21=<NULL>,CALLF22=<NULL>,CALLF23=<NULL>,CALLF24
=<NULL>,CALLF25=<NULL>,CALLF26=<NULL>,CALLF27=<NULL>,CALL
F28=<NULL>,CALLF29=<NULL>,CALLF30=<NULL>,CALLF31=<NULL>,C
ALLF32=<NULL>,CALLF33=<NULL>,CALLF34=<NULL>,CALLF35=<NULL
>,CALLF36=<NULL>,CALLF37=<NULL>,CALLF38=<NULL>,CALLF39=<N
ULL>,CALLF40=<NULL>,CALLF41=<NULL>,CALLF42=<NULL>,CALLF43=
<NULL>,CALLF44=<NULL>,CALLF45=<NULL>,CALLF46=<NULL>,CALLF4
7=<NULL>,CALLF48=<NULL>,CALLF49=<NULL>,CALLF50=<NULL>,CAL
LF51=<NULL>,CALLF52=<NULL>,CALLF53=<NULL>,CALLF54=<NULL>,
CALLF55=<NULL>,CALLF56=<NULL>,CALLF57=<NULL>,CALLF58=<NUL
L>,CALLF59=<NULL>,CALLF60=<NULL>,CALLF61=<NULL>,CALLF62=<
NULL>,CALLF63=<NULL>,CRESPARI=1,CRESOFF=1,TEMPOFF=1,PENTIME
=0,CBQ=0,NMULBAC=0,CONCELL=FALSE,BTSHSCSD=FALSE,PUREBBSIG4
4CONF=FALSE,MAXRETR=ONE,NSLOTST=9,NY1=20,NBLKACGR=1,NFRAM
EPG=2,MSTXPMAXCH=2,PWROFS=0,ASCISER=ASCI_DISABLED,NOCHFBLK
=1,NOCHBLKN=1,INTCLASS=FALSE,INTAVEPR=31-10-25-4055,RFRSINDP=60,CELLBARR=FALSE,CREALL=NOTALLOWED,NALLWACC=A
LLALLOWED,EC=FALSE,DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFS
HNH,IMSIATDT=FALSE,T3212=6,PWROUT=M10DB-M6DBDB5,DIRTCHASS=NOSDCCHMS,BMONTH=DISABLED(0)-DISABLED(0)DISABLED(0),BSMONTH=ENABLED(30)-ENABLED(60)ENABLED(90),EARCLM=TRUE,HOPMODE=SYNHOP,EEXCDIST=FALSE,EQ=D
ISABLED,QL=50,EPRE=DISABLED,T200=44-31-41-90-90-90135,T3101=HLFSEC-12,T3105=MS10-4,T3109=HLFSEC30,T3111=HLFSEC3,TSYNC=400,TSYNCUL=1000,TSYNCDL=1000,TSYNCR=400,TTRAU=400,
ENANCD=DISABLED,NCDP1=H51,NCDP2=NOTUSED,TGRANT=4,NRPGRANT=20,VGRULF=2,TNOCH=16,EH
RACT=FALSE,HRACTT1=6000,HRACTT2=6000,SDCCHCONGTH=100,ASCIU
LR=ULRDISABLE,TUPLREP=20,EEOTD=FALSE,AMRFRC1=RATE_01,AMRFRT
H12=6-0,AMRFRC2=RATE_03,AMRFRTH23=120,AMRFRC3=RATE_06,AMRFRTH34=240,AMRFRC4=RATE_08,AMRHRC1=RATE_01,AMRHRTH12=180,AMRHRC2=RATE_02,AMRHRTH23=240,AMRHRC3=RATE_03,AMRHRTH34=<NULL>,AMRHRC4=<NULL>,AMRFRI
C=START_MODE_FR,AMRHRIC=START_MODE_HR,AMRLKAT=100,QSRHI=N
EVER,FDDQMI=MDB20,FDDQO=DB00,QSRHCINI=QSEARCHI,FDDREPQTY=
RSCP,FDDMURREP=0,UMTSSRHPRI=FALSE;
SET
PWRC:NAME=BTSM:0/BTS:0/PWRC:0,EBSPWRC=FALSE,EMSPWRC=TRUE,P
WRINCSS=DB4,PWREDSS=DB2,PWRCONF=2,PCONINT=0,PAVRLEV=41,PAVRQUAL=42,LOWTLEVD=15,UPTLEVD=20,LOWTLEVU=10,UPTLEVU=15,LOWTQUAD=
5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=24,EPWCRLFW=FA
127-183
Mr.M.Kaufmann
LSE,PCRLFTH=12,EBSPWCR=FALSE,LOWTQUAMRDL=10,LOWTQUAMRUL=
10,UPTQUAMRDL=13,UPTQUAMRUL=13;
CREATE
PTPPKF:NAME=BTSM:0/BTS:0/PTPPKF:0,RACODE=80,RACOL=0,BSCDVMA=
15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=6,GMSTXPMAC=15,ABU
TYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4,GTXINT=3,GS=0,GMANRE
TS=2-2-2-2,GMANMSAL=716,T3168=7,T3192=0,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1,GPENTI
ME=0,GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE,TRESEL=
0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15,TAVGT=5,PRP
BCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1,BPAGCHR=0,BPRACH
R=0,DRXTMA=7,CACKTYP=1,GAM=3,GASTRTH=1020,GPDPDTCHA=0,QSRHPRI=NEVER,FDDGQO=DB00;
CREATE
TRX:NAME=BTSM:0/BTS:0/TRX:0,TRXFREQ=BCCHFREQ,PWRRED=6,RADIO
MR=ON,RADIOMG=1,MOEC=FALSE,TRXAREA=NONE,LPDLMN=0,GSUP=FA
LSE;
CREATE
TRX:NAME=BTSM:0/BTS:0/TRX:1,TRXFREQ=CALLF01,PWRRED=6,RADIOM
R=ON,RADIOMG=1,MOEC=FALSE,TRXAREA=NONE,LPDLMN=0,GSUP=FALS
E;
CREATE
FHSY:NAME=BTSM:0/BTS:0/FHSY:1,HSN=63,MOBALLOC=CALLF01&CALLF0
2&CALLF03&CALLF04&CALLF05&CALLF06&CALLF07&CALLF09,AMRFRC1=
RATE_01,AMRFRTH12=6-0,AMRFRC2=RATE_03,AMRFRTH23=120,AMRFRC3=RATE_06,AMRFRTH34=240,AMRFRC4=RATE_08,AMRHRC1=RATE_01,AMRHRTH12=180,AMRHRC2=RATE_02,AMRHRTH23=240,AMRHRC3=RATE_03,AMRHRTH34=<NULL>,AMRHRC4=<NULL>,AMRFRI
C=START_MODE_FR,AMRHRIC=START_MODE_HR;
CREATE
CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:0,CHTYPE=BCBCH,TERTCH=<N
ULL>,FHSYID=0,MAIO=0,TSC=<NULL>,EXTMODE=FALSE,GDCH=<NULL>
,CHPOOLTYP=<NULL>;
CREATE
CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:1,CHTYPE=TCHF_HLF,TERTCH=0100,FHSYID=0,MAIO=0,TSC=0,EXTMODE=FALSE,GDCH=<NULL>,CHPOOLTY
P=<NULL>;
CREATE
P=<NULL>;
CREATE
CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:3,CHTYPE=SDCCH,TERTCH=<NU
128-183
Mr.M.Kaufmann
LL>,FHSYID=0,MAIO=0,TSC=<NULL>,EXTMODE=FALSE,GDCH=<NULL>,
CHPOOLTYP=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
CHAN:NAME=BTSM:0/BTS:0/TRX:1/CHAN:0,CHTYPE=TCHF_HLF,TERTCH=0112,FHSYID=0,MAIO=0,TSC=<NULL>,EXTMODE=FALSE,GDCH=<NULL>,CH
POOLTYP=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
129-183
Mr.M.Kaufmann
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE
P=<NULL>;
CREATE BTS:NAME=BTSM:0/BTS:1,CELLGLID="555"-"10"-2040020402,BSIC=01,PLMNP=255,CELLRESH=2,MSTXPMAXGSM=<NULL>,MSTXPMAXDCS=<
NULL>,MSTXPMAXPCS=31,RXLEVAMI=6,RDLNKTO=7,RACHBT=127,RACHL
AS=204,TCCCHLDI=100,PCCCHLDI=255,FACCHQ=5,CELLTYP=STDCELL,SY
SID=PCS1900,BCCHFREQ=532,CALLF01=537,CALLF02=542,CALLF03=<N
CALLF19=<NULL>,CALLF20=<NULL>,CALLF21=<NULL>,CALLF22=<NUL
L>,CALLF23=<NULL>,CALLF24=<NULL>,CALLF25=<NULL>,CALLF26=<
NULL>,CALLF27=<NULL>,CALLF28=<NULL>,CALLF29=<NULL>,CALLF30
=<NULL>,CALLF31=<NULL>,CALLF32=<NULL>,CALLF33=<NULL>,CALL
F34=<NULL>,CALLF35=<NULL>,CALLF36=<NULL>,CALLF37=<NULL>,C
ALLF38=<NULL>,CALLF39=<NULL>,CALLF40=<NULL>,CALLF41=<NULL
>,CALLF42=<NULL>,CALLF43=<NULL>,CALLF44=<NULL>,CALLF45=<N
CALLF61=<NULL>,CALLF62=<NULL>,CALLF63=<NULL>,CRESPARI=1,CR
ESOFF=1,TEMPOFF=1,PENTIME=0,CBQ=0,NMULBAC=0,CONCELL=FALSE,
BTSHSCSD=FALSE,PUREBBSIG44CONF=FALSE,MAXRETR=ONE,NSLOTST=
9,NY1=20,NBLKACGR=1,NFRAMEPG=2,MSTXPMAXCH=2,PWROFS=0,ASCI
SER=ASCI_DISABLED,NOCHFBLK=1,NOCHBLKN=1,INTCLASS=FALSE,INTAV
EPR=31-10-25-4055,RFRSINDP=60,CELLBARR=FALSE,CREALL=NOTALLOWED,NALLWACC=A
LLALLOWED,EC=FALSE,DTXDLFR=FALSE,DTXDLHR=FALSE,DTXUL=SHNFS
HNH,IMSIATDT=FALSE,T3212=6,PWROUT=M10DB-M6DBDB5,DIRTCHASS=FALSE,BMONTH=ENABLED(30)-ENABLED(60)ENABLED(90),BSMONTH=ENABLED(30)-ENABLED(60)130-183
Mr.M.Kaufmann
ENABLED(90),EARCLM=FALSE,HOPMODE=BBHOP,EEXCDIST=FALSE,EQ=DI
SABLED,QL=50,EPRE=DISABLED,T200=44-31-41-90-90-90135,T3101=HLFSEC-12,T3105=MS10-4,T3109=HLFSEC30,T3111=HLFSEC3,TSYNC=400,TSYNCUL=1000,TSYNCDL=1000,TSYNCR=400,TTRAU=400,
ENANCD=DISABLED,NCDP1=H51,NCDP2=NOTUSED,TGRANT=4,NRPGRANT=20,VGRULF=2,TNOCH=16,EH
RACT=FALSE,HRACTT1=6000,HRACTT2=6000,SDCCHCONGTH=100,ASCIU
LR=ULRDISABLE,TUPLREP=20,EEOTD=FALSE,AMRFRC1=RATE_01,AMRFRT
H12=6-0,AMRFRC2=RATE_03,AMRFRTH23=120,AMRFRC3=RATE_06,AMRFRTH34=240,AMRFRC4=RATE_08,AMRHRC1=RATE_01,AMRHRTH12=180,AMRHRC2=RATE_02,AMRHRTH23=240,AMRHRC3=RATE_03,AMRHRTH34=<NULL>,AMRHRC4=<NULL>,AMRFRI
C=START_MODE_FR,AMRHRIC=START_MODE_HR,AMRLKAT=100,QSRHI=N
EVER,FDDQMI=MDB20,FDDQO=DB00,QSRHCINI=QSEARCHI,FDDREPQTY=
RSCP,FDDMURREP=0,UMTSSRHPRI=FALSE;
SET
PWRC:NAME=BTSM:0/BTS:1/PWRC:0,EBSPWRC=FALSE,EMSPWRC=FALSE,P
WRINCSS=DB4,PWREDSS=DB2,PWRCONF=2,PCONINT=0,PAVRLEV=41,PAVRQUAL=42,LOWTLEVD=15,UPTLEVD=20,LOWTLEVU=10,UPTLEVU=15,LOWTQUAD=
5,UPTQUAD=4,LOWTQUAU=5,UPTQUAU=4,RDLNKTBS=24,EPWCRLFW=FA
LSE,PCRLFTH=12,EBSPWCR=FALSE,LOWTQUAMRDL=10,LOWTQUAMRUL=
10,UPTQUAMRDL=13,UPTQUAMRUL=13;
CREATE
PTPPKF:NAME=BTSM:0/BTS:1/PTPPKF:0,RACODE=81,RACOL=0,BSCDVMA
=15,PKTNDEC=2,PKTNINC=2,PKTNMA=4,GRXLAMI=6,GMSTXPMAC=15,AB
UTYP=ACBU8BIT,RAARET=TRUE,GPATH=PKAAP4,GTXINT=3,GS=0,GMANR
ETS=2-2-2-2,GMANMSAL=716,T3168=7,T3192=0,INICSCH=CS2,NTWCOR=NC0,GTEMPOFF=1,GPENTI
ME=0,GRESOFF=0,GCELLRESH=2,C31H=TRUE,C32QUAL=FALSE,TRESEL=
0,RARESH=2,GHCSTH=10,GHCSPC=3,ALPHA=3,TAVGW=15,TAVGT=5,PRP
BCCH=0,PCMECH=MEABCCH,NAVGI=10,BSPBBLK=1,BPAGCHR=0,BPRACH
R=0,DRXTMA=7,CACKTYP=1,GAM=3,GASTRTH=1020,GPDPDTCHA=0,QSRHPRI=NEVER,FDDGQO=DB00;
CREATE
TRX:NAME=BTSM:0/BTS:1/TRX:0,TRXFREQ=BCCHFREQ,PWRRED=6,RADIO
MR=ON,RADIOMG=1,MOEC=TRUE,TRXAREA=NONE,LPDLMN=0,GSUP=FAL
SE;
CREATE
TRX:NAME=BTSM:0/BTS:1/TRX:1,TRXFREQ=CALLF01,PWRRED=6,RADIOM
R=OFF,RADIOMG=254,MOEC=FALSE,TRXAREA=NONE,LPDLMN=0,GSUP=F
ALSE;
CREATE
FHSY:NAME=BTSM:0/BTS:1/FHSY:1,HSN=63,MOBALLOC=CALLF01&BCCHF
REQ,AMRFRC1=RATE_01,AMRFRTH12=6131-183
Mr.M.Kaufmann
0,AMRFRC2=RATE_03,AMRFRTH23=120,AMRFRC3=RATE_06,AMRFRTH34=240,AMRFRC4=RATE_08,AMRHRC1=RATE_01,AMRHRTH12=180,AMRHRC2=RATE_02,AMRHRTH23=240,AMRHRC3=RATE_03,AMRHRTH34=<NULL>,AMRHRC4=<NULL>,AMRFRI
CREATE
FHSY:NAME=BTSM:0/BTS:1/FHSY:2,HSN=0,MOBALLOC=CALLF01,AMRFRC1
=RATE_01,AMRFRTH12=6-0,AMRFRC2=RATE_03,AMRFRTH23=120,AMRFRC3=RATE_06,AMRFRTH34=240,AMRFRC4=RATE_08,AMRHRC1=RATE_01,AMRHRTH12=180,AMRHRC2=RATE_02,AMRHRTH23=240,AMRHRC3=RATE_03,AMRHRTH34=<NULL>,AMRHRC4=<NULL>,AMRFRI
CREATE
CHAN:NAME=BTSM:0/BTS:1/TRX:0/CHAN:0,CHTYPE=BCBCH,TERTCH=<NU
CHPOOLTYP=<NULL>;
CREATE
CHAN:NAME=BTSM:0/BTS:1/TRX:0/CHAN:1,CHTYPE=SDCCH,TERTCH=<NU
CHPOOLTYP=<NULL>;
CREATE
POOLTYP=<NULL>;
CREATE
POOLTYP=<NULL>;
CREATE
POOLTYP=<NULL>;
CREATE
POOLTYP=<NULL>;
CREATE
POOLTYP=<NULL>;
132-183
Mr.M.Kaufmann
CREATE
CHAN:NAME=BTSM:0/BTS:1/TRX:1/CHAN:3,CHTYPE=TCHFULL,TERTCH=0153,FHSYID=1,MAIO=1,TSC=1,EXTMODE=FALSE,GDCH=<NULL>,CHPOOLTY
P=<NULL>;
CREATE TGTBTS:NAME=TGTBTS:0,CELLGLID="555"-"10"-1100011005,BSIC=71,BCCHFREQ=113,SYSID=BB900,MSTXPMAXGSM=5,MSTXPMAXDCS=<NU
LL>,MSTXPMAXPCS=<NULL>;
SET
HAND:NAME=BTSM:0/BTS:0/HAND:0,INTERCH=TRUE,INTRACH=FALSE,IER
CHOSDCCH=TRUE,IRACHOSDCCH=TRUE,LOTERCH=FALSE,LOTRACH=TRU
E,RXQUALHO=FALSE,RXLEVHO=FALSE,DISTHO=TRUE,PBGTHO=TRUE,NCE
LL=6,THORQST=5,HOAVELEV=8-1,HOAVQUAL=82,HOAVDIST=8,HOAVPWRB=31,HOLTHLVDL=63,HOTDLINT=20,HOLTHLVUL
=20,HOTULINT=20,HOLTHQUDL=0,HOLTHQUUL=0,HOTMSRM=34,DPBGTH
O=FALSE,HIERC=FALSE,PL=7,HIERF=RANK1,CCDIST=FALSE,HORXLVDLI=2
6,HORXLVDLO=32,HOCCDIST=5,ININHO=FALSE,CCELL1=<NULL>,CCELL2
=<NULL>,EXTCHO=FALSE,HOTMSRME=100,HOMSTAM=32,HOMRGTA=4,
NOBAKHO=FALSE,NOFREPHO=FALSE,MAXFAILHO=4,ELIMITCH=FALSE,MAI
RACHO=10,TINOIERCHO=60,ERUDGR=FALSE,TINHRUGR=10,TINHRDGR=
5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2,RHOLTQUL=3,
RHOLTQDL=3,EFULHO=FALSE,THLEVFULHO=30,ALEVFULHO=22,TRFHOE=FALSE,TRFHOT=10,TRFKPRI=FALSE,TRFHITH=90,TRFLTH=70,T
RFMMA=9,TRFMS=3,ELEVHOM=FALSE,AMRACMRDL=5,HOLTHQAMRDL=8,
HOLTHQAMRUL=8,HOTHAMRCDL=23,HOTHAMRCUL=23,HOTHAMRDDL=1
0,HOTHAMRDUL=10;
SET
BTS:NAME=BTSM:0/BTS:0,SMSCBUSE=TRUE,HOPP=FALSE,EXCDIST=35;
CREATE
ADJC:NAME=BTSM:0/BTS:0/ADJC:0,TGTCELL=BTSM:0/BTS:1,RXLEVMIN=20
,HOM=40,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,FH
ORLMO=6,TIMERFHO=12,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=30,TI
NHFAIHO=5,GSUP=FALSE,GTEMPOFF=<NULL>,GPENTIME=<NULL>,GRES
OFF=<NULL>,GHCSTH=<NULL>,GHCSPC=<NULL>,FULHOC=FALSE,FULR
XLVMOFF=69,TRFHOM=67,BHOFOT=100,LEVHOM=69,USG=SI_2_5;
SET
HAND:NAME=BTSM:0/BTS:1/HAND:0,INTERCH=TRUE,INTRACH=TRUE,IERC
HOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE,LOTRACH=TRUE
,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO=TRUE,NCELL
=6,THORQST=5,HOAVELEV=8-1,HOAVQUAL=82,HOAVDIST=8,HOAVPWRB=31,HOLTHLVDL=20,HOTDLINT=20,HOLTHLVUL
133-183
Mr.M.Kaufmann
0,HOTHAMRDUL=10;
SET
BTS:NAME=BTSM:0/BTS:1,SMSCBUSE=TRUE,HOPP=TRUE,EXCDIST=35;
CREATE
SET
HAND:NAME=BTSM:0/BTS:2/HAND:0,INTERCH=FALSE,INTRACH=FALSE,IER
CHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE,LOTRACH=TRU
E,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO=TRUE,NCEL
L=6,THORQST=5,HOAVELEV=8-1,HOAVQUAL=82,HOAVDIST=8,HOAVPWRB=31,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL
O=FALSE,HIERC=TRUE,PL=7,HIERF=RANK1,CCDIST=FALSE,HORXLVDLI=2
0,HOTHAMRDUL=10;
SET
BTS:NAME=BTSM:0/BTS:2,SMSCBUSE=TRUE,HOPP=FALSE,EXCDIST=35;
CREATE
0,HOM=40,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,F
HORLMO=6,TIMERFHO=12,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=30,
TINHFAIHO=5,GSUP=FALSE,GTEMPOFF=<NULL>,GPENTIME=<NULL>,GRE
SOFF=<NULL>,GHCSTH=<NULL>,GHCSPC=<NULL>,FULHOC=FALSE,FUL
RXLVMOFF=69,TRFHOM=67,BHOFOT=100,LEVHOM=69,USG=SI_2_5;
SET
HOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE,LOTRACH=TRUE
,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=FALSE,PBGTHO=TRUE,NCELL
134-183
Mr.M.Kaufmann
0,HOTHAMRDUL=10;
SET
BTS:NAME=BTSM:9/BTS:0,SMSCBUSE=FALSE,HOPP=FALSE,EXCDIST=35;
CREATE
SET
HOSDCCH=TRUE,IRACHOSDCCH=TRUE,LOTERCH=TRUE,LOTRACH=TRUE,
RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO=TRUE,NCELL
0,HOTHAMRDUL=10;
SET
CREATE
135-183
Mr.M.Kaufmann
SET
HAND:NAME=BTSM:45/BTS:0/HAND:0,INTERCH=TRUE,INTRACH=TRUE,IER
E,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=FALSE,PBGTHO=FALSE,NCE
0,HOTHAMRDUL=10;
SET
CREATE
SET
E,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO=TRUE,NCEL
L=6,THORQST=5,HOAVELEV=8-2,HOAVQUAL=62,HOAVDIST=8,HOAVPWRB=8,HOLTHLVDL=10,HOTDLINT=35,HOLTHLVUL
=<NULL>,EXTCHO=FALSE,HOTMSRME=99,HOMSTAM=32,HOMRGTA=4,N
OBAKHO=TRUE,NOFREPHO=TRUE,MAXFAILHO=2,ELIMITCH=TRUE,MAIRAC
HO=2,TINOIERCHO=60,ERUDGR=FALSE,TINHRUGR=10,TINHRDGR=5,RAV
EW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2,RHOLTQUL=3,RHOL
TQDL=3,EFULHO=FALSE,THLEVFULHO=6,ALEVFULHO=21,TRFHOE=FALSE,TRFHOT=10,TRFKPRI=FALSE,TRFHITH=90,TRFLTH=70,T
136-183
Mr.M.Kaufmann
0,HOTHAMRDUL=10;
SET
BTS:NAME=BTSM:66/BTS:0,SMSCBUSE=FALSE,HOPP=FALSE,EXCDIST=35,
EEXCDIST=TRUE;
SET
O=TRUE,HIERC=FALSE,PL=0,HIERF=RANK0,CCDIST=FALSE,HORXLVDLI=5,
HORXLVDLO=6,HOCCDIST=5,ININHO=TRUE,CCELL1=BTSM:77/BTS:1,CCEL
L2=<NULL>,EXTCHO=FALSE,HOTMSRME=100,HOMSTAM=32,HOMRGTA=
4,NOBAKHO=FALSE,NOFREPHO=FALSE,MAXFAILHO=4,ELIMITCH=FALSE,M
AIRACHO=10,TINOIERCHO=60,ERUDGR=FALSE,TINHRUGR=10,TINHRDGR
=5,RAVEW=8,RUGRUL=1,RUGRDL=1,RDGRUL=2,RDGRDL=2,RHOLTQUL=
3,RHOLTQDL=3,EFULHO=FALSE,THLEVFULHO=30,ALEVFULHO=33,TRFHOE=FALSE,TRFHOT=10,TRFKPRI=FALSE,TRFHITH=90,TRFLTH=70,T
0,HOTHAMRDUL=10;
SET
CREATE
ADJC:NAME=BTSM:77/BTS:0/ADJC:0,TGTCELL=BTSM:77/BTS:1,RXLEVMIN=
CREATE
12,HOM=80,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,
FHORLMO=6,TIMERFHO=12,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=3
0,TINHFAIHO=7,GSUP=FALSE,GTEMPOFF=<NULL>,GPENTIME=<NULL>,G
RESOFF=<NULL>,GHCSTH=<NULL>,GHCSPC=<NULL>,FULHOC=TRUE,F
ULRXLVMOFF=14,TRFHOM=67,BHOFOT=100,LEVHOM=69,USG=SI_2_5;
CREATE
137-183
Mr.M.Kaufmann
CREATE
RESOFF=<NULL>,GHCSTH=<NULL>,GHCSPC=<NULL>,FULHOC=FALSE,F
CREATE
CREATE
CREATE
CREATE
CREATE
CREATE
138-183
Mr.M.Kaufmann
CREATE
SET
E,RXQUALHO=TRUE,RXLEVHO=FALSE,DISTHO=FALSE,PBGTHO=FALSE,NC
ELL=6,THORQST=5,HOAVELEV=8-1,HOAVQUAL=82,HOAVDIST=8,HOAVPWRB=16,HOLTHLVDL=10,HOTDLINT=20,HOLTHLVUL
6,HORXLVDLO=32,HOCCDIST=5,ININHO=TRUE,CCELL1=<NULL>,CCELL2
0,HOTHAMRDUL=10;
SET
CREATE
SET
139-183
Mr.M.Kaufmann
0,HOTHAMRDUL=10;
SET
CREATE
CREATE
SET
0,HOTHAMRDUL=10;
SET
CREATE
140-183
Mr.M.Kaufmann
SET
CHOSDCCH=FALSE,IRACHOSDCCH=FALSE,LOTERCH=TRUE,LOTRACH=FAL
SE,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=FALSE,PBGTHO=FALSE,NC
ELL=6,THORQST=5,HOAVELEV=8-1,HOAVQUAL=82,HOAVDIST=8,HOAVPWRB=13,HOLTHLVDL=20,HOTDLINT=20,HOLTHLVUL
0,HOTHAMRDUL=10;
SET
CREATE
CREATE
ADJC:NAME=BTSM:99/BTS:0/ADJC:1,TGTCELL=TGTBTS:0,RXLEVMIN=10,H
OM=30,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,FHO
RLMO=0,TIMERFHO=12,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=30,TIN
HFAIHO=7,GSUP=FALSE,GTEMPOFF=<NULL>,GPENTIME=<NULL>,GRESO
FF=<NULL>,GHCSTH=<NULL>,GHCSPC=<NULL>,FULHOC=FALSE,FULRX
LVMOFF=69,TRFHOM=67,BHOFOT=100,LEVHOM=30,USG=SI_2_5;
SET
CHOSDCCH=TRUE,IRACHOSDCCH=TRUE,LOTERCH=TRUE,LOTRACH=TRUE
,RXQUALHO=TRUE,RXLEVHO=TRUE,DISTHO=TRUE,PBGTHO=FALSE,NCELL
141-183
Mr.M.Kaufmann
0,HOTHAMRDUL=10;
SET
CREATE
CREATE OPC:NAME=OPC:0,SS7MTPTYP=CCITT,OPC=52-41,MSCSPC=841,NTWIND=NAT0,BSSAPSSN=254,MSCPERTFLAG=TRUE,M2T1=450,M2T2
=1000,M2T3=10,M2T4N=80,M2T4E=5,M2T5=1,M2T6=60,M2T7=20,FLO
WCTH=3,CONGTH=0,SANTIME=10,ERRCORMTD=BASIC_ERROR_CORRECT
ION,N1=110,N2=3000,M3T1=9,M3T2=13,M3T3=9,M3T4=8,M3T5=8,M3T
12=12,M3T13=8,M3T14=20,M3T17=10,M3T19=12,M3T22OR20=36,M3T
23OR21=36,M3T1TM=100,M3T2TM=6,TCONN=3,TIAS=96,TIAR=180,TREL
=20,TGUARD=36,TSBS=60,TWCUSER=20,TINT=36,SMLCSPC=<NULL>,AP
LESSNBSC=250,APLESSNSMLC=252,SMLCPERTFLAG=TRUE,M3T10=60;
CREATE SS7L:NAME=SS7L:0,LNKA=0-0,TSLA=0-16,SLC=0,LKSET=0;
CREATE
X25D:NAME=X25D:0,CLOCK=EXTERNAL,BAUDRATE=BAUD_64000,DTEDC
E=DTE,T1=80,T4=200,RETRY=8,L2WIN=7,LCN2WC=1,L3WIN=7,T20=180
0,T21=2000,T22=1800,T23=1800,T26=1800,T28=0,R20=3,R22=3,R23=
3,L3PS=PACKET_2048,TRACE="",N2WC=6;
CREATE OMAL:NAME=OMAL:0,LINKTYPE=X25D,X121ADDR="907001";
CREATE SYNC:NAME=SYNC:0,PCMSOBJ=0;
CREATE
ENVA:NAME=ENVA:0,ENVANAME=FIRE,INTINF=LOW,THR=2,ASEV=CRITICA
L,ASTRING="es brennt";
CREATE
ENVA:NAME=ENVA:1,ENVANAME=SMOKE,INTINF=LOW,THR=2,ASEV=CRITI
CAL,ASTRING="es nebelt";
CREATE
ENVA:NAME=ENVA:2,ENVANAME=TEMPERATURE,INTINF=LOW,THR=2,ASE
V=CRITICAL,ASTRING="es waermt";
CREATE
ENVA:NAME=ENVA:3,ENVANAME=DOOR_OPEN,INTINF=LOW,THR=2,ASEV
=CRITICAL,ASTRING="es zieht";
CREATE TRACE:NAME=TRACE:0,RECCRI=NO_CRITERIA;
142-183
Mr.M.Kaufmann
CREATE CTRSCHED:NAME=CTRCO:0/CTRSCHED:0,CID=770,MACONN=1,START=1-1-1992,STOP=1-12009,PERWEEK=ALL(0),TRACERECTYP=ALL;
CREATE
SCANBSC:NAME=SCANBSC:0,MEASLST=ALLMEAS(0),GRANP=MINUTES_60,
REPMETHD=BYFILE,START=1-1-1995,STOP=31-12-2099,RECINT=ALL(0);
CREATE
SCANBTSE:NAME=SCANBTSE:0,MEASLST=ALLMEAS(0),OBJLST=SELFADAP
TING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTSM:NAME=SCANBTSM:0,MEASLST=BTSEPRLD,OBJLST=SELFADAPT
ING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTSM:NAME=SCANBTSM:1,MEASLST=IFRMABIS,OBJLST=SELFADAPTI
NG(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTS:NAME=SCANBTS:0,MEASLST=ALLMEAS(0),OBJLST=SELFADAPTIN
G(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTSIHO:NAME=SCANBTSIHO:0,MEASLST=ALLMEAS(0),OBJLST=(770)-SELFADAPTING(0)&(77-1)-SELFADAPTING(0)&(77-2)SELFADAPTING(0)&(77-3)SELFADAPTING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTSOHOI:NAME=SCANBTSOHOI:0,MEASLST=ALLMEAS(0),OBJLST=(7
7-0)-SELFADAPTING(0)&(77-1)-SELFADAPTING(0)&(77-2)SELFADAPTING(0)&(77-3)SELFADAPTING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANBTSOHON:NAME=SCANBTSOHON:0,MEASLST=ALLMEAS(0),OBJLST=(
77-0)-SELFADAPTING(0)&(6-0)SELFADAPTING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANTRX:NAME=SCANTRX:0,MEASLST=TRANAVTI,OBJLST=SELFADAPTING
(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
CREATE
SCANTRX:NAME=SCANTRX:1,MEASLST=ILUPLKIC,OBJLST=SELFADAPTING(
0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
143-183
Mr.M.Kaufmann
CREATE SCANCTRX:NAME=SCANCTRX:0,OBJLST=TRXLIST(99-0-0&77-31&66-0-3),START=1-1-1995,STOP=31-12-2099,RECINT=ALL(0),RXLVR=715-23-31-39-47-55,TIMADVR=1-2-3-4-5-6-7,FER=10-20-30-40-50-100200,FERSERTYPE=TCH_FULL;
CREATE SCANCHAN:NAME=SCANCHAN:0,OBJLST=77-0-0-ALLTCH(0)&77-01-ALLTCH(0),START=1-1-1995,STOP=31-12-2099,RECINT=ALL(0);
CREATE
SCANSS7L:NAME=SCANSS7L:0,MEASLST=ALLMEAS(0),OBJLST=SELFADAP
TING(0),GRANP=MINUTES_60,REPMETHD=BYFILE,START=1-11995,STOP=31-12-2099,RECINT=ALL(0);
CREATE
SCANGPRS:NAME=SCANGPRS:0,MEASLST=ALLMEAS(0),OBJLST=SELFADAP
TING(0),GRANP=MINUTES_60,START=1-1-1995,STOP=31-122099,RECINT=ALL(0);
144-183
Mr.M.Kaufmann
Appendix D (command manual)

CREATE ADJC
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSM BTS ADJC CREATE
ADJC
Applicability:
Phase 2.
Visibility level 2.
Command Description:
This command sets the specific parameters for the adjacent cells of a given cell.
Validity ranges of the object addresses "btsmn", btsn and "adjcn" can be found in
Appendix A.
System Responses:
CREATE ADJC: NAME=BTSM:btsmn/BTS:btsn/ADJC:adjcn,TGTCELL=

[,RXLEVMIN=] [,HOM=] [,HOMSOFF=] [,HOMDTIME=]
[,HOMDOFF=] [,MICROCELL=] [,FHORLMO=]
[,TIMERFHO=] [,PLNC=] [,PPLNC=] [,LEVONC=]
[,TINHBAKHO=] [,TINHFAIHO=] [,GSUP=]
[,GTEMPOFF=] [,GPENTIME=] [,GRESOFF=]
[,GHCSTH=] [,GHCSPC=] [,FULHOC=]
[,FULRXLVMOFF=] [,TRFHOM=] [,BHOFOT=]
[,LEVHOM=] [,USG=];
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
UNSUCCESSFUL_SUPERORDINATE_NOTEQUIPPED
The BTS object instance must be already equipped.
The TGTBTS object instance must be already equipped.
If GSUP is TRUE the relative PTPPKF object instance must be
already equipped.
Application Guidelines:
1. No administrative state is associated with this object.
2. The attribute penalityPriorityNcell (PPLNC) must be set to a value not smaller than
the attributepriorityLayerNcell (PLNC).
3. The timer TIMERFHO is running on the adjacent cell serving the Directed Retry
signalling procedure: that is the timer is defined in ADJC A-B for Directed Retry from
A to B.
4. The attribute TINHFAIHO should be set to a value greater than the timer BSCT7
(see BSC object) and timer THORQST (see HAND object).
5. If the GSUP is FALSE the following attributes must not be specified: GTEMPOFF,
GPENTIME, GRESOFF and GHCSPC.
UNSUCCESSFUL_OBJECT_ALREADY_EQUIPPED
The instance of the object must not be already created in order to
perform the command.
UNSUCCESSFUL_INVALID_ATTRIBUTES
145-183
Mr.M.Kaufmann
One or more attributes have been incorrectly set.

MAX_ADJC_COMPL_BAND_EXCEEDED
The number of adjacent cells having their BCCHFREQ in the complementary
band exceeds the allowed maximum number.
For more details, see Application Guideline n. 7.
LAST_ADJC_RESERVED_FOR_LOTRACH
When the intracell handovers are MSC controlled (attribute
LOTRACH of HAND object set at FALSE) one of the 32 allowed
ADJCs is reserved by BSC for LOTRACH handling. So the operator
can configure only 31 ADJC cells.
UNSUCCESSFUL_WRONG_ME_ID
The object address is incorrect.
UNSUCCESSFUL_INVALID_TARGET_CELL
The serving cell and the target cell must be different.
An ADJC with the same serving and target cell already exist.
UNSUCCESSFUL_INVALID_BCCF
The target cell and the serving cell must have different BCCH frequencies.
TOO_MANY_REFERENCES_TO_TARGET_CELL
The maximum number of adjacent cells for the target cell (96) has
been reached.
SUBORDINATE_EQUIPPED
In order to set the GSUP parameter at TRUE value, both the serving
and the target cells must have the relative PTPPKF already equipped.
UNSUCCESSFUL_INVALID_STATUS
The command can be performed only if the SCA object instance
related to the BTS is in LOCKED state
UNSUCCESSFUL_BCCF_OUT_OF_RANGE
The selected value for the BCCH frequency is out of range.
For more details, see the Application Guideline n. 6.
A30808-X3247-K230-2-7619 63
Commands
CML:BSC
6. The BCCHFREQ attribute related to the serving cell SYSID attribute as follows.
Theymust belong either to the same frequency band or to the complementary bands
in the case of dual-band network (GSMDCS, GSMPCS, GSM850PCS).
In the following table, the allowed frequency ranges allowed as complementary
bands for the ADJC BCCHFREQ attribute depending on BSC NETWTYPE and
serving cell SYSID attribute:
7. The maximum number of adjacent cells having their BCCHFREQ in the complementary
band, with respect to the SYSID of the serving cell, depends on the delta
between the lowest and the highest frequency of the ADJCs belonging to this
subset, as shown in the following table:
Example of Command Execution
Create ADJC:NAME=BTSM:0/BTS:0/ADJC:0,TGTCELL=BTS:3,RXLEVMIN=12,
HOM=69,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,
FHORLMO=0,TIMERFHO=4,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=30,
NETWTYPE BTS SYSID Complementary Band
GSMR GSMR --GSMDCS BB900 DCS1800 (512..885)
EXT900 DCS1800 (512..885)
F2ONLY900 DCS1800 (512..885)
DCS1800 F2ONLY900( 0..124, 975..1023)
GSMDCS bcch(0-124) DCS1800 (512..885)
GSMDCS bcch(512-885) BB900 (0..124)
GSMPCS BB900 PCS1900 (512..810)
EXT900 PCS1900512..810
F2ONLY900 PCS1900512..810
146-183
Mr.M.Kaufmann
PCS1900 F2ONLY900(0..124, 975..1023)

GSM850PCS GSM850 PCS1900 (512..810)
PCS1900 GSM850 (128..251)
GSM850PCS bcch(128-251) PCS1900 (512..810)
GSM850PCS bcch(512-810) GSM850 (128..251)
Max Number of ADJC in complementary Band
Delta
16 Any
17 Any, if frequency 0 is present
18 512
22 256
29 128
All 111 or frequency in BB900 band
CML:BSC Commands
TINHFAIHO=7,GSUP=TRUE,GTEMPOFF=1,GPENTIME=0,GRESOFF=0,
GHCSTH=10,GHCSPC=3,FULHOC=TRUE,FULHOM=1,TRFHOM=0,BHOFOT=1,
LEVHOM=0,USG=SI_2_5;
GET ADJC: NAME=BTSM:btsmn/BTS:btsn/ADJC:adjcn

[,REQATTL=TGTCELL, RXLEVMIN, HOM, HOMSOFF,
HOMDTIME, HOMDOFF, MICROCELL, FHORLMO,
TIMERFHO, PLNC, PPLNC, LEVONC, TINHBAKHO,
TINHFAIHO, GSUP, GTEMPOFF, GPENTIME,
GRESOFF, GHCSTH, GHCSPC, FULHOC,
FULRXLVMOFF, TRFHOM, BHOFOT, LEVHOM, USG];
Command Tree:
MANAGED-ELEMENTBSS-FUNCTIONALBTSMBTSADJCGET ADJC
Applicability:
Phase 2.
Visibility level 1.
This command is used to retrieve the values of the parameters, selected by the operator,
related to the adjacent cells of a given cell.
Appendix A.
System Responses:
GET ACK:
TGTCELL: targetCell
RXLEVMIN: rxLevMinCell
HOM: hoMargin
HOMSOFF hoMarginStaticOffset
HOMDTIME: hoMarginDelayTime
HOMDOFF: hoMarginDynamicOffset
MICROCELL: microcell
FHORLMO: fHORxLevMinOffset
TIMERFHO: timerFHO
PLNC: priorityLayerNcel
PPLNC: penalityPriorityLayerNcell
LEVONC: levelOffsetNcell
TINHBAKHO: timerInhibitBackHO
TINHFAIHO: timerInhibitFailHO
GSUP gprsSupported
147-183
Mr.M.Kaufmann
GTEMPOFF: gprsTemporaryOffset
GPENTIME: gprsPenaltyTime
GRESOFF: gprsReselectOffset
GHCSTH: gprsHierarchycalCellStructureThreshold
GHCSPC: gprsHierarchycalCellStructPriorityClass
FULHOC: fastULHoCell
FULRXLVMOFF: fastULRxLevMinOffset
CML:BSC Commands
None.
Get ADJC:NAME=BTSM:0/BTS:0/ADJC:0,REQATTL=TGTCELL&RXLEVMIN&
HOM&HOMSOFF&HOMDTIME&HOMDOFF&MICROCELL&FHORLMO&
TIMERFHO&PLNC&PPLNC&LEVONC&TINHBAKHO&TINHFAIHO&GSUP&
GTEMPOFF&GPENTIME&GRESOFF&GHCSTH&GHCSPC&FULHOC&
FULRXLVMOFF& TRFHOM&BHOFOT&LEVHOM&USG;
TRFHOM: trafficHandoverMargin
BHOFOT: backHoForbiddenTimer
LEVHOM: levelHOMargin
USG: usage
GET NACK:
UNSUCCESSFUL_OBJECT_NOTEQUIPPED
The object instance must be already equipped.
SET ADJC: NAME=BTSM:btsmn/BTS:btsn/ADJC:adjcn [,TGTCELL=]

[,RXLEVMIN=] [,HOM=] [,HOMSOFF=] [,HOMDTIME=]
[,HOMDOFF=] [,MICROCELL=] [,FHORLMO=]
[,TIMERFHO=] [,PLNC=] [,PPLNC=] [,LEVONC=]
[,TINHBAKHO=] [,TINHFAIHO=] [,GSUP=] [,GTEMPOFF=]
[,GPENTIME=] [,GRESOFF=] [,GHCSTH=] [,GHCSPC=]
[,FULHOC=] [,FULRXLVMOFF=] [,TRFHOM=]
[,BHOFOT=] [,LEVHOM=] [,USG=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSM BTS ADJC SET ADJC
Applicability:
Phase 2.
Visibility level 2.
This command modifies the specific parameters for adjacent cells of a given cell.
Appendix A.
System Responses:
SET ACK
Successful
SET NACK
NACK CAUSES:
The BTS object instance must be already equipped.
The TGTBTS object instance must be already equipped.
If GSUP is TRUE the relative PTPPKF object instance must be
already equipped.
148-183
Mr.M.Kaufmann
One or more attributes have been incorrectly set.
MAX_ADJC_COMPL_BAND_EXCEEDED
The number of the adjacent cells having their BCCHFREQ in the
complementary band exceed the allowed maximum number.
For more details, see Application Guidelines n. 8.
LAST_ADJC_RESERVED_FOR_LOTRACH
When the intracell handovers are MSC controlled (attribute
LOTRACH of HAND object set at FALSE) one of the 32 allowed
ADJCs is reserved by BSC for LOTRACH handling, so in this case the
operator can configure at most 31 ADJC cells.
The object address is incorrect.
UNSUCCESSFUL_INVALID_TARGET_CELL
The serving cell and the target cell must be different.
An ADJC with the same serving and target cell already exist.
UNSUCCESSFUL_INVALID_BCCF
The target and serving cell must have different BCCH frequency.
TOO_MANY_REFERENCES_TO_TARGET_CELL
The maximum number of adjacent cells for the target cell (96) has
been reached.
In order to set the GSUP parameter at TRUE value, both the serving
and the target cells must have the relative PTPPKF already equipped.
The command can be performed only if the SCA object instance
related to the BTS is in LOCKED state.
UNSUCCESSFUL_BCCF_OUT_OF_RANGE
The selected value for the BCCH frequency is out of range. For more
details, see the Application Guideline n. 7.
CML:BSC
1. No administrative state is associated with this object.
2. The attribute penalityPriorityNcell (PPLNC) must be set at a value not smaller than
the attributepriorityLayerNcell (PLNC).
3. The timer TIMERFHO is running on the adjacent cell serving the Directed Retry
signalling procedure: that is the timer is defined in ADJC A-B for Directed Retry from
A to B.
4. The attribute TINHFAIHO should be set at a value greater than the timer BSCT7
(see BSC object) and timer THORQST (see HAND object).
5. If the GSUP is FALSE the following attributes must not be specified: GTEMPOFF,
GPENTIME, GRESOFF and GHCSPC.
6. If the related BTS is a GSM (DCS) cell, it is possible to create no more than 16 ADJC
MOs in the DCS (GSM) complementary band.
7. The BCCHFREQ attribute related to the serving cell SYSID attribute as follows.
Theymust belong either to the same frequency band or to the complementary bands
in the case of dual-band network (GSMDCS, GSMPCS, GSM850PCS).
In the following table, the allowed frequency ranges allowed as complementary
bands for the ADJC BCCHFREQ attribute depending on BSC NETWTYPE and
serving cell SYSID attribute:
8. The maximum number of adjacent cells having their BCCHFREQ in the complementary
band with respect to the serving cells SYSID depends on the delta between the
lower and the highest frequency of the ADJC belonging to this subset, as shown in
the following table.
NETWTYPE BTS SYSID Complementary Band
149-183
Mr.M.Kaufmann
GSMR GSMR --GSMDCS BB900 DCS1800 (512..885)

EXT900 DCS1800 (512..885)
F2ONLY900 DCS1800 (512..885)
DCS1800 F2ONLY900( 0..124, 975..1023)
GSMDCS bcch(0-124) DCS1800 (512..885)
GSMDCS bcch(512-885) BB900 (0..124)
GSMPCS BB900 PCS1900 (512..810)
EXT900 PCS1900512..810
F2ONLY900 PCS1900512..810
PCS1900 F2ONLY900(0..124, 975..1023)
GSM850PCS GSM850 PCS1900 (512..810)
PCS1900 GSM850 (128..251)
GSM850PCS bcch(128-251) PCS1900 (512..810)
GSM850PCS bcch(512-810) GSM850 (128..251)
CML:BSC Commands
Set ADJC:NAME=BTSM:0/BTS:0/ADJC:0,TGTCELL=BTS:3,RXLEVMIN=12,
HOM=69,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,MICROCELL=FALSE,
FHORLMO=0,TIMERFHO=4,PLNC=0,PPLNC=0,LEVONC=0,TINHBAKHO=30,
TINHFAIHO=7,GSUP=TRUE,GTEMPOFF=1,GPENTIME=0,GRESOFF=0,
GHCSTH=10,GHCSPC=3,FULHOC=TRUE,FULHOM=1,TRFHOM=0,BHOFOT=1,
LEVHOM=0,USG=SI_2_5;
Max Number of ADJC in
Complementary Band
Delta
16 Any
17 Any, if frequency 0 is present
18 512
22 256
29 128
All 111 or frequency in BB900 band
DELETE ADJC
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSM BTS ADJC DELETE
ADJC
Applicability:
Phase 2.
Visibility level 2.
This command deletes an adjacent cells of a given cell.
Appendix A.
System Responses:
None.
Delete ADJC:NAME=BTSM:0/BTS:0/ADJC:0;
DELETE ADJC: NAME=BTSM:btsmn/BTS:btsn/ADJC:adjcn;
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
150-183
Mr.M.Kaufmann
The command can be performed only if the SCA object
instance related to the BTS is in LOCKED state.
151-183
Mr.M.Kaufmann
CHAN Object
CREATE CHAN: NAME=BTSM:btsmn/BTS:btsn/TRX:trxn/CHAN:chann
,CHTYPE= [,TERTCH=] [,FHSYID=] [,MAIO=] [,TSC=]
[,EXTMODE=] [,GDCH=] [,CHPOOLTYP=];
Command Tree:
MANAGED-ELEMENTBSS-FUNCTIONALBTSM BTS TRX CHAN
CREATE CHAN
Applicability:
Phase 2.
Visibility level 2.
This command defines a Physical Radio Channel by specifying its attributes which allow
to map Logical Channels onto Physical Radio Channel.
Validity ranges of the object addresses btsmn, "btsn", "trxn" and "rtsln" can be found
in Appendix A.
System Responses:
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
The instance of the object must not be already created in order
to perform the command.
UNSUCCESSFUL_SUBORDINATE_EQUIPPED
The TRX which the channel belongs to must be equipped.
FHSY instance pointed by CHAN instance is not equipped.
UNSUCCESSFUL_BROADCAST_CHAN_NOTEQUIPPED
The channel type of the first channel created in the BTS must
be MAINBCCH, MBCCHC or BCBCH.
UNSUCCESSFUL_INVALID_TIME_SLOT
Make reference to Application Guidelines n. 1, n. 20, n. 25, n.
45, n. 47.
UNSUCCESSFUL_INVALID_CHAN_TYPE
Make reference to Application Guidelines n. 2, n. 3, n. 4, n. 6,
n. 12, n. 19, n. 24, n. 25, n. 27, n. 32, n. 33, n. 40, n. 42.
UNSUCCESSFUL_FREQ_OUT_OF_RANGE
If the channel type is SDCCH or SCBCH and the "sysIndicator"
attribute (see BTS object) is EXT900, then the TRX
carrier frequency must belong to the BB900 frequency band.
UNSUCCESSFUL_WRONG_PCMB_NUMBER
Make reference to Application Guideline n. 37.
UNSUCCESSFUL_TIME_SLOT_ZERO_ALLOCATION
The tsln 0 of a pcmb line is used for synchronism.
UNSUCCESSFUL_TIME_SLOT_ALREADY_ALLOCATED
UNSUCCESSFUL_SUB_SLOT_ALREADY_ALLOCATED
One or more attributes have been incorrectly set. For more
152-183
Mr.M.Kaufmann
details see Application Guidelines n. 5, n. 11, n. 28, n. 29, n.

38, n. 44, n. 46.
UNSUCCESSFUL_WRONG_LICD_CARD
UNSUCCESSFUL_NO_MORE_SMSCBCH_ALLOWED
UNSUCCESSFUL_HOPPING_ACTIVE
UNSUCCESSFUL_NO_MORE_FREQ_AVAILABLE
If the FHSYID is equal to 0 frequency hopping must be
disabled (ENHOPP parameter of the BTS object).
UNSUCCESSFUL_INVALID_MAIO
Make reference to Application Guidelines n. 14, n. 15, n. 27,
n. 31.
UNSUCCESSFUL_INVALID_HOPP_GROUP
Make reference to Application Guidelines n. 16, n. 17, n. 27,
n. 31.
UNSUCCESSFUL_OVERLAP_BAND
When the frequency band of the BTS is EXT900 the channel
can use only the Frequency Hopping sequence in the same
band (base or extended) of the superordinate TRX.
HOPPING_NOT_ALLOWED
In case of synthesizer frequency hopping, it is not allowed to
set the FHSYID of the channel subordinated to the broadcast
TRX at a value different from 0.
If the channel is a PBCCH, it cannot be set to hopping mode.
PREVIOUS_CHAN_DOUBLE
The previous timeslot supports a channel in Extended Mode.
HSCSD_HOPP_INCONSISTENT
Make reference to Application Guidelines n. 34 and n. 36.
CML:BSC
1. If the channel type is MAINBCCH, MBCCHC, BCBCH, CCCH, SCBCH or SDCCH
(i.e. control channels) then no time slots must be allocated on the pcmb line. As a
consequence, the terrTraffChannel parameter must be skipped by the operator.
2. If the channel type is MAINBCCH, BCBCH or MBCCHC, then rtsln must be 0.
3. If the channel type is MAINBCCH, BCBCH, MBCCHC or CCCH then the trx the
channel belongs to must be the broadcast one.
4. If the channel type is MBCCHC or BCBCH, then the parameter NBLKACGR
(noOfBlocksForAccessGrant), which indicates the number of TDMA frames
reserved for the Access Grant channel during a period of 51 TDMA frames, must be
lower than 2; the NBLKACGR parameter is set by the SET BTS command and its
default value is "0".
5. If the channel type is MAINBCCH, MBCCHC, BCBCH, CCH, SCBCH or SDCCH,
then the attribute TSC must be equal to the BCC attribute (see BTS object).
6. The channel CCCH cannot be created if the MBCCHC or BCBCH have already been
configured.
The first CCCH channel must be created on rtsln = 2;
the second CCCH channel must be created on rtsln = 4;
the third CCCH channel must be created on rtsln = 6.
7. The tsln and ssln set by the TERTCH (pcmbn-tsln-ssln) parameter must not be
already allocated.
8. After the creation of the CHAN object, the ADMINISTRATIVE state of this object is
set at LOCKED. An UNLOCK command is required to put this object in service.
9. Only BSC with SN16 network and QTLP cards can support TCHF&HLF channel.
10. Only one BCBCH or SCBCH can be created in a BTS.
153-183
Mr.M.Kaufmann
11. If FHSY is either equal to 0 or SKIPPED then MAIO is SKIPPED. If FHSY>0 then
MAIO is NOT SKIPPED.
12. If the channel type is MAINBCCH, MBCCHC, BCBCH, CCCH then the FHSYID
must be equal to 0.
13. The number of channels, with the same time slot number, pointing to the same
FHSY instance can not be greater than the number of frequencies in the mobile allocation
of the frequency hopping law.
14. CHAN instances, with the same time slot number, pointing to the same FHSY
instance must have different values for MAIO attribute.
HSCSD_TSC_INCONSISTENT
GPRS_TSC_INCONSISTENT
All the traffic channels subordinate to a TRX with GSUP set at
TRUE must have the same TSC.
GPRS_HOPP_INCONSISTENT
If the TRX has the GSUP set at TRUE single TCHs must have
the same FHSYID and MAIO, and if one or more CCCHs have
already been equipped the channels cannot hop (i.e. FHSYD
attribute must be 0).
INVALID_COMMAND
Only one PBCCH can be allocated.
A PBCCH can be allocated only if the PBCCH is already
equipped.
15. The value for MAIO attribute must be less than the number of frequencies in the
mobile allocation of the FHSY instance used.
16. CHAN instances, with the same time slot number, can not point to different FHSY
instances if the two FHSY instances use the same frequencies.
17. It is not possible to have one CHAN instance with FHSYID=0 and another CHAN
instance, with the same time slot number, pointing to a FHSY instance, if the carrier
frequency of superordinate TRX of the first channel is included in the mobile
allocation of FHSY instance pointed by the second.
18. The SCBCH channel can be equipped only on time slots 1, 2, 3 of the BCCH-TRX.
19. If the channel type is SCBCH then the parameter NBLKACGR (noOfBlocksForAccessGrant
attribute, set by the SET BTS command) must not be equal to 0.
20. When the frequency band of the BTS is EXT900 the channel can use only the
Frequency Hopping sequence in the same band (base or extended) of the
superordinate TRX.
21. The creation of a CHAN causes a temporary loss of service for the whole TRX
because of a reset of the associated BBSIG. It is suggested to shutdown the TRX
before creating one or more channels to avoid that calls are dropped.
22. Creation of TCHF&HLF channels must be compatible with the type of hardware
used for TRAU equipment. Only TRAC V3 boards can handle half rate channels
coding-decoding feature.
23. The tsln set by the TERTCH (pcmbn-tsln-ssln) parameter is not compatible with the
PCM line type attribute (parameter PCMTYPE of BSC object).
24. No more than other three channels containing SDCCH subchannels (i.e. MAINBCCHCOMBINED,
BCBCH, SCBCH, SDCCH) must belong to the same transceiver.
25. If any channel containing SDCCH subchannels is equipped on a BTS, then at least
one of them must be on the BCCH-TRX.
26. In case of concentric cell the SDCCH channels cannot be created on TRXs with
trxArea parameter set at INNER.
27. In case of concentric cell and base band hopping selected, the attribute FHSYID of
a channel subordinated of a INNER TRX cannot be set with the frequency hopping
system that use frequencies of complete area (and viceversa).
28. If cellType attribute values EXTCELL all the control and signalling channels must
have EXTMODE=TRUE.
If cellType attribute is different from EXTCELL the EXTMODE attribute cannot be set
154-183
Mr.M.Kaufmann
at TRUE.
29. The radio timeslot number (rtsln) of an extended channel must be an even one.
30. The timeslot following an extended channel must be not equipped.
31. The extended channels use two consecutive timeslots: therefore, in case of
extended cell, all the previous Application Guidelines regarding frequency hopping
consistency apply also to the timeslot following the channel timeslot.
32. The creation of a SCBCH on a TRX different from BCCH-TRX is allowed only if the
CELLTYPE attribute of the BTS object is set at EXTCELL and at least one CCCH
and one SDCCH have already been configured.
33. It is not allowed to configure the third CCH channel if the CELLTYPE attribute of the
BTS object is set at EXTCELL.
34. If the HSCSD service is activated at BTS side (i.e. attribute BTSHSCSD of BTS
object set at TRUE) the following requirements must be satisfied:
CML:BSC
In the following tables wrong (first table) and right (second table) creation examples
are shown (for each channel the FHSY is specified).
The problem occurs on timeslots 2 of TRX:1 and TRX:2 where the application
guideline on multislot allocation (point 1 above) is not satisfied as a consequence of
the choice on timeslot 2 of TRX:0. The right settings are the following:
35. If the HSCSD service is activated at BTS side (i.e. attribute BTSHSCSD of BTS
object set at TRUE) the following TSC requirements must be satisfied:
36. In a cell with Base Band Hopping Mode, if the HSCSD service is activated at BTS
side (attribute BTSHSCSD of BTS object set at TRUE), the first CCCH channel
cannot be created if the MOBALLOC attribute of some FHSY object instances
contains the BCCH frequency and if some channels equipped in the BCCH-TRX is
hopping (i.e. FHSYID is different from 0).
37. The field pcmb_number of the attribute TERTCH must be equal either to the
pcmbNumber0 field of the PCMCON0 attribute or to the pcmbNumber1 field of the
PCMCON1 attribute of the related BTSM object.
The field pcmb_number of the attribute TERTCH must be equal to that of any other
traffic channel already present on the same TRX.
38. Compatibility between CHTYPE and ASCISER: if ASCISER is equal to VBSENABLED
or VGCSENABLED or VBS_VGCSENABLED:
1. Case Base Band Hopping Mode: on a given TRX, single TCHs, on timeslot
from 1 to 7 must have the same FHSYID and MAIO and if one or more
CCCHs have already been equipped, channels on the BCCH-TRX can not
hop (i.e. FHSYID attribute must be 0).
2. Case Synthesizer Hopping Mode: on a given TRX different from the BCCH
one, all single TCHs must have the same FHSYID and MAIO.
TRX:0 TRX:1 TRX:2
0 BCCH TCH(0) TCH(0)
1 TCH(1) TCH(1) TCH(1)
2 SDCCH(2) TCH(2 or 3) TCH(2 or 3)
TRX:0 TRX:1 TRX:2
0 BCCH TCH(0) TCH(0)
2 SDCCH(2) SDCCH(2) SDCCH(2)
1. Case Base Band Hopping Mode: on a given TRX, single TCHs on timeslot
from 1 to 7 must have the same TSC.
2. Case Synthesizer Hopping Mode: on a given TRX all single TCHs must
have the same TSC.
CML:BSC Commands
155-183
Mr.M.Kaufmann
39. A TCH channel type can be created if at least one of the following conditions is satisfied:
a SDCCH channel type already exists;
a channel type containing a SDCCH (e.g. a MBCCHC, BCBCH or SCBCH)
already exists.
40. The PBCCH and PCCCH channels must be created on the BCCH-TRX only.
The PBCCH and PCCCH configuration is allowed only for TCHFULL and
TCHFULLANDHALF channels.
41. All channels on BCCH-TRX must have the same TSC (Training Sequence Code) for
every GPRS activation status (activated or not).
42. If the channel is a PBCCH or a PCCCH than the EXTMODE parameter cannot be
set at TRUE.
43. TERTCH attribute is an optional one, but, if selected, all its subfields (pcmbn, tsln
and ssln) become mandatory.
44. At the creation of a GPRS channel (PBCCH, PCCCH, RPDTCH) the GSUP flag of
the related TRX should be already set at TRUE.
On BCCH TRX the operator can create no more than 5 GPRS channels.
45. The RPDTCH channels must be created as adjacent each other.
46. If the flag EEOTD (BTS object) is enabled, TSC must be equal to BS Colour
Code(bcc).
47. No RPDTCH can be equipped on timeslot 0 in case of base band hopping.
Create CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:0,CHTYPE=TCHFULL,
TERTCH=0-2-0,FHSYID=0,MAIO=0,TSC=2,EXTMODE=FALSE,
GDCH=GPRSPBCCH,CHPOOLTYP=TCHSDPOOL;
NOCHFBLK NOCHBLKN CHTYPE
1..4 1..4
5 1..3 MAINBCCH
6 1..2
71
1..3 1 MBCCHC or BCBCH
GET CHAN: NAME=BTSM:btsmn/BTS:btsn/TRX:trxn/CHAN:rtsln

[,REQATTL=CHTYPE, TERTCH, FHSYID, MAIO, TSC,
EXTMODE, GDCH, CHPOOLTYP];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSM BTS TRX CHAN
GET CHAN
Applicability:
Phase 2.
Visibility level 0.
This command is used to retrieve the parameter values of a CHAN previously created
through the CREATE CHAN command.
in Appendix A.
System Responses:
None.
GET ACK:
156-183
Mr.M.Kaufmann
NAME: name
CHTYPE: channelCombination
TERTCH: TerrestrialTrafficChannel
Pcmb Number: pcmb number first subchannel
TSL1: Timeslot Number (timeslot number first subchannel)
SSL1: Subslot Number (subslot number first subchannel)
FHSYID: frequencyHoppingID
MAIO: maio
TSC: trainingSequenceCode
EXTMODE: extendedMode
GDCH: gprsDedicatedChannel
CHPOOLTYP: channelPoolType
GET NACK:
NACK CAUSES:
Commands
CML:BSC
Get CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:0,REQATTL=CHTYPE&TERTCH&
FHSYID&MAIO&TSC&EXTMODE&GDCH&CHPOOLTYP;
DELETE CHAN: NAME=BTSM:btsmn/BTS:btsn/TRX:trxn/CHAN:rtsln;
Command Tree:
DELETE CHAN
Applicability:
Phase 2.
Visibility level 2.
CML:BSC
This command deletes a Radio Channel previously created through the CREATE CHAN
command.
in Appendix A.
System Responses:
1. If rtsln=2 and the channel type is CCCH, then it is first necessary to delete the other
CCCH in the TRX;
if rtsln=4 and the channel type is CCCH then it is first necessary to delete the CCCH
on rtsln=6 of the same TRX.
2. The deletion of a CHAN causes a temporary loss of service for the whole TRX
because of a reset of the associated BBSIG. It is suggested to shutdown the TRX
before deleting one or more channels to avoid that calls are dropped.
3. The last channel including some SDCCH subchannels equipped on the BCCH-TRX
cannot be deleted if any other SDCCH is equipped on a different TRX on the same
BTS.
4. The last extended or not extended TCH channel cannot be deleted if the intracell
handover for extended cell (attribute EXTCHO of HAND object) is enabled.
5. The broadcast channel cannot be deleted if there are other channels equipped in
157-183
Mr.M.Kaufmann
the BTS.
6. It is not possible to delete a CCCH channel in an EXTENDED cell with SCBCH
channel equipped.
7. The last SDCCH cannot be deleted if there are traffic channels equipped in the cell.
8. A PBCCH cannot be deleted if some PCCCHs are allocated.
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
Before deleting a CHAN, the relative object instance must be
in LOCKED state.
INVALID_COMMAND
Make reference to Application Guidelines n. 1, n. 3, n. 4, n. 5,
n. 6, n. 7, n. 8.
UNSUCCESSFUL_SMSCB_USED
The SCBCH and BCBCH channels can be deleted only if the
SMSCBUSE parameter is set at FALSE (SMSCBUSE parameter
of the BTS object).
The last hopping channel can be deleted only if hopping is
disabled (ENHOPP parameter of the BTS object set at
FALSE).
CML:BSC Commands
Delete CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:0;
SET CHAN: NAME=BTSM:btsmn/BTS:btsn/TRX:trxn/CHAN:chann

[,FHSYID=] [,MAIO=] [,TSC=] [,GDCH=]
[,CHPOOLTYP=];
Command Tree:
SET CHAN
Applicability:
Phase 2.
Visibility level 2.
This command modifies the attributes of a Physical Radio Channel previously created
through the CREATE CHAN command.
in Appendix A.
System Responses:
SET ACK:
Successful
SET NACK:
NACK CAUSES:
158-183
Mr.M.Kaufmann

One or more attributes have been incorrectly set. For more details
see Application Guidelines n. 1, n. 2, n. 3, n. 15.
The FHSY object instance must be already equipped.
The attributes FHSYID and MAIO can be modified only if the
Frequency Hopping is disabled (ENHOPP parameter of the BTS
object must be FALSE).
UNSUCCESSFUL_NO_MORE_FREQ_AVAILABLE
The number of channels, with the same time slot number, pointing
to the same FHSY instance can not be greater than the number of
frequencies in the mobile allocation of the frequency hopping law.
UNSUCCESSFUL_INVALID_HOPP_GROUP
Make reference to Application Guidelines n. 4, n. 5, n. 8, n. 9.
Make reference to Application Guidelines n. 6 and n. 7.
UNSUCCESSFUL_OVERLAP_BAND
When the frequency band of the BTS is EXT900 the channel can
use only the Frequency Hopping sequence in the same band (base
or extended) of the superordinate TRX.
HOPPING_NOT_ALLOWED
In case of synthesizer frequency hopping, it is not allowed to set the
FHSYID of the channel subordinated to the broadcast TRX at a
value different from 0.
If the channel is a PBCCH, it cannot be set to hopping mode.
HSCSD_HOPP_INCONSISTENT
HSCSD_TSC_INCONSISTENT
UNSUCCESSFUL_INVALID_CHAN_TYPE
Make reference to Application Guidelines n. 12, n. 13.
GPRS_TSC_INCONSISTENT
All channels on BCCH-TRX must have the same TSC (Training
Sequence Code) for every GPRS activation status (activated or
not).
GPRS_HOPP_INCONSISTENT
If the TRX has the GSUP set at TRUE single TCHs must have the
same FHSYD and MAIO and if one or more CCCHs have already
been equipped, the channels cannot hop (i.e. FHSYD attribute
must be 0).
CML:BSC
1. If the channel type is MAINBCCH, MBCCHC, BCBCH, CCCH, SCBCH or SDCCH
(i.e. control channels) then the attribute TSCmust be equal to the BCC attribute (see
CREATE BTS).
2. The final value for FHSYID and MAIO must belong to one of the following cases:
FHSYID=0 MAIO=0
FHSYID>0 MAIO=0-63.
3. If the channel type is MAINBCCH, MBCCHC, BCBCH or CCCH, the FHSYID must
be equal to 0.
4. CHAN instances, with the same time slot number, pointing to the same FHSY
instance must have different values for MAIO attribute.
5. The value for MAIO attribute must be less than the number of frequencies in the
mobile allocation of the FHSY instance used.
159-183
Mr.M.Kaufmann
6. To modify the TSC attribute the CHAN must be put in the locked state.
7. The FHSYID attribute can be modified from 0 to different from 0 value only if the
channel is locked.
The FHSYID attribute can be modified from different from 0 value to different from
0 value only if the two frequency hopping systems have the same HSN, otherwise
the channel must be put in locked state.
8. In case of concentric cell and base band hopping selected, the attribute FHSYID of
a channel subordinated of a INNER TRX cannot be set with the frequency hopping
system that use frequencies of complete area (and viceversa).
9. The extended channels use two consecutive timeslots: therefore, in case of
extended cell, all the previous Application Guidelines regarding frequency hopping
apply also to the timeslot following the channel timeslot.
10. If the HSCSD service is activated at BTS side (i.e. attribute BTSHSCSD of BTS set
as TRUE) the following requirements must be satisfied:
11. If the HSCSD service is activated at BTS side (i.e. attribute BTSHSCSD of BTS set
as TRUE) the following TSC requirements must be satisfied:
INVALID_COMMAND
Only one PBCCH can be allocated.
A PBCCH can be allocated only if the PBCCH is already equipped.
The RPDTCH channels must be created as adjacent each other.
No RPDTCH can be equipped on timeslot 0 in case of base band
hopping.
1. Case Base Band Hopping Mode: on a given TRX, single TCHs, on timeslot
from 1 to 7 must have the same FHSYID and MAIO and if one or more
CCCH have already been equipped, channels on the BCCH-TRX cannot
hop (i.e. FHSYID attribute must be 0).
2. Case Synthesizer Hopping Mode: on a given TRX different from the BCCH
one, all single TCHs must have the same FHSYID and MAIO.
1. Case Base Band Hopping Mode: on a given TRX, single TCHs on timeslot
from 1 to 7 must have the same TSC.
2. Case Synthesizer Hopping Mode: on a given TRX all single TCHs must
have the same TSC.
CML:BSC Commands
12. The PBCCH and PCCCH channels must be created on the BCCH-TRX only.
The PBCCH and PCCCH configuration is allowed only for TCHFULL and
TCHFULLANDHALF channels.
13. If the channel is a PBCCH or a PCCCH the EXTMODE parameter cannot be set at
TRUE value.
14. If the flag EEOTD (BTS object) is enabled, TSC must be equal to BS Colour
Code(bcc).
15. If the GDCH attribute is set at a value different from NULL (PBCCH, PCCCH,
RPDTCH) the GSUP flag of the related TRX should be already set at TRUE.
On BCCH-TRX the operator can create no more than 5 GPRS channels.
Set CHAN:NAME=BTSM:0/BTS:0/TRX:0/CHAN:0,FHSYID=<DEFAULT>,
MAIO=<DEFAULT>,TSC=2,GDCH=PBCCH,CHPOOLTYP=TCHSDPOOL;
FRL object (New)

The FRL functional object represents the physical link connection on Gb interface. The
connection can be realised via A interface (PCMA) or directly to SGSN via PCMG.
In case of A interface connection the 64 kbit/s time slot are reserved on PCMS and
handled in TRAU as transparent channel.
160-183
Mr.M.Kaufmann
CREATE FRL: NAME=FRL:frln ,PCUN= ,GLK= ,GTS= [,T391=]

[,N391=]
[,N392=] [,N393=] [,TCONG=] [,TCONOFF=] [,FRSTD=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL FRLCREATE FRL
Applicability:
Phase 2.
Visibility level 2.
This command creates an instance of the FRL object class. It can be done only if the
PCU and PCMA/PCMG are created. Creation of FRL link means to make a semi-permanent
network connection between the time slot on PCMA or PCMG and the corresponding
time slot on internal 2 Mbit/s. The availability of time slot on internal 2 Mbit/s
must be checked using data assigned in PCU object and the space already allocated to
other FRL links.
The status at creation will be Locked-Disabled/Offline. When the BSC have been
aligned with the remote peer the FRL object will be put in Enabled state.
The validity range of the object address "frln" can be found in Appendix A.
System Responses:
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
OBJECT_ALREADY_EQUIPPED
SUPERORDINATE_NOTEQUIPPED
The relevant PCU and PCMA/PCMG object instances must be
already equipped.
The timeslot inserted in the CREATE FRL command must be not
allocated by other links.
CML:BSC Commands
None.
Create FRL:NAME=FRL:3,PCUN=0,GLK=PCMG:0,GTS=2&12,T391=10,N391=50,
N392=34,N393=10,TCONG=20,TCONOFF=25,FRSTD=ITU;
The FRL can be connected only to a PCMA or a PCMG.
The operator cannot specify twice the same timeslot in the timeslot
list.
UNSUCCESSFUL_VAR_OUT_OF_RANGE
The attribute TCONOFF can assume one of the following values: 0,
10..30.
Before deleting a FRL, the relative TRAU object instance must be in
LOCKED state.
161-183
Mr.M.Kaufmann
The number of timeslots assigned to the FRL must be compatible

with the PCMTYPE attribute of the BSC object.
UNSUCCESSFUL_NOT_ENOUGH_INT_TSL
There must be enough free internal timeslots in order to submit the
command.
UNSUCCESSFUL_EXCEED_OBJECT_NBR
FRL instances greater than 31 or more than 16 FRLs per PCU are
allowed only with SNAP network card.
i The value of the timer T391 set on the BSC side must be lower than
the value of the timer T392 set either on the SGSN or the network side
of the Frame Relay link.
GET FRL: NAME=FRL:frln [,REQATTL=PCUN, GLK, GTS, T391, N391,

N392, N393, TCONG, TCONOFF, FRSTD];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL FRL GET FRL
Applicability:
Phase 2.
Visibility level 0.
This command is used to retrieve the parameter values of an instance of the FRL object
class.
System Responses:
GET ACK:
NAME: name
PCUN pcuNumber
CML:BSC Commands
None.
Get FRL:NAME=FRL:0,REQATTL=PCUN&GLK&GTS&T391&N391&N392&N393&
TCONG&TCONOFF&FRSTD;
GLK gprsLink
GTS gprsTimeslot
T391 timer391
N391 n391
N392 n392
N393 n393
TCONG timeCongestion
TCONOFF timeCongestionOff
FRSTD frameRelayStandard
GET NACK:
NACK CAUSES:
DELETE FRL: NAME=FRL:frln;
162-183
Mr.M.Kaufmann
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL FRL DELETE FRL
Applicability:
Phase 2.
Visibility level 2.
This command deletes a previously created instance of the FRL object class. It can be
done only if all NSVC, attached to considered FRL, are deleted and the deletion implies
the removing of the semi-permanent network connection. The object to be deleted, shall
Commands
CML:BSC
be previously locked.
System Responses:
None.
Delete FRL:NAME=FRL:3;
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
Before deleting a FRL, the relative object instance must be in
LOCKED state.
Before deleting a FRL, the relative TRAU object instance must be in
LOCKED state (if the FRL is attested on PCMA).
All the NSVC object instances associated to the FRL object instancemust
be previously deleted.
SET FRL: NAME=FRL:frln [,GTS=] [,T391=] [,N391=] [,N392=]

[,N393=]
[,TCONG=] [,TCONOFF=] [,FRSTD=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL FRL SET FRL
Applicability:
Phase 2.
Visibility level 2.
This command modifies the specific parameters of the FRL object class. It is used to
assign different time slot to a specific FRL link. The change could be
increasing/decreasing the number of time slots or changing the time slot number. For all
these actions the consequent semi-permanent connection shall be changed. The
command must be done in Locked state in order to inform the remote end ot the new
163-183
Mr.M.Kaufmann
link configuration. Also T391, N391, N392 and N393 can be changed with set command.
No lock procedure is foreseen for changing this attribute.
Commands
CML:BSC
System Responses:
None.
Set FRL:NAME=FRL:3,GTS=2&12,T391=10,N391=50,N392=34,N393=10,
TCONG=20,TCONOFF=25,FRSTD=ITU;
SET FRL ACK:
Successful
SET FRL NACK:
NACK CAUSES:
When the GTS attribute is changed the FRL and the
relative TRAU must be in LOCKED state.
The FRSTD parameter can be set only if the FRL
object is in LOCKED state.
The timeslot inserted in the SET FRL command must
not be allocated by other links.
The number of timeslots assigned to the FRL must be
compatible with the PCMTYPE attribute of the BSC
object.
UNSUCCESSFUL_NOT_ENOUGH_INT_TSL
There must be enough free internal timeslots in order
to submit the command.
i The value of the timer T391 set on the BSC side must be lower than
the value of the timer T392 set either on the SGSN or the network side
of the Frame Relay link.
NSVC object (New)

The NSVC (Network Service Virtual Container) functional object represents the end-toend
communication between BSS and SGSN. At each side of Gb interface, there is one
to one correspondence between NSVC and NSVL then the NSVL can be seen as an
attribute of NSVC.
CREATE NSVC: NAME=NSVC:nsvcn,NSVCI=,NSVLI=;
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL NSVCCREATE NSVC
Applicability:
Phase 2.
Visibility level 2.
164-183
Mr.M.Kaufmann
This command creates an instance of the NSVC object class. It can be done only if FRL
is created. The status at creation will be Locked Disabled/Offline.
When the GbIC have been aligned with the remote peer the NSVC object will be put in
Enabled state.
The validity range of the object address "nsvcn" can be found in Appendix A.
System Responses:
None.
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
The FRL object instance must be already equipped.
The maximum number of NSVCs relative to a PCU that can be
created is 16.
NSVC instances numbers greater than 31 or more than 16 FRLs per
PCU are allowed only with SNAP network card.
INVALID_ATTRIBUTE_VALUE
Different NSVCs of the same PCU cannot have the same NSVCI or
the same NSVLI.
CML:BSC Commands
Create NSVC:NAME=NSVC:10,NSVCI=3,NSVLI=20-50;
GET NSVC: NAME=NSVC:nsvcn [,REQATTL=NSVCI, NSVLI];

Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL NSVCGET NSVC
Applicability:
Phase 2.
Visibility level 1.
This command is used to retrieve the parameter values of an instance of the NSVC
object class.
System Responses:
None.
Get NSVC:NAME=NSVC:0,REQATTL=NSVCI&NSVLI;
GET ACK:
NAME: name
NSVCI: Network Service Virtual Connection Identifier
NSVLI: Network Service Virtual Link Identifier
165-183
Mr.M.Kaufmann
GET NACK:
NACK CAUSES:
DELETE NSVC: NAME=NSVC:nsvcn;
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL NSVCDELETE NSVC
Applicability:
Phase 2.
Visibility level 2.
This command deletes a previously created instance of the NSVC object class. It can
be done only if the NSVC is in locked state.
System Responses:
None.
Delete NSVC:NAME=NSVC:10;
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
Before deleting a NSVC, the relative object instance must be in
LOCKED state.
The last NSVC can be deleted only if there are no PTPPKFs
equipped.
PCMG object
The PCMG functional object represents the direct physical connection between BSC
and SGSN. This line carries 32 time slot of 64 kbit/s that can handle maximum of 31 FRL
and it can be connected to a single circuit of LICD.
The PCMG cannot be redounded. Therefore, unlikely than the PCMB and PCMS, it
does not have the parameter LREDUNEQ. If ASUBENCAP (BSC parameter) is TRUE,
then it is possible to create another PCMG or PCMS in the unused trunk (A or B) of the
same PCML of the PCMG. Instead if ASUBENCAP is FALSE, the PCMG takes busy
both trunks A and B of the PCML.
CREATE PCMG: NAME=PCMG:pcmgn, PCML= [,CRC=] [,BER=]

[,LOWBER=] [,CODE=] [,NUA=] [,BAF=] [,REMAL=];
Command Tree:
166-183
Mr.M.Kaufmann
MANAGED-ELEMENT BSS-FUNCTIONAL PCMG CREATE PCMG

Applicability:
Phase 2.
Visibility level 2.
This command creates an instance of the PCMG object class. It can be done only if the
LICD is created. Creation of PCMG line means to associate a specific LICD port to a Gb
interface connection.
The validity range of the object address "pcmgn" can be found in Appendix A.
System Responses:
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
The LICD object instances must be already equipped.
UNSUCCESSFUL_LINK_CONNECTED
The TRUNK of the LICD card corresponding to the referenced line
must not be already connected to a PCM line.
Commands
CML:BSC
After the creation of the object the ADMINISTRATIVE state of this object is set at
LOCKED. An UNLOCK command is required to put this object in service.
For PCM30:
Create PCMG:NAME=PCMG:0,PCML=0-0-A,CRC=FALSE,CODE=HDB3,
NUA=FALSE,BER=0,BAF=0;
For PCM24:
Create PCMG:NAME=PCMG:3,PCML=1-2-A,CRC=FALSE,CODE=HDB3,
NUA=FALSE,BER=0,BAF=0,LOWBER=0,REMAL=CCITT;
The attributes REMAL can be set only with the PCM24 lines
(parameter PCMTYPE of BSC object).
The value assigned to LOWBER attribute must be greater or equal
to the BER one. This means that the bit error rate for LOWBER is
lower or equal than the BER one. For example: LOWBER = 3 (106 bit error rate) BER = 2 (10-5 bit error rate).
The attributes CODE, NUA and BAF can be set only with the
PCM30 lines (parameter "Pcm Type" of BSC object).
GET PCMG: NAME=PCMG:pcmgn [,REQATTL= PCML, CRC, CODE,

NUA, BER, BAF, LOWBER, REMAL];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCMG GET PCMG
Applicability:
Phase 2.
Visibility level 1.
167-183
Mr.M.Kaufmann
This command is used to retrieve the parameter values of an instance of the PCMG
object class.
System Responses:
GET ACK:
NAME: name
PCML: pcmLine
CRC: crc
CODE: code
NUA: NotUrgentAlarms
BER: BitErrorRate
BAF: baf
LOWBER: lowerBitErrorRate
REMAL: remoteAlarmType
GET NACK:
NACK CAUSES:
Commands
CML:BSC
None.
Get PCMG:NAME=PCMG:0,REQATTL=PCML&CRC&CODE&NUA&BER&BAF&
LOWBER&REMAL;
DELETE PCMG: NAME=PCMG:pcmgn;
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCMG DELETE PCMG
Applicability:
Phase 2.
Visibility level 2.
This command deletes a previously created instance of the PCMG object class. It can
be done only if all FRL attached to considered PCMG are deleted.
System Responses:
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
OBJECT_NOTEQUIPPED
CML:BSC Commands
None.
Delete PCMG:NAME=PCMG:0;
168-183
Mr.M.Kaufmann
Before deleting a PCMG, the relative object instance must be in

LOCKED state.
All FRLs attached to this PCMG must be deleted and all the
timeslotS related to the PCMG must be free.
SET PCMG: NAME=PCMG:pcmgn [,CRC=] [,BER=] [,LOWBER=]

[,CODE=] [,NUA=] [,BAF=] [,REMAL=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCMG SET PCMG
CML:BSC Commands
Applicability:
Phase 2.
Visibility level 2.
This command modifies the specific parameters of the PCMG object class.
System Responses:
None.
For PCM30:
Set PCMG:NAME=PCMG:0,CRC=FALSE,CODE=HDB3,NUA=FALSE,BER=0,
BAF=0;
For PCM24:
Set PCMG:NAME=PCMG:3,CRC=FALSE,CODE=HDB3,NUA=FALSE,BER=0,
BAF=0,LOWBER=0,REMAL=CCITT;
SET ACK:
Successful
SET NACK:
NACK CAUSES:
OBJECT_NOTEQUIPPED
When the attributes CODE, BAF and CRC are changed the
PCMG must be in LOCKED state.
The attribute REMAL can be set only with the PCM24 lines
(parameter PCMTYPE of BSC object).
The attributes CODE, NUA and BAF can be set only with the
PCM30 lines (parameter PCMTYPE of BSC object).
The value assigned to LOWBER attribute must be greater or
equal to the BER one.
169-183
Mr.M.Kaufmann
PCU object
GET PCU: NAME=PCU:pcun [,REQATTL=NMO, NSEI, TNSVCBLK,
NNSVCBLKR, NNSVCUBLR, TNSVCR, NNSVCRR,
TNSVCTST, TNSVCPTST, NNSVCTSTR, NBVCBR,
NBVCUR, NBVCRR, T1, T2, TF1, N3101, N3103, N3105,
NRLCMAX, T3141, T3169, T3172, T3191, T3193, T3195,
TEMPCH, THPROXT, TIMEDTBFREL];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCU GET PCU
Applicability:
Phase 2.
Visibility level 1.
This command is used to retrieve the parameter values of an instance of the PCU object
class.
The validity range of the object address "pcun" can be found in Appendix A.
System Responses:
GET ACK:
NAME: name
NMO: networkModeOf Operation
NSEI: NetworkServiceElementIdentifier
TNSVCBLK: timerInNsvcBlockProcedure
Commands
CML:BSC
None.
Get PCU:NAME=PCU:0,REQATTL=NMO&NSEI&TNSVCBLK&NNSVCBLKR&
NNSVCUBLR&TNSVCR&NNSVCRR&TNSVCTST&TNSVCPTST&NNSVCTSTR&
NBVCBR&NBVCUR&NBVCRR&T1&T2&TF1&N3101&N3103&N3105&NRLCMAX&
T3141&T3169&T3172&T3191&T3193&T3195&TEMPCH&THPROXT&
TIMEDTBFREL;
NNSVCBLKR: numberOfNsvcBlockRetries
NNSVCUBLR: numberOfNsvcUnblockRetries
TNSVCR: timerNsvcReset
NNSVCRR: numberOfNsvcResetRetries
TNSVCTST: timerInNsvcTestProcedure
TNSVCPTST: timerNsvcPeriodicTestProcedure
NNSVCTSTR: NumberOfNsvcTestRetries
NBVCBR: NumberOfBvcBlockRetries
NBVCUR: NumberOfBvcUnblockRetries
NBVCRR: NumberOfBvcResetRetries
T1: t1
T2: t2
TF1: tf1
N3101: n3101
170-183
Mr.M.Kaufmann
N3103: n3103
N3105 n3105
NRLCMAX numberRlcMax
T3141 t3141
T3169: t3169
T3172: t3172
T3191: t3191
T3193: t3193
T3195: t3195
TEMPCH: TimerEmptyChannel
THPROXT: thresholdProximityTimer
TIMEDTBFREL: timeDelayTBFRelease
GET NACK:
NACK CAUSES:
None.
TIMEDTBFREL;
GET PCU: NAME=PCU:pcun [,REQATTL=NMO, NSEI, TNSVCBLK,

NNSVCBLKR, NNSVCUBLR, TNSVCR, NNSVCRR,
TNSVCTST, TNSVCPTST, NNSVCTSTR, NBVCBR,
NBVCUR, NBVCRR, T1, T2, TF1, N3101, N3103, N3105,
NRLCMAX, T3141, T3169, T3172, T3191, T3193, T3195,
TEMPCH, THPROXT, TIMEDTBFREL];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCU GET PCU
Applicability:
Phase 2.
Visibility level 1.
This command is used to retrieve the parameter values of an instance of the PCU object
class.
System Responses:
GET ACK:
NAME: name
NMO: networkModeOf Operation
NSEI: NetworkServiceElementIdentifier
TNSVCBLK: timerInNsvcBlockProcedure
Commands
CML:BSC
171-183
Mr.M.Kaufmann
None.
TIMEDTBFREL;
NNSVCBLKR: numberOfNsvcBlockRetries
NNSVCUBLR: numberOfNsvcUnblockRetries
TNSVCR: timerNsvcReset
NNSVCRR: numberOfNsvcResetRetries
TNSVCTST: timerInNsvcTestProcedure
TNSVCPTST: timerNsvcPeriodicTestProcedure
NNSVCTSTR: NumberOfNsvcTestRetries
NBVCBR: NumberOfBvcBlockRetries
NBVCUR: NumberOfBvcUnblockRetries
NBVCRR: NumberOfBvcResetRetries
T1: t1
T2: t2
TF1: tf1
N3101: n3101
N3103: n3103
N3105 n3105
NRLCMAX numberRlcMax
T3141 t3141
T3169: t3169
T3172: t3172
T3191: t3191
T3193: t3193
T3195: t3195
TEMPCH: TimerEmptyChannel
THPROXT: thresholdProximityTimer
TIMEDTBFREL: timeDelayTBFRelease
GET NACK:
NACK CAUSES:
DELETE PCU: NAME=PCU:pcun;
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCU DELETE PCU
Applicability:
Phase 2.
Visibility level 2.
This command deletes a previously created instance of the PCU object class. The
PPCU/PPXU cards related to this PCU functionality will be implicitly deleted by the
system.
CML:BSC Commands
System Responses:
172-183
Mr.M.Kaufmann
None.
Delete PCU:NAME=PCU:0;
DELETE ACK:
Successful
DELETE NACK:
NACK CAUSES:
OBJECT_NOTEQUIPPED
All the FRL object instances associated to the PCU object instance
must be previously deleted.
If the PCU object instance is the last equipped in the BSC all
PTPPKF object instances must be deleted.
Delete PCU:NAME=PCU:0;
SET PCU: NAME=PCU:pcun [,NMO=] [,NSEI=] [,TNSVCBLK=]

[,NNSVCBLKR=] [,NNSVCUBLR=] [,TNSVCR=]
[,NNSVCRR=] [,TNSVCTST=] [,TNSVCPTST=]
[,NNSVCTSTR=] [,NBVCBR=] [,NBVCUR=] [,NBVCRR=]
[,T1=] [,T2=] [,TF1=] [,N3101=] [,N3103=] [,N3105=]
[,NRLCMAX=] [,T3141=] [,T3169=] [,T3172=] [,T3191=]
[,T3193=] [,T3195=] [,TEMPCH=] [,THPROXT=]
[,TIMEDTBFREL=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL PCU SET PCU
Applicability:
Phase 2.
Visibility level 2.
This command modifies the specific parameters of the PCU object class.
To change NSEI and NMO parameters, the PCU must be LOCKED and the same check
like create must be done. In this case the command is not forwarded to PCU because
at unlock all the configuration is reloaded. To set the other attributes the PCU object
could remain unlocked.
System Responses:
None.
SET ACK:
Successful
SET NACK:
NACK CAUSES:
OBJECT_NOTEQUIPPED
The NSEI attribute can be set only if the PCU is in
LOCKED state.
Different PCU instances must have different NSEI
values.
Commands
CML:BSC
173-183
Mr.M.Kaufmann

Set PCU:NAME=PCU:0,NMO=2,NSEI=40,TNSVCBLK=3,NNSVCBLKR=25,
NNSVCUBLR=7,TNSVCR=6,NNSVCRR=32,TNSVCTST=20,TNSVCPTST=5,
NNSVCTSTR=20,NBVCBR=12,NBVCUR=21,NBVCRR=14,T1=4,T2=6,TF1=50,
N3101=32,N3103=23,N3105=10,NRLCMAX=26,T3141=16,T3169=4,T3172=23,
T3191=9,T3193=5,T3195=23,TEMPCH=45,THPROXT=30-90-120,
TIMEDTBFREL=15;
174-183
Mr.M.Kaufmann
PPLD object
CREATE PPLD: NAME=PPLD:ppldn;
A30808-X3247-K230-2-7619 571
Command Tree:
MANAGED-ELEMENT BSS-EQUIPMENT BSCEPPLDCREATE PPLD
Applicability:
Phase 2.
Visibility level 2.
This command adds a PPLD card to the system. Each card supports the level 2 of the
LAPD protocol; the LAPD link can be configured at 64 kbit/s or 16 kbit/s.
The LAPD link can be for BTSM (LPDLM), TRX (LPDLR), TRAU (LPDLS); the PPLD
card has the following restriction about the managing of these different link:
The validity range of the object address "ppldn" can be found in Appendix A.
System Responses:
PDLM number + LPDLS number <= 8
PDLM number + LPDLS number + LPDLR number <= 64
CREATE ACK:
Successful
LOAD IN PROGRESS: SFWR
Processor Type: PPLD
Processor: 2
Directory: SYS_BACKUP
N.E Software Version: 01-00-01-01-04-04_95-03-01
File Software Version: 01-00-01-01-04-04_95-03-01
CREATE NACK:
NACK CAUSES:
The instance of the object must not be already created in order
to perform the command.
CML:BSC Commands
1. The relevant hardware has to be plugged in the corresponding slot before submitting
the command.
2. After the creation of the object, the ADMINISTRATIVE state of this object is set to
UNLOCKED. The UNLOCK command is NOT required to put this object in service.
3. The system can support LAPD Links only after the creation of two PPLD cards at
least. One PPLD is available to the system whilest the other is a physical spare.
Create PPLD:NAME=PPLD:2;
If the object instance number is greater then 2, the EPWR
object instance must be already equipped.
INVALID_COMMAND
A PPLD object instance can not be created if NTWCARD =
NTWSNAP (BSC object).
175-183
Mr.M.Kaufmann
PTPPKF object
CREATE PTPPKF: NAME=BTSM:btsmn/BTS:btsn/PTPPKF:ptppkfn,=,
RACODE=, RACOL= [,BSCDVMA=] [,PKTNDEC=]
[,PKTNINC=] [,PKTNMA=] [,GRXLAMI=] [,GMSTXPMAC=]
[,ABUTYP=] [,RAARET=] [,GPATH=] [,GTXINT=] [,GS=]
[,GMANRETS=] [,GMANMSAL=] [,T3168=] [,T3192=]
[,INICSCH=] [,NTWCOR=] [,GTEMPOFF=] [,GPENTIME=]
[,GRESOFF=] [,GCELLRESH=] [,C31H=] [,C32QUAL=]
[,TRESEL=] [,RARESH=] [,GHCSTH=] [,GHCSPC=]
[,ALPHA=] [,TAVGW=] [,TAVGT=] [,PRPBCCH=]
[,PCMECH=] [,NAVGI=] [,BSPBBLK=] [,BPAGCHR=]
[,BPRACHR=] [,DRXTMA=] [,CACKTYP=] [,GAM=]
[,GASTRTH=] [,GPDPDTCHA=] [,QSRHPRI=]
[,FDDGQO=] [,GMAPERTCHRES=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSMBTSPTPPKF
CREATE PTPPKF
Applicability:
Phase 2.
Visibility level 2.
This command creates an instance of the PTPPKF object class. It can be done only if
the super-ordinate BTS and all the necessary NSVC (at least one) are created. Creation
of PTPPKF object means to allow GPRS service in a specific cell.
The information to the mobile about the GPRS service in the network are provided via
system information. The status at creation will be Locked-Disabled/Offline.
On the created PTPPKF, a BVCI reset procedure is performed toward SGSN. After a
positive termination of the procedure, the PTPPKF shall became Locked-Enabled and
a block procedure is necessary to reflect the locked condition.
Validity ranges of the object addresses btsmn, btsn and "ptppkfn" can be found in
Appendix A.
System Responses:
CREATE ACK:
Successful
CREATE NACK:
NACK CAUSES:
CML:BSC Commands
None.
Create PTPPKF:NAME=BTSM:0/BTS:0/PTPPKF:0,RACODE=1,
RACOL=5,BSCDVMA=5, PKTNDEC=6,PKTNINC=7,PKTNMA=0,GRXLAMI=10,
GMSTXPMAC=20,ABUTYP=0,RAARET=0,GPATH=2,GTXINT=9,GS=3,
GMANRETS=2, GMANMSAL=7,T3166_68=2,T3192=3,INICSCH=CS1,
NTWCOR=0,GTEMPOFF=2, GPENTIME=25,GRESOFF=20,GCELLRESH=7,
C31H=0,C31QUAL=TRUE, TRESEL=5,RARESH=6,GHCSTH=11,GHCSPC=4,
ALPHA=8,TAVGW=15,TAVGT=7, PRPBCCH=12,PCMECH=0,NAVGI=9,
BSPBBLK=0,BPAGCHR=5,PBRACHR=8, DRXTMA=4,CACKTYP=1,
GASTRTH=10-20,GPDPDTCHA=0,QSRHPRI=UMDB82,FDDGQO=DB08,
GMAPERTCHRES=0;
176-183
Mr.M.Kaufmann

The relevant BTS object instance must be already created.
At least one PCU instance must already exist.
At least one NSVC must be created.
The ThresholdIdleChanHV field of the GASTRTH parameter has to
be lower than the ThresholdIdleChanVH field.
The command must be done in LOCKED state if the following
attributes are changed: RACODE, RACOL, GPDPDTCHA.
GET PTPPKF NAME=BTSM:btsmn/BTS:btsn/PTPPKF:ptppkfn

[,REQATTL=RACODE, RACOL, BSCDVMA, PKTNDEC,
PKTNINC, PKTNMA,GRXLAMI, GMSTXPMAC, ABUTYP,
RAARET, GPATH, GTXINT, GS, GMANRETS, GMANMSAL,
T3168, T3192, INICSCH, NTWCOR,
GTEMPOFF, GPENTIME, GRESOFF, GCELLRESH, C31H,
C32QUAL, TRESEL, RARESH, GHCSTH, GHCSPC, ALPHA,
TAVGW, TAVGT, PRPBCCH, PCMECH, NAVGI, BSPBBLK,
BPAGCHR, BPRACHR, DRXTMA, CACKTYP, GAM,
GASTRTH, GPDPDTCHA, QSRHPRI, FDDGQO,
GMAPERTCHRES];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSMBTSPTPPKF
GET PTPPKF
Applicability:
Phase 2.
Visibility level 1.
This command is used to retrieve the parameter values of an instance of the PTPPKF
object class.
Appendix A.
System Responses:
GET ACK:
NAME: name
RACODE: RoutingAreaCode
RACOL: RoutingAreaColour
BSCDVMA: bscountdownValueMax
PKTNDEC: packetNumberDecrement
PKTNINC: packetNumberIncrement
PKTNMA: packetNumberMax
GRXLAMI: gprsRxLevelAccessMin
GMSTXPMAC: gprsMxTxPwrMaxCch
ABUTYP: accessBurstType
RAARET: randomAccessRetry
GPATH: gprsPriorityAccessThreshold
GTXINT: gprsTxInterval
GS: gprsSlot
GMANRETS: gprsMaxNumberRetransmission
GMANMSAL: gprsMaxNumberMsAllocated
T3168 t3168
T3192 t3192
177-183
Mr.M.Kaufmann
INICSCH: initialCodingScheme
NTWCOR: networKControlOrder
GTEMPOFF: gprsTemporaryOffset
GPENTIME: gprsPenaltyTime
GRESOFF: gprsReselectionOffset
GCELLRESH: gprsCellReselectHysteresis
C31H: c31Hysteresis
C32QUAL c32Qualifier
TRESEL tResel
RARESH: routingAreaReselectHysteresis
GHCSTH: gprsHierarchycalCellStructureThreshold
GHCSPC: gprsHierarchycalCellStructurePriorityClass
ALPHA: alphaPowerControlAlgorithm
TAVGW: tAverageWeight
TAVGT: AverageTime
PRPBCCH: powerRedactionOnPbcch
PCMECH: oowerControlMeasurementChannel
Commands
CML:BSC
None.
Get PTPPKF:NAME=BTSM:0/BTS:0/PTPPKF:0,REQATTL=RACODE&
RACOL&BSCDVMA&PKTNDEC&PKTNINC&PKTNMA&GRXLAMI&GMSTXPMAC&
ABUTYP&RAARET&GPATH&GTXINT&GS&GMANRETS&GMANMSAL&
T3168&T3192&INICSCH&NTWCOR&GTEMPOFF&GPENTIME&GRESOFF&
GCELLRESH&C31H&C32QUAL&TRESEL&RARESH&GHCSTH&GHCSPC&
ALPHA&TAVGW&TAVGT&PRPBCCH&PCMECH&NAVGI&BSPBBLK&BPAGCHR&
BPRACHR&DRXTMA&CACKTYP&GAM&GASTRTH&GPDPDTCHA&QSRHPRI&
FDDGQO&GMAPERTCHRES;
NAVGI: nAverageInterference
BSPBBLK bsPbcchBlocks
BPAGCHR: bsPagchBlocksReserved
BPRACHR: bsPrachBlocksReserved
DRXTXMA: discontinousReceptionTimerMax
CACKTYP: controlAcknowledgementType
GAM: gamma
GASTRTH: gprsAllocationStrategyThresholds
GPDPDTCHA gprsPercentageOfDinamicPdtchAvailable
QSRHPRI qSearchPriority
FDDGQO fddGPRSQOffset
GMAPERTCHRES gprsMaxPercentageTCHReserved
GET NACK:
NACK CAUSES:
DELETE PTPPKF NAME=BTSM:btsmn/BTS:btsn/PTPPKF:ptppkfn;
Command Tree:
MANAGED-ELEMENTBSS-FUNCTIONALBTSMBTSPTPPKFDELETE
178-183
Mr.M.Kaufmann
PTPPKF
Applicability:
Phase 2.
Visibility level 2.
This command deletes a previously created instance of the PTPPKF object class. It can
be done only if the object is in Locked state. The appropriate system information shall
be sent on Um interface to inform the mobile about availability of the service. Because
of also SGSN knows the BVCI connected to this object, appropriate actions to inform it
about new PTPPKF configurations should be taken by BSC.
Commands
CML:BSC
Appendix A.
System Responses:
None.
Delete PTPPKF:NAME=BTSM:0/BTS:0/PTPPKF:0;
DELETE ACK:
SUCCESSFUL
DELETE NACK:
NACK CAUSES:
Before deleting a PTPPKF, the relative object instance must be in
LOCKED state.
The PTPPKF cannot be deleted if there is a subordinate TRX with GSUP
set at TRUE.
A GPRS handover relationship (ADJC) can be configured only between
two GPRS cells (PTPPKF equipped).
This means that no incoming relationship must contain GSUP set at TRUE;
this parameter cannot be TRUE in any ADJC object in the BSC referring
the BTS with the same instance number of the PTPPKF being deleted as
TGTCELL.
The same nack cause is generated for the outgoing ADJC relationship:
GSUP cannot be TRUE in any ADJC instance subordinated to the BTS
with the same instance number of the PTPPKF being deleted.
SET PTPPKF: NAME=BTSM:btsmn/BTS:btsm/PTPPKF:ptppkfn

[,RACODE=] [,RACOL=] [,BSCDVMA=] [,PKTNDEC=]
[,PKTNINC=] [,PKTNMA=] [,GRXLAMI=] [,GMSTXPMAC=]
[,ABUTYP=] [,RAARET=] [,GPATH=] [,GTXINT=] [,GS=]
[,GMANRETS=] [,GMANMSAL=] [,T3168=] [,T3192=]
[,INICSCH=] [,NTWCOR=] [,GTEMPOFF=] [,GPENTIME=]
[,GRESOFF=] [,GCELLRESH=] [,C31H=] [,C32QUAL=]
[,TRESEL=] [,RARESH=] [,GHCSTH=] [,GHCSPC=]
[,ALPHA=] [,TAVGW=] [,TAVGT=] [,PRPBCCH=]
[,PCMECH=] [,NAVGI=] [,BSPBBLK=] [,BPAGCHR=]
[,BPRACHR=] [,DRXTMA=] [,CACKTYP=] [,GAM=]
179-183
Mr.M.Kaufmann
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL BTSMBTSPTPPKF SET
PTPPKF
Applicability:
Phase 2.
Visibility level 2.
This command modifies the specific parameters of the PTPPKF object class. It is used
to change the configuration attributes associated to this object. Some attributes can be
changed without the interruption of the service while some other needs interruption of
the service. The following attributes can be changed only after PTPPKF locking, that
means service interruption: RACODE, RACOL and CACKTYP (reserved for further
implementation).
Appendix A.
System Responses:
SET ACK:
Successful
SET NACK:
CML:BSC Commands
None.
Set PTPPKF:NAME=BTSM:0/BTS:0/PTPPKF:0,RACODE=1,RACOL=5,BSCDVMA=5,
PKTNDEC=6,PKTNINC=7,PKTNMA=0,GRXLAMI=10,GMSTXPMAC=20,ABUTYP=0,
RAARET=0,GPATH=2,GTXINT=9,GS=3,GMANRETS=2,GMANMSAL=7,
T3166_68=3,T3192=2,INICSCH=CS1,NTWCOR=0,GTEMPOFF=2,GPENTIME=25,
GRESOFF=20,GCELLRESH=7,C31H=0,RARESH=6,GHCSTH=11,GHCSPC=4,
ALPHA=8,TAVGW=15,TAVGT=7,PRPBCCH=12,PCMECH=0,NAVGI=9,
BSPBBLK=0,BPAGCHR=5,PBRACHR=8,DRXTMA=4,CACKTYP=1,
GASTRTH=10-20,GPDPDTCHA=0,QSRHPRI=UMDB82,FDDGQO=DB08,
GMAPERTCHRES=0;
NACK CAUSES:
The command must be done in LOCKED state if the following
attributes are changed: RACODE, RACOL, GPDPDTCHA.
The ThresholdIdleChanHV field of the GASTRTH parameter
has to be lower than or equal to the ThresholdIdleChanVH
field.
SCAN BTSGPRSMEAS object

CREATE SCANGPRS: NAME=SCANGPRS:scann ,MEASLST= ,OBJLST=
[,GRANP=] [,START=] [,STOP=] 180-183
,RECINT=;
Mr.M.Kaufmann
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL SCANGPRS CREATE
SCANGPRS
Applicability:
Phase 2.
Visibility level 2.
This command creates the configuration of instance of the scanner of SCANGPRS
object. The parameter specify the values for the scheduling and reporting activities.
The validity range of the object address "scann" can be found in Appendix A.
System Responses:
CREATE ACK:
STATUS_MANAGER -> SYSTEM_BROADCAST
*** INFORMATION ***
CHANGED STATE EVENT REPORT:
NAME = SCANGPRS:instn
Administrative State = from NO_ADMINISTRATIVE_STATE to UNLOCKED
Operational State = from NO_OPERATIONAL_STATE to ENABLED
Old Availability Status = Null Status
New Availability Status = Off_Duty
DBA -> LMT_LOCAL
*** RESPONSE TO JOB 1 ***
Create Ack SCANGPRS:
commandResponse = SUCCESSFUL
CREATE NACK
NACK CAUSES:
The number of equipped scanner of GPRMEAS class is 5.
The instance of the object must not be already created in order to perform
the command.
UNSUCCESSFUL_POOL_EXHAUSTED
The list of free pools is too small for the lists of meas or list of object
requested.
WRONG_LIST_OF_MEASURE
ACTMEASLS is not in the allowed range of values.
CML:BSC Commands
1. The measurements have to be applied to already equipped object instances; after
the creation of the object the ADMINISTRATIVE state is UNLOCKED.
2. When a Restart of BSC is done, the Performance Measurements Data collected in
the last granularity are not significant.
Create SCANGPRS:NAME=SCANGPRS:0,MEASLST=allMeas(0),
OBJLST=selfAdapting(0),GRANP=MINUTES_30,START=1-1-2001,
STOP=31-12-2001,RECINT=all(0);
UNSUCCESSFUL_LIST_OF_OBJECT
The OBJLIST contains the same object more times.
ACTOBJLS = LST_ELEMENTS but no object has been specified in
OBJLIST.
ACTOBJLS contains a value out of range.
181-183
Mr.M.Kaufmann
UNSUCCESSFUL_MEAS_ALREADY_PRESENT
The same measure on the same object has been already configured in
an other scanner.
UNSUCCESSFUL_TIMEFRAME_INCORRECT
Start date > stop date.
UNSUCCESSFUL_TIMEFRAME_ELAPSED
Actual date > stop date.
UNSUCCESSFUL_NO_RECORDING_PERIOD
There is not any recording period (VLDFreq).
UNSUCCESSFUL_WRONG_RECORDING_DURATION
Recording period duration is not multiple of granularity.
UNSUCCESSFUL_WRONG_RECORDING_START
Recording period start is not a multiple of granularity.
UNSUCCESSFUL_RECORDING_DAY_ELAPSED
Recording period start + duration > 24:00.
UNSUCCESSFUL_RECORDING_OVERLAPPED
PERTYPE = WEEKLY_PERIOD and periods are overlapped.
UNSUCCESSFUL_DBC_NOT_UPDATE
The pub management functions fail, the commands are refused.
SET SCANGPRS: NAME=SCANGPRS:scann [,MEASLST=] [,OBJLST=]

[,GRANP=] [,START=] [,STOP=] [,RECINT=];
Command Tree:
MANAGED-ELEMENT BSS-FUNCTIONAL SCANGPRS SET SCANGPRS
Applicability:
Phase 2.
Visibility level 2.
This command creates the configuration of instance of the scanner of SCANGPRS
object. The parameter specify the values for the scheduling and reporting activities.
The validity range of the object address "scann" can be found in Appendix A.
System Responses:
SET ACK:
STATUS_MANAGER -> SYSTEM_BROADCAST
*** INFORMATION ***
CHANGED STATE EVENT REPORT:
Administrative State = from NO_ADMINISTRATIVE_STATE to UNLOCKED
Operational State = from NO_OPERATIONAL_STATE to ENABLED
Old Availability Status = Null Status
New Availability Status = Off_Duty
DBA -> LMT_LOCAL
*** RESPONSE TO JOB 1 ***
Set Ack SCANGPRS:
commandResponse = SUCCESSFUL
SET NACK
NACK CAUSES:
MAX_NUMBER_OF_OBJECT_INSTANCES_IS_ALREADY_CREATED
The number of equipped scanner of GPRMEAS class is 5.
UNSUCCESSFUL_POOL_EXHAUSTED
The list of free pools is too small for the lists of meas or list of object
requested.
182-183
Mr.M.Kaufmann
The LSTGPRSMEASTYP does not contain valid Measure lds.
WRONG_LIST_OF_MEASURE
ACTMEASLS is not in the allowed range of values.
UNSUCCESSFUL_LIST_OF_OBJECT
The OBJLIST contains the same object more times .
Commands
CML:BSC
1. The measurements have to be applied to already equipped object instances; after
the creation of the object the ADMINISTRATIVE state is UNLOCKED.
2. When a Restart of BSC is done, the Perfomance Measurements Data collected in
the last granularity are not significant.
Set SCANGPRS:NAME=SCANGPRS:0,MEASLST=measList(TNPDTLC |MPDTQLEN
| NPMSDISQ | MEAOLPDC | NATPRRE),OBJLST=selfAdapting(0),
GRANP=MINUTES_60,START=1-1-2001,STOP=2-2-2002,RECINT=all(0);
ACTOBJLS = LST_ELEMENTS but no object has been specified in
OBJLIST.
ACTOBJLS contains a value out of range.
UNSUCCESSFUL_MEAS_ALREADY_PRESENT
The same measure on the same object has been already configured in
an other scanner.
UNSUCCESSFUL_TIMEFRAME_INCORRECT
Start date > stop date.
UNSUCCESSFUL_TIMEFRAME_ELAPSED
Actual date > stop date.
UNSUCCESSFUL_NO_RECORDING_PERIOD
There is not any recording period (VLDFreq).
UNSUCCESSFUL_WRONG_RECORDING_DURATION
Recording period duration is not multiple of granularity.
UNSUCCESSFUL_WRONG_RECORDING_START
Recording period start is not a multiple of granularity.
UNSUCCESSFUL_RECORDING_DAY_ELAPSED
Recording period start + duration > 24:00.
UNSUCCESSFUL_DBC_NOT_UPDATE
The pub management functions fail, the commands are refused.
183-183
Mr.M.Kaufmann

GPRSP 60 V 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GPRSP 60 V 5

Uploaded by

Copyright:

Available Formats

Database planning

handbook for GPRS

The reproduction, transmission or use of this document or its contents

Proprietary data, company confidential.

Channel Configuration Overview______________________________________________51

Packet Common Control Channel PCCCH___________________________________________52

Control Channel Configuration________________________________________________58

Physical Layer Protocol__________________________________________________________35

Temporary block flow (TBF)______________________________________________________10

Packet Common Control Channel__________________________________________________58

Mobility Management States______________________________________________________60

Packet Timing Advance Feature________________________________________________61

System Information Management______________________________________________63

Operational sequence to configure a BSC for GPRS_______________________________67

HW/ SW Restrictions in the GPRS release_______________________________________68

Design of Radio cells____________________________________________________69

GPRS Path loss criterion C1______________________________________________________70

The MS shall make a cell reselection if:_____________________________________________74

GPRS features BR5.5____________________________________________________80

QoS (Quality of service)______________________________________________________84

GPRS support on CCCH & PCCH_____________________________________________87

Discontinuous Reception (DRX)_______________________________________________88

DRX (Paging) on CCCH_________________________________________________________88

8 GPRS BR 5.5 implementation aims__________________________________________90

Object Structure, SBS Parameter List_______________________________________91

Relevant GSM specifications______________________________________________98

GPRS features BR6.0___________________________________________________99

Appendix C (database example)___________________________________________106

Appendix D (command manual)_________________________________________125

11.1 Horizontalallocation ___________________________________________________________99

GPRS architecture, interfaces

Serving GPRS Support Node

Gn-Interface between SGSN and GGSN

Figure 2 Protocol stack for data transmission in GPRS

The GSM RF is the physical radio channel used to transfer

The Medium Access Control provides the access to the

The Logical Link Control layer provides a logical connection

The mapping of different Layers is shown in the next figure:

Normal B = Normal Burst (1 TDMA frame)

FCS = Frame Check Sequence

BCS = Block Check Sequence

transmission and reception data flow in GPRS

There are two different Radio block structures:

Radio Block structure for data transfer:

Radio Block structure for control message:

RLC/ MAC control message

Radio block: RLC/MAC Blocks

To ensure the right transmission order of RLC/MAC blocks, there is a Block

C3 : Parity - Pattern of the FN

Uplink State Flag

Bits C13, C14

both bits are used to perform

Figure 5 C-bits of PCU frame

Figure 6 Standard PCU Frame

The MAC provides the establishment of a Temporary Block Flow (TBF),

This timer is started at network

TBF establishment initiated by MS on PCCCH

The purpose of the packet access procedure is to establish a TBF.

This parameter indicates whether

not allowed in the cell

The MS shall initiate a packet access procedure by scheduling the sending

This parameter indicates the type

See GSM 5.02