05 ZXUR 9000 GSM Configuration 83P

ZXUR 9000 GSM
Configuration
Contents
 Introduction of Data Configuration File

 Equipment template configuration
 Transmission network configuration
 Radio network configuration
 Configuration Data Import
 Data Modification After Template Import
2
Introduction of Templates for Quick Data
Configuration
 V4_Template_Equipment.xls
 Data configuration related to rack, shelf,
board, office information, and basic
networking
 V4_Template_TransportNetwork.xls
 Parameter configuration for transmission
and integration on the A/Gb and Abis
interfaces
 GSM Radio Quick Configuration

Template.xls
 Radio parameter configuration on the
Abis interface
© ZTE All rights reserved 3

Source of Templates
 BSC data configuration templates are released in the OMM

version package.
 Path of Equipment and Transport Network templates:
 ums-clnt\deploy\template\GROUND
 Path of GSM Radio Quick Configuration Template

 ums-clnt\deploy\template\GSM

Introduction to the first sheet
 The first sheet of all quick data configuration templates is the “Template Info” sheet, which
provides the basic template information for OMM. By this sheet, OMM can judge whether
the template matches with OMM and acquire the categorization information of templates.
Therefore, the content of this sheet must be kept complete no matter which of other sheets
are selected

Introduction of Index Sheets in the Templates
 Index sheet of V4_Template_Equipment_en.xls

 Index sheet of V4_Template_TransportNetwork_en.xls depends on the Network

configuration type. A template can be generated like shown here.

 From previous sheet we can generate the following template

indexes

 Index sheet of GSM Radio Quick Configuration Template.xls

Parameter Properties in the Template
 The fifth line of the template is the description of parameter

properties as shown in the following figure:
 R=Read
 W= Write It can be modified.
 R= Read it can be Read
 I= Initial Must be configured during Data creation
 Primary Key It is compulsory during data creation and modification.
 The first and fifth lines of the template are not allowed to be modified;
otherwise the template cannot be imported normally.
Rows of the template files
 The first row ( purple ) : the parameter name in the database

 The second row ( yellow ) : the parameter name in the GUI of EMS
 The third row ( light blue ) : the parameter type ex : long, ipv4 , string,...etc.
 The fourth row ( green ) : the parameter description and value options if it’s a
list
 The fifth row ( light green ) : the parameter properties
1
2
3
4

The common columns
 All the sheets starts with three columns A,B and C which are as follow :
 Column A : Result : it’s used to show the result of the import of the template
 Column B : modification indication : it’s used to Add, delete, modify or pass (
ignore ) the data input
 Column C : Managed element object ID : it’s used to indicate the NE ID ( BSC in
this case ) in the EMS

Contents

13
UR9000 GSM Configuration
 IMPORTANT
 The following will describe the configuration steps and
parameters used by WINDTRE in the testbed.
 The configuration steps will show first how to fill up the
templates files and which parameters to configure by default
values.
 Each template will provides all sheets necessary to be configured
according to the testbed scenario
 Each sheet will provide the parameter name in GUI ( 2nr row )
and its value used by WINDTRE in testbed scenario

UR 9000 configuration details
 Equipment Template
 Sheets to be configured for this scenario are in purple colour

Equipment template configuration
 Basic info
 ME ID : 100
 Omp's omc port gateway : is for bond2:1

 OMCB Server IP Address : is for OMCB
 PLMN CONFIG
 BSC of ME ID 100 belongs to MCC 222 and MNC 88

 Shelf Config
 The BSC is configured with only one Rack of ETCA V2 . Only one
shelf is available ( master shelf N 3)

 Board Config
 EGPB2aboards(shelf 3, slot 15 & slot 16 ports 1) are used as Gb interface boards

 EGPB2aboards (shelf 3, slot 17 & slot 18ports 1)) are used as IP Abis interface boards
 ESDTT2aboards(shelf 3, slot 23 & slot 24ports 1) are used as TDM A interface
 Board Config
 Snapshot from testbed RNC1 / BSC1

 Interface IP
 Interface board : An interface board should be mentioned
