Cisco Cisco Packet Data Interworking Function (PDIF)
SGSN Changes in Release 16
▀ SGSN Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
500
The SGSN now supports use of NRI-RAI based address resolution which includes both local lookup as well as DNS
Query for non-local RAIs when selection of the call control profile is based on the old-RAI and the PLMN Id of the
BSC where the subscriber originally attached. This feature was formerly supported only for 3G subscribers and is now
extended to 2G subscribers. The command enables the SGSN to perform address resolution for peer SGSN with an NRI
when an unknown PTMSI (Attach or RAU) comes from an SGSN outside the pool. The SGSN uses NRI-RAI based
address resolution for the non-local RAIs for 2G subscribers in place of RAI based address resolution.
Query for non-local RAIs when selection of the call control profile is based on the old-RAI and the PLMN Id of the
BSC where the subscriber originally attached. This feature was formerly supported only for 3G subscribers and is now
extended to 2G subscribers. The command enables the SGSN to perform address resolution for peer SGSN with an NRI
when an unknown PTMSI (Attach or RAU) comes from an SGSN outside the pool. The SGSN uses NRI-RAI based
address resolution for the non-local RAIs for 2G subscribers in place of RAI based address resolution.
This functionality is applicable in situations for either inter- or intra-PLMN when the SGSN has not chosen a local NRI
value (configured with SGSN Service commands) other than
value (configured with SGSN Service commands) other than
local-pool-rai
or
nb-rai
. This means the RAI
(outside pool but intra-PLMN) NRI length configured here will be applicable even for intra-PLMN with differently
configured NRI lengths (different from the local pool). This functionality is not applicable to call control profiles with
an associated MSIN range as ccprofile selection is not IMSI-based.
configured NRI lengths (different from the local pool). This functionality is not applicable to call control profiles with
an associated MSIN range as ccprofile selection is not IMSI-based.
Previous Behavior: For a 2G new SGSN subscriber, old SGSN RAI based local lookup and RAI based DNS query is
performed. For non-pooling scenarios the address look up based on RAI is correct. However, for pooling scenarios the
NRI/RAI based lookup and DNS query should not be performed.
performed. For non-pooling scenarios the address look up based on RAI is correct. However, for pooling scenarios the
NRI/RAI based lookup and DNS query should not be performed.
New Behavior: For 2G New SGSN subscriber if the command
peer-nri-length
is configured, the local look up for
address will be NRI/RAI based. If the address is not found locally, a NRI/RAI based DNS A- Query or SNAPTR is
performed.
performed.
Command Changes
peer-nri-length
This command enables the SGSN to use NRI-FQDN-based DNS resolution for non-local RAIs when selection of the
call control profile is based on the old-RAI and the PLMN Id of the BSC where the subscriber originally attached. This
command was formerly supported only for 3G subscribers and is now extended to 2G subscribers. The command
enables the SGSN to perform DNS query with an NRI when RAU comes from an SGSN outside the pool. The SGSN
uses NRI-FQDN-based DNS resolution for the non-local RAIs for 2G subscribers in place of RAI-FQDN-based DNS
resolution.
call control profile is based on the old-RAI and the PLMN Id of the BSC where the subscriber originally attached. This
command was formerly supported only for 3G subscribers and is now extended to 2G subscribers. The command
enables the SGSN to perform DNS query with an NRI when RAU comes from an SGSN outside the pool. The SGSN
uses NRI-FQDN-based DNS resolution for the non-local RAIs for 2G subscribers in place of RAI-FQDN-based DNS
resolution.
configure
call-control profile profile_name
peer-nri-length length [rai-fqdn-fallback]
remove peer-nri-length [rai-fqdn-fallback]
end
Notes:
Fall back to RAI based query when NRI based query fails is not supported in the following scenarios:
2G Context Request and Identification Request are not supported.
S4 support of this extension for all applicable scenarios are not supported.