WR - OC2011 - E03 - 1 ZXWR RNC Quick Data Configuration P68

ZXWR RNC Quick Data
Configuration
Contents
 RNC Networking Topology

 RNC Quick Configuration Flow
 Importing and Exporting of Configuration Data
 Configuration Technical Subjects
RNC Networking Topology
Radio Network Layer
Transport Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer
© ZTE Corporation. All rights reserved

Radio Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Radio Network Layer
Transport Network
Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Radio Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Radio Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Radio Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Radio Network Layer
(CP&UP)IP Layer
(CP)SCTP Layer
(CP)M3UA Layer
(UP)GTP-U Layer

Contents

Main Changes in RNC V3.11
 For the data used to build ROMP in a newly-commissioned site,

the IUCS interface, IUPS interface, and IUB interface should be
configured with at least one office, and at least one cell should be
configured with radio data. All data required in the protocol stack
must be configured. Otherwise, ROMP will be restarted repeatedly
and cannot be powered on.
 For a newly-commissioned site, if the IP bearer is used for IUCS,
the MGW office must be configured.
 A manual creation step is added in the quick configuration, i.e., it is
necessary to create “Logical RNC Associated With PLMN
Configuration Information” manually after the radio resource
management is created. Otherwise, the data of the cell cannot be
imported.
 All boards (except RCB/ROMB) must be allocated to OMP (i.e.,

Module 1).
 The SMP module is deleted, and its functions are now fulfilled by
CMP. The value range and planning rules of the CMP module No.
are changed.
 A DMP module, which is used for call processing only, is added.
The RCB board of the DMP module must be configured as
“None,” instead of “master-slave.”
 It is not necessary to assign a Resource Allocation Subsystem to
the CMP module. Instead, it is necessary to assign a Resource
Allocation Subsystem to each NodeB, which can be realized by
quick data configuration. This field has been added in the
NodeB_Ground template.
 The capacity of each RCP is increased, i.e., each RCP can process up
to 50000 pieces of uplink scrambling codes.
 In RNCV3.11 and later versions, user-plane IPs cannot be allocated
by DSP (i.e., the “slave” in logical CPU Resource). Instead, user-
plane IPs can only be allocated by board.
 If NodeB data is configured manually, it is necessary to check
whether QOS profile index is configured. If it is not configured,
please add it manually. Otherwise, services will be affected (QOS
profile index will be created automatically if the data is configured
by loading template, and therefore it is not necessary to add QOS
profile index manually).
 If there is IUR office, it is necessary to create IUR QOS related
configuration manually. Otherwise IUR service failure will occur.
Boards & Slots

RNC Quick Configuration Template
 RNC Ground Resource Template:

 Hardware configuration data of RNC boards
 Global RNC office configuration data, and transmission data
 Configuration data of interface, route, and other ground resources
 Local RNC office configuration data
 Configuration data of the offices on the IUCS/IUPS/IUR interface
 NodeB Office Data Template:

 NodeB office NE data
 NodeB transmission type configuration data
 NodeB path group configuration data

RNC Quick Configuration Template
 RNS Radio Data Template:

 NodeB configuration data
 Data of UTRAN cells
 Data of neighbor cells that are not managed by the local RNC
 Data of UTRAN cells for the serving cell
 Configuration data of GSM cells
 Data of GSM neighbor cells of the serving cell

Template Path
 The configuration templates can be acquired from the directory

of OMMR version or the directory of OMMR client
 ums-clnt\deploy\template\rnc
 RNC Ground Resource Template, NodeB Office Data Template, RNS Radio
Data Template
 ums-clnt\deploy\template\rnc\template_EN
 RNS Radio Data Template

Quick Configuration Templates Filling Flow

Quick Data Configuration Flow

Contents

 Importing and Exporting of Configuration
Data
Importing RNC Ground Resource
1 2

Importing NodeB Office Resource

