Release Note для Cisco Cisco Packet Data Gateway (PDG)
SAEGW Changes in Release 15.0
▀ SAEGW Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
442
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.
UDP Port Extension header helps in handling the Error-Indication message efficiently. If any GTP-U peer supports this
extension header, then sending this extension header in Error-Indication message will help in processing the Error-
Indication message.
extension header, then sending this extension header in Error-Indication message will help in processing the Error-
Indication message.
Support for Supported Extension Headers Notification message helps notify the GTP-U peer about the GT-U
capabilities of the node. This message is sent only in case the node was required to interpret a mandatory extension
header (by setting the comprehension required in extension header), but the node was not yet upgraded to support that
extension header.
capabilities of the node. This message is sent only in case the node was required to interpret a mandatory extension
header (by setting the comprehension required in extension header), but the node was not yet upgraded to support that
extension header.
DSCP Marking - GTP-U on per APN Basis
This feature provides the flexibility to have a different DSCP marking table on per APN basis so that traffic on each of
the APNs can be marked differently, depending on the needs of the APN.
the APNs can be marked differently, depending on the needs of the APN.
The P-GW supports configurable DSCP marking of the outer header of a GTP-U tunnel packet based on a QCI/THP
table for the S5/S8 and Gn/Gp interfaces. This feature allows configuring DSCP marking table on a per APN basis.
table for the S5/S8 and Gn/Gp interfaces. This feature allows configuring DSCP marking table on a per APN basis.
Previously, DSCP marking table was configured on P-GW service level. As part of this requirement, new CLI is added
to associate the qos-qci-mapping table in APN.
to associate the qos-qci-mapping table in APN.
In order to be backward compatible with old configuration, if a DSCP marking table is associated with P-GW service
and not with the APN, then the one in P-GW service will be used. If table is associated in both P-GW service and APN,
then the one on APN will take precedence.
and not with the APN, then the one in P-GW service will be used. If table is associated in both P-GW service and APN,
then the one on APN will take precedence.
Indirect Forward Tunneling - DL and UL Forwarding
Support is provided for LTE to 3G PS Handovers with downlink and uplink indirect data forwarding in this release.
SRVCC PS-to-CS Handover Indication Support in P-GW
This feature helps in notifying the PCRF about the exact reason for PCC rule deactivation on Voice bearer deletion.
This exact cause will help PCRF to then take further action appropriately.
This exact cause will help PCRF to then take further action appropriately.
Previous Behavior:
1. Support of voice bearer flag in BearerFlags IE was not present in Delete Bearer Cmd initiated by MME.
2. Support of new Rule Failure Code PS_TO_CS_HANDOVER in Charging Rule Report was not present.
2. Support of new Rule Failure Code PS_TO_CS_HANDOVER in Charging Rule Report was not present.
New Behavior: This feature ensures complete compliance for SRVCC, including support for PS-to-CS handover
indication when voice bearers are released. The support for SRVCC feature was first added in StarOS Release 12.2.
indication when voice bearers are released. The support for SRVCC feature was first added in StarOS Release 12.2.
SRVCC service for LTE comes into the picture when a single radio User Equipment (UE) accessing IMS-anchored
voice call services switches from the LTE network to the Circuit Switched domain while it is able to transmit or receive
on only one of these access networks at a given time. This removes the need for a UE to have multiple Radio Access
Technology (RAT) capability.
voice call services switches from the LTE network to the Circuit Switched domain while it is able to transmit or receive
on only one of these access networks at a given time. This removes the need for a UE to have multiple Radio Access
Technology (RAT) capability.