340651698.

xls

Category

Check Rule

ATM Transport Carrier

Check AAL2 Path Carrier

ATM Transport Carrier

Check SAAL Link Carrier

ATM Transport Carrier

Check IPoA PVC Carrier

IP Link Availability

Check IP Path Availability

IP Link Availability

Check SCTP Link Availability

Redundant Cell

GSM Cell

Redundant Cell

NRNC Cell

12/20/2016

124

340651698.xls

Redundant Cell

LTE Cell

Redundant ATM Transport

Check ATM Port

Redundant ATM Transport

Check ATM Traffic Record

Redundant ATM Transport

Check SAAL Link

Redundant IP Transport

Check IP Port

Redundant IP Transport

Check SCTP Link

Redundant Device IP

Check DEVIP

Redundant Area Information

Check LAC

Redundant Area Information

Redundant Area Information

Check SAC
Check RAC

Redundant Area Information

Check URA

GSMCELL

Check GSMCELL Frequency

GSMCELL

Check GSMCELL and GSMCELL

Consistency

GSMCELL

Check GSMCELL and GCELL Consistency

UMTS Cell Relationship

Check Cell Existence

UMTS Cell Relationship

Check Cell Relationship Existence

UMTS Cell Relationship

Check Consistency for the DC Cell value of

Tcell

UMTS Neighboring Relationship

Check TwinCell Neighboring Reflexivity

12/20/2016

224

340651698.xls

UMTS Neighboring Relationship

Check CellRelation between FDDCELL to

TWINCELL with no BLINDHO

UMTS Neighboring Relationship

Check Unidirectional Intra Neighboring

Relations

UMTS Neighboring Relationship

Check Unidirectional Inter Neighboring

Relations

UMTS Neighboring Relationship

Unidirectional neighboring relation check

between UMTS and GSM network

UMTS Neighboring Relationship

Check Total Number of Intra and Inter

Neighboring Cells for Each UMTS Cell

UMTS Neighboring Relationship

Check Total Number of Intra Neighboring

Cells for Each UMTS Cell

UMTS Neighboring Relationship

Check Total Number of Inter Neighboring

Cells for Each UMTS Cell

UMTS Neighboring Relationship

Check Total Number of Intra Neighboring

Cells with Sib11 Usage for Each UMTS
Cell

UMTS Neighboring Relationship

Check Total Number of Inter Neighboring

Cells with Sib11 Usage for Each UMTS
Cell

UMTS Neighboring Relationship

Check Total Number of GSM Neighboring

Links for Each UMTS Cell

UMTS Neighboring Relationship

Check Intra-frequency Neighboring

Relationship(Total Number Exceeds
31)Validity

UMTS Neighboring Relationship

Check The NIRATOverLap of The GSM

Neighboring Cell

CELLHSPA

Check FddCell with Activated CELLHSPA

CELLHSPA

Check TwinCell with Deactivated

CELLHSPA

12/20/2016

324

340651698.xls

NRNCCELL

Check Existence of NRNCCell

NRNCCELL

Check Consistency of NRNCCell

NRNCCELL

Check CellName Conflict

NRNCCELL

Check NRNCCELL CnOperatorGroup

Consistency

UMTS Neighboring cells distance

Check the distance between UMTS cells

and UMTS cells

UMTS Neighboring cells distance

Check the distance between UMTS cells

and GSM cells

Iub Data Consistency(ATM)

Check Consistency of NCP

Iub Data Consistency(ATM)

Check Consistency of CCP

Iub Data Consistency(ATM)

Check Consistency of ALCAP

Iub Data Consistency(ATM)

Check Consistency of AAL2PATH

12/20/2016

424

340651698.xls

Iub Data Consistency(ATM)

Check Consistency of OMCH

Iub Data Consistency(IP)

Check Consistency of NCP

Iub Data Consistency(IP)

Check Consistency of CCP

Iub Data Consistency(IP)

Check Consistency of IPPATH

Iub Data Consistency(IP)

Check Consistency of OMCH

Iub Data Consistency(IP)

Check Consistency for IPPOOL Network

12/20/2016

524

340651698.xls

Radio Data Consistency

Check Consistency of LOCELL

Check Dynamic Spectrum Sharing

Task

Check DSS Flag

Check Dynamic Spectrum Sharing

Task

Check for Frequency Band Conflict

Check Dynamic Spectrum Sharing

Task

Check Whether GSM BS and UMTS BS in

