WMFD-190900_A&Iu Interface Flow Control

Page 1 of 10

WMFD-190900_A&Iu Interface Flow Control

Contents
3.5.2.2.65 WMFD-190900_A&Iu Interface Flow Control

3.5.2.2.65 WMFD-190900_A&Iu Interface Flow Control

Definition

Benefits

Requirements

Impact on the System

Interaction with Other Features

Application Scenario

Implementation Principle

Charging

Feature Specifications

Application Limitations

Standard Compliance

Release History

Definition
The A/Iu interface is the access point of mobile services. Generally, in a mobile softswitch network, the MSC
server connects to the BSC/RNC over the A/Iu interface through the MGW and communicates with the MGW
using IP. If the IP bandwidth becomes insufficient due to transmission interruption, router interface fault, or rapid
traffic increase, congestion occurs over the signaling links. Failure to reduce the traffic over the A/Iu interface can
lead to a sharp drop in service success rate. The A&Iu Interface Flow Control feature is therefore developed to
control the traffic over the A/Iu interface in the case of signaling congestion, so as ensure the service success rate.
The MSOFTX3000 supports hierarchical flow control based on the monitoring at the SCTP layer and the service
layer. Therefore, the MSOFTX3000 is capable of stabilizing the service access rate when the bandwidth of
signaling links is insufficient. The flow control on the SCTP layer can ease the signaling congestion of the SCTP
links between the MSC server and neighboring network nodes. The flow control on the service layer can ease the
signaling congestion of the end-to-end links between the MSC server and the BSC/RNC. The related data can be
configured to determine whether to enable the Forward Explicit Congestion Notification (FECN) or Multilevel Sleek
Control (MLSC). When both mechanisms are enabled, flow control starts first on the SCTP layer.
The flow control mechanisms are as follows:
1. In an IP network, congestion occurs when the bandwidth becomes insufficient due to transmission
interruption, faults over the router interface, or a rapid increase in traffic. Failure to reduce the traffic over the
A&Iu interface can lead to a sharp drop in service success rate. The A&Iu interface is the access point of

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 2 of 10

mobile services. In a mobile softswitch network, the MSC server generally connects to the BSC/RNC through
the MGW. In addition, the MSC server communicates with the MGW through IP. Therefore, effective flow
control must be applied in case of congestion over the A&Iu interface.
2. The MSOFTX3000 supports hierarchical flow control based on the monitoring at the SCTP layer and the
service layer. Therefore, the MSOFTX3000 is capable of stabilizing the service access rate when the
bandwidth of signaling links is insufficient. The flow control on the SCTP layer can ease the signaling
congestion of the SCTP links between the MSC server and neighboring network nodes. The flow control on
the service layer can ease the signaling congestion of the end-to-end links between the MSC server and the
BSC/RNC. The related data can be configured to determine whether to enable the Forward Explicit
Congestion Notification (FECN) or Multilevel Sleek Control (MLSC). When both mechanisms are enabled,
flow control starts first on the SCTP layer.
3. When the CPU of the WCCU/WCSU with the smallest module number is overloaded, the MSC server sends
an extended OVERLOAD message containing the information about the traffic that the MSC can process at
the next second.
4. When the CPU of the BSC is overloaded, the BSC sends an extended OVERLOAD message to the MSC
server. This message indicates the traffic that the BSC can process at the next second. Based on the traffic
indicated by the OVERLOAD message, the MSC server activates flow control on downlink messages.

Benefits
For...

Benefits

Carriers

Subscribers

The A&Iu interface flow control feature enables the system to effectively control
the service traffic when signaling congestion occurs on the A&Iu interface. It helps
to ensure normal implementation of most services and reduce the impact of
signaling congestion on the system.

The A&Iu interface flow control feature prevents service interruptions caused by
signaling congestion, and thus improves the customer satisfaction and increases
the earnings of carriers.

None.

Requirements
Involved NEs
Table 1 lists the NEs involved in implementing the A&Iu interface flow control feature.
Table 1 NEs involved in implementing the A&Iu interface flow control feature
NE

Supporting Versions

Function Description

MSC server

V100R007C01 and later

Implements flow control over the A&IU interface.

Hardware Compatibility
This feature is compatible with all hardware versions.

Impact on the System

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 3 of 10

This feature has no adverse impact on the system.

Interaction with Other Features

None.

Application Scenario
This feature is applicable to the GSM and UMTS R99/R4 networks. When the service success rate decreases
because of signaling congestion, the A&Iu interface flow control feature can be used to reduce the impact of
signaling congestion on the system.

