Cisco Cisco Packet Data Gateway (PDG)
MME Changes in Release 17
▀ MME Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
292
CSCub06751 - NASTAR Cell tracing
Feature Changes
Subscriber Information for LTE Cell Traces
With this feature the MME is capable of sending trace information (IMSI, Trace reference, etc.) for all UEs to the TCE,
in compliance with 3GPP TS 32.413, Release 10. Upon trace activation, the eNodeB sends the allocated Trace
Reference and Trace Recording References in a Cell Traffic Trace message to MME over S1AP, which looks up the
IMSI/IMEI associated with the corresponding S1 session and forwards the two references and UE ID to the Trace
Collection Entity (TCE) indicated in the Cell Traffic Trace message.
in compliance with 3GPP TS 32.413, Release 10. Upon trace activation, the eNodeB sends the allocated Trace
Reference and Trace Recording References in a Cell Traffic Trace message to MME over S1AP, which looks up the
IMSI/IMEI associated with the corresponding S1 session and forwards the two references and UE ID to the Trace
Collection Entity (TCE) indicated in the Cell Traffic Trace message.
This functionality assists the TCE in correlating the Trace Reference and Trace Recording Session Reference generated
by the eNodeB with the IMSI/IMEI corresponding to the traced session, since the eNodeBs only have access to the
temporary UE identities but not to the permanent ones.
by the eNodeB with the IMSI/IMEI corresponding to the traced session, since the eNodeBs only have access to the
temporary UE identities but not to the permanent ones.
With this enhancement, operators have better trace information, improving the management of UEs.
Command Changes
session trace
The TCE Connection parameter and credentials will be configured via the CLI, using the existing session trace
mechanism. To allow the configuration of different sets of TCE Connection parameters for Cell Traffic Tracing reports
and regular Session Tracing, as well as the ability to enable/disable Cell Traffic Tracing independently from regular
Session Tracing, a new Network Element, eNB, has been introduced.
mechanism. To allow the configuration of different sets of TCE Connection parameters for Cell Traffic Tracing reports
and regular Session Tracing, as well as the ability to enable/disable Cell Traffic Tracing independently from regular
Session Tracing, a new Network Element, eNB, has been introduced.
The existing mechanism and CLI syntax will be used to configure, process, store and manage TCE Connection
parameters for the eNB Network Element.
parameters for the eNB Network Element.
configure
session trace network-element { all | enb | mme | pgw | sgw | ggsn } [ collection-timer
sec ] [ tce-mode { none | push transport sftp path string username name { encrypted
password enc_pw | password password } } ]
sec ] [ tce-mode { none | push transport sftp path string username name { encrypted
password enc_pw | password password } } ]
no session trace network-element { all | enb | mme | pgw | sgw | ggsn }
end
Notes:
The TCE IP address provided in the Cell Traffic Trace messages must correspond to the configured TCE
connection. It is the responsibility of the operator to ensure that the TCE transport is properly configured at the
MME and eNodeB.
MME and eNodeB.
Up to 8 TCEs are supported for each MME instance.
Performance Indicator Changes
MME Schema