BS Pair of DSS Task Belong to Same
MBTS

Check Dynamic Spectrum Sharing

Task

Check Parameters Based on UMTS BS

Data

Inter-System Neighboring Relationship

Inter-System UMTS external cell

Consistency check by CGI in UMTS

12/20/2016

624

340651698.xls

Inter-System Neighboring Relationship

Inter-System UMTS external cell

Consistency check by Name in UMTS

Inter-System Neighboring Relationship

Inter-System GSM external cell

Consistency check by CGI in UMTS

Inter-System Neighboring Relationship

Inter-System GSM external cell

Consistency check by Name in UMTS

Inter-System Neighboring Relationship

Inter-System LTE external cell Consistency

check by CGI in UMTS

Inter-System Neighboring Relationship

Inter-System LTE external cell Consistency

check by Name in UMTS

Inter-System Neighboring Relationship

3G-3G Unidirectional Intra neighboring

relationship check in UMTS

Inter-System Neighboring Relationship

3G-3G Unidirectional Inter neighboring

relationship check in UMTS

3G-2G Unidirectional neighboring

relationship check in UMTS
3G-LTE Unidirectional neighboring
Inter-System Neighboring Relationship
relationship check in UMTS
Inter-System Neighboring Relationship

12/20/2016

724

340651698.xls

LTE CELL

Check LTECELL and eNodeB/Cell

Consistency

LTE CELL

Check LTECELL and LTECELL

Consistency

LTE Neighboring Relationship

Unidirectional neighboring relation check

between UMTS and LTE network

12/20/2016

824

340651698.xls

Check the AAL2 paths (AAL2PATH) whose bearers are null, including:
1. AAL2 Paths (AAL2PATHs) configured on Iub adjacent nodes, whose mapping NodeBs are in
ATM mode.
2. AAL2 paths (AAL2PATHs) configured for Iub adjacent nodes, whose NodeBs are in dual-stack
mode and are not configured with IP paths.
3. AAL2 paths (AAL2PATHs) configured for IUCS and Iur adjacent nodes.
4. AAL2 paths (AAL2PATHs) configured for layer 2 adjacent nodes in a cascade. In the cascade,
adjacent nodes in layer 1 are UNI, and adjacent nodes in layer 2 are Iub.
Check all the SAALLNKs whose bearers are null. The objects using SAALLNKS are as follows:
Adjacent Node (ADJNODE) (Iub or UNI), NCP Link (NCP), CCP Link (CCP), and MTP3
Signalling Link (MTP3LNK).
Check the IPOAPVCs whose bearers are null, including:
1. IPOAPVCs used by NODEBIPs in ATM mode
2. IPOAPVCs used by IUPS interfaces
3. IPOAPVCs used by IUBC interfaces and CBSADDRs
In direct connection mode, check:
1. Whether the local and peer IP addresses of the IP path are the same as those of the
MPGrp/PPPlink/IPOAPVC.
2. Whether the local IP address of the IP path is the same as that of the
ETHIP/ETHTRKIP/DEVIP and whether the peer IP address of the IP path is on the same network
segment as that of the IPETHIP/ETHTRKIP.
In route connection mode, check:
1. Whether the IP address of the gateway is the same as the peer IP address of the
MPGrp/PPPLink and whether the local IP address of the IP path is the same as that of PGrp/
PPPlink/IPOAPVC, and whether the peer IP address of the IP path is on the same network
segment as that of the destination IP address of the route.
2. Whether the IP address of the gateway is on the same network segment as the peer IP
address of the IPOA of ETHIP/ETHTRKIP/DEVIP, whether the local IP address of the IP path is
the same as that of the ETHIP/ETHTRKIP, and whether the peer IP address of the IP path is on
the same network segment as the destination IP address of the route.
In direct connection mode, check:
1. Whether the local and peer IP addresses of the SCTP link are the same as those of the
MPGrp/PPPlink.
2. Whether the local IP address of the SCTP link is the same as that of the ETHIP/ETHTRKIP
and whether the peer IP address of the SCTP link is on the same network segment as that of the
ETHIP/ETHTRKIP.
In route connection mode, check:
1. Whether the IP address of the gateway is the same as the peer IP address of the
MPGrp/PPPLink, whether the local IP address of the SCTP link is the same as that of the
MPGrp/ PPPlink, and whether the peer IP address of the SCTP link is on the same network
segment as the destination IP address of the route.
2. Whether the IP address of the gateway is on the same network segment as the peer IP
address of the ETHIP/ETHTRKIP, whether the local IP address of the SCTP link is the same as
that of the ETHIP/ETHTRKIP, and whether the peer IP address of the SCTP link is on the same
network segment as the destination IP address of the route.
Check whether there are any redundant external GSM cells. Redundant external GSM cells are
cells whose neighbor relationships (GSMNCELLs) are not configured.
Check whether there are any redundant external UMTS cells. Redundant external UMTS cells
are cells whose neighbor relationships (INTRAFREQNCELLs/INTERFREQNCELLs) are not
configured or external UMTS cells for GSM.

