Cisco Cisco Packet Data Interworking Function (PDIF) Notas De La Versión
S-GW Changes in Release 15.0
S-GW Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
555
CR-1057: Essential correction to the TAD IE inclusion in Bearer Resource Command over S4
Previous Behavior: Since TAD IE is mandatory in Bearer Resource Command, EGTPC rejects the
Bearer Resource Command if the TAD IE is missing.
New Behavior: For S4-SGSN, TAD IE marked as conditional over S4 interface. If S4-SGSN receives
this IE from the UE, it shall include it over S4 interface. So at EGTPC, message validation is changed
for the presence of this IE. If S-GW receives this IE, the S-GW will forward it to P-GW over S5/S8
interface.
for the presence of this IE. If S-GW receives this IE, the S-GW will forward it to P-GW over S5/S8
interface.
CR-1095: Correction on the bearer ctxt for mod procedure
Previous Behavior: It was unclear whether or not to include the Bearer context to be modified IE in the
MBR message over the S5/S8 interfaces for a TAU/RAU/HO without S-GW change procedure.
New Behavior: The bearer context to be modified IE is not included in the MBR message over the
S5/S8 interfaces for a TAU/RAU/HO without S-GW change procedure.
CR-1102: Missing Cause Value for MUPSAP
Previous Behavior: There was no specific rejection cause defined for Create Session Request for
additional PDN connectivity request in PMIP bases S5/S8 scenario, even though it was not allowed.
New Behavior: New rejection cause “Multiple PDN connections for a given APN not allowed” is
defined for S-GW in the reply message for Create Session Request for additional PDN connectivity to
the MME/S4-SGSN when PMIP-based S5/S8 is used.
the MME/S4-SGSN when PMIP-based S5/S8 is used.
CR-1105: Downlink bearers release during mobility
Previous Behavior: In the TAU/RAU without S-GW change procedure, the target MME/SGSN sends
the Modify Bearer Request message to the S-GW. No downlink userplane information is included in
this message. As the source SGSN may not remove the SGSN IP address and TEID in the S-GW
when the UE comes to IDLE state, or the UE may be in ECM-CONNECTED state in the source side,
if the S-GW maintains the connection with the source side, userplane data will be sent to the source
network.
this message. As the source SGSN may not remove the SGSN IP address and TEID in the S-GW
when the UE comes to IDLE state, or the UE may be in ECM-CONNECTED state in the source side,
if the S-GW maintains the connection with the source side, userplane data will be sent to the source
network.
New Behavior: Bearer Context To be Modified IE will be included in the above Modify Bearer
Request message with the mandatory EBI IE. If only EBI is included, the S-GW will remove the
downlink userplane information.
downlink userplane information.
3GPP TS 29.281 (GTP-U) Release 10 Compliance
Previous Behavior: S-GW was not fully compliant to 3GPP TS 29.281 Rel-10 to support UDP Port Extension header in
Error indication message and Supported Extension Headers Notification message.
Error indication message and Supported Extension Headers Notification message.
New Behavior: This feature enhances the GTP-U capabilities of S-GW in compliance to 3GPP TS 29.281 Release 10.
Support for UDP Port Extension Header in Error Indication message and Supported Extension Headers Notification
message was added to become fully compliant with 3GPP Release 10.
Support for UDP Port Extension Header in Error Indication message and Supported Extension Headers Notification
message was added to become fully compliant with 3GPP Release 10.
Supported Extension Headers Notification message indicates a list of supported extension headers that the node can
support. This message is sent only in case a GTP entity was required to interpret a mandatory extension header (by
setting the comprehension required in extension header), but the GTP entity was not yet upgraded to support that
extension header.
support. This message is sent only in case a GTP entity was required to interpret a mandatory extension header (by
setting the comprehension required in extension header), but the GTP entity was not yet upgraded to support that
extension header.
If a Supported Extension Headers Notification is received from peer GTP-U entity, node will not send the
extension header to the peer entity.
If a message which contains extension header is received from peer GTP-U entity and the extension header is set
to comprehension required and the extension header cannot be interpreted by the node, it will send a Supported
Extension Headers Notification message. This message shall include all the extension headers supported by the
node.
Extension Headers Notification message. This message shall include all the extension headers supported by the
node.