by rack/shelf/slot. If the interface is a loopback then 0/0/0.
 Port type : indicates if the port is physical or logical (
0:Interface, 1:Loopback port, 2:Virtual port)
 MAC address : Mac address of interface board and ports
should be assigned manually according to plan .
 Each interface( GB, ABIS, A) could be configured with one or
more Ips. Depending on the system capacity, dimensioning
and redundancy protection.
 In this scenario we have 2 IPGB interfaces on slot 15 and 16
 2 interfaces for Abis on slot 17 and 18
 2 loopback IPs for Gb, 2 for ETCB and 2 for Abis
 Note : A interface is not represented as it uses TDM-A

 Interface IP

 Service IP :
 Assign IP used for UP service to different Interfaces as follow :
Bit0=1:A Interface, Bit1=1:Abis PS Interface, Bit2=1:Abis CS
Interface, Bit3=1:Gb Interface of
Bit 3 Bit 2 Bit 1 Bit 0
GB Abis-CS Abis - PS A
 Example : 100 means Abis-CS only

 From previous IP interface table we have :
IP1 IP2
IPGB 192.168.187.114 192.168.187.115
ETCB 192.168.163.132 192.168.163.133
Abis 192.168.163.134 192.168.163.135
 Service IP
 192.168.163.132 and 192.168.163.132 used for Abis-CS

 Slave or Dsp service config
 Slots 9 and 10 for USP2a . Slots 11 and 12 for ETCB

 One service IP can support one or more interface types.
 Every set of service IPs should cover all interface types.
 One set must be filled in one line of record.

Contents

26
Transmission network configuration
 BSC protocol stack:

 TDM A interface
iBSC MSS
BSSAP BSSAP
TDM A UP SCCP SCCP
MTP3 TDM A CP MTP3
MTP2 MTP2
Physical Layer Physical Layer

 BSC protocol stack:

 IP A interface
BTS BSC IP A CP MSS

BSC MGW
RR BSSAP BSSAP
Payload Payload
SCCP SCCP
RTP IP A UP RTP BTSM BTSM
M3UA M3UA
UDP UDP SCTP SCTP SCTP SCTP
IP IP IP IP IP IP
MAC/PPP MAC/PPP MAC / PPP MAC / PPP MAC / PPP MAC / PPP

 IPGB interface
 CP UP

 The Transmission netwrok configuration will be divided into 3

parts :
 Abis Integration
 GB integration
 A integration
 The 3 interfaces integration flow require the creation of “Local

office “namely the BSC1 which is common to all.

 Local office
 BSC ID 100 is created with OPC 16170 ( 14 bits )

Contents
 Abis
 GB
 A

32
ABIS integration
 Abis integration flow Site name VLAN for 2G 2G IP
1. Local office WZ001L 2001 192.168.166.4
2. Static Route
3. SCTP Config(ABIS)
4. IP Path Group
5. IP Bearer(ABIS)
the Control & user plane work flow of the Abis interfaces.The control ip
and user plane ip is same. CDR/CRP board Fulfills service processing
function, there are CMP and RUP models in one CDR/CRP board. site.

Abis integration
 Static Route
• Configure the Static Route in the V4_Template_TransportNetwork.
• MSC, MGW, SGSN, and SDR each has an interface board IP. If the IP addresses do not belong
to the same network section, the static route should be configured.
Parameter Name Parameter Description

USERLABEL
Configure this parameter according to on-site planning.
MEID
ROUTESEQ Fill in this item according to the sequence of routes in on-
site planning.
ROUTEPREFIX According to on-site planning, it can be set as either
MSC/MGW/SGSN loopback address or SDR address.
SUBNETMASKLEN Default: 32
NEXTHOPTYPE Configure this parameter according to on-site planning.
0:IP address
1:Interface
NEXTHOPIPADDR When the next-hop is an IP, configure this parameter
according to on-site planning.
VPNID
DISTANCE Configure this parameter according to on-site planning.
The default of Route Distance is 1.
BFDSET
By default, BFD is disabled.

ABIS Integration
 IP Path group :
 Path Group ID 1 is created for BTS1 with 1Gbps bandwidth