12/20/2016

924

340651698.xls

Check whether there are any redundant external LTE cells. Redundant external LTE cells are
cells whose neighbor relationships (LTENCELLs) are not configured.
Check whether there are any redundant ATM ports (IMA group, UNI link, and Fractional ATM
link). Redundant ATM ports are the ATM ports that are not used by the following links: AAL2 Path
(AAL2PATH), IPoA PVC (IPOAPVC), SAAL Link (SAALLNK), VPL/VCL Cross-Connects
(VPCLCX) (high end or low end), and ATM Logical Port (ATMLOGICPORT).
Check whether there are any redundant ATM flow indexes. Redundant ATM flow indexes are the
ATM flow indexes that are not used by the following links: AAL2 Path (AAL2PATH), IPoA PVC
(IPOAPVC), SAAL Link (SAALLNK), VPL/VCL Cross-Connects (VPCLCX).
Check whether there are any redundant SAAL links. Redundant SAAL links are the SAAL links
that are not used by the following objects: Adjacent Node (ADJNODE) (Iub or UNI), NCP Link
(NCP), CCP Link (CCP), and MTP3 Signalling Link (MTP3LNK).
Check whether there are any redundant IP ports. Redundant IP ports are the IP ports for
PPPLNKs, MPGRPs, ETHIPs, or ETHTRKIPs that do not carry services.
Check whether there are any SCTP links that are not used by NCP Link (NCP), CCP Link (CCP),
and MTP3 Signalling Link (MTP3LNK).
Check whether a device IP address is used by single objects, such as the IPoA PVC (IPOAPVC),
NodeB Electronic Serial Number (NODEBESN), CBS Address (CBSADDR), IP Path (IPPATH),
and SCTP Link (SCTPLNK). If the device IP address is not used by such single objects, it is
redundant and will be displayed when detected.
Check whether there are any redundant LACs. An LAC is redundant when it meets the following
conditions:
1. This LAC is not used by the Mapping of LAC to SNA (LASNAMAP).
2. This LAC is not used by any cell.
Check whether there are any redundant SACs. An SAC that is not used by any cell is redundant.
Check whether there are any redundant RACs. An RAC that is not used by any cell is redundant.
Check whether there are any redundant URAs. A URA is redundant when it meets the following
conditions:
1. This URA is not used by any Cell URA (CELLURA).
2. This URA is not used by any Neighboring RNC URA (NRNCURA).
Check whether the frequency of a GSM cell is valid. Invalid frequencies are as follows: 0, 125 to
127, 252 to 258, 294 to 305, 341 to 511, and 886 to 954.
Check whether the mapping parameters of external GSM cells of different RNCs are consistent.
The cell global identification (CGI), which consists of the mobile country code (MCC), mobile
network code (MNC), location area code (LAC), and cell identity (CI), is used to map external
GSM cells. Check all the parameters if the RNC versions are the same and check only the public
parameters if the RNC versions are different.
Check whether the mapping parameters of an intra-system external GSM cell on the UMTS
network are consistent with those of a cell on the GSM network. The cell global identification
(CGI), which consists of the mobile country code (MCC), mobile network code (MNC), location
area code (LAC), and cell identity (CI), is used to map external cells. An external GSM cell can
automatically synchronize the mapping parameters with the mapping cell. Inconsistent key
mapping parameters, such as CELLNAME, NCC, BCC, BCCHARFCN, and RAC, affect UE
handovers.
Check whether there are any NodeBs for which no cell is configured. Such NodeBs are
redundant and will be displayed when detected.
Check whether there are any cells configured with no neighboring cells, such as intra-frequency
neighboring cell (INTRAFREQNCELL), inter-frequency neighboring cell (INTERFREQNCELL),
and neighboring GSM cell (GSMNCELL).
Check whether the TCELL parameter is consistent between two DC cells under the same NodeB.
A DC cell is configured on the physical NodeB.
Check the inter-frequency neighbor relationship between a TwinCell and an FDDCell under the
same NodeB.

