Cisco Cisco Packet Data Gateway (PDG)
S-GW Changes in Release 16
S-GW Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
575
UE changes RAT type and performs a Service Request procedure in another RAT type. In this scenario, the MME/S4-
SGSN always includes ULI in the MBR (if location reporting is enabled in P-GW). Since the ULI is received by the S-
GW it will send an MBR to the P-GW even if the location info or RAT type has not changed since it was last known.
SGSN always includes ULI in the MBR (if location reporting is enabled in P-GW). Since the ULI is received by the S-
GW it will send an MBR to the P-GW even if the location info or RAT type has not changed since it was last known.
To remedy this situation, the software has been enhanced so that a new flag is introduced in the MBR. CLII is set to 1
by the MME/S4-sGSN if:
by the MME/S4-sGSN if:
1. ISR is active and
2. Location info has changed.
2. Location info has changed.
The S-GW sends the ULI info in MBR to the P-GW if ISR is active and
1. RAT type is changed or
2. CLII flag is set.
2. CLII flag is set.
CSCui37806 - Suspend Notification/Acknowledge message in SGSN pool
Feature Changes
Support for Suspend Notification/Acknowledge Message in SGSN Pool Scenario
The S-GW has been enhanced to add the IP address, Port number and Hop counter in the Suspend Notification message.
This includes Suspend notification and acknowledge messages in the SGSN pool scenario to the UDP port number and
IP address definition for GTPv2 messages. This enhancement ensures that the SGSN will not have to repeat sending the
Suspend Notification message in a SGSN Pool scenario.
This includes Suspend notification and acknowledge messages in the SGSN pool scenario to the UDP port number and
IP address definition for GTPv2 messages. This enhancement ensures that the SGSN will not have to repeat sending the
Suspend Notification message in a SGSN Pool scenario.
CSCui37810, CSCui47711 - PGW restoration upon PGW failure w/o restart
Feature Changes
Support for New Cause Value in the S-GW
The PGW Restart Notification may also be used to signal that the peer PGW has failed and not restarted. In this case,
the P-GW Restart Notification now contains a new cause value, PGW not responding. While sending the PRN, the S-
GW includes the cause with this new cause value depending on the echo response.
the P-GW Restart Notification now contains a new cause value, PGW not responding. While sending the PRN, the S-
GW includes the cause with this new cause value depending on the echo response.
CSCui47671 - ULI inclusion cond during Service Request procedure when ISR
is active
Feature Changes
Support for Including ULI Inclusion Condition During Service Request when ISR is active.
If ISR is active and the UE initiates a Service Request procedure then the MME/S4-SGSN are not in a position to decide
whether the ULI has changed since it was last known. For example, when the UE changes RAT type and performs a
Service Request procedure in another RAT type. In this scenario, the MME/S4-SGSN always includes ULI in the MBR
(if location reporting is enabled in P-GW). Since the ULI is received by the S-GW it will send an MBR to the P-GW
even if the location info or RAT type has not changed since it was last known.
whether the ULI has changed since it was last known. For example, when the UE changes RAT type and performs a
Service Request procedure in another RAT type. In this scenario, the MME/S4-SGSN always includes ULI in the MBR
(if location reporting is enabled in P-GW). Since the ULI is received by the S-GW it will send an MBR to the P-GW
even if the location info or RAT type has not changed since it was last known.