Implementation Principle
The A&Iu interface flow control feature is implemented based on the negative feedback mechanism. The signaling
load is monitored on both the SCTP layer and the service layer. On the SCTP layer, the signaling load is
monitored based on the retransmission ratio of SCTP packets. On the service layer, the signaling load is
monitored based on the delay of transaction interaction. On detecting the signaling overload on the A&Iu
interfaces, the MSOFTX3000 starts flow control and restricts new service requests at an early stage of the service
flow to lower the bandwidth usage. When the fault that causes the signaling congestion is rectified, the
MSOFTX3000 automatically stops the flow control.
When the CPU of the WCCU/WCSU with the smallest module number is overloaded, the MSC server calculates at
the interval of three seconds the remaining traffic processing capabilities of the WCCU/WCSU for the next second.
(The remaining processing capabilities can only be used for processing location updates, mobile originated calls
(MOCs), mobile originated SMS (SMMOs), and handover request (HO) messages.) The MSC server distributes
the remaining processing capabilities evenly to the BSCs that support the extended OVERLOAD message.
When the MSC server receives the extended OVERLOAD message from a BSC, the MSC server activates or
deactivates flow control on the PAGING/HO messages based on the information contained in the extended
OVERLOAD message, that is, the number of PAGING/HO messages that can be processed by the BSC at the
next second. Within the next second, the MSC server sends the number of PAGING/HO messages specified in
the extended OVERLOAD message, and stops sending the subsequent PAGING/HO messages.
Flow Control on the Messages of Ordinary MOCs
When the MSC server receives the service request of a basic call, it determines whether to trigger the FECN flow
control. The FECN flow control is triggered in one of the following scenarios:

The MSC server detects that the WIFM/WBSG at the bottom layer is overloaded.

The UMG8900 is overloaded and informs the MSC server of the overload event. (To trigger the FECN flow
control in this scenario, the MSC server needs to work together with the UMG8900.)

The flow control on the messages of ordinary MOCs is as follows:

If the service request is rejected during the FECN flow control, the MSC server sends a service denial
message to the BSC/RNC.

If the service request is accepted during the FECN flow control, the MSC server determines whether to
connect the call based on whether the MLSC is enabled for the peer BSC/RNC.

If the MSC server determines to perform MLSC flow control on the service request, it rejects the call and
sends a service denial message to the BSC/RNC.

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 4 of 10

NOTE:

FECN flow control is used to prevent overload on the WIFM/WBSG.

MLSC flow control is used to prevent overload or congestion on the A&Iu interface.

Figure 1 shows the FECN/MLSC flow control.

Figure 1 FECN/MLSC flow control

The FECN/MLSC flow control is as follows:

1. The MSC server receives a CM Service Req message from the BSC/RNC at detection point a.
2. The MSC server determines whether to perform FECN flow control on the CM Service Req message.

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 5 of 10

If the MSC server determines that the CM Service Req message is rejected during the FECN flow
control, it sends a CM Service Rej message to the BSC/RNC.

If the MSC server determines that the CM Service Req message is accepted during the FECN flow
control, it determines whether to perform MLSC flow control on the message at detection point b. If the
CM Service Req message is rejected during the MLSC flow control, the MSC server sends a CM
Service Rej message to the BSC/RNC. If the CM Service Req message is accepted during the MLSC
flow control, the MSC server processes the CM service request message according to the ordinary
processing flow at detection point c.

3. The BSC/RNC processes the CM service denial messages at detection points d and e.
Flow Control on the PAGING/HO Messages
When processing PAGING/HO messages, the MSC server checks whether the priority indicator is enabled for the
initial downlink message sent to the corresponding BSC/RNC, that is, different priority levels may be set for the
downlink messages. When the downlink flow control function is enabled, the MSC server processes the messages
according to their priority levels.

If the priority indicator is enabled for the corresponding BSC/RNC, the MSC server sets the priority indicator
to 0 in the PAGING/HO messages, and the message priority of VIP subscribers to 2. In addition, when VIP
subscribers are paged, flow control is deactivated.

If the priority indicator is not enabled for the corresponding BSC/RNC, the MSC server sets the priority
indicator to 2 in the PAGING/HO messages.

Figure 2 shows the flow control on the downlink PAGING/HO messages with the priority indicator.
Figure 2 Flow control on the downlink PAGING/HO messages with the priority indicator

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 6 of 10

The flow control on the downlink PAGING/HO messages with the priority indicator is as follows:
1. On receiving a PAGING/HO message, the MSC server, at detection point a, checks whether the priority
indicator is enabled for the initial downlink message sent to the BSC/RNC. If the function is enabled, the

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 7 of 10