Importing RNS Radio Resource
1 Check whether the RCP UL
scrambling code configuration is
consistent with the planning data.
In V3.11, the capacity of each RCP
is increased, i.e., each RCP can
process up to 50000 pieces of
uplink scrambling codes.

In V3.11 and later versions, a global switch is added in the
3 Radio Resource Management interface. If the parameter is
set as “0,” Iu-flex is not enabled.
NRI Bit Num.

4 Creating Logical RNC Associated With PLMN Configuration Information


Open the corresponding log.xls file, and check whether all data is
6 loaded successfully.

Exporting Ground Resource Template

Exporting Ground Resource Template
Output Here

Exporting Radio Resource Template

Contents
 Modifying RNC ID
 Adding PLMN
 Subject About Module No.
 Outer IP Segment Reassembling Board Configuration
 Configuring IP Address With SLAVE(DSP) as Unit
 Deleting Global NodeB Offices
 Adding QOS Profile Index to NodeB Office Manually
 Adding QOS Profile Index to IUR Office Manually
Modifying RNC ID
1 Modify local RNC ID and local NE ID. Firstly,
copy the Config Set to the managed element
of the new RNC ID. Then modify the NE ID.
In this example, RNC1 is modified as
RNC4095.
3
2

Modifying RNC ID
4
Set NE type

Modifying RNC ID
5
Modify NE ID

Modifying RNC ID
6
Check NE ID

Contents
 Adding PLMN
Adding PLMN at RNC Office
1
Set NE Type

Adding PLMN at RNC Office
2
Add PLMN

Adding PLMN at CN Office
1
Modify the value of PLMN Number of Sharing the RNC from “1” to “2”
(maximum value: 4)

Adding PLMN at CN Office
2
Each PLMN must have one and only one default CS/PS office.
Therefore, if a PLMN is added, a CS office within the PLMN must be set as the default office.)

Contents
 Adding PLMN
Introduction to CMP/DMP
 Of RNC equipment, there are two boards that need to be

allocated with Module No., i.e., ROMB and RCB. The Module No.
ranges from 1 to 127.
 For RNC V3.11 and later versions, two modules of RCB are
changed a little, i.e., SMP is deleted, and DMP is added, but this is
not a function replacement. Instead, the function of SMP is
integrated to CMP, and DMP processes the calls of UE users
alone. The range of CMP module No. is 3-18. DMP module No. is
from 32 to 127. Both CMP module No. and DMP module No. are
allocated from smaller numbers (e.g., CMP module No. is
allocated from 3 on, and DMP module No. from 32 on).

Introduction to CMP/DMP Value Range of Module
No.
Function Unit Module No.
ROMP 1
RPU 2
CMP 3-18
DMP 32-127
Rules of Configuring Module No.

Function Module
Basic Configuration Rules
Unit No.
ROMP 1 All boards (except ROMB/RCB) must be allocated to ROMP Module 1.
RPU 2 The virtual address should be configured on RPU Module 2.
It is used to process the IU-interface signaling and CN-office path/path
group.
CMP(IU) 3-6
Each module supports 32 IU-interface SCTP links at most. The
association links must be allocated evenly among the modules.
It is used to process cells.
CMP(IUB) 7-18 All objects of the same NodeB must be allocated to the same module
No., and the NodeBs must be allocated evenly among the modules.
Please select the module Nos. when creating boards, and there is
DMP 32-127
nothing else to be configured.

Introduction to CMP/DMP
 DMP/CMP on the same board is prohibited (the two modules on

an RCB must be either CMP or DMP).
 The RCB of CMP must be in master/slave configuration. The RCB
of DMP must be set as “NONE,” and all DMPs should act as a
resource pool by default.

