Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
P-GW Changes in Release 15.0
P-GW Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
403
MME/S4-SGSN shall be locally configured to know that P-GW in the same PLMN supports the S-GW restoration
feature. When this feature is enabled at P-GW, it shall support it for all S-GWs/MMEs.
feature. When this feature is enabled at P-GW, it shall support it for all S-GWs/MMEs.
Unauthenticated IMSI for SM
Code changes added to send Unauthenticated IMSI flag along with emergency session type in Create request to ACS.
Modified P-GW Features
This section identifies P-GW features modified in release 15.0.
3GPP Tracing to Increase Number of Simultaneous Traces from 30 to 1000
Increases the number of simultaneous session traces that can be enabled.
Previous Behavior:3GPP trace limit was 30 sessions.
New Behavior: 3GPP tracing has been enhanced to increase the number of simultaneous traces from 30 to 1000. The
generated trace files are forwarded to external trace collection entity at regular intervals through (S)FTP if “push” mode
is enabled. If the push mode is not used, the files are stored on the local hard drive and must be pulled off by the TCE
using FTP or SFTP.
generated trace files are forwarded to external trace collection entity at regular intervals through (S)FTP if “push” mode
is enabled. If the push mode is not used, the files are stored on the local hard drive and must be pulled off by the TCE
using FTP or SFTP.
Important:
The number of session trace files generated would be limited by the total available hard disk
capacity.
3GPP Tracing to Intercept Random Subscriber
Previous Behavior: Previously, a subscriber identifier like IMSI was required in order to enable trace. Sometimes
operators want to enable a trace without knowing the subscriber ID. For example, an operator may want to monitor the
next “n” number of calls, or monitor subscribers in a particular IMSI range. The InTracer tool allows these use cases.
operators want to enable a trace without knowing the subscriber ID. For example, an operator may want to monitor the
next “n” number of calls, or monitor subscribers in a particular IMSI range. The InTracer tool allows these use cases.
New Behavior: 3GPP tracing has been enhanced to intercept random subscribers with this feature. The current session
trace feature is either signaling or management based, which is very specific to a particular subscriber. The requirement
is to trace random subscribers which are not explicitly linked or identified by IMSI in GTP messages or configured
through CLI.
trace feature is either signaling or management based, which is very specific to a particular subscriber. The requirement
is to trace random subscribers which are not explicitly linked or identified by IMSI in GTP messages or configured
through CLI.
The random subscribers could be in an IMSI range, context activation in particular time intervals, etc.
The session trace is activated on demand for a limited period of time for specific analysis purposes. The maximum limit
would restrict the number of random subscriber tracing. Random session trace will be given priority over signalling and
management-based session trace.
would restrict the number of random subscriber tracing. Random session trace will be given priority over signalling and
management-based session trace.
3GPP TS 29.281 (GTP-U) Release 10 Compliance
Previous Behavior: P-GW was not fully compliant to 3GPP TS 29.281 Release 10 to support UDP Port Extension
header in Error indication message and Supported Extension Headers Notification message.
header in 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.
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.