NodeB Signaling Management (RAN17.1 - 01)
NodeB Signaling Management (RAN17.1 - 01)
Issue 01
Date 2015-03-23
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Contents
7 Parameters.....................................................................................................................................21
8 Counters........................................................................................................................................22
9 Glossary.........................................................................................................................................26
10 Reference Documents...............................................................................................................27
1.1 Scope
This document describes NodeB Signaling Management, including its technical principles,
related features, network impact, and engineering guidelines.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies to macro base stations (BTS3900, BTS3900L, BTS3900A, BTS3900AL,
BTS3900C, and DBS3900) and LampSite base stations.
RAN17.1 01 (2015-03-23)
This issue includes the following changes.
l NBAP_RL_SETUP_REQ
l NBAP_RL_ADD_REQ
l NBAP_RL_RECFG_PREP
l NBAP_RL_RECFG_COMMIT
l NBAP_RL_SETUP_REQ
l NBAP_RL_RECFG_PREP
l NBAP_RL_RECFG_COMMIT
In IP transmission mode, the SCTP unit and the main control signaling unit provide the common
signaling processing capability. In ATM transmission mode, the SAAL unit and the main control
signaling unit provide the common signaling processing capability. In either mode, the baseband
signaling unit provides the baseband signaling processing capability.
Figure 3-1 shows the signaling processing architecture for 3900 series base stations in IP
transmission mode.
Figure 3-1 Signaling processing architecture for 3900 series base stations in IP transmission
mode
Figure 3-2 shows the signaling processing architecture for 3900 series base stations in ATM
transmission mode.
Figure 3-2 Signaling processing architecture for 3900 series base stations in ATM transmission
mode
The SCTP unit is deployed on a board specified by the ADD SCTPLNK command by default,
and it can be deployed on a board with a higher processing capacity. You can query the board
carrying the SCTP unit by running the DSP SCTPLNK command.
The baseband signaling unit can work in distributed deployment mode on all supportive boards.
Table 3-1 describes deployment of signaling units on different boards of different versions.
WMPT All versions SCTP unit (for IP transmission) or SAAL Provides only
unit (for ATM transmission) common signaling
Main control signaling unit processing
capability.
UTRP All versions SCTP unit (for IP transmission) or SAAL Provides only
unit (for ATM transmission) common signaling
processing
capability.
WMPT All versions SCTP unit (for IP transmission) or SAAL Provides only
unit (for ATM transmission) common signaling
Main control signaling unit processing
capability.
UTRP All versions SCTP unit (for IP transmission) or SAAL Provides only
unit (for ATM transmission) common signaling
processing
capability.
NOTE
In RAN14.0 and later versions, replacing the WMPT with the UMPT on a NodeB improves both the
common and baseband signaling processing capabilities of the NodeB.
3.3.1 Principles
IP transmission protocols generally have higher CNBAP specifications than ATM transmission
protocols.
3.3.2 Suggestions
The following are suggestions to consider when configuring signaling units:
l When both the WMPT and UTRP boards are configured, the SCTP link (for IP
transmission) or the SAAL link (for ATM transmission) must be configured on the UTRP
board. Otherwise, the signaling specifications of WMPT and UTRP boards are equivalent
to those of only the WMPT board.
l When both the UMPT and UTRPc boards are configured, the SCTP link (for IP
transmission) or the SAAL link (for ATM transmission) must be configured on the UMPT
or UTRPc board. Otherwise, the NodeB cannot reach the maximum signaling
specifications.
l In ATM/IP dual-stack transmission mode, CS services must be carried over ATM and all
other services and signaling must be carried over IP. Otherwise, the NodeB cannot reach
the maximum signaling specifications.
l The signaling processing capability of the WBBPa board is less than that of the WBBPb
or WBBPd board. It is good practice to replace the WBBPa board with the WBBPb or
WBBPd board if the WBBPa board experiences signaling overload.
NOTE
In IP transmission mode, the transmission signaling link is the SCTP link. In ATM transmission
mode, the transmission signaling link is the SAAL link.
NodeB signaling load is evaluated during busy hours and therefore the evaluation result comes
from busy-hour traffic.
When the soft handover factor is greater than or equal to 0.4, calculate the NodeB signaling load
using the following formula:
Where,
When the soft handover factor is greater than or equal to 0.4, calculate the NodeB signaling load
using the following formula:
Where,
l Define the precaution threshold (Thpre) as 50% and the alarm threshold (Thalarm) as 60%
for congestion at a site:
NOTE
l The alarm threshold for congestion is calculated based on the signaling peak-to-average ratio (PAR)
on live networks. Huawei's empirical PAR value is 1.6 and therefore the alarm threshold value is 1/1.6
(rounded as 60%).
l To calculate the PAR value, select the three types of signaling message NBAP_RL_SETUP_REQ,
NBAP_RL_ADD_REQ, and NBAP_RL_RECFG_PREP from the Iub interface signaling tracing
result, and then measure the actual maximum CNBAP value per second and the ratio of average CNBAP
values in one hour.
5.1 Counters
This chapter lists the counters related to this feature. For details about the counters, see NodeB
Performance Counter Reference.
5.2 Alarms
None
6.1 Background
l Mobile applications on smartphones cause more network signaling load.
l Statistics on live networks show that more than 70% PS signaling traffic may come from
7% smartphones. These smartphones will cause signaling bursts on live networks.
l System congestion, such as FACH congestion and NodeB signaling overload, causes
repeated resource requests from smartphones. The congestion wastes a large number of
signaling packets and causes the signaling processing capability of the NodeB to decrease.
l Advantages
The signaling impact of smartphones on the network is reduced.
l Restrictions and disadvantages
FACH congestion occurs, which consumes radio resources. In addition, the UE
compatibility issue occurs.
NOTE
l The EFD feature must be deployed by professional service personnel from Huawei.
l For details about the EFD feature, see Enhanced Fast Dormancy Feature Parameter Description in
the RAN feature documentation.
Huawei has introduced E2E Flow Control Phase 1 and E2E Flow Control Phase 2. Phase 1 can
be used independently. Phase 2 serves as a supplement to Phase 1 and therefore Huawei
recommends that Phase 2 be used together with Phase 1.
l Without E2E Flow Control, the NodeB will reject the radio link setup requests of all services and
respond to the RNC with the RADIO LINK SETUP FAILURE messages if the CPU usage on the
NodeB reaches 90%, and will discard the RADIO LINK SETUP REQUEST messages of all services
if the CPU usage on the NodeB reaches 95%.
l For details about E2E Flow Control, see E2E Flow Control Feature Parameter Description in the RAN
feature documentation.
l Advantages
The capacity of common channels is expanded. Adding an SCCPCH significantly alleviates
common channel congestion, thereby reducing RRC connection setup failures due to no
reply and CCH call drops. In addition, Iub signaling traffic caused by repeated resource
requests from UEs is also reduced.
l Restrictions and disadvantages
The SCCPCH needs to be added on the whole network because of the UE compatibility
issue. In addition, the new SCCPCH occupies downlink power, which increases downlink
power load. Therefore, operators must check the downlink power load on the whole
network when using this solution.
l Advantages
Implementation is easy.
l Restrictions and disadvantages
– If a UTRP is added, operators must modify transmission configurations and cable
connections.
– Replacing the WMPT with the UMPT interrupts the NodeB services.
– Boards cannot be added to a NodeB if the NodeB has reached the maximum
configuration.
l Applicable scenarios
The NodeB has not reached the maximum configuration.
l Splitting mode
– Split a site by sector.
– Split a site by frequency band. For example, split a site into two sites, one running on
UMTS 850 MHz and the other running on UMTS 1900 MHz.
– Split a site by UTRA absolute radio frequency channel number (UARFCN). This mode
is not recommended because operators must redeploy the antenna system in this splitting
mode.
l Advantages
Implementation is easy and only a small modification workload is required. Operators do
not need to add antennas, sectors, or carriers, and do not need to consider the site location.
l Advantages
This solution is widely used to rectify the issues like congestion and NodeB signaling
overload caused by heavy traffic.
l Restrictions and disadvantages
Implementation takes a long time because operators must consider where to deploy the new
site and perform the network planning and optimization.
l Applicable scenarios
The site experiences any type of congestion and NodeB signaling overload.
7 Parameters
8 Counters
9 Glossary
10 Reference Documents