Professional Documents
Culture Documents
1 Critical
0 Critical
4 Critical
13 Critical
14 Critical
15 Critical
17 Critical
18 Critical
20 Critical
23 Critical
1 Critical
0 Critical
1 Critical
0 Critical
1 Critical
0 Critical
0 Critical
1 Critical
1 Critical
0 Critical
1 Critical
0 Critical
1 Critical
3 Critical
3 Critical
3 Critical
4 Critical
4 Critical
1 Critical
0 Critical
3 Critical
18 Critical
20 Critical
23 Critical
26 Critical
30 Critical
3 Critical
3 Critical
3 Critical
3 Critical
6 Critical
6 Critical
6 Critical
6 Critical
3 Critical
3 Critical
6 Critical
6 Critical
3 Critical
3 Critical
6 Critical
6 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
0 Critical
0 Critical
1 Critical
50 Critical
18 Critical
0 Critical
40 Critical
5000 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
3 Critical
34 Critical
0 Critical
0 Critical
50 Critical
18 Critical
18 Critical
0 Critical
4 Critical
5 Critical
5 Critical
6 Critical
2 Critical
1 Critical
3 Critical
3 Critical
1 Critical
0 Prohibited
0 Critical
0 Critical
60 Critical
25 Critical
25 Critical
50 Critical
14 Critical
0 Critical
0 Critical
0 Critical
2 Critical
2 Critical
0 Critical
Critical
1 Prohibited
1 Critical
4 Critical
4 Critical
1 Critical
2 Critical
0 Critical
0 Critical
0 Prohibited
0 Prohibited
0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0 Critical
6 Critical
0 Critical
0 Critical
0 Critical
0 Critical
1;1;1;1 Critical
30;30;30;30 Critical
0 Prohibited
1 Critical
1200 Critical
1800 Critical
600 Critical
3000 Critical
0 Critical
0 Critical
3 Critical
0 Prohibited
85 Critical
5 Critical
95 Critical
0 Prohibited
0 Prohibited
1 Prohibited
20 Critical
1 Critical
1 Critical
1 Critical
0 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
0 Critical
1 Critical
1 Critical
0 Critical
1 Critical
200 Critical
0;0;0;255;255;0;0;0;0;0;0;0;0;255;127;0;0;0;0;0;0;0;0;255;255;255;255;255;31;0;0;255;0;0;0;255;255;255;255;0;0;0;0;0;0;255;127;0;0;0;0
Critical
0 Prohibited
0 Critical
0 Prohibited
1 Critical
1 Prohibited
1 Prohibited
0 Critical
80 Critical
1 Critical
80 Critical
0 Critical
65 Critical
0 Critical
100 Critical
1 Critical
2 Critical
0 Critical
0 Critical
12 Critical
6 Critical
59 Critical
59 Critical
20 Critical
1 Critical
600 Critical
30 Critical
30 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0;0;0;0 Critical
1 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
1122 Critical
1122 Critical
0 Critical
0 Critical
0 Critical
0 Critical
3 Critical
20 Critical
1 Critical
1 Prohibited
1 Prohibited
0 Critical
3 Critical
0 Critical
0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0 Critical
0 Critical
85 Critical
1 Critical
0 Critical
1 Critical
46 Critical
22 Critical
46 Critical
22 Critical
22 Critical
8 Critical
22 Critical
48 Critical
38 Critical
0 Critical
0 Critical
90.0 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Critical
1500 Critical
100 Critical
100 Critical
18 Critical
0 Prohibited
180.0 Critical
0 Prohibited
2 Critical
1800 Critical
20 Critical
4 Prohibited
60 Critical
15 Critical
1 Prohibited
1 Critical
3 Critical
0 Critical
0 Critical
6 Critical
0 Critical
0 Critical
1000 Critical
800 Critical
0 Critical
0 Critical
100 Prohibited
100 Prohibited
300 Prohibited
30 Prohibited
1800 Prohibited
10 Critical
3 Critical
3 Critical
0 Critical
300 Critical
400 Critical
3 Critical
1 Critical
10 Critical
0 Critical
3 Critical
3 Critical
1 Critical
100 Critical
0 Critical
1 Critical
0 Prohibited
0 Critical
0 Critical
1 Critical
1 Critical
5 Critical
3 Critical
1200 Critical
80 Critical
30 Critical
0 Critical
1000 Critical
800 Critical
3000 Critical
100 Critical
0 Prohibited
0 Critical
1 Critical
1114130 Critical
30 Critical
3 Critical
3 Critical
3 Critical
3 Critical
3 Critical
0 Critical
80 Prohibited
40 Prohibited
80 Prohibited
80 Prohibited
100 Prohibited
100 Prohibited
80 Critical
80 Critical
100 Critical
80 Critical
100 Critical
100 Critical
10 Critical
0 Critical
200 Critical
1 Critical
0 Critical
40 Critical
0 Critical
0 Prohibited
60 Critical
0 Prohibited
0 Prohibited
1 Critical
0 Critical
0 Critical
254 Critical
3 Critical
1200 Critical
1 Critical
300 Critical
6 Critical
3 Critical
0 Critical
1000 Critical
0 Critical
0 Critical
550 Critical
3 Critical
0 Prohibited
0 Critical
1 Critical
0 Critical
1 Critical
60 Critical
1 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Prohibited
1 Critical
700 Critical
0 Critical
3 Critical
0 Critical
1 Critical
0 Critical
0 Critical
1 Critical
65535 Critical
0 Critical
0 Prohibited
0 Critical
0 Prohibited
1 Critical
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Critical
1 Critical
0 Prohibited
1 Critical
0 Prohibited
0 Critical
0 Critical
1 Critical
3 Critical
200 Critical
600 Critical
1 Critical
300 Critical
50 Prohibited
30 Critical
50 Prohibited
1 Critical
1 Critical
1 Critical
1 Critical
0 Critical
1 Critical
0 Critical
0 Critical
12 Critical
3 Critical
0 Critical
80 Critical
3 Critical
3 Critical
2 Critical
0 Critical
0 Critical
0 Critical
0 Critical
3 Critical
0 Critical
3 Critical
1 Critical
0 Critical
50 Critical
0 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Prohibited
3 Critical
0 Critical
0 Critical
0 Critical
120 Critical
3 Critical
1 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
180 Critical
30 Critical
300 Critical
30 Critical
30 Critical
30 Critical
30 Critical
30 Critical
30 Critical
90 Critical
1 Critical
100 Critical
1 Critical
15 Critical
100 Critical
50 Critical
250 Critical
60 Critical
3000 Critical
80 Critical
150 Critical
100 Critical
60 Critical
25 Critical
300 Critical
90 Critical
110 Critical
60 Critical
60 Critical
100 Critical
100 Critical
150 Critical
200 Critical
20 Critical
5 Critical
90 Critical
300 Critical
100 Critical
60 Critical
40 Critical
100 Critical
100 Critical
180 Critical
11 Critical
100 Critical
500 Prohibited
500 Prohibited
550 Critical
200 Critical
20 Prohibited
30 Prohibited
30 Prohibited
30 Prohibited
120 Critical
100 Critical
20 Critical
6 Critical
1 Critical
60 Critical
50 Critical
50 Critical
50 Critical
50 Critical
100 Critical
5 Critical
180 Critical
10 Critical
30 Critical
10 Critical
100 Critical
100 Critical
50 Critical
50 Critical
60 Critical
20 Critical
20 Critical
300 Critical
120 Critical
50 Critical
100 Critical
20 Critical
20 Critical
50 Critical
100 Critical
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
1 Critical
1 Critical
40 Prohibited
1 Critical
0 Critical
1 Prohibited
1 Prohibited
1 Prohibited
1 Critical
1 Critical
0 Prohibited
1 Prohibited
1 Critical
2 Critical
0 Critical
0 Critical
1 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
64 Prohibited
15 Critical
0 Prohibited
10 Critical
0 Prohibited
0 Critical
4 Critical
1 Critical
1 Critical
7 Prohibited
2 Critical
0 Critical
5 Critical
3 Critical
18 Critical
0 Critical
1 Critical
3 Critical
9 Critical
10 Critical
85 Critical
144 Critical
400 Critical
50 Critical
12 Critical
0 Critical
20 Critical
1 Critical
0 Critical
1 Critical
0 Critical
1 Critical
3 Critical
3 Critical
1 Critical
0 Critical
0 Critical
4;8;12;16;20;24;28;32;36;40;44;48;52;56;60;64 Critical
3 Critical
3 Critical
20 Critical
20 Critical
2 Critical
0 Critical
5 Critical
3 Critical
18 Critical
0 Critical
1 Critical
19 Critical
1 Critical
1 Critical
1 Critical
0 Critical
1 Critical
0 Critical
1 Critical
0 Prohibited
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
0 Critical
1 Critical
4 Critical
0 Critical
1 Critical
0 Critical
0 Critical
1 Critical
1 Critical
5 Critical
5 Critical
0 Critical
0 Critical
50 Critical
5 Critical
10 Critical
50 Critical
0 Critical
600 Critical
20 Critical
0 Critical
40 Critical
24 Critical
48 Critical
0 Critical
20 Critical
10 Critical
10 Critical
30 Critical
0 Critical
1 Critical
1 Critical
120 Critical
1123 Critical
14 Critical
14 Critical
0 Critical
0 Critical
0 Critical
Critical
360 Critical
0 Critical
0 Critical
18 Critical
0 Critical
0 Critical
1 Critical
1123 Critical
14 Critical
1 Critical
0;0;0;0;0;0;0;0 Critical
100 Critical
1 Critical
1 Critical
0 Critical
100 Critical
50 Critical
40 Critical
2 Critical
1 Critical
50 Critical
40 Critical
2 Critical
60 Critical
20 Critical
90 Critical
2 Critical
1 Critical
100 Critical
1 Critical
1122 Critical
0 Critical
1 Critical
Critical
10 Critical
0 Critical
1 Critical
0 Critical
500 Critical
0 Critical
0 Critical
0 Critical
1 Critical
1 Critical
5 Critical
5 Critical
30 Critical
40 Critical
0 Critical
1 Critical
1 Critical
1 Critical
1 Critical
5 Critical
5 Critical
13 Critical
20 Critical
0 Critical
100 Critical
50 Critical
1 Critical
1836 Critical
2 Critical
1 Critical
4 Critical
1 Critical
47111 Critical
0 Critical
0 Critical
3001 Critical
1122 Critical
3001 Critical
1 Critical
100 Critical
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Prohibited
0 Critical
5 Critical
5 Critical
5 Critical
1 Critical
200 Critical
720 Critical
720 Critical
50 Critical
1122 Critical
3001 Critical
1 Critical
1122 Critical
50 Critical
45000 Critical
1122 Critical
3001 Critical
1122 Critical
1122 Critical
0.0.0.0 Critical
4 Critical
0 Critical
0 Critical
50 Critical
1122 Critical
3001 Critical
1122 Critical
1 Critical
10.227.69.116 Critical
4 Critical
50 Critical
14019 Critical
96 Critical
0.0.0.0 Critical
4 Critical
1000 Critical
2 Critical
1000 Critical
48 Critical
100 Critical
1 Critical
0 Critical
0 Critical
17 Critical
0 Critical
60 Critical
1000 Critical
1 Critical
1 Critical
875 Critical
60 Prohibited
1123 Critical
1 Critical
1 Critical
1134 Critical
1 Critical
2 Critical
1122 Critical
0 Critical
1 Critical
255;255;255;255 Prohibited
410,1;410,7 Prohibited
No_Value Prohibited
1 Prohibited
1 Prohibited
1122 Critical
1 Critical
1 Critical
6 Critical
0 Critical
1 Critical
10 Critical
0 Critical
1 Critical
0 Critical
1 Critical
1134 Critical
1 Critical
1 Critical
13 Critical
0 Critical
0 Critical
Critical
1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1 Critical
1134 Critical
17 Critical
17 Critical
1122 Critical
0 Critical
1135 Critical
1 Critical
1 Critical
0 Prohibited
60 Critical
80 Critical
0 Critical
70 Critical
999 Critical
1 Critical
30 Critical
1 Critical
0 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
30 Critical
2 Critical
0 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
0 Critical
1 Critical
0 Critical
0 Critical
0 Critical
5 Critical
3 Critical
0 Critical
30 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
1 Critical
0 Critical
0 Critical
25 Critical
3 Critical
0 Critical
1 Critical
0 Critical
000000000000 Critical
Critical
Critical
Critical
Critical
0 Critical
Critical
Critical
Critical
1 Critical
1 Critical
0 Critical
20 Critical
0 Critical
0 Critical
0 Critical
18 Critical
50 Critical
0 Critical
Meaning
Adjacent Net Element Identifier
udp checksum switch
UDP and RTP Demultiplexing Switch
Net Element ID
User Label
OMCB Inner Service Ip Address
OMCB Inner Service Ip Address
whether or not in order
Priority Adjust Coefficient
The parameter indicates maximum length of multiplexing UDP packet.
UDP and RTP multiplexing Switch
NodeB Inner IP
NodeB Inner IP
Net Element Reserved Parameter1
Net Element Reserved Parameter10
Net Element Reserved Parameter11
Net Element Reserved Parameter12
Net Element Reserved Parameter13
Net Element Reserved Parameter14
Net Element Reserved Parameter15
Net Element Reserved Parameter16
Net Element Reserved Parameter17
Net Element Reserved Parameter18
Net Element Reserved Parameter19
Net Element Reserved Parameter2
Net Element Reserved Parameter20
Net Element Reserved Parameter 1
Net Element Reserved Parameter 10
Net Element Reserved Parameter 11
Net Element Reserved Parameter 12
Net Element Reserved Parameter 13
Net Element Reserved Parameter 14
Net Element Reserved Parameter 15
Net Element Reserved Parameter 16
Net Element Reserved Parameter 17
Net Element Reserved Parameter3
Net Element Reserved Parameter 18
Net Element Reserved Parameter 19
Net Element Reserved Parameter 2
Net Element Reserved Parameter 20
Net Element Reserved Parameter 21
Net Element Reserved Parameter 22
Net Element Reserved Parameter4
Net Element Reserved Parameter5
Net Element Reserved Parameter6
Net Element Reserved Parameter7
Net Element Reserved Parameter8
Net Element Reserved Parameter9
Payload Type of Multiplexing UDP packet
0
CS12.2K call payload under the condition of UDP multiplexing
CS64K call payload under the condition of UDP multiplexing
Multiplexing UDP port
Destination IP address
net mask for Destination IP
Length of Destination IP address
Destination IP address
TrPath ID
Transport BandWidth Adjustment Switch based on IP SLA
IP Domain No
Reserved Field1
RX bandwidth Ratio of TrPath reserved for NRT Service
TX bandwidth Ratio of TrPath reserved for NRT Service
RX bandwidth Ratio of TrPath reserved for RT Service
Route Select Factor
TX bandwidth Ratio of TrPath reserved for RT Service
Rx bandwidth
Tx bandwidth
User Label
CIR Weight Of Rate Vibration Service
Adjacent Net Element Identifier
udp checksum switch
UDP and RTP Demultiplexing Switch
0
User Label
Net Element ID
A Office Object ID
whether or not in order
Transmission type at A interface
Priority Adjust Coefficient
The parameter indicates maximum length of multiplexing UDP packet.
UDP and RTP multiplexing Switch
Net Element Reserved Parameter 23
Net Element Reserved Parameter 24
Net Element Reserved Parameter 25
Net Element Reserved Parameter 26
Net Element Reserved Parameter 27
Net Element Reserved Parameter 28
Net Element Reserved Parameter 29
Net Element Reserved Parameter 3
Net Element Reserved Parameter 30
Net Element Reserved Parameter 31
Net Element Reserved Parameter 32
Net Element Reserved Parameter 33
Net Element Reserved Parameter 34
Net Element Reserved Parameter 35
This parameter indicates the time interval between sending RTCP (SR and SDES) packets.
This parameter indicates the RTCP packet switch. RTCP is an optional protocol in 3GPP. If this switch is
turned on, RTCP packets are sent periodically based on RTP sessions to the opposite end.
CS12.2K call payload under the condition of RTP multiplexing
CS64K call payload under the condition of RTP multiplexing
Payload Type of Multiplexing UDP packet
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 4.75kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 5.15kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 5.9kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 6.7kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 7.4kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 7.95kbps.
This parameter specifies C/I hysteresis for increasing the AMR HR codec mode from 10.2kbps.
This parameter indicates the initial speech codec mode of AMR FR employs the mode specified by
Startmode or the default initial codec mode specified in protocol 45.009. The initial codec mode specified in
the protocol is described as follows:
1. When there is one codec mode, this mode is employed as the initial mode.
2. When there are two or three codec modes, the lowest speed mode is employed as the initial mode.
3. When there are four modes, the mode with the second lowest speed is employed as the initial mode.
For the A interface using IP, this parameter is not used. Instead, the system control parameter
IpaAMRStartMode decides the initial codec mode.
This parameter specifies whether the AMR noise suppression on the MS is disabled for the AMRFR speech
version. The noise suppression function on the MS keeps the speech quality by controlling the background
noise.
This parameter decides the initial codec mode for the AMR FR speech version. The value must not be larger
than the number of codec modes contained in the ACS. The parameter values are described as follows:
1: the initial codec mode employs the one with the lowest speed
2: the initial codec mode employs the one with the second lowest speed
3: the initial codec mode employs the one with the third lowest speed
4: the initial codec mode employs the one with the forth lowest speed
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 4.75kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 5.15 kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 5.9kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 6.7kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 7.4kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 7.95kbps.
This parameter specifies the C/I threshold for reducing the AMR FR codec mode to 10.2kbps.
This parameter specifies whether the ACS of AMR FR contains the 4.75kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 5.15 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 5.9 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 6.7 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 7.4 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 7.95 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 10.2 kbps codec mode.
This parameter specifies whether the ACS of AMR FR contains the 12.2 kbps codec mode.
This parameter specifies whether the ACS of AMR HR contains the 4.75 kbps codec mode.
This parameter specifies whether the ACS of AMR HR contains the 5.15 kbps codec mode.
This parameter specifies whether the ACS of AMR HR contains the 5.9 kbps codec mode.
This parameter specifies whether the ACS of AMR HR contains the 6.7 kbps codec mode.
This parameter specifies whether the ACS of AMR HR contains the 7.4 kbps codec mode.
This parameter specifies C/I hysteresis for increasing the AMR FR codec mode from 4.75kbps.
This parameter specifies C/I hysteresis for increasing the AMR FR codec mode from 5.15kbps.
This parameter specifies C/I hysteresis for increasing the AMR FR codec mode from 5.9kbps.
This parameter specifies C/I hysteresis for increasing the AMR FR codec mode from 6.7kbps.
This parameter specifies C/I hysteresis for increasing the AMR FR codec mode from 7.4kbps.
This parameter indicates the initial speech codec mode of AMR HR employs the mode specified by
Startmode or the default initial codec mode specified in protocol 45.009. The initial codec mode specified in
the protocol is described as follows:
1. When there is one codec mode, this mode is employed as the initial mode.
2. When there are two or three codec modes, the lowest speed mode is employed as the initial mode.
3. When there are four modes, the mode with the second lowest speed is employed as the initial mode.
For the A interface using IP, this parameter is not used. Instead, the system control parameter
IpaAMRStartMode decides the initial codec mode.
This parameter specifies whether the AMR noise suppression on the MS is disabled for the AMRHR speech
version. The noise suppression function on the MS keeps the speech quality by controlling the background
noise.
1: the initial codec mode employs the one with the lowest speed
2: the initial codec mode employs the one with the second lowest speed
3: the initial codec mode employs the one with the third lowest speed
4: the initial codec mode employs the one with the forth lowest speed
This parameter specifies the C/I threshold for reducing the AMR HR codec mode to 4.75kbps.
This parameter specifies the C/I threshold for reducing the AMR HR codec mode to 5.15kbps.
This parameter specifies the C/I threshold for reducing the AMR HR codec mode to 5.9kbps.
This parameter specifies the C/I threshold for reducing the AMR HR codec mode to 6.7kbps.
This parameter specifies the C/I threshold for reducing the AMR HR codec mode to 7.4kbps.
The hysteresis for changing AMROWFS mode includes two factors, which are represented by two
parameters: amrOwfsHysteresis1 and amrOwfsHysteresis2.
amrOwfsThresholds1+amrOwfsHysteresis1≤amrOwfsThresholds2+amrOwfsHysteresis2
The hysteresis for changing AMROWFS mode includes two factors, which are represented by two
parameters: amrOwfsHysteresis1 and amrOwfsHysteresis2.
amrOwfsThresholds1+amrOwfsHysteresis1≤amrOwfsThresholds2+amrOwfsHysteresis2
There are two thresholds for changing AMROWFS mode, which are represented by two parameters:
amrOwfsThresholds1 and amrOwfsThresholds2.
The two parameter values must meet the following two conditions:
(1) amrOwfsThresholds1≤amrOwfsThresholds2
The two parameter values must meet the following two conditions:
(1) amrOwfsThresholds1≤amrOwfsThresholds2
The hysteresis for changing AMROWHS mode includes two factors, which are represented by two
parameters: amrOwhsHysteresis1 and amrOwhsHysteresis2.
amrOwhsThresholds1+amrOwhsHysteresis1≤amrOwhsThresholds2+amrOwhsHysteresis2
The hysteresis for changing AMROWHS mode includes two factors, which are represented by two
parameters: amrOwhsHysteresis1 and amrOwhsHysteresis2.
amrOwhsThresholds1+amrOwhsHysteresis1≤amrOwhsThresholds2+amrOwhsHysteresis2
There are two thresholds for changing AMROWHS mode, which are represented by two parameters:
amrOwhsThresholds1 and amrOwhsThresholds2.
The two parameter values must meet the following two conditions:
(1) amrOwhsThresholds1≤amrOwhsThresholds2
(2) amrOwhsThresholds1+amrOwhsHysteresis1≤amrOwhsThresholds2+amrOwhsHysteresis2
There are two thresholds for changing AMROWHS mode, which are represented by two parameters:
amrOwhsThresholds1 and amrOwhsThresholds2.
The two parameter values must meet the following two conditions:
(1) amrOwhsThresholds1≤amrOwhsThresholds2
(2) amrOwhsThresholds1+amrOwhsHysteresis1≤amrOwhsThresholds2+amrOwhsHysteresis2
The hysteresis for changing AMRWFS mode includes four factors, which are represented by four
parameters: amrWfsHysteresis1, amrWfsHysteresis2, amrWfsHysteresis3, and amrWfsHysteresis4.
amrWfsThresholds1+amrWfsHysteresis1≤amrWfsThresholds2+amrWfsHysteresis2≤amrWfsThresholds3
+amrWfsHysteresis3≤amrWfsThresholds4+amrWfsHysteresis4
The hysteresis for changing AMRWFS mode includes four factors, which are represented by four
parameters: amrWfsHysteresis1, amrWfsHysteresis2, amrWfsHysteresis3, and amrWfsHysteresis4.
amrWfsThresholds1+amrWfsHysteresis1≤amrWfsThresholds2+amrWfsHysteresis2≤amrWfsThresholds3
+amrWfsHysteresis3≤amrWfsThresholds4+amrWfsHysteresis4
There are four threshold values during AMRWFS mode change: amrWfsThresholds1, amrWfsThresholds2,
amrWfsThresholds3, and amrWfsThresholds4. The following condition must be met:
amrWfsThresholds1≤amrWfsThresholds2≤amrWfsThresholds3≤amrWfsThresholds4,amrWfsThresholds1
+amrWfsHysteresis1≤amrWfsThresholds2+amrWfsHysteresis2≤amrWfsThresholds3+
amrWfsHysteresis3≤amrWfsThresholds4+amrWfsHysteresis4
There are four threshold values during AMRWFS mode change: amrWfsThresholds1, amrWfsThresholds2,
amrWfsThresholds3, amrWfsThresholds4. The following condition must be met:
amrWfsThresholds1≤amrWfsThresholds2≤amrWfsThresholds3≤amrWfsThresholds4,amrWfsThresholds1
+amrWfsHysteresis1≤amrWfsThresholds2+amrWfsHysteresis2≤amrWfsThresholds3+
amrWfsHysteresis3≤amrWfsThresholds4+amrWfsHysteresis4
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 4.75k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 5.15k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 5.9k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 6.7k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 7.4k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 7.95k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 10.2k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Full Rate AMR (FR AMR)
supports 12.2k. If yes, the full-rate ACS can be configured with the
current rate. If not, the ACS cannot be configured with the current
rate, therefore, FR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 4.75k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate,
therefore, HR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 5.15k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate,
therefore, HR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 5.9k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate,
therefore, HR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 6.7k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate,
therefore, HR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 7.4k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate,
therefore, HR AMR speech cannot use the current rate.
This parameter indicates whether the Half Rate AMR (HR AMR)
supports 7.95k. If yes, the ACS can be configured with the current
rate. If not, the ACS cannot be configured with the current rate.
Therefore, HR AMR speech cannot use the current rate.
This parameter indicates the time period in which the target of forced handover cannot be a handover
target any more after the forced handover fails.
Start: The target fails to carry out the handover and release the channel.
Stop: None.
Start: A forced handover is initiated and the assignment waits for channel releases.
Stop: The user that initiates the forced release accesses a channel.
Timeout action: More forced handovers or releases will be initiated or the assignment will still queue for
resources, depending on parameter settings.
This parameter decides the time to wait for resources after a forced release. If a resource is obtained within
this period, no more forced releases will be initiated and the assignment will stop queuing. If not, more
forced releases will be initiated or the assignment will still queue for resources, depending on specified
settings. The parameter should be set according to the time required for a complete forced release.
Start: A forced release is initiated and the assignment waits for channel releases.
Stop: The user that initiates the forced release accesses a channel.
Timeout action: More forced releases will be initiated or the assignment will still queue for resources,
depending on parameter settings.
During searches for the targets of forced handovers or releases, if the call duration of the targets is larger
than this parameter, these targets will be considered to have enough long calls and can be the targets of
forced handovers or releases. No more searches for the target with the longest call duration will be done. In
this way, the number of times of searches is reduced.
During searches for the targets of forced handovers or releases, if the priorities of the targets are not higher
than this priority, these targets will be considered to have the lowest priorities and can be the targets of
forced handovers or releases. No more searches will be done. In this way, the number of times of searches
is reduced. The value "1" indicates the highest priority.
#N/A
This parameter decides whether to allow forced releases during an assignment or carry out the assignment
according to the cell settings when there are no available channels in the cell.
This parameter decides whether to allow forced releases during a handover or carry out the handover
according to the cell settings when there are no available channels in the cell.
This parameter (PriThreshold) uses the service of preferred access for high-priority subscriber, that is eMLPP
service, the system may set some reserved channels (currently, only full rate TCH channels are supported to
be the reserved channels).
When CS instance calls database to apply for channels, the subscriber's PriorityLevel information reaches to
database, and is compared with PriThreshold in the database and BSC table. When
PriorityLevel≤PriThreshold (the less the subscriber's priority level value, the higher the priority level, that is
the subscriber's priority level is not lower than PriThreshold priority), the reserved channel can be used.
During an assignment, this parameter decides whether to allow queuing or carry out the assignment
according to the cell settings when there are no available channels in the cell.
During a handover, this parameter decides whether to allow queuing or carry out the assignment according
to the cell settings when there are no available channels in the cell.
#N/A
This parameter indicates the selection order of reserved channel and non-reserved channel. If this feature is
enabled, the reserved channel has the higher priority.
0 (NO): Disabled.
1 (YES): Enabled. The related functions include queuing, forced handover and release, and reserved
channels.
#N/A
#N/A
#N/A
#N/A
Abis allocation to consider the quality of the circuit
Abis exclusive support
Switch of CAC for A Interface of BSC
This parameter is a user access control switch based on the SIM card
priority.
This switch controls one cell.
This parameter specifies the access priority classes which are forbidden for access.
Each MS in GSM system has an access priority class (15 classes in all). Class 10 is not used for access control
as specifiedin the protocol.
This parameter is valid when UseCellAcc is set to 0. Otherwise, the AccessControl parameter at the cell level
is used foraccess control.
This parameter indicates the validity period of a neighbor cell's load information.
Acoustic Echo Canceller Function Control
Automatic Level Control Function Control
This parameter indicates a switch that controls whether to carry the
IMEI in encryption. If this parameter is set to 1, the BSC will inform
the MS to carry the IMEI for tracing, even if this is not required by
MSC.
This parameter specifies whether to allow simultaneous sending of connection and channel activation
commands.
At the Abis interface using E1 line for transport, the LAPD packet generating has a long delay, which leads to
long delay for message interaction. When the BSC sends the connection command and channel activation
command to the BTS at the same time, the message interaction delay can be reduced.
#N/A
It indicates whether the Call Detail Trace (CDT) function is supported.
CDTOPTION_0: It indicates whether to report the intra-BSC handover success message. The default value is
1.
CDTOPTION_1: It indicates whether to report the PS service information. The default value is 1.
CDTOPTION_10: It indicates whether to report the PS access failure message. The default value is 0.
Report recent seven MR before Ho when Ho succeed
0
CDTOPTION_2: It indicates whether to report the location update information. The default value is 1.
CDTOPTION_3: It indicates whether to report the short message information. The default value is 1.
CDTOPTION_4: It indicates whether to report the access failure message. The default value is 0.
CDTOPTION_7: It indicates whether to report the measurement report in location update. The default value
is 0.
CDTOPTION_8: It indicates whether to report the measurement report in short message. The default value
is 1.
CDTOPTION_9: It indicates whether to report the measurement report after a normal call is completed. The
default value is 1.
This parameter determines whether the affected cell notifies the related MS of cell selection unavailable
when the A interface is broken. The MS after receiving the notification will select the other networks of the
operator, for example, a 3G/4G network.
This parameter determines whether to check IMSI during access.
For some MSs, when accessing the network again after call drop, the BSC may detect the IMSI conflict from
the IMSI contained in the initial access information, and then sends CLEAR REQ to the MSC. In this case, a
call drop is recorded both at the A interface and inside the BSC.
If the IMSI conflict is not checked, the BSC does not send CLEAR REQ to the MSC, and the BSC does not
record a call drop. In this case, the MSC initiates the release procedure after detecting the IMSI conflict. This
will reduce the call drop records.
#N/A
#N/A
CIC Block Alarm Switch
#N/A
#N/A
This parameter determines whether to assign a channel to subcell 2 directly according to the first
measurement report when the Co-BCCH is used.
A group of switchs for Iur-g: "On Demand" mode switch of Common Measurement
A group of switchs for Iur-g: "Periodic" mode switch of Common Measurement
Send confusion message allowed
This parameter indicates the CMP's CPU usage threshold that triggers the FUC-based flow control when
being exceeded. That is to say, if the CPU usage exceeds the threshold and the parameter CpuFucFlc is set
to "Yes", the FUC-based flow control will be enabled.
This parameter decides whether to enable FUC-based flow control when the CPU usage of the CMP
increases to the threshold of the FUC-based flow control.
This parameter indicates the CPU usage threshold for initiating the paging flow control when the threshold
is exceeded.
This parameter decides whether to enable paging flow control when CPU usage is high.
This parameter indicates the CMP's CPU usage threshold that triggers the system messaging-based flow
control when being exceeded. That means if the CPU usage exceeds the threshold and the parameter
CpuSysInfoFlc is set to "Yes", the system messaging-based flow control will be enabled.
This parameter decides whether to enable system messaging-based flow control when the CPU usage of the
CMP increases to the threshold of the system messaging-based flow control.
#N/A
This parameter determines whether a handover is enabled during circuit data service.
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
This parameter decides whether the BSC supports dynamic HR. The dy-
namic HR channel allocation function enables the network to allocate
full-rate or half-rate channels to MSs according to the traffic in the cell
when it allocate channels for the MSs. Allocating half-rate channels when
the channels in the cell are likely to be congested minimizes the duration
of possible congestions in peak hours.
When the cell load is larger than the emergency threshold,the the
system will add trx license for this cell.This paramter is the period
for this apply.
#N/A
#N/A
#N/A
This parameter controls whether the MOS calculation result is
reported.
This parameter determines whether the enhanced and the pre-processed measurement reports are
reported. If this parameter is set to "Yes", the TRACEID and a value (unit: ms) are attached to various
measurement reports.
This parameter specifies whether the Assignment Failure message is allowed to be sent to the MSC if the
external directed retry procedure fails.
This parameter specifies the first SIM card level which is forbidden for access. This parameter uses ACC data
for the useraccess control based on the SIM card level.
Flex A function switch. It determines whether the Flex A function is supported. If the Flex A function is
enabled, iBSC can be interconnected with multiple MSCs, and one iBSC can be connected with at most 16
MSCs.
Flex GB function switch. It determines whether the Flex GB function is supported. If the Flex GB function is
enabled, iBSC can be interconnected with multiple SGSNs, and one iBSC can be connected with 16 SGSNs at
most.
It expands the service area of an SGSN, reduces the number of inter-SGSN PS handovers and routing area
updates, and reduces the frequency and flow of HLR update.
SGSN POOLs have overlapping area, which are suitable for various mobile modes of MS.
It helps increase the network capacity. The traffic hot spot moves with the movement of users, but the
VLR/SGSN of MS is relatively fixed in an SGSN POOL. Thus, when the traffic in hot spot area suddenly
increases, the load of an SGSN will not increase.
It improves the overall disaster tolerance capability of the network. When an SGSN is faulty in the SGSN
POOL, its traffic can be taken over by another SGSN in the SGSN POOL.
This parameter specifies whether to report the CS service failure observation.
This parameter specifies whether to report the PS service failure observation.
This parameter specifies whether to report the DBS failure observation.
#N/A
This parameter indicates the supported frequency band. If you select DCS1800, the DCS1800 frequency
band will be supported. If you select PCS1900, the PCS1900 frequency band will be supported. This
parameter cannot be modified after you select a frequency band.
GSM Logical Function Object ID
The BSC ID cannot be modified. By default, its value is the same as that of the Subnetwork ID parameter.
#N/A
#N/A
This parameter decides whether BSC initiates a classmark request, asking the UE to report its
UtranClassmark information after the UE performs handover from 3G network to 2G network. During a
handover from the 3G network to the 2G network, it is possible that the handover request does not contain
the UE’s UtranClassmark information, or contains improper information. This would cause failures when the
UE performs 2G->3G handover later.
This parameter is a switch to support the HR channel defragmentation function and can be configured on
both BSCs and cells. The HR channel defragmentation function is enabled only when both BSC- and cell-level
switches are enabled and the proportion of the idle TCH/Fs in these cells is not more than the threshold
proportion of the TCH/Fs to the total available service channels in the cell where the defragmentation is
enabled.
#N/A
#N/A
This parameter specifies the maximum number of immediate assignment message retransmissions. It can
be set to 0 and 1. The value 0 indicates that the immediate assignment message is not retransmitted, while
1 indicates that the message is retransmitted up to one time.
A group of switchs for Iur-g: "On Demand" mode switch of information exchange
A group of switchs for Iur-g: "On Modification" mode switch of information exchange
This parameter indicates whether inter-BSC handover on the SDCCH is allowed. When the parameter value
is 1 (yes), the target cell of a handover on SDCCH can be an external cell. When the parameter value is 0, an
external cell cannot be the target cell of a handover on SDCCH.
#N/A
#N/A
#N/A
#N/A
#N/A
This parameter indicates the initial AMR rate when IPA is applied. When IPA is applied, the ACS of AMR
speech coding modes is specified by the MSC, so the initial rate cannot be exactly decided. For this reason,
the default rate or the maximum rate is used as the initial rate, and this applies when ACS is a rate set.
When this parameter is set to Default, the initial rate is coded according to the default value specified in the
protocol 45.009.
When one mode is used, the corresponding rate is used as the initial coding mode.
When two or three modes are used, the lowest rate is used as the initial coding mode.
When four modes are used, the second lowest rate is used as the initial coding mode.
The load indication process informs the adjacent BSCs about the load at the cell border, thus providing more
information as references in both normal handover and the intra-BSC traffic handover.
This parameter determines whether load indication is allowed, and the validity of parameter “Load
indication valid time” and “Load indication period”.
If this parameter is set to “0” (Not send load indication), the latter two parameters are invalid.
During load indication, the BSC sends the BSSAP LOAD INDICATION message to MSC periodically to inform
the MSC about the load status. The message includes the time indication information, which indicates the
valid time period of the service load information.
The MSC then sends the BSSAP LOAD INDICATION message to neighboring BSCs.
decides the period for the BSC to send the load indication message.
This parameter specifies the threshold for sending the load indication. If the load of a cell administered by
this BSC is higher than the value of this parameter, the system initiates a load indication process, which
informs adjacent BSCs about the load of the cells at the border so that more references can be provided in
normal handovers and intra-BSC handovers.
If the resource usage of an external adjacent cell is higher than the value of this parameter, the system does
not trigger handover to the cell.
During load indication, the BSC sends the BSSAP LOAD INDICATION message to MSC periodically to inform
the MSC about the load status. The message includes the time indication information, which indicates the
valid time period of the service load information.
MSC relays the information in the BSSAP LOAD INDICATION message to neighboring BSCs.
This parameter represents the valid time length of the load message.
Counter 1: Number of few MS MR received before connection failure after handover from adjacent cell
Counter 2: Number of few MS MR received before connection failure after handover from adjacent 3G cell
This parameter specifies whether the BTS power field is contained in the MR.
MR Report Enable
This parameter indicates the highest flow control level when MSCs are overloaded or signalling points are
congested.
Multile Signaling Point (MSP) function switch. It determines whether the MSP function is supported.
One signaling point can be configured with at most 16 links. To make A interface have sufficient bandwidth
and implement the MSP function, configure more links at A interface.
This parameter enables or disables unidirectional call detection. If this function is enabled, the user plane
will detect unidirectional calls and report necessary information to the back-end to facilitate fault location.
1: Perform radio pre-access procedure and determine whether to perform handover with the current
transmission resources
This parameter specifies the lower threshold of channel number within each BA range monitored by an idle
MS during re-selection.
This parameter specifies the upper threshold of channel number within each BA range monitored by an idle
MS during re-selection.
This parameter specifies the number of BA ranges that can be monitored with priority by an idle MS during
re-selection.
This parameter enables or disables wireless reassignment for the BSC.
This parameter specifies the level decision threshold for intra-cell directed retry during reassignment. When
the level of an adjacent cell is higher than that of the serving cell and reaches the threshold, the intra-cell
directed retry applies.
This parameter specifies the maximum retry number for terminal access by using a reassignment (normal
assignment) or handover (directed retry) command when the BSC receives a reassignment failure message
during a reassignment.
It indicates delay time before finishing BCCH handover, BTS block message is received after timer is timeout
(or BTS block is failed), select handover TRX to do handover.
Channel reformation and migration is implemented by intra-cell handover and temporarily occupies more
cell channels. Only when the cell channel use rate is lower than or equal to this parameter value, channle
reformation and migration can be performed.
This parameter specifies the threshold for the BSC to send a resource indication to the MSC. The value
indicates the ratio of the count of current available channels to the count of total channels. If the current
available resources are fewer than the specified threshold, the BSC sends a resource indication to the MSC,
indicating the resource situation.
1. Automatic sending mode: Upon receiving the BSSAP RESOURCE REQUEST message, the BSC returns a
BSSAP RESOURCE INDICATION message containing no resource information as response. Afterwards, when
the condition is met for automatic sending of resource information, the BSC sends a BSSAP RESUORCE
INDICATION message to the MSC. The parameter Periodicity IE in the BSSAP RESOURCE REQUEST message
specifies the message sending interval. If Periodicity IE is 0, the BSC neglects this value.
The condition for automatically sending resource information can be a traffic threshold or the interval
between two messages.
2. One-time mode: Upon receiving the BSSAP RESOURCE REQUEST message, the BSC returns a BSSAP
RESOURCE INDICATION message containing the resource information. If the BSSAP RESOURCE REQUEST
message does not contain Extended Resource Indication IE, the BSC stops sending return messages, and
waits for the next BSSAP RESOURCE REQUEST message. If the BSSAP RESOURCE REQUEST message contains
Extended Resource Indication IE, the BSC follows the rule set by Subsequent Mode in the message, as in
mode 4. If the previous mode is 1 or 3, the BSC uses the previous mode. Otherwise, mode 4 is used.
3. Periodicity mode: Upon receiving the BSSAP RESOURCE REQUEST message, the BSC returns a BSSAP
RESOURCE INDICATION message containing the resource information, and then sends the message
periodically.
If Periodicity IE in the BSSAP RESOURCE REQUEST message is not 0, the sending period is the multiplication
of Periodicity IE and 100 ms. If the Periodicity IE is 0, the BSSAP RESOURCE REQUEST message is considered
incorrect.
4. Stop mode: Upon receiving the BSSAP RESOURCE REQUEST message, the BSC returns a BSSAP RESOURCE
INDICATION message containing no resource information as response. Afterwards, the BSC does not send
any information about the cell resources to the MSC.
This parameter determines whether to use BER to calculate the average quality.
If the parameter is set to 1 (Yes), it is required to convert the RQ degree to the BER before calculating the
average.
If the parameter is set to 0 (No), use the RQ degree directly for calculating the average
This parameter indicates the period of scanning idle SDCCHs when the dynamic SDCCH/TCH conversion
function is enabled in a cell. After the dynamic SDCCH/TCH conversion function is enabled in a network, the
network scans SDCCHs at the period specified by this parameter to find the number of idle SDCCHs for
determining whether to convert SDCCH back to TCH
This parameter is a switch to enable the simultaneous sending of the immediate assignment message and
the channel activation message.
According to a general immediate assignment flow, the immediate assignment message is sent after the
channel activation message and the channel activation acknowledgement message. When this procedure is
followed, the immediate assignment message may fail after the channel activation message is sent and the
channel activation acknowledgement message is received if MS times out due to a long transmission delay
at Abis interface (for example, when a satellite medium is used for transmission). Sending the immediate
assignment message and the channel activation message at the same time can ensure the timely sending of
the immediate assignment message, improving the success rate of immediate assignment when the
transmission delay at Abis interface is long.
A CS paging is received in the PS service, if the paging coordination function is enabled, the system will send
a Paging CS message on the PACCH channel. This parameter specifies whether to send the Paging CS
message also on the CCCH channel. If the paging coordination function is disabled, this parameter specifies
whether to send the Paging CS message on the CCCH channel when a CS paging is received in the PS service.
#N/A
This parameter describes the SNS process monitoring timer. The conditions of timer start, stop, and timeout
action are described as follows:
Timer stop: It stops when the SNS response from SGSN is received.
This parameter describes the maximum number of retrying the SNS adding operation. When SNS_T1
expires, if the SNS Ack message is not received from SGSN, BSS retries the adding operation. If the SNS Ack
message is not received after the maximum number of retries are implemented, the flow is terminated and
a message is sent to O&M.
This parameter describes the maximum number of modifying the SNS weight. When SNS_T1 expires, if the
SNS Ack message is not received from SGSN, BSS retries the weight modification operation. If the SNS Ack
message is not received after the maximum number of retries are implemented, the flow is terminated and
a message is sent to O&M.
This parameter describes the maximum number of retrying the SNS configuration operation. When SNS_T1
expires, if the SNS Config Ack message is not received from SGSN, BSS retries the configuration operation. If
the SNS Config Ack message is not received after the maximum number of retries are implemented, the
flow is terminated and a message is sent to O&M.
This parameter describes the maximum number of retrying the SNS deleting operation. When SNS_T1
expires, if the SNS Ack message is not received from SGSN, BSS retries the deleting operation. If the SNS Ack
message is not received after the maximum number of retries are implemented, the flow is terminated and
a message is sent to O&M.
This parameter describes the maximum number of retrying the SNS SIZE operation. When SNS_T1 expires, if
the SNS Size Ack message is not received from SGSN, BSS retries the SNS Size operation. If the SNS Size Ack
message is not received after the maximum number of retries are implemented, the flow is terminated and
a message is sent to O&M.
This parameter determines whether the BSC supports a SON transfer application. The parameter is used
with the RIMSupport parameter. When the SONTrans function is enabled, the RIMSupport function must
also be enabled. In this case, the BSC can reply to a request of acquiring GSM cell loads from the external
UTRAN or E-UTRAN network through a Gb interface during the RAN Information Management (RIM)
process, and synchronizes the loads to the external network.
Blocking/Unblocking period
Protection period for global resetting
Circuit resetting period on BSS side
Circuit group blocking unblocking period
Protective time for No.7 signal instantaneous disconnection
Global resetting period
ATER block circuit group timer
ATER block circuit timer
ATER reset timer
ATER reset circuit timer
ATER BLOCK APORT CIRCUIT TIMER
ATER BLOCK APORT CIRCUIT GROUP TIMER
#N/A
It indicates whether to use an external TC.
#N/A
This parameter is one of TFO control parameters. It decides whether TFO is enabled.
0: disable
1: enable
When TFO is disabled, i.e., TFOControl_0 is set to 0, other related functions are also disabled, i.e. the values
of TFOControl_1, TFOControl_2 and TFOControl_3 are 0.
TFO is an inband protocol. The TC on both sides uses this protocol to negotiate the coding and decoding
after a call is set up. The sender decoder and receiver coder are bypassed.
The voice frame used over the air interface is directly sent to the receiver to improve voice quality.
If the speech version supported by the cell is not AMR, you can set up TF0 if the speech versions
supported by two cells are same. If speech version is AMR, TFO can be set up only if the supported speech
coding and decoding types are the same. Otherwise, TFO cannot be set up.
This parameter is used to enable dynamic SDCCH configuration function in the cell. After TCH is dynamically
converted to SDCCH channel and SDCCH channel is idle, to prevent from frequent channel conversion, a
time limit will be added for the conversion from SDCCH channel to TCH channel. During this limit, SDCCH
channel cannot be converted to TCH channel.
ATER reset guard timer
1: Perform transport pre-access procedure and determine whether to perform handover with the current
transmission resources.
This parameter enable or disables notification reporting if the loss of TRAU frame synchronization lasts for a
certain time period.
#N/A
This parameter is a switch for raising the air interface timeslot blocking alarm.
This parameter determines whether a TS-based reserved channel is effective. If it is set to 0, the parameter
IsRsv is not effective.
If this parameter is set to 1 (yes), the load of the first subcell is used as the whole cell load, and applied for
neighbor cell sorting, traffic handover decision.
If this parameter is set to 0 (No), the whole cell load is used, including the first and second subcell.
Whether the BTS 2.0 carrier on the BTSV2 site supports the AMR voice algorithm decides whether the
services on the carrier can use AMR voice coding.
This parameter decides whether the BTS adds the speech quality related parameters in the measurement
report, preprocessing of measurement report, and preprocessing of enhanced measurement report.
This parameter indicates the maximum number of Logic Link Control (LLC) frames bufferred in a BSSGP
instance. In packet-switched service, the parameter is used to prevent an instance from occupying extra
User Blocks (UBs).
If the PTP BVC must be blocked due to OAM intervention or equipment faults (disable blocking/unblocking
the signaling BVC), BSS will first set the BVC status as “Blocked” and discard the uplink service data.
To notify SGSN to stop sending downlink data, BSS initiates BVC blocking procedure. BSC repeats BVC
blocking procedure after sending BVC BLOCK message to SGSN. If BSC fails to receive BVC BLOCK
ACKNOWLEDGE message from SGSN in BSSGPT1, then BVC blocking repeats for a maximum of N times.
BSC stops BVC blocking and notifies OMS for N times if there is no answer. N depends on maximum retries
of BVC BLOCK.
This parameter determines the leaky bucket size of a BSSGP Virtual Connection (BVC). The leaky bucket size
varies with the parameter value to meet a calibration for flow control deviation.
BVC flow control occurs at Gb interface between SGSN and BSS, and only in downlinks. BSS provides control
parameters and SGSN executes, in order to avoid one BVC on BSS to abandoning some LLC data because of
the overtime caused by grouping channel is too busy (too many LLC frame caches) and to avoid abandoning
new downlink LLC data because of limit of memory resource (overflow of LLC frame caches).
BSSGP process at BSS side counts current leaking rate of BVC periodically (including short statistics and long
statistics). If the long statistics timer overflows, this parameter unconditionally initiates the BVC flow control
process; if the discrepant range of adjacent leaking rates is over CellFcThs, acknowledgement by SGSN is
required. If the short statistics timer overflows and if discrepant range of adjacent leaking rates is over
CellFcThs, this parameter initiates the BVC flow control process, and acknowledgement by SGSN is required.
This is the minimum value of leaking rate R in reported BVC flow control parameters under all kinds of flow
control mode, that is, the reported parameter R must be equal or over the set value, in the unit of 100 bps.
To keep the initial status consistent between the two BVC sides, the “Reset BVC” process must be initiated
in the following cases:
For faults that affect NSE, BSC initiates Signaling BVC RESET procedure. For faults that affect a single BVC,
BSC initiates the PTP BVC RESET procedure. BSC initiates all PTP BVC RESET procedure for corresponding
NSE after a signaling BVC reset procedure.
BSC repeats the BVC RESET procedure after sending “BVC RESET” message to SGSN and if BSC fails to
receive “BVC RESET ACKNOWLEDGE”
message from SGSN in BSSGPT2. The BVC RESET process could be repeated for N times at most. If there is
no answer after the N times, BSC stops BVC RESET and notifies OMS. N depends on maximum retries of BVC
RESET.
If the PTP BVC must be unblocked due to the OAM intervention or recovery of the equipment fault (disable
blocking/unblocking the signaling BVC), BSS will first set the BVC status as “Unblocked”.
To notify SGSN to start sending the downlink data, BSS will initiate the BVC unblocking procedure. BSC
repeats the BVC unblocking procedure after sending the BVC UNBLOCK message to SGSN. If BSC fails to
receive the BVC UNBLOCK ACKNOWLEDGE message from SGSN in BSSGPT1 then BVC unblocking repeats for
a maximum of N times.
BSC stops BVC unblocking and notifies OMS for N times if there is no answer. N depends on maximum
retries of BVC UNBLOCK.
This parameter indicates whether to support the compression and restoration of the user plane codec mode
according to bandwidth usage.
This parameter is the BVC leakage ratio measurement period in the “BVC Flow Control” process, that is, BVC
long measurement period.
To provide reference to the BVC flow control at SGSN side, the BSSGP process at BSS side periodically
measures the current BVC leakage ratio. BSC initiates the “BVC flow control” procedure unconditionally
when the long measurement timer overflows. SGSN confirms to BSC if the difference of leakage ratios
between the two times exceeds CellFcThs.
BSC also initiates “BVC flow control” procedure with SGSN confirmation if the short measurement timer
overflows, and the difference of the leakage ratio between the two timers exceed CellFcThs. The conditions
of timer start, stop, and timeout actions are as follows:
This parameter determines whether the affected cell notifies the related MS of PS inaccessiable when the
Gb interface is broken. The parameter is used to avoid an impact of invalid PS service requests on the
system.
This is one of the EDGE evolution functions. If this function is enabled, the GERAN carriers of two
independent frequency points (or different MAIO values in the case of frequency hopping) can be received
by the same terminal. This function is developed on the basis of multi-timeslot technology, and the
difference between them is that multi-timeslot allocation can span multiple carriers.
Max retry times to create PFC. If "Creat BSS PFC" is not received before timer BSSGPT6 is timeout, BSS sends
"Download BSS PFC" message according to max times of retrying to create PFC. If "Create BSS PFC" is not
received still after trying DownLoadBSSPRCMax+1, the process is completed and inform O&M.
This parameter indicates whether the cell supports DTM enhanced capability. If yes, then:1, The MS enters
the DTM transmission state without releasing PS when it receives a paging request from CS. 2, The MS
enters the Packet Transfer state without releasing PS resources when CS is released under DTM.
This parameter specifies whether DTM handover is supported. When this function is enabled, the BSC can
provide simultaneous CS and PS handover for DTM subscribers, improving the service continuity for DTM
mode.
This function can only be used when the DTM function is enabled.
This parameter indicates whether to continue CS handover when PS handover fails during DTM handover,
when DTM handover is enabled.
EGPRS2-A is the phase-I implementation of EGPRS2. In this phase, 16QAM, 32QAM, and Turbo code are
used, QPSK and 1.2-multiple symbol rate are not used. Also, DAS and UAS modulation coding scheme are
used.
This parameter indicates whether to support EGPRS prior to GPRS. After this function is enabled, in case
EGPRS and GPRS share channel, the system adjusts the number of allocated blocks for EGPRS and GPRS
according to the allocating weight of EGPRS.
This parameter indicates the allocating weights of EGPRS. When the EGPRS prior to GPRS function is
supported, the system adjusts the number of blocks allocated to EGPRS and GPRS according to this
allocating weight.
If the value is 0, EGPRS service fails to get blocks. If the value is 100, GPRS service fails to get blocks.
This parameter specifies whether PS Handover Indications is contained in the PS handover message.
This parameter determines whether the PS Handover message contains the request for BSC to respond for
the SI/PSI information.
On the basis of Radio Status, enhanced Radio Status reports three more cause values:
x02: indicates the enhanced Radio Status process is used when the cell reselection occurs. Usually, it helps
satisfy the service requirement to the maximum extent.
x03: indicates the enhanced Radio Status process is used when the MS is required to perform cell
reselection and LLC frame transfer is not supported.
reselection failure.
When Radio Status with the cause value x02 is received, the
When Radio Status with the cause value x03 is received, either
there are data to be sent to MS, then the downlink LLC frame sending is resumed.
can better understand the status of MS, which avoids sending data
In flow control mode 1, BSC reports a flow control parameter in accordance with an actual flow of radio
ports. The actual statistical flow is lower due to radio port retransmission and TBF failure. Therefore, the
actual flow control parameter reported by BSC is the value of actual statistical flow multiplied by a value
determined by this parameter.
In flow control mode 2, BSC reports a flow control value in accordance with the maximum flow of a cell. The
maximum flow is determined by the configured channel quantity (channel quantity × max. flow per
channel). This parameter is used to set the maximum flow of a channel, and the unit is 100 bps.
This parameter indicates whether to report the Current Bucket Level (CBL) in a BVC/MC flow control
message.
BSC has different flow control modes to report flow control parameters to SGSN. The modes are as follows:
1: Mode 1: Report flow control parameters according to actual traffic on radio interface counted at BSC;
2: Mode 2: Report flow control parameters according to max traffic that the cell can provide;
3: Mode 3: Reserved
"Flow control mode 1 parameter" is enabled if selecting "mode 1"; "Flow control mode 2 parameter" is
enabled if selecting "mode 2".
This parameter indicates whether IP segment optimization is enabled. The function is described as follows:
During the segmentation of LLC at the air interface, if the NU is discontinuous, the current LLC will be
transmitted with a 20-ms delay.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI0 (Reserved)
services. Generally, this function is not enabled for this type of data. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI1 (LLGMM)
services. Generally, this function is not enabled for the GMM signaling. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI10 (Reserved)
services. Generally, this function is disabled for this type of data. The purpose of this function is to transfer
the LLC frames from the source cell cache to the target cell when an MS performs cell reselection. This can
ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI11 (User-Data)
services. Generally, this function is enabled for user data. The purpose of this function is to transfer the LLC
frames from the source cell cache to the target cell when an MS performs cell reselection. This can ensure
the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI12 (Reserved)
services. Generally, this function is disabled for this type of data. The purpose of this function is to transfer
the LLC frames from the source cell cache to the target cell when an MS performs cell reselection. This can
ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI13 (Reserved)
services. Generally, this function is disabled for this type of data. The purpose of this function is to transfer
the LLC frames from the source cell cache to the target cell when an MS performs cell reselection. This can
ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI14 (Reserved)
services. Generally, this function is disabled for this type of data. The purpose of this function is to transfer
the LLC frames from the source cell cache to the target cell when an MS performs cell reselection. This can
ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI15 (Reserved)
services. Generally, this function is disabled for this type of data. The purpose of this function is to transfer
the LLC frames from the source cell cache to the target cell when an MS performs cell reselection. This can
ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI2 (TOM2)
services. Generally, this function is not enabled for TOM2 services. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI3 (User-Data)
services. Generally, this function is enabled for user data. The purpose of this function is to transfer the LLC
frames from the source cell cache to the target cell when an MS performs cell reselection. This can ensure
the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI4 (Reserved)
services. Generally, this function is not enabled for this type of data. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI5 (User-Data)
services. Generally, this function is enabled for user data. The purpose of this function is to transfer the LLC
frames from the source cell cache to the target cell when an MS performs cell reselection. This can ensure
the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI6 (Reserve)
services. Generally, this function is not enabled for this type of data. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI7 (LLSMS)
services. Generally, this function is not enabled for LLSMS services. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI8(TOM8)
services. Generally, this function is not enabled for TOM8 services. The purpose of this function is to
transfer the LLC frames from the source cell cache to the target cell when an MS performs cell reselection.
This can ensure the continuity of downlink data after cell reselection.
This parameter specifies whether the BSC supports the LLC frame transfer function for SAPI9 (User-Data)
services. Generally, this function is enabled for user data. The purpose of this function is to transfer the LLC
frames from the source cell cache to the target cell when an MS performs cell reselection. This can ensure
the continuity of downlink data after cell reselection.
Max retry times to modify PFC. If "Modify BSS PFC Ack" is not received before timer BSSGPT8 is timeout, BSS
sends "Modify BSS PFC" message according to max times of retrying to modify PFC. If "Modify BSS PFC Ack"
is not received still after trying ModifyBssPFCMax +1, the process is completed and inform O&M.
This parameter determines the actual leaky bucket size of a Mobile Station (MS). The leaky bucket size
varies with the parameter value to meet a calibration for flow control deviation.
This parameter is the MS leakage ratio measurement period in the ‘MS Flow Control’ process.
For reference of flow control at the SGSN side, the BSSGP process at the BSS side periodically measures the
current leakage ratio of each MS. When the statistic timer overflows, the ‘MS Flow Control’ process is
initiated unconditionally.
The conditions of timer start, stop, and timeout actions are as follows:
Timer start: BSSGP receives the downlink LLC frame at idle status.
MS flow control occurs at Gb interface between SGSN and BSS, and only in downlinks. BSS provides control
parameters and SGSN executes, to avoid one MS on BSS to abandoning some LLC data because of the
overtime caused by grouping channel is too busy (too many LLC frame caches) and to avoid abandoning new
downlink LLC data because of limit of memory resource (overflow of LLC frame caches).
The BSSGP process at the BSS side periodically measures the current leakage ratio of MS. When the statistic
timer overflows, the ‘MS Flow Control’ process is initiated unconditionally.
This is the minimum value of leaking rate R in reported MS flow control parameters under all kinds of flow
control mode, that is, the reported parameter R must be equal or over the set value, in the unit of 100 bps.
When the network after setting USF, receives a valid data block from the mobile station in a block assigned
for this USF, it will reset counter N3101. The network will increment counter N3101 for each USF for which
no data is received. N3101max shall be greater than 8. If N3101 = N3101max, the network shall stop the
scheduling of RLC/MAC blocks from the mobile station for this USF and start timer T3169.
This parameter is the counter N3103, which is a RLC/MAC layer parameter in the Packet Control Unit (PCU).
The counter N3103 counts the number of Packet Uplink ACK/NACK retry attempts.
In the process of packet uplink transmission, if the network detects that the TBF is completed (CV=0, and
V(Q)=V(R)), and has received all RLC data blocks, the network should send a Packet Uplink ACK/NACK
message, set the Final ACK Indicator (FAI) to 1, adds a legal RRBP field in the header of the RLC/MAC control
block, and clears the counter N3103.
If the MS receives the PACKET UPLINK ACK/NACK message (FAI=1) from the network, the MS should send
the PACKET CONTROL ACK message on the block specified by the RRBP and releases the TBF.
If the network does not receive the PACKET CONTROL ACK message on the block specified by the RRBP, the
counter N3103 is increased by 1 and the PACKET UPLINK ACK/NACK message is retransmitted.
If the value of counter N3103 exceeds the limit specified by the parameter N3103max, the network starts
the timer T3169. Upon timeout of T3169, the network can use the TFI and USF resources again.
When the network after sending a RRBP field in the downlink RLC data block or in Iu mode also RLC/MAC
control block, receives a valid RLC/MAC control message from the mobile station, it will reset counter
N3105. The network will increment counter N3105 for each allocated data block for which no RLC/MAC
control message is received for this TBF. The value of N3105max is network dependent.
For the MS, NACC is part of the GERAN Feature Package 1. The function includes:
1. The MS in PS transmission state can receive the system messages required for accessing the new cell.
2. The MS notifies the network (CCN mode) when deciding to perform a cell reselection.
1. After MS performs cell reselection, the network sends the system messages of neighbor cells of the new
cell on the PACCH.
2. After receiving the cell change information from the MS, the network sends to the MS the system
messages of recommended neighbor cells or other neighbor cells.
When NACC is used together with CCN, Packet (P)SI Status functions, the cell reselection time can be
reduced.
There are three network operation modes:
Network Operation Mode 1: The network sends to the "GPRS-attached" MS the CS paging message on the
same channel of GPRS paging channel (packet or CCCH paging channel), or on the GPRS traffic channel
(when it is assigned with a packet data channel). Mode 1 indicates that MS only need to monitor one paging
channel.
Network operation mode 1 is required while configuring PBCCH; Gs interface is required while configuring
network operation mode 1.
Network Operation Mode 2: The network sends to the “GPRS-attached” MS the CS paging message on the
CCCH paging channel, which is also for GPRS paging. Mode 2 indicates that the MS only need to monitor
CCCH paging channel, but when BSC allocates a packet data channel, the CS paging message uses the CCCH
paging channel.
Network Operation Mode 3: The network sends to the "GPRS-attached" MS the CS paging message on the
CCCH paging channel, and sends the GPRS paging message either on the packet paging channel (if there is
any in the cell) or on the CCCH paging channel. Mode 3 indicates that the MS must monitor two paging
channels (if packet paging channel is available in the cell) in order to receive CS or GPRS paging message.
This parameter determines if intra-BSC cell supports CS page coordination. This parameter is broadcast in
GPRS CELL OPTIONS through SI13, PSI1, and PSI13 messages. It is invalid when the NMO value is 1.
Page coordination means that CS service paging can be sent to a subscriber on the PS service channel
PACCH when the MS is in the PS transmission state.
This parameter indicates a field of implicit rejection carried in a paging message. The field means implicitly
rejecting an access to a terminal with low access priority.
This parameter determines whether to enable the UPPB resource alarm function. The availability of UPPB
board resources can be measured through the availability of each DSP resource on UPPB board. The
measured indexes include failure ratio for allocating memory, use ratio for MAC instance, use ratio for
BSSGP instance, use ratio of mac-tlli index, use ratio for bssgp-tlli index, use ratio for radio channel instance,
and use ratio for TS instance.
PFC flow control occurs at Gb interface between SGSN and BSS, and only in downlink. BSS provides control
parameters and SGSN executes. It helps avoid a PFC in BSS discarding some LLC data due to timeout caused
by grouping channels being too busy (too many LLC frame buffers) and avoid discarding new downlink LLC
data due to limited memory resource (overflow of LLC frame buffer).
The BSSGP process at the BSS side periodically measures the current leakage ratio of MS. When the statistic
timer overflows, the 'PFC Flow Control' process is initiated unconditionally.
In EGPRS system with broadband features, the QoS concept of UMTS has been imported, which enables
transferring the negotiable QoS configuration to BSS through Gb interface.
BSS can maintain QoS subscribing information through function PFC (packet flow context) flow, which
include acquiring QoS, modifying QoS, and deleting QoS signaling flow. Network notifies MS if the network
supports PFC flow through the system message parameter PFC_FEATURE_MODE. If yes, the MS will add PFI
when establishing uplink TBF (PACKET RESOURCE REQUEST). BSS can decide QoS as MS requires according
to PFI.
This parameter indicates the highest-order encoding mode that can be used for POC service by an EGPRS-
attached MS.
This parameter indicates the highest-order encoding mode that can be used for POC service by a GPRS-
attached MS.
This parameter indicates if PoC subscriber applies for dedicated POC channel. PoC indicates Push to talk
over Cellular. Consider the MS with proper function as walkie-talkie. This kind of MS has a talkie key. After
pressing this key, you can talk with other subscribers or in a group.
This parameter indicates the upper limit of Abis resource proportion in the Full Dynamic Abis Resource Pool
that can be assigned to PS services. If the limit is exceeded, the remaining idle Abis resources cannot be
assigned to PS services.
The proportion of Abis resources used for PS services = number of Abis resources Assigned to PS services /
total Abis resources available in the resource pool
This parameter indicates the upper limit of PoC service subscribers in shared downlink channel.
If dedicated PoC channel is configured, it indicates the upper limit of PoC subscribers on the downlink of
each dedicated PoC channel. If it exceeds this number, PoC subscriber access is not allowed on the downlink
of this dedicated PoC channel.
This parameter indicates the upper limit of PoC service subscribers in shared uplink channel.
If dedicated PoC channel is configured, it indicates the upper limit of PoC subscribers on the uplink of each
dedicated PoC channel. If it exceeds this number, PoC subscriber access is not allowed on the uplink of this
dedicated PoC channel.
This parameter represents the maximum number of sending the PS Handover Required message during PS
handover. The message is sent again after expire of T12PsHo timer.
This parameter determine whether PS handover is supported.
This parameter indicates whether to choose PS route by NSVC. It is meaningful only when multiple IPGB
boards exist on site.
If BSC supports choosing route by NSVC, an IPGB board can send NS-ALIVE message through itself and thus
individually detects its NSVC status. At the same time, the user plane selects the NSVC in normal route
status to provide service. If BSC does not support choosing route through NSVC, the IPGB board sends the
NS-ALIVE message through another board and thus does not individually detect the route status of NSVC.
This parameter indicates whether the BSS writes the uplink power control information in the IMMEDIATE
ASSIGNMENT message after receiving a CHANNEL ACCESS REQUEST message from the MS.
It describes whether 2G/3G priority selection control is supported during PS handover or reselection.
The SGSN can add the Service UTRAN CCO information in such messages as PS Handover Request, Create
BSS PFC, or DL UnitData PDU to indicate for the BSC whether 3G is preferred, not preferred, or forbidden
during PS handover and reselection.
This parameter is a BSSGP layer parameter. When GPRS-attached MS leaves a special mode, BSS adopts one
of the following strategies:
In case of Routing Area Update, MS and SGSN directly negotiate GMM status. With the “Resume” method
(usually for the MS in the packet transmission status), BSS will initiate the “RESUME” process to SGSN for
the purpose of notifying SGSN to start the normal packet downlink transmission action. If BSC fails to
receive the “RESUME ACK/NACK” message from SGSN in BSSGPT4, then repeats Resume procedure for a
maximum of N times.
BSC stops the Resume procedure and notify OMS N times if there is no answer. N depends on the
parameter ResumeMax.
Default value of resumesetopt is 0, that means: when PS service is suspended, the suspend message isn’t
sent in Gb interface, the voice channel release message informs MS that it’s resumed and doesn’t need to
send RA update process resume.
When resumesetopt is 1, that means: when PS service is suspended, the suspend message is sent in Gb
interface, the voice channel release message informs MS that it isn’t resumed and needs to send RA update
process resume.
If resumesetopt is 0,and resumemax isn’t 3, that means: when PS service is suspended, the suspend
message isn’t sent in Gb interface, the voice channel release message informs MS that it’s resumed and
doesn’t need to send RA update process resume, a resume message is sent in Gb after the voice channel is
released. It’s used for test.
This parameter indicates the number of RIM retries. The maximum number of RIM retries is 3.
This parameter indicates whether the RIM function is enabled.
The RIM function refers to the quick reselection between BSCs or between BSC and RNC. In BSC external
Network Assisted Cell Change (NACC), to accelerate the speed to access a new cell during cell reselection for
the MS, BSC sends the new cell system messages to the MS when it is in source cell before the cell
reselection. This reduces the time for listening to complete system messages after the MS reselects the new
cell.
To obtain system messages of a cell out of the BSC, the external NACC needs the RAN Information
Management (RIM) process between SGSN and BSC.
When an BSC supports the RIM function, service triggers BSC to obtain, store and update the system
messages of external cell through the RIM process. Accordingly, when the RIM function is supported, the
BSC also needs to provide the system messages of its cells and notifies the message changes to
corresponding BSCs/RNCs, if requested by other BSCs/RNCs.
#N/A
Ratio of Abis resources that need dynamic management
This parameter indicates whether the Reduced Transmission Time Interval (RTTI) function is supported.
RTTI is a concept relative to BTTI. Basic Transmission Time Interval (BTTI) means that four consecutive Bursts
are used on a channel to transmit a radio block, and it takes 20 ms to transmit a radio block. For RTTI, two
consecutive Bursts on two channels (PDCH-pair) respectively are used, and it takes only 10 ms to transmit a
radio block.
This parameter indicates whether the extended uplink TBF is supported for a signalling TBF. This switch is
valid when the switch of extended uplink TBF is enabled. The signaling TBF refers to a TBF established for
transmitting GMM signalling.
This parameter indicates whether to rank the LLC frames by SNDCP number for transmission.
This parameter determines which solution (DSCP or BSSGP) is used to identify the specific service.
This parameter determines whether an implicit access rejection field is carried in a paging message. The
terminal supporting the implicit rejection function determines whether to initiate an implicit rejection flow
when initiating an access request.
This parameter indicates whether to support the resource optimization function based on user service
types.
MS first sends a SUSPEND message to BSS over SDCCH when a Class B GPRS MS is about to initiate a voice
service. BSS initiates suspending procedure to SGSN to notify SGSN to stop sending PS paging and downlink
packet data after BSS receives the message.
BSC repeats suspending procedure after sending SUSPEND message to SGSN. If BSC fails to receive SUSPEND
ACK/NACK message from SGSN in BSSGPT3 then BSC repeats the suspending procedure for a maximum of N
times.
BSC stops suspending and notify OMS for N times if there is no answer. N depends on the maximum number
of suspending retries.
This parameter determines whether BSC supports TBF establishment process. TBF flow establishment refers
to while releasing uplink TBF, to determine if new uplink TBF shall be established immediately for CTRL_ACK
field in Packet Control Acknowledgement message.
This parameter indicates whether the BSC supports fast ACK/NACK reporting (FANR) function. If both the
network and MS support this function, the MS can add the DL radio block reception information in the UL
radio block, and the network can add the UL radio block reception information in the DL radio block. In this
way, the MS and network can be informed timely of the reception of UL and DL radio blocks, thus
quickening the re-transmission of UL and DL radio blocks that are not properly received.
This parameter indicates whether to analyze application layer data and desert LLC frames received by the
MS.
When an MS reselects a cell in packet-switched service, the LLC frames of the original cell transfer to the
new cell. This parameter indicates the maximum number of transferred LLC frames in a BSSGP instance. If
the transferred LLC frames exceeds the number, the remaining frames will be discarded.
This is a BSSGP layer parameter used to specify the maximum number of times the BSS retries to obtain the
radio access capability of an MS via the Radio Access Capability Update procedure when the BSS does not
have the information of the access capabilities of MSs. The access capabilities are required by the BSS for
assigning a proper packet channel to each MS when the MS is establishing the uplink TBF.
1. The BSS sends the RADIO ACCESS CAPABILITIES UPDAE message to the SGSN.
2. If the BSS does not receive the RADIO ACCESS CAPABILITIES UPDAE ACK/NACK message from the SGSN,
the BSS re-starts the procedure.
3. The BSC retries the procedure for the number of times specified by UpdateMax, and, if still not receives
returned messages, stops the RADIO ACCESS CAPABILITIES UPDATE procedure and notifies the OMS.
Global process in BSC central module MP uses the timer value. BSS initiates BVC blocking/unblocking
procedure for a point-to-point BVC in case of OAM intervention or device faults. BSC repeats this procedure
if SGSN does not return “BVC BLOCK/UNBLOCK ACK/NACK” messages.
At this time, the number of sending increases by 1. The interval between the messages is the BVC
blocking/unblocking retry time. T1 is timeout
but does not exceed the max number of sending, try to re-send it.
The conditions of timer start, stop, and timeout actions are as follows:
Timer stop: The “BVC BLOCK/UNBLOCK ACK/NACK” message is received from SGSN.
BSS initiates "BVC reset" process when BVC (including PTP BVC and signaling BVC) is required to be reset
(disconnection to connection at Gb interface, and cell is changed from GPRS support to GPRS/EDGE support)
due to certain reason. BSC repeats the procedure if SGSN does not return “BVC RESET ACK/NACK” message.
At this time, the number of sending increases by 1. The interval between the messages is the BVC reset
retry time. T2 is timeout but does not exceed the max number of sending, try to re-send it. T2 is timeout
and exceeds the max number of sending. Change the proper BVC database status to BLOCK.
The conditions of timer start, stop, and timeout actions are as follows:
BSS initiates to suspend SGSN procedure after receiving SUSPEND message from MS BSC repeats the
process if SGSN does not respond suspend ACK/NACK message. At this time, the number of sending times
increases by 1.
The interval between the messages is the suspend retry time. T3 is timeout but does not exceed the max
number of sending, try to re-send
it. T3 is timeout but does not exceed the max number of sending, stop the suspend process.
The conditions of timer start, stop, and timeout actions are as follows:
Timer stop: BSC receives the suspend ACK/NACK message from SGSN.
This parameter monitors BSSGP resuming procedure. Service process in BSC peripheral module MP uses the
timer value. BSS initiates resuming procedure to SGSN when GPRS-attached MS is not in dedicated mode
and BSS uses Notify SGSN to resume GPRS service policy. BSC repeats the process if SGSN does not respond
resume ACK/NACK message. At this time, the number of sending times increases by 1. The interval between
the messages is the resume retry time.
T4 is timeout but does not exceed the max number of sending, try to re-send it. If T4 is timeout and exceeds
the max number of sending,
The conditions of timer start, stop, and timeout actions are as follows:
Timer stop: BSC receives the resume ACK/NACK message from SGSN.
Service process in BSC peripheral module MP uses the timer value. BSC repeats Radio Access Capability
Update procedure after BSS initiates RA_CAPABILITY procedure to SGSN and if SGSN does not return the
“RA_CAPABILITY UPDATE ACK/NACK” message. Also, the number of sending times increases by 1. The
interval between the messages is the retry time for radio access capability update. T5 is timeout but does
not exceed the max number of sending, try to re-send it.
If T5 is timeout and exceeds the max number of sending, update process of radio access capability stops.
The conditions of timer start, stop, and timeout actions are as follows:
Timer start: BSC initiates the radio access capability update process.
Timer stop: BSC receives the radio access capability update ACK/NACK message from SGSN.
While BSS initiates "Create PFC" process to SGSN, if SGSN does not respond "Create PFC ACK/NACK"
message, you should repeat "Create PFC" process. The interval between twice is PFC creation retry time.
The conditions of timer start, stop, and timeout actions are as follows:
When BSS initiates "Modify PFC" process to SGSN, if SGSN does not respond the "Modify PFC ACK/NACK"
message, repeat "Modify PFC" process. The interval between two Modify PFC procedures is the PFC
creation retry time.
Timer stop: The BSC receives the SGSN Modify BSS PFC Ack message.
This parameter is the timer for performing the complete synchronization of 2G cell attributes and the NACC
information.
Timeout action: All 2G cell attributes and NACC information is synchronized to the 3G system.
#N/A
#N/A
#N/A
BSS Function Timer ID
#N/A
#N/A
This parameter is a timer used for supervising the sending of radio information in the location process.
This parameter specifies the waiting time for the completion of an intra-BSC handover.
This parameter is the timer for the services to obtain 2G cell load information from the database.
Timeout action: The service saves the copy of obtained load information in the storage area, and the
synchronization platform synchronizes the information to the 3G system.
This parameter is the mT11 timer used for traffic control when the cell is overloaded. The mT11 timer
coordinates with mT12 to modify the ACCESS CONTROL parameter for the cell configuration, and notifies
the MS via system messages.
During the lifetime of the timer mT11, the BSC does not process the RACH Load Indication message from the
BTS, and the value of this timer must be less than that of timer mT12.
Timer start: When the RACH Load Indication message from the BTS is received.
Timeout action: The BSC resumes processing the RACH Load Indication message.
The value of this timer must be greater than that of timer mT11. The traffic control procedure is described
as follows:
When the network receives the OVERLOAD message for the first time, the system reduces one traffic
control level and starts mT11 and mT12. During mT11, the OVERLOAD message is neglected. If the network
still receives the OVERLOAD message between mT11 and mT12, it reduces one traffic control level again,
and restarts the two timers. If the network does not receive the OVERLOAD message after mT12, it
increases a traffic control level, and restarts mT12.
The different traffic control levels have different ratios of traffic being rejected.
Timer start: When the RACH Load Indication message from the BTS is received.
Timer stop: When the RACH Load Indication message is received again from the BTS after mT11 times out.
Timer for a unilateral conversation check. The timer sets the threshold of the package lost duration. If the
package lost duration exceeds the threshold, a unilateral conversation check is triggered.
#N/A
This parameter determines the time of the BSC in waiting for a paging response after sending a paging
message. The paging mode includes precise paging and common paging.
If the BSC does not receive any response within this time range, the BSC will initiate paging again according
to the paging configuration.
This parameter is the delay release timer while dynamic PDCH channel is converted into TCH channel. The
conditions of timer start, stop, and timeout actions are as follows:
Timer start: All services (including uplink and downlink) on PDCH are released.
Timer start: The destination channel receives the “CHL ACITIVATION ACK” message and sends the “RADIO
AVAILABLE” message to the source channel.
Timer stop: In MS access, the destination channel receives the “ASSIGNMENT COM” or “HANDOVER COM”
message.
This parameter is a timer used to wait for the start of directed retry. The timer is started to wait for queuing,
forced handover, and forced release actions when the cell fails to assign an available channel. When the
timer expires, a directed retry process is initiated.
Stop: An available channel resource is obtained after queuing, forced handover, and forced release.
Timer stop: RANCS instance receives the "CONNECT CONF" sent by RANA instance, or the "CONNECT FAIL"
when RANA fails to establish the link.
This parameter is timer T5, used to supervise modification process of encryption mode, that is, the timer
that waits for MS response after configuring radio encryption mode.
Timer Start: T5 timer starts when BSC receives CIPHER MODE COMMAND message from MSC.
Timer Stop: T5 timer suspends when BSC receives CIPHER MODE COMPLETE message from MS.
Overtime Action: If this timer is overtime, BSC will send BSSAP CIPHER MODE REJECT message to MSC.
Timer start: timer T6 starts when BSC receives the DTAP (SAPI = 3) message from MSC and there is no SAPI3
link.
Timer stop: timer T6 stops when BSC receives the ESTABLISH CONFIRM message from BTS.
Overtime action: When timer T6 expires, the BSSMAP SAPI"n" REJECT message will be sent to MSC.
This parameter is timer rmsT7, used to calculate the protective time that PO responds external handover
completion message.
Timer start: it starts when RANCS sends the HANDOVER REQUIRED message to MSC.
Timer stop: it stops when RANCS instance receives HANDOVER COMMAND response from MSC.
Timeout action: clear the reason of channel request, record the number of outgoing attempts and request
failures, do penalty for target cell, and wait for handover decision to initiate handover.
Timer start: rmsT8 starts after handover command is sent in Serve state while RANCS instance should be
handed over to an external cell.
Timer stop: rmsT8 timer stops if RANCS instance receives HO COMCLEAR CMD (handover success) or UM
HO FAIL (handover failed).
Timer start: T9 starts when RF CHANNEL RELEASE is sent to BTS when RANCS instance is released.
Timer stop: T9 stops when RANCS instance receives RF CHANNEL RELEASE ACKNOWLEDGE response from
BTS.
The BSC sends a PRE-HANDOVER NOTIFICATION message to the BTS, plus the RTD (delay time), so that the
BTS can coordinate with TC to achieve such actions as disabling speech rate modification, exiting TFO.
Afterwards, the BSC sends the handover command to the MS. The RTD is the transmission delay between
BTS and TC, and can be reported to BSC by BTS via the ROUND TRIP DELAY REPORT message. Before
receiving RTD, the BSC uses the default value RtdDefault.
notification message (custom message at the Abis interface) from the BTS.
#N/A
It describes the time of Required process which controls PS handover. After PS Handover Required is sent,
the timer starts. The timer stops after receiving PS Handover Required Ack or Nack. The PS Handover
Required is sent again after expire of timer.
This parameter indicates the timer used by the source BSS for synchronizing CS handover and PS handover
acknowledgment information. The timer start and stop conditions are described as follows:
Timer start: During DTM handover, a HANDOVER REQUIRED message or PS-HANDOVER-REQUIRED PDU
message is sent.
Timer stop: (1) The BSC receives the HANDOVER REQUIRED REJECT message or BSSMAP HANDOVER
COMMAND message from the MSC, and receives the PS-HANDOVER-REQUIRED-ACK PDU message or PS-
HANDOVER-REQUIRED-NACK PDU message from the SGSN.
(2) The BSC receives the BSSMAP HANDOVER COMMAND message that contains the (RR) HANDOVER
COMMAND L3 information, and the MSC chooses to continue CS handover.
(3) The BSC receives the BSSMAP HANDOVER COMMAND message that contains the (RLC/MAC) DTM
HANDOVER COMMAND L3 information, and the MSC chooses to send the DTM handover command to the
MS without waiting for the PS handover acknowledgment.
Timer start: The BSC receives the PS-HANDOVER-REQUEST PDU message that contains CS Indication IE or
the HANDOVER REQUEST message that contains PS Indication IE.
Timer stop: Both HANDOVER REQUEST and PS-HANDOVER-REQUEST PDU messages are received, and PS
Indication and CS Indication IE contain the same information.
This timer indicates the time period for the instant assigning process.
Timer start: The timer starts when BSC sends an IMMEDIATE ASSIGNMENT COMMAND message.
Timer stop: The timer stops when BSC receives the ESTABLISH INDICATION message.
Timeout action: The BSC sends an RF CHANNEL RELEASE message to the BTS.
This timer indicates the time period for intra-BSC handover procedure.
Timer start: The timer starts when BSC sends HANDOVER COMMAND message to MS.
Timer stop: The timer suspends when BSC receives HANDOVER COMPLETE message on a new channel or
HANDOVER FAILURE message on an old channel from MS.
Timeout action: If the timer is timeout, the BSC sends a CLEAR REQUEST message to MSC, with the cause
CAUSE_RI_FAIL (radio interface failure) and the new channel is released.
This timer indicates the time period for assignment procedure and internal handover of a cell.
Timer start: The timer starts when BSC sends RIL3_RR ASSIGNMENT COMMAND message to MS.
Timer stop: The timer stops when BSC receives RIL3_RR ASSIGNMENT COMPLETE message or RIL3_RR
ASSIGNMENT FAILURE message.
Timeout action: For the assignment procedure, the old and new channels are released, related MS
connections are cleared, and a BSSAP ASSIGNMENT FAILURE message is sent to the MSC; for the intra-cell
handover, the BSC sends a CLEAR REQUEST message to the MSC, with the cause CAUSE_RI_FAIL (radio
interface failure).
This timer supervises the channel release process.
Timer start: The timer starts when BSC sends RIL3_RR CHANNEL RELEASE message to MS.
Timer stop: The timer stops when BSC receives RELEASE INDICATION message from BTS (when BTS receives
DISC frame from MS).
Timeout action: If this timer is timeout, BSC will send CHANNEL RELEASE message to MS.
After releasing the UM interface radio link layer, in order to make sure the radio link is disconnected, BSC
sets a period of protection time rmsT3111. Releases the wireless channel and deactivates it after rmsT3111
timer stops.
Timer start: rmsT3111 timer starts when BSC receives RELEASE INDICATION message.
Timeout action: If rmsT3111 timer is timeout, the BSC will send RF CHANNEL RELEASE message to BTS.
This parameter is Timer T3121, indicating the protection time after sending Inter-System to Utran Handover
Command (UM) to
MS.
The timer starts when BSC sends the "inter-system to utran handover command" message to MS.
The timer stops when BSC receives "CLEAR COMMAND" message from MSC or "HANDOVER FAILURE"
message from MS.
Timeout action: The BSC sends “CLEAR REQUEST” message to MSC, with the cause CAUSE_RI_MSG_FAIL
(radio interface message failure).
This parameter is timer T3169. During the packet uplink transmission, if N3101 or N3103 counter stops, BSS
starts the T3169 timer. Network utilizes TFI and USF resources on release when T3169 stops.
Timer Start: T3169 timer starts when the counter N3101 = N3101_MAX or the counter N3103 =
N3103_MAX.
N3101=N3101_MAX or N3103=N3103_MAX indicates that MS does not respond BSC, collects TFI and USF
resource for BSC reuse.
This parameter is timer T3169. The conditions of timer start, stop, and timeout actions are as follows.
Timer start/restart: During the packet downlink transmission, if RLC data block is the final downlink data
block to be transmitted, BSC sends the RLC data block with the Final Block Identifier (FBI) domain as 1. It
contains an effective RRBP domain to initialize the release of downlink TBF. At this time, the network starts
or restarts T3191.
Timer stop: If RLC mode is ACK mode and MS finds that all downlink blocks have been collected, MS sends
the “Packet Downlink Acknowledgement”
message (with FAI domain = 1) through the uplink block specified in RRBP domain. If BSC receives the Packet
Downlink Acknowledgement message
If RLC mode is NACK mode, MS sends the “Packet Control Acknowledgement” message in the uplink block
specified by RRBP field. If BSC receives
the “Packet Control Acknowledgement” message before T3191 expires, T3191 stops.
This parameter the protection time of downlink TBF when the radio link fails or when the cell change leads
to MS failure to respond.
This parameter is the timer for the enhanced DTM CS release. The timer start and stop conditions are
described as follows:
Timer start: The Packet CS Release Indication message is sent by the BSC.
Timer stop: The BSC receives a message indicating that the Packet SI Status message has been completely
received. After RR is released, the Packet SI Status message is a required for keeping PS resources. The BSC
sends a Channel Release message indicating that the PS transmission is kept after CS release.
Timeout action: If the Packet SI Status message is not received after the timer times out, the BSC sends a
Channel Release message indicating that the PS transmission is not kept after CS release.
This parameter is timer T9101, supervising the reception of RLSD.
Timer start condition: T9101 starts when BSC sends the “BSSAP CLEAR COMPLETE” message to MSC.
Timer stop condition: T9101 stops when the RLSD message from MSC is received.
Overtime Action: If this timer is overtime, BSC will send RLSD message to release SCCP connection.
Timer Start: T9103 timer starts when BSC sends CHANNEL ACTIVATION message to BTS.
Timer Stop: T9103 timer suspends when BSC receives CHANNEL ACTIVATION ACK or CHANNEL ACTIVATION
NACK message.
Overtime Action: If this timer is overtime, BSC will send RF CHANNEL RELEASE message to BTS
Timer Start: T9104 timer starts when BSC sends a CLEAR REQUEST message to MSC.
Timer Stop: T9104 timer suspends when BSC receives CLEAR COMMAND message from MSC.
Timeout Action: If this timer is overtime, CLEAR REQUEST message will be resent (four times at the most).
Timer Start: T9105 timer starts when BSC sends BSSAP SCCP_CONNECTION_REQ message to MSC.
Overtime Action: If this timer is overtime, BSC will send CHANNEL RELEASE message to MS.
Timer stop: Receive handover execution message at Ater sent from CS old service instance. Receive
resource release request message at Ater from CS new service instance.
Timeout action: send release command to CS service from Ater and release iTC resource message to iTC.
This parameter is the SCCP connection wait timer at the Ater interface. It is used to wait the SCCP CONNECT
CONFIRM message of iTC.
Timer stop: The SCCP connection number that corresponds to this service is illegal while iTC resource
request from service is handled.
Timeout action: send Disconnect Request to SCCP and terminate Ater service.
It is Ater wait resource release timer at Ater, used to wait for the RESOURCE RELEASE ACKNOWLEDGE
message from iTC.
When the BSC receives the assignment command from the MSC, if the MR is not enough for deciding
whether channels can be assigned in the second sub-cell, the BSC sets this parameter to wait for more MR.
In micro-micro handover control, a delay time value is required (the timer value). Timer Start: relevant timer
starts instantly when a call enters a micro cell. Timer Stop: relevant timer stops when it reaches the set
value. Existing call can use neighboring micro cell in the same layer only when the timer stops. In this way, it
could prevent fast moving mobiles staying in the micro cell layer.
This parameter is T13 timer. It supervises BTS and MS modes modification process. Mode modification
refers to modify channel mode. When there is not SDCCH and FACCH is allocated, new channel is not
allocated after assignment, but modify the modes.
Timer start: When BSC sends the “MODE MODIFY” message to BTS and sends the “CHANNEL MODE
MODIFY” message to MS.
Timer stop: When BSC receives the “MODE MODIFY ACK/NACK” message from BTS and the “CHANNEL
MODE MODIFY” message from MS.
Timeout action: If the timer is overtime, the BSC will send “BSSAP ASSIGNMENT FAILURE” message to MSC.
Connection delay timer. This timer is used to wait for connection finished after sending connection request,
including Abis connection and TC connection.
This parameter is an expiration timer waiting for the response from the opposite end after a RAN
INFORMATION APPLICATION ERROR message is sent by the control end. The timer is started when the
control end sends a RAN INFORMATION APPLICATION ERROR message. It is stopped when a response
message is received from the opposite end. If no response is received before the expiration of the timer, the
control end sends the RAN INFORMATION APPLICATION ERROR message again, or informs the process
failure after sending the message for the specified times.
This parameter is an expiration timer waiting for the response from the opposite end after a RAN
INFORMATION REQUEST message is sent by the control end. The timer is started when the control end
sends a RAN INFORMATION REQUEST message. It is stopped when a response message is received from the
opposite end. If no response is received before the expiration of the timer, the control end sends a RAN
INFORMATION REQUEST message again, or informs the process failure after sending the message for
RIMRetryTimes times.
This parameter indicates the time period for deciding whether a handover in the subcell is ping-pong
handover. If two handovers in a subcell are performed within the time specified by this parameter, a ping-
pong handover between related subcells is recorded in the performance report. The recorded cases include:
the MS performs handover back and forth between two subcells within the same site, or the MS performs
handover back and forth between two subcells between two sites.
This parameter indicates a delay of deactivating an SDCCH.
This parameter indicates a period of releasing a Standalone Dedicated Control Channel (SDCCH).
This timer is used for TRAU frame synchronization. If call release due to TRAU frame synchronization lost is
enabled, a call is released when this timer expires.
It is stopped when the DSP detects that the TRAU frame (voice frame) is synchronized.
This parameter is the IP transmission access control timer at the Abis interface.
This timer indicates the wait time for a handover request from the A interface during a 2G/3G relocation
procedure.
It is started after the BSC sends a radio resource reservation success message to the RNC.
It is stopped when the BSC receives of a handover request from the MSC.
At its expiry, the radio resources are immediately released, and this instance is released.
This parameter describes the response to apply for resource from iTC, to configure this timer wait for iTC
during iBSC handover.
Timer stop:
Timeout action: clear the proper new RANCS process id related to this service process. The new CS service
instance related to this service process does not exist.
This parameter indicates a timer for waiting for the BTS response
after the BSC allocates the dynamic frequencies and informs the
BTS to start using them.
#N/A
When using IP carrier at user plane of interface A, because TC is placed at MGW, CN shall be informed to
replace codec during intra-BSC handover. CN replacement codec is triggered by “HANDOVER PERFORMED”
message. To ensure MSC has received this message and successfully
command MGS to replace codec against obstacles at speech aspect, “HANDOVER PERFORMED ACK”
message is added. This timer is used to wait for “HANDOVER PERFORMED ACK” message from MSC.
Timer start: It starts when BSC sends HANDOVER PERFORMED message to MSC.
Timer stop: It stops when BSC receives HANDOVER PERFORMED ACK message from MSC.
Timeout action: BSC releases call while sending CLEAR REQUEST message to MSC.
This parameter defines the interval of the timer for waiting for internal handover command from MSC after
the service process sends the internal handover request.
#N/A
It describes the time of waiting for resource release after PS handover command is sent.
The timer starts after sending PS Handover Command message. The timer stops when receiving DELETE BSS
PFC from SGSN or handover finish message from destination cell. The PS Handover Cancel message is sent
to SGSN after expire of timer.
This parameter indicates a timer for waiting for the MSC response
after the BSC initiates a rerouting procedure and attempts to access
the MSC during an MOCN implementation.
This parameter indicates a timer for waiting for the SGSN response
after the BSC initiates a rerouting procedure and attempts to access
the MSC during an MOCN implementation.
This timer indicates the wait time before the BSC receives a Relocation Commit message from the RNC
during a relocation procedure via the Iur-g interface that is configured between 2G and 3G networks.
It is stopped when the BSC receives a Relocation Commit message via the Iur-g interface from the RNC.
At its expiry, the relocation instance and the corresponding allocated resources are released.
#N/A
#N/A
#N/A
#N/A
Global Reserved Parameter 1
Global Reserved Parameter 10
Global Reserved Parameter 11
Global Reserved Parameter 12
Global Reserved Parameter 13
Global Reserved Parameter 14
Global Reserved Parameter 15
Global Reserved Parameter 16
Global Reserved Parameter 17
Global Reserved Parameter 18
Global Reserved Parameter 19
Global Reserved Parameter 2
Global Reserved Parameter 20
Global Reserved Parameter 3
Global Reserved Parameter 4
Global Reserved Parameter 5
Global Reserved Parameter 6
Global Reserved Parameter 7
Global Reserved Parameter 8
Global Reserved Parameter 9
#N/A
With this parameter enabled, if the BSC receives a DISCONNECT or RELEASE message and then a handover
occurs, the BSC will not send a handover command to the BS to avoid MS release delay. The BSC does not
determine whether to hand over in the time period set by the parameter ForbidRelHoMargin when the BSC
receives a DISCONNECT or RELEASE message. This parameter is used to decrease the call drop rate during a
release without impairing the handover success rate.
This parameter specifies a time period for handover disabling during a release.
BSC Handover Control ID
This parameter indicates whether queuing is allowed during inter-BSC outgoing handovers, that is, whether
queuing is allowed according to the Queuing Indicator parameter in the Handover Required message.
This parameter determines whether MSC should respond messages for BSC outgoing handover. If the
parameter is set to 1, the HANDOVER REQUIRE message contains Response Request, and the MSC, upon
handover failure, will return the Response Request Reject message to the BSC. If the parameter is set to 0,
the MSC will not return the message to the BSC upon handover failure, and the BSC knows the handover
fails when the timer T7 times out.
This parameter enables or disables the detection on handover command loss due to Abis congestion to
avoid handover call drop.
This parameter decides whether to allows the BSC to perform intra-cell handovers.
#N/A
#N/A
If the parameter is set to 1 (Yes), the BSC adds Synchronization Indication IE to the sent Handover Command
message and sets ROT to 1 for both synchronized and asynchronized handovers. In this case, the MS adds
Mobile Observed Time Difference in the sent Handover Complete message, indicating the clock reference
difference between two handover cells.
This parameter decides whether to allow an assignment to request a channel from other cells in the BSC
when the assignment fails to obtain a channel.
This parameter indicates whether to allow the inter-cell (with different network IDs) handover. If it is set to
"NO", The adjacent cell to which handover (or reselection) performed must have the sane network ID
(MCC/MNC) as this cell.
the policy of choosing speech version in 3GPP IPA BSC handover
#N/A
This parameter specifies the handover method employed by CS services when performing intra-BSC
Handover in the case of 3GPP IPA.
By default, compatible versions are used before and after the internal handover, and the handover is
performed conforming to the protocol.
1: The services use the handover procedure supported by the MSC for handover from AMR-HR to AMR-FR
using SET 1.
#N/A
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of downlink level handover on the SDCCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of downlink level handover on the TCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of downlink quality handover on the SDCCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of downlink quality handover on the TCH.
This parameter is used to control whether the N value, P value, or average PBGT value is applied for
neighbor cell selection in the case of PBGT handover on the SDCCH.
This parameter is used to control whether the N value, P value, or average PBGT value is applied for
neighbor cell selection in the case of PBGT handover on the TCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of uplink level handover on the SDCCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of uplink level handover on the TCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of uplink quality handover on the SDCCH.
This parameter is used to control whether the N value, P value, or average level value is applied for
neighbor cell selection in the case of uplink quality handover on the TCH.
In an outgoing handover, this parameter specifies the contents in the Old BSS to New BSS Information
contained in the HANDOVER REQUIRED message.
The four items Synchronization Indication, Cipher Mode Setting, Multi-Rate configuration, and Frequency
List are controlled by the upper four bits.
BIT5: Whether the hopping frequency is set with the FreqList format. 0: NO, 1: YES
BIT7: Whether the HANDOVER COMMAND contains the Cipher information parameter. 0: NO, 1: YES
#N/A
This parameter decides whether to allow an assignment to request a channel from the cells outside the BSC
when the assignment fails to obtain a channel.
This parameter is a timer used to determine whether a handover is a ping-pong handover. The timer is
started when an MS performs handover from a cell. If the MS performs handover to the source cell, and the
interval between two handovers is shorter than the value of this parameter, this handover is recorded as a
ping-pong handover.
#N/A
#N/A
#N/A
This parameter specifies whether the A+B solution for TD handover is enabled.
With the parameter HoCmdLostOpt enabled, when the time configured by this parameter expires, the BSC
starts to check whether the call is resumed. If yes, the handover command is considered to be lost. This
parameter should be set greater than T200×N200; otherwise, the BSC cannot determine accurately whether
the handover command is lost.
This parameter specifies the duration for the RRM module to wait
for an IFTA check response sent from other RRM modules after
allocating an IFTA channel and initiating a check.
When the IFTA function is enabled, the BSC needs to receive
a measurement report with neighbor cell measurement data to
estimate interference before allocating TCH channels. However, in
some cases, if the BSC does not receive a measurement report
with neighbor cell measurement data after receiving an assignment
command from the MSC, it needs to wait for a certain time to
receive the measurement report. The BSC can be set to wait for
several times. This parameter specifies how long the BSC waits in
each time.
This parameter determines the maximum retry times of CS service paging (exact paging excluded).
When the first paging is not responded, the system can initiate multiple paging operations according to the
value of this parameter.
When the first paging is not responded for the CS service, the core network may initiate paging for another
time. This parameter determines whether the exact paging policy is applied for subsequent paging
operations of the CS service in the core network.
BSC Precise Paging Configuration ID
This parameter determines the switch of BSC exact paging. This function indicates that the system performs
paging in the cells for exact paging. If the system does not reach any subscriber, it performs paging within
the range required by the core network. The exact paging cells include the Visit Paging Cell (VPC) and Home
Paging Cell (HPC). The VPC indicates a cell around the cell where the last service exists. It can be a handover
or reselection adjacent cell, or can be configured additionally. The HPC indicates a group of cells calculated
based on the cells where latest services are triggered.
If this parameter is set to "No", only the VPC is used for exact paging. If this parameter is set to "Yes", both
the VPC and HPC are used for exact paging.
This parameter determines whether the exact paging of PS service covers the cells out of the paging range
of core network. The paging of PS service is usually applied for routing cells. However, some VPCs and HPCs
may not in these routing cells.
This parameter determines the maximum retry times of PS service paging (exact paging excluded).
When the first paging is not responded, the system can initiate multiple paging operations according to the
value of this parameter.
When the first paging is not responded for the PS service, the core network may initiate paging for another
time. This parameter determines whether the exact paging policy is applied for subsequent paging
operations of the PS service in the core network.
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
This parameter is used at the MS side. It belongs to GPRS Cell Options
IE and is broadcast to the MS in the SI13 message on BCCH and
in the PSI13 message on PSI13, indicating whether to use the 8-bit or
11-bit access burst in PRACH, PTCCH/U, and the PACKET CONTROL
ACKNOWLEDGEMENT messages.
TLV is the transmission format at Abis interface. T, L, and V respectively represent attribute, length, and
value.
This parameter sets the duration that the super site triggers the handover towards satellite link after the
terrestrial link is broken. This parameter is supported from version 6.20.61.
Site Equipment Object ID
Site Equipment Object ID
This parameter sets the site ID.
This parameter sets the duration that the super site triggers the handover towards terrestrial link after the
terrestrial link becomes normal. It is valid in the automatic handover mode.
The super site supports two switchover modes from the satellite link to the terrestrial link: Automatic
switchover and manual switchover.
This parameter is a functional switch that determines whether the BSC can obtain the information of Iur-g
capacity and load from the RNC. The original Iur-g functional switch still takes effect. It controls whether the
RNC obtains the capacity and load information from the BSC.
The value 0 indicates that the BSC does not obtain data from the RNC.
The value 1 indicates that the BSC obtains data from the RNC.
This parameter determines the delay time of reporting based on event E. The system reports or stops
reporting measurement reports after this delay time when the corresponding conditions are met.
This parameter specifies the threshold 1 for reporting Load with the Event E method. The load is reported
when the Load value exceeds this threshold.
This parameter specifies the threshold 2 for reporting Load with the Event E method. The load is reported
when the Load value drops below this threshold.
This parameter specifies the threshold 1 for reporting NRT Load with the Event E method. The load is
reported when the NRT Load value exceeds this threshold.
This parameter specifies the threshold 2 for reporting NRT Load with the Event E method. The load is
reported when the NRT Load value drops below this threshold.
This parameter specifies the threshold 1 for reporting RT Load with the Event E method. The load is
reported when the RT Load value exceeds this threshold.
This parameter specifies the threshold 2 for reporting RT Load with the Event E method. The load is
reported when the RT Load value drops below this threshold
2: Load
6: RT Load
7: NRT Load
This parameter indicates the upper overload threshold of non-real-time services. When the load of non-
real-time services is equal to or higher than the threshold but lower than NRTThs_0, it is regarded that the
cell is overloaded with non-real-time services. Non-real-time services refer to PS services.
The load is calculated by dividing the number of occupied PDCHs (including dynamic PDCHs and static
PDCHs) by the number of available PDCHs.
This parameter indicates the lower overload threshold of non-real-time services. When the load of non-real-
time services is equal to or higher than the threshold but lower than NRTThs_1, it is regarded that the cell is
moderately loaded with non-real-time services. Otherwise, the load of non-real-time services is regarded
low. Non-real-time services refer to PS services.
The load is calculated by dividing the number of occupied PDCHs (including dynamic PDCHs and static
PDCHs) by the number of available PDCHs
This parameter indicates the overload threshold of non-real-time services. When the load of non-real-time
services is equal to or higher than the threshold, it is considered that the cell is overloaded with non-real-
time services. Non-real-time services refer to PS services. The load is calculated by dividing the number of
occupied PDCHs (including dynamic PDCHs and static PDCHs) by the number of available PDCHs.
1 On Demand
2 Periodic
7 Event E
This parameter indicates the unit of load report period when common measurement is periodical.
1: 10 ms
2: 1 Min
This parameter indicates the load report period when common measurement is periodical.
(1) The subscriber whose services are forcibly handed over fails to request for channels in its adjacent cells.
(3) The subscriber whose services are forcibly handed over fails to release the channel in the time specified
by the parameter ForceHoWait.
This parameter indicates the maximum number of attempted forced releases when there are no available
channels in the cell during an assignment. After a forced release is started, if the user fails to release the
channel in ForceRelWait and the maximum number is not reached, more forced releases can be attempted.
This parameter decides the waiting time before the next target search if the forced handover target cannot
be found and there are no available channels in the cell during an assignment.
Start: No target is found after a forced handover is initiated during the assignment.
At expiry: Another search for the forced handover target will be done.
This parameter decides the waiting time before the next target search if the forced release target cannot be
found and there are no available channels in the cell during an assignment.
Start: No target is found after a forced release is initiated during the assignment.
At expiry: Another search for the forced release target will be done.
If there are no available channels in the cell during an assignment and both forced handover and forced
release are allowed, forced handovers will be attempted first. If no channel is accessed, no more forced
handovers will be done after the timer expires. Instead, forced releases will be attempted. This parameter
decides when to attempt such forced releases.
Start: The assignment triggers a preemption, that is, attempted forced handovers or releases begin.
This parameter specifies the preemption strategy in the assignment process when there are no available
channels.
Its value corresponds to 15 levels of priority (1 to 15) which are defined by the parameter "Priority" in the
Assignment Command message or Handover Request message from the CN.
eMLPP ID
eMLPP User Priority Configuration ID
This parameter indicates the maximum number of attempted forced releases when there are no available
channels in the cell during a handover. After a forced handover is started, if one of the following three
events happens and the maximum number is not reached, more forced handovers can be attempted:
(1) The user whose services are handed over forcedly fails to request for channels in its adjacent cells.
(3) The user whose services are handed over forcedly fails to release the channel in ForceHoWait.
This parameter indicates the maximum number of attempted forced releases when there are no available
channels in the cell during a handover. After a forced release is started, if the user fails to release the
channel in ForceRelWait and the maximum number is not reached, more forced releases can be attempted.
This parameter decides the waiting time before the next target search if the forced handover target cannot
be found and there are no available channels in the cell during a handover.
At expiry: Another search for the forced handover target will be done.
This parameter decides the waiting time before the next target search if the forced release target cannot be
found and there are no available channels in the cell during a handover.
Start: No target is found after a forced release is initiated during the handover.
At expiry: Another search for the forced release target will be done.
If there are no available channels in the cell during a handover and both forced handover and forced release
are allowed, forced handovers will be attempted first. If no channel is accessed, no more forced handovers
will be done after the timer expires. Instead, forced releases will be attempted. This parameter decides
when to attempt such forced releases.
This parameter decides the time period in which preemptions (forced handovers or releases) can be
initiated when there are no available channels in the cell during a handover. If the duration expires, services
must queue (The queuing period includes the preemption time) and no more forced handovers or releases
will be initiated.
Start: The handover triggers a preemption, that is, attempted forced handovers or releases begin.
This parameter specifies the preemption strategy in handovers when there are no available channels.
Its value corresponds to 15 levels of priority (1 to 15) which are defined by the parameter "Priority" in the
Assignment Command message or Handover Request message from the CN.
This parameter decides the maximum time to wait in queue for resources when there are no available
channels in the cell during an assignment. If no resource is obtained during the time period, the assignment
fails.
Start: No channel is available for the assignment and the assignment queues.
At expiry: The channel allocation will fail and an assignment failure message will be sent to the MSC.
This parameter decides the maximum time to wait in queue for resources when there are no available
channels in the cell during a handover. If no resource is obtained during the time period, the handover fails.
Start: No channel is available for the handover and the handover queues.
Network Resource Identifier (NRI). Each iBSC can be configured with at most 16 SGSN neighbor offices, and
each SGSN neighboroffice has an NRI. This parameter is consistent with that at the CN side.
To support the transmission bandwidth adjustment function based on the SLA for IP transmission paths, this
parameter sets the percentage of reducing bandwidth when the actual packet loss ratio is higher than the
reference value of the packet loss ratio.
To support the transmission bandwidth adjustment function based on the SLA for IP transmission paths, this
parameter sets the percentage of increasing bandwidth when the actual packet loss ratio is lower than the
reference value of the packet loss ratio.
To support the transmission bandwidth adjustment function based on the SLA for IP transmission paths, this
parameter sets the accelerating factor in the slow start algorithm. The accelerating factor affects
BandIncPer by improving the bandwidth increase rate according to the decrease rate of the packet loss
ratio. In this way, the problem that the bandwidth increase rate is low and the adjustment effect is too small
is solved.
IP SLA Bandwidth Manager Object ID
To support the transmission bandwidth adjustment function based on the SLA for IP transmission paths, a
bandwidth adjustment switch is configured for the IP transmission path of each adjacent interface. When
the switch is turned on and if the packet loss ratio is higher than the reference value of the packet loss ratio,
the RNC dynamically reduces the effective bandwidth of the transmission path to limit the number of
subsequent new services and to limit the traffic of non–real-time services so that the quality of existing
services is ensured. If the packet loss ratio is lower than the reference value of the packet loss ratio, the RNC
dynamically increases the effective bandwidth of the transmission path for more new services and to
properly increase the traffic of non–real-time services so that the bandwidth waste can be avoided.
This parameter indicates the reference value of the packet loss ratio. When the actual packet loss ratio is
higher than the reference value, the effective bandwidth should be reduced.
To support the transmission bandwidth adjustment function based on the SLA for IP transmission paths, this
parameter sets a transmission path’s minimum effective receiving bandwidth.
This parameter sets the signaling weight. Signaling weight determines the frequency of the local endpoint
being selected during signaling transmission.
For the local endpoint, this parameter determines the frequency of the local endpoint being selected as the
source endpoint during the process of sending signaling from the local endpoint to the opposite end. In
dynamic configuration, the weight is sent to the opposite end (SGSN), and SGSN uses the weight to
determine the frequency of the opposite endpoint being selected as the destination endpoint.
During the process of sending signaling from the local end to the opposite end, the following two factors are
considered in determining the frequency of the opposite endpoint being selected as the destination
endpoint: the opposite endpoint weight configured in static configuration, the opposite endpoint weight
acquired in dynamic configuration.
For the local endpoint, this parameter determines the frequency of the local endpoint being selected as the
source endpoint during the process of sending signaling from the local endpoint to the opposite end. In
dynamic configuration, the weight is sent to the opposite end (SGSN), and SGSN uses the weight to
determine the frequency of the opposite endpoint being selected as the destination endpoint.
During the process of sending signaling from the local end to the opposite end, the following two factors are
considered in determining the frequency of the opposite endpoint being selected as the destination
endpoint: the opposite endpoint weight configured in static configuration, the opposite endpoint weight
acquired in dynamic configuration.
This parameter indicates the timeout type of a port. It decides the speed to determine the timeout of a
member link. For more information, refer to IEEE 802.3ad. Options include:
0-Long timeout
1-Short timeout
Location Area ID
This parameter indicates whether the IMSI (IMSI Attach/Detach Allowed,
ATT) attach/detach. IMSI detach occur when MS reports switch-off or
when the SIM card is taken out from the MS.
The network (normally VLR) marks "Detach" flag in subscriber
information table. Such procedure assists the network to prevent
unnecessary paging broadcast message to MS. Accordingly, the IMSI
Attach process means that the MS reports entering the working status
to the network or the MS checks after the SIM card is re-inserted into
the MS whether the LAI where the MS is located is consistent with
the original one saved. If yes, the IMSI Attach process will be started;
otherwise, the location updating process will be started instead.
The network (normally VLR) marks "Attach" flag in subscriber information
table after the notification about IMSI attach or location area update
has been received.
This parameter is included in "Control channel information" and is used
for RIL3_RR SYSTEM INFORMATION TYPE3 message.
Each GSM PLMN is divided into many location areas (LAs) in order to determine the MS location, the
location area code identifiesthe different location areas. LAC comes under LAI (LAI = MCC + MNC + LAC).
One location area contains multiple cells.
Location update results from two major causes in GSM system. One is when MS changes from old LAC to
new LAC and the second is when the network notifies MS for periodic location update.
Network controls the location time interval and depends upon T3212 timer. Network broadcasts to all MSs
in the cell by RIL3_RR SYSTEM INFORMATION TYPE3 message. T3212 timer is one of the system control
parameters.
The setting of this parameter will affect the overall service performance and utilization rate of radio
resources of the network. For the area with higher traffic, the period could be bigger (for example 16 or 20
hours, even 25 hours); for the area with ordinary traffic, the value of T3212 could be smaller (for example 3
or 6 hours); for the area with extreme overload traffic, it is recommended to set T3212 as 0.
MSC load sharing proportion. When users configure each MSC neighbor office, they should also configure
the MSC load sharingproportion. BSC uses this parameter for selecting MSC for unknown NRI and NULL-NRI.
Whether A-interface user-plane speech and data packets support all-IP transmission.
Network Resource Identifier (NRI). Each iBSC can be configured with at most 16 MSC neighbor offices, and
each MSC neighboroffice has an NRI. This parameter is consistent with that at the CN side.
MSC Office Object ID
MSC ID, only effective at iBSC side. FlexA allows iBSC to connect 16 MSCs.
Network Resource Identifier (NRI). Each iBSC can be configured with at most 16 MSC neighbor offices, and
each MSC neighboroffice has an NRI. This parameter is consistent with that at the CN side.
Whether A-interface user-plane speech and data packets support PCM over IP transmission.
Whether A-interface user-plane speech and data packets support PCM over TDM transmission.
#N/A
Number of signaling point office pollings. It is used for message load sharing between different signaling
point offices underthe same MSC.
Nri Configuration Object ID
Nri Configuration Object ID
MSC/SGSN NRI
Pcu process Sub Unit Object ID
Pcu process Sub Unit Object ID
Routing Area ID
Routing Area ID
RAC is a composition part of Routing Area Identity (RAI). RAI defines the GPRS serving cell identification.
GPRS system dividesthe location area (LAs) to several routing areas (RAs) using RAI (MCC+MNC+LAC+RAC).
Routing Area (RA) distribution, similarto GSM system, uses the location area to manage a group of cells. MS
initiates ‘Routing area update’ procedure in cell reselectionmode if new RAI differs from old RAI during cell
reselection.
SGSN knows the routing area information of the MS in the standby status. Then, when the network has
packet data or circuitdata to transmit, it will page the MS in that routing area. RAI cannot span more than
one SGSN.
This parameter specifies a channel busy threshold for urgent release of baseband resources. When a cell
fails to request baseband resources, the BSC searches for cells whose radio channel busy ratios are less than
this threshold, and then selects a TRX to release some baseband resources after locating such cells.
This parameter specifies a channel busy threshold for urgent allocation of baseband resources. When the
radio channel busy ratio of a cell is greater than this threshold due to sudden traffic increase, specific TRXs
are selected to allocate more baseband resources.
This parameter specifies a traffic threshold for baseband resource release. The BSC selects specific TRXs to
release baseband resources when detecting in a measurement report that the traffic in a cell is less than this
threshold
This parameter specifies a traffic threshold for baseband resource allocation. The BSC selects specific TRXs
to allocate baseband resources when detecting in a measurement report that the traffic in a cell is greater
than this threshold.
Site ID
Site baseband share Configuration ID
This parameter represents the duration of the AB-based clock synchronous measurement statistics. The unit
is minute.
This parameter represents the start time of the AB-based clock synchronization measurement statistics. The
unit is hour.
This parameter represents the start time of the AB-based clock synchronous measurement statistics. The
unit is minute.
This parameter indicates whether to enable the AB-based synchronization measurement on Sunday.
This parameter indicates whether to enable the AB-based synchronization measurement on Monday.
This parameter indicates whether to enable the AB-based synchronization measurement on Tuesday.
This parameter indicates whether to enable the AB-based synchronization measurement on Wednesday.
This parameter indicates whether to enable the AB-based synchronization measurement on Thursday.
This parameter indicates whether to enable the AB-based synchronization measurement on Friday.
This parameter indicates whether to enable the AB-based synchronization measurement on Saturday.
This parameter represents the duration of the MTD-based clock synchronization measurement statistics.
The unit is minute.
This parameter represents the start time of the MTD-based clock synchronization measurement statistics.
The unit is hour.
This parameter represents the start time of the MTD-based clock synchronization measurement statistics.
The unit is minute.
This parameter indicates whether to enable the MTD-based synchronization measurement on Sunday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Monday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Tuesday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Wednesday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Thursday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Friday.
This parameter indicates whether to enable the MTD-based synchronization measurement on Saturday.
If this parameter is enabled, when the remaining time of the current adjustment period is not enough for
lossless adjustment, the system directly performs lossy adjustment; otherwise, lossy adjustment will not be
implemented.
BSC Um Soft Synchronous Configuration ID
This parameter indicates whether inter-BSC clock software synchronous measurement is supported.
Sets whether to adjust the frame number when the initial adjustment command is executed.
Enables/Disables the cycle adjustment function. After the initial adjustment on a site, the cycle adjustment
needs to be enabled because the clock deviation accumulates.
This parameter sets the receive level difference threshold between a neighbor cell and the serving cell. A
neighbor cell can be used as a reference neighbor cell if N of P differences are less than the threshold.
This parameter represents the start time of clock synchronization adjustment. The unit is hour.
This parameter represents the start time of clock synchronization adjustment. The unit is minute.
This parameter represents the clock synchronization adjustment duration. The unit is minute.
This parameter indicates whether to enable clock synchronization adjustment on Sunday.
This parameter indicates whether to enable clock synchronization adjustment on Monday.
This parameter indicates whether to enable clock synchronization adjustment on Tuesday.
This parameter indicates whether to enable clock synchronization adjustment on Wednesday.
This parameter indicates whether to enable clock synchronization adjustment on Thursday.
This parameter indicates whether to enable clock synchronization adjustment on Friday.
This parameter indicates whether to enable clock synchronization adjustment on Saturday.
This parameter determines whether to use the AB-based clock offset information collection strategy for the
Um software synchronization function.
This parameter determines whether to use the MTB-based clock offset information collection strategy for
the Um software synchronization function.
The software synchronous measurement decision is started only when the serving cell level reaches the
synchronous measurement switchover threshold.
This parameter sets the maximum number of measured carriers allowed for each base station.
Enables/Disables the Um soft synchronous function.
0
#N/A
0
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
0
0
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
Impact on Network
N/A
No
No
Null
N/A
Null
Null
No
No
No
No
Null
Null
No
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
No
None
No
No
No
Service interrupt
Yes/Service interrupt
Yes/Service interrupt
Service interrupt
No
No
No
No
No
No
No
Null
No
No
No
N/A
Null
Null
Null
Service interrupt
None
N/A
Null
N/A
Null
No
Null
Null
Null
None
None
None
None
None
None
None
None
None
None
None
None
None
None
No
No
No
No
Null
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
amrOwfsThresholds1+
amrOwfsHysteresis1≤amrO
wfsThresholds2+
amrOwfsHysteresis2
The hysteresis for changing
AMROWFS mode includes
two factors, which are
represented by two
parameters:
amrOwfsHysteresis1 and
amrOwfsHysteresis2.
amrOwfsThresholds1+
amrOwfsHysteresis1≤amrO
wfsThresholds2+
amrOwfsHysteresis2
No
No
(1)
amrOwfsThresholds1≤amrO
wfsThresholds2
(2) amrOwfsThresholds1+
amrOwfsHysteresis1≤
amrOwfsThresholds2+
amrOwfsHysteresis2
There are two thresholds for
changing AMROWFS mode,
which are represented by
two parameters:
amrOwfsThresholds1 and
amrOwfsThresholds2.
(1)
amrOwfsThresholds1≤amrO
wfsThresholds2
(2) amrOwfsThresholds1+
amrOwfsHysteresis1≤
amrOwfsThresholds2+
amrOwfsHysteresis2
No
No
amrOwhsThresholds1+
amrOwhsHysteresis1≤amrO
whsThresholds2+
amrOwhsHysteresis2
The hysteresis for changing
AMROWHS mode includes
two factors, which are
represented by two
parameters:
amrOwhsHysteresis1 and
amrOwhsHysteresis2.
amrOwhsThresholds1+
amrOwhsHysteresis1≤amrO
whsThresholds2+
amrOwhsHysteresis2
(1)
amrOwhsThresholds1≤amrO
whsThresholds2
(2) amrOwhsThresholds1+
amrOwhsHysteresis1≤amrO
whsThresholds2+
amrOwhsHysteresis2
There are two thresholds for
changing AMROWHS mode,
which are represented by
two parameters:
amrOwhsThresholds1 and
amrOwhsThresholds2.
(1)
amrOwhsThresholds1≤amrO
whsThresholds2
(2) amrOwhsThresholds1+
amrOwhsHysteresis1≤amrO
whsThresholds2+
amrOwhsHysteresis2
amrWfsThresholds1+
amrWfsHysteresis1≤amrWfs
Thresholds2+
amrWfsHysteresis2≤amrWfs
Thresholds3+
amrWfsHysteresis3≤amrWfs
Thresholds4+
amrWfsHysteresis4
The hysteresis for changing
AMRWFS mode includes
four factors, which are
represented by four
parameters:
amrWfsHysteresis1,
amrWfsHysteresis2,
amrWfsHysteresis3, and
amrWfsHysteresis4.
amrWfsThresholds1+
amrWfsHysteresis1≤amrWfs
Thresholds2+
amrWfsHysteresis2≤amrWfs
Thresholds3+
amrWfsHysteresis3≤amrWfs
Thresholds4+
amrWfsHysteresis4
There are four thresholds for
changing AMRWFS mode,
which are represented by
four parameters:
amrWfsThresholds1,
amrWfsThresholds2,
amrWfsThresholds3, and
amrWfsThresholds4.
(1)
amrWfsThresholds1≤amrWf
sThresholds2≤amrWfsThres
holds3≤amrWfsThresholds4
(2) amrWfsThresholds1+
amrWfsHysteresis1≤amrWfs
Thresholds2+
amrWfsHysteresis2≤amrWfs
Thresholds3+
amrWfsHysteresis3≤amrWfs
Thresholds4+
amrWfsHysteresis4
There are four thresholds for
changing AMRWFS mode,
which are represented by
four parameters:
amrWfsThresholds1,
amrWfsThresholds2,
amrWfsThresholds3, and
amrWfsThresholds4.
(1)
amrWfsThresholds1≤amrWf
sThresholds2≤amrWfsThres
holds3≤amrWfsThresholds4
(2) amrWfsThresholds1+
amrWfsHysteresis1≤amrWfs
Thresholds2+
amrWfsHysteresis2≤amrWfs
Thresholds3+
amrWfsHysteresis3≤amrWfs
Thresholds4+
amrWfsHysteresis4
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
No
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
No
#N/A
Yes
No
#N/A
Yes
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
No
No
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
#N/A
No
No
#N/A
#N/A
#N/A
#N/A
No
No
No
No
No
No
Yes
No
Yes
Yes
No
No
No
No
#N/A
#N/A
#N/A
No
#N/A
No
No
No
No
No
None
No
No
No
No
No
No
No
No
#N/A
#N/A
No
#N/A
#N/A
No
No
No
No
No
No
No
No
No
No
#N/A
None
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
Full-rate channels can be
converted to half-rate
channels only when the
BSC-level and cell-level
DynaHREnable is enabled.
No
#N/A
#N/A
#N/A
No
No
No
Yes
No
No
No
No
No
#N/A
No
N/A
N/A
#N/A
#N/A
No
No
#N/A
#N/A
No
No
No
No
#N/A
#N/A
#N/A
#N/A
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
No
No
None
No
#N/A
No
No
No
No
No
No
No
No
None
No
#N/A
No
#N/A
No
No
No
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
#N/A
#N/A
#N/A
No
No
No
No
#N/A
#N/A
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
#N/A
No
No
No
No
No
#N/A
No
None
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
This parameter is valid when
the Support Enhanced DTM
parameter of BSC-level is
enabled
Yes
Yes
No
No
No
No
No
No
No
No
None
No
No
No
No
No
No
#N/A
#N/A
#N/A
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
No
None
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
No
No
No
#N/A
#N/A
#N/A
No
#N/A
#N/A
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
No
#N/A
No
No
No
No
#N/A
#N/A
#N/A
#N/A
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
None
None
No
None
None
None
None
#N/A
#N/A
No
None
None
#N/A
None
#N/A
None
None
None
None
None
None
None
None
None
None
None
#N/A
None
#N/A
#N/A
#N/A
None
None
Yes
No
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
No
Yes
Yes
No
No
Yes
Yes
Yes
Yes
No
Yes
No
Yes
#N/A
Yes
Yes
No
No
No
Yes
No
No
No
No
Yes
Yes
Yes
Yes
#N/A
None
None
None
No
None
None
None
None
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
None
None
None
N/A
N/A
N/A
None
None
None
#N/A
None
None
None
None
None
None
None
N/A
N/A
N/A
N/A
None
No
None
No
None
None
None
None
None
None
None
None
None
None
None
No
None
No
N/A
N/A
N/A
N/A
#N/A
N/A
N/A
N/A
N/A
None
Null
#N/A
Null
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
#N/A
No
None
N/A
N/A
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
None
N/A
None
MinTxBitRate<=TxBitRate;
MinRxBitRate<=RxBitRate
Null
None
N/A
N/A
N/A
N/A
None
None
N/A
N/A
N/A
N/A
None
None
None
None
None
N/A
N/A
N/A
N/A
N/A
None
None
None
None
None
None
None
N/A
Null
None
#N/A
None
None
#N/A
None
#N/A
#N/A
None
No
None
No
None
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
No
No
No
No
No
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
#N/A
N/A
N/A
N/A
N/A
N/A
N/A
No
No
Yes
None
None
None
None
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
None
#N/A
None
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
None
None
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
ZTE 2G BSC Parameter Level Guideline | 2018 333
INTRODUCTION
PARAMETER CATEGORIZATION
amrOwfsThresholds1+
amrOwfsHysteresis1≤amrOwfsThreshol
ds2+amrOwfsHysteresis2
amrOwfsThresholds1+
amrOwfsHysteresis1≤amrOwfsThreshol
ds2+amrOwfsHysteresis2
(2) amrOwfsThresholds1+
amrOwfsHysteresis1≤
amrOwfsThresholds2+
amrOwfsHysteresis2
(2) amrOwfsThresholds1+
amrOwfsHysteresis1≤
amrOwfsThresholds2+
amrOwfsHysteresis2
amrOwhsThresholds1+
amrOwhsHysteresis1≤amrOwhsThreshol
ds2+amrOwhsHysteresis2
amrOwhsThresholds1+
amrOwhsHysteresis1≤amrOwhsThreshol
ds2+amrOwhsHysteresis2
(2) amrOwhsThresholds1+
amrOwhsHysteresis1≤amrOwhsThreshol
ds2+amrOwhsHysteresis2
(2) amrOwhsThresholds1+
amrOwhsHysteresis1≤amrOwhsThreshol
ds2+amrOwhsHysteresis2
amrWfsThresholds1+
amrWfsHysteresis1≤amrWfsThresholds2
+
amrWfsHysteresis2≤amrWfsThresholds3
+
amrWfsHysteresis3≤amrWfsThresholds4
+amrWfsHysteresis4
(1)
GBssAmr amrWfsThresholds1 6 Critical amrWfsThresholds1≤amrWfsThresholds
2≤amrWfsThresholds3≤amrWfsThreshol
ds4
(2) amrWfsThresholds1+
amrWfsHysteresis1≤amrWfsThresholds2
+
amrWfsHysteresis2≤amrWfsThresholds3
+
amrWfsHysteresis3≤amrWfsThresholds4
+amrWfsHysteresis4
(1)
GBssAmr amrWfsThresholds2 6 Critical amrWfsThresholds1≤amrWfsThresholds
2≤amrWfsThresholds3≤amrWfsThreshol
ds4
(2) amrWfsThresholds1+
amrWfsHysteresis1≤amrWfsThresholds2
+
amrWfsHysteresis2≤amrWfsThresholds3
+
amrWfsHysteresis3≤amrWfsThresholds4
+amrWfsHysteresis4
MinRxBitRate<=RxBitRate