Cisco Cisco ASR 5000 Technical Manual
Service−req: This defines the SR message that is received by the SGSN.
♦
Actions: This defines the actions to be taken when the SGSN receives the previously mentioned
messages during the active calls when the congestion control threshold has been reached.
messages during the active calls when the congestion control threshold has been reached.
Drop: This instructs the SGSN to drop the defined message when the congestion control
threshold has been reached.
threshold has been reached.
♦
Reject: This instructs the SGSN to reject the defined message when the congestion control
threshold has been reached.
threshold has been reached.
♦
Note: Drop and reject actions can further be refined for LAPI. The low−priority−ind−ue keyword is
used with a drop/reject action.
used with a drop/reject action.
•
low−priority−ind−ue: This instructs the SGSN to reject/drop the defined message, only if a message
from the UE includes a LAPI, when the congestion control threshold has been reached.
from the UE includes a LAPI, when the congestion control threshold has been reached.
•
New Call Policy
This specifies the drop or rejection of any new call messages when congestion occurs. The drop or reject
actions for new calls (attach request or new inter−SGSN RAU) can be refined to LAPI or APN−based, or
both. Here is the CLI syntax:
actions for new calls (attach request or new inter−SGSN RAU) can be refined to LAPI or APN−based, or
both. Here is the CLI syntax:
new−call−policy { drop | reject } [ apn−based ] [ low−priority−ind−ue ]
Here are some notes about this syntax:
Message Type/call Event: When a new call policy is defined, it is taken for all of the attach requests
or Inter−SGSN RAUs. For this reason, no message/call event type is required in this CLI command.
or Inter−SGSN RAUs. For this reason, no message/call event type is required in this CLI command.
•
Actions: This defines the actions to be completed when the SGSN receives the previously mentioned
messages during the active calls when the congestion control threshold has been reached.
messages during the active calls when the congestion control threshold has been reached.
Drop: This instructs the SGSN to drop the new call messages when the congestion control
threshold has been reached.
threshold has been reached.
♦
Reject: This instructs the SGSN to reject the new call messages when the congestion control
threshold has been reached.
threshold has been reached.
♦
Note: The drop and reject actions can further be refined for LAPI and APN−based. The
low−priority−ind−ue and apn−based keywords are used with the drop/reject actions.
low−priority−ind−ue and apn−based keywords are used with the drop/reject actions.
•
low−priority−ind−ue: This instructs the SGSN to reject/drop the defined message, only if a message
from the UE includes a LAPI, when the congestion control threshold has been reached.
from the UE includes a LAPI, when the congestion control threshold has been reached.
•
apn−based: This instructs the SGSN to reject/drop the new call messages based on the APN if the
congestion control threshold has been reached. This only occurs if an APN is configured under the
operator policy with congestion control.
congestion control threshold has been reached. This only occurs if an APN is configured under the
operator policy with congestion control.
Note: If the congestion action profile is configured with both the LAPI and APN−based options, then
new call events will be rejected only if both conditions are matched.
new call events will be rejected only if both conditions are matched.
•
SM Messages
This defines the policy for the SM messages, such as active or modification requests. The response from the
SGSN can only be reject, and this can be refined to LAPI or APN−based, or both. Here is the CLI syntax:
SGSN can only be reject, and this can be refined to LAPI or APN−based, or both. Here is the CLI syntax:
sm−messages reject [ apn−based] [ low−priority−ind−ue ]