D/C Module No. Planning Solution for Newly-
Commissioned Sites
Total
Number of CMPNotIub CMPIub DMP Site Cell BHCA(K) OL(K)
RCBs
4 1 1 2 250 500 1000 9
6 1 3 2 750 1500 1000 12
8 1 3 4 750 1500 2000 24
10 1 3 6 750 1500 3000 27
12 1 5 6 1250 2500 3000 36
14 1 5 8 1250 2500 4000 45
16 1 7 8 1750 3500 4000 48
18 2 6 10 1500 3000 5000 54
20 2 8 10 2000 4000 5000 60
22 2 8 12 2000 4000 6000 72
24 2 8 14 2000 4000 7000 72
26 2 10 14 2500 5000 7000 84
28 2 10 16 2500 5000 8000 90
30 2 10 18 2500 5000 9000 90
32 2 12 18 3000 6000 9000 108
34 2 12 20 3000 6000 10000 108
37 3 13 21 3250 6500 10500 117

Modifying NodeB Home CMP Module No.
 After the SMP function is integrated to CMP in RNC V3.11 and

later versions, all objects of the same NodeB must be allocated to
the same CMP according to the configuration specification. The
operation falls into two steps.

Modifying NodeB Home Module No.
NodeB_Ground.xls It is only necessary to modify the three fields of

MODIND/ANI/NEID and the NDBALCMOUDULE
field.

Choose Batch modify NodeB Attached Module to perform the

modification.

RNC Configuration > Ground Parameters Configuration > SET
ASSOCIATION(SET SCTP).

Modifying IU-Interface Association Module No.
It is only necessary to modify the two fields of
NodeB_Ground.xls MODIND/ASSOCID and the MOUDULE field.

Contents
 Adding PLMN
Outer IP Segment Reassembling Board
Configuration
 In V3.07.310 and earlier versions, the IP segment packets from the
CN to RNC is usually assigned to the GIPI at slot 11 in shelf. If the
IUPS traffic is too heavy, the GIPI will bear too much load, leading
to GIPI reset.
 In V3.09.30, a different priority segment reassembling board may
be allocated to the RUB board in each resource shelf, so as to
reduce the load of the IP segment ReAssembe Board, and hence
avoid single-board performance bottleneck and optimize the
configuration of external IP segment reassembling. It is necessary
to configure the DSP service IP.
 In RNC V3.11 series, the relation between boards and DSP service
IPs is deleted. The configuration of IP segment ReAssembe Board
can be fulfilled by loading templates.
Configuration

Configuration
 In V3.07.310 and earlier versions, the IP segment packets from the
CN to RNC is usually assigned to the GIPI at slot 11 in shelf. If the
IUPS traffic is too heavy, the GIPI will bear too much load, leading
to GIPI reset.
 In V3.09.30, a different priority segment reassembling board may
be allocated to the RUB board in each resource shelf, so as to
reduce the load of the IP segment ReAssembe Board, and hence
avoid single-board performance bottleneck and optimize the
configuration of external IP segment reassembling. It is necessary
to configure the DSP service IP.
 In RNC V3.11 series, the relation between boards and DSP service
IPs is deleted. The configuration of IP segment ReAssembe Board
can be fulfilled by loading templates.
Contents
 Adding PLMN
Configuring IP Address With SLAVE(DSP) as Unit
 On the existing GUI of OMCR, logical CPU Resource can only be

batch-created or batch-deleted by board.

Configuring IP Address With SLAVE(DSP) as Unit
 Sometimes, there are two special scenarios in the field.

 In the new site using RNCV3.11, the IP resources are limited, and no more IPs can be
acquired to configure IP by board.
 In the old site to be upgraded to RNCV3.11, an RUB board has been allocated with two
or more IP addresses with DSP as the unit. This function needs to be kept in data
maintenance.
 OMCR provides a configuration solution for the two scenarios

mentioned above.
 For example, two user-plane IP addresses are configured on RPU for RUB2, i.e., 1.1.1.1
and 2.2.2.2. After the first IP (1.1.1.1) is allocated to N RUBs, the UDP ports left can only
be used by M (M<15) DSPs of the (N+1)th RUB.
 And there are (15-M) idle DSPs on the (N+1)th RUB. Usually, it is recommended that the