ABIS integration
 SCTP Config ( Abis)
 Sctp association id 1 is created between BSC ( IP :

192.168.163.134) and BTS 1 ( 192.168.166.4)
 Local port / remote port : 20001/ 20001
ABIS integration
 IP Bearer (ABIS) : UP link between BSC and BTS1
 Site ID 20001 is created with ANEID 1.

 The IP path bearer is 1 Gbps bandwidth and connect BSC with
BTS 1 ( IP : 192.168.166.4)
Contents

 Abis integration
 GB integration
 A integration
38
GB integration
IPGB integration flow
1. Local office
2. SGSN Office
3. Static Route
4. NRI
5. Ip Gb Descripti
on Board Port Local End Peer End Mask Vlan
BSC1 GB EGPB2a(1-3- 192.168.187.1 192.168.187.1
GE2:1 30 602
Interface IP1 15) 18 17
BSC1 GB EGPB2a(1-3- 192.168.187.1 192.168.187.1

GE2:1 30 603
Interface IP2 16) 22 21
BSC1 Gb 192.168.187.1
N/A NA /32 /32 N/A
loopback IP 1 14
BSC1 Gb 192.168.187.1
N/A NA /32 /32 N/A
loopback IP 2 15

GB integration
 SGSN office
 Two SGSN defined as ANEID 3002 and 3003 for SGSN ID 2 and
SGSN ID 3
GB integration
 Static Route
• Configure the Static Route in the V4_Template_TransportNetwork.
• MSC, MGW, SGSN, and SDR each has an interface board IP. If the IP addresses do not belong
to the same network section, the static route should be configured.
Parameter Name Parameter Description

USERLABEL
MEID
ROUTESEQ Fill in this item according to the sequence of routes in on-
site planning.
ROUTEPREFIX According to on-site planning, it can be set as either
MSC/MGW/SGSN loopback address or SDR address.
SUBNETMASKLEN Default: 32
NEXTHOPTYPE Configure this parameter according to on-site planning.
0:IP address
1:Interface
NEXTHOPIPADDR When the next-hop is an IP, configure this parameter
according to on-site planning.
VPNID
DISTANCE Configure this parameter according to on-site planning.
The default of Route Distance is 1.
BFDSET
By default, BFD is disabled.
GB integration
 NRI :
 Allocation of NRI 2 to SGSN2 and NRI 3 to SGSN3

GB integration
 Ip GB
 Two IPGB links created for each SGSN from EGPB boards slot 15
and 16
Contents
 GB integration
 TDM A integration
 Ip A integration
44
TDM A integration
 TDM A integration flow

 Local office
 Adjacent office ( CN)
 No 7 PCM
 Mtp2 Link
 Mtp3 Route
 Mtp3 RouteSet
 MSC office

TDM A integration
 Adjacent office (CN).......1
 MSC ANEID 2001 with OFFICE ID 1 is defined. DPC is 16201

 MGW ANEID 2002 with OFFICEID 2 is defined. DPC is 7945
TDM A integration
 Adjcent office ( CN) ......2

TDM A integration
 No 7 PCM
 4 PCMs created 2 ,3, 4 and 5 in the ESDTT2a board slot 23

TDM A integration
 Mtp2 Link
 Mtp2 link 1 and linkset 1 are defined on PCM 1 with slot number
31 as signalling.

TDM A integration
 Mtp3 Route
 Route ID 1 is defined using Link Set 1

TDM A integration
 Mtp3RouteSet
 Two Route set defined for MSC and MGW

TDM A integration
 MSC Office
 MSC office is defined

Contents
 GB integration
 TDM A integration
 Ip A integration
53
IPA Signal Flow
CMP
Control Plane
Switch Network
EGPB EGPB A
Abis EDTI
ESDTI
EDTT User Plane
Switch Network
RUP

All-IP Control Plane Data Flow
E E
G G
IPAbis IPA
P CMP P
B B
SCTP
SDR EGPB CMP EGPB MSC

All-IP User Plane Data Flow
IPA
SDR EGPB RUP EGPB MGW

IPA Networking Modes
 The control plane and user plane are logically independent.

 Each of the two lines involves four IPs.
 BSC control plane interface IP and BSC user plane interface IP can
