для Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 17
SGSN Enhancements for 17.4 ▀
Release Change Reference, StarOS Release 17 ▄
477
New statistics have been introduced under “show egtpc statistics verbose” and “show sgtpc statistics verbose” to reflect
the context response sent and received with the new reject cause “Target Access Restricted for the subscriber”.
the context response sent and received with the new reject cause “Target Access Restricted for the subscriber”.
For more information refer to the 3GPP TS 29.274 (section 7.3.6), TS 29.060 (section 7.5.4), TS 29.060 Annex B (Table
B.5: Mapping from Gn/Gp to NAS Cause values – Rejection indication from SGSN) and TS 29.274 Annex C (Table C.5:
Mapping from S3/S16 to NAS Cause values – Rejection indication from MME/S4-SGSN)
B.5: Mapping from Gn/Gp to NAS Cause values – Rejection indication from SGSN) and TS 29.274 Annex C (Table C.5:
Mapping from S3/S16 to NAS Cause values – Rejection indication from MME/S4-SGSN)
Previous Behavior: In earlier releases:
The target node (SGSN/MME) does not send the target RAT type in SGSN Context request to the source node.
The target node (SGSN/MME) rejects RAU/TAU with cause “No suitable cells in Location/Tracking Area” only
after ULA/ULR is received with target RAT restricted for the subscriber in Access-Restriction-Data.
New Behavior: From this release onwards:
The target node (SGSN/MME) sends the target RAT Type in SGSN Context request to source node.
The source node (SGSN/MME) rejects the SGSN Context Request/Context Request with the cause “Target
Access Restricted for the subscriber” if target RAT is restricted for the subscriber as per Access-Restriction-
Data received in ULA/ULR using RAT Type received in SGSN Context request/Context request.
Data received in ULA/ULR using RAT Type received in SGSN Context request/Context request.
The target node (SGSN/MME) sends RAU/TAU reject after Context Response/SGSN Context Response
received with EGTP/GTP cause “Target Access Restricted for the subscriber”.
Customer Impact: Rejecting RAU/TAU much early in call cycle results in reduced signaling.
Performance Indicator Changes
show sgtpc statistics verbose
New statistic is added to this show command to display Target Access Restricted statistics for GTPv1 mobility
management messages.
management messages.
Target Access Restricted
show egtpc statistics verbose
New statistic is added to this show command to display Target Access Restricted statistics for GTPv2 mobility
management messages.
management messages.
Target Access Restricted
CSCus64306 - SGSN cannot reject RAU with MNC/MCC that arrive in HEX
Feature Changes
Validation of MCC/MNC Values in the Old RAI Field
This feature is developed to comply with 3GPP TS 24.008. As per 3GPP TS 24.008, in some abnormal instances the
MCC stored in the Mobile Station (MS) contains elements which do not belong to the set {0, 1 ... 9}. In such cases the
Mobile Station should transmit the stored values using full hexadecimal encoding. When receiving such an MCC, the
network should treat the RAI as deleted. In some instances it is possible that the MNC stored in the Mobile Station has
the following:
MCC stored in the Mobile Station (MS) contains elements which do not belong to the set {0, 1 ... 9}. In such cases the
Mobile Station should transmit the stored values using full hexadecimal encoding. When receiving such an MCC, the
network should treat the RAI as deleted. In some instances it is possible that the MNC stored in the Mobile Station has
the following: