Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
GGSN Changes in Release 15.0
▀ GGSN Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
212
The session trace is activated on demand for a limited period of time for specific analysis purposes. The maximum limit
will restrict on the number of random subscriber tracing. Random session trace will be given priority over signaling and
management based session trace.
will restrict on the number of random subscriber tracing. Random session trace will be given priority over signaling and
management based session trace.
Earlier in order to enable trace subscribers, the identifier like IMSI was mandatory. But there are scenario where
Operators want to enable the trace without knowing the subscriber id. Cases like Operator wanting to monitor the next
‘n’ number of calls, or monitor subscribers in a particular IMSI range are some use cases now which are possible with
this enhancement. This cab be provisioned by tools like Cisco InTracer.
Operators want to enable the trace without knowing the subscriber id. Cases like Operator wanting to monitor the next
‘n’ number of calls, or monitor subscribers in a particular IMSI range are some use cases now which are possible with
this enhancement. This cab be provisioned by tools like Cisco InTracer.
The valid combinations of Session Trace types per service (Network element) are:
Signaling only
Management only
Random only
Management and Signaling
Management and Random
Refer to the GGSN Command Changes section for the new CLI.
3GPP TS 29.281 (GTPU) Release 10 Compliance
Previous Behavior: GGSN 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.
in Error indication message and Supported Extension Headers Notification message.
New Behavior: This feature enhances the GTPU capabilities of GGSN and PGW 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.
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.
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 GTPU entity, node will not send the
Extension Header to the peer entity.
If a message which contains Extension Header is received from peer GTPU entity; if 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 GTPU 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.
With the support for Supported Extension Headers Notification message it helps notifying the GTPU peer about the
GTPU 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.
GTPU 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.
ACL Limit Behavior Change
A 16 ACL limit for redirect-css is now removed and a generic limit for ACL is applied.
DNS Support for IPv4/IPv6 PDP Contexts