Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 17
SGSN Enhancements for 17.7 ▀
Release Change Reference, StarOS Release 17 ▄
469
Previous Behavior: As a part of this functionality, the target access restriction feature instructs the source-SGSN or the
source-MME to reject outbound RAU when the target access was restricted for the subscriber. Rejection was performed
without checking "access-restriction-data no-check" in the call control profile configuration.
source-MME to reject outbound RAU when the target access was restricted for the subscriber. Rejection was performed
without checking "access-restriction-data no-check" in the call control profile configuration.
New Behavior: With release 17.6.1, a new command keyword
target-access-restriction
has been introduced
to the call control profile configuration to control (enable/disable) target access restriction functionality. Target access
restriction is now disabled by default on both the SGSN and the MME. Refer to the Command Changes section below
for the command information to enable/disable this functionality.
restriction is now disabled by default on both the SGSN and the MME. Refer to the Command Changes section below
for the command information to enable/disable this functionality.
The default behaviors for the SGSN and the MME now differ:
New Behavior for the MME only:“target-access-restriction” keyword configuration will control the target
access restriction feature for the MME without other consideration:
No Rejection: if “target-access-restriction” is not enabled, then the source-MME will not reject the
outbound RAU Request based on the ARD profile of the subscriber per the Access-Restriction-Data
received in ULA/ULR using the RAT Type IE received in the Context Request.
received in ULA/ULR using the RAT Type IE received in the Context Request.
Rejection: if “target-access-restriction” is enabled, then the source-MME will reject the outbound RAU
Request based on the ARD profile of the subscriber per the Access-Restriction-Data received in
ULA/ULR using the RAT Type IE received in the Context Request.
ULA/ULR using the RAT Type IE received in the Context Request.
New Behavior for the SGSN only:The SGSN also considers "access-restriction-data no-check" in the call
control profile configuration prior to rejecting outbound RAU when target access restriction functionality is
enabled. The SGSN’s target access restriction behavior is dependent upon the SGSN’s “access-restriction-data
no-check” configuration:
enabled. The SGSN’s target access restriction behavior is dependent upon the SGSN’s “access-restriction-data
no-check” configuration:
No Rejection: if “target-access-restriction” is enabled, and if “access-restriction-data no-check” is
enabled, then the source-SGSN will not reject the outbound RAU Request based on the ARD profile
of the subscriber per the Access-Restriction-Data received in ULA/ULR using the RAT Type IE
received in the Context Request.
of the subscriber per the Access-Restriction-Data received in ULA/ULR using the RAT Type IE
received in the Context Request.
Rejection: if “target-access-restriction” is enabled, and if “access-restriction-data no-check” is not
enabled, then the source-SGSN will ignore the “target-access-restriction enabled” configuration and
the source-SGSN will reject the outbound RAU Request based on the ARD profile of the subscriber
per the Access-Restriction-Data received in ULA/ULR using the RAT Type IE received in the
Context Request.
the source-SGSN will reject the outbound RAU Request based on the ARD profile of the subscriber
per the Access-Restriction-Data received in ULA/ULR using the RAT Type IE received in the
Context Request.
Command Changes for the MME
access-restriction-data
With release 17.6.1, the MME has access to this command in the call-control-profile configuration mode. The new
keyword
keyword
target-access-restriction
enables or disables rejection of the outbound RAU Request based on the
ARD profile of the subscriber per the Access-Restriction-Data received in ULA/ULR using the RAT Type IE received
in the Context Request.
in the Context Request.
configure
call-control-profile ccprof_name
access-restriction-data target-access-restriction
remove access-restriction-data [ target-access-restriction ]
end