12/20/2016

1024

340651698.xls

If the blind handover of all inter-frequency neighbor relationships between FDDCells and
TwinCells is False, the neighboring relationship whose NCellID value is the largest will be
displayed.
Check the unidirectional intra-frequency neighbor relationships from cells under an NE to the
cells under a specified NE. For example, cell 2 under NE 2 is configured as the neighboring cell
of cell 1 under NE 1 but cell 1 is not configured as the neighboring cell of cell 2, and the two cells
are intra-frequency neighboring cells. Note that NE 1 and NE2 may be the same.
Check the unidirectional inter-frequency neighbor relationships from cells under an NE to the
cells under a specified NE. For example, Cell 2 under NE 2 is configured as the neighboring cell
of cell 1 under NE 1 but cell 1 is not configured as the neighboring cell of cell 2, and the two cells
are inter-frequency neighboring cells. Note that NE 1 and NE2 may be the same.
Check and add the missing unidirectional neighboring GSM cells. If GSM cell A is a neighboring
cell of UMTS cell B but UMTS cell B is not a neighboring cell of GSM cell A, GSM cell A is a
unidirectional neighboring GSM-UMTS cell of UMTS cell B. UEs can be handed over only from
cell B to cell A but not from cell A to cell B. Too many abnormal unidirectional neighboring cells
affect UE handovers.
Check whether the total number of intra- and inter-frequency neighboring cells configured for a
UMTS cell is correct. The total number is incorrect if it is less than the minimum total number of
intra- and inter-frequency neighboring cells or greater than the maximum total number of intraand inter-frequency neighboring cells. The minimum and maximum numbers can be set in the
Set Number of Neighboring Cells area.
Check whether the number of intra-frequency neighboring cells configured for a UMTS cell is
correct. The number is incorrect if it is less than the minimum number or greater than the
maximum number. The minimum and maximum numbers can be set in the Set Number of
Neighboring Cells area.
Check whether the number of inter-frequency neighboring cells configured for a UMTS cell is
correct. The number is incorrect if it is less than the minimum number or greater than the
maximum number. The minimum and maximum numbers can be set in the Set Number of
Neighboring Cells area.
Check whether the number of intra-frequency neighboring cells (SIB11 configured) configured for
a UMTS cell is correct. The number is incorrect if it is less than the minimum number or greater
than the maximum number. The minimum and maximum numbers can be set in the Set Number
of Neighboring Cells area.
Check whether the number of inter-frequency neighboring cells (SIB11 configured) configured for
a UMTS cell is correct. The number is incorrect if it is less than the minimum number or greater
than the maximum number. The minimum and maximum numbers can be set in the Set Number
of Neighboring Cells area.
Check whether the number of neighboring GSM cells configured for a UMTS cell is correct. The
number is incorrect if it is less than the minimum number or greater than the maximum number.
The minimum and maximum numbers can be set in the Set Number of Neighboring Cells area.
If a UMTS NE is configured with more than 31 intra-frequency neighboring cells, check whether
both the switches HO_INTRA_FREQ_DETSET_INTO_ACTSET_SWITCH and
HO_INTRA_FREQ_DETSET_RPRT_SWITCH are enabled for the HOSWITCH parameter in
UCORRMALGOSWITCH of the UMTS NE. The intra-frequency neighboring cells take effect only
when both switches are enabled.
If DynShutDownType of a cell is set to IRATSHUTDOWN, NIRATOverLap of at least one
neighboring GSM cell of the cell must be set to TRUE.
Check whether there are any FddCells whose HSPA services are active. You can set the
downlink frequency of an FddCell in the Set Downlink Frequency area.
Check whether there are any TwinCells whose HSPA services are inactive. You can set the
downlink frequency of a TwinCell in the Set Downlink Frequency area.

12/20/2016

1124

340651698.xls