MSC server sets the priority indicator to 0. If the function is disabled, the MSC server sets the priority
indicator to 2.
2. The MSC server checks the value of the priority indicator in the PAGING/HO message. If the value is 0 and
the current overload level has exceeded the critical overload level, the MSC server adds the message to the
flow control matrix and determines whether to start flow control on the downlink messages.
3. If the PAGING/HO message is rejected during the flow control, the MSC server discards the message at
detection point c. If the PAGING/HO message is accepted during the flow control, the MSC server sends the
PAGING/HO message to the BSC/RNC.
4. The BSC/RNC transparently transfers the PAGING/HO message to the MS/UE at detection point d.
NOTE:
The FECN/MLSC flow control is subject to the data configuration of the RAN Office Flow Control table.
The broadband downlink flow control function is controlled by Use the flow control function in the ADD M3LNK
command.
The narrowband downlink flow control function is controlled by Use the flow control function in the ADD N7LNK
command.
Sending an Extended OVERLOAD Message to the BSC Upon CPU Overload of the WCCU/WCSU With the
Smallest Module Number
When the CPU of the WCCU/WCSU with the smallest module number is overloaded, the MSC server sends an
extended OVERLOAD message to the BSC, indicating the remaining traffic processing capabilities of the
WCCU/WCSU for the next second. (The remaining processing capabilities can only be used for processing
location updates, MOCs, SMMOs, and HO messages.)
Figure 3 shows the flow of sending an extended OVERLOAD message to the BSC upon CPU overload of the
WCCU/WCSU with the smallest module number.
Figure 3 Sending an extended OVERLOAD message to the BSC upon CPU overload of the WCCU/WCSU with
the smallest module number

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 8 of 10

The flow of sending an extended OVERLOAD message to the BSC upon CPU overload of the WCCU/WCSU with
the smallest module number is as follows:
When the MSC server determines to send an OVERLOAD message to the BSC upon CPU overload of the
WCCU/WCSU with the smallest module number, the MSC server checks whether the BSC connected to the MSC
server supports the extended OVERLOAD message.

If the BSC supports the extended OVERLOAD message, the MSC server sends an extended OVERLOAD
message to the BSC, indicating the remaining traffic processing capabilities of the WCCU/WCSU for the next
second. (The remaining processing capabilities can only be used for processing location updates, MOCs,
SMMOs, and HO messages.)

If the BSC does not support the extended OVERLOAD message, the MSC server sends an OVERLOAD
message that does not contain the remaining traffic processing capabilities of the WCCU/WCSU.
NOTE:

To implement the extended OVERLOAD function on the MSC server, the BSC must support the extended
OVERLOAD message.
Flow Control on Mobile Originated PAGING/HO Messages on Receiving an Extended OVERLOAD Message
from the BSC
When the MSC server receives the extended OVERLOAD message from a BSC, the MSC server activates or
deactivates flow control on the downlink PAGING/HO messages based on the information contained in the
extended OVERLOAD message, that is, the number of PAGING/HO messages that can be processed by the BSC
at the next second. The MSC server can either activate flow control on downlink PAGING/HO messages over the
A interface.

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 9 of 10

Figure 4 shows the flow control on mobile originated PAGING/HO messages when the MSC server receives an
extended OVERLOAD message from the BSC.
Figure 4 Flow control on mobile originated PAGING/HO messages when the MSC server receives an extended
OVERLOAD message from the BSC

Assume that the counted number of PAGING/HO messages sent by the MSC within a second is A, and the
number of PAGING/HO messages specified in the extended OVERLOAD message sent by the BSC is B. Before
sending a PAGING/HO message, the MSC server checks whether A exceeds B at detection point a.

If A exceeds B, the MSC server does not send the PAGING/HO message.

If A does not exceed B, the MSC server sends the PAGING/HO message to the BSC.
NOTE:

To implement the extended OVERLOAD function on the MSC server, the BSC must support the extended
OVERLOAD message.

Charging
None.

Feature Specifications
None.

Application Limitations
None

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015

WMFD-190900_A&Iu Interface Flow Control

Page 10 of 10

Standard Compliance
Table 2 lists the standards with which the A&Iu interface flow control feature complies.
Table 2 Standards with which the A&Iu interface flow control feature complies
Category

Purpose

Name

Remarks

3GPP

Signalling Transport
Mechanism Specification
for the Base Station
System - Mobile Services
Switching Centre (BSSMSC) Interface

3GPP TS 0806

3GPP

UTRAN Iu interface:
General aspects and
principles

3GPP TS 25.410

Release History
History

Version

Details

Initial release

V100R007C01

Implements flow control over the A&IU interface.

Second release

V100R008C03 and
V200R008C03

The A&Iu interface flow control feature is enhanced by adding

the OVERLOAD message to implement flow control.

Parent topic: WMFD-1XXXXX

http://localhost:7890/printtopics.html?time=Wed Jan 7 22:45:38 UTC+0700 2015

1/7/2015