(N+1)th RUB be allocated to the second IP address.
 For the second scenario, we can perform batch-creation twice (batch-create the first IP
first, then batch-create the second IP) on the (N+1)th RUB to solve the problem.

Configuring Logical CPU Resource Manually
1 Right-click the (N+1)th RUB, and choose Batch Create Logical CPU Resource.
2
finish the allocation of the first IP

Configuring Logical CPU Resource Manually
Because the first IP is not enough for all logical CPU resources of the board,
3 the OMCR will prompt the following information.
Right-click the (N+1)th RUB, and choose Batch Create Logical CPU Resource.
4 Click Add, and choose the second IP address.
Then, click OK to allocate IP for the DSPs left.

Contents
 Adding PLMN
Deleting Global NodeB Offices
1
Nodeb_Ground
Template

Contents
 Adding PLMN
Adding QOS Profile Index to NodeB Office
Manually
 It is required that the record of each site should have been
configured in the Qos Configuration Related to Network
Element tab. Otherwise, services cannot be established.

Adding QOS Profile Index to NodeB Office
Manually
Parameter Name Filling Instruction
This parameter is valid only when Transport QOS Profile Type is
set as According to ARP/THP/TC Config.
Basic Priority Transport Bearer In all IP transmission mode, fill in 3.
Type Index
In IP+ATM transmission mode, fill in 2.
In ATM transmission mode, this parameter is invalid, fill in 0.
This parameter is valid only when Transport QOS Profile Type is
Basic Priority Transport
set as According to ARP/THP/TC Config Transport QOS. Fill in “1”
Reserved Bandwidth Index
fixedly
V3.11.10.08 series: Only valid when value of Transport QOS
Profile Type is According to Service Type Config Transport Qos.
In all IP transmission mode, the default value is 1.
In mixed transmission mode, the default value is 3.
Transport Qos Profile In ATM transmission mode, the default value is 4.
parameter Index V3.11.10.11 series: Only valid when value of QosProfileType is
According to Service Type Config Transport Qos.
In all IP transmission mode, the default value is 17.
In mixed transmission mode, the default value is 19.
In ATM transmission mode, the default value is 20.

Contents
 Adding PLMN
Adding QOS Profile Index to IUR Office Manually
 In OMMRV3.09 series versions, the QosIndex parameter of the

office is configured when the office is configured in the Ground
Template. In RNCV3.11, due to the change of RNC database
structure, QosIndex is configured in Radio Resource
Management. After the commissioning engineers configure the
IUR grounding information, they may forget to configure
QosIndex in Radio Resource Management. In consequence, the
service on the IUR interface may fail.

Adding QOS Profile Index to IUR Office Manually

WR - OC2011 - E03 - 1 ZXWR RNC Quick Data Configuration P68

Uploaded by

Copyright:

Available Formats

WR - OC2011 - E03 - 1 ZXWR RNC Quick Data Configuration P68

Uploaded by

Document Information

Original Title

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

WR - OC2011 - E03 - 1 ZXWR RNC Quick Data Configuration P68

Uploaded by

Copyright:

Available Formats

ZXWR RNC Quick Data

 RNC Networking Topology

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

Radio Network Layer

Transport Network Layer

© ZTE Corporation. All rights reserved

 RNC Networking Topology

 For the data used to build ROMP in a newly-commissioned site,

 All boards (except RCB/ROMB) must be allocated to OMP (i.e.,

© ZTE Corporation. All rights reserved

 RNC Ground Resource Template:

 NodeB Office Data Template:

© ZTE Corporation. All rights reserved

 RNS Radio Data Template:

© ZTE Corporation. All rights reserved

 The configuration templates can be acquired from the directory

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 RNC Networking Topology

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

NRI Bit Num.

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

© ZTE Corporation. All rights reserved

 Of RNC equipment, there are two boards that need to be

© ZTE Corporation. All rights reserved

Rules of Configuring Module No.

© ZTE Corporation. All rights reserved