Check the NRNCCELL cell of the local RNC under intra- and inter-system NRNCs. If the source
UMTS cell for NRNCCELL does not exist on the NRNCs, NRNCCELL is redundant and displayed
in the detection list. If NRNCID of NRNCCELL does not exist on these NRNCs, the CME does
not check NRNCCELL.
Check whether the parameters the NRNCCELL under the current RNC are consistent with the
parameters of the source UMTS cell under the neighboring RNC. Check all the parameters if the
RNC versions are the same and check only the public parameters if the RNC versions are
different.
Check whether the names of two cells are conflicting:
1. The name of a cell conflicts with the name of its NRNCELL under the same RNC.
2. The cell name under an RNC conflicts with the cell name on a neighboring RNC.
3. The cell name under an RNC conflicts with its NRNCELL name under a neighboring RNC.
4. The NRNCELL name under an RNC conflicts with the NRNCELL cell name under another
RNC. The two RNCs may not be neighboring RNCs.
Check whether the operator groups of neighboring RNC cells are consistent.
Check whether a UMTS cell is too distant from its neighboring UMTS cell. You can set Maximum
Distance of 3G-3G Neighboring Cells in the Set Maximum Distance of Neighboring Cells
area. The longitude and latitude information about cells can be imported as engineering
parameters. If the cell is too distant from its neighboring cell, UE handovers are affected.
Check whether a UMTS cell is too distant from its neighboring GSM cell. You can set Maximum
Distance of 3G-2G Neighboring Cells in the Set Maximum Distance of Neighboring Cells
area. The longitude and latitude information about cells can be imported as engineering
parameters. If the cell is too distant from its neighboring cell, UE handovers are affected.
Check whether the following parameters of the NCP ports that share the same port number are
consistent: Service Type, Peak Cell Rate (PCR), Sustain Cell Rate (SCR), Min Cell Rate (MCR),
Max Burst Size (MBS), Timer CC (CCTM), Timer Poll (POLLTM), Timer Idle (IDLETM), Timer NoResponse (NRTM), Timer Keep-Alive (KATM), Max Connection Control Count(MaxCC), Max Poll
Data Count (MaxPD), Max STAT Count (MaxSTATLE), virtual path identifier (VPI), virtual channel
identifier (VCI), and CarrierType.
Check whether the following parameters of the CCP ports that share the same port number are
consistent: Service Type, Peak Cell Rate (PCR), Sustain Cell Rate (SCR), Min Cell Rate (MCR),
Max Burst Size (MBS), Timer CC(CCTM), Timer Poll (POLLTM), Timer Idle (IDLETM), Timer NoResponse (NRTM), Timer Keep-Alive (KATM), Max Connection Control Count (MaxCC), Max Poll
Data Count (MaxPD), Max STAT Count (MaxSTATLE), virtual path identifier (VPI), virtual channel
identifier (VCI), and CarrierType.
Check the following parameters: ATM Address (NSAP), Service Type, Peak Cell Rate(PCR),
Sustain Cell Rate (SCR), Min Cell Rate(MCR), Max Burst Size (MBS), Timer CC (CCTM), Timer
Poll (POLLTM), Timer Idle (IDLETM), Timer No-Response (NRTM), Timer Keep-Alive (KATM),
Max Connection Control Count (MaxCC), Max Poll Data Count (MaxPD), Max STAT Count
(MaxSTATLE), virtual path identifier (VPI), virtual channel identifier (VCI), and CarrierType.
Check whether the number of IMA links(IMALNKNUM), IMA protocol version(IMAVER), frame
length(FRMLEN), and minimum number of active links(MINLNKNUM) on the RNC are consistent
with those on the NodeB if IMA links are configured.
Check whether the number of E1/T1 timeslots of the FRAATM links(TSBITMAP) on the RNC are
consistent with that on the NodeB if FRAATM links are configured.
Check whether the number of AAL2PATHs on the RNC is consistent with that on the NodeB.
Check whether the following parameters on the RNC are consistent with those on the NodeB:
Service Type(ST), Peak Cell Rate(PCR), Sustain Cell Rate(SCR), Min Cell Rate(MCR), Max
Burst Size(MBS), Cell Delay Variation Tolerance(CDVT), virtual path identifier (VPI), virtual
channel identifier (VCI), and CarrierType.

12/20/2016

1224

340651698.xls