be the same.

 IPA networking mode can be classified by two criteria:

 Whether the interface address at BSC is in the same network segment
with that at CN :
 If they are in the same network segment, only the switch is needed for IPA networking,
and the router is not needed.
 If they are in different network segments, both the switch and router are needed for IPA
networking.
 How the control plane and the user plane use the interfaces at BSC side:
 The control plane and the user plane use different EGPB physical interfaces configured
with different IP addresses, but do not use sub-interfaces.
 The control plane and the user plane use the same EGPB physical interface configured
with the same IP address, but do not use sub-interfaces. (Frequently used)
 The control plane and the user plane use the same EGPB physical interface, different
sub-interfaces configured with different IP addresses.
 The control plane and the user plane use the same EGPB physical interface configured
with different IP addresses, but do not use sub-interfaces. (Not often used)
 1.The control plane and the user plane use different EGPB physical
interfaces configured with different IP addresses, but do not use sub-
interfaces.
Networking mode 1- The control plane and the user plane using different physical interfaces
Virtual IP Interface IP Interface IP Virtual IP

of BSC CP of BSC CP Switch 1 of MSC CP of MSC
A B C D
Virtual IP Interface IP Interface IP Virtual IP

of BSC UP of BSC UP Switch 2 of MGW UP of MGW
A’ B’ C’ D’
 For the static route of BSC control plane, set Next hop IP as the
interface IP of CN (C)
 For the static route of BSC user plane, set Next hop IP as the
interface IP of CN (C’)

 2.The control plane and the user plane use the same EGPB physical
interface configured with the same IP address, but do not use sub-
interfaces. (Frequently used)
Networking mode 2 – The control plane and the user plane using the same physical interface but different sub-
interfaces
Virtual IP Interface Virtual IP

of BSC CP IP of MSC of MSC
Interface IP of CP C D
A
BSC CP B
Interface IP Switch VLAN1、
Interface IP of
ofBSCBSC
UP “B”
B’
VLAN2

of BSC UP IP of MGW of MGW
A’ UP C’ D’

 3.The control plane and the user plane use the same EGPB
physical interface, different sub-interfaces configured with
different IP addresses.
Networking mode 2 – The control plane and the user plane using the same physical interface but different sub-
interfaces

of BSC CP IP of MSC of MSC
Sub-interface IP CP C D
A
of BSC CP B
Switch VLAN1、
Sub-interface IP
VLAN2
of BSC UP B’

of BSC UP IP of MGW of MGW
A’ UP C’ D’

 4.The control plane and the user plane use the same EGPB physical
interface configured with different IP addresses, but do not use sub-
interfaces. (Not often used)
Networking mode 3 – The control plane and the user plane using the same physical interface configured with
different IP addresses
Interfac Virtual
Virtual IP
e IP of IP of
of BSC CP A
MSC CP C MSC D
Interface IP
of BSC CP B
Switch
Interface IP
of BSC UP B’
Virtual IP Interface Virtual
of BSC UP IP of MGW IP of
A’ UP C’ MGW D’
 For the static route of BSC control plane, set Next hop IP as the interface
IP of CN (C)
 For the static route of BSC user plane, set Next hop IP as the interface IP
of CN (C’)
 5.If the interface address of BSC is not in the same network

segment with that of CN, it is necessary to add a router between
them. The following figure shows the networking mode.
Networking mode 2 – The control plane and the user plane using the same physical interface but different sub-interfaces
Virtual Interface Virtual IP

IP of BSC IP of MSC of MSC
Sub-interface IP CP D E
CP A
of BSC CP B
Switch VLAN1,
Sub-interface of Router C VLAN2
BSC UP B’
Virtual
Interface Virtual IP
IP of
IP of MGW of MGW
BSC UP
UP D’ E’
A’
 For the static route of BSC, set Next hop IP as the IP of the
router (C)

