Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
SGSN Changes in Release 15.0
▀ SGSN Enhancements for March 31, 2014
▄ Cisco ASR 5x00 Release Change Reference
490
New Behavior: Now, when XID for random IOV-UI negotiation failure occurs during intra-RAU or standalone
authentication for SMS, the SGSN moves the subscriber to STANDBY and marks the XID negotiation as a failure.
authentication for SMS, the SGSN moves the subscriber to STANDBY and marks the XID negotiation as a failure.
In some situations of XID negotiation failure, the SGSN will respond as outlined in CSCun13033.
CSCun13033 - Detach request is not triggered in following scenario
Feature Changes
Changes to handling of failures of XID negotiation for radome IOV-UI are also incorporated into related issues
CSCum56967 and CSCun09183.
CSCum56967 and CSCun09183.
Responses to XID Negotiation Failure
Previous Behavior: SGSN clears the subscriber based on the configured negotiation failure action if the previous XID
negotiation for random IOV-UI fails upon receiving any uplink packets whether ciphered or unciphered.
negotiation for random IOV-UI fails upon receiving any uplink packets whether ciphered or unciphered.
New Behavior: The SGSN manner of handling failure of XID negotiation for random IOV-UI has been modified, so
that now the SGSN:
that now the SGSN:
Initiates XID for new random IOV-UI negotiation:
1. with the MS is in STANDBY state, any uplink packet (in either ciphered or unciphered mode, except
Attach / Intra-RAU) from the MS which results in CELL-UPDATE, READY TIMER START and
RADIO STATUS READY causes an event indication to the application.
RADIO STATUS READY causes an event indication to the application.
Initiates Detach:
1. with the MS is in STANDBY state, any uplink activity causes the SGSN to initiate a new XID
exchange, which if it fails or aborts due to the reception of SUSPEND, RADIO-STATUS and
READY-TIMER expiry, results in the SGSN initiating Detach.
READY-TIMER expiry, results in the SGSN initiating Detach.
2. when PAGING is ongoing , any Page response from the MS results in the SGSN initiating Detach.
3. during OLD_SGSN ISRAU, when any uplink data comes before T3 tunnel timer expiry then the SGSN
3. during OLD_SGSN ISRAU, when any uplink data comes before T3 tunnel timer expiry then the SGSN
initiates Detach.
Handles Messages:
1. Attach and intra-RAU (from both local and non-local TLLI or from both the same and different RA)
will be processed in any state.
Moves to STANDBY state:
1. MS is moved to STAND-BY state if the XID exchange failed due to any of the following cases
suspend, radio status, BVC block, BVC reset, ready timer expiry, no response received for XID
exchange during INTRA-RAU/Standalone Authentication for SMS.
exchange during INTRA-RAU/Standalone Authentication for SMS.
2. XID is ongoing in READY state and if the MS moves to either 3G or to the peer-SGSN then the
subscriber is moved to STANDBY state.
Also, all the uplink packets received from the MS (like ACTIVATE, ACTIVATE SECONDARY PDP, DE-
ACTIVATE, MODIFY, SMS) will be dropped and the XID message will be retried whenever the XID is ongoing in
READY STATE. Whenever the SGSN initiates the XID in READY state, it informs the GTP to stop forwarding the
data if any is received for that MS. Upon the reception of XID response in READY state, GTP will be informed to start
forwarding the data queued, if there is any.
ACTIVATE, MODIFY, SMS) will be dropped and the XID message will be retried whenever the XID is ongoing in
READY STATE. Whenever the SGSN initiates the XID in READY state, it informs the GTP to stop forwarding the
data if any is received for that MS. Upon the reception of XID response in READY state, GTP will be informed to start
forwarding the data queued, if there is any.