Check the following parameters: RNC IP address, NodeB IP address, Service Type(ST), Peak
Cell Rate(PCR), Sustain Cell Rate(SCR), Min Cell Rate(MCR), Max Burst Size(MBS), Cell Delay
Variation Tolerance(CDVT), virtual path identifier (VPI), virtual channel identifier (VCI), and
CarrierType.
Check the NCP ports that share the same port number. The local IP address of the SCTP link on
the NodeB must be consistent with one of the destination IP addresses (two can be configured)
of the SCTP link on the RNC. The destination IP address of the SCTP link on the NodeB must be
consistent with one of the local IP addresses (two can be configured) of the SCTP link on the
RNC.
The local port of the SCTP link on the NodeB must be consistent with the peer port of the SCTP
link on the RNC. The peer port of the SCTP link on the NodeB must be consistent with the local
port of the SCTP link on the RNC.
Check the CCP ports that share the same port number. The local IP address of the SCTP link on
the NodeB must be consistent with one of the destination IP addresses (two can be configured)
of the SCTP link on the RNC. The destination IP address of the SCTP link on the NodeB must be
consistent with one of the local IP addresses (two can be configured) of the SCTP link on the
RNC.
The local port of the SCTP link on the NodeB must be consistent with the peer port of the SCTP
link on the RNC. The peer port of the SCTP link on the NodeB must be consistent with the local
port of the SCTP link on the RNC.
Check whether the number of IP paths on the NodeB is the same as that on the RNC and
whether the DSCP is consistent.
The local IP address of an IP path on the RNC must be consistent with the peer IP address of the
IP path on the NodeB, and the peer IP address of the IP path on the RNC must be consistent
with the local IP address of the IP path on the NodeB.
Check whether the path type, physical bearer type, and the sending and receiving bandwidths
are consistent with those of the peer end.
If the MP bearer is configured, check whether the local IP address of the IP path (MPIPADDR) on
the RNC is consistent with the peer IP address of the IP path on the NodeB, whether the peer IP
address of the IP path (MPPEERIPADDR) on the RNC is consistent with the local IP address of
the IP path on the NodeB, and check the number of timeslots, settings of IP header compression,
maximum receiving unit, and restart timer are consistent at both ends.
EtherIP is not a negotiated parameter. Its values on the NodeB and RNC are independent of
each other. PPPoE is not a negotiated parameter. PPPoE is used on the NodeB and Ethernet is
used on the RNC.
If the PPP bearer is configured, check whether the local IP address of IP path (PPPIPADDR) on
the RNC is consistent with the peer IP address of the IP path on the NodeB, whether the peer IP
address of the IP path (PPPPEERIPADDR) on the RNC is consistent with the local IP address of
the IP path on the NodeB, and whether the IP header compression is consistent at both ends.
If IP paths are used for interconnection on the NodeB side, the peer IP routes must be reachable
on both RNC and NodeB sides.
If EPs are used for interconnection on the NodeB side, local IP addresses must be available in
the EPs on the NodeB side, which are the same as the corresponding peer IP addresses on the
RNC side. In addition, the peer IP routes must be reachable on both RNC and NodeB sides.
Check whether the local IP address of the OMCH (RNCIP) on the RNC is consistent with the
peer IP address of the OMCH on the NodeB and whether the peer IP address of the OMCH on
the RNC is consistent with the local IP address of the OMCH on the NodeB.
If EPs are used for interconnection on the NodeB side, the peer IP routes must be reachable on
both RNC and NodeB sides.
If IP paths are used for interconnection on the NodeB side, local IP addresses must be available
in the IPPOOLIP list on the RNC side, which are the same as the corresponding peer IP
addresses on the NodeB side. In addition, the peer IP routes must be reachable on both RNC
and NodeB sides.

12/20/2016

1324

340651698.xls

1. If a cell exists on an RNC and a physical NodeB, check whether the uplink frequency, downlink
frequency, and maximum transmit power on the RNC are consistent with those on the NodeB.
2. Check for cells that exist only on the RNC side or NodeB side.
Check whether the dynamic spectrum sharing (DSS) switch of the UMTS is consistent with the
DSS task.
DSS switch is the DSS NodeB Flag of the basic NodeB attributes. If the NodeB is in the DSS
task, the DSS switch should be TRUE. If the NodeB is not in the DSS task, the DSS switch
should be FALSE.
Check whether DSS shared frequencies conflict.
When a DSS task exists, check whether the spectrums shared on the UMTS side are consistent
with the DSS spectrums set in the DSS task.
1. Check whether the pair of GBTS and NodeB in DSS tasks comprises the same co-module
MBTSs:
2. The coverage type in DSS tasks is not Bufferzone.
Check whether the parameters for the DSS shared carriers on the UMTS side are correctly set.
InterFreq Load Handover Method Selection of the DSS cell in the NodeB is set to
MEASUREHO.

