Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 17
▀ SGSN Enhancements for 17.4
▄ Release Change Reference, StarOS Release 17
478
Digit 1 or 2 not in the set {0, 1 ... 9}
Digit 3 not in the set {0, 1 ... 9, F} hex
In such cases the MS should transmit the stored values using full hexadecimal encoding. When receiving such an MNC,
the network should treat the RAI as deleted. The same handling is applicable for a network where a 3-digit MNC is sent
by the mobile station to a network using only a 2-digit MNC.
the network should treat the RAI as deleted. The same handling is applicable for a network where a 3-digit MNC is sent
by the mobile station to a network using only a 2-digit MNC.
A validation check has been introduced to verify the MCC and MNC fields received in the old RAI IE in Attach/RAU
requests. When the MCC and MNC fields received in the RAU request (inter-SGSN) and are invalid, the RAU request
is rejected by SGSN. When the MCC and MNC fields received in the Attach Request and are invalid, the identity of the
MS is retrieved directly from the MS instead of sending identity request to the peer node where peer SGSN identity is
derived from the old-RAI.
requests. When the MCC and MNC fields received in the RAU request (inter-SGSN) and are invalid, the RAU request
is rejected by SGSN. When the MCC and MNC fields received in the Attach Request and are invalid, the identity of the
MS is retrieved directly from the MS instead of sending identity request to the peer node where peer SGSN identity is
derived from the old-RAI.
Important:
This feature is applicable for both 2G and 3G networks.
A new CLI command
[no] rai-skip-validation
has been introduced under both IuPS service and GPRS service
configuration modes. This new command enables/disables rejection of RAU requests with invalid MCC/MNC values in
the old RAI field. By default the old RAI MCC/MNC fields are validated. This command also impacts the PTMSI
attaches where the old RAI field is invalid. If the OLD RAI field is invalid and if the validation is enabled through the
new CLI command, the identity of the MS is requested directly from the MS instead of the peer SGSN.
the old RAI field. By default the old RAI MCC/MNC fields are validated. This command also impacts the PTMSI
attaches where the old RAI field is invalid. If the OLD RAI field is invalid and if the validation is enabled through the
new CLI command, the identity of the MS is requested directly from the MS instead of the peer SGSN.
Previous Behavior: Validation check is absent for the MCC/MNC fields in old RAI received from MS in RAU request
or Attach request.
or Attach request.
New Behavior: A validation check has been introduced to verify the MCC and MNC fields received in the old RAI IE
in Attach/RAU requests. A new CLI command
in Attach/RAU requests. A new CLI command
[no] rai-skip-validation
has been introduced under the IuPS
service and GPRS service configuration modes. If invalid MCC/MNC values are received from MS in old RAI field in a
RAU request, the request is rejected by the SGSN. If invalid MCC/MNC values are received from MS in old RAI field
in a Attach request, the identity of the MS is retrieved directly from the MS instead of sending identity request to the
peer Node where the MS identity is derived from the valid old-RAI. By default the old RAI MCC/MNC fields are
validated.
RAU request, the request is rejected by the SGSN. If invalid MCC/MNC values are received from MS in old RAI field
in a Attach request, the identity of the MS is retrieved directly from the MS instead of sending identity request to the
peer Node where the MS identity is derived from the valid old-RAI. By default the old RAI MCC/MNC fields are
validated.
Command Changes
rai-skip-validation
This new command is introduced under both IuPS and GPRS service configuration modes. Validation check is done as
per 3GPP TS 24.008 for MCC/MNC fields of old RAI IE in Attach/RAU requests. RAU requests with invalid
MCC/MNC values in the old RAI field are rejected. For Attach requests with invalid MCC/MNC values in the old RAI
field, identity of the MS is retrieved directly from the MS instead of sending identity request to the peer Node where the
MS identity is derived from the valid old-RAI.
per 3GPP TS 24.008 for MCC/MNC fields of old RAI IE in Attach/RAU requests. RAU requests with invalid
MCC/MNC values in the old RAI field are rejected. For Attach requests with invalid MCC/MNC values in the old RAI
field, identity of the MS is retrieved directly from the MS instead of sending identity request to the peer Node where the
MS identity is derived from the valid old-RAI.
configure
context context_name
iups-service service_name
[no] rai-skip-validation
end
configure