Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
SAEGW Changes in Release 15.0
SAEGW Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
441
SAEGW Enhancements for September 30, 2013
SAEGW Feature Changes as of September 30, 2013
This section provides information on SAEGW feature changes in release 15.0.
Important:
For more information regarding features in this section, refer to the SAEGW Administration Guide
for this release.
New SAEGW Features
This section identifies new SAEGW features available in release 15.0.
Authorized Qos Policy to be Displayed at SM for P-GW and SAEGW
Code added to display PCRF authorized in
show subscribers pgw-only full all
for P-GW and in
show
subscribers saegw-only full all
for SAEGW.
Node Functionality GTP Echo
This feature helps exchange capabilities of two communicating GTP nodes, and uses the new feature based on whether
it is supported by the other node.
it is supported by the other node.
This feature allows S-GW to exchange its capabilities (MABR, PRN, NTSR) with the peer entities through ECHO
messages. By this, if both the peer nodes support some common features, then they can make use of new messages to
communicate with each other.
messages. By this, if both the peer nodes support some common features, then they can make use of new messages to
communicate with each other.
With new “node features” IE support in ECHO request/response message, each node can send its supported features
(MABR, PRN, NTSR). This way, S-GW can learn the peer node’s supported features. S-GW’s supported features can
be configured by having some configuration at the service level.
(MABR, PRN, NTSR). This way, S-GW can learn the peer node’s supported features. S-GW’s supported features can
be configured by having some configuration at the service level.
If S-GW wants to use new message, such as P-GW Restart Notification, then S-GW should check if the peer node
supports this new feature or not. If the peer does not support it, then S-GW should fall back to old behavior.
supports this new feature or not. If the peer does not support it, then S-GW should fall back to old behavior.
If S-GW receives a new message from the peer node, and if S-GW does not support this new message, then S-GW
should ignore it. If S-GW supports the particular feature, then it should handle the new message as per the specification.
should ignore it. If S-GW supports the particular feature, then it should handle the new message as per the specification.
Modified SAEGW Features
This section identifies SAEGW features modified in release 15.0.
3GPP TS 29.281 (GTP-U) Release 10 Compliance
Previous Behavior: P-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 P-GW in compliance to 3GPP TS 29.281 Rel-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.