Check parameter consistency between a source UMTS cell on an external M2000 and an
external UMTS cell on the local M2000. The cells are identified with RNCID+CELLID.
The parameters to be checked are as follows: Cell Name (CELLNAME), Band Indicator
(BANDIND), UL Frequency Ind (UARFCNUPLINKIND), Uplink UARFCN (UARFCNUPLINK),
Downlink UARFCN (UARFCNDOWNLINK), DL Primary Scrambling Code (PSCRAMBCODE),
Location Area Code (LAC), RAC Configuration Indication (CFGRACIND), Routing area code
(RAC), Cell oriented Cell Individual Offset (CIO), TX Diversity Indication (TXDIVERSITYIND),
STTD Support Indicator (STTDSUPIND), CP1 Support Indicator (CP1SUPIND), Min Quality
Level (QQUALMIN), Min RX level (QRXLEVMIN), Max Allowed UE UL TX Power
(MAXALLOWEDULTXPOWER), Min Rx level Extend Support (QRXLEVMINEXTSUP), Delta Min
Rx level (DELTAQRXLEVMIN), DPCH Tx Diversity Mode for MIMO User
(DPCHDIVMODFORMIMO), FDPCH Tx Diversity Mode for MIMO User
(FDPCHDIVMODFORMIMO), Use of HCS (USEOFHCS), HCS Priority Level (HCSPRIO), Quality
Threshold for HCS Reselection (QHCS), STTD Support Indicator (EFACHSUPIND), VPLimitInd
(VPLIMITIND), DPCH Tx Diversity Mode for Other User (DPCHDIVMODFOROTHER), FDPCH
Tx Diversity Mode for Other User (DPCHDIVMODFOROTHER), Tx Diversity Mode for DCHSDPA User (DIVMODFORDCHSDPA), and Closed Loop Time Adjust Mode
(CLOSEDLOOPTIMEADJUSTMODE).

12/20/2016

1424

340651698.xls

Check parameter consistency between a source UMTS cell on an external M2000 and an
external UMTS cell on the local M2000. The cells are identified with CELLNAME.
The parameters to be checked are as follows: Neighboring RNC ID (RNCID), Cell ID of
Neighboring RNC (CELLID), Band Indicator (BANDIND), UL Frequency Ind
(UARFCNUPLINKIND), Uplink UARFCN (UARFCNUPLINK), Downlink UARFCN
(UARFCNDOWNLINK), DL Primary Scrambling Code (PSCRAMBCODE), Location Area Code
(LAC), RAC Configuration Indication (CFGRACIND), Routing area code (RAC), Cell oriented Cell
Individual Offset (CIO), TX Diversity Indication (TXDIVERSITYIND), STTD Support Indicator
(STTDSUPIND), CP1 Support Indicator (CP1SUPIND), Min Quality Level (QQUALMIN), Min RX
level (QRXLEVMIN), Max Allowed UE UL TX Power (MAXALLOWEDULTXPOWER), Min Rx
level Extend Support (QRXLEVMINEXTSUP), Delta Min Rx level (DELTAQRXLEVMIN), DPCH
Tx Diversity Mode for MIMO User (DPCHDIVMODFORMIMO), FDPCH Tx Diversity Mode for
MIMO User (FDPCHDIVMODFORMIMO), Use of HCS (USEOFHCS), HCS Priority Level
(HCSPRIO), Quality Threshold for HCS Reselection (QHCS), STTD Support Indicator
(EFACHSUPIND), VPLimitInd (VPLIMITIND), DPCH Tx Diversity Mode for Other User
(DPCHDIVMODFOROTHER), FDPCH Tx Diversity Mode for Other User
(DPCHDIVMODFOROTHER), Tx Diversity Mode for DC-HSDPA User (DIVMODFORDCHSDPA),
and Closed Loop Time Adjust Mode (CLOSEDLOOPTIMEADJUSTMODE).
Note: RNC ID (RNCID) and Cell ID of Neighboring RNC (CELLID) cannot be updated.