Parameters of IPA Integration
BSC CN
BSC signaling point code and sub-service field MSC signaling point code and sub-service field
Network appearance Network appearance
Signaling sub-system Signaling sub-system
Virtual IP of BSC control plane Virtual IP of MSC control plane
Virtual IP of BSC user plane Virtual IP of MGW user plane
Interface IP of BSC control plane Interface IP or router IP of MSC control plane
Interface IP of BSC user plane Interface IP or router IP of MGW user plane
Protocol type, property and port No. of the Protocol type, property and port No. of the
application server process application server process
Whether there is a routing context identifier and Whether there is a routing context identifier and
what is the value of the identifier what is the value of the identifier
Service mode and protocol type supported by the Service mode and protocol type supported by the
application server process application server process
MCC/MNC/LAC/CI MCC/MNC/LAC/CI
The interface board ‘s port work mode (self- The interface board ‘s port work mode (self-
adaptive/forced), rate, work mode (duplex or not) adaptive/forced), rate, work mode (duplex or not)

Parameters of IPA Integration
Parameter Location in the quick configuration template
Signaling Protocol Type TransportNetwork-->Adjacent Office(CN)
MSC Signaling Point Code TransportNetwork-->Adjacent Office(CN)
BSC Signaling Point Code TransportNetwork-->Local Office
MSC Signaling Point Type TransportNetwork-->Adjacent Office(CN)
BSC Signaling Point Type TransportNetwork-->Local Office
SSF TransportNetwork-->Adjacent Office(CN)
TransportNetwork-->Static Route
IP of MSC Control Plane TransportNetwork-->IP Path（CN）
TransportNetwork-->SCTP Config（CN）
IP of MGW User Plane TransportNetwork-->Static Route
Equipment-->Interface IP
Interface IP of BSC Control Plane
TransportNetwork-->SCTP Config（CN）
Interface IP of BSC User Plane Equipment-->Interface IP
Loopback IP of BSC Control Plane Equipment-->Interface IP
Equipment-->Interface IP
Loopback IP of BSC User Plane Equipment-->Service IP
Equipment-->Slave config
Application type of ASP TransportNetwork-->SCTP Config（CN）
AS application server type（TAG） TransportNetwork-->M3uaAS Config（CN）
Whether exist context for AS TransportNetwork-->M3uaAS Config（CN）
M3UA ROUTEMODE TransportNetwork-->M3uaAS Config（CN）
Local Port No. of SCTP (A interface) Association TransportNetwork-->SCTP Config（CN）
Peer Port No. of SCTP (A interface) Association TransportNetwork-->SCTP Config（CN）
IPA Quick Configuration Template
 Equipment table
 PLMN Config: MCC, MNC
 Board Config: IPA-related boards (EGPB, RUP, CMP)
 Interface IP: IPA interface IP, IPA loopback IP
 Service IP: define the service IP of IPA user plane;
 Slave Config: associate the service IP of IPA user plane with the RUP board.

IPA Quick Configuration Template
 Transport Network table:

 Local Office: define the office’s signaling point;
 Static Route: configure the IPA route;
 IP Path Group: configure the IPA route group;
 Adjacent Office(CN): configure the MSC adjacent office;
 IP Path(CN): configure IPA route;
 SCTP Config(CN): configure IPA association, ASP;
 M3uaAs Config(CN: configure AS and M3UA Route;
 M3uaRouteSet: associate adjacent office and M3UA Route;
 MSC Office: configure Flex A, multi-PLMN.

Contents

68
Radio network configuration
 Template : GSM Radio Quick Configuration Template.xls
SITE freque
BSC SITE Cell
ME ID UserLa Cell ID ncyBa NCC BCC LAC RAC
Name ID Name
bel nd
WZ001 222-88-
20011 1800 7 0 1
D1 25000
100 BZTP1 20001 WZ001
WZ001 222-88-
20012 1800 7 1 1
D2 25000
 For initial configuration only the purple colour sheets need to be

configured, other sheets will be configured by default at first
then optimized.

 GGsmCell
 GTrx

 GGsm cell
 Cell ID 20011 and 20012 are created on Band 2 (DCS-1800 MHz)

 GGsm Cell
 The Two cells 20011 and 20012 support EDGE, belongs to SGSN
ID 2 and NSEI 16170.
 Rac is 1 lac is 25000
 GTrx
 Both cells ( here related by GSM Cell Configuration ID 1 and 2 )

have only one TRX
 GTrx
 TSC 1 and TSC 0 are assigned for Cell 20011 and 20012
respectively
Contents

75
Configuration Data Import - Step 1
 Configuration management :
 Create subnetwork
 Set subnetwork ID and
MCC

Configuration Data Import
 Create managed element from the subnetwork and

 Fill in proper parameters such as :
 User Label : BSC1

 Managed Element type : GSM
 Managed Element IP Address : 129.0.1.1
 Save

Configuration Data Import
 Right click on the ME and choose the “import quick

configuration data “

 In the window of Import Quick Configuration Data, click

Choose to locate the template to be imported.
 Click Open.

 Click Execute to import the template.
 Import and execute the Equipment, TransportNetwork, and Radio Quick Configuration
Templates in the same way.

 The template import is complete.
 In the Result column, if Success Number equals Total Number, it

indicates all the templates are imported completely; otherwise, it
indicates some records are not imported.
 View the import result: The result file is zipped and saved by EMS in the same
path as the saved templates . Unzip the file to view the details.
 In the result file, the import result is shown in Column A (Result), and the
MODIND field for a successful record is automatically modified to “P” in
Column B.

Thank you

05 ZXUR 9000 GSM Configuration 83P

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

05 ZXUR 9000 GSM Configuration 83P

Uploaded by

Copyright:

Available Formats

ZXUR 9000 GSM

 Introduction of Data Configuration File

 GSM Radio Quick Configuration

© ZTE All rights reserved 3

 BSC data configuration templates are released in the OMM

 Path of GSM Radio Quick Configuration Template

© ZTE All rights reserved 4

© ZTE All rights reserved 5

© ZTE All rights reserved 6

 Index sheet of V4_Template_TransportNetwork_en.xls depends on the Network

© ZTE All rights reserved 7

 From previous sheet we can generate the following template

© ZTE All rights reserved 8

 Index sheet of GSM Radio Quick Configuration Template.xls

© ZTE All rights reserved 9

 The fifth line of the template is the description of parameter

 The first row ( purple ) : the parameter name in the database

© ZTE All rights reserved 11

© ZTE All rights reserved 12

 Introduction of Data Configuration File

© ZTE All rights reserved 14

© ZTE All rights reserved 15

 Omp's omc port gateway : is for bond2:1

 BSC of ME ID 100 belongs to MCC 222 and MNC 88

© ZTE All rights reserved 17

© ZTE All rights reserved 18

 EGPB2aboards(shelf 3, slot 15 & slot 16 ports 1) are used as Gb interface boards

© ZTE All rights reserved 20

© ZTE All rights reserved 21

© ZTE All rights reserved 22

 Example : 100 means Abis-CS only

 192.168.163.132 and 192.168.163.132 used for Abis-CS

© ZTE All rights reserved 24

 Slave or Dsp service config

 Slots 9 and 10 for USP2a . Slots 11 and 12 for ETCB

© ZTE All rights reserved 25

 Introduction of Data Configuration File

 BSC protocol stack:

© ZTE All rights reserved 27

 BSC protocol stack:

BTS BSC IP A CP MSS

© ZTE All rights reserved 28

© ZTE All rights reserved 29

 The Transmission netwrok configuration will be divided into 3

 The 3 interfaces integration flow require the creation of “Local

© ZTE All rights reserved 30

 BSC ID 100 is created with OPC 16170 ( 14 bits )

© ZTE All rights reserved 31

 Radio network configuration

 Abis integration flow Site name VLAN for 2G 2G IP

1. Local office WZ001L 2001 192.168.166.4

© ZTE All rights reserved 33

Parameter Name Parameter Description

© ZTE All rights reserved 34

 Path Group ID 1 is created for BTS1 with 1Gbps bandwidth

© ZTE All rights reserved 35

 Sctp association id 1 is created between BSC ( IP :

 Site ID 20001 is created with ANEID 1.

 Introduction of Data Configuration File

 Configuration Data Import

BSC1 GB EGPB2a(1-3- 192.168.187.1 192.168.187.1

© ZTE All rights reserved 39

Parameter Name Parameter Description

 Allocation of NRI 2 to SGSN2 and NRI 3 to SGSN3