Cisco Cisco ASR 5000 Technical Manual

In Releases 17.0 and later, the SGSN also required a congestion control policy similar to that of the MME.

The SGSN can have three congestion control actions, and each action is associated with an action profile.
Here is the CLI syntax:

 sgsn−service action−profile <action_profile_name>

These three policy types can be configured for the MME in Releases 14.0 and later:

Critical: This defines the critical congestion control threshold for the MME service.

• 

Major: This defines the major congestion control threshold for the MME service.

• 

Minor: This defines the minor congestion control threshold for the MME service.

• 

Note: The action−profile parameter defines the action profile that is associated with the policy type (minor,
major, or critical).

The SGSN congestion control policy action profile is configured in sgsn−global configuration mode. It
defines the action to be completed for these types of call/message events when any congestion control
threshold has been reached in the SGSN node:

Active calls

• 

New calls

• 

SM messages

• 

Here is the syntax for the configuration of the SGSN congestion control policy action profile:

congestion−action−profile <action_profile_name>

The sections that follow describe the various policies that can be configured under the SGSN congestion
action profile.

This specifies the drop or reject of any active call messages when congestion occurs during an active call. A
drop or reject of active calls can only be defined as LAPI for the message. Here is the CLI syntax:

Here are some notes about this syntax:

Message Type/call Event: These message types or call events can be defined for an active call policy:

RAU: This defines the Routing Area Update (RAU) message that is received by the SGSN.

♦ 

•