Check parameter consistency between a source GSM cell on an external M2000 and an external
GSM cell on the local M2000. The cells are identified with MCC+MNC+LAC+CI.
The parameters to be checked are as follows: GSM Cell Name (GSMCELLNAME), Network
Color Code (NCC), BS Color Code (BCC), Inter-RAT Cell Frequency Number (BCCHARFCN),
and Routing area code (RAC).
Check parameter consistency between a source GSM cell on an external M2000 and an external
GSM cell on the local M2000. The cells are identified with CELLNAME.
The parameters to be checked are as follows: Mobile country code (MCC), Mobile network code
(MNC), Location Area Code (LAC), GSM cell ID (CID), Network Color Code (NCC), BS Color
Code (BCC), Inter-RAT Cell Frequency Number (BCCHARFCN), and Routing area code (RAC).
Check parameter consistency between a source LTE cell on an external M2000 and an external
LTE cell on the local M2000. The cells are identified with MCC+MNC+EUTRANCELLID.
The parameters to be checked are as follows: LTE Cell Name (LTECELLNAME), Tracking Area
Code (TAC), LTE Physical Cell Identity (CELLPHYID), LTE Cell Frequency Band (LTEBAND),
LTE Cell Downlink Frequency (LTEARFCN), and LTE Cell Supporting PS HO Indicator
(SUPPPSHOFLAG).
Check parameter consistency between a source LTE cell on an external M2000 and an external
LTE cell on the local M2000. The cells are identified with CELLNAME.
The parameters to be checked are as follows: Mobile country code (MCC), Mobile network code
(MNC), LTE Cell Identity (EUTRANCELLID), Tracking Area Code (TAC), LTE Physical Cell
Identity (CELLPHYID), LTE Cell Frequency Band (LTEBAND), LTE Cell Downlink Frequency
(LTEARFCN), and LTE Cell Supporting PS HO Indicator (SUPPPSHOFLAG).
Check whether there are unidirectional neighbor relationships between intra-frequency
neighboring UMTS cells on the local M2000 and intra-frequency neighboring UMTS cells on an
external M2000.
Check whether there are unidirectional neighbor relationships between inter-frequency
neighboring UMTS cells on the local M2000 and inter-frequency neighboring UMTS cells on an
external M2000.
Check whether there are unidirectional neighbor relationships between UMTS cells on the local
M2000 and GSM cells on an external M2000.
Check whether there are unidirectional neighbor relationships between UMTS cells on the local
M2000 and LTE cells on an external M2000.

12/20/2016

1524

340651698.xls

Check parameter consistency between an external LTE cell and a source LTE cell on the
eNodeB. The cells are identified with MCC+MNC+EUTRANCELLID.
The parameters to be checked are as follows: LTE Cell Name (LTECELLNAME), Tracking Area
Code (TAC), LTE Physical Cell Identity (CELLPHYID), LTE Cell Frequency Band (LTEBAND),
and LTE Cell Downlink Frequency (LTEARFCN).
Check parameter consistency of external LTE cells that are configured on two UMTS NEs. The
cells are identified with MCC+MNC+EUTRANCELLID.
The parameters to be checked are as follows: LTE Cell Name (LTECELLNAME), Tracking Area
Code (TAC), LTE Physical Cell Identity (CELLPHYID), LTE Cell Frequency Band (LTEBAND),
LTE Cell Downlink Frequency (LTEARFCN), LTE Cell Supporting PS HO Indicator
(SUPPPSHOFLAG), and BLACKFLAG (BlackCell List Flag).
Check whether there are unidirectional neighbor relationships between UMTS cells and LTE
cells.

12/20/2016

1624

340651698.xls

Supported
Operation

Edit

Edit

Edit

Edit

Edit

Edit
Edit

12/20/2016

1724

340651698.xls

Edit

Edit

Edit

Edit
Edit
Edit

Edit

Edit
Edit
Edit
Edit

None

None

Autofix

Edit
Edit
Edit
Autofix

12/20/2016

1824

340651698.xls

Autofix

Refresh

Refresh

Refresh

Edit

Edit

Edit

Edit

Edit

Edit

Autofix

Edit
Autofix
Autofix

12/20/2016

1924

340651698.xls

Refresh

Refresh and
modify

Refresh and
modify

None

None

None

None

None

None

None

12/20/2016

2024

340651698.xls

None

None

None

None

None

None

12/20/2016

2124

340651698.xls

None

Autofix

Edit

None

Autofix

Refresh

12/20/2016

2224

340651698.xls

Refresh

Refresh

Refresh

Refresh

Refresh

Refresh

Refresh
Refresh
Refresh

12/20/2016

2324

340651698.xls

Autofix

Edit

Refresh

12/20/2016

2424