ZXUR 9000 GSM Data Configuration Guide
January 14, 2024 | Author: Anonymous | Category: N/A
Short Description
Download ZXUR 9000 GSM Data Configuration Guide...
Description
ZXUR 9000 GSM Configuration Guide
Data
About This Document Summary Chapter
Description
1 Introduction to Quick Data Configuration
Provides an introduction about quick data configuration.
2 Quick Data Configuration Template Filling Scenarios
Introduces some scenarios of filling in Quick Data Configuration Templates.
3 Quick Data Configuration Template Filling Specifications
Introduces the specifications of Quick Data Configuration Templates.
4 Common Ground Data Configuration Method
Introduces the method of configuring common ground data.
5 Common Wireless Data Configuration Method
Introduces the method of configuration common radio data
6 Example for Templates of Typical Scenarios
Provides the example for templates of typical scenarios.
TABLE OF CONTENT
1 1.1 1.1.1 1.1.2 1.2 1.2.1 1.2.2 1.2.3 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.3.5 1.4 1.4.1 1.4.2
Introduction to Quick Data Configuration......................................................1 General Description...........................................................................................1 Contents of Templates.......................................................................................1 Template Structure............................................................................................4 Preparation of Quick Configuration Data............................................................6 Quick Data Configuration Template Filling Scenarios........................................6 Quick Data Configuration Template Filling Flow................................................8 Board Configuration...........................................................................................9 Quick Configuration Data Planning..................................................................10 CMP Module No. Configuration and Planning Principles (CRP).......................10 RUP (User-plane IP) Configuration Planning Advices......................................11 A/Gb Interface Data Configuration Planning Advices.......................................13 IPOE1 SDR Base Station Configuration Data Planning Advices......................14 Control-Plane IP Planning................................................................................14 Importing Quick Configuration Data.................................................................15 Creating Subnetwork and Managed Element...................................................15 Loading Quick Configuration Template............................................................16
2 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.2 2.4.3
Quick Data Configuration Template Filling Scenarios................................22 Basic Data Configuration of BSC Commissioning............................................22 Configuration of Global Resources..................................................................22 Physical Configuration of Board.......................................................................22 IP Related Configuration..................................................................................23 Local Office Configuration................................................................................24 A-interface Integration Configuration................................................................24 A-interface Integration Parameters..................................................................24 A-Interface Office Configuration.......................................................................27 A-interface Integration Configuration................................................................28 GB Interface Integration...................................................................................29 Gb-interface Integration Parameters................................................................29 Gb Interface Office Configuration.....................................................................31 Gb-interface Integration Parameter..................................................................31 SDR Site Commissioning Configuration...........................................................31 Configuring IPOE Abis/IPAbis IP......................................................................31 Configuring SDR Ground Resource.................................................................32 Radio Resource Configuration.........................................................................34
3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5
Quick Data Configuration Template Filling Specifications.........................37 V4_Template_Equipment.................................................................................37 Basic Info......................................................................................................... 37 Plmn Config.....................................................................................................39 Shelf Config.....................................................................................................40 Board Config....................................................................................................41 Interface IP......................................................................................................44
3.1.6 3.1.7 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 3.2.14 3.2.15 3.2.16 3.2.17 3.2.18 3.2.19 3.2.20 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.10 3.3.11 3.3.12 3.3.13 3.3.14 3.3.15 3.3.16 3.3.17 3.3.18 3.3.19
Service IP........................................................................................................ 47 Slave or Dsp Service Config............................................................................48 V4_Template_TransportNetwork.....................................................................49 Choose............................................................................................................ 49 Local Office......................................................................................................50 Static Route.....................................................................................................51 IP Path Group..................................................................................................52 SCTP Config(ABIS).........................................................................................53 IP Bearer(ABIS)...............................................................................................55 Adjacent Office(CN).........................................................................................58 IP Path(CN).....................................................................................................60 SCTP Config(CN)............................................................................................60 M3uaAS Config(CN)........................................................................................61 M3uaRoute......................................................................................................62 M3uaRouteSet.................................................................................................63 MSC Office......................................................................................................64 SGSN Office....................................................................................................65 NRI.................................................................................................................. 66 Ip Gb................................................................................................................ 66 No.7 PCM........................................................................................................ 69 Mtp2Link.......................................................................................................... 69 Mtp3 Route......................................................................................................71 Mtp3RouteSet..................................................................................................72 GSM Radio Quick Configuration Template......................................................73 GSiteBaseBandShare (Optional).....................................................................73 GMocnArea......................................................................................................74 GBssIftaMa......................................................................................................75 GGsmCell........................................................................................................ 76 GHoppingFrequency(Optional)........................................................................78 GHoppingBaseband(Optional).........................................................................79 GTrx................................................................................................................. 79 GExternalGsmCell(Optional)............................................................................80 GExternalUtranCellFDD...................................................................................81 GExternalUtranCellTDDLcr..............................................................................82 GExternalEutranCellFDD.................................................................................83 GExternalEutranCellTDD.................................................................................84 GGsmRelation.................................................................................................85 GUtranRelation................................................................................................86 GEutranRelation..............................................................................................87 GGsmVpcRelation...........................................................................................87 GGsmIntfRelation............................................................................................88 GCellGroup......................................................................................................89 GBssGLFShare................................................................................................89
4
Common Ground Data Configuration Method.............................................90
5 5.1 5.1.1
Common Wireless Data Configuration Method...........................................91 Configuring and Downloading Radio Data on ICM...........................................91 Importing, Downloading, and Activating GSM Radio Quick Configuration Template on ICM.............................................................................................91
5.1.2
5.5.1 5.5.2 5.5.3 5.6 5.6.1 5.6.2 5.7 5.7.1 5.7.2 5.7.3
Exporting, Importing, Checking, Downloading, and Activating the Optimization Template on ICM........................................................................94 Special Subject 1: Capacity Expansion............................................................98 Adding TRXs in Batch......................................................................................98 Creating Cell, TRX, and Neighbor Cell in Batch...............................................99 Configuring RF Frequency Hopping...............................................................100 Adding RF Frequency Hopping Group...........................................................101 Changing the Frequency-Hopping of Each Cell to Non-Frequency-Hopping. 102 Creating Baseband Frequency Hopping........................................................103 Special Subject 2: Timeslot Modification........................................................104 Configuring and Modifying Channels.............................................................104 Special Subject 3: Data Modification..............................................................108 Modification of Basic Parameters...................................................................108 Special Subject 4: Configuring CO-BCCH Cell with GSM Radio Quick Configuration Template.................................................................................114 Creating CO-BCCH Cell in Non-frequency-hopping Scenario........................114 Creating CO-BCCH Cell in RF Frequency Hopping Scenario........................115 Modifying Non-CO-BCCH Cell to CO-BCCH Cell...........................................117 Special Subject 5: Neighbor Cell Modification................................................118 Adding and Deleting External Neighbor Cell..................................................118 Adding and Deleting 3G Reselection Neighbor Cells.....................................120 Special Subject 6: Capacity Reduction..........................................................121 Deleting TRXs in Batch..................................................................................121 Deleting Cells in Batch and Delete the Related Neighbor Cells.....................122 Deleting Sites in Batch...................................................................................123
6 6.1 6.2
Example for Templates of Typical Scenarios............................................125 IPA(FlexA)+IPAbis+IPGb Scenario................................................................125 TDMA+IPAbis+IPGb Scenario.......................................................................125
5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.3 5.3.1 5.4 5.4.1 5.5
TABLES Table 2-1 IP A-interface Integration Parameters...................................................................24 Table 2-2 TDMA-interface Integration Parameters...............................................................26 Table 2-3 IP Gb-interface Integration Parameters................................................................29 Table 2-4 E1 Gb interface Integration Parameters................................................................30 Table 2-5 FlexGb Integration Parameters.............................................................................30 Table 2-6 IP Path Group.......................................................................................................32 Table 2-7 IP Bearer(ABIS):...................................................................................................32 Table 2-8 IP Bearer(ABIS)....................................................................................................33
1
Introduction to Quick Data Configuration This chapter describes basic principles and the operation steps of quick data configuration, and aims to guide quick equipment commissioning in the field. For different OMM versions, the detailed operations may be different. The parameter description in the templates of this Guide applies to ZXM-OMMRV12.15 series.
1.1
General Description 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).
1.1.1
Contents of Templates There are three iBSC quick data configuration templates, which include the following data: 1.
V4_Template_Equipment.xls:
Basic configuration of global iBSC
Operator information
The shelf, board, and hardware configuration of iBSC
Interface (real interface, loopback interface, and virtual interface) information.
User-plane IP and resource data
2.
V4_Template_TransportNetwork.xls:
Local office and adjacent office configuration data
Static route information
SCTP configuration data
Abis/A/Gb/MSC/SGSN link and office configuration data
Abis/A/Gb-interface path group and transmission configuration data
Signaling link and M3UA configuration data
3.
GSM Radio Quick Configuration Template.xls
Configuration data of GSM cells
Frequency hopping configuration data
TRX configuration data
External GSM cell and GSM relation configuration data
External Utran cell and Utran relation configuration data
Tip: Quick data configuration templates can be acquired from the directory of OMMR version or the directory of OMMR client, as detailed below: ums-clnt\deploy\template\GROUND ums-clnt\deploy\template\GSM
1.1.2
Template Structure 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 structure of the sheets is as shown below.
The first five rows of the sheets fixed data in the template, and cannot be modified. The first row is the field name. The second row is the description of the fields. The third row is the value range of the fields. The fourth row is the example of the values of the fields. 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.
1.2
Preparation of Quick Configuration Data
1.2.1
Quick Data Configuration Template Filling Scenarios 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) Interface IP Service IP Slave or Dsp Service Config
Local Office Local Signaling Points Static Route IP Path Group Adjacent Office(CN)
IPA
IP Path(CN) SCTP Config(CN) M3uaAs Config(CN) M3uaRouteSet MSC Office Nri(Necessary for FlexA) In the TDMA+IPAbis (SDR base stations) scenario, IPAbis
TDMA
Local Office
CS user-plane data is
Local Signalling Points
processed on ETCB, and it is
Adjacent Office(CN)
necessary to configure the
No.7 PCM
following two sheets. In the
Mtp2Link
TDMA+TDM Abis scenario, it is
Mtp3Route
not necessary to configure these two sheets. Service IP Slave or Dsp Service Config
Mtp3RouteSet MSC Office Nri(Necessary for FlexA) Static Route
IPGb
Interface IP
SGSN Office
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.
1.2.2
Quick Data Configuration Template Filling Flow 1.
Prerequisites for filling in quick data 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. 2.
Quick configuration template data planning:
V4_Template_Equipment.xls: includes mainly Basic configuration of global iBSC, operator information, Shelf & Board Configuration information, and networking & IP planning, which should be prepared by field engineers according to the actual situation. V4_Template_TransportNetwork.xls: Perform planning about the CMP module allocated to the sites: 3 – 63 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 Abisinterface, 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.) GSM Radio Quick Configuration Template.xls: Perform BVCI planning. SITE+CELLID is recommended. 3.
Fill in V4_Template_Equipment.xls, V4_Template_TransportNetwork.xls, and GSM Radio Quick Configuration Template.xls one by one according to the planning data.
Please refer to the next chapter for the detailed steps of filling the quick configuration templates.
1.2.3
Board Configuration This section introduces the boards that need to be configured in different scenarios, as shown in the table below. Board
Full Name
Name EGPB EDTI
ESDTI
Logical Name
Enhanced GE Process Board
EGPB(IP A/IP Abis/IP Gb)
Enhanced Digital Trunk board IP
EDTI(IPoE Abis)
version
EDGB(E1 Gb)
Enhanced SDH Digital Trunk
ESDTI(IPoSTM-1 Abis)
board IP version
ESDGB(STM-1 Gb)
EDTT
ESDTT
ESDTG
ETCB UMP
Enhanced Digital Trunk board TDM version Enhanced SDH Digital Trunk board TDM version Enhanced SDH Digital Trunk board GSM version
EDAB(E1 A) EDBB(E1 Abis) EDTB(E1 Ater) ESDAB(STM-1 A) ESDBB(STM-1 Abis) ESDTB(STM-1 Ater) ESDQB(STM-1 A)
Enhanced TransCoder Board
ETCB(E1 A/STM-1 A)
Universal Management Process
OMM
Board
OMP CRP (integrated with the functions of
USP
Universal Service Process Board
EGBS
Enhanced GE Base Switch board EGBS
EGFS ERS
Enhanced GE Fabric Switch board Enhanced Resource Shelf
CMP and RUP)
EGFS ERS
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. OMM is at Slots 5/6 fixedly, in 1+1 backup. EGBS is at Slots 19/20 fixedly, in 1+1 backup. EGFS is at Slots 21/22 fixedly, in 1+1 backup. Configure other boards according to on-site situation and the planning.
1.3
Quick Configuration Data Planning
1.3.1
CMP Module No. Configuration and Planning Principles (CRP) 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. CRPs should be in master/slave configuration. They are configured in Shelves 1-3, in which the CRPs are sequenced from the first pair to the nth pair from left to right. Usually, the number of CRPs is balanced in these three shelves. The A-interface signaling and SCTPs are first evenly allocated to the physical CRPs (CMPs) and then evenly allocated to the CMP modules. For base station configuration, the number of TRXs should be balanced among the modules. Each CRP (CRP pair) can be configured with at most two to three CMP modules, depending on the A-interface application type configured when CRP is created. The range of the module No. is 3 – 63. Currently, it is recommended that the USESCENE parameter of CRP be set to IPA fixedly. Each CRP (CRP pair) is configured with two CMP modules. The USESCENE here is used only to restrict the number of CMP modules, and it is not related to the Ainterface transmission. 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 Board type
TDMA
IPA
USP
6
8
USP2a
12
16
IPA+IPABIS scenario,one IP address support board number: Address type/Board type Board QTY supported by single Abis address Board QTY supported by single IPA address
USP
USP2a
4
2
6
3
IPA+IPAbis scenario: It is recommended that IPA IP and IP Abis IP be configured separately. Each IPA IP (Support A interface) can be bound with six USPs, or three USP2as. One IP Abis IP (Support Abis_CS interface and Abis_PS interface) can be bound with four CRPs, the four CPRs ,or 2 USP2as. In the template, each CRP should be configured with one record of CRP+IPA+IPAbis. IPA address and IP Abis are applied from the operator. The Abis address of IPOE is allocated by ZTE. IPA and FE Abis IPs should be reserved in advance for later expansion. TDM A+IPAbis, scenario,one IP address support board number: Address type/Board type Board QTY supported by single Abis address
USP
USP2a
ETCB
4
2
2
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 userplane 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.
1.3.3
A/Gb Interface Data Configuration Planning Advices 1.
IPA-interface data configuration advices: The value range of ANEID is 2001-2048. The value range of the transmission path group ID is 2001-2048. The transmission path group ID should be consistent with ANEID. For the FlexA scenario, each
combination of peer-end MSC office + MGW user-plane IP (IP segment) is associated with a logical transmission path, e.g., for two MSC offices and two MGWs (two user-plane IP subnet), 2*2, i.e., four IPA paths need to be configured. The logical transmission path bandwidth is set to “Total number of interfaces * 500M / Number of adjacent offices / Number of peer-end user-plane IPs. The bandwidth of the transmission path group is the sum of all the logical transmission bandwidth within the group. The logical transmission path under each transmission path group is numbered from 1, and each MSC office + MGW service IP (IP segment) corresponds to a logical transmission path. The transmission path group configuration module is the first home module of SCTP. Office ID, MSC ID, and MSC CN ID are numbered from “1.” The value range of SCTP ID is 2001-2048. The AS number is 1, and the ASP Number and the route Number are both 1. 2.
TDM A-interface data configuration advices: The value range of ANEID is 20012048. 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.
5.
A-interface logical transmission path configuration principles for FlexA scenario: It is configured according to the numbers of MSC offices and MGW user-plane subnets; the channel between every pair of MSC and MGW should be configured with one A-interface logical transmission path, i.e. the office used by the logical transmission path is MSC, and the IP address is the service IP address (or IP segment) of MGW.
1.3.4
IPOE1 SDR Base Station Configuration Data Planning Advices 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. When there are more than 254 sites, use 118.19.siteid-254.100. The IPOE path bandwidth is “Number of timeslots * 64 K -128 K.”
1.3.5
Control-Plane IP Planning 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. BSC side
Core side
IP
Port
IP
Port
IP1
Port1
IP5
Port5
IP2
Port1
IP6
Port5
IP1
Port2
IP5
Port6
IP2
Port2
IP6
Port6
Association 1
Association 2
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.
1.4
Importing Quick Configuration Data 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.
1.4.1
Creating Subnetwork and Managed Element Right-click the target NE in Configuration Management, and select Create Subnetwork.
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.
Right-click created subnetwork node, and select Create Managed Element.
Set Managed Element modetype to “GSM. Set Managed Element IP Address to “129.0.1.1” fixedly, and click the Save button to finish the creation of BSC Managed Element.
1.4.2
Loading Quick Configuration Template 1.
Apply for Mutex Right.
2.
Select an NE and click Import Quick Configuration Data.
3.
Click Choose and select a quick data configuration template.
4.
Select the sheet to be imported. Select all the sheets if the template is configured for the first time. Click Execute to load the quick data configuration template.
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
2.1
Basic Data Configuration of BSC Commissioning 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.
2.1.1
Configuration of Global Resources The configuration of global resource involves the following sheets (V4_Template_Equipment template):
Basic Info: Configure the basic information of the global office, including the operation & maintenance IP, logserver IP, etc.
2.1.2
Plmn Config: Configure the operator information of the NE.
Physical Configuration of Board
Note:
Compared with V6.50.10*, the main differences of board configuration in V6.50.20* are as listed below: CRP is integrated with the functions of CMP and RUP.
In V6.50.20*, USP does not act as CMP and RUP anymore. They are merged into one board named as CRP, which processes both control-plane and user-plane services. The boards for control-plane resource processing should be in 1+1 backup, while the boards for user-plane resource processing should use the load-share mode. Therefore, the USP boards should be in pairs. 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. The board configuration involves the following sheets (V4_Template_Equipment template):
2.1.3
Shelf Config: Configure shelf information.
Board Config: Configure board information (refer to the Board Warehouse sheet).
IP Related Configuration 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
Interface IP: Configure the control-plane& user-plane loopback IP, real-interface (sub-interface) IP, and OMCB gateway virtual-interface IP of IP A, IP Gb, IPOE Abis, and IP Abis.
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.
Slave or Dsp Service Config: Configure the service IP resource of user-plane resource boards CRP/ETCB to allocate IP UDP port resources.
2.1.4
Local Office Configuration Configure the Local Office sheet (V4_Template_TransportNetwork Template)
Local Office: configure local office information.
2.2
A-interface Integration Configuration
2.2.1
A-interface Integration Parameters 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:
Table 2-1 IP A-interface Integration Parameters Integration Parameter iBSC signaling point code iBSC signaling point type MSC signaling point code MSC signaling point type
Value Description Specify whether it is 14bit or 24bit signaling code (in decimal). SEP/STP/STEP Specify whether it is 14bit or 24bit signaling code (in decimal). SEP/STP/STEP
Location in Quick Configuration Template TransportNetwork-->Local Office->OPC This Item needs to be configured on OMM TransportNetwork-->Adjacent Office(CN)-->DPC This Item needs to be configured on OMM
Sub-service
International SPC, Reserved
TransportNetwork-->Adjacent
field
international SPC ,National
Office(CN)-->SSF
SPC, Reserved National SPC TransportNetwork-->Adjacent
Protocol Type
CHINA / ITU / ANSI
IP address of
Control-plane service IP of
TransportNetwork-->SCTP
MSC
MSC, ASP peer-end IP.
Config(CN)-->REMADDR
Office(CN)--> PROTOCOLTYPE
TransportNetwork-->Static Route-IP address of
User-plane service IP of
>ROUTEPREFIX;
MGW
MGW
TransportNetwork-->IP Path(CN)--> DESTIPADDR
Gateway to
The gateway of the control-
TransportNetwork-->Static Route--
MSC
plane service IP to MSCS
>NEXTHOPIPADDR
Gateway to
The gateway of the user-
TransportNetwork-->Static Route--
MGW
plane service IP to MGW
>NEXTHOPIPADDR
iBSC controlplane real interface IP iBSC userplane real interface IP iBSC controlplane loopback IP
IP interface board IP, connected to MSC IP interface board IP, connected to MGW
Equipment-->Interface IP--> IPADDR
Equipment-->Interface IP--> IPADDR Equipment-->Interface IP-->
iBSC Control-plane service
IPADDR;
IP, ASP peer-end IP.
TransportNetwork-->SCTP Config(CN)-->LOCADDR Equipment-->Interface IP—
iBSC userplane loopback IP
>IPADDR; iBSC user-plane service IP,
Equipment-->Service IP-->
used by AIPB DSP
SERVICEIP; 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 SCTP bearer
Usually M3UA is used.
It needs to be configured on GUI.
protocol type Application type of
Client/Server
association
TransportNetwork-->SCTP Config(CN)-->PROPERTY
Select IPSP_CLIENT, and Application
the Application server tag of
server tag (AS
the peer end should be
property)
IPSP_SERVER. This should
TransportNetwork-->M3uaAS Config-->TAG
be negotiated with CN. TransportNetwork-->M3uaAS “Whether exists routing Whether context exists
context” Value range: YES/NO If YES is filled in, the routing text needs to be filled in.
Config-->EXISTLOCALCONTEXT; TransportNetwork-->M3uaAS Config-->LOCALCONTEXT; TransportNetwork-->M3uaAS Config-->EXISTPEERCONTEXT; 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 ROUTEMODE
M3UA route sequence
TransportNetwork-->M3uaRoute->ROUTEMODE
Table 2-2 TDMA-interface Integration Parameters Integration Parameter iBSC signaling point code iBSC signaling point type MSC signaling point code
Value Description Specify whether it is 14bit or 24bit signaling code (in decimal) One of SEP, STP, and SETP Specify whether it is 14bit or 24bit signaling code (in decimal)
Location in Quick Configuration Template TransportNetwork-->Local Office->OPC This Item needs to be configured on OMM TransportNetwork-->Adjacent Office(CN)-->DPC
MSC signaling point type SSF Signaling protocol type No.7 PCM SN Frame format of E1 interface
One of SEP, STP, and SETP Sub-service field (SSF) CHINA / ITU / ANSI
Dual-frame/Multi-frame
TS
SS7 link TS
Correction Method)
Usually the basic error correction method is adopted.
LINKTYPE (Signaling Link
TransportNetwork-->Adjacent Office(CN)-->SSF TransportNetwork-->Adjacent Office(CN)--> PROTOCOLTYPE >N7PCM
Signaling link code (SLC)
Error
OMM
TransportNetwork-->No.7 PCM--
CIC
SLC
LECM (Link
This Item needs to be configured on
64K / n*64K / 2M
Group Type)
Equipment-->Board Config->CRC4MODE TransportNetwork--> Mtp2Link -->SLC TransportNetwork--> Mtp2Link -->TS TransportNetwork--> Mtp2Link->LECM
TransportNetwork--> Mtp2Link->LINKTYPE
FlexA Integration Parameters Integration Parameter Length of MSC NRI
Value Description Length of MSC NRI
Location in Quick Configuration Template TransportNetwork--> MSC Office --> MSCNRILen
MSC NULL-
TransportNetwork--> MSC Office
NRI ID
--> MSCNULLNRI
MSC CN ID NRI Load allocate radio of MSC
MSC CN identification MSC network route identification MSC load sharing ratio
TransportNetwork--> MSC Office --> MSCCNID TransportNetwork--> Nri--> NRI TransportNetwork--> MSC Office --> AllocateRatio
2.2.2
A-Interface Office Configuration Office configuration consists of local office configuration and adjacent office configuration. Office configuration involves the following sheets (V4_Template_TransportNetwork template): Local Office: To configure local office information. Adjacent Office(CN): To configure adjacent office information. MSC Office: To configure MSC office information. Nri: To configure the MSC NRI in the FlexA scenario. The configuration is not needed in the non-FlexA scenario.
2.2.3
A-interface Integration Configuration For different A-interface types, the sheets involved are different (V4_Template_TransportNetwork template), as detailed below: IP A integration configuration (make sure the required IP has been configured in the IP related sheets in the V4_Template_Equipment template): SCTP Config(CN): configure SCTP related data. M3uaAS Config: configure application server. M3uaRoute: configure M3ua route. M3uaRouteSet: configure M3ua route set. Static Route: configure static route. TDM A interface integration configuration: Mtp2Link: configure Mtp2 link. Mtp3Route: configure Mtp3 route.
Mtp3RouteSet: configure Mtp3 route set. No.7 PCM: configure No. 7 PCM.
2.3
GB Interface Integration
2.3.1
Gb-interface Integration Parameters 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 Integration Parameter Network Service Entity Identifier (NSE ID)
Value Description
Location in Quick Configuration Template
It should be consistent with the configuration at
TransportNetwork-->Ip Gb-->NSEID
SGSN. Static/Dynamic configuration; If
Subnet
dynamic configuration
Configuration
is selected, the preset
Type
SGSN IP address
TransportNetwork-->Ip Gb->SNCFGTYPE
needs to be configured. Configuration of
Local endpoint IP and
TransportNetwork-->Ip Gb-->IPADDRESS
local end point
UDP port number
TransportNetwork-->Ip Gb-->UDPPORT
Configuration of
Peer endpoint IP and
peer end point
UDP port number
Signaling
SGSN IP Address
TransportNetwork-->Ip Gb-->UDPPORT
TransportNetwork-->Ip Gb--
Data weight
configured
TransportNetwork-->Ip Gb-->IPADDRESS
TransportNetwork-->Ip Gb-->SIGWEIGHT
weight
The pre-
Static Configuration:
>DATAWEIGHT Use this parameter when dynamic NSEI is used.
The pre-
Use this parameter
configured
when dynamic NSEI
SGSN UDP port
is used.
TransportNetwork-->Ip Gb->SGSNIPADDRESS
TransportNetwork-->Ip Gb->SGSNUDPPORT
Table 2-4 E1 Gb interface Integration Parameters Integration
Value Description
Parameter
Location in Quick Configuration Template
It should be
Network Service
consistent with the
Entity Identifier
configuration at
(NSEI)
TransportNetwork-->Fr Gb-->NSEID
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
configuration at
Identifier (NSVCI)
SGSN. It should be
Digital Link Connection Identifier (DLCI)
TransportNetwork-->Fr Gb-->NSVCID
consistent with the configuration at
TransportNetwork-->Fr Gb-->DLCI
SGSN.
Table 2-5 FlexGb Integration Parameters Integration Parameter Length of SGSN NRI
Value Description Length of SGSN NRI
Location in Quick Configuration Template TransportNetwork--> SGSN Office --> SGSNNRILen
SGSN NULL-
TransportNetwork--> SGSN Office -->
NRI ID
SGSNNULLNRI
SGSN CN ID NRI
SGSN CN identification SGSN network route identification
TransportNetwork--> SGSN Office --> SGSNCNID TransportNetwork--> Nri--> NRI
Load allocate
SGSN Load Sharing
TransportNetwork--> SGSN Office -->
radio of SGSN
Ratio
ALLOCATERATIO
2.3.2
Gb Interface Office Configuration Gb interface office configuration involves the following sheets (V4_Template_TransportNetwork template): SGSN Office: configure SGSN office information.
2.3.3
Gb-interface Integration Parameter For different Gb-interface types, the sheets involved are different (V4_Template_TransportNetwork template), as detailed below: IP Gb integration (make sure the related IP has been configured in the IP related sheets in the V4_Template_Equipment template): Ip Gb: configure IP Gb integration related parameters. E1 Gb interface: Fr Gb: configure E1 Gb integration related parameters.
2.4
SDR Site Commissioning Configuration
2.4.1
Configuring IPOE Abis/IPAbis IP 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: SCTP Config(ABIS): configure the IPOE Abis/IP Abis service IP.
2.4.2
Configuring SDR Ground Resource The SDR ground resource is configured in the V4_Template_TransportNetwork template, which is explained per transmission mode (IP, IPOE) respectively.
2.4.2.1
Ground Resource Configuration for IP Site 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
The parameters to be planned:
Table 2-6 IP Path Group Parameter Name
Planning Principles
TRPATHGROUPSEQ (Path
The transmission path group ID should be the
Group Id)
same as the Site ID.
MODULE
Module No. is the same as the site module No.
TXBITRATE RXBITRATE
The recommended TX bandwidth of the transmission path group is 100000. The recommended RX bandwidth of the transmission path group is 100000.
Table 2-7 IP Bearer(ABIS): Parameter Name
Planning Principles
ANEID
ANEID should be the same as the site ID.
NEID
Site ID
MODULE
Site module No.
TXBITRATE RXBITRATE DESTIPADDR
The recommended TX bandwidth of the logical transmission path is 100000. The recommended RX bandwidth of the logical transmission path is 100000. Site IP address Set it to the transmission path group IP, i.e., the
TRPATHGROUPSEQ
TRPATHGROUPSEQ in the “IP Path Group” sheet.
2.4.2.2
Ground Resource Configuration for IPOE Site 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.
IP Bearer (ABIS): configure the office information of the IPOE sites
Lucent Channel (Optional): configure transparent channel related information.
The parameters to be planned:
Table 2-8 IP Bearer(ABIS) Parameter Name
Planning Principles
ANEID
ANEID should be the same as the site ID.
NEID
Site ID
MODULE
Site module No. The backward bandwidth of the logical
TXBITRATE
transmission path is configured according to the actual physical bandwidth.
The backward bandwidth of the logical RXBITRATE
transmission path is configured according to the actual physical bandwidth.
DESTIPADDR
Site IP address The transmission path group ID should be the
TRPATHGROUPSEQ
same as the Site ID.
Interface Board
The information of the E1 interface board used.
E1LIST
The slot of E1 interface board and the PCM No.
TSLIST
Timeslot configuration
MPLINK(MP Port No.)
It is the MP port No.
MPIPADDRESS
IP address of the MP port
MPIPADDRMASKLEN
IP address mask length of the MP port The IP header compression is required to be
IPHCOPT
enabled.
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.
2.
If the unnumbered port is required to be configured, it is unnecessary to configure MPIPADDRESS. The system will automatically create the corresponding unnumbered port and the static route that uses the unnumbered port (the static route network prefix should be the value of the DESTIPADDR parameter).
2.4.3
Radio Resource Configuration 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 SITE ID
Location in Quick Configuration Template GSM_Radio--> GGsmCell-->GBtsSiteManagerId
1.
2.
3.
4.
Cell ID
GSM_Radio--> GGsmCell-->GGsmCellId
LAC
GSM_Radio--> GGsmCell-->refGLocationArea
CI
GSM_Radio--> GGsmCell-->cellIdentity
NCC
GSM_Radio--> GGsmCell-->ncc
BCC
GSM_Radio--> GGsmCell-->bcc
RAC
GSM_Radio--> GGsmCell-->refGRoutingArea
FreqBand
GSM_Radio--> GGsmCell-->freqBand
BVC
GSM_Radio--> GGsmCell-->BVC
TRX ID
GSM_Radio--> GTrx-->GTrxId
BCCH arfcn
GSM_Radio--> GTrx-->arfcn
GGsmRelation
GSM_Radio--> GGsmRelation-->RELATIONCGI
Radio data configuration:
GGsmCell: configure GSM cells.
GTrx: configure TRX.
Adjacent cell configuration:
GGsmRelation: configure GSM adjacent cell relation.
GUtranRelation: configure UTRAN adjacent cell relation.
GEutranRelation: configure E-UTRAN adjacent cell relation.
Frequency hopping system:
GHoppingFrequency: configure RF frequency hopping system.
GHoppingBaseband: configure baseband frequency hopping system.
External resource configuration:
GExternalGsmCell: configure GSM external cells.
GExternalUtranCellFDD:configure UTRAN FDD external cells.
5.
GExternalUtranCellTDDLcr: configure UTRAN TDD external cells.
GExternalEutranCellFDD: configure E-UTRAN FDD external cells.
GExternalEutranCellTDD: configure E-UTRAN TDD external cells.
Baseband resource sharing in a site:
GSiteBaseBandShare: configure baseband resource sharing in a site (necessary for cran sites).
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).
GBssFunction: configure GSM logical function.
GHandoverControl: configure handover control.
GScHandoverControl: configure the sub-cell handover control.
GPsHandoverControl: configure PS handover control.
GFhHandoverControl: configure FH handover control.
GPsChannelSchedule: configure PS channel scheduling.
GPowerControl: configure power control.
GTs: configure timeslot.
3
Quick Data Configuration Template Filling Specifications This chapter introduces the filling specifications of three quick data configuration templates. The method of filling in V4_Template_Equipment.xls and V4_Template_TransportNetwork.xls varies in different scenarios. All configurations that are the same in different scenarios must be filled in unless otherwise specified. The different sheets configured in different scenarios will be specified by scenario, e.g., E1 A/IP A/IPOE/FE Abis/IP Gb/E1 Gb. For optional configuration sheets, Optional will be specified in Parameter Description. The sheets of which the filling instruction is not described do not need to be filled in. Field engineers should configure the parameters according to the actual situation. 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
3.1.1
Basic Info Configure the basic information of the bureau, including the operation & maintenance IP, logserver IP, etc.
Parameter Name MEID MODETYPE
Parameter Description Fill in the planned BSCID. Fill in the BSCID for MEID in all the sheets. 3: GSM OMP IP address, fixed as 129.0.1.1 (the factory setting of
OMPIPADDR
OMP IP) This OMP IP is a fixed IP in V4 BSC. Fixed as 129.200.0.1, the OMM bond2:1 address
OMPGATEWAY
This is similar to the eth6 in V3 BSC. For V4 BSC, this IP should be fixed.
OMPIPMASKLEN SNTPSERVER SNTPSYNCHANNEL
Keep the default: 8 Fixed as 129.200.0.1; the OMM bond2:1 interface IP, used as the OMP SNTP synchronization server Fixed as 1, Connected by OMM server OMCB operation and maintenance IP 1. Fill in it according to the planned IPAbis address, i.e.,
OMCBAGIPADDR
OMCB Channel IP (shares an IP with SCTP IP of IPAbis) 2. Take one IP from the planned IPAbis user plane loopback port IPs as OMCBAGIPADDR, which can also be used as the user plane loopback port IP. Fixed as 129.200.0.5, OMCB Server factory-set IP, OMM bond2:5 address.
OMCBSIPADDR
It is the IP of eth4/eth4:1 in V3 BSC and acts as the communications IP between the internal network and SDR. This IP is a fixed IP in V4 BSC.
OMCBSIPMASKLEN INNEROMCBIP TIMEZONESET SUMMFLAG
Keep the default: 8 Fill in the value according to the planning when UMTS OMCB supports multi-path protection; default 0.0.0.0 Fill in the time zone according to actual situation. The Daylight Saving Time flag; fill in the value according to the actual situation.
SUMMSTART SUMMEND SUMMOFFSET
The start time of Daylight Saving Time; fill in the default 0/0/0/0 when it is not supported. The end time of Daylight Saving Time; fill in the default 0/0/0/0 when it is not supported. The step of Daylight Saving Time; fill in the value according to the actual situation; recommended value: 60
Location on OMMR interface: 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.
3.1.2
Plmn Config Configure operator information, including operator information supported by the current NE and the adjacent NE.
Parameter Name
Parameter Description
USERLABEL
Fill in the user label of operator name information.
MEID
Fill in the planned BSCID. Fill in the value according to the planning. It is recommended
PLMNID
that it be set as MCC+MNC, e.g., 410006. This ID will be used in the tables of the following sections.
MCC
Fill in the MCC
MNC
Fill in the MNC
MNCBCDCODELEN
Default: 2
DEFAULTPLMNIND
Default: 1
ISLOCALPLMN
Default: 1
Location on OMMR interface: Managed Element > Plmn Group Configuration > PLMN Group
3.1.3
Shelf Config 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 MEID
Parameter Description Fill in the planned BSCID. Fill in the BSC Rack No. The RACKSEQ of all shelves
RACKSEQ
should be set as “1.” V4 BSC uses single rack currently.
SHELFSEQ
Fill in shelf No. 1 – 3. Fill in the shelf type. Currently, the hardware type is 33:ETCA V1, i.e., fill in “33.” 34:ETCA V2 is a new shelf
SHELFTYPE
type and is not used currently. 33:ETCA V1 34:ETCA V2 Master/slave shelf flag. 0:Not Master Shelf
ISMASTFLAG
1:Is Master Shelf Fill in “1” for the master shelf. Fill in “0” for the slave shelf.
Location on OMMR interface: Managed Element > Equipment > Rack > Shelf
3.1.4
Board Config 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 MEID BOARDINFO
Parameter Description Fill in the planned BSCID. Fill in the slot information of the board. Format: Rack/Shelf/Slot
PHYBRDTYPE
Fill in the physical board type.
LOGICBRDTYPE
Fill in the logical board type. Fill in “1” for the OMP board. For CRP, fill in the MODULESEQ according to the planning.
MODULESEQ
The value range is 3 – 63. Refer to Section 1.3.1. Separate the MODULESEQs with “;” Fill in “0” for all the other boards. For OMM, OMP, CRP, EGBS, and EGFS, the BACKUPMODE is 1+1 master/slave configuration by default, i.e., fill in “1” fixedly. For the boards in master/slave configuration, fill in the record of the slot on the left. The board information of the
BACKUPMODE
backup slot will be created automatically and does not need to be filled in. In V4 BSC, the BACKUPMODE of other interface boards and processing boards is M+N backup. In the configuration process, fill in “0” (no backup) for each board. For these boards, master/slave configuration can also be used if necessary.
MODETYPE EXTPORTTYPE
1:2G Fill in the type of the interface board actually used. The default value for other boards is 0, which means invalid. It is the optical interface board rate mode. Fill in this
SDHPORTMUXMOD
according to the on-site integration planning. Default: 1,
E
which means SDH AU-4. The default value for other boards is 0, which means invalid.
PCMMAPTYPE CRC4MODE
Valid only to the optical interface board. Do not fill in this item for other boards. It is the E1 frame format, which is valid only to the E1 interface. This parameter does not need to be configured for
other boards. Default: 1, which means double frame. Configure this parameter according to the integration planning of the interface on which the interface board is configured. E1 impedance. It is valid only to the E1 interface board. It is IMPEDANCE
not necessary to configure this parameter to other boards. Default: 0: 75Ω. Fill in the value according to the interface type of EGPB. Default: 2, i.e., fiber. This parameter does not need to be
WIRETYPE
configured for other boards. 2:Fiber(default value) 3:Cable Fill in the A-interface scenario where CRP is used. For the GSM mode, configure this parameter to “1” or “2” for CRP, and to “0” or “null” for other boards. 0:Invalid 1:TDMA
USESCENE
2:IPA Currently, it is recommended that the USESCENE parameter of CRP be set to IPA fixedly. Each CRP (CRP pair) is configured with two CMP modules. The USESCENE here is used only to restrict the number of CMP modules, and it is not related to the A-interface transmission.
Rear Card Type of AG
This parameter defines the rear card type of the AG boards.
Boards
This parameter is needed only for AG. It does not need to be configured for other modes including GSM, i.e., fill in “0” or leave it blank.
1.
At present, APS optical port protection needs to be configured manually. It is recommended using the following configuration: 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.
Location on OMMR interface: 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 Fill in the user label of this IP, for example, IPA_Interface,
USERLABEL
which identifies the interface board IP in the A Over IP scenario.
MEID
Fill in the planned BSCID. Fill in the board on which this IP is configured. Format: rack/shelf/slot
BOARDINFO
The loopback interface IP and virtual interface IP are not configured on any board, which are 0/0/0 by default. Fill in the real interface IP according to the actual position of the EGPB interface board.
MODULE
Only the virtual interface IP requires the configuration of module No.; the virtual address is configured on OMP by default; therefore, it is fixed as 1.
The loopback interface IP and real interface IP do not require the configuration of module No., but this field is the primary key for fill-in. It can be set as 1. Fill in the interface type of this IP address according to the actual purpose of each IP. IPA/IPGb/FE Abis interface address: 0:Interface. PORTTYPE
IPA/IPGb/FE Abis/IPOE control plane/user plane processing address: 1:Loopback port OMCB gateway virtual address/LMT forwarding virtual address: 2:Virtual Port. Fill in the No. of the interface IP address; The real interface address is unique in the board, which is sequenced from 1 to 4. The loopback interface address is unique in BSC, which is
LOCALPORT
sequenced from 1 to 128. Fill in 0 for all virtual interface addresses. 0:invalid, 1~4:real port, 1~128:loop port
SUBPORT
Normally it is the default: 0 (invalid) This field is required to be filled in if Vlans are divided for the real interface IP. For the real interface IP with Vlans, the filling method is as follows: 1. In the first record, fill in the interface of the physical board of the real interface IP; fill 0 for SUBPORT, and 0 for VLANID; fill in the MAC field according to the planning and value range in BSC; it is recommended that MAC field be left blank, because the system will allocate an MAC IP to the real interface automatically; fill 0.0.0.0 for IPADDR, and 0 for SUBNETMASKLEN. 2. In the second record, fill in the planned IP and Vlan information of the real interface; the SUBPORT field is numbered in sequence, starting from 1; fill in the planned Vlan for VLANID. The MAC field is null. Fill in the planned IP for IPADDR; fill in the planned mask length for SUBNETMASKLEN. 3. If the physical board interface is configured with more than one IP with Vlan, we can continue to configure the records with
IP and Vlan information, and number the SUBPORT field in sequence. Fill in the value according to the planning. If Vlan is planned, fill VLANID
in this field according to the explanation of the previous field. If Vlan is not planned, fill 0 (invalid).
VPNID
Fill in 0 (invalid) for all interface IPs. Loopback/virtual interface: fill in 00-00-00-00-00-00 (invalid) or leave it blank. Real interface: all the interfaces are planned together; value
MAC
range: 00:19:C6:3E:30:10 to 00:19:C6:4E:30:0F. It is recommended that this parameter be left blank, in this case, it will be allocated by the system. Fill in this item according to the actual planning. When there
IPADDR
are two or more IPs configured on the same real port, separate these IPs with “;”. Loopback port: fixed as 32. Real port: based on the actual planning. When there are two or
SUBNETMASKLEN
more IPs configured on the same real port, separate the mask bit with “;”. Virtual port: no need to be fill in
Location on OMMR interface: 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 MEID
Parameter Description Fill in the planned BSCID. Fill in the IPA/IPGb/IPAbis user plane loopback interface IP
SERVICEIP
defined in the sheet of Interface IP. Each IP occupies one line. IPA user-plane loopback port address: 0001 (i.e., the A interface uses this IP as the user-plane service IP.) IPGb user-plane loopback port address: 1000 (i.e., the Gb interface uses this IP as the user-plane service IP.) IPAbis user-plane loopback port address: 0110 (i.e., Abis_CS and Abis_PS share this IP as the user-plane service IP.)
2GIPAPPTYPE
If it is planned that the A interface and Abis interface share one user-plane service IP, this field should be configured to 0111 (i.e. A interface, Abis_CS, and Abis_PS share this IP as the uer-plane service IP.) Bit0=1:A Interface of GSM Network Bit1=1:Abis PS Interface of GSM Network Bit2=1:Abis CS Interface of GSM Network Bit3=1:Gb Interface of GSM Network
3GIPAPPTYPE
Do not fill in this item for the GSM mode.
AGIPAPPTYPE
Do not fill in this item for the GSM mode.
VPNID
Default: 0, i.e., invalid. Fill in the operator’s MCC and MNC, which should be separated with “:”, indicating that this service IP configuration
PLMNINFO
only applies to the Local PLMN Group. Default: 65535:65535, indicating that this service IP configuration applies to All PLMN.
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
3.1.7
Slave or Dsp Service Config 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 MEID BOARDINFO
Parameter Description Fill in the planned BSCID. Fill in the slot information of the CRP or ETCB board: rack/shelf/slot. To allocate IP (UDP port) for CRP Slave or ETCB DSP: IPA+IPAbis scenario: When the A interface and Abis_CS/Abis_PS share one userplane loopback port IP, fill in this shared IP. When the A interface and Abis interface use different user-plane
SERVICEIP
loopback port IP, the two IPs should be filled in and separated with “;”. TDMA+IPAbis scenario: Fill in the planned Abis_CS+ Abis_PS user-plane loopback port IP in the record of CRP board. Fill in the planned Abis_CS user-plane loopback port IP in the record of ETCB board.
IUBPRECFGIP
Not required for the GSM mode.
Location on OMMR interface: Managed Element > Transport Network > User Plane Service Configuration > Service IP Configuration of Slave
3.2
V4_Template_TransportNetwork
3.2.1
Choose The TransportNetwork template applies to the GSM/UMTS/AG multi-mode scenario. It contains many sheets. Select the scenario in the in the Choose sheet before data preparation, so as to hide unnecessary sheets and fields. Enable Macro before using this template. 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.
3.2.2
Local Office Configure BSC local office information in this sheet. Parameter Name MEID
Parameter Description Fill in the planned BSCID. 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: 2, i.e., Disable
NETAPPEARANCEFLAG
It is an integration M3UA parameter. It is invalid by default. Set this parameter only when it needs to be enabled. 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.
OPC14 OPC24
Configure this item according to on-site planning. It is a decimal 14-bit signaling code of BSC. Configure this item according to on-site planning. It is a
decimal 24-bit signaling code of BSC. MODETYPE
Default: 0, i.e., 2G
ATMADDR
Do not fill in this item for the GSM mode.
CSNRIBITNUM
Do not fill in this item for the GSM mode.
PSNIRBITNUM
Do not fill in this item for the GSM mode. It is necessary to fill in this item for GU dual-mode
BSCID
according to the planning. Do not fill in this item for other modes. By default, it is set the same as MEID.
Location on OMMR interface: Managed Element > Transport Network > No.7 Signalling Configuration > Local End Signalling Point
3.2.3
Static Route 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
USERLABEL
The static route ID, for example, Route_to_MSC
MEID
Fill in the planned BSCID.
ROUTESEQ
Configure it according to the sequence of routes in on-site planning; it is unique in BSC. Configure the static route destination address or IP segment,
ROUTEPREFIX
MSC/MGW/SGSN loopback IP, or SDR address according to the on-site planning.
SUBNETMASKLEN NEXTHOPIPADDR VPNID DISTANCE
Fill in the mask of the target IP according to the on-site planning. When the next hop type is IP, configure the next hope IP according to the on-site planning. Configure it according to the on-site planning. Default: 0 (invalid) Route management distance priority: the lower the value, the higher the priority. Route Distance is 1 by default. Bidirectional forwarding detection: BFD is disabled by default.
BFDSET
To enable it, the switch for this function should be enabled on the remote equipment.
IPOE scenario: If local PPP or MP port IP is configured in the IP Bearer(ABIS) sheet, it is not necessary to configure the static route to the SDR subnet. If local PPP or MP port IP is not configured in the IP Bearer(ABIS) sheet, it is necessary to configure the static route to the SDR subnet, to which the next hop is interface. Location on OMMR interface: Managed Element > Transport Network > IP Configuration > Route Global Configuration > Static Route(IPV4)
3.2.4
IP Path Group 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
USERLABEL
It is the user label of path group, used to distinguish offices.
MEID
Fill in the planned BSCID. Configure it according to the on-site planning. It is unique in BSC.
TRPATHGROUPSEQ
Recommended value: IPAbis office: 1-2000 IPA office: 2001-2048
FATHERID
Default: 65535 Configure it according to the on-site planning. It should be
MODULE
consistent with the home module planned for each office, for example, the modules of path group, transmission path, SCTP, and office. Configure it according to the on-site planning. If the physical IP interface in this path group is planned with Vlan, set it to
TRPATHGROUPTYPE
5; if not, set it to 2. 2:ETHERNET_NOVLAN (default) 5:ETHERNET_VLANTAG
PLMNID
Configure it according to the on-site planning. Fill in the PLMNID value in the sheet of Plmn Config. In the case of single Plmn, its value range is 0-100. Default:
PLMNRSVRATIO
0 In the case of multiple Plmn Groups, configure it according to the on-site planning. Configure it according to the on-site planning. Currently the EGPB board with GE interface is used, so it is
TXBITRATE
recommended that this parameter be configured to 1000000kbps; for the IPAbis site, it can be configured to 100000kbps.
RXBITRATE
The same as above.
For the IPAbis office, this sheet should be configured for the FE site, while it is not required for the IPOE site. The transmission path group is associated automatically with the IP Bearer(ABIS) sheet. Location on OMMR interface: Managed Element > Transport Network > Transmission Path Group
3.2.5
SCTP Config(ABIS) Configure the association information for the IPAbis office. The association information for each IPAbis office should be configured in a separate record. Parameter Name USERLABEL MEID
Parameter Description It is the user label of SCTP, which can be consistent with the SiteID. Fill in the planned BSCID. Fill in the planned association ID, which is consistent with the SiteID and unique in the BSC. It should be planned together
ASSOCIATIONSEQ
with the IPA interface association ID. Recommended value: IPAbis office association ID: 1-2000 IPA office association ID: 2001-2048
MODULE LOCPORT
Fill in the planned module No. of association, which must be consistent with the site module No. Fill in the planned local port No. of association, which should be consistent with the association ID and SiteID. 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.
VPNID1
Default 0: Invalid Fill in the planned remote port No. of association. Unlike BSCV3, the remote port No. here must be consistent with the
REMPORT
local port No., as specified in the BSCV4 configuration principles; it is also consistent with the association ID and SiteID.
Fill in the planned remote IP of association. The remote port REMIPADDR1
here refers to the association address at the SDR side, which is the IP of the SDR site.
MAXRTO
MINRTO
INITRTO
HEARTBEAT
DELAYACK
Default: 500 This parameter can be left blank. Default: 50 This parameter can be left blank. Default: 100 This parameter can be left blank. Default: 500 This parameter can be left blank. Default: 20 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. Location on OMMR interface: Managed Element > Transport Network > IP Configuration > Association
3.2.6
IP Bearer(ABIS) Configure Abis office and Abis logical link (transmission path) information. Parameter Name
Parameter Description
USERLABEL
Fill in the planned user label of base station.
MEID
Fill in the planned BSCID. Fill in the adjacent NE ID, including the adjacent cell IDs of the A office and SGSN office. It should be unique in BSC and consistent with SiteID.
ANEID
Recommended value: ANEID of Abis office: 1-2000 ANEID of A office: 2001-2048 ANEID of SGSN office: 3001-3016
NEID
Fill in the planned SiteID; the recommended value range is 1-2000.
Fill in the association ID configured in the sheet of SCTP ASSOCIATIONSEQ
Config(ABIS) corresponding to the Abis office; it is consistent with SiteID by default.
PLMNID
Fill in the value according to the on-site planning. Fill in the PLMNID value in the sheet of Plmn Config. Fill in the planned module No. The planning principles are: 1. The allocation of sites on different modules is balanced.
MODULE
2. If there is more than one LAC, each LAC should be allocated with different module numbers according to the quantity of sites. Fill in the bearer IP type. Default: 1.
ABISSRVBRSTYPE
1:IPv4 4:IPv6 7:IPv4 & IPv6 For the site that uses FE transmission, fill in 100000kbps.
TXBITRATE
For the site that uses IPOE transmission, configure this parameter according to the actual physical transmission bandwidth.
RXBITRATE
The same as above. This parameter does not need to be configured by default,
DESTIPADDR
because it will be generated automatically when static SCTP is used. Fill in the peer-end SDR IP when dynamic SCTP is used. This parameter does not need to be configured by default, because it will be generated automatically when static
DESTIPMASKLEN
SCTP is used. Fill in the peer-end SDR IP mask length when dynamic SCTP is used.
IPDOMAINNO TRPATHGROUPSEQ
It should be configured when multipath protection is supported. Default: 0 (invalid) Fill in the Path Group ID configured in the sheet of IP Path Group corresponding to the Abis office. It is consistent with SiteID by default. If IP transmission is used at the Abis office, this parameter must be filled in and should be consistent with the parameter in the "IP Path Group" sheet.
If IPOE transmission is used at the Abis office, this parameter does not need to be filled in and it will be generated automatically. For IPOE site, fill in the slot information of the interface BOARDINFO
board of this site according to on-site configuration in the format of Rack/Shelf/Slot. For IPOE site, fill in the E1 No. on the interface board corresponding to the site according to the on-site transmission planning.
E1LIST
1. Value range of E1 No. on EDTI board: 1-32 Value range of E1 No. on ESDTI board: 1-252 2. If more than one E1 is used in this site, the No. of each E1 has to be configured and separated from the others by “;”, such as “5;11”. For the IPOE site, fill in the TS on E1 corresponding to the
TSLIST
site according to the on-site transmission planning (1-31). If there is more than one E1, the TS for each E1 should be separated from others with “;”, for example, “1-31;1-30”. For the IPOE site, it should be configured as MP (value range: 1-512, unique in the board), no matter one or
MPLINK
multiple E1s are used. Do not fill in this parameter. It is recommended that the value be allocated automatically by the system. For the IPOE site, fill in the local MP IP according to the onsite 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. For the IPOE site, configure it according to the on-site
MPIPADDRMASKLEN
planning. Do not fill in this parameter. It is recommended that the value be allocated automatically by the system. Default: 24 Only for IPOE site. It is commended that the IP head
IPHCOPT
compression be enabled. IP header compression should also be enabled at the OMCB/SDR side.
1.
For the IPOE scenario, it is necessary to fill in BOARDINFO, E1LIST, TSLIST, MPLINK, MPIPADDRESS, and MPIPADDRMASKLEN.
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. Location on OMMR interface: Managed Element > GSM Logical Configuration > Link Configuration > Abis Office Managed Element > GSM Logical Configuration > Link Configuration > Multi Plmn > Logical Abis Link > Abis Transmission Path
3.2.7
Adjacent Office(CN) Configure A-interface adjacent office in this sheet. Parameter Name
Parameter Description
USERLABEL
Fill in the user label of the adjacent office.
MEID
Fill in the planned BSCID. Fill in the planned adjacent NE ID of the A interface. Refer to
ANEID
the description of ANEID in the IP Bearer(ABIS) sheet. Recommended value: 2001~2048 Fill in the planned ID of the adjacent office. GSM:1-64
OFFICEID
Recommended value: 1. If there is more than one A-interface adjacent office, number the offices in sequence.
NEID PLMNID
Fill in 1 by default for GSM. Configure it according to the on-site planning. Fill in the PLMNID value in the sheet of Plmn Config.
MODETYPE
Default: 3, i.e., GSM
NETYPE
Configure this parameter according to on-site planning. Normally, if CN provides only one set of signaling point, this
item should be configured as 576, i.e., MGW+MSCSERVER. If two sets of signaling point are provided simultaneously (MSC and MGW), create the 576:MGW+MSCSERVER office and the 64:MGW office respectively. 32:RNC 64:MGW 576:MGW+MSCSERVER 1023:SMLC Set this parameter according to the A-interface bearer type. SRVBRSTYPE
1:IP A; 2:TDM A. For the IPSig+TDM Voice scenario, it should be configured as 2:TDM A. Fill in the encode type of signalling point according to on-site
SPCTYPE
planning: 14:SPC 14 bits, 24:SPC 24 bits
DPC
Fill in the decimal point code according to on-site planning. Configure this parameter according to on-site planning, which needs to be negotiated with CN.
SSF
0: International SPC, 4: Reserved international SPC, 8: National SPC, 12: Reserved National SPC Fill in the value according to on-site planning. 1:Associated; 2:Quasi-associated; 3:No connection Normally, if CN provides only one set of MSC signaling point, i.e., BSC signaling is sent to MSC directly, set the MSC office
AM
to direct-connection. If CN provides two sets of signaling point (MSC and MGW) and the BSC signaling needs to be sent to MSC indirectly through the MGW signaling STP, set the MSC office to quasidirect-connection and MGW office to direct-connection.
BANDFLAG PROTOCOLTYPE
Whether to support broadband properties: 0: Not Support; 1: Support. Fill in “1” for IPA and “0” for TDMA. Configure this parameter according to on-site planning, which needs to be negotiated with CN. 1:CHINA
2:ITU 3:ANSI ATMADDR
Do not fill in this item for the GSM mode.
DEFAULTFLAG
Do not fill in this item for the GSM mode.
CAPACITYWEIGHT
Do not fill in this item for the GSM mode.
NUMOFNRI
Do not fill in this item for the GSM mode.
NRILIST
Do not fill in this item for the GSM mode.
Location on OMMR interface: 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.
3.2.9
SCTP Config(CN) 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
USERLABEL
Fill in the planned user label of SCTP.
MEID
Fill in the planned BSCID. Fill in the adjacent office ID of the A interface that the SCTP
OFFICEID
belongs to, i.e., the adjacent office ID of MSC in the Adjacent Office sheet. Fill in the planned SCTP ID, which should be unique within the
ASSOCIATIONSEQ
BSC and planned together with the SCTP of IPAbis. An 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. Fill in the property of SCTP according to the on-site IPA PROPERTY
integration planning. Normally, BSC is the SCTP client, i.e. fill in 2: Client. MSC is the SCTP server. This configuration needs to be negotiated with CN.
LOCPORT LOCADDR1 REMPORT REMADDR1
Fill in the local port No. of the planned IPA-interface SCTP BSC. Fill in the control-plane loopback address of the planned IPAinterface SCTP BSC. Fill in the remote port No. of the planned IPA-interface SCTP MSC. By default, it is consistent with LOCPORT. Fill in the control-plane loopback address of the planned IPAinterface SCTP MSC. Fill in the value according to on-site planning. It should be numbered in sequence and is unique in the BSC. One ASP
ASPSEQ
uses one SCTP. If an A-interface adjacent office is configured with multiple SCTPs, there should be multiple ASPs configured.
MAXRTO
Default: 500
MINRTO
Default: 50
INITRTO
Default: 100
HEARTBEAT
Default: 500
DELAYACK
Default: 20
Location on OMMR interface: Managed Element > Transport Network > IP Configuration > Association Managed Element > Transport Network > No.7 Signalling Configuration > Local End Signalling Point > Adjacent Office Information > ASP Configuration
3.2.10
M3uaAS Config(CN) 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.
MEID
Fill in the planned BSCID.
OFFICEID
Fill in the adjacent office ID of the MSC of this AS. Configure this item according to on-site planning. It should
ASID
be numbered in sequence. Usually, one MSC adjacent office is configured with one AS record. Fill in the ASP No. defined in the adjacent of the MSC. It
ASPSEQ
should be consistent with the ASPSEQ in the SCTP Config(CN) sheet. An AS can be configured with 16 ASPs at most, separated with English character “;”. Default: 0, i.e., False
EXISTLOCALCONTEXT
This parameter is usually used when an ASP serves more than one AS.
LOCALCONTEXT
Default: 4294967295, i.e., invalid. Set the planning value when the routing context is used. Default: 0, i.e., False
EXISTPEERCONTEXT
This parameter is usually used when an ASP serves more than one AS.
PEERCONTEXT
Default: 4294967295, i.e., invalid. Set the planning value when the routing context is used. Integration parameter: Configure it according to the on-site planning. Default: IPSP CLIENT, which should be
TAG
consistent with the PROPERTY in the “SCTP Config(CN)” sheet, i.e., BSC acts as the client, while MSC acts as the server. Integration parameter: Configure it according to the on-site
ASMODE
planning, which needs to be negotiated with CN. 1: Override, 2: Loadshare Value of N in loadshare mode: Under the loadshare mode,
MODEN
it is the minimum number of ASPs needed for the AS service, N>=1.When ASMODE is Override, fill in the default “0.” Value of K in loadshare mode: Under the loadshare mode,
MODEK
it is the number of ASPs for backup. N+K=ASP Number. When ASMODE is Override, fill in the default “0.”
When the AS traffic mode is configured as overload participation mode (Loadshare), the value of N must be greater than 0, and the value of N+K must equal the number of ASPs configured. Location on OMMR interface: 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
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID.
ROUTEID
It should be numbered in sequence. Usually, one AS record corresponds to an M3uaRoute record. Route range mode. Default: 0
ROUTEMODE
0:natural sort 1:ikebana sort
ASID1 ASID2 ASID3 ASID4
The AS object referenced. It should be consistent with the ASID in the M3uaAS Config sheet. If this route references multiple AS objects, it is necessary to fill in this item. Default: 0. If this route references multiple AS objects, it is necessary to fill in this item. Default: 0. If this route references multiple AS objects, it is necessary to fill in this item. Default: 0.
Location on OMMR interface: 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
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID.
OFFICEID ROUTEID1
Fill in the adjacent office ID of the A interface that the M3UA route set is allocated to. Fill in the M3UA ROUTEID associated with the adjacent office of the A interface. It should be consistent with M3uaRoute. Fill in the second M3UA ROUTEID associated with the
ROUTEID2
adjacent office of the A interface. It should be consistent with M3uaRoute. If the second route does not exist, fill in the default “0.”
Location on OMMR interface: Managed Element > Transport Network > No.7 Signalling Configuration > M3ua RouteSet
3.2.13
MSC Office This sheet is used to configure MSC office and the NRI Length/Null-NRI value in the FlexA scenario.
Parameter Name
Parameter Description
USERLABEL
Fill in the planned user label of the MSC office.
MEID
Fill in the planned BSCID. Fill in the value according to on-site planning. Default: 1. When
MSCID
there is more than one MSC office, they should be numbered in sequence. long:[1..16] Fill in the value according to on-site planning. In FlexA
MSCCNId
scenario, the value needs to be negotiated with CN side. Fill in “65535” in non-FlexA scenario.
AllocateRatio
MSC load sharing radio: It is an integration parameter; the value needs to be negotiated with the CN side in the FlexA scenario. This ratio applies only to the scenario that MS does not carry NRI or carries NULL-NRI and invalid NRI, or the scenario that MS carries NRI but the corresponding MSC is unreachable. In this case, BSC will access the MS with lower load according to the MSC load sharing ratio configured.
PLMNID
Fill in the value according to the on-site planning. Fill in the PLMNID value in the sheet of Plmn Config.
OFFICEID
Fill in the OfficeID defined for the MSC office in the Adjacent Office sheet. Fill in the value according to on-site planning. In FlexA
MSCNRILen
scenario, the value needs to be negotiated with CN side. Fill in “255” in non-FlexA scenario. Fill in the value according to on-site planning. In FlexA
MSCNULLNRI
scenario, the value needs to be negotiated with CN side. Fill in “0” in non-FlexA scenario.
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. Location on OMMR interface: 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
3.2.14
SGSN Office This sheet is used to configure SGSN office and the NRI Length/NULL-NRI value in the FlexGb scenario. Parameter Name
Parameter Description
USERLABEL
Fill in the planned user label of the SGSN office.
MEID
Fill in the planned BSCID. Fill in the planned adjacent NE ID of the Gb interface. Refer to
ANEID
the description of ANEID in the IP Bearer(ABIS) sheet. Recommended value: 3001~3016 Fill in the value according to on-site planning. Default: 1. When
SGSNID
there is more than one SGSN office, they should be numbered in sequence. Fill in the value according to on-site planning. In FlexGb
SGSNCNId
scenario, the value needs to be negotiated with SGSN side. Fill in “65535” in non-FlexGb scenario.
PLMNID ALLOCATERATIO
>Fill in the value according to the on-site planning. Fill in the PLMNID value in the sheet of Plmn Config. SGSN load sharing radio: It is an integration parameter; the value needs to be negotiated with the SGSN side in the FLEXGb scenario. This ratio applies only to the scenario that MS does not carry NRI or carries NULL-NRI and invalid NRI, or the scenario that MS carries NRI but the corresponding SGSN is unreachable. In this case, BSC will access the MS with lower load according to the SGSN load sharing ratio configured. Fill in the value according to on-site planning. In FlexGb
SGSNNRILen
scenario, the value needs to be negotiated with SGSN side. Fill in “255” in non-FlexGb scenario. Fill in the value according to on-site planning. In FlexGb
SGSNNULLNRI
scenario, the value needs to be negotiated with SGSN side. Fill in “0” in non-FlexGb scenario.
Location on OMMR interface: 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
USERLABEL
Fill in the planned user label of the MSC/SGSN office.
MEID
Fill in the planned BSCID. Fill in the NRI of the planned MSC/SGSN. This is an
NRI
integration parameter, and its value needs to be negotiated the CN side. Fill in the value according to the on-site planning. Fill in
PLMNID
the PLMNID value in the sheet of Plmn Config. Fill in the planned MSCID.
MSCID
0: Invalid MSC office If it is not configured, use the default 0. Fill in the planned SGSNID.
SGSNID
0: Invalid SGSN office If it is not configured, use the default 0.
Location on OMMR interface: 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
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID.
SGSNID
Fill in the value of SGSNID, which should be consistent with
the SGSNID in the SGSN Office sheet. Fill in the value according to on-site planning. It is an NSEID
integration parameter and should be consistent with the value at the SGSN side. Fill in the value according to on-site planning. It is an integration parameter and should be consistent with the value at the SGSN side. In static configuration, it is necessary to use a record for local endpoint and remote endpoint respectively
IPAddress
and fill in BSC loopback address and SGSN loopback address respectively. If there is more than one loopback address, it is necessary to use more one record. In dynamic configuration, it is necessary to fill in the loopback address of the local endpoint. Fill in the value according to on-site planning. It is an integration parameter and should be consistent with the value at the SGSN side.
UDPPort
In static configuration, it is necessary to configure the UDP port No. of the local endpoint and the remote endpoint. In dynamic configuration, it is only necessary to configure the UDP port No. of the local endpoint.
IPAddrLen
Default: 4:IPV4 Fill in the signaling weight planned. This is an integration
SIGWEIGHT
parameter and its value should be consistent with that at the SGSN side.
DATAWEIGHT
Fill in the data weight planned. This is an integration parameter and its value should be consistent with that at the SGSN side. Fill in the value according to on-site planning. 0:static configuration
SNCfgType
1:dynamic configuration This is an integration parameter and its value should be consistent with that at the SGSN side. Configure this parameter according to on-site planning. In static configuration, fill in “0.0.0.0” for both local endpoint
SGSNIPAddress
and remote endpoint. In dynamic configuration, fill in the loopback address of the remote endpoint.
SGSNUDPPort
Configure this parameter according to on-site planning.
In static configuration, fill in “0” for both local endpoint and remote endpoint. In dynamic configuration, fill in the UDP port No. of the remote endpoint. SGSNIPAddrLen
Default: 4:IPV4 Fill in the slot information of the IPGb interface board: Rack/Shelf/Slot.
BOARDINFO
In static configuration, it is only necessary to configure this item for the records of local endpoint. Do not configure this item for the records of remote endpoint.
Location on OMMR interface: 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 Method of filling in template in static configuration:
Method of filling in template in dynamic configuration:
3.2.17
No.7 PCM This sheet is used to configure the PCM of the A interface in the TDMA scenario. Parameter Name
Parameter Description
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID. Fill in the adjacent office ID associated with A-interface circuits. It
OFFICEID
should be consistent with the OFFICEID in the Adjacent Office(CN) sheet.
N7PCM
It is an integration parameter. Its value is the same as that at CN side. Configure this item according to on-site planning. Fill in the Slot
BOARDINFO
No. of the interface board of this A-interface E1. It must be set to EDAB/ESDAB/EDTB/ESDTB/ESDQB.
PCM
The PCM No. of the A interface. 1 means the first E1 of the interface board.
Location on OMMR interface: 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
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID.
LINK LINKSET
Configure this item according to on-site planning. Link ID should be numbered in sequence. Configure this item according to on-site planning. Link Set ID
should be numbered in sequence. An adjacent office supports a maximum of two link sets. It is recommended configuring one link set. Fill in the A-interface adjacent office ID associated with signaling OFFICEID
links. It should be consistent with the OFFICEID in the Adjacent Office(CN) sheet.
MODULE
Fill in the value according to on-site planning. It is recommended that the signaling links be evenly allocated to each CMP module. It is an integration parameter. Its value is the same as that at CN side.
LINKTYPE
1: 64K link 2: n*64K link 3: 2M link It is an integration parameter. Its value is the same as that at CN
SLC
side. One office can be configured with 16 links at most. The SLCs of these links should be different from each other. It is an integration parameter. Its value is the same as that at CN side.
LECM
1: Basic error correction method, transmission delay < 15 ms 2: Prevention cycle resending error correction mode, transmission delay >=15 ms
BOARDINFO PCM
Configure this item according to on-site planning, i.e., the Slot No. of the interface board where MTP2Link is on. The PCM No. of the E1 interface board where MTP2Link is on. “1” corresponds to the first E1 of the interface board. Fill in the start TS of MTP2Link. It is an integration parameter
TS
and its value should be consistent with the value at CN side. When LINKTYPE is 2M link, the start TS No. should be 1. It is the number of MTP2Link timeslots. It is an integration parameter and the value should be the same as that at CN side.
TSNUM
When LINKTYPE is 64K link, the value of TSNUM is “1.” When LINKTYPE is n*64K link, the value of TSNUM is “8 – 25.” When LINKTYPE is 2M link, the value of TSNUM is “31.”
Location on OMMR interface:
Managed Element > Transport Network > No.7 Signalling Configuration > Mtp2 Link
3.2.19
Mtp3 Route This sheet is used to configure the MTP3 signaling route in the TDMA scenario. Parameter Name
Parameter Description
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID.
ROUTEID
Configure this item according to on-site planning. ROUTEID should be numbered in sequence. 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
LINKSET_1
value according to the on-site planning. Use the Linkset data in the Mtp2Link sheet. Fill in “0” if the second bearer link group for the route does not exist. It is the signaling link permutation mode. Fill in the value according to on-site planning. Default: 0 0:Any arrangement (default value) 1:According to SLS_bit0 choose routing groups 2:According to SLS_bit1 choose link groups
LPM
3:According to SLS_bit2 choose link groups 4:According to SLS_bit3 choose link groups 5:According to SLS_bit0 and SLS_bit1 choose link groups 6:According to SLS_bit1 and SLS_bit2 choose link groups 7:According to SLS_bit2 and SLS_bit3 choose link groups 8:Floral sort 9:1:According to SLS_bit4 choose routing groups 10:According to SLS_bit3 and SLS_bit4 choose link groups
Location on OMMR interface: 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
USERLABEL
Fill in the planned user label.
MEID
Fill in the planned BSCID. Fill in the adjacent office ID associated with MTP3RouteSet. It
OFFICEID
should be consistent with the OFFICEID in the Adjacent Office(CN) sheet.
ROUTEID1
It is the first bearer route of the office route. Use the ROUTE ID data in the Mtp3 Route for this parameter. It is the second bearer route of the office route. Use the
ROUTEID2
ROUTE ID data in the Mtp3 Route for this parameter. Fill in “0” if the bearer route of the office route does not exist. 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. It is the fourth bearer route of the office route. Use the
ROUTEID4
ROUTE 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.
Location on OMMR interface: Managed Element > Transport Network > No.7 Signalling Configuration > Mtp3 RouteSet
3.3
GSM Radio Quick Configuration Template 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
3.3.1
GSiteBaseBandShare (Optional) This sheet needs to be configured only for Cran sites. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
GBtsSiteManagerId
Fill in SiteID according to the on-site planning.
UserLabel
Fill in the planned user label of the site. Configure this parameter according to the on-site planning.
BaseBandShare
0:Not Support 1:Support
bbRequestTraThs bbReleaseTraThs bbOverThs bbLowerThs
Traffic threshold for allocating baseband Fill in the value according to on-site planning. Default: 70. Traffic threshold for releasing baseband Fill in the value according to on-site planning. Default: 0. Channel busy threshold for urgent allocation of baseband Fill in the value according to on-site planning. Default: 80. Channel busy threshold for urgent release of baseband Fill in the value according to on-site planning. Default: 60.
Location on OMMR interface: 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 MEID
Parameter Description Fill in the planned BSCID. Share Area ID
GMocnAreaId
Configure this parameter according to the on-site planning. Defines the MOCN share-area attribute, i.e., whether it is
MocnAreaAttr
Share Area of Self BSC or Share Area of Other BSC. 0:Share Area of Self BSC 1:Share Area of Other BSC When MocnAreaAttr is “1:Share Area of Other BSC,”
refPlmnGroup
fill in “mcc,mnc.” If there are two or more parameters, separate them by ";".(refPlmnGroup and refGMPlmn are mutual exclusive to each other) When MocnAreaAttr is “0:Share Area of Self BSC,”
refGMPlmn
fill in “mcc,mnc.” If there are two or more parameters, separate them by ";".(refGMPlmn and refPlmnGroup are mutual exclusive to each other)
DistributeRatio
Set this parameter according to the planning.
Location on OMMR interface: 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 do not share the CN node. The operators share the radio network resources (cell TRX). 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. Refer to the MOCN Network Sharing Feature Guide for details.
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 Configure GSM cells. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
GBtsSiteManagerId
Fill in SiteID according to the on-site planning.
GGsmCellId
Fill in the planned Cell ID.
UserLabel
Fill in the planned user label.
CellIdentity
Fill in the planned CI.
ncc
Fill in the planned NCC.
bcc
Fill in the planned BCC.
freqBand
Fill in the planned cell frequency band. Default 0:GSM900
0:GSM900\(1..124\) 1:EGSM900\(0 .. 124,975 .. 1023\) 2:DCS1800\(512 .. 885\) 3:RGSM\(0 .. 124,955 .. 1023\) 4:PCS1900\(512 .. 810\) 7:GSM850\(128..251\) It indicates whether to enable subcell. subcellUsed
0:No 1:Yes It indicates the frequency band of subcell. 0:GSM900\(1..124\)(GSM900\(1..124\)) 1:EGSM900\(0 .. 124,975 .. 1023\)(EGSM900\(0 .. 124,975 ..
subFreqBand
1023\)) 2:DCS1800\(512 .. 885\)(DCS1800\(512 .. 885\)) 3:RGSM\(0 .. 124,955 .. 1023\)(RGSM\(0 .. 124,955 .. 1023\)) 4:PCS1900\(512 .. 810\)(PCS1900\(512 .. 810\)) 7:GSM850\(128..251\)(GSM850\(128..251\)) Fill in the planned cell type. Default 1:Macro Cell 0:Umbrella Cell
CellType
1:Macro Cell 2:Micro Cell 3:Micro-micro Cell 4:Extended Cell Configure this parameter according to the on-site planning. 0:Not Support
PsSupport
1:GPRS 2:EDGE When PS service is supported, it is necessary to configure a certain number of static PDCHs or dynamic TCHs. Fill in the planned BVC in the format of: SGSNID,NSEI,BVCI SGSNID,NSEI,BVCI
BVC
They should be separated by “,”. The SGSNID should be consistent with the SGSNID configured in the “SGSN Office” and “IP Gb” sheets. BVCI should be SiteID+CellID.
refGRoutingArea
Fill in the planned RAC value.
refGLocationArea
Fill in the MCC, MNC, LAC, and GMocnAreaId planned.
Separate them with “,”. Fill in “0” for GMocnAreaId. Configure this parameter according to the on-site planning. EmergencyCall
0: No 1: Yes Configure this parameter according to the on-site planning.
DynaHREnable
0: Not support 1: Support
bcchFrequency
Fill in the planned BCCH frequency of cell.
taAllowed
Fill in nothing or the planned value.
CcchConf
Fill in nothing or the planned value.
bsAgBlkRes
Fill in nothing or the planned value.
bsPaMframs
Fill in nothing or the planned value.
txInteger
Fill in nothing or the planned value.
msTxPwrMaxCCH
Fill in nothing or the planned value.
rxLevAccessMin
Fill in nothing or the planned value.
cellReselPI
Fill in nothing or the planned value.
reselOffset
Fill in nothing or the planned value.
penaltyTime
Fill in nothing or the planned value.
DownPowerBmp
Fill in nothing or the planned value.
preprocess
Fill in nothing or the planned value.
rachAccessMin
Fill in nothing or the planned value. Fill in the parameter according to the planning. If this
GLFShareId
parameter is not configured, this cell will not be involved in GL frequency spectrum sharing.
GroupCallControl CellScenarioName
VGCS/VBS (group call/broadcast) call support This is a new function and it is disabled by default. Cell scenario name
Location on OMMR interface: 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
MEID
Fill in the planned BSCID.
GBtsSiteManagerId
Fill in SiteID according to the on-site planning.
GGsmCellId
Fill in the planned Cell ID. Fill in the planned frequency-hopping system ID. If there is
fhsId
more than one frequency system, the systems should be numbered in sequence.
userLabel
Fill in the planned user label.
HSN
Fill in the planned frequency hopping SN.
MaArfcnList
Fill in the planned MA frequency list, in which the frequencies should be separated by “;”.
Location on OMMR interface: 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
MEID
Fill in the planned BSCID.
GBtsSiteManagerId
Fill in SiteID according to the on-site planning.
GGsmCellId
Fill in the planned Cell ID.
userLabel
Fill in the planned user label.
fhsId
Fill in the planned frequency hopping ID.
HSN
Fill in the planned frequency hopping SN.
MaArfcnList
Fill in the planned MA frequency list, in which the frequencies should be separated by “;”.
Location on OMMR interface:
Managed Element > GSM Logical Configuration > Cell Information Configuration > Baseband Hopping System
3.3.7
GTrx Configure TRX. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
GBtsSiteManagerId
Fill in SiteID according to the on-site planning.
GGsmCellId
Fill in the planned Cell ID.
GTrxId
Fill in the planned TRXID.
UserLabel
Fill in the planned user label.
BCCHMARK
Configure this parameter according to on-site planning. Fill in “1” for BCCH TRXs and “0” for other TRXs. Default: 0 (or null)
trxType
0:Common TRX 1:Extended TRX
trxPriority
Fill in the planned TRX priority, or null
pwrReduction
Fill in the planned static power level or null.
powerClass
Fill in the planned TRX power level or null.
tsc
Fill in the planned TSC, which should be consistent with the BCC of the base station.
tsc2
Fill in the planned TSC2. Default: 0
arfcn
Fill in the planned TRX frequency.
refGBtsPanel
Fill in the used TRX panel. It is not required for SDR sites. Fill in the used subcell. Default: 1
refGSubCell
In the scenario where subcell is used, fill in the value according to the planning. Configure whether TS frequency-hopping is supported.
TsFHSupport
0:No 1:Yes This function is seldom used. It is disabled normally.
refGHoppingBaseband
In the case of baseband frequency-hopping, configure it according to the on-site planning, which should be
consistent with GHoppingBaseband. refGHoppingFrequenc y maio
In the case of RF frequency-hopping, configure it according to the on-site planning, which should be consistent with GHoppingFrequency. In the case of RF frequency-hopping, configure MAIO according to the on-site planning.
staticSdNum
Fill in the number of static SDCCHs as planned.
staticPdNum
Fill in the number of static PDCCHs as planned.
dynTchNum
Fill in the number of dynamic TCHs as planned.
Location on OMMR interface: Managed Element > GSM Logical Configuration > Cell Information Configuration > Trx
3.3.8
GExternalGsmCell(Optional) Configure GSM external cells. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
userLabel
Fill in the planned user label of the external neighbor cell.
mcc
Fill in the MCC of the external neighbor cell.
mnc
Fill in the MNC of the external neighbor cell.
lac
Fill in the LAC value of the external neighbor cell.
cellIdentity
Fill in the CI value of the external neighbor cell. Fill in the frequency band of the external neighbor cell. Default 0:GSM900 0:GSM900\(1..124\)
freqBand
1:EGSM900\(0 .. 124,975 .. 1023\) 2:DCS1800\(512 .. 885\) 3:RGSM\(0 .. 124,955 .. 1023\) 4:PCS1900\(512 .. 810\) 7:GSM850\(128..251\)
bcchFrequency
Fill in the BCCH frequency of the external neighbor cell.
ncc
Fill in the NCC of the external neighbor cell.
bcc
Fill in the BCC of the external neighbor cell.
Configure this parameter according to the on-site planning. psSupport
0: No 1: Yes
rac
Fill in the RAC value of the external neighbor cell. Type of external adjacent cell 0:Umbrella Cell
cellType
1:Macro Cell 2:Micro Cell 3:Micro-micro Cell 4:Extended Cell
MsTxPwrMax
Maximum power of MS.
Location on OMMR interface: Managed Element > GSM Logical Configuration > External Resource Configuration > External GSM Cell Configuration
3.3.9
GExternalUtranCellFDD This sheet is used to configure FDD 3G external neighbor cells. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
userLabel
Fill in the user label of the external neighbor cells.
mcc
Fill in the MCC of the external neighbor cell.
mnc
Fill in the MNC of the external neighbor cells.
rnc_id
Fill in the RNC ID of the external neighbor cells.
ci
Fill in the CI of the external neighbor cells.
lac
Fill in the LAC of the external neighbor cells.
arfcn3g
Fill in the frequency of the external neighbor cells.
scCode
Fill in the FDD scrambling code of the external neighbor cells.
diversity
Fill in whether the external neighbor cells use Tx diversity.
rac
Fill in the RAC value of the external neighbor cell.
Location on OMMR interface:
Managed Element -> GSM Logical Configuration -> External Resource Configuration -> External UTRAN FDD Cell Configuration
3.3.10
GExternalUtranCellTDDLcr This sheet is used to configure TDD 3G external neighbor cells. Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
userLabel
Fill in the user label of the external neighbor cells.
mcc
Fill in the MCC of the external neighbor cell.
mnc
Fill in the MNC of the external neighbor cells.
rnc_id
Fill in the RNC ID of the external neighbor cells.
ci
Fill in the CI of the external neighbor cells.
lac
Fill in the LAC of the external neighbor cells.
arfcn3g
Fill in the frequency of the external neighbor cells.
CellPara
Fill in the cell parameters of the external neighbor cells.
diversity
Fill in whether the external neighbor cells use Tx diversity.
rac
Fill in the RAC value of the external neighbor cell. Fill in the bandwidth of the external neighbor cells.
bandWidth3g
0:3.84Mcps 1:1.28Mcps 3.84Mcps is not used currently. Default: 1. Fill in whether the external neighbor cells use SyncCase
syncCaseTstd
or TSTD (Time Switched Transmit Diversity). SyncCase means synchronization mode and is not used currently.
Location on OMMR interface: Managed Element -> GSM Logical Configuration -> External Resource Configuration -> External UTRAN TDD Cell Configuration
3.3.11
GExternalEutranCellFDD This sheet is used to configure FDD 4G external utran cells.
Parameter Name
Parameter Description
MEID
Fill in the planned BSCID.
userLabel
Fill in the user label of the external neighbor cells.
mcc
Fill in the MCC of the external neighbor cell.
mnc
Fill in the MNC of the external neighbor cells.
enbId
Fill in the ENODB ID of the external neighbor cells.
EUTRANID
Fill in the cell ID of the external neighbor cells.
PCID
Fill in the physical ID of the external neighbor cells.
ArfcnLTE
Fill in the frequency of the external neighbor cells.
TAC
Fill in the TAC of the external neighbor cells. Fill in the ENODB type of the external neighbor cells.
ENBInd
0:Home eNB 1:Macro eNB Fill in the Min. bandwidth of the adjacent channel of the external neighbor cells, which indicates the number of resource blocks that can be measured by MS. 0:1.4\(6RB\) 1:3\(15RB\)
measureBandwidth
2:5\(25RB\) 3:10\(50RB\) 4:15\(75RB\) 5:20\(100RB\) 6:reserved 7:reserved
Location on OMMR interface: Managed Element -> GSM Logical Configuration -> External Resource Configuration -> External E-UTRAN FDD Cell Configuration
3.3.12
GExternalEutranCellTDD This sheet is used to configure TDD 4G external neighbor cells. Parameter Name MEID
Parameter Description Fill in the planned BSCID.
userLabel
Fill in the user label of the external neighbor cells.
mcc
Fill in the MCC of the external neighbor cell.
mnc
Fill in the MNC of the external neighbor cells.
enbId
Fill in the ENODB ID of the external neighbor cells.
EUTRANID
Fill in the cell ID of the external neighbor cells.
PCID
Fill in the physical ID of the external neighbor cells.
ArfcnLTE
Fill in the frequency of the external neighbor cells.
TAC
Fill in the TAC of the external neighbor cells. Fill in the ENODB type of the external neighbor cells.
ENBInd
0:Home eNB 1:Macro eNB Fill in the Min. bandwidth of the adjacent channel of the external neighbor cells, which indicates the number of resource blocks that can be measured by MS. 0:1.4\(6RB\) 1:3\(15RB\)
measureBandwidth
2:5\(25RB\) 3:10\(50RB\) 4:15\(75RB\) 5:20\(100RB\) 6:reserved 7:reserved
Location on OMMR interface: Managed Element -> GSM Logical Configuration -> External Resource Configuration -> External E-UTRAN TDD Cell Configuration
3.3.13
GGsmRelation Configure GSM adjacent cell relation. Parameter Name MEID GBtsSiteManagerId
Parameter Description Fill in the planned BSCID. Configure the SiteID of the source cell according to the onsite planning.
GGsmCellId
Fill in the planned source Cell ID.
UserLabel
Fill in the planned user label of neighbor cell. Fill in the planned neighbor cell relation type.
RelationType
0:Handover and reselect 1:Reselect 2:Handover
RELATIONCGI
Fill in the planned neighbor cell CGI, which should be separated by comma: mcc,mnc,lac,ci.
RxLevMin
Configure it according to the on-site planning. Default: 15.
HoMarginPbgt
Configure it according to the on-site planning. Default: 30.
HoMarginRxLev
Configure it according to the on-site planning. Default: 30.
HoMarginRxQual
Configure it according to the on-site planning. Default: 30.
NCellLayer
Fill in the value according to on-site planning. Default: 0, i.e., Undefined
MacroMicroHoThs
Configure it according to the on-site planning. Default: 20.
MacroMicroHoN
Configure it according to the on-site planning. Default: 2.
HoPriority
Cell handover priority. Default: 3.
IsRelatedCell
Is related cell. Default: 0.
IsHoForceNcell
Is handover forced neighbor cell. Default: 0, i.e., No.
MaxForceHoDiff
Max level difference of force handover. Default: 9
HoForceResThs
Handover force resource threshold. Default: 40
RepPrioCS
CS adjacent cell report priority. Default: 0, i.e., low.
CCNSUPPORT
CCN support. Default: 1, i.e., yes
Location on OMMR interface: Managed Element > GSM Logical Configuration > Cell Information Configuration > Adjacent Relation Configuration > Adjacent GSM Cell Configuration
3.3.14
GUtranRelation This sheet is used to configure 3G adjacent cell relation.
Parameter Name MEID GBtsSiteManagerId
Parameter Description Fill in the planned BSCID. Fill in the SiteID of the source cell according to the on-site planning.
GGsmCellId
Fill in the planned source cell ID.
UserLabel
Fill in the planned user label of neighbor cell. Fill in the planned neighbor cell relation type.
RelationType
0:Handover and reselect 1:Reselect 2:Handover
RELATIONCGI
Fill in the planned neighbor cell CGI, which should be separated by comma: mcc,mnc,rnc_id,ci.
Location on OMMR interface: Managed Element -> GSM Logical Configuration -> Cell Information Configuration -> Adjacent Relation Configuration -> Adjacent UTRAN Cell Configuration
3.3.15
GEutranRelation This sheet is used to configure 4G adjacent cell relation. Parameter Name MEID GBtsSiteManagerId
Parameter Description Fill in the planned BSCID. Fill in the SiteID of the source cell according to the on-site planning.
GGsmCellId
Fill in the planned source cell ID.
UserLabel
Fill in the planned user label of neighbor cell.
RELATIONCGI
Fill in the planned neighbor cell CGI, which should be separated by comma: mcc,mnc, enbId,EUTRANID.
Location on OMMR interface: Managed Element -> GSM Logical Configuration -> Cell Information Configuration -> Adjacent Relation Configuration -> Adjacent E-UTRAN Cell Configuration
3.3.16
GGsmVpcRelation This sheet is used to configuration the paging cell relation. Parameter Name MEID GBtsSiteManagerId
Parameter Description Fill in the planned BSCID. Fill in the SiteID of the source cell according to the on-site planning.
GGsmCellId
Fill in the planned source cell ID.
UserLabel
Fill in the planned user label of neighbor cell.
RELATIONCGI
Fill in the planned neighbor cell CGI, which should be separated by comma: mcc,mnc, lac,ci.
Location on OMMR interface: 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 This sheet is used to configure interfering adjacent cell relation.
Parameter Name MEID GBtsSiteManagerId
Parameter Description Fill in the planned BSCID. Fill in the SiteID of the source cell according to the on-site planning.
GGsmCellId
Fill in the planned source cell ID.
UserLabel
Fill in the planned user label of neighbor cell.
RELATIONCGI
Fill in the planned neighbor cell CGI, which should be separated by comma: mcc,mnc, lac,ci. Whether to transfer IFTA information with this interfering cell In most cases, configuring interfering cell is to enable the
IFTATransfer
IFTA function. If the interfering cell is used in the IFTA function, set this parameter to “1.” Otherwise, set it to “0.” The default value of the interfering cell’s DL signal strength
DwLinkStrength1
measured in the current cell. If there is no history measurement data obtained, use the default “25” (typical estimated value of the neighbor cell RxLev). The default value of the current cell’s DL signal strength
DwLinkStrength2
measured in the interfering cell. If there is no history measurement data obtained, use the default “25” (typical estimated value of the neighbor cell RxLev). When there is no measurement value reported about an
NcellLowLevel
interference message, use the NcellLowLevel to estimate the history interference. Default: 10 (typical value of NcellLowLevel)
Location on OMMR interface: 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 Modifying module No. 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.
5.1
Configuring and Downloading Radio Data on ICM
5.1.1
Importing, Downloading, and Activating GSM Radio Quick Configuration Template on ICM The GSM Radio Quick Configuration template is under the \zxommr\umsclnt\deploy\template\GSM\GSM Radio Quick Configuration Template.xls directory. Import the GSM Radio Quick Configuration template through ICM with the following steps. Synchronize data from the snapshot area to ICM. Rightclick the target NE, select Synchronize, and click Yes in the pop-up Confirm dialog box.
Create plan area on ICM: Right-click the target NE, and choose Create Plan Area.
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.
After the data is activated, it is necessary to synchronize OMM data on ICM.
5.1.2
Exporting, Importing, Checking, Downloading, and Activating the Optimization Template on ICM 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.
The following is an example of the exported Optimization template.
142_OMMR_gsm_radi o_20120728122308.xls
Use the following method to import the Optimization template. 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.
After the data is activated, it is necessary to synchronize OMM data on ICM.
5.2
Special Subject 1: Capacity Expansion
5.2.1
Adding TRXs in Batch 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.
2.
5.2.2
Import, check, download, and activate data.
Creating Cell, TRX, and Neighbor Cell in Batch 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. GGsmCell: Create cell GTrx: Create TRX. GHoppingFrequency: Fill in RF frequency hopping group. GHoppingBaseband: Fill in baseband frequency hopping group. GTrx: Create TRX.
Fill in data in the following sheets to create a neighbor cell: GExternalGsmCell: Create 2G external adjacent cell. GExternalUtranCellFDD: Create UTRAN FDD adjacent cell. GExternalUtranCellTDDLcr: Create UTRAN TDD adjacent cell.
GGsmRelation: Create GSM neighbor cell relation. GUtranRelation: Create UTRAN neighbor cell relation.
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.
2.
Import, check, download, and activate data.
5.2.3
Configuring RF Frequency Hopping 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 TRX is changed from non-frequency-hopping to frequency-hopping, fill in the corresponding GHoppingFrequency DN column. The index is the FhsID in the GHoppingFrequency sheet.Modify the corresponding “ARFCN” column to “null.”Modify the corresponding MAIO according to the planning data. If the frequency-hopping TRX is newly-filled in, it is not necessary to fill in the “ARFCN” column.
3.
Import, check, download, and activate data.
5.2.4
Adding RF Frequency Hopping Group 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-FrequencyHopping When frequency-hopping is changed to non-frequency hopping in the Plan template, it is necessary to delete the frequency-hopping group and modify the frequency-hopping of the cell to non-frequency-hopping. Fill in “invalid” for “GHoppingFrequency DN.” The template needs to be imported twice before it can be modified successfully. It is necessary to modify the cell frequency-hopping association first and then delete frequency-hopping group.
5.2.6
Creating Baseband 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.
3.
Import, check, download, and activate data.
5.3
Special Subject 2: Timeslot Modification
5.3.1
Configuring and Modifying Channels Configure dynamic PDCCH, static PDCCH, static SDCCH, TCH dynamic/static modification in batch. 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) 8:SDCCH + CBCH(SDCCH + CBCH) 14:PDTCH+PACCH+PTCCH(PDTCH+PACCH+PTCCH) Method 2: Perform batch modification on OMM. Click Configuration Management > Data Batch Configuration Management.
Choose the NE to be modified.
In the topology tree, select GSM Logical Configuration > Cell Information Configuration > Trx > Ts.
Click the
button to add a filtering condition, e.g., in the following figure, the timeslot
of Gtrx=2,GTs=7 is filtered out, then click OK and the
button on the lower-left.
Choose TS Channel Combination, right-click it, and click Modify.
Fill in the modified channel code. Refer to Method 1.
Click the
or
on the upper-left to validate the modification.
5.4
Special Subject 3: Data Modification
5.4.1
Modification of Basic Parameters 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.
8.
Modify frequency (non-frequency-hopping): Export the Optimization template, and modify ARFCH in the GTrx sheet; if BCCH frequency is to be modified, besides the above operation, modify BCCH frequency in the GGSMCell sheet.
9.
Modify frequency (RF frequency hopping): Open the GSM Radio Quick Configuration
template,
and
modify
the
frequency
parameters
in
the
GHoppingFrequency sheet. If the related TRXs in the GTrx sheet have frequency, modify the value to “null.” Otherwise, no modification is needed.
5.5
Special Subject 4: Configuring CO-BCCH Cell with GSM Radio Quick Configuration Template
5.5.1
Creating CO-BCCH Cell in Non-frequency-hopping Scenario 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.
5.5.2
Creating CO-BCCH Cell in RF Frequency Hopping Scenario 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.
5.5.3
Modifying Non-CO-BCCH Cell to CO-BCCH Cell 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.
5.6
Special Subject 5: Neighbor Cell Modification
5.6.1
Adding and Deleting External Neighbor Cell 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.
Modifying Neighbor Cells:
Scenario 1: Add 10 GSM external cells on BSC, add five of them to each cell as the neighbor cells, then delete five neighbor cells of each cell, and add the other five external cells as the neighbor cells. 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.
5.6.2
Adding and Deleting 3G Reselection 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.
5.7
Special Subject 6: Capacity Reduction
5.7.1
Deleting TRXs in Batch 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.
3.
Delete non-frequency-hopping TRXs (non-BCCH TRXs): Open the GSM Radio Quick Configuration template, delete the TRXs in the GTrx sheet first, and then import the modified template into OMM and perform data synchronization.
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.
6.1
IPA(FlexA)+IPAbis+IPGb Scenario
IPA(FlexA)+IPAbis +IPGb Quick Configuration.zip
6.2
TDMA+IPAbis+IPGb Scenario
TDMA+IPAbis+IPGb Quick Configuration.zip
View more...
Comments
