Vous êtes sur la page 1sur 3

Internal Use Only

Control Plane Architecture at UR11.1 Version

1. Overview
ZTE RNC contains RCB board, which is divided into RCP and RSP used to process control plane
protocol at U9.3 version. RCP is mainly used to handle the radio protocol including CELL-related
and UE-related procedure. RSP is mainly used to handle signaling transport protocol including
SCTP and M3UA. Every Cell and UE belongs to a RCP and the relation is configured before RCP
startup and cant be changed during running.
The above architecture has an advantage of high system reliability. However, there is a shortage.
The traffic in the telecommunication network could be different respect to time and area. If the
NodeB and cell is affiliated to a given RCP, sometime traffic in these NodeBs and cells could
exceed the maximum capacity of the RCP, and the other boards in the same RNC might not be
fully utilized.
To improve RCB board utilization efficiency, ZTE RNC introduces Control Plane Resource
Sharing at UR11.1 version. Instead of RCP and RSP, RCB board is divided into DMP and CMP.
DMP mainly handle UE-related radio procedure and all DMPs serve as a pool. CMP mainly
handle NodeB/CELL-related procedure and signaling transport procedure. This architecture can
avoid local congestion in some boards due to disproportionate traffic distribution in network
Control Plane Resource Sharing Technology has a huge advantage that it can improve RNC
Capacity. At U9.3 Version RNC with 34 RCB boards has 7000K BHCA, if upgrade to UR11.1
Version, the capacity of RNC with 34 RCB boards will increase approximate 30% to 9000K
BHCA.

2. Logic Board Function


2.1. Protocol Stack Overview
Refer to Figure 1, DMP handle dedicated procedure of RANAP/RNSAP/NBAP and RRC. CMP
handle common procedure of RANAP/RNSAP/NBAP and transport protocol including SCCP,
M3UA, SCTP, MTP3B and ALCAP.

<>
All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only

Figure 1 protocol distribution

2.2. DMP function


DMP only handle UE-related radio procedure such as RRC/RANAP/RNSAP/NBAP dedicated
procedure and dedicated radio resource algorithm. There is no resource configuration belong to
DMP. So, when a DMP is added and physical board is configured, this DMP will serve UE
immediately, no extra configuration is needed.

2.3. CMP function


Compared to DMP, CMP has complex structure and function.
First, CMP serve NodeB and CELL. NBAP Common procedure and Cell radio resource algorithm
are implemented at CMP. Every NodeB and Cell is also affiliated to a given CMP as preconfiguration.
Secondly, CMP handle connectionless signalling of RANAP and RNSAP(e.g. paging).
Third, signaling transport protocol such as SCCP/M3UA/SCTP/MTP3B/ and transport control
plane protocol such as ALCAP is resident at CMP, meantime CMP also manage the transport
bandwidth resource.

3. Basic DBS Configuration Rule


We list some basic config rule as following.

When a NodeB is added, a CMP module must be specified to serve it. The management
module of NodeB cannot be changed during running.

Uplink Scrambling Code is managed by CMP. A SC range needs to be configured for every
CMP and the range value must be different.

SCTP link is also managed by CMP. If a SCTP link is used to transport IUB message of a
NodeB, then the module of the SCTP Link must be same to the host module of the NodeB.
2
<>
All Rights reserved, No Spreading abroad without Permission of ZTE

Internal Use Only


For SCTP link used to IU/IUR, the module can be an arbitrary CMP. It is recommended that
the number of SCTP link used to IU/IUR is equal among CMPs if there is more than one
SCTP link used to IU/IUR.

For transport resource management, PathGroup and TrPath is mainly resource object. They
also need a configured CMP module. TrPath belong to a PathGroup and the module of TrPath
must be same to the module of its parent PathGroup. If a TrPath is used to manage IUB
resource of a NodeB, then the module of the TrPath must be same to the module of the
NodeB. It is recommended that the number of PathGroup used to IU/IUR is equal among
CMPs if there is more than one PathGroup used to IU/IUR.

Finally, consider the system high reliability and function characterization, we strongly suggest that
the CMP logical board type is split into two sub-type at OMC level: CMP(Iub) and CMP(NotIub).
CMP(Iub) is used to IUB-related config. CMP(NotIub) is used to IU/IUR-related config.

<>
All Rights reserved, No Spreading abroad without Permission of ZTE

Vous aimerez peut-être aussi