This feature is developed for both SGSN and
MME. In the SGSN, activation restriction of PDP context on the basis
of access type can be configured using the restrict access-type
command under the APN profile configuration mode. This command is
now extended to MME; a new keyword "eps" is introduced
to configure the APN profile to restrict the PDP context activation
from EPS network access. If this CLI is enabled access to APN's associated
with this APN profile are not allowed on MME/SGSN. By default,
any activation on SGSN for this APN is rejected with cause code
'Requested APN not supported in current RAT and PLMN combination66'.
During mobility scenarios the PDPs related to this APN are deactivated
on the SGSN and the PDPs are also deactivated up to the GGSN/PGW.
the MME attach is rejected if the default bearer related APN is
not supported under the APN profile. By default the EMM cause and
the ESM cause in attach reject are 'ESM failure19' and 66
If the first default bearer APN is allowed,
after a successful attach if the subsequent second default bearer
APN is not supported, activation is rejected with cause 'Requested
APN not supported in current RAT and PLMN combination66'.
This is default MME behavior.
During mobility procedures
on MME, if APN is not supported for bundle, bearers will deactivated
all the way up to PGW and as well on MME for that particular bundle.
the APN is not supported for all the bundles received from a peer
node for a Tracking Area Update procedure at a new MME, Tracking
Area Update is rejected with EMM cause 'No Suitable Cells In tracking
If the APN is not supported for all the
bundles received from a peer node for SRNS relocation procedure
at the new MME, SRNS is rejected with GTPV2 cause 'Denied in RAT82' in
Forward relocation response (if the peer node is MME/S4
SGSN). SRNS is rejected with GTPV1 cause 'Relocation failure213'
in Forward relocation response if the peer node is a Gn Gp SGSN.
operator can configure different cause values other than the default
cause values mentioned in the scenarios described above. For SGSN/MME
cause code remapping is done by configuring various options of the
local-cause-code-mapping command under the Call Control Profile
configuration mode (for both SGSN and MME) and MME Service Configuration
mode (for MME only).