consistency check rules
DESCRIPTION
CC Check ruleTRANSCRIPT
FREEOPEN INFORMATIONTMOS User Guide 1 (95)
MO/ETX/A/PO qtxsock 1999-11-30 B 1/1553-APR 102 56/1A Uen
/
Uppgjord — Prepared Datum — Date Rev Dokumentnr — Document no
Godkänd — Approved Kontr — Checked Tillhör/referens — File/reference
E
Consistency Check Rules
Copyright
Disclaimer
Trademarks
Contents Page
1 Introduction 21.1 Prerequisites 21.2 User Interface Conventions 21.3 Typographic Conventions 21.4 General Information 3
2 Consistency Check Rules Overview 4
3 Performed Consistency Checks 53.1 Checks on the Area Level 53.2 Checks on the MSC Level 63.3 Checks on the BSC Level 73.4 Checks on the Internal Cell Level 8
4 Consistency Check Rules 94.1 List of Consistency Check Rules 94.2 Check Rules for the MSC 194.3 Check Rules for the Inner Cell 234.4 Check Rules for the Outer Cell 254.5 Check Rules for the BSC 274.6 Check Rules for the Internal Cell 324.7 Check Rules for the Overlaid Subcell 674.8 Check Rules for the Channel Group 734.9 Check Rules for the External Cell 774.10 Check Rules for the Neighbour Relation 854.11 Check Rules for the Transceiver Group 894.12 Check Rules for the Site 914.13 Check Rules for the Foreign Cell 91
SEIF v1.2,
FREEOPEN INFORMATIONTMOS User Guide 2 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
1 Introduction
This document is intended for users of the Cellular Network Adminis-tration (CNA) in the GSM OSS R8.1, in the following text referred toas OSS R8.1. The document describes the scope of the ConsistencyCheck rules applied within CNA. It is a supplement to the main CNAUser Guide, and is supposed to be read in that context.
1.1 Prerequisites
It is assumed that the user of this document:
• is familiar with Sun workstations and window-basedinterfaces
• has a working knowledge of the OSS R8.1
• has proper authority to use the CNA Consistency Checkfunctions.
1.2 User Interface Conventions
The Consistency Check rules do not have a user interface of its own.The rules are selected in the UI described in the CNA User Guide.They cannot be edited.
1.3 Typographic Conventions
System element names, such as names of commands, programs,and directories are shown in Courier as follows:
Store the file in the $TMOSADMHOME/common_files/cha directory.
Text in boldface Courier indicates that the characters are to be typedexactly as shown.
Enter the following command: cd /usr/local/tmos/tap
When a command string is longer than one line in the opened win-dow, the string will continue on the following line. The user must adda back-slash "\" at the end of all lines but the last to tell the systemthat the command string continues over more than one line. Theprinciple is shown for a three line command string:
SYBASE=/usr/local/sybase; export SYBASE;\
TMOSHOME=/usr/local/tmos; export TMOSHOME;\
cd /var/tmos_cold_tnm; tnm_trandbload.sh >/dev/null
FREEOPEN INFORMATIONTMOS User Guide 3 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Text in boldface, italic Courier represents variables that must be sup-plied by the user. The principle is shown in the following example,where the hostname is to be supplied by the user.
The command rlogin has the following syntax:
rlogin hostname
The words "Enter" and "Type" are used in the following ways:
• "Enter" means "Type the string shown here and endyour input with Return."
• "Type" means "Type exactly what is shown here, andnothing else."
1.4 General Information
Not applicable.
FREEOPEN INFORMATIONTMOS User Guide 4 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
2 Consistency Check Rules Overview
The Consistency Check rules are used to avoid entering inconsistentand/or incorrect data in the network. It is highly recommended to runa Consistency Check Job as described in the CNA User Guide beforedata in a changed Planned Area is transferred to the network and tothe Valid Area.
The various rules are selected or deselected using the windowsdescribed in CNA User Guide.
FREEOPEN INFORMATIONTMOS User Guide 5 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
3 Performed Consistency Checks
Consistency Checks can be performed on the Valid Area or onPlanned Area on the following levels:
a Area
See section 3.1.
b MSC
See section 3.2.
c BSC
See section 3.3.
d Internal Cell
See section 3.4.
The result of failed checks is displayed on screen. It may also beprinted or saved in a file.
3.1 Checks on the Area Level
When a Consistency Check is performed for the Valid Area or for aPlanned Area the following rules are checked for the MSCs in thearea and in the objects contained in the MSCs:
a The check rules specified for MSC
See section 4.2.
b The check rules specified for Inner Cell
See section 4.3.
c The check rules specified for Outer Cell
(See section 4.4.
The following rules are checked for the BSCs in the area and in theobjects contained in the BSCs:
a The check rules specified for BSC
See section 4.5.
b The check rules specified for Internal Cell
See section 4.6.
FREEOPEN INFORMATIONTMOS User Guide 6 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
c The check rules specified for Overlaid Subcell
See section 4.7.
d The check rules specified for Channel Group
See section 4.8.
e The check rules specified for External Cell
See section 4.9.
f The check rules specified for Neighbour Relation
See section 4.10.
g The check rules specified for Transceiver Group
See section 4.11.
h The check rules specified for Site
See section 4.12.
The following rules are checked for the Foreign Cells in the area:
a The checks specified for Foreign Cell
See section 4.13.
3.2 Checks on the MSC Level
When a Consistency Check is performed for the Valid Area or for aPlanned Area, the following rules are checked for a MSC in the areaand in the objects contained in that MSC:
a The check rules specified for MSC
See section 4.2.
b The check rules specified for Inner Cell
See section 4.3.
c The check rules specified for Outer Cell
See section 4.4.
The following rules are checked for the BSCs in the MSC and in theobjects contained in the BSCs:
a The check rules specified for BSC
FREEOPEN INFORMATIONTMOS User Guide 7 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
See section 4.5.
b The check rules specified for Internal Cell
See section 4.6.
c The check rules specified for Overlaid Subcell
See section 4.7.
d The check rules specified for Channel Group
See section 4.8.
e The check rules specified for External Cell
See section 4.9.
f The check rules specified for Neighbour Relation
See section 4.10.
g The check rules specified for Transceiver Group
See section 4.11.
h The check rules specified for Site
See section 4.12.
3.3 Checks on the BSC Level
When a Consistency Check is performed for the Valid Area or for aPlanned Area, the following rules are checked for a BSC in the areaand in the objects contained in that BSC:
a The check rules specified for BSC
See section 4.5.
b The check rules specified for Internal Cell
See section 4.6.
c The check rules specified for Overlaid Subcell
See section 4.7.
d The check rules specified for Channel Group
See section 4.8.
e The check rules specified for External Cell
FREEOPEN INFORMATIONTMOS User Guide 8 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
See section 4.9.
f The check rules specified for Neighbour Relation
See section 4.10.
g The check rules specified for Transceiver Group
See section 4.11.
h The check rules specified for Site
See section 4.12.
3.4 Checks on the Internal Cell Level
When a Consistency Check is performed for the Valid Area or for aPlanned Area, the following rules are checked for an Internal Cell inthe area and in the objects contained in that Internal Cell:
a The check rules specified for Inner Cell
See section 4.3.
b The check rules specified for Outer Cell
See section 4.4.
c The check rules specified for Internal Cell
See section 4.6.
d The check rules specified for Overlaid Subcell
See section 4.7.
e The check rules specified for Channel Group
See section 4.8.
f The check rules specified for External Cell
See section 4.9.
g The check rules specified for Neighbour Relation
See section 4.10.
FREEOPEN INFORMATIONTMOS User Guide 9 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4 Consistency Check Rules
The different Check Rules are described as follows:
Rule no: Rule number in the CNA - Consistency CheckPreferences window.
UI Window: The UI window containing the applicable rule,represented by the window title.
Check: A short description of what is checked and which ob-ject types and parameters the particular check isacting on.
Object: States which versions of the particular object that ischecked.
Comments: A short comment on the particular check. Thecomment describes why the check is performed.
4.1 List of Consistency Check Rules
The various Consistency Check rules are listed according to theirnumber. The table lists the CNA - Consistency Check Preferencessubwindow (UI window, see CNA User Guide) in which the ruleappears, and the descriptive text in the window (UI text).
Table 1 Consistency Check Rules
Rule no. UI Window/UI Text See section:
1 Cell Global Identity - Number ofdifferent CGI in the MSC
4.2.6
2 Cell Global Identity - Inner Cell, CGIin corresponding Internal Cell
4.3.3
3 Cell Global Identity - Inner Cell, CGIin Foreign cell with same name
4.3.4
4 Cell Global Identity - Uniqueness ofInner Cell CGI in the MSC
4.3.6
5 Cell Global Identity - Outer Cell CGIequal to corresponding Inner orForeign Cell
4.4.3
FREEOPEN INFORMATIONTMOS User Guide 10 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
6 Cell Global Identity - Uniqueness ofOuter Cell CGI in the MSC
4.4.4
7 Cell Global Identity - Internal CellCGI corresponding to Inner Cell andlacking
4.6.5
Inner Cell in the MSC 4.6.6
8 Cell Global Identity - Uniqueness ofInternal Cell CGI in the BSC
4.6.8
9 Cell Global Identity - Uniqueness ofInternal Cell CGI among ExternalCells in the BSC
4.6.9
10 Cell Global Identity - External CellCGI in corresponding Internal orForeign Cell
4.9.2
11 Cell Global Identity - Uniqueness ofExternal Cell CGI in the BSC
4.9.3
12 Cell Global Identity - CGI defined(Foreign Cell)
4.13.2
13 Cell Global Identity - Uniqueness ofForeign Cell CGI
4.13.3
14 Channel number/Frequency alloca-tion page 1 - BCCHNO defined andin DCHNO
4.6.34
15 Channel number/Frequency alloca-tion page 1 - Range of DCHNO inthe cell when type is GSM 1800 orGSM 1900
4.6.38
16 Channel number/Frequency alloca-tion page 1 - Maximum number ofDCHNO in the cell
4.6.37
17 Channel number/Frequency alloca-tion page 1 - Minimum andMaximum Number of SDCCH in theCell
4.6.39
18 Channel number/Frequency alloca-tion page 1 - Maximum number ofCBCH in the Internal Cell
4.6.40
19 Channel number/Frequency alloca-tion page 1 - Supervision of logicalchannels limit values for BCCH
4.6.70
20 Not defined
FREEOPEN INFORMATIONTMOS User Guide 11 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
21 Channel number/Frequencyallocation
4.6.71
page 1 - Supervision of logical 4.6.72
channels limit values for SDCCH, 4.6.73
TCH, CBCH 4.6.74
4.6.75
22 Not defined
23 Channel number/Frequency alloca-tion page 1 - Seizure supervision forTCH
4.6.76
24 Channel number/Frequency alloca-tion page 1 - Seizure supervision forSDCCH
4.6.77
25 Channel number/Frequencyallocation
4.7.9
page 1 - Supervision of logical 4.7.10
channels limit values for SDCCH, 4.7.11
TCH (Overlaid Subcell) 4.7.12
26 Channel number/Frequency alloca-tion page 1 - DCHNO in the cellwithin connected TG capability
4.8.4
27 Channel number/Frequency alloca-tion page 2 - Neighbours with samefrequencies
4.6.56
28 Channel number/Frequency alloca-tion page 2 - Minimum number ofDCHNO in the Channel Group
4.11.4
29 Channel number/Frequency alloca-tion page 2 - Uniqueness ofDCHNO in Channel Groupsconnected to the cell
4.8.5
30 Channel number/Frequency alloca-tion page 2 - Maximum number ofSDCCH in Channel Group
4.8.7
31 Channel number/Frequency alloca-tion page 2 - Maximum number ofCBCH in Channel Group
4.8.8
FREEOPEN INFORMATIONTMOS User Guide 12 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
32 Channel number/Frequency alloca-tion page 2 - BCCHNO defined andequal (External - Internal/ForeignCell)
4.9.8
33 Channel number/Frequency alloca-tion page 2 - BCCHNO defined andin DCHNO (Foreign Cell)
4.13.6
34 Channel number/Frequency alloca-tion page 2 - Operation Mode - BAlists
4.6.46
35 Channel number/Frequency alloca-tion page 2 - BCCHNOs subset ofACTIVE and IDLE lists
4.6.41
36 Channel number/Frequency alloca-tion page 2 - BCCHNO in ACTIVElist corresponds to neighbour
4.6.42
37 Channel number/Frequency alloca-tion page 2 - Neighbours withadjacent frequencies
4.6.57
38 Channel number/Frequency alloca-tion page 2 - Value range and maxnumber of measurementfrequencies in the cell
4.6.43
39 Not defined
40 Power page 1 - BSPWRB and 4.6.19
BSPWRT defined and within 4.7.2
connected TG capability 4.11.2
41 Not defined
42 Power page 1 - BSPWR defined 4.6.22
43 Power page 1 - BSTXPWR defined 4.6.23
44 Power page 1 - CCHPWR defined 4.6.26
45 Power page 1 - MSTXPWR defined 4.6.27
46 Power page 1 - BSRXMIN defined 4.6.28
47 Power page 1 - BSRXSUFF defined 4.6.29
48 Power page 1 - MSRXMIN defined 4.6.31
49 Power page 1 - MSRXSUFF defined 4.6.32
50 Power page 1 - BSTXPWR defined(Overlaid Subcell)
4.7.4
FREEOPEN INFORMATIONTMOS User Guide 13 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
51 Power page 1 - MSTXPWR defined(Overlaid Subcell)
4.7.5
52 Power page 1 - Relation betweenBSPWR - BSTXPWR
4.6.24
53 Power page 1 - Relation betweenBSTXPWR in Internal Cell -Overlaid Subcell
4.6.25
54 Power page 1 - BSPWRB, maxvalue in the edge of the band (GSM1900)
4.6.20
55 Power page 1 - BSTPWRT, max 4.6.21
value in the edge of the band (GSM1900)
4.7.3
56 Power page 2 - BSPWR definedand equal (External - Internal/Foreign Cell)
4.9.9
57 Power page 2 - BSTXPWR definedand equal (External - Internal/Foreign Cell)
4.9.10
58 Power page 2 - MSTXPWR definedand equal (External - Internal/Foreign Cell)
4.9.11
59 Power page 2 - BSRXMIN definedand equal (External - Internal/Foreign Cell)
4.9.12
60 Power page 2 - BSRXSUFF definedand equal (External - Internal/Foreign Cell)
4.9.13
61 Power page 2 - MSRXMIN definedand equal (External - Internal/Foreign Cell)
4.9.14
62 Power page 2 - MSRXSUFF defineand equal (External - Internal/Foreign Cell)
4.9.15
63 Power page 2 - BSPWR defined(Foreign Cell)
4.13.7
64 Power page 2 - BSTXPWR defined(Foreign Cell)
4.13.8
65 Power page 2 - MSTXPWR defined(Foreign Cell)
4.13.9
FREEOPEN INFORMATIONTMOS User Guide 14 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
66 Power page 2 - BSRXMIN defined(Foreign Cell)
4.13.10
67 Power page 2 - BSRXSUFF defined(Foreign Cell)
4.13.11
68 Power page 2 - MSRXMIN defined(Foreign Cell)
4.13.12
69 Power page 2 - MSRXSUFF defined(Foreign Cell)
4.13.13
70 Power page 2 - Relation betweenMSRXSUFF - MSRXMIN
4.6.33
71 Power page 2 - Relation betweenBSRXSUFF - BSRXMIN
4.6.30
72 State in Cells and Channel Groups -Cell state when some parametersare changed
4.6.2
73 State in Cells and Channel Groups -Channel Group state when TSC ischanged
4.6.3
74 State in Cells and Channel Groups -Channel Group state when TSC ischanged (Overlaid Subcell)
4.7.1
75 State in Cells and Channel Groups -Channel Group state when TG ischanged
4.8.1
76 State in Cells and Channel Groups -Channel Group state when ChannelGroup 0 is halted
4.6.4
77 Neighbour relations - Number ofNeighbour Relations in BSC
4.5.6
78 Neighbour relations - Number ofNeighbour Relations with internalneighbour
4.5.7
79 Neighbour relations - Number ofNeighbour Relations with externalneighbour
4.5.8
80 Neighbour relations - Number ofNeighbour Relations to Internal Cell
4.6.10
81 Neighbour relations - Two-wayNeighbour Relation
4.10.2
82 Neighbour relations - Consistency ofsome Neighbour Relation data
4.10.3
FREEOPEN INFORMATIONTMOS User Guide 15 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
83 Neighbour relations - Neighbours inBSC, System Type when operationsmode is SINGLE
4.6.11
84 Neighbour relations - Relationbetween KHYST - LHYST
4.10.4
85 Neighbour relations - Relation be-tween BQOFFSET - KHYST andLHYST
4.10.6
86 Neighbour relations - Relation be-tween AWOFFSET - KHYST andLHYST
4.10.5
87 BSC - Existence of BSC connectionand BSC (Inner Cell)
4.3.1
88 BSC - Lacking correspondingInternal Cell in BSC (Inner Cell)
4.3.2
89 BSC - Corresponding Valid AreaBSC
4.5.1
90 BSC - Superfluous External Cell 4.9.4
91 BSC - Number of Internal Cells 4.5.2
92 BSC - Number of External Cells 4.5.4
93 BSC - Number of Channel Groups 4.5.3
94 BSC - Size of LOAS 4.5.5
95 BSC - Max number of PriorityProfiles
4.5.9
96 BSC - System Type, BSC - InternalCell
4.6.45
97 BSC - Multi band Operation Mode 4.5.10
98 MSC - Corresponding Valid AreaMSC
4.2.1
99 MSC - Uniqueness of the LocationArea Identity
4.2.2
100 MSC - ATT intercell correspondence 4.2.3
101 MSC - Number of Inner Cells andOuter Cells in the MSC
4.7.4
102 MSC - Number of different LAI de-fined in the set of Inner Cells andOuter Cells
4.2.5
FREEOPEN INFORMATIONTMOS User Guide 16 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
103 MSC - Sum of NCSs defined in heset of Inner and Outer Cells
4.2.7
104 MSC - Uniqueness of Inner Celldesignation in the area
4.3.5
105 MSC - Existence of MSC connection(Outer Cell)
4.4.1
106 MSC - Lacking corresponding Inneror Foreign Cell in the area (OuterCell)
4.4.2
107 MSC - Superfluous Outer Cell 4.4.5
108 MSC - Lacking related Inner orOuter Cell in the MSC (NeighbourRelation)
4.10.1
109 MSC - MSC name defined (ForeignCell)
4.13.1
110 BSC - CAPLTCHEMER in MSC andEMERGPRL in connected BSCs
4.5.11
111 Miscellaneous page 1 - Uniquenessof Internal Cell designation in thearea
4.6.7
112 Miscellaneous page 1 - Existence ofTransceiver Group connection
4.8.3
113 Miscellaneous page 1 - AGBLK(BCCHTYPE - COMB - COMBC)
4.6.13
114 Miscellaneous page 1 - BSIC (NCCand BCC) defined (Internal Cell)
4.6.12
115 Miscellaneous page 1 BSIC (NCCand BCC) defined (External-Internal/Foreign Cell)
4.9.7
116 Miscellaneous page 1 - BCCHNOand BSIC not same betweenneighbours
4.6.35
117 Miscellaneous page 1 - NCCPERM,at least one value defined
4.6.15
118 Miscellaneous page 1 - NCCPERM, 4.6.16
NCC lacking or superfluous 4.6.17
119 Miscellaneous page 1 - DTXUdefined
4.6.18
FREEOPEN INFORMATIONTMOS User Guide 17 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
120 Miscellaneous page 1 - Relation be-tween XRANGE and TALIM,MAXTA and TN values
4.6.59
121 Miscellaneous page 1 - XRANGEwhen subcell structure exists
4.6.63
122 Miscellaneous page 1 - Relationbetween MAXTA - TALIM
4.6.64
123 Miscellaneous page 1 - LOL defined 4.7.6
124 Miscellaneous page 1 - TAOLdefined
4.7.7
125 Miscellaneous page 2 - LackingInternal or Foreign Cell in the area
4.9.1
126 Miscellaneous page 2 - LAYER inExternal - Internal/Foreign Cell
4.9.6
127 Miscellaneous page 2 - MISSNM inExternal - Internal/Foreign Cell
4.9.16
128 Miscellaneous page 2 - AW inExternal - Internal/Foreign Cell
4.9.17
129 Miscellaneous page 2 - SCHO inExternal - Internal/Foreign Cell
4.9.18
130 Miscellaneous page 2 - SuperfluousTransceiver Group
4.11.1
131 Miscellaneous page 2 -Corresponding Valid Area Sites
4.12.1
132 Miscellaneous page 2 - SuperfluousForeign Cell
4.13.4
133 Miscellaneous page 2 - BSICdefined (Foreign Cell)
4.13.5
134 Miscellaneous page 2 - COSITE,neighbours in same Site
4.10.7
135 Miscellaneous page 2 - Relation 4.6.65
between SSLEN - INILEN in InternalCell - Overlaid Subcell
4.7.13
136 Miscellaneous page 2 - Relationbetween SSRAMPSI - SSLENSI
4.6.68
137 Miscellaneous page 2 - Relationbetween AW - ASSOC
4.6.1
138 Miscellaneous page 2 - Relationbetween SSRAMPSD - SSLENSD
4.6.67
FREEOPEN INFORMATIONTMOS User Guide 18 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
139 Miscellaneous page 2 - BSIC equalon same Site
4.6.39
140 Miscellaneous page 3 - ResourceType
4.6.44
connection to Priority Profile 4.7.8
141 Miscellaneous page 3 - Cell SystemType (External - Internal/ForeignCell)
4.9.5
142 Miscellaneous page 3 - Loadsharing, BSC - cell
4.6.47
143 Miscellaneous page 3 - Cell LoadSharing, cell - cell
4.6.48
144 Miscellaneous page 3 - Relationbetween CLSLEVEL - CLSACC
4.6.51
145 Miscellaneous page 3 - Relationbetween LIMIT1 to LIMIT4
4.6.52
146 Miscellaneous page 3 - Relationbetween DTX - HOP - HSN
4.6.54
147 Miscellaneous page 3 - Relationbetween DTX - HOP
4.6.53
148 Miscellaneous page 3 - Relation be-tween TALIM - TAOL andTAOLHYST
4.6.58
149 Miscellaneous page 3 - Relationbetween DTXFUL - DTXU
4.6.55
150 Miscellaneous page 3 - EXTPEN, 4.6.78
External Cell - BSC 4.9.19
151 State in Cells and Channel Groups -Miscellaneous page 3 - ChannelGroup State when all DCHNOsremoved
4.8.2
152 Miscellaneous page 3 - Relation 4.6.66
between INIDES - SSDES 4.7.14
153 Miscellaneous page 3 - Relation be-tween TSC in Internal Cell -Overlaid Subcell
4.6.62
154 Miscellaneous page 3 - RelationSIMSG - cell state
4.6.69
155- 199 Not defined
FREEOPEN INFORMATIONTMOS User Guide 19 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Rule no. UI Window/UI Text See section:
200 Miscellaneous page 1 - Relationbetween XRANGE - MC
4.6.60
201 Miscellaneous page 1 - Relationbetween MC - BSMC
4.6.61
202 Miscellaneous page 2 - Relationbetween SCLDUL - SCLDLL
4.6.50
203 Miscellaneous page 2 - Relationbetween subcell structure - SCLD
4.6.49
204 Miscellaneous page 3 - Relationbetween AGBLK - CBCH
4.6.14
205 Not defined
206 Miscellaneous page 1 - XRANGEwithin connected TG capacity
4.11.3
207 Channel number/Frequency alloca-tion page 1-Frequency band forBCCHNO and DCHNO
4.8.6
208 Miscellaneous Page 3 - RelationBetween XRANGE and GPRSSUP
4.6.79
209 GPRS within Connected TGCapability
4.11.5
210 Maximum Channel Data Rate 4.6.80
211 Layers connected to HCS bands inIncreasing Order
4.5.12
4.2 Check Rules for the MSC
4.2.1 Corresponding Valid Area MSC
Rule no: 98
UI Window: MSC
Check: Checks that a corresponding MSC of the same typeand revision exists in the Valid Area if the MSCbelongs to a Planned Area.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
FREEOPEN INFORMATIONTMOS User Guide 20 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Non-Ericsson MSC
Comments: This check detects any inconsistencies between datain different objects.
4.2.2 Uniqueness of LAI in the Area
Rule no: 99
UI Window: MSC
Check: Checks, for the set of all the Inner Cells belonging tothe MSC, that the Location Area Identity (LAI = MCC +MNC + LAC) is not in the set of all the Inner Cellswithin the area belonging to other MSCs, or in the setof Foreign Cells.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.2.3 ATT Intercell Correspondence
Rule no: 100
UI Window: MSC
Check: Checks for all Internal Cells corresponding to Inner Cellsbelonging to the MSC, that ATT is identical for theInternal Cells with the same LAI.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 21 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.2.4 Number of Inner Cells and Outer Cells in the MSC
Rule no: 101
UI Window: MSC
Check: Checks that the total number of Inner and Outer Cells inthe MSC does not exceed the value of the Cellconversion table parameter.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A failureindicates that the command MGCEI and MGOCI will failduring an Update of the Network with the Planned Area.
4.2.5 Number of Different LAIs Defined in the Set of Inner Cells andOuter Cells in the MSC
Rule no: 102
UI Window: MSC
Check: Checks that the number of different Location Area Identi-ties defined in the set of Inner and Outer Cells in theMSC does not exceed the value of the Location area fileparameter.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGCEI and MGOCI willfail during an Update of the Network with the PlannedArea.
FREEOPEN INFORMATIONTMOS User Guide 22 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.2.6 Size of the CGI/LAI Analysis Tree
Rule no: 1
UI Window: Cell Global Identity
Check: Checks that the CGI/LAI analysis tree, based on the de-fined Cell Global Identity (CGI = MCC + MNC + LAC +CI) in the set of Inner and Outer Cells in the MSC doesnot exceed the value of the corresponding fileparameter.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGCEI and MGOCI willfail during an Update of the Network with the PlannedArea.
4.2.7 Sum of NCSs Defined in the Set of Inner Cells and Outer Cells inthe MSC
Rule no: 103
UI Window: MSC
Check: Checks that the total sum of NCSs (Number of countersets for Neighbouring Cell statistics) in the set of InnerCells and Outer Cells in the MSC does not exceed thevalue of the Neighbouring Cell statistics file parameter.
Object: MSC, CME20 SS R7
MSC, GSM 900/1800 SS R8
MSC, CMS40 SS R4
MSC, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGCEC and MGOCCwill fail during an Update of the Network with thePlanned Area.
FREEOPEN INFORMATIONTMOS User Guide 23 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.3 Check Rules for the Inner Cell
4.3.1 Existence of a BSC Connection
Rule no; 87
UI Window: BSC
Check: Checks that a BSC connection has been defined for theInner Cell.
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGCEI will fail duringan Update of the Network with the Planned Area.
4.3.2 Lacking Corresponding Internal Cell in the BSC
Rule no: 88
UI Window: BSC
Check: Checks that there is an Internal Cell with the same cellname as the Inner Cell, belonging to the BSC stated bythe Inner Cell if a stated connection is defined.
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.3.3 CGI in Corresponding Internal Cell
Rule no: 2
UI Window: Cell Global Identity
Check: Checks that CGI is defined.
FREEOPEN INFORMATIONTMOS User Guide 24 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Checks that CGI in the Inner Cell, if defined, is identicalto CGI in the corresponding Internal Cell if there is acorresponding Internal Cell.
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.3.4 CGI Inner Cell - Foreign Cell
Rule no: 3
UI Window: Cell Global Identity
Check: Checks that CGI in the Inner Cell, if defined, is identicalto CGI in Foreign Cell with the same name(Non-Ericsson BSC).
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.3.5 Uniqueness of the Inner Cell Name in the Area
Rule no: 104
UI Window: MSC
Check: Checks that the Inner Cell name is unique in the set ofInner Cells and Foreign Cells within the area.
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
FREEOPEN INFORMATIONTMOS User Guide 25 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.3.6 Uniqueness of Inner Cell CGI in the MSC
Rule no: 4
UI Window: Cell Global Identity
Check: Checks that the Inner Cell CGI, if defined, is unique inthe set of Inner and Outer Cells within the MSC.
Object: Inner Cell, CME20 SS R7
Inner Cell, GSM 900/1800 SS R8
Inner Cell, CMS40 SS R4
Inner Cell, GSM 1900 SS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGCEI will fail duringan Update of the Network with the Planned Area.
4.4 Check Rules for the Outer Cell
4.4.1 Existence of an MSC Connection
Rule no: 105
UI Window: MSC
Check: Checks that an MSC connection has been defined forthe Outer Cell.
Object: Outer Cell, CME20 SS R7
Outer Cell, GSM 900/1800 SS R8
Outer Cell, CMS40 SS R4
Outer Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command MGOCI will fail duringan Update of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 26 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.4.2 Lacking Corresponding Inner Cell or Foreign Cell in the Area
Rule no: 106
UI Window: MSC
Check: Checks that there is an Inner Cell or a Foreign Cell withthe same cell name as the Outer Cell, belonging to theMSC stated by the Outer Cell.
Object: Outer Cell, CME20 SS R7
Outer Cell, GSM 900/1800 SS R8
Outer Cell, CMS40 SS R4
Outer Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.4.3 CGI in Corresponding Inner Cell or Foreign Cell
Rule no: 5
UI Window: Cell Global Identity
Check: Checks that CGI is defined.
Checks that CGI in the Outer Cell is identical to CGI inthe corresponding Inner Cell or Foreign Cell if there is acorresponding Inner Cell or Foreign Cell.
Object: Outer Cell, CME20 SS R7
Outer Cell, GSM 900/1800 SS R8
Outer Cell, CMS40 SS R4
Outer Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.4.4 Uniqueness of Outer Cell CGI in the MSC
Rule no: 6
UI Window: Cell Global Identity
Check: Checks that the Outer Cell CGI, if defined, is unique inthe set of Outer and Inner Cells in the MSC.
FREEOPEN INFORMATIONTMOS User Guide 27 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Outer Cell, CME20 SS R7
Outer Cell, GSM 900/1800 SS R8
Outer Cell, CMS40 SS R4
Outer Cell, GSM 1900 SS R8
Comments: The check is only performed on a Planned Area. A fail-ure indicates that the command MGOCI will fail duringan Update of the Network with the Planned Area.
4.4.5 Superfluous Outer Cell
Rule no: 107
UI Window: MSC
Check: Checks that there is at least one Neighbour Relation,belonging to a BSC that belongs to the same MSC asthe Outer Cell, which has the same related cell name asthe Outer Cell name.
Object: Outer Cell, CME20 SS R7
Outer Cell, GSM 900/1800 SS R8
Outer Cell, CMS40 SS R4
Outer Cell, GSM 1900 SS R8
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.5 Check Rules for the BSC
4.5.1 Corresponding Valid Area BSC
Rule no: 89
UI Window: BSC
Check: Checks that a corresponding BSC of the same type andrevision exists in the Valid Area if the BSC belongs to aPlanned Area.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 28 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Non-Ericsson MSC
Comments: This check detects any inconsistencies between data indifferent objects.
4.5.2 Number of Internal Cells
Rule no: 91
UI Window: BSC
Check: Checks that the number of Internal Cells in the BSCdoes not exceed the value of the Internal Cell fileparameter.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEI will fail duringan Update of the Network with the Planned Area.
4.5.3 Number of Channel Groups
Rule no: 93
UI Window: BSC
Check: Checks that the number of Channel Groups in the BSCdoes not exceed 512.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDGI and RLDEI willfail during an Update of the Network with the PlannedArea.
FREEOPEN INFORMATIONTMOS User Guide 29 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.5.4 Number of External Cells
Rule no: 92
UI Window: BSC
Check: Checks that the number of External Cells in the BSCdoes not exceed the value of the External Cell fileparameter.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEI will fail duringan Update of the Network with the Planned Area.
4.5.5 Size of LOAS
Rule no: 94
UI Window: BSC
Check: Checks that LOAS equals or exceeds 1.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.5.6 Number of Neighbour Relations
Rule no: 77
UI Window: Neighbour Relations
Check: Checks that the number of Neighbour Relations in theBSC does not exceed 8,192.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 30 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area.
4.5.7 Number of Neighbour Relations with Internal Neighbour
Rule no: 78
UI Window: Neighbour Relations
Check: Checks that the number of Neighbour Relations in theBSC, where the related cell is an Internal Cell, does notexceed the size of the file holding handover counterdata for relations where the Neighbouring Cell is anInternal Cell.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area.
4.5.8 Number of Neighbour Relations with External Neighbour
Rule no: 79
UI Window: Neighbour Relations
Check: Checks that the number of Neighbour Relations in theBSC, where the related cell is an External Cell, does notexceed the size of the file holding handover counterdata for relations where the Neighbouring Cell is anExternal Cell.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 31 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.5.9 Maximum Number of Priority Profiles
Rule no: 95
UI Window: BSC
Check: Checks that maximum number of Priority Profiles is 32.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLPPI will fail during anUpdate of the Network with the Planned Area.
4.5.10 Multiband Operation Mode
Rule no: 97
UI Window: BSC
Check: Checks that Global System Type = MIXED if OperationMode = Multi.
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
Comments: A failure indicates that the command RLOMC will failduring an Update of the Network with the Planned Area.
4.5.11 EMERGPRL, CAPLTCHEMER
Rule no: 110
UI Window: BSC
Check: Based on the CAPLTCHEMER parameter in the MSC towhich the BSC is connected, the following is checked:
- if CAPLTCHEMER > 0 that DCA = ON and thatEMERGPRL = CAPLTCHEMER
- if CAPLTCHEMER = 0 that DCA = OFF
- if MSC is of Non-Ericsson type that DCA = OFF
FREEOPEN INFORMATIONTMOS User Guide 32 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: BSC, CME20 BSS R7
BSC, GSM 900/1800 BSS R8
BSC, CMS40 BSS R4
BSC, GSM 1900 BSS R8
BSC, CME20 SS R7
BSC, GSM 900/1800 SS R8
BSC, CMS40 SS R4
BSC, GSM 1900 SS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.5.12 Layers Connected to HCS bands in Increasing Order
Rule no: 211
UI Window: BSC
Check: Based on the HCS bands parameters, it is checked that:
- all layers have been connected
- a layer has been connected to one and only one HCSband
- within each HSC band, the layers are defined insuccessive order (contiguous and increasing order)
- across all HCS bands, the layers are defined inincreasing order
Object: BSC, GSM 900/1800 BSS R8
BSC, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLHBC will fail duringan update of the Network with the Planned Area.
4.6 Check Rules for the Internal Cell
4.6.1 ASSOC - AW Parameter Relation
Rule no: 137
UI Window: Miscellaneous Page 2
Check: Checks that ASSOC in BSC = ON when AW = ON inthe Internal Cell.
FREEOPEN INFORMATIONTMOS User Guide 33 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
ASSOC is defined for each System Type and the CellSystem Type determines to which ASSOC AW has tobe compared.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.2 Cell State During Update
Rule no: 72
UI Window: State in Cells and Channel Groups
Check: Checks if the corresponding Internal Cell in the Networkhas to be set to "HALTED" during an Update, if theInternal Cell belongs to a Planned Area.
An Internal Cell which is not already halted has to be setto "HALTED" during an Update if any of the following pa-rameters are changed: CGI, BSIC, BCCHNO, AGBLK,MFRMS, BCCHTYPE, FNOFFSET or XRANGE.
Note! In R8, if the BCCHNO parameter, only, has beenchanged, the Internal Cell does not always need to be"HALTED".
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects changed data and issues a warning.
4.6.3 Channel Group State During Update
Rule no: 73
UI Window: State in Cells and Channel Groups
Check: Checks if the corresponding Channel Groups in the Net-work has been set to the "HALTED" state during anUpdate if the Internal Cell belongs to a Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 34 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
All Channel Groups which are not already halted, andfor which the Subcell type is Underlaid, have to be setto "HALTED" during an Update if the TSC parameter ischanged.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.4 Channel Group State Active
Rule no: 76
UI Window: State in Cells and Channel Groups
Check: Checks that no Channel Group is "ACTIVE" whenChannel Group 0 is "HALTED" for all the ChannelGroups belonging to the cell and to the Planned Area.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.5 Lacking Corresponding Inner Cell in the MSC
Rule no: 7
UI Window: Cell Global Identity
Check: Checks that there is an Inner Cell with the same cellname belonging to the same MSC as the BSC whichthe Internal Cell belongs to.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 35 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.6 CGI in Corresponding Inner Cell
Rule no: 7
UI Window: Cell Global Identity
Check: Checks that CGI is defined.
Checks that CGI, in the Internal Cell, if defined, is identi-cal to CGI in the corresponding Inner Cell if there is acorresponding Inner Cell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.7 Uniqueness of Internal Cell Name in the Area
Rule no: 111
UI Window: Miscellaneous Page 1
Check: Checks that the Internal Cell name is unique in the setof Internal and Foreign Cells within the area.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.8 Uniqueness of Internal Cell CGI in the BSC
Rule no: 8
UI Window: Cell Global Identity
Check: Checks that the Internal Cell CGI, if defined, is unique inthe set of Internal Cells within the BSC.
Object: Internal Cell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 36 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEC will fail duringan Update of the Network with the Planned Area.
4.6.9 Uniqueness of Internal Cell CGI among External Cells in the BSC
Rule no: 9
UI Window: Cell Global Identity
Check: Checks that the Internal Cell CGI, if defined, is not inthe set of External Cell CGIs within the BSC.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEC will fail duringan Update of the Network with the Planned Area.
4.6.10 Number of Neighbour Relations
Rule no: 80
UI Window: Neighbour Relations
Check: Checks that the number of Neighbour Relationsbelonging to the Internal Cell does not exceed 64.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 37 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.11 Operation Mode - Neighbour Relation
Rule no: 83
UI Window: Neighbour Relations
Check: If the Operation mode of the parent BSC is "SINGLE",all the neighbours shall have the same System Type asthe Internal Cell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.12 BSIC Defined
Rule no: 114
UI Window: Miscellaneous Page 1
Check: Checks that both NCC and BCC are defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.13 AGBLK Range
Rule no: 113
UI Window: Miscellaneous Page 1
Check: Checks that AGBLK equals or exceeds zero or equalsor is less than two 0 if BCCHTYPE = COMB or ifBCCHTYPE = COMBC.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 38 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEC will fail duringan Update of the Network with the Planned Area.
4.6.14 AGBLK and CBCH Parameter Relation
Rule no: 204
UI Window: Miscellaneous Page 3
Check: Checks in Internal Cell that AGBLK exceeds zero ifCBCH = ON in the Channel Group connected to the cell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.15 NCCPERM Defined
Rule no: 117
UI Window: Miscellaneous Page 1
Check: Checks that at least one value is defined for NCCPERM.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 39 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.16 NCC Subset of NCCPERM
Rule no: 118
UI Window: Miscellaneous Page 1
Check: Checks that the NCCs in the Neighbouring Cells are asubset of the NCCPERM in the Internal Cell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.17 NCCPERM Without Corresponding NCC
Rule no: 118
UI Window: Miscellaneous Page 1
Check: Checks which NCCPERM in the Internal Cell that doesnot correspond to any NCC in the neighbouring cells.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.18 DTXU Defined
Rule no: 119
UI Window: Miscellaneous Page 1
Check: Checks that DTXU is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 40 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.6.19 BSPWRB and BSPWRT Defined
Rule no: 40
UI Window: Power Page 1
Check: Checks that BSPWRB and BSPWRT are defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.6.20 BSPWRB Maximum Value
Rule no: 54
UI Window: Power Page 1
Check Checks that the value of BSPWRB is equal to orless than what is stated for the following frequencynumbers in the GSM 1900 band:
DCHNO BSPWRB
512, 585 31
587, 610 31
612, 685 31
687, 710 31
712, 735 31
737, 810 31
Object: Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments This check detects any inconsistencies betweendata in different objects. The value refers to FCCregulations described in CNA User Guide.
FREEOPEN INFORMATIONTMOS User Guide 41 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.21 BSPWRT Maximum Value
Rule no: 55
UI Window: Power Page 1
Check Checks that the value of BSPWRT is equal to orless than what is stated for the following frequencynumbers in the GSM 1900 band:
DCHNO BSPWRT
512, 585 31
587, 610 31
612, 685 31
687, 710 31
712, 735 31
737, 810 31
Object: Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments This check detects any inconsistencies betweendata in different objects. The value refers to FCCregulations described in CNA User Guide.
4.6.22 BSPWR Defined
Rule no: 42
UI Window: Power Page 1
Check: Checks that BSPWR is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
FREEOPEN INFORMATIONTMOS User Guide 42 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.23 BSTXPWR Defined
Rule no: 43
UI Window: Power Page 1
Check: Checks that BSTXPWR is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.24 BSPWR and BSTXPWR Parameter Relation
Rule no: 52
UI Window: Power Page 1
Check: Checks that BSPWR >= BSTXPWR.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.25 BSTXPWR Internal Cell - Overlaid Subcell
Rule no: 53
UI Window: Power Page 1
Check: Checks that BSTXPWR in an Internal Cell equals or ex-ceeds BSTXPWR in the corresponding Overlaid Subcell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 43 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.26 CCHPWR Defined
Rule no: 44
UI Window: Power Page 1
Check: Checks that CCHPWR is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.6.27 MSTXPWR Defined
Rule no: 45
UI Window: Power Page 1
Check: Checks that MSTXPWR is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.28 BSRXMIN Defined
Rule no: 46
UI Window: Power Page 1
Check: Checks that BSRXMIN is defined.
Object: Internal Cell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 44 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the commands RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.29 BSRXSUFF Defined
Rule no: 47
UI Window: Power Page 1
Check: Checks that BSRXSUFF is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.30 BSRXSUFF and BSRXMIN Parameter Relation
Rule no: 71
UI Window: Power Page 2
Check: Checks that BSRXMIN equals or exceeds BSRXSUFFwhen EVALTYPE = 1.
(Parameters are entered as positive values. The systemchanges the sign of the values for use in thecalculations.)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
FREEOPEN INFORMATIONTMOS User Guide 45 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.31 MSRXMIN Defined
Rule no: 48
UI Window: Power Page 1
Check: Checks that MSRXMIN is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.32 MSRXSUFF Defined
Rule no: 49
UI Window: Power Page 1
Check: Checks that MSRXSUFF is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLNRI willfail during an Update of the Network with the PlannedArea.
4.6.33 MSRXSUFF and MSRXMIN Parameter Relation
Rule no: 70
UI Window: Power Page 2
Check: Checks that MSRXMIN equals or exceeds MSRXSUFFwhen EVALTYPE = 1.
(Parameters are entered as positive values. The sys-tem changes the sign of the values for use in thecalculations.)
Object: Internal Cell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 46 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.34 BCCHNO Defined
Rule no: 14
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that BCCHNO is defined.
Checks that BCCHNO is in the set of DCHNO inChannel Group 0 if BCCHNO is defined.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC, RLNRI andRLCFE will fail during an Update of the Network withthe Planned Area.
4.6.35 BCCHNO and BSIC in Neighbours
Rule no: 116
UI Window: Miscellaneous Page 1
Check: Checks that two or more neighbours to the current celldo not have the same BCCHNO and BSIC.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 47 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.36 Cell BSIC on Site
Rule no: 139
UI Window: Miscellaneous Page 2
Check: Checks that all Internal Cells on the same Site haveidentical BSICs.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.37 Maximum Number of DCHNO in the Cell
Rule no: 16
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks, for the set of all the Channel Groups belongingto the Internal Cell and its Overlaid Subcell, that thetotal number of DCHNO does not exceed 32.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCFI will fail during anUpdate of the Network with the Planned Area.
4.6.38 DCHNO Range in the Cell
Rule no: 15
UI Window: Channel Number
Frequency Allocation Page 1
FREEOPEN INFORMATIONTMOS User Guide 48 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Check: If the System Type is defined as GSM 1800 or GSM1900, and if the total number of DCHNO for the set ofall the Channel Groups belonging to the Internal Celland its Overlaid Subcell exceeds 18, the range of theDCHNO must not exceed 112.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCFI and RLDEC willfail during an Update of the Network with the PlannedArea.
4.6.39 Minimum and Maximum Number of SDCCH in the Cell
Rule no: 17
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks, for the set of all the Channel Groups belongingto the Internal Cell, that:
- that SDCCH exceeds zero if BCCHTYPE = NCOMB
- that SDCCH is less than or equals 16 if BCCHTYPE =NCOMB
- that the total number of SDCCH is less than or equals15 if BCCHTYPE = COMB or BCCHTYPE = COMBS
Checks in Channel Group 0 that:
- that SDCCH is less than or equals 7 if CCHPOS =BCCH and XRANGE = NO
- that SDCCH is less than or equals 3 if CCHPOS =BCCH and XRANGE = YES
Object Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the commands RLCCC and RLDECwill fail during an Update of the Network with thePlanned Area.
FREEOPEN INFORMATIONTMOS User Guide 49 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.40 Maximum Number of CBCH in the Cell
Rule no: 18
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks, for the set of all the Channel Groups belongingto the Internal Cell, that no more than one CBCH is setto "YES" if BCCHTYPE = NCOMB or if BCCHTYPE =COMB, or that no CBCH = "YES" if BCCHTYPE =COMBC.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCCC and RLDECwill fail during an Update of the Network with thePlanned Area.
4.6.41 BCCHNO Subset of ACTIVE and IDLE Lists
Rule no: 35
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that the BCCHNOs in all Neighbouring Cells area subset of the ACTIVE and IDLE lists.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.42 Superfluous BCCHNO in ACTIVE List
Rule no: 36
UI Window: Channel Number
Frequency Allocation Page 2
FREEOPEN INFORMATIONTMOS User Guide 50 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Check: Checks in the ACTIVE list that all frequencies in the listcorrespond to a BCCHNO in any of the NeighbouringCells.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.43 Value range and max number of Measurement Frequencies inthe cell
Rule no: 38
UI Window: Channel Number
Frequency Allocation Page 2
Check Checks that the maximum range of MBCCHNO is 278 ifthe cell system type is GSM 1800/GSM 1900
Checks if the Global System Type is "MIXED" and thelist type is IDLE that:
- if the Cell system Type is GSM, with BCCH in the Pband, and MBCCHNO is in the P band, and in the GSM1800/GSM 1900 band, that the maximum number ofMBCCHNO is 22 if the MBCCHNO range is between112 and 256.
- if the cell system type is GSM with BCCH in the Pband, and if MBCCHNO is in the P and in the G1 band,and in the GSM 1800/GSM 1900 band, the maximumnumber of MBCCHNO is 18 in the P and G1 band andin the GSM 1800/GSM 1900 band.
- if the cell system type is GSM with BCCH in the G1band, and if MBCCHNO is in the G1 band, and in theGSM 1800/GSM 1900 band, the maximum number ofMBCCHNO is 22 if the MBCCHNO range is between112 and 256.
- if the cell system type is GSM 1800/GSM 1900 withMBDDHNO in the P band and in the G1 band, that themaximum number MBCCHNO is 22 in the P band andin the G1 band.
Checks if the Global System Type is "MIXED"and thelist type is ACTIVE that:
FREEOPEN INFORMATIONTMOS User Guide 51 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
- if the cell system type is GSM with BCCH in the Pband, and if MBCCHNO in the GSM 1800/GSM 1900band, the maximum number of MBCCHNO is 22 if theMBCCHNO range is between 112 and 256.
- if the cell system type is GSM 1800/GSM 1900 withBCCH in the P and in the G1 band, that the maximumnumber MBCCHNO is 22 in the P band and in the G1band.
Object: Internal Cell, GSM 900/1800 R8 BSC and GSM 1900R8 BSC
Comments: A failure indicates that the command RLMFC or RLDECwill fail during an Update of the Network with thePlanned Area.
This check depends on limitations in the SystemInformation massages.
4.6.44 Resource Type - Priority Profile Connection
Rule no: 140
UI Window: Miscellaneous Page 3
Check: Checks that the Resource Type (that is, SDCCHUL,TCHFRUL, and TCCHRUL) connection to a PriorityProfile exists.
Object: Internal Cell, CME20 R7 BSC; GSM 900/1800 R8 BSC
CMS40 R4 BSC; GSM 1900 R8 BSC
Comments: A failure indicates that the command RLPRC will failduring an Update of the Network with the Planned Area.
4.6.45 System Type BSC - Internal Cell
Rule no: 96
UI Window: BSC
Check: Checks that Cell System Type = Global System Type inthe BSC when Global System Type in the BSC is not"MIXED".
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 52 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 1900 BSS R8
Comments: A failure indicates that the command RLDEI or RLTYCwill fail during an Update of the Network with thePlanned Area.
4.6.46 Operation Mode BA Lists
Rule no: 34
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that the ACTIVE and IDLE parameters onlycontain frequencies from one frequency band whenOperation Mode in the BSC is "SINGLE".
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.47 Load Sharing BSC - Cell
Rule no: 142
UI Window: Miscellaneous Page 3
Check: Checks that Load Sharing is "ACTIVE" in the BSC whenCell Load Sharing is "ACTIVE".
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 53 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.48 Cell Load Sharing Cell - Cell
Rule no: 143
UI Window: Miscellaneous Page 3
Check: Checks that not all neighbours which are on the samehierarchical level have HOCLSACC = OFF when CellLoad Sharing State = "ACTIVE".
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.49 Parameter SCLD and Subcell Structure
Rule no: 203
UI Window: Miscellaneous Page 2
Check: Checks that a Subcell structure exists if SCLD = ON.
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 1900 BSS R8
Comments: Performed on a Planned Area, only. A failure indicatesthat the command RLDSE and RLLLC will fail during anUpdate of the Network with the Planned Area.
4.6.50 SCLDUL and SCLDLL Parameter Relation
Rule no: 202
UI Window: Miscellaneous Page 2
Check: Checks that SCLDUL exceeds SCLDLL if SCLD = ON.
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 1900 BSS R8
Comments: Performed on a Planned Area, only. A failure indicatesthat the command RLDSE and RLLLC will fail during anUpdate of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 54 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.51 CLSLEVEL and CLSACC Parameter Relation
Rule no: 144
UI Window: Miscellaneous Page 3
Check: Checks that CLSLEVEL is less than CLSACC.
Object: Internal Cell, CME20 R7 BSC; GSM 900/1800 R8 BSC
CMS40 R4 BSC; GSM 1900 R8 BSC
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.52 Idle Channel Measurement
Rule no: 145
UI Window: Miscellaneous Page 3
Check: Checks that LIMIT1 is less than LIMIT2, which is lessthan LIMIT3, which is less than LIMIT4.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: A failure indicates that the command RLIMC will failduring an Update of the Network with the Planned Area.
4.6.53 Discontinuous Transmission - HOP
Rule no: 147
UI Window: Miscellaneous Page 3
Check: Checks that Frequency Hopping (HOP = ON) is usedwhen Discontinuous Transmission is used (DTXD = ONand DTXU is less than 2).
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 55 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.54 Discontinuous Transmission - HSN - Number of Frequencies
Rule no: 146
UI Window: Miscellaneous Page 3
Check: Checks that the number of hopping frequencies is not amultiple of 13 when Discontinuous Transmission is used(DTXD = ON and DTXU is less than 2), HOP = ON andHSN = 0 (cyclic hopping).
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.55 DTXFUL - DTXU Parameter Relation
Rule no: 149
UI Window: Miscellaneous Page 3
Check: Checks, if DTXFUL = 0 and DTXU = OFF (= 0 or 2) thatone or more neighbours have DTXU = ON (= 0 or 1).
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 56 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.56 Neighbours with Identical Frequencies
Rule no: 27
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks, for the set of all Neighbour Relations belong-ing to the Internal Cell, that there is no identicalfrequency in any Neighbouring Cell.
The frequencies for the selected cell is the total set ofDCHNOs of all the Channel Groups belonging to thecell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.57 Neighbours with Adjacent Frequencies
Rule no: 37
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks, for the set of all Neighbour Relations belongingto the Internal Cell, that Neighbouring Cells cannot havethe next frequency up or down.
The frequencies for the selected cell is the total set ofDCHNOs of all the Channel Groups belonging to thecell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 57 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.58 TALIM - TAOL - TAOLHYST Parameter Relation
Rule no: 148
UI Window: Miscellaneous Page 3
Check: Checks that TALIM exceeds (TAOL + TAOLHYST) inthe Overlaid Subcell.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.59 XRANGE and TALIM, MAXTA and TN Parameter Relation
Rule no: 120
UI Window: Miscellaneous Page 1
Check: Checks that the values of TALIM and MAXTA is lessthan or equals 63 when XRANGE = NO and that TN = 0or 2 when XRANGE = YES.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEC will fail duringan Update of the Network with the Planned Area.
4.6.60 MC and XRANGE Parameter Relation
Rule no: 200
UI Window: Miscellaneous Page 1
Check: Checks that XRANGE = OFF if MC = ON
Object: Internal Cell, GSM 900/1800 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 58 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCDC and RLDECwill fail during an Update of the Network with thePlanned Area.
4.6.61 MC and BSMC Parameter Relation
Rule no: 201
UI Window: Miscellaneous Page 1
Check: Checks that BSCMC = ON in the BSC if MC = ON.
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.62 TSC when Subcell Structure Exists
Rule no: 153
UI Window: Miscellaneous Page 3
Check: Checks that the TSC parameter in Internal Cell andOverlaid Subcell do not have identical values when asubcell structure exists.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.63 XRANGE when Subcell Structure Exists
Rule no: 121
UI Window: Miscellaneous Page 1
Check: For R7/R4: Checks that no Subcell structure existswhen XRANGE = YES.
For R8: Checks that no subcell structure exists whenXRANGE = YES and XRANGESUBCELL = 0.
FREEOPEN INFORMATIONTMOS User Guide 59 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Internal Cell, CME20 BSS R7
Internal Cell, CMS40 BSS R4
GSM 900/1800 BSS R8
GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLDSI will fail during anUpdate of the Network with the Planned Area.
4.6.64 TALIM and MAXTA Parameter Relation
Rule no: 122
UI Window: Miscellaneous Page 1
Check: Checks that TALIM is less than MAXTA.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.65 SSLEN and INILEN Parameter Relation
Rule no: 135
UI Window: Miscellaneous Page 2
Check: Checks that INILEN is less than SSLEN.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
FREEOPEN INFORMATIONTMOS User Guide 60 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.66 INIDES and SSDES Parameter Relation
Rule no: 152
UI Window: Miscellaneous Page 3
Check: Checks that INIDES is less than SSDES.
(Parameters are entered as positive values. The systemchanges the sign of the values for use in thecalculations.)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.67 SSRAMPSD and SSLENSD Parameter Relation
Rule no: 138
UI Window: Miscellaneous Page 2
Check: Checks that SSRAMPSD is less than or equalsSSLENSD.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.68 SSRAMPSI and SSLENSI Parameter Relation
Rule no: 136
UI Window: Miscellaneous Page 2
Check: Checks that SSRAMPSI is less than or equals SSLENSI.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 61 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.6.69 SIMSG Value Change Consequences
Rule no: 154
UI Window: Miscellaneous Page 3
Check: Checks that the cell has STATE = ACTIVE when thevalue of the SIMSG parameter is changed.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSMC will fail duringan Update of the Network with the Planned Area.
4.6.70 Supervision of Logical Channel Limit Value for BCCH
Rule no: 19
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for BCCH" does not exceedthe total number of logical BCCHs in the Internal Cell.
The total number of logical BCCHs = + 1 (if BCCHNO isdefined)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 62 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.71 Supervision of Logical Channel Limit Value for Full Rate TCH
Rule no: 21
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHFR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to the cell where thesubcell type is undefined or Underlaid.
The total number of logical TCHs =
+ Sum {over Channel Groups belonging to theUnderlaid Cell}
[+ 8* (The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)]
-1 (if BCCHNO is defined)
Object: Internal Cell, CME20 BSS R7
Internal Cell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.6.72 Supervision of Logical Channel Limit Value for Enhanced FullRate TCH
Rule no: 21
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHEFR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to the cell where thesubcell type is undefined or Underlaid.
The total number of logical TCHs =
+ Sum {over Channel Groups belonging to theUnderlaid Cell}
[+ 8* (The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)]
-1 (if BCCHNO is defined)
FREEOPEN INFORMATIONTMOS User Guide 63 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Internal Cell, CME20 BSS R7
Internal Cell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.6.73 Supervision of Logical Channel Limit Value for Half Rate TCH
Rule no: 21
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHHR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to the cell where thesubcell type is undefined or Underlaid.
The total number of logical TCHs =
+Sum {over Channel Groups belonging to the UnderlaidCell}
{[+ 8* (The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)] - 1 (if BCCHNO is defined)}
*2 (that is, maximum value when all channels are halfrate)
Object: Internal Cell, CME20 BSS R7
Internal Cell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.6.74 Supervision of Logical Channels Limit Value for SDCCH
Rule no: 21
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for SDCCH" does not ex-ceed the total number of logical SDCCHs in the set ofall the Channel Groups belonging to the cell.
The total number of logical SDCCHs =
+ Sum {over Channel Groups belonging to the cell}
FREEOPEN INFORMATIONTMOS User Guide 64 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
[+ 8* (The defined number of SDCCHs in the ChannelGroup) - 1(if CBCH = YES)]
+ 4 (from the SDCCH/4, if BCCHNO is defined andBCCHTYPE = COMB)
+ 3 (from the SDCCH/4, if BCCHNO is defined andBCCHTYPE = COMBC)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.6.75 Supervision of Logical Channel Limit Value for CBCH
Rule no: 21
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for CBCH" does not exceedthe total number of logical CBCHs in the set of all theChannel Groups belonging to the cell.
The total number of logical CBCHs =
+ Sum {over Channel Groups belonging to the cell}
[+ 1 (if CBCH = YES)]
+ 1 (if BCCHNO is defined and BCCHTYPE = COMBC)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 65 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.76 Seizure Supervision for TCH
Rule no: 23
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that "Seizure Supervision for TCH" is activatedin the connected BSC if the Internal Cell belongs to aPlanned Area and if "Seizure Supervision for TCH" inthe Internal Cell is activated.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.6.77 Seizure Supervision for SDCCH
Rule no: 24
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that "Seizure Supervision for SDCCH" is acti-vated in the connected BSC if the Internal Cell belongsto a Planned Area and if "Seizure Supervision forSDCCH" in the Internal Cell is activated.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 66 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.6.78 EXTPEN Value
Rule no.: 150
UI Window: Miscellaneous Page 3
Check: Checks in the External Cell that the value of theEXTPEN parameter is identical in all External Cells forwhich the corresponding Internal Cells are connected tothe same BSC.
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 900 BSS R8
Comments. This check detects any inconsistencies between data indifferent objects.
4.6.79 Relation between XRANGE and GPRSSUP
Rule no.: 208
UI Window: Miscellaneous Page 3
Check: Checks that XRANGE and GPRSSUP are not set toYES at the same time.
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 900 BSS R8
Comments. This check is only performed on a Planned Area. A fail-ure indicates that the command RLGSI will fail during anupdate of the Network with the Planned Area.
4.6.80 Maximum Channel Data Rate
Rule no.: 210
UI Window: Miscellaneous Page 4
Check: Checks that the value of CMDR is lower or equal to thevalue of MAXCHDATARATE in the BSC.
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 900 BSS R8
Comments. This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 67 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.7 Check Rules for the Overlaid Subcell
4.7.1 Channel Group State
Rule no: 74
UI Window: State in Cells and Channel Groups
Check: Checks that the corresponding Channel Groups in theNetwork have to be set to "HALTED" during an Updateif the Overlaid Cell belongs to a Planned Area.
All Channel Groups which are not already halted, andwhose subcell type is Overlaid, have to be set to"HALTED" during an Update if the TSC parameter ischanged.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.7.2 BSPWRT Defined
Rule no: 40
UI Window: Power Page 1
Check: Checks that BSPWRT is defined.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLDGC willfail during an Update of the Network with the PlannedArea.
FREEOPEN INFORMATIONTMOS User Guide 68 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.7.3 BSPWRT Maximum Value
Rule no: 55
UI Window: Power Page 1
Check: Checks that the value of BSPWRT is equal to orless than what is stated for the following frequencynumbers in the GSM 1900 band:
DCHNO BSPWRT
512, 585 31
587, 610 31
612, 685 31
687, 710 31
712, 735 31
737, 810 31
Object: Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies betweendata in different objects. The value refers to FCCregulations described in CNA User Guide.
4.7.4 BSTXPWR Defined
Rule no: 50
UI Window: Power Page 1
Check: Checks that BSTXPWR is defined.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLDGC willfail during an Update of the Network with the PlannedArea.
FREEOPEN INFORMATIONTMOS User Guide 69 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.7.5 MSTXPWR Defined
Rule no: 51
UI Window: Power Page 1
Check: Checks that MSTXPWR is defined.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLDGC willfail during an Update of the Network with the PlannedArea.
4.7.6 LOL Defined
Rule no: 123
UI Window: Miscellaneous Page 1
Check: Checks that LOL is defined.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLDGC willfail during an Update of the Network with the PlannedArea.
4.7.7 TAOL Defined
Rule no: 124
UI Window: Miscellaneous Page 1
Check: Checks that TAOL is defined.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 70 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC and RLDGC willfail during an Update of the Network with the PlannedArea.
4.7.8 Resource Type - Priority Profile Connection
Rule no: 140
UI Window: Miscellaneous Page 3
Check: Checks that the Resource Type (that is, SDCCHOL,TCGFROL, and TCHHROL) connection to a PriorityProfile exists.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: A failure indicates that the command RLPRC will failduring an Update of the Network with the Planned Area.
4.7.9 Supervision of Logical Channel Limit Value for Full Rate TCH
Rule no: 25
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHFR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to an Overlaid Subcell.
The total number of logical TCHs =
+ Sum {over Channel Groups belonging to the OverlaidSubcell}
[+ 8* (The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)]
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
FREEOPEN INFORMATIONTMOS User Guide 71 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.7.10 Supervision of Logical Channel Limit Value for Enhanced FullRate TCH
Rule no: 25
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHEFR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to an Overlaid Subcell.
The total number of logical TCHs =
+ Sum {over Channel Groups belonging to the OverlaidSubcell}
[+ 8*(The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)]
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.7.11 Supervision of Logical Channel Limit Value for Half Rate TCH
Rule no: 25
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for TCHHR" does not ex-ceed the total number of logical TCHs in the set of allthe Channel Groups belonging to an Overlaid Subcell.
The total number of logical TCHs =
+ Sum {over Channel Groups belonging to the OverlaidSubcell}
[+ 8* (The defined number of DCHNOs in the ChannelGroup) - (The defined number of SDCCHs in theChannel Group)]
*2 (that is, maximum value when all channels are halfrate)
Object: Overlaid Subcell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 72 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Overlaid Subcell, CMS40 BSS R4
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.7.12 Supervision of Logical Channel Limit Value for SDCCH
Rule no: 25
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks that the "Limit value for SDCCH" does not ex-ceed the total number of logical SDCCHs in the set of allthe Channel Groups belonging to an Overlaid Subcell.
The total number of logical SDCCHs =
+ Sum {over Channel Groups belonging to the OverlaidSubcell}
[+ 8* (The defined number of SDCCHs in the ChannelGroup)]
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSLC will fail duringan Update of the Network with the Planned Area.
4.7.13 SSLEN and INILEN Parameter Relation
Rule no: 135
UI Window: Miscellaneous Page 2
Check: Checks that INILEN is less than SSLEN.
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 73 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.7.14 INIDES and SSDES Parameter Relation
Rule no: 152
UI Window: Miscellaneous Page 3
Check: Checks that INIDES is less than SSDES.
(Parameters are entered as positive values. The systemchanges the sign of the values for use in thecalculations.)
Object: Overlaid Subcell, CME20 BSS R7
Overlaid Subcell, GSM 900/1800 BSS R8
Overlaid Subcell, CMS40 BSS R4
Overlaid Subcell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies in the ratio be-tween parameter values in the object and issues awarning.
4.8 Check Rules for the Channel Group
4.8.1 Channel Group State
Rule no: 75
UI Window: State in Cells and Channel Groups
Check: Checks that the corresponding Channel Group in theNetwork has been set to the "HALTED" state during anUpdate if the Channel Group belongs to a Planned Area.
A Channel Group which is not already halted has to beset to "HALTED" during an Update if the Channel Groupconnection to a Transceiver Group is changed.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed when Planned Area is se-lected. It detects changed data and generates awarning to the user.
FREEOPEN INFORMATIONTMOS User Guide 74 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.8.2 Channel Group State when Removing DCHNO
Rule no: 151
UI Window: State in Cells and Channel Groups
Check: Checks that the Channel Group status = "HALTED"when all DCHNOs are removed from the ChannelGroup if the Channel Group belongs to a Planned Area.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: A failure indicates that the command RLCFE will failduring an Update of the Network with the Planned Area.
4.8.3 Existence of Transceiver Group Connection
Rule no: 112
UI Window: Miscellaneous Page 1
Check: Checks that a Transceiver Group connection has beendefined for the Channel Group.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.8.4 Minimum Number of DCHNO
Rule no: 28
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that at least one DCHNO is defined in theChannel Group.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 75 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLSTC will fail duringan Update of the Network with the Planned Area.
4.8.5 Uniqueness of DCHNO in the Cell
Rule no: 29
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks for each Channel number in the DCHNO that itis unique in the total set of DCHNOs in all the ChannelGroups belonging to the cell.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCFI and RLDEC willfail during an Update of the Network with the PlannedArea.
4.8.6 Frequency Band for BCCHNO and DCHNO
Rule no: 207
UI Window: Channel Number
Frequency Allocation Page 1
Check: Checks:
- if BCCHNO is in the P band (1 - 124), that allDCHNO in Channel Group 0 are in the P band.
- if BCCHNO is in the P band (1-124) and GPRSSUPis equal to YES, that all DCHNO are in the P band
- if BCCHNO is in the G1 band (0 and 975 - 1,023),that all DCHNO in Channel Group 0 are in the Pband or in the G1 band.
- if BCCHNO is in the G1 band (0 and 975-1023)and GPRSSUP is equal to YES, that all DCHNO arein the P band or in the G1 band
FREEOPEN INFORMATIONTMOS User Guide 76 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 1900 BSS R8
Comments: A failure indicates that the command RLCFI will failduring an Update of the Network with the PlannedArea.
4.8.7 Maximum Number of SDCCH
Rule no: 30
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that the number of SDCCH + 1, for time slot 0in the BCCHNO, does not exceed the defined number ofDCHNO if the Channel Group = 0 and if TN = 0.
Checks that the number of SDCCH is less than orequals DCHNO if the Channel Group is not 0, or if theChannel Group = 0 and TN is not 0.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCCC and RLCFE willfail during an Update of the Network with the PlannedArea.
4.8.8 Maximum Number of CBCH
Rule no: 31
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that SDCCH equals or exceeds 1 if CBCH =YES, if the Channel Group belongs to an Internal Cell oran Underlaid Subcell.
Object: Channel Group, CME20 BSS R7
Channel Group, GSM 900/1800 BSS R8
Channel Group, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 77 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Channel Group, GSM 1900 BSS R8
Comments: This check is only performed on a Planned Area. A fail-ure indicates that the command RLCCC will fail duringan Update of the Network with the Planned Area.
4.9 Check Rules for the External Cell
4.9.1 Lacking Internal Cell or Foreign Cell in the Area
Rule no: 125
UI Window: Miscellaneous Page 2
Check: Checks that there is an Internal Cell or a Foreign Cellwith the same cell name within the area.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.9.2 CGI in Corresponding Internal Cell or Foreign Cell
Rule no: 10
UI Window: Cell Global Identity
Check: Checks that CGI is defined and identical in thecorresponding Internal Cell or Foreign Cell.
Checks that CGI in the External Cell, if defined, is iden-tical to CGI in the corresponding Internal Cell or ForeignCell if there is a corresponding Internal Cell or ForeignCell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Net work with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
FREEOPEN INFORMATIONTMOS User Guide 78 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.9.3 Uniqueness of External Cell CGI in the BSC
Rule no: 11
UI Window: Cell Global Identity
Check: Checks that the External Cell CGI, if defined, is uniquein the set of Internal and External Cells within the BSC.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is included in the Consistency Check onlywhen the current selection for Consistency Check is anMSC or a BSC.
This check is only performed on a Planned Area. A fail-ure indicates that the command RLDEC will fail duringan Update of the Network with the Planned Area.
4.9.4 Superfluous External Cell
Rule no: 90
UI Window: BSC
Check: Checks that the External Cell has at least oneNeighbour Relation in the BSC.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.9.5 Cell System Type, External Cell - Internal/Foreign Cell
Rule no: 141
UI Window: Miscellaneous Page 3
Check: Checks that the Cell System Type parameter is identi-cal in both cells if there is a corresponding Internal Cellor Foreign Cell.
Object: External Cell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 79 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: A failure indicates that the command RLDEI will failduring an Update of the Network with the Planned Area.
4.9.6 LAYER Defined and Identical in Corresponding Cells
Rule no: 126
UI Window: Miscellaneous Page 2
Check: Checks that LAYER, if defined, is identical to LAYER inthe corresponding Internal Cell or Foreign Cell if there isa corresponding Internal Cell or Foreign Cell.
Note: R7/R4 cells have 1-3 LEVELs.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.9.7 BSIC Defined and Identical in Corresponding Cells
Rule no: 115
UI Window: Miscellaneous Page 1
Check: Checks that both NCC and BCC are defined.
Checks that NCC and BCC, if defined, are identical toNCC and BCC in the corresponding Internal Cell or For-eign Cell if there is a corresponding Internal Cell orForeign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 80 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.8 BCCHNO Defined and Identical in Corresponding Cells
Rule no: 32
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that BCCHNO is defined.
Checks that BCCHNO, if defined, is identical to BC-CHNO in the corresponding Internal Cell or Foreign Cellif there is a corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.9 BSPWR Defined and Identical in Corresponding Cells
Rule no: 56
UI Window: Power Page 2
Check: Checks that BSPWR is defined.
Checks that BSPWR, if defined, is identical to BSPWRin the corresponding Internal Cell or Foreign Cell if thereis a corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 81 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.10 BSTXPWR Defined and Identical in Corresponding Cells
Rule no: 57
UI Window: Power Page 2
Check: Checks that BSTXPWR is defined.
Checks that BSTXPWR, if defined, is identical to BSTX-PWR in the corresponding Internal Cell or Foreign Cell ifthere is a corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.11 MSTXPWR Defined and Identical in Corresponding Cells
Rule no: 58
UI Window: Power Page 2
Check: Checks that MSTXPWR is defined.
Checks that MSTXPWR, if defined, is identical to MSTX-PWR in the corresponding Internal Cell or Foreign Cellif there is a corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 82 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.12 BSRXMIN Defined and Identical in Corresponding Cells
Rule no: 59
UI Window: Power Page 2
Check: Checks that BSRXMIN is defined.
Checks that BSRXMIN, if defined, is identical toBSRXMIN in the corresponding Internal Cell or ForeignCell if there is a corresponding Internal Cell or ForeignCell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.13 BSRXSUFF Defined and Identical in Corresponding Cells
Rule no: 60
UI Window: Power Page 2
Check: Checks that BSRXSUFF is defined.
Checks:
- if the corresponding cell is an Internal Cell and EVAL-TYPE = 1 in its BSC that BSRXSUFF = BSRXSUFF inthe Internal Cell
- if the corresponding cell is a Foreign Cell thatBSRXSUFF = BSRXSUFF in the Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
FREEOPEN INFORMATIONTMOS User Guide 83 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.14 MSRXMIN Defined and Identical in Corresponding Cells
Rule no: 61
UI Window: Power Page 2
Check: Checks that MSRXMIN is defined.
Checks that MSRXMIN, if defined, is identical toMSRXMIN in the corresponding Internal Cell or ForeignCell if there is a corresponding Internal Cell or ForeignCell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Net work with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.15 MSRXSUFF Defined and Identical in Corresponding Cells
Rule no: 62
UI Window: Power Page 2
Check: Checks that MSRXSUFF is defined.
Checks:
- if the corresponding cell is an Internal Cell and EVAL-TYPE = 1 in its BSC, that MSRXSUFF = MSRXSUFF inthe Internal Cell.
- if the corresponding cell is a Foreign Cell, thatMSRXSUFF = MSRXSUFF in the Foreign Cell.
Object: External Cell, CME20 BSS R7
FREEOPEN INFORMATIONTMOS User Guide 84 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check is performed on a Planned Area. A failureindicates that the command RLNRI will fail during anUpdate of the Network with the Planned Area. It alsodetects any inconsistencies between data in differentobjects.
4.9.16 MISSNM Defined and Identical in Corresponding Cells
Rule no: 127
UI Window: Miscellaneous Page 2
Check: Checks that MISSNM, if defined, is identical to MISSNMin the corresponding Internal Cell or Foreign Cell if thereis a corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.9.17 AW Defined and Identical in Corresponding Cells
Rule no: 128
UI Window: Miscellaneous Page 2
Check: Checks that AW, if defined, is identical to AW in the cor-responding Internal Cell or Foreign Cell if there is acorresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 85 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.9.18 SCHO Defined and Identical in Corresponding Cells
Rule no: 129
UI Window: Miscellaneous Page 2
Check: Checks that SCHO, if defined, is identical to SCHO inthe corresponding Internal Cell or Foreign Cell if there isa corresponding Internal Cell or Foreign Cell.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.9.19 EXTPEN Value
Rule no: 150
UI Window: Miscellaneous Page 3
Check: Checks in the External Cell that EXTPEN = ON whenthe corresponding cell is an Internal Cell connected to aBSC of Ericsson type.
Object: External Cell, CME20 BSS R7
External Cell, GSM 900/1800 BSS R8
External Cell, CMS40 BSS R4
External Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10 Check Rules for the Neighbour Relation
4.10.1 Lacking Related Inner Cell or Outer Cell in the MSC
Rule no: 108
UI Window: MSC
Check: Checks that there is an Inner Cell or an Outer Cell withthe same name as the Neighbouring Cell belonging tothe same MSC as the BSC to which the NeighbourRelation belongs.
FREEOPEN INFORMATIONTMOS User Guide 86 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10.2 Two-way Neighbour Relations
Rule no: 81
UI Window: Neighbour Relations
Check: Checks that the Internal Cell is a Neighbour to all itsNeighbouring Cells. This is checked for all the InternalCells Neighbouring Cells, except those that are handledas Foreign Cells.
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10.3 Consistency of Neighbour Relations Data
Rule no: 82
UI Window: Neighbour Relations
Check: If EVALTYPE = 1 in the BSC, checks the values ofthe following parameters in the Neighbour Relation inthe opposite direction:
KHYST = KHYST
LHYST = LHYST
TRHYST = TRHYST
KOFFSET = - KOFFSET
LOFFSET = - LOFFSET
TROFFSET = - TROFFSET
FREEOPEN INFORMATIONTMOS User Guide 87 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
AWOFFSET = AWOFFSET
BQOFFSET = BQOFFSET
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between datain different objects.
4.10.4 KHYST and LHYST Parameter Relation
Rule no: 84
UI Window: Neighbour Relations
Check: Checks that KHYST is less than or equals LHYST whenEVALTYPE = 1.
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10.5 AWOFFSET and KHYST or AWOFFSET and LHYST ParameterRelation
Rule no: 86
UI Window: Neighbour Relations
Check: Checks that AWOFFSET equals or exceeds KHYST orthat AWOFFSET equals or exceeds LHYST whenEVALTYPE = 1.
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
FREEOPEN INFORMATIONTMOS User Guide 88 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10.6 BQOFFSET and KHYST or BQOFFSET and LHYST ParameterRelation
Rule no: 85
UI Window: Neighbour Relations
Check: Checks that BQOFFSET equals or exceeds KHYST orthat BQOFFSET equals or exceeds LHYST whenEVALTYPE = 1.
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.10.7 COSITE for Neighbours
Rule no: 134
UI Window: Miscellaneous Page 2
Check: Checks that COSITE (CS) = YES when the Internal Celland its neighbouring Overlaid Subcell is connected tothe same Site and NO or Undefined if the cells areconnected to different Sites.
Object: Neighbour Relation, CME20 BSS R7
Neighbour Relation, GSM 900/1800 BSS R8
Neighbour Relation, CMS40 BSS R4
Neighbour Relation, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 89 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.11 Check Rules for the Transceiver Group
4.11.1 Superfluous Transceiver Group
Rule no: 130
UI Window: Miscellaneous Page 2
Check: Checks that at least one Channel Group in the BSC hasbeen connected to the Transceiver Group.
Object: Transceiver Group, CME20 BSS R7
Transceiver Group, GSM 900/1800 BSS R8
Transceiver Group, CMS40 BSS R4
Transceiver Group, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.11.2 BSPWRB and BSPWRT Defined and within Connected TGCapability
Rule no: 40
UI Window: Power Page 1
Check: Checks that the value of the BSPWRB parameter in theInternal Cell and BSPWRT in Internal Cell and OverlaidSubcell can be handled by the RBS hardware which theInternal Cell and Overlaid Subcell is connected to.
(RBS hardware data is available only when BCM isinstalled.)
Object: Transceiver Group, CME20 BSS R7
Transceiver Group, GSM 900/1800 BSS R8
Transceiver Group, CMS40 BSS R4
Transceiver Group, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 90 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.11.3 XRANGE within Connected TG Capability
Rule no: 206
UI Window: Miscellaneous Page 1
Check: Checks that RBS hardware to which the Internal Cell isconnected has capability to support Extended Rangewhen XRANGE = ON in the Internal Cell.
(RBS hardware data is available only when BCM isinstalled.)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.11.4 DCHNO within Connected TG Capability
Rule no: 26
UI Window: Channel Number/Frequency Allocation Page 1
Check: Checks that the minimum and maximum value of theDCHNO parameter in the Channel Group can be han-dled by the RBS hardware to which the Channel Groupis connected.
(RBS hardware data is available only when BCM isinstalled.)
Object: Internal Cell, CME20 BSS R7
Internal Cell, GSM 900/1800 BSS R8
Internal Cell, CMS40 BSS R4
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
FREEOPEN INFORMATIONTMOS User Guide 91 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.11.5 GPRS within Connected TG Capability
Rule no: 209
UI Window: Miscellaneous page 4
Check: Checks that the RBS hardware, to which the InternalCell is connected, has the capability to support GPRSwhen the GPRSSUP parameter is set to YES in theInternal Cell.
(RBS hardware data is available only when BCM isinstalled.)
Object: Internal Cell, GSM 900/1800 BSS R8
Internal Cell, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.12 Check Rules for the Site
4.12.1 Corresponding Valid Area Sites
Rule no: 131
UI Window: Miscellaneous Page 2
Check: Checks for all Sites belonging to the BSC that there arecorresponding Sites in the Valid Area if the BSCbelongs to a Planned Area.
Object: Site, CME20 BSS R7
Site, GSM 900/1800 BSS R8
Site, CMS40 BSS R4
Site, GSM 1900 BSS R8
Comments: This check detects any inconsistencies between data indifferent objects.
4.13 Check Rules for the Foreign Cell
4.13.1 MSC Connection Defined
Rule no: 109
UI Window: MSC
Check: Checks that the MSC connection is defined.
FREEOPEN INFORMATIONTMOS User Guide 92 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
Object: Foreign Cell
Comments: None.
4.13.2 CGI Defined
Rule no: 12
UI Window: Cell Global Identity
Check: Checks that CGI is defined.
Object: Foreign Cell
Comments: None.
4.13.3 Uniqueness of Foreign Cell CGI
Rule no: 13
UI Window: Cell Global Identity
Check: Checks that the Foreign Cell CGI, if defined, is uniquein the set of Foreign Cells.
Object: Foreign Cell
Comments: None.
4.13.4 Superfluous Foreign Cell
Rule no: 132
UI Window: Miscellaneous Page 2
Check: Checks that there is at least one Neighbour Relation inthe area which has the same Related cell name as theForeign Cell name.
Object: Foreign Cell
Comments: None.
4.13.5 BSIC Defined
Rule no: 133
UI Window: Miscellaneous Page 2
Check: Checks that both NCC and BCC are defined.
Object: Foreign Cell
Comments: None.
FREEOPEN INFORMATIONTMOS User Guide 93 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.13.6 BCCHNO Defined
Rule no: 33
UI Window: Channel Number
Frequency Allocation Page 2
Check: Checks that BCCHNO is defined.
Checks that BCCHNO is in the set of DCHNO.
Object: Foreign Cell
Comments: None.
4.13.7 BSPWR Defined
Rule no: 63
UI Window: Power Page 2
Check: Checks that BSPWR is defined.
Object: Foreign Cell
Comments: None.
4.13.8 BSTXPWR Defined
Rule no: 64
UI Window: Power Page 2
Check: Checks that BSTXPWR is defined.
Object: Foreign Cell
Comments: None.
4.13.9 MSTXPWR Defined
Rule no: 65
UI Window: Power Page 2
Check: Checks that MSTXPWR is defined.
Object: Foreign Cell
Comments: None.
FREEOPEN INFORMATIONTMOS User Guide 94 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
4.13.10 BSRXMIN Defined
Rule no: 66
UI Window: Power Page 2
Check: Checks that BSRXMIN is defined.
Object: Foreign Cell
Comments: None.
4.13.11 BSRXSUFF Defined
Rule no: 67
UI Window: Power Page 2
Check: Checks that BSRXSUFF is defined.
Object: Foreign Cell
Comments: None.
4.13.12 MSRXMIN Defined
Rule no: 68
UI Window: Power Page 2
Check: Checks that MSRXMIN is defined.
Object: Foreign Cell
Comments: None.
4.13.13 MSRXSUFF Defined
Rule no: 69
UI Window: Power Page 2
Check: Checks that MSRXSUFF is defined.
Object: Foreign Cell
Comments: None.
FREEOPEN INFORMATIONTMOS User Guide 95 (95)
1999-11-30 B 1/1553-APR 102 56/1A UenDatum — Date Rev Dokumentnr — Document no
E
References
1/1553-APR 102 56/1A CNA User Guide