Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 16
▀ SGSN Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
506
CSCub16578 - SNAPTR Queries for GGSN selection
Feature Changes
S-NAPTR Query Support for GGSN Selection
Previous Behavior: S-NAPTR queries were only supported by the S4-SGSN for P-GW selection.
New Behavior: With this release, the SGSN supports S-NAPTR queries for GGSN selection for both EPC and non-
EPC capable UE. Changes were made to the
EPC capable UE. Changes were made to the
apn-resolve-dns-query
command to support this new functionality -
refer to the Command Line Interface Reference and see Command Changes indicated below.
By supporting S-NAPTR queries, it is possible for the Gn/Gp-SGSN to perform Topological Gateway Selection
provided with feature enhancement CSCzn60387. Refer to CSCzn60387 for the command needed to configure the
SGSN’s canonical name for the Gn/Gp-SGSN.
provided with feature enhancement CSCzn60387. Refer to CSCzn60387 for the command needed to configure the
SGSN’s canonical name for the Gn/Gp-SGSN.
Command Changes
apn-resolve-dns-query
epc-ue
and
non-epc-ue
are new keywords for APN configuration with the
apn-resolve-dns-query snaptr
command. This command now enables the operator to configure whether to use GGSN S-NAPTR queries applicable for
both EPC-capable UEs and non-EPC-capable UEs.
both EPC-capable UEs and non-EPC-capable UEs.
configure
apn-profile profile_name
apn-resolve-dns-query snaptr [ epc-ue non-epc-ue ]
remove apn-resolve-dns-query snaptr
end
Notes:
If neither of the new keywords are included, then S-NAPTR query is applicable to all UE, both EPC-capable UE
and non-EPC capable UE.
epc-ue
- S-NAPTR queries applicable for EPC-capable UE.
non-epc-ue
- S-NAPTR queries applicable for non-EPC-capable UE.
CSCub34940 - Bypass APN remap functionality
Feature Changes
Bypassing APN Remap for Specific IMEI Ranges
Previous Behavior: If a local default APN configured in an IMEI profile could not be used, then any default APN
configured under an operator policy was used.
configured under an operator policy was used.