Professional Documents
Culture Documents
ZXUR 9000 GSM Data Configuration Guide
ZXUR 9000 GSM Data Configuration Guide
Configuration Guide
About This Document
Summary
Chapter Description
1 Introduction to Quick Data Provides an introduction about quick data configuration.
Configuration
2 Quick Data Configuration Introduces some scenarios of filling in Quick Data
Template Filling Scenarios Configuration Templates.
3 Quick Data Configuration Introduces the specifications of Quick Data Configuration
Template Filling Specifications Templates.
4 Common Ground Data Introduces the method of configuring common ground data.
Configuration Method
5 Common Wireless Data Introduces the method of configuration common radio data
Configuration Method
6 Example for Templates of Typical Provides the example for templates of typical scenarios.
Scenarios
TABLE OF CONTENT
Quick Data Configuration: Type network planning data into an Excel table in a fixed
format and load the whole table into the OMM system so as to add, modify, or delete
data in batch (this Guide deals only with batch-adding).
There are three iBSC quick data configuration templates, which include the following
data:
1. V4_Template_Equipment.xls:
Operator information
ums-clnt\deploy\template\GROUND
ums-clnt\deploy\template\GSM
The basic information of the TemplateInfo sheet includes NE Type, Template Type, Data
Type, etc.
The Index sheet is the index of all sheets in the template, including Sheet Name, Index,
and MEMO
Data related sheets include all sheets related to data in the template.
The fifth row is the data field indication, it indicates the Primary Key and R-W-I (items
required to be filled in).
The first column is the Result column. It is not necessary to fill in this column in the
process of preparing data. This column is used to record the result of loading quick
configuration data in OMM. If the loading succeeds, the OMM will record “Success.” If
the loading fails, the Result column will be exported as the result file.
The second column is the MODIND column. It is the modification indicator, and the value
options are A/D/M/P, which represent Add, Delete, Modify, and Pass. Fill in A for a
newly-added item and D for a deleted item. At present quick data configuration applies
mainly to new commissioning sites. It supports A, D, and P functions, and supports the
M function in some sheets.
This section describes which sheets need to be filled in under different scenarios, such
as, FE Abis, IPOE, IPA, TDMA, and IPGb. The configuration of other scenarios will be
updated later. The quick data configuration supports only SDR base stations, and does
not support V2/V3 base stations. The basic configuration data of BSC and the board
configuration data and radio configuration data for different scenarios should be filled in
according to on-site planning and configuration.
Scene V4_Template_Equipment V4_Template_TransportNetwork
Static Route(Optional)
IP Path Group
FE Abis
SCTP Config(ABIS)
IP Bearer(ABIS)
Static Route(Optional)
IPOE SCTP Config(ABIS)
IP Bearer(ABIS)
Local Office
Interface IP
Local Signaling Points
Service IP
Static Route
Slave or Dsp Service Config
IP Path Group
Adjacent Office(CN)
IPA IP Path(CN)
SCTP Config(CN)
M3uaAs Config(CN)
M3uaRouteSet
MSC Office
Nri(Necessary for FlexA)
Static Route
Interface IP SGSN Office
IPGb
Service IP Ip Gb
Nri(Necessary for FlexGb)
In the IPGb scenario, it is also necessary to configure the PS Support, BVC, RAC fields
and the PS channel in the GGsmCell sheet of the GSM Radio Quick Configuration
Template.
The equipment configuration data, radio planning data, networking data, A/Gb-interface
integration data, A/Gb/Abis-interface transmission resource, and IP planning data of the
office have been acquired,
Tip:
BSCID should be unique in the network. It shall not be the same as other
BSCIDs or RNCIDs.
V4_Template_TransportNetwork.xls:
Perform planning about transmission path group ID: Abis: 1 – 2000, A: 2001 – 2048.
Perform planning about SCTP ID: IPAbis: 1 – 2000, M3UA: 2001 – 2048.
Perform planning about ANEID: Abis: 1 – 2000, A: 2001 – 2048, SGSN: 3001 – 3016.
Perform planning about transmission resources, MP/PPP port (the MP and PPP ports in
the subnets of the same CPU must be unique), local MP/PPP IP, and peer Site IP of
IPOE sites.
Perform planning about the interface board resource, local interface IP, peer Site IP of
the FE sites.
Note:
1. Plan the Path Group ID and ANEID. The value range here is only the recommended
value range, which can avoid the ID conflict between A\Gb\Ater-interface office and Abis-
interface, e.g., on the Abis interface, the Path Group ID and ANEID are planned from 1 to
2000 in sequence, while on the A\Gb interface, the Path Group ID and ANEID are planned
from 2001.
2. In the planning of SCTP ID, it is recommended that IPABIS started from 1, but it is
necessary to reserve the IDs smaller than 2048 for M3UA (in the current version, the M3UA
SCTP ID is restricted to values smaller than 2048.)
Please refer to the next chapter for the detailed steps of filling the quick configuration
templates.
This section introduces the boards that need to be configured in different scenarios, as
shown in the table below.
Board
Full Name Logical Name
Name
ESDBB(STM-1 Abis)
Enhanced SDH Digital Trunk
ESDTG ESDTB(STM-1 Ater)
board GSM version
ESDQB(STM-1 A)
The OMP board must be created firstly, i.e., the OMP information must be filled in the
first row of the Board Config sheet in the quick data configuration template. It is at Slots
7/8 fixedly, in 1+1 backup.
For V4 BSC series, there is only one type of service processing board, i.e., CRP, which
is integrated with the functions of CMP and RUP.
The module No. of OMP is configured as “1,” the CMP module No. of the CRP board is
configured as the planned module No., and the module Nos. of other boards are all
configured as “0.”
Note:
When the physical board type is USP and TDMA networking is used on the A interface,
CRP is configured with three CMP modules.
When the physical board type is USP and IPA networking is used on the A interface, CRP is
configured with two CMP modules.
Considering that TDMA may be replaced by IPA later, we recommend that 2-CMP module
configuration of IPA be used in all projects.
1.3.2 RUP (User-plane IP) Configuration Planning Advices
CRP is the only CS/PS user-plane service processing board in the IPA+IPAbis scenario.
Only in the TDMA+IPAbis scenario (built-in TC) will ETCB act as the CS service
processing board and CRP act the PS service processing board.
In V3 BSC, it is only necessary to apply for the user-plane service processing IP for IPA.
This IP needs to be bound with AIPB to allocate UDP port resources. In V4 BSC,
besides IPA, it is also necessary to apply for the user-plane service processing IP for
IPAbis. This IP and IPA's user-plane service processing IP need to be bound with CRP
to allocate UDP port resources.
For the TDMA+IPAbis scenario, it is not only necessary to bind CRP with the IPAbis
user-plane service IP, but also bind ETCB with the IPAbis user-plane IP for processing
CS services.
The user-plane service processing IPs should be visible to the corresponding adjacent
office, i.e., the SDR base stations of adjacent offices on the Abis interface can access
IPAbis’ user-plane IP, the MGW of the adjacent offices on the A interface can access
IPA’s user-plane IP, and the SGSN of the adjacent offices on the Gb interface can
access IPGb’s service IP.
The user-plane processing resources use load sharing between the master/slave CRPs.
RUP Slave Qty on single CRP board under IPA and TDMA
USP 6 8
USP2a 12 16
TDM A+IPAbis scenario: IP Abis address falls into two types, i.e., every two ETCBs can
share one IP Abis address (Support Abis_CS interface), the two ETCBs starting from the
third one should be bound with the second IP Abis address, and so on. Every four USPs
or 2 USP2as can share one IP Abis address (Support Abis_CS interface and Abis_PS
interface),. In template, each CRP should be configured with one record, and each
ETCB should be configured with one record.
Tip:
The IPA/IPAbis addresses here are user-plane loop-back addresses, which need to be defined
in the Interface IP sheet. Meanwhile, it is necessary to define the port attributes of these user-
plane IPs in the Service IP sheet, and then bind these IP addresses with CRP/ETCB in the
Slave or Dsp Service Config sheet. Refer to the template filling instructions in the following
sections.
2. TDM A-interface data configuration advices: The value range of ANEID is 2001-
2048. The Linkset type should be configured as 64 K or 2 M according to the data
configuration provided by MSS, and Linkset ID should be numbered from 1. The
number of Links should be configured evenly among the physical CRPs (CMPs)
first and then allocated evenly among the modules. Mtp3 route is numbered from 1.
Office ID, MSC ID, and MSC CN ID are numbered from 1.
3. IP Gb-interface data configuration advices: ANEID starts from 3001. The paths are
allocated evenly to the modules of different CMPs. The value range of SGSN ID
and SGSN CN ID is 1 – 7.
4. TDM Gb-interface data configuration advices: ANEID starts from 3001. The paths
are allocated evenly to the modules of different CMPs. The value range of SGSN
ID and SGSN CN ID is 1 – 7.
Each site is configured with one adjacent office, one transmission path group, one
logical transmission path, and one SCTP. The adjacent office ID, transmission path
group ID, SCTP ID, remote port No., and local port No. should all be set as Site ID. Site
IP is 118.18.siteid.100, and the IP of the corresponding interface is 118.18.siteid.254.
ML-PPP port No. is the No. of the first E1 used by the base station.
BSC control-plane service flow ends on the CMP module of BSC. It is recommended
configuring two control-plane IPs on the A interface, thus, when an IP becomes invalid,
the system will switch to the other IP. In this case, the multi-homing SCTP mode needs
to be used. In the multi-homing mode, the data is received on the first pair of IP. When
the first pair of IP becomes invalid, it will be switched to the second pair. This is called
SCTP multi-homing.
IP Port IP Port
Because BSC does not support multi-path base station, it is not recommended using
SCTP multi-homing in single transmission path scenario. Currently, select the first
IPAbis user-plane loop-back address and use it as the base station SCTP IP and the
OMCB channel maintenance IP unless otherwise required.
For IPGb, the control plane IP and the user plane IP are the same and they cannot be
set separately. Usually, it is recommended that two service IPs be allocated to the PS
domain. For the IP Gb interface board EGPB, it is recommended using no-backup
networking.
The prerequisites for loading quick configuration data are that both Subnet and Managed
Element have been created and that the three quick data configuration templates are
filled completely according to the planning data and template filling specifications. The
sequence of importing templates is: V4_Template_Equipment->
V4_Template_TransportNetwork-> GSM Radio Quick Configuration Template.
Set SubNetwork ID, which is the same as the planned BSC ID.
Input the planned MCC and click the Save button to finish the subnetwork creation.
Set Managed Element IP Address to “129.0.1.1” fixedly, and click the Save button to
finish the creation of BSC Managed Element.
5. In the process of importing the quick configuration data, the Importing Progress
column shows the import progress of the sheets and the Result column shows the
import result (the number of items imported successfully/the total number of the
items).
6. After the loading of quick configuration data finishes, whether the quick
configuration data is imported successfully and the storage path (at the same
directory level as the imported quick configuration template) of the generated result
file are displayed at the lower part of the window. Open the import result file to
check the detailed result. If the loading fails, an “Error Information” sheet will be
added, which records all sheets that fail to be loaded. Click a specific sheet and
check the Result field to see the details. In this field, the value for the loaded
sheets is Success and the value of MODIND will change to “P (Pass),” while the
error information for unloaded sheets will be displayed and the value of MODIND is
still "A (Add).” We can modify and save the items with error information in the result
file, and then load it again as a quick data configuration template.
7. After the quick configuration data is imported into OMMR, the configuration data is
displayed in the Modify Area of Configuration Management. After all-data
synchronization or modified-data synchronization is performed, a Snapshot Area
will be generated with the copy of the configuration data, i.e., the data in the
Snapshot Area is consistent with the BSC configuration data after the last data
synchronization. The data configuration, either by importing quick configuration
template or by GUI, is performed in the Snapshot Area. Only the configuration
data synchronized last time can be viewed in the Snapshot Area, but it cannot be
modified.
2 Quick Data Configuration Template
Filling Scenarios
This section describes the data that must be configured in initial BSC commissioning. If
the integration parameters of the A/Gb/Abis interface cannot be acquired temporarily,
configure the basic data of BSC first, and synchronize the data to BSC to finish BSC
boards power-on, commissioning, and other preparations (refer to the BSC
Commissioning Guide for details). Then, configure integration parameters and perform
integration commissioning of the interfaces after acquiring the integration planning data.
Basic Info: Configure the basic information of the global office, including the
operation & maintenance IP, logserver IP, etc.
Note:
Compared with V6.50.10*, the main differences of board configuration in V6.50.20* are as
listed below:
Each CRP pair can be configured with two to three CMP modules. In different scenarios, the
number of modules that need to be configured is different. Refer to Section 1.3.1 for details.
Two-module IPA networking should be used no matter what networking mode is used on the
A interface. Each module supports a maximum of 512 TRXs and 256 cells. Each CRP has
eight Slaves. The Slaves on CRP can process CS services and PS services simultaneously.
Board Config: Configure board information (refer to the Board Warehouse sheet).
IP related configuration is used mainly to configure the interface IPs of the IP interface
boards, control plane and user plane loopback IP, and virtual interface IP.
It defines the service interface type of user-plane loopback IPs, and binds the IPs with
the user-plane resource boards CRP/ETCB, so as to allocate UDP port resources. For
different IP types, the sheets involved are different (V3_Template_Equipment template),
as detailed below:
1. IP interface configuration
2. Service IP address
Interface IP: Configure the service interface type of the user-plane loopback IP of
IP A, IP Gb, IPOE Abis, and IP Abis.
The A interface can be divided into two types based on the transmission type on the A
interface, i.e., IP A and TDM A. The integration parameters are as listed in the following
tables:
TransportNetwork-->Adjacent
Protocol Type CHINA / ITU / ANSI
Office(CN)--> PROTOCOLTYPE
TransportNetwork-->Static Route--
IP address of User-plane service IP of >ROUTEPREFIX;
MGW MGW TransportNetwork-->IP Path(CN)-->
DESTIPADDR
iBSC control-
IP interface board IP,
plane real Equipment-->Interface IP--> IPADDR
connected to MSC
interface IP
iBSC user-
IP interface board IP,
plane real Equipment-->Interface IP--> IPADDR
connected to MGW
interface IP
Equipment-->Interface IP-->
iBSC control-
iBSC Control-plane service IPADDR;
plane
IP, ASP peer-end IP. TransportNetwork-->SCTP
loopback IP
Config(CN)-->LOCADDR
Equipment-->Interface IP—
>IPADDR;
iBSC user-
iBSC user-plane service IP, Equipment-->Service IP-->
plane
used by AIPB DSP SERVICEIP;
loopback IP
Equipment--> Slave or Dsp Service
Config--> SERVICEIP
SCTP local
TransportNetwork-->SCTP
end port
Config(CN)-->LOCPORT
number
SCTP peer
TransportNetwork-->SCTP
end port
Config(CN)-->REMPORT
number
Application
TransportNetwork-->SCTP
type of Client/Server
Config(CN)-->PROPERTY
association
TransportNetwork-->M3uaAS
Config-->EXISTLOCALCONTEXT;
“Whether exists routing
TransportNetwork-->M3uaAS
context”
Whether Config-->LOCALCONTEXT;
Value range: YES/NO
context exists TransportNetwork-->M3uaAS
If YES is filled in, the routing
Config-->EXISTPEERCONTEXT;
text needs to be filled in.
TransportNetwork-->M3uaAS
Config-->PEERCONTEXT
TransportNetwork-->M3uaAS
Override/Loadshare Config-->ASMODE;
AS traffic If the Loadshare mode is TransportNetwork-->M3uaAS
mode used, MODEN/MODEK Config-->MODEN;
needs also be configured. TransportNetwork-->M3uaAS
Config-->MODEK
M3UA TransportNetwork-->M3uaRoute--
M3UA route sequence
ROUTEMODE >ROUTEMODE
TransportNetwork-->Adjacent
SSF Sub-service field (SSF)
Office(CN)-->SSF
Signaling TransportNetwork-->Adjacent
CHINA / ITU / ANSI
protocol type Office(CN)--> PROTOCOLTYPE
TransportNetwork-->No.7 PCM--
No.7 PCM SN CIC
>N7PCM
TransportNetwork--> Mtp2Link
SLC Signaling link code (SLC)
-->SLC
TransportNetwork--> Mtp2Link
TS SS7 link TS
-->TS
LECM (Link
Usually the basic error
Error TransportNetwork--> Mtp2Link--
correction method is
Correction >LECM
adopted.
Method)
LINKTYPE
TransportNetwork--> Mtp2Link--
(Signaling Link 64K / n*64K / 2M
>LINKTYPE
Group Type)
Nri: To configure the MSC NRI in the FlexA scenario. The configuration is not needed in
the non-FlexA scenario.
IP A integration configuration (make sure the required IP has been configured in the IP
related sheets in the V4_Template_Equipment template):
The Gb interface can be divided into two types based on the transmission type on the
Gb interface, i.e., IP Gb and E1 Gb. The integration parameters are as listed in the
following tables:
Table 2-3 IP Gb-interface Integration Parameters
It should be
Network Service
consistent with the
Entity Identifier TransportNetwork-->Ip Gb-->NSEID
configuration at
(NSE ID)
SGSN.
Static/Dynamic
configuration; If
Subnet dynamic configuration
TransportNetwork-->Ip Gb--
Configuration is selected, the preset
>SNCFGTYPE
Type SGSN IP address
needs to be
configured.
Static Configuration:
Configuration of Peer endpoint IP and
TransportNetwork-->Ip Gb-->IPADDRESS
peer end point UDP port number
TransportNetwork-->Ip Gb-->UDPPORT
Signaling
TransportNetwork-->Ip Gb-->SIGWEIGHT
weight
TransportNetwork-->Ip Gb--
Data weight
>DATAWEIGHT
The pre-
Use this parameter
configured TransportNetwork-->Ip Gb--
when dynamic NSEI
SGSN IP >SGSNIPADDRESS
is used.
Address
It should be
Network Service
consistent with the
Entity Identifier TransportNetwork-->Fr Gb-->NSEID
configuration at
(NSEI)
SGSN.
It should be
Bearer Chanel consistent with the TransportNetwork-->Fr Gb-->STARTTS
(BRCH) timeslot No. configuration at TransportNetwork-->Fr Gb-->AR
SGSN.
It should be
Network Service
consistent with the
Virtual Connection TransportNetwork-->Fr Gb-->NSVCID
configuration at
Identifier (NSVCI)
SGSN.
It should be
Digital Link
consistent with the
Connection Identifier TransportNetwork-->Fr Gb-->DLCI
configuration at
(DLCI)
SGSN.
IP Gb integration (make sure the related IP has been configured in the IP related sheets
in the V4_Template_Equipment template):
E1 Gb interface:
For IP Abis sites, it is necessary to the real interface IP of the interface boards. This is
not needed for IPOE sites.
For both IPOE Abis and IP Abis sites, it is necessary to configure service IP for
processing CS&PS services.
V4_Template_Equipment template:
Interface IP: configure the IPOE Abis/IP Abis service IP as the loopback interface.
Service IP: configure the interface attributes of the IPOE Abis/IP Abis service IP.
Slave or Dsp Service Config: Configure and bind service IPs for user-plane service
processing boards.
V4_Template_TransportNetwork template:
The IP Path Group sheet and the IP Bearer (ABIS) sheet are required to be configured
for the ground resource of the sites with IP transmission.
IP Path Group: configure the transmission path group of the sites with IP
transmission
IP Bearer (ABIS): configure the office information of the sites with IP transmission
NEID Site ID
For the ground resource of IPOE transmission sites, it is only necessary to configure the
IP Bearer (ABIS) sheet, and the transmission path group related information will be
generated automatically. Besides, if there is transparent channel, the Lucent Channel
sheet needs also to be configured.
NEID Site ID
Additional remarks:
1. The MPLINK of all IPOE sites is required to be set to MP, and the IP header
compression function should be enabled. This parameter applies only to OMMR.
This function should also be configured on the SDR base station, and it is valid only
when the switch is enabled on both OMMR and OMMB. Refer to OMMB related
parameter configuration guide.
Radio resources are configured in the GSM Radio Quick Configuration Template).
The basic parameters to be planned and the corresponding sheets are as shown in the
following table.
Parameter Name Location in Quick Configuration Template
CI GSM_Radio--> GGsmCell-->cellIdentity
6. The items in the following sheets can only be modified, but cannot be added or
deleted. The default values will be generated in the template creation process (field
engineers can export the quick configuration template and modify the parameters
according to actual requirements).
Each sheet is attached with the corresponding OMM screenshots for reference, but not
all screenshots are provided. The OMM screenshots corresponding to quick
configuration templates are not included in this Guide.
3.1 V4_Template_Equipment
Configure the basic information of the bureau, including the operation & maintenance IP,
logserver IP, etc.
Parameter Name Parameter Description
Fill in the planned BSCID. Fill in the BSCID for MEID in all
MEID
the sheets.
MODETYPE 3: GSM
On the topology tree on the upper left of the Configuration Management window,
select SubNetwork > ME > Modify Area, and the configuration directory will be
displayed on the lower part.
Select Managed Element > System Global Configuration > Operation Maintenance
Configuration > Basic Info.
Note: In the following sections, only the description about the location on the OMMR
interface is provided, and the screenshots are omitted.
MNCBCDCODELEN Default: 2
DEFAULTPLMNIND Default: 1
ISLOCALPLMN Default: 1
This sheet is used to configure V4 BSC rack and shelf, and fill in one record for each
shelf. V4 BSC shelf Nos. are 1, 2, 3 from up down. CDM DIP and Shelf No. are set in
factory setting. Shelf 3 is the master shelf by default and is required to be configured.
Shelf 1 and shelf 2 are slave shelves. They should be configured with one (only one)
master shelf. The concepts of master/slave shelves in V4 BSC are different from the
concepts of control shelf, resource shelf, and switch shelf. Except OMM and OMP, which
must be configured to the master shelf, the processing boards and interface boards of
other interfaces can be configured to any shelf.
For an experimental site or in the scenario where GSM and other products share a
single shelf under a rack, Shelf 1 or Shelf 2 may be used as the master shelf. In this
case, it is necessary to check the CDM configuration of the shelf.
Parameter Name Parameter Description
Create related boards according to the BSC configuration actually planned. OMM, OMP,
EGBS, and EGFS must be configured to fixed slots. The slots of other interface boards
and processing boards can either be configured according to pre-sales planning or be
adjusted as needed.
In V4 BSC, CRP/ETCB must be configured to the front slots 1-14, while
EGPB/EDTI/ESDTI must be configured to rear slots 15~28.
Parameter Name Parameter Description
MODETYPE 1:2G
For the board providing optical ports, if the optical ports are not in backup
configuration, do not configure intra-board protection. Enable the four optical ports
as the working ports. If the ports are in 1:1 backup, configure inter-board protection,
and enable four optical ports for each board. The default setting of the working port
protection is (1,1), (2,2), (3,3), or (4,4).
2. In the process of creating Board object on GUI, set Object ID as Slot No.
3. In the process of creating Board object on GUI, it is not necessary to fill in the
Module No. of the unit. Except OMM/OMP/CRP, other boards are managed by the
OMP module fixedly (Module 1). Do not mix the Module No. here with the board
module No. in the quick configuration template.
4. Both the physical type and the logical type of all boards can be searched in the
Board Warehouse sheet. This sheet is a static board type sheet, and is used as a
query sheet. It does not need to be filled in or modified.
Managed Element > Equipment > Rack > Shelf > Board
3.1.5 Interface IP
This sheet is used to configure the real interface IP, control-plane and user-plane
loopback IP, the virtual gateway (OMP IP) of OMCB operation and maintenance
channel, and the LMT forwarding virtual IP in the IPA/IPGb/FE Abis/IPOE scenario.
The OMP IP needs to be used as the gateway address when the route from OMMB to
SDR is added on OMM server. Meanwhile, it is necessary to configure OMP address as
the virtual interface in the Interface IP sheet. Otherwise, the link of the SDR site cannot
be established in OMCB.
Parameter Name Parameter Description
Managed Element > Transport Network > IP Configuration > IP Interfaces Configuration
3.1.6 Service IP
In the Interface IP sheet, the user-plane IPs configured on the A/Abis/Gb interface are
called loopback IP addresses. They cannot be distinguished in the service process, and
it is necessary to define the interface property for all the user-plane addresses in this
sheet. The service IP of each user plane is configured in a dedicated row.
Parameter Name Parameter Description
The A-interface and Abis_CS\Abis_PS cannot share user-plane service IPs, i.e., the A
interface uses the A-interface loopback address as the user-plane service IP, and
Abis_CS\Abis_PS uses the IPAbis loopback address as the user-plane service IP.
As to the user-plane IP planning rules, refer to Section 1.3.2 RUP (User-plane IP)
Configuration Planning Advices for details.
When the user-plane service IP is shared or is used by only one interface, the
configuration of Slave or Dsp Service Config is different, as detailed in the next section.
Location on OMMR interface:
Managed Element > Transport Network > User Plane Service Configuration > Service IP
Configuration
The configuration of this sheet is similar to the IPA scenario that V3 BSC needs to
allocation the IP+UDP port to AIPB (the IP here is A-interface user-plane IP).
BSCV4 allocates the IP+UDP port resource for the service processing board RUP in the
IPA+IPAbis scenario (The IP here is the user-plane loopback port address defined with
attributes in the sheet of Service IP. Besides the user-plane loopback port IP for A
interface, another user-plane loopback port IP for Abis interface needs to be allocated.
BSCV4 can just allocate one user-plane loopback port IP to be shared by A interface
and Abis interface.); one set of (or one) IP added to each RUP board should be
configured in a separate record line. In this scenario, the IP+UDP port resource is not
required to be allocated for ETCB.
If BSCV4 also allocates the IP+UDP port resource for the PS service processing board
CRP and the CS service processing board ETCB in the TDMA+IPAbis scenario (The
resource allocated to CRP is the Abis_CS+Abis_PS user-plane loopback port IP. Each
Abis_CS+Abis_PS user-plane loopback port IP can be configured with four CRP boards
(or two USP2a boards). The resource allocated to ETCB is the Abis_CS user-plane
loopback port IP. Each Abis_CS user-plane loopback port IP can be configured with two
ETCB boards), one IP added to each CRP/ETCB board should be configured in a
separate record line.
Here, it is not necessary to allocate the IP+UDP port resource in the IPGb scenario to
the service processing board.
Parameter Name Parameter Description
Managed Element > Transport Network > User Plane Service Configuration > Service IP
Configuration of Slave
3.2 V4_Template_TransportNetwork
3.2.1 Choose
For GSM, select GSM only in Radio Type, and it is not necessary to select the
transmission type.
Then, click Generate to finish the setting and filtering.
Default: 1
When there is only signaling point on BSC, set this
NET parameter to “NET1.”
When there is more than one signaling point on BSC, set
the NET type of this office by increasing SNs.
Default: 0
If the value of NETAPPEARANCEFLAG is “1,” set this
NETAPPEARANCE parameter according to the integration planning.
When the value of NETAPPEARANCEFLAG is “2,” fill in
“0” for this parameter.
Managed Element > Transport Network > No.7 Signalling Configuration > Local End
Signalling Point
It is not necessary to configure this sheet in the IPA/IPGb/IPAbis scenarios. Static route
needs to be configured when MSC, MGW, SGSN, and SDR service IP (loopback IP) and
the real interface IP at BSC are not in the same subnet.
Parameter Name Parameter Description
When the next hop type is IP, configure the next hope IP
NEXTHOPIPADDR
according to the on-site planning.
IPOE scenario:
Managed Element > Transport Network > IP Configuration > Route Global Configuration
> Static Route(IPV4)
It is necessary to configure the IP transmission path group for the user plane and define
the path group bandwidth in the IPAbis scenario. The configuration of each project
occupies one record, including the IPAbis transmission path configured in the “IP
Bearer(ABIS)” sheet. Configure the bandwidth resource that defines Abis-interface user
plane. Do not configure transmission path group and transmission path for the control
plane.
Parameter Name Parameter Description
Configure the association information for the IPAbis office. The association information
for each IPAbis office should be configured in a separate record.
Parameter Name Parameter Description
Fill in the planned local port IP of SCTP. The local port here
refers to the SCTP IP at BSC side. It should be consistent
LOCIPADDR1 with the OMCBAGIPADDR in the Basic Info sheet, i.e., take
one IP from the planned IP Abis user-plane loopback IP and
use it as the OMCBAGIPADDR&SCTP IP.
Default: 500
MAXRTO
This parameter can be left blank.
Default: 50
MINRTO
This parameter can be left blank.
Default: 100
INITRTO
This parameter can be left blank.
Default: 500
HEARTBEAT
This parameter can be left blank.
Default: 20
DELAYACK
This parameter can be left blank.
In the default configuration of base station SCTP, iBSC acts as the server, and the base
station acts as the client.
3.2.6 IP Bearer(ABIS)
Configure Abis office and Abis logical link (transmission path) information.
Parameter Name Parameter Description
For the IPOE site, fill in the local MP IP according to the on-
site planning.
MPIPADDRESS Do not fill in this parameter. It is recommended that the
unnumbered IP interface and static route be created
automatically by the system.
2. An SCTP can either be configured with only one independent PPP link or
configured with MP LINK. Do not configure more than one independent PPP link to
one SCTP.
3. For FE sites, configure the path group in the IP Path Group in advance.
For IPOE sites, the path group can be created through this sheet automatically, and it
must be configured on the MP/PPP port.
Managed Element > GSM Logical Configuration > Link Configuration > Abis Office
Managed Element > GSM Logical Configuration > Link Configuration > Multi Plmn >
Logical Abis Link > Abis Transmission Path
Managed Element > Transport Network > No.7 Signalling Configuration > Local End
Signalling Point > Adjacent Office Information
Managed Element > GSM Logical Configuration > Link Configuration > A Office
3.2.8 IP Path(CN)
In the current version, IPA admission control is disabled by default, so do not configure
this sheet unless otherwise required.
This sheet is used to configure the SCTP and the ASP to the adjacent office of MSC in
the IPA scenario .
Parameter Name Parameter Description
Fill in the planned SCTP ID, which should be unique within the
BSC and planned together with the SCTP of IPAbis. An
ASSOCIATIONSEQ
adjacent office of the A interface can be configured with a
maximum of 16 SCTPs.
MODULE Fill in the planned Home Module No. of SCTP, based on the
principle that the A-interface signaling link load should be
allocated to idle CMP modules or the CMPs with fewer SDRs.
MINRTO Default: 50
DELAYACK Default: 20
Managed Element > Transport Network > No.7 Signalling Configuration > Local End
Signalling Point > Adjacent Office Information > ASP Configuration
This sheet is used to configure the M3UA AS of the MSC adjacent office in the IPA
scenario.
Parameter Name Parameter Description
USERLABEL Fill in the planned user label of AS.
Managed Element > Transport Network > No.7 Signalling Configuration > Local End
Signalling Point > Adjacent Office Information > AS Configuration
3.2.11 M3uaRoute
This sheet is used to configure the signaling route of M3ua in the IPA scenario.
Parameter Name Parameter Description
Managed Element > Transport Network > No.7 Signalling Configuration > M3ua Route
3.2.12 M3uaRouteSet
This sheet is used to configure the signaling route set of M3ua in the IPA scenario.
Parameter Name Parameter Description
Managed Element > Transport Network > No.7 Signalling Configuration > M3ua
RouteSet
This sheet is used to configure MSC office and the NRI Length/Null-NRI value in the
FlexA scenario.
Parameter Name Parameter Description
In FlexA networking, MSC NRI Length, MSC NULL-NRI, and MSC CN ID need to be
queried at CN side. They must be configured the same as those at CN side. Otherwise,
mobile phones cannot access the network.
Managed Element > GSM Logical Configuration > Link Configuration > MSC Office
Managed Element > GSM Logical Configuration > Link Configuration > Nri
Managed Element > GSM Logical Configuration > Link Configuration > Multi Plmn
This sheet is used to configure SGSN office and the NRI Length/NULL-NRI value in the
FlexGb scenario.
Parameter Name Parameter Description
Managed Element > GSM Logical Configuration > Link Configuration > SGSN Office
Managed Element > GSM Logical Configuration > Link Configuration > Nri
Managed Element > GSM Logical Configuration > Link Configuration > Multi Plmn
3.2.15 NRI
In the FlexA and FlexGb scenarios, it is necessary to configure the NRI of the
MSC/SGSN office, one record for each NRI.
When MSC NRI is the same as SGSN NRI, they can be filled in the same row.
Parameter Name Parameter Description
Managed Element -> GSM Logical Configuration -> Link Configuration -> Nri
3.2.16 Ip Gb
This sheet is used to configure the NSVC related information in the IPGb scenario.
Parameter Name Parameter Description
Managed Element > GSM Logical Configuration > Link Configuration > SGSN Office >
IP Nse
Managed Element > GSM Logical Configuration > Link Configuration > SGSN Office >
IP Nse > Local End Point
Managed Element > GSM Logical Configuration > Link Configuration > SGSN Office >
IP Nse > Remote End Point
This sheet is used to configure the PCM of the A interface in the TDMA scenario.
Parameter Name Parameter Description
Managed Element > GSM Logical Configuration > Link Configuration > A Interface Pcm
Managed Element > GSM Logical Configuration > Link Configuration > A Interface Pcm
> A Interface N7 Pcm
Managed Element > GSM Logical Configuration > Link Configuration > A Interface Pcm
> A Interface N7 Pcm > A Interface Trunk
3.2.18 Mtp2Link
This sheet is used to configure No. 7 signaling link and signaling link group related
information in the TDMA scenario.
Parameter Name Parameter Description
This sheet is used to configure the MTP3 signaling route in the TDMA scenario.
Parameter Name Parameter Description
It is the first bearer link group for the route. Fill in the value
LINKSET_1 according to the on-site planning. Use the Linkset data in the
Mtp2Link sheet.
It is the second bearer link group for the route. Fill in the
value according to the on-site planning. Use the Linkset data
LINKSET_1
in the Mtp2Link sheet. Fill in “0” if the second bearer link
group for the route does not exist.
Managed Element > Transport Network > No.7 Signalling Configuration > Mtp3 Route
3.2.20 Mtp3RouteSet
This sheet is used to configure the MTP3 signaling route set in the TDMA scenario.
Parameter Name Parameter Description
It is the first bearer route of the office route. Use the ROUTE
ROUTEID1
ID data in the Mtp3 Route for this parameter.
It is the third bearer route of the office route. Use the ROUTE
ROUTEID3 ID data in the Mtp3 Route for this parameter. Fill in “0” by
default if the bearer route of the office route does not exist.
Managed Element > Transport Network > No.7 Signalling Configuration > Mtp3
RouteSet
For some sheets of the GSM Radio Quick Configuration Template, the data can be
added or deleted. It is not necessary to configure these sheets for new sites. The sheets
are listed below and will not be described in details in this Guide.
GBssFunction
GCellIfta
GHandoverControl
GScHandoverControl
GPsHandoverControl
GFhHandoverControl
GPsChannelSchedule
GPowerControl
GPriorityResel
GTs
Managed Element > GSM Logical Configuration > Site Information Configuration > Site
baseband share Configuration
Note:
By GSM CRAN, the baseband resources will be allocated to logical TRX dynamically
according to the change of traffic in the cells, so that the baseband resources will be shared
among these cells.
Refer to the Base Band Resource Sharing Feature Guide for details.
3.3.2 GMocnArea
This sheet needs to be configured only when multiple operators share a radio cell.
Parameter Name Parameter Description
Share Area ID
GMocnAreaId Configure this parameter according to the on-site
planning.
Managed Element -> GSM Logical Configuration -> Global Information Configuration ->
Share Area Configuration
Note:
MOCN (Multi-Operator Core Network): One radio network can be connected with the CN
nodes of multiple operators, so that these operators can share the same radio network.
Features of OMCN:
The operators are allowed to deploy A/Gb-Flex. The CN nodes of an operator form a CN
Pool.
The MSs in the same shared cell will be routed the CN of their subscribed operator through
RAN.
3.3.3 GBssIftaMa
This sheet needs to be configured only when Intelligent Frequency Timeslot Allocation
(IFTA) needs to be used.
3.3.4 GGsmCell
Managed Element > GSM Logical Configuration > Cell Information Configuration > GSM
Cell Configuration
3.3.5 GHoppingFrequency(Optional)
This sheet is used to configure the RF frequency hopping system.Do not configure this
sheet if there is no RF frequency hopping.
Parameter Name Parameter Description
Managed Element > GSM Logical Configuration > Cell Information Configuration >
Frequency Hopping System
3.3.6 GHoppingBaseband(Optional)
This sheet is used to configure the baseband frequency hopping system. Do not
configure this sheet if there is no baseband frequency hopping.
Parameter Name Parameter Description
3.3.7 GTrx
Configure TRX.
Parameter Name Parameter Description
refGBtsPanel Fill in the used TRX panel. It is not required for SDR sites.
Managed Element > GSM Logical Configuration > Cell Information Configuration > Trx
3.3.8 GExternalGsmCell(Optional)
userLabel Fill in the planned user label of the external neighbor cell.
Managed Element > GSM Logical Configuration > External Resource Configuration >
External GSM Cell Configuration
3.3.9 GExternalUtranCellFDD
3.3.10 GExternalUtranCellTDDLcr
Managed Element -> GSM Logical Configuration -> External Resource Configuration ->
External UTRAN TDD Cell Configuration
3.3.11 GExternalEutranCellFDD
Managed Element -> GSM Logical Configuration -> External Resource Configuration ->
External E-UTRAN FDD Cell Configuration
3.3.12 GExternalEutranCellTDD
Managed Element -> GSM Logical Configuration -> External Resource Configuration ->
External E-UTRAN TDD Cell Configuration
3.3.13 GGsmRelation
Managed Element > GSM Logical Configuration > Cell Information Configuration >
Adjacent Relation Configuration > Adjacent GSM Cell Configuration
3.3.14 GUtranRelation
Managed Element -> GSM Logical Configuration -> Cell Information Configuration ->
Adjacent Relation Configuration -> Adjacent UTRAN Cell Configuration
3.3.15 GEutranRelation
Managed Element -> GSM Logical Configuration -> Cell Information Configuration ->
Adjacent Relation Configuration -> Adjacent E-UTRAN Cell Configuration
3.3.16 GGsmVpcRelation
Managed Element -> GSM Logical Configuration -> Cell Information Configuration ->
Adjacent Relation Configuration -> Visit Paging Cell
Note:
VPC cells are a group of cells (including the current cell) that are geographically
close to the current cell. If the user’s last service is in the current cell, the paging for
user is more likely to be achieved in this cell.
3.3.17 GGsmIntfRelation
Managed Element -> GSM Logical Configuration -> Cell Information Configuration ->
Adjacent Relation Configuration -> Interfere Gsm Cell Configuration
3.3.18 GCellGroup
None.
3.3.19 GBssGLFShare
None.
4 Common Ground Data Configuration
Method
Note: It is required that data modification and configuration be performed through quick
data configuration templates. Manual modification on OMM is not recommended, such
as:
Modifying site IP
Adding/deleting sites
These modifications are achieved by modifying the corresponding fields in the IP Path
Group, SCTP Config(IUP-ABIS), and IP Bearer(ABIS) sheets in the
V4_Template_TransportNetwork template, i.e., modify the fields of the corresponding
site records in these three tables.
5 Common Wireless Data Configuration
Method
This chapter provides 16 verified wireless data configuration scenarios. In the initial
configuration, there are 20 sites, each site has two cells, and each cell has two TRXs.
OMMR version: OMMR(R4)V12.11.40P03; ICM version: MOSSV12.11.41g; iBSC
version: iBSCV6.50.100fP001.For later versions, refer to this method to modify and
configure related parameters.
Note: It is required that data modification and configuration be performed through quick
data configuration templates. Manual modification on OMM is not recommended.
Right-click the newly created plan area, and select Data Import.Import the GSM Radio
Quick Configuration template in Plan Area into the Plan area of ICM.
After the data importing finishes, right-click Plan area, and select Data Check to perform
validity check.
After the validity check is passed, click Submit to submit data.
Download and activate data on ICM under the following path: Configuration > Plan
Data Activation.
Click the button, drag the new plan are to Selected Plan Area, and click OK.
Right-click the new task, and perform the “Create Delta," “Download,” and “Activate”
operations one by one. In the download and activation process, release the mutex right
on OMM. After the data is downloaded from ICM to OMM, perform a global check on
OMM, modify the error, and then activate data.
If the optimization template needs to be modified, export the template on ICM first, and
import the modified template into ICM. Then, check and activate the template.Create the
target NE and plan area on ICM (note: it is necessary to perform data synchronization
once each time before the creation of new plan area).Right-click the plan area and select
Export.
Right-click the plan area, click Import, and import the Optimization template in the
optimization area.
After the data importing finishes, right-click Plan area, and select Data Check to perform
validity check.
After the validity check is passed, click Submit to submit data.
Download and activate data on ICM under the following path: Configuration > Plan
Data Activation.
Click the button, drag the new plan are to Selected Plan Area, and click OK.
Right-click the new task, and perform the “Create Delta," “Download,” and “Activate”
operations one by one. In the download and activation process, release the mutex right
on OMM. After the data is downloaded from ICM to OMM, perform a global check on
OMM, modify the error, and then activate data.
1. Open the GSM Radio Quick Configuration template, and fill in the information of the
new TRX in the GTrx sheet. Configure SD/PD/dynamic TCH according to the
planning, and the system will allocate them automatically. If the channel type needs
to be modified, the modification needs to be exported from ICM. Refer to Subject 2
Timeslot Modification for details.
Note: The value of BCC should not be the same as the value of TSC2.
1. Fill in the cell TRX and neighbor cell information in the GSM Radio Quick
Configuration template.
Open the GSM Radio Quick Configuration template, and configure the following sheets
to create a cell or TRX.
When a 2G neighbor cell is created in the GGsmRelation sheet, the index line is
RELATION CGI, and the format is “MCC,MNC,LAC,CI.”Add 2G internal neighbor cells
and external neighbor cells here.
When a 3G neighbor cell is created in the GUtranRelation sheet, the index line is
RELATION CGI, in the “mcc,mnc,rnc_id,ci” format.
Note: During the configuration of 3G neighbor cells, at most three types of FDD/TDD
neighbor cell frequencies can be configured to each cell.
Add an RF frequency hopping group to each cell. The three TRXs in the cell will use the
RF frequency hopping group.
1. Open the GSM Radio Quick Configuration template, and fill in the
GHoppingFrequency sheet according to network planning.
2. In the GSM Radio Quick Configuration template, modify the GTrx sheet.
If the frequency-hopping TRX is newly-filled in, it is not necessary to fill in the “ARFCN”
column.
Add an RF frequency hopping group to the cell in scenario 3, and add two TRXs that use
the second frequency-hopping group.
Open the GSM Radio Quick Configuration template, and fill the information of the new
RF frequency-hopping group in the GHoppingFrequency sheet.
4. Open the GSM Radio Quick Configuration template, add two TRXs to each cell in
the GTrx sheet, and quote the second frequency hopping group. Index the Fh of
the RF frequency hopping group.
5.2.5 Changing the Frequency-Hopping of Each Cell to Non-Frequency-
Hopping
Create a baseband frequency hopping group for each cell, and associate the first three
TRXs with the first frequency hopping group. Then add a baseband frequency hopping
group and a TRX to each cell and associate all the non-frequency-hopping TRXs with
the second frequency-hopping group.
1. Open the GSM Radio Quick Configuration template, and fill baseband frequency
hopping group information in the GHoppingBaseband sheet.
2. Open the GTrx sheet, modify the non-frequency-hopping TRXs to baseband
frequency hopping, and fill the frequency hopping group No. in the
“GHoppingBaseband DN” column.For newly-added baseband hopping frequency, it
is necessary to fill in the frequency.
Method 1: Perform the modification through the ICM optimization template. Export the
optimization template from ICM and modify the target timeslot in the GTs sheet.
0:Full rate traffic channel(Full rate traffic channel)
1:TCH/H\(0,1\)+FACCH/H\(0,1\)+SACCH/TH\(0,1\)(TCH/H\(0,1\)+FACCH/H\
(0,1\)+SACCH/TH\(0,1\))
3:SDCCH/8+SACCH/C8(SDCCH/8+SACCH/C8)
4:FCCH+SCH+BCCH+CCCH(FCCH+SCH+BCCH+CCCH)
5:BCCH+SDCCH/4(BCCH+SDCCH/4)
6:BCCH+CCCH(BCCH+CCCH)
7:BCCH+SDCCH/4+CBCH(BCCH+SDCCH/4+CBCH)
14:PDTCH+PACCH+PTCCH(PDTCH+PACCH+PTCCH)
of Gtrx=2,GTs=7 is filtered out, then click OK and the button on the lower-left.
Modify site name, cell name, LAC, CI, RAC, BCC, NCC, half rate threshold, and TRX
frequency in batch.
1. Modify site name: export the optimization template, and modify User label in
“GBtsSiteManager” and “GBtsEquipment.”
2. Modify cell name: Export the Optimization template, and modify the "User Label"
column in the GGsmCell, GSubCell, GGsmRelation, and GUtranRelation sheets.
3. Modify RAC: Export the Optimization template, and modify LAC in the
“GLocationArea” sheet. Location Area ID and Managed Object Description do not
need to be modified, because they will be associated automatically.
4. Modify CI: Export the Optimization template, and modify CI in the GGsmCell sheet.
5. Modify RAC: Export the optimization template, and modify RAC in the
“GRoutingArea” sheet. Routing Area ID and Managed Object Description do not
need to be modified.
6. Modify BCC and NCC: Export the Optimization template; modify BCC and NCC in
the GGSMCell sheet first; modify the corresponding TSC (TSC=BCC) in the GTrx
sheet, and make sure the value of TSC should be different from the value of TSC2.
7. Modify the half rate threshold: Export the Optimization template, and modify hrThs
in the "GGSMCell” sheet.
1. Open the GSM Radio Quick Configuration template, and fill cell information in the
GGsmCell sheet. For CO-BCCH cells, select sub-cells in the "Subcell Used"
column, and fill the frequency band of the second sub-cell in the "Frequency Band
of SubCell" column. If this template is imported into OMM, two sub-cells will be
created automatically in SUBCELL.
2. Open the GSM Radio Quick Configuration template, and add TRX information of
CO-BCCH cells in the GTrx sheet. In the following figure, TRX1 is the BCCH TRX
of the cell; the frequency band of TRX1 and TRX2 is 1800, and both are in the first
sub-cell; the frequency band of TRX3 is 900, and it is in the second cell.
3. Load the GSM Radio Quick Configuration template into OMM, check the loading
result, and perform data synchronization.
1. Open the GSM Radio Quick Configuration template, and fill cell information in the
GGsmCell sheet. For CO-BCCH cells, select sub-cells in the "Subcell Used"
column, and fill the frequency band of the second sub-cell in the "Frequency Band
of SubCell" column. As shown in the following figure, fill in SITEID=11.CELLID=4.
The frequency band of the first sub-cell is 1800 and that of the second sub-cell is
900.
2. Open the GSM Radio Quick Configuration template, and fill the information of the
RF frequency-hopping group in the GHoppingFrequency sheet. As shown in the
following figure, create two RF frequency hopping groups for this cell. The first
frequency hopping group will use the TRX of the first sub-cell, and the second
frequency hopping group will use the TRX of the second sub-cell.
3. Open the GSM Radio Quick Configuration template, and add TRX information of
CO-BCCH cells in the GTrx sheet. In the following figure, TRX1 is the BCCH TRX
of the cell; the frequency band of TRX1, TRX2, and TRX3 is 1800, and they are in
the first sub-cell; the frequency band of TRX4 and TRX5 is 900, and they are in the
second cell. In GHoppingFrequency DN, TRX2 and TRX3 use the first RF
frequency hopping group of the cell. TRX4 and TRX5 use the second RF frequency
hopping group of the cell.
4. Load the GSM Radio Quick Configuration template into OMM, check the loading
result, and perform data synchronization.
1. Open the GSM Radio Quick Configuration template, and modify cell information in
the GGsmCell sheet. It is necessary to modify “Subcell Used” and “Frequency
Band of SubCell.”
2. Open the GSM Radio Quick Configuration template, and add TRX information of
the second cell in the GTrx sheet.
Import the GTrx sheet first, and then import the GGsmCell sheet. Only the GGsmCell
sheet can be imported successfully at the first time, and another importing is needed to
import both sheets successfully.
3. Load the GSM Radio Quick Configuration template into OMM, check the loading
result, and perform data synchronization.
Add GSM external cell on BSC. Add these external cells as neighbor cells for each cell.
Delete the neighbor cells.
1. Add GSM external cell: Open the GSM Radio Quick Configuration template, and fill
GSM external cell information in the GExternalGsmCell sheet.
2. Add neighbor cell relation: fill in cell handover/reselection relation in the
GGsmRelation sheet.
3. Delete neighbor cells: open the GSM Radio Quick Configuration template, and
delete the target neighbor cells in the GGsmRelation sheet.
Scenario 2: Add 10 3G external cells on BSC, add five of them to each cell as the
reselection neighbor cells, then delete two reselection neighbor cells of each cell, and
add the other five 3G external cells as the neighbor cells.
Add 3G external cells on BSC, and add these cells as neighbor cells for each cell.
Delete 3G reselection neighbor cells.
1. Add 3G external cells: Open the GSM Radio Quick Configuration template, and add
3G external cells in the GExternalUtranCellFDD and GExternalUtranCellTDDLcr
sheets.
2. Add 3G neighbor cell relation: Open the GSM Radio Quick Configuration template,
and add 3G neighbor cell relation in the GUtranRelation sheet; the index is
"RELATION CGI" and the format is "mcc,mnc,rnc_id,ci."
3. Delete 3G neighbor cell: In the GUtranRelation sheet, fill in “D” in the NODIND
column if the reselection neighbor cells to be deleted.
1. Delete the TRXs involved in RF frequency hopping: Open the GSM Radio Quick
Configuration template, and delete TRX in the GTrx sheet. If the TRXs in the RF
frequency hopping group are all deleted, it is necessary to delete the corresponding
frequency hopping group in the GHoppingFrequency sheet.
2. Delete TRXs involved in baseband frequency hopping: Open the GSM Radio Quick
Configuration template, delete the TRXs in the GTrx sheet, and then import the
modified template into OMM. If the TRXs in the frequency hopping group are not
deleted completely, modify the MA Frequency List of the corresponding frequency
hopping group in the GHoppingBaseband sheet. If the TRXs of the frequency
hopping group are all deleted, delete the corresponding frequency hopping group in
the GHoppingBaseband sheet.
5.7.2 Deleting Cells in Batch and Delete the Related Neighbor Cells
1. Open the GSM Radio Quick Configuration template, and delete related cells in the
GGsmCell sheet. Import the modified template into OMM, check the loading result,
and download and synchronized data. The neighbor cell relation and reverse
neighbor cell relation will also be deleted in this process.
5.7.3 Deleting Sites in Batch
1. Export the UNI_OFFICE_SubNetwork template from OMM, and delete related sites
in the SCTP Config(IUB-ABIS) and IP Bearer(ABIS) sheets.
2. Import, check, download, and activate data through ICM.
6 Example for Templates of Typical
Scenarios
The attachments are templates of V12.11.40XX series. They can be used as the
reference for the data configuration and modification for later versions. In the field
operation, the templates in on-site version package should be used. Do not import the
templates in this Guide directly to the OMM used in the field.
IPA(FlexA)+IPAbis
+IPGb Quick Configuration.zip
TDMA+IPAbis+IPGb
Quick Configuration.zip