06 ZXUR 9000 UMTS Configuration 85P

ZXUR 9000 UMTS
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 IU/IUR/IUB
interfaces
 UMTS Radio Quick Configuration

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

Source of Templates
 RNC data configuration templates are released in the OMMR

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

 ums-clnt\deploy\template\UMTS

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 UMTS 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 ( RNC in
this case ) in the EMS

Contents

13
UR9000 UMTS 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 ( 2nd 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
 Omp's omc port gateway : is for bond2:1

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

 Shelf Config
 The RNC1 is configured with only one Rack of ETCA V2 . Only

one shelf is available ( master shelf N 3)

 Board Config
 One pair of USP2a is used at slot 9/10 with logical module as CDR 3,64,65.
 One EGPB2a is used at slot 17
 4 interface boards EXGB1a are used at slots ( 23/24/25/26)

 Board config
 Sapshot from testbed RNC1/BSC1

 Global Info
 This sheet indicates the default IP fragment reassembly board. If no

fragment reassembly board is configured or the configured fragment
reassembly board is abnormal, the database will select a board as the
default fragment reassembly board among all valid interface boards
 Related feature : ZTE UMTS RNC IP UTRAN Feature Guide(V4)
 Interface IP
 Interface board : An interface board should be mentioned by
rack/shelf/slot. If the interface is a loopback then 0/0/0. Common Ips
 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 ( Iu, Iur, Iub ) could be configured with one or
more Ips. Depending on the system capacity, dimensioning
and redundancy protection.
 In this scenario we have 2 Ips for each interface ( Iub, Iucs,
Iups, Iur ) per CP and same per UP ( except Iucs and Iur CP
which share the same IP )
 Iub require additional 2 ips for IUB common.
 So 4 Interfaces *2 (CP +UP) * 2 ( Ips ) – 2 Ips shared + 2Ip for
Iub common = 16

 OMCB Ip is for OMCB link to be established through OMP board

 Interface IP
 Group 1 and group 2 are Ethernet aggregation

 Service IP :
 Assign IP used for UP service to different Interfaces as follow :
Bit0=1:Iub , Bit1=1: Iur , Bit2=1: IuCS , Bit3=1: IuPS , Bit4=1:Iub Common
Interface (for CCIU), Bit5=1:Preconfiguration IuB
Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Iub Preconfiguration Iub Common IuPS IuCS Iur Iub
 Example : 100 means IuCS only

 From previous IP interface table ( ppt 25) we have :
IP1 IP2
Iub UP 192.168.165.230 192.168.165.231
Iur UP 192.168.187.110 192.168.187.111
IuCS UP 192.168.187.108 192.168.187.109
IuPS UP 192.168.187.112 192.168.187.113
IuB common UP 192.168.165.226 192.168.165.227

 Service IP

 CCIU Service Config
 Service Iub Common IP used for CCIU slave

 UCIU Ip combination type :

 Interface type combination : Bit0=1:Iub , Bit1=1: Iur , Bit2=1: IuCS , Bit3=1:
IuPS , Bit4=1:Iub Common Interface (for CCIU), Bit5=1:Preconfiguration IuB
 Iub UP + IUR UP + IUCS UP + IUPS UP all combined.

 Slave or Dsp service config
 Slave boards use same Service IP

 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.

 Channel Port: used for Ethernet aggregation, Channel group ID

1 is used to group the following IPs :

 Member port
 Slot 23 port 1 and slot 25 port 2 are aggregated to Channel

group ID 1
Contents

32
Transmission network configuration
 RNC protocol Stack
Node B Iu-PS
domain
Iub Radio Iu-PS

Transmission signaling
Radio
signaling OMCB RANAP data
Radio channel
signaling ALCAP control SCCP IUUP
Radio
NBAP STC-SSCF data BOOTP MTP3B M3UA GTPU
SSCF-UNI SSCF-UNI FP UDP OMCB SSCF-NNI UDP
SCTP SCTP
SSCOP SSCOP UDP IP IP(OMM) SSCOP IP
AAL2
AAL5 IP AAL5 IP AAL5 IP AAL5 IP AAL5
Data Link
ATM Data Link ATM ATM Data Link ATM Data Link ATM Data Link ATM
PHY PHY PHY PHY PHY PHY PHY
RNC
Radio Iur Radio Iu-CS

signaling signaling
Transmission Transmission
RNSAP signaling RANAP signaling
Radio
SCCP ALCAP SCCP ALCAP data
Radio
MTP3B M3UA MTP3B data MTP3B M3UA MTP3B IUUP
SSCF-NNI SSCF-NNI FP SSCF-NNI SSCF-NNI RTP/RTCP
SCTP SCTP
SSCOP SSCOP UDP SSCOP SSCOP AAL2 UDP
AAL2
AAL5 IP AAL5 IP AAL5 IP AAL5 IP
ATM Data Link ATM ATM Data Link ATM Data Link ATM ATM Data Link
PHY PHY PHY PHY PHY PHY
RNC Iu-CS
domain
 The Transmission netwrok configuration will be divided into 3

parts :
 Iub Integration
 Iu integration
 Iur integration
 The 3 interfaces integration flow require the creation of “Local

office “namely the RNC1 which is common to all.
 The local office, IP path group and static route are common
sheets for all interfaces

 Local office
 OPC : 16172
 NRI CS : 0
 NRI PS : 5
Contents
 IUB Integration
 IU integration
 IUR integration

36
Iub integration
 The Iub integration flow is :

 IP path Group : UP
 Iub office : UP and CP
 SCTP ( IUB ) : CP
 IUB bearer : UP
 Static Route : UP and CP

Iub Integration
 IP Path group :
 Path Group ID 2011 is created for Node B WZ001 with 100Mbps

bandwidth

Iub integration
 IUB office
 WZ001 defined as NE ID 20001 is created

Iub integration
 SCTP ( IUB) : CP connection between RNC and NodeB
 SCTP association ID : 2001

 Local IP address : IUB _ CP : 192.168.165.228
 Remote IP address : NODEB IP : 192.168.165.244
 Local port / remote port : 2905 / 2906
Iub integration
 IP Bearer ( IUB) : UP link between RNC1 and NodeB
 IP path Group ID 2011 is used to connect the RNC1 to NodeB

WZ001 with 100Mbps bandwidth
 Node B IP is 192.168.165.244 same as used in SCTP
Iub 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 Configure this parameter according to on-site planning.
By default, BFD is disabled.
Contents

 IUB Integration
 IU integration
 IUR integration

43
IU integration
 IuCS and IuPS integration flow is same. The sheets used will be as
follow :

IU integration
1. Adjacent Office(CN)
2. Static Route
3. SCTP Config(CN)
4. M3uaAS Config(CN)
5. M3uaRoute
6. M3uaRouteSet
7. IP Path Group
8. IP Path(CN)

IU 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 Configure this parameter according to on-site planning.
By default, BFD is disabled.
IU Integration
 IP PATH Group
 Path group ID 2002 and 2001 and created for GGSN2 and GGSN3
with 1Gbps bandwidth respectivly
 Path group ID 2003 is created for MSC1 with 100Mbps
bandwidth

IU integration
 Adjacent office CN .............1
 SGSN2 : NE ID 2 with DPC 16357

 SGSN3 : NE ID 3 with DRC 16355
 MGW+MSC : NE ID 4096 and NE ID 4 respectively with DPC
16258
IU integration
 Adjacent office ( CN) ..........2
 SGSN2 is default SGSN and NRI PS is 2

 SGSN3 is secondary SGSN and NRI PS is 3
 MSC+MGW NRI CS is 0
IU integration
 SCTP Config ( CN)
 Two associations for each SGSN, 4 for the MSC

IU integration
NE SCTPAdjacend
Config ( Associatio
CN ) Local Local IP Remote Remote IP ASP
office ID n ID port port number
192.168.187.106;1 10.10.10.24;10.1
SGSN3 3 2906 2906 92.168.187.107 2905 0.10.27 9
192.168.187.106;1 10.10.10.25;10.1
SGSN3 3 2907 2907 92.168.187.107 2905 0.10.26 10
192.168.187.106;1 10.10.10.5;10.10
SGSN2 2 2908 2906 92.168.187.107 2905 .10.8 11
192.168.187.106;1 10.10.10.6;10.10
SGSN2 2 2909 2907 92.168.187.107 2905 .10.7 12
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2910 2905 92.168.187.105 2921 192.168.173.65 14
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2911 2906 92.168.187.105 2922 192.168.173.65 15
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2912 2907 92.168.187.105 2923 192.168.173.65 16
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2913 2908 92.168.187.105 2924 192.168.173.65 17

IU integration
 M3uaAS Config
 AS number 2,3,4 created for SGSN2, SGSN3 and MSC+MGW

IU integration
 M3ua Route
 Route number 2,3 and 4 created for AS numbers 2, 3 and 4

respectively

IU integration
 M3ua RouteSet

IU integration
 IP Path ( CN)
 The IP path bearers for IUCS and IUPS

Contents

 IUB Integration
 IU integration
 IUR integration

56
IUR integration
 IUR configuration flow

1. Adjacent Office(CN)
2. Static Route
3. SCTP Config(CN)
4. M3uaAS Config(CN)
5. M3uaRoute
6. M3uaRouteSet
7. IP Path Group
8. IP Path(CN)

IUR integration
 IP PATH group
 Path group ID 501 for IUR IP UP bearer with 100Mbps bandwidth

IUR integration
 Adjacent office ( CN ) : RNC2 is defined as NEID 501 and DPC
16173

IUR integration
 SCTP Config ( CN)
 SCTP association ID 501 is between RNC1 and RNC2.

 Local IP : 192.168.187.104 / 192.168.187.105
 Remote IP ( RNC2) : 192.168.165.216 / 192.168.165.217
 Local port / remote port : 1111 / 2222
 ASP number 13 created
IUR integration
 M3uaAs Config
 AS number 501 created for ASP number 13

IUR integration
 M3ua Route
 M3ua RouteSet

IUR integration
 IP PATH ( CN)
 IP Path bearer for UP between RNC1 and RNC2 with 1Gbps

bandwidth and RNC2 IP : 192.168.165.222

Contents

64
Radio network configuration
 Template : UMTS Radio Quick Configuration Template.xls

 for the commissioning part only two sheets need to be created
as the Iub link will be created automatically.
 For additional configurations, such as
Adjacent cells, neighbour cell
Relationship ...it can be
Created though SON or
Optimization templates
 UTRAN cells and Logical
Cells should be created
By template
 UUtranCellFDD
 Node B No 20001 from NEID : 20001 is created with 6 cells

 Band 0 is used : 2100Mhz
 DUARFCN : 3 frequency channels : 2112.6 Mhz, 2117.6 MHz, 2122.6 MHz
 LAC : 23700 , RAC : 1
 UUtranCellFDD : remianing parameters could be left empty (

default ) at first .
 Two sectors with 3 cells each so the WZ001 is a S3/3

 Radio network summary
User Cell ID PSC DUARFCN Frequency

label
Sector 1 F1
WZ001U1 10101 101 10563
F2
WZ001W1 10121 121 10613
F3
WZ001V1 10111 111 10588
Sector 2 F1
WZ001V2 10112 112 10588
F2
WZ001U2 10102 102 10563
F3
WZ001W2 10122 122 10613

 ULogicalCell

Contents

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

Configuration Data Import - Steps 2 and 3
 Create Managed Element

Configuration Data Import
 Fill in proper parameters such as :
 User Label : RNC1

 Managed Element type : UMTS
 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.

Contents

79
Data Modification After Template Import
 Choose Enable for Whether IUB/IUR/IUCS has IP license

(default value: Disable).

 Configuration of PTP clock source for IP 1588 clock on the Iub

interface:
 Click Modify Area for the ME to be modified.
 Choose PTP Interface

Configuration as shown in the
right figure:

 In PTP Interface Configuration-Table Mode, click the New button.
 In the pop-up PTP Interface Configuration window, click the Edit button.

 Modify the parameters according to the samples marked in red boxes in the
following figure:

 Modify the parameters according to the samples marked in red box in the
following figure:

Thank you

06 ZXUR 9000 UMTS Configuration 85P

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

06 ZXUR 9000 UMTS Configuration 85P

Загружено:

Авторское право:

Доступные форматы

ZXUR 9000 UMTS

 Introduction of Data Configuration File

 UMTS Radio Quick Configuration

© ZTE All rights reserved 3

 RNC data configuration templates are released in the OMMR

 Path of UMTS Radio Quick Configuration Template

© ZTE All rights reserved 4

© ZTE All rights reserved 5

© ZTE All rights reserved 6

© ZTE All rights reserved 7

 From previous sheet we can generate the following template

© ZTE All rights reserved 8

 Index sheet of UMTS 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

 RNC1 of ME ID 500 belongs to MCC 222 and MNC 88

© ZTE All rights reserved 17

 The RNC1 is configured with only one Rack of ETCA V2 . Only

© ZTE All rights reserved 18

© ZTE All rights reserved 19

© ZTE All rights reserved 20

 This sheet indicates the default IP fragment reassembly board. If no

© ZTE All rights reserved 22

 OMCB Ip is for OMCB link to be established through OMP board

 Group 1 and group 2 are Ethernet aggregation

 Example : 100 means IuCS only

© ZTE All rights reserved 25

© ZTE All rights reserved 26

 CCIU Service Config

 Service Iub Common IP used for CCIU slave

© ZTE All rights reserved 27

 UCIU Ip combination type :

 Iub UP + IUR UP + IUCS UP + IUPS UP all combined.

© ZTE All rights reserved 28

 Slave or Dsp service config

 Slave boards use same Service IP

© ZTE All rights reserved 29

 Channel Port: used for Ethernet aggregation, Channel group ID

© ZTE All rights reserved 30

 Slot 23 port 1 and slot 25 port 2 are aggregated to Channel

 Introduction of Data Configuration File

Iub Radio Iu-PS

Radio Iur Radio Iu-CS

 The Transmission netwrok configuration will be divided into 3

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

© ZTE All rights reserved 34

 Radio network configuration

 The Iub integration flow is :

© ZTE All rights reserved 37

 Path Group ID 2011 is created for Node B WZ001 with 100Mbps

© ZTE All rights reserved 38

 WZ001 defined as NE ID 20001 is created

© ZTE All rights reserved 39

 SCTP association ID : 2001

 IP Bearer ( IUB) : UP link between RNC1 and NodeB

 IP path Group ID 2011 is used to connect the RNC1 to NodeB

Parameter Name Parameter Description