The Trace Data tab is enabled via the HSS Server Tab Include Trace Data field via the HSS Node Test Case. It will include the Trace-Data AVP in the Subscription-Data-AVP for the S6a/S6d interfaces. Per 3GPP TS 32.422, TS 29.272 and TS 29.002.
Trace Data Tab describes the mechanisms used for the control and configuration of the Trace, Minimization of Drive Test (MDT) and Radio Link Failure (RLF) reporting functionality at the EMs, NEs and UEs. For Trace functionality, it covers the triggering events for starting/stopping of subscriber/UE activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of Trace results in the Network Elements (NEs) and User Equipment (UE) and the transfer of these results to one or more EM(s) and/or Network Manager(s) (NM(s)). For MDT, it also covers logged MDT and immediate MDT mechanisms in both area based and signalling based scenarios.
The HSS Server tab is used to define the information in LTE requests sent from the HSS node to the MME/SGSN.
|
|
|
|
||
MDT Configuration |
Measurements collected for HSS related processing are reported on the HSS Node report tab.
Used to configure the relevant fields that are a part of the Trace-Data AVP which is a section of the Subscription-Data-AVP.
Trace Event List | Triggering eventsThis mandatory parameter defines when to start a Trace Recording Session and which message shall be recorded first, when to stop a Trace Recording Session and which message shall be recorded last respectively. The messages in the start triggering event tables indicate the transaction to be recorded first and the starting time of the Trace Recording Session within a Trace Session for the traced MS/subscriber in the given NE. The messages in the stop triggering event tables indicate the transaction to be recorded last and the stopping time of the Trace Recording Session.
|
Enable to add Operation and Maintenance Centre (OMC) ID.
|
|||
Add the IP address for the Trace Collection Entity. Enter a valid IPV4 or IPV6 address
|
|||
Minimization of Drive Test (MDT). Enable to configure Job trace Type. Job Type:
|
MSC Server |
Start triggering events |
Stop triggering events |
Mobile Originated Call |
Receipt of the CM SERVICE-REQUEST message with service type set to originating call establishment |
Reception of CC-RELEASE COMPLETE or CM-SERVICE ABORT message |
Mobile Terminated Call |
Sending of PAGING REQUEST message |
Reception of CC-RELEASE COMPLETE or CM-SERVICE ABORT message |
Mobile Originated SMS |
Receipt of the CM SERVICE-REQUEST message with service type set to Short Message service |
Transmission of RP-ACK/RP-NACK message |
Mobile Terminated SMS |
Sending of PAGING REQUEST message |
Reception of RP-ACK/RP-NACK message |
IMSI Attach |
Receipt of the MM-LOCATION UPDATING REQUEST message |
Sending of MM-LOCATION-UPDATING ACCEPT or MM-LOCATION-UPDATING-REJECT message |
Location Update |
Receipt of the MM-LOCATION UPDATING REQUEST message |
Sending of MM-LOCATION-UPDATING ACCEPT or MM-LOCATION-UPDATING-REJECT message |
IMSI Detach |
Receipt of the MM-IMSI DETACH INDICATION message |
Reception of MM-IMSI DETACH INDICATION message |
Handover |
Receipt of the BSSMAP-HANDOVER-REQUIRED message in case of GSM or RANAP-RELOCATION-REQUIRED message in case of UMTS |
Reception of BSSMAP-CLEAR COMPLETE message in case of GSM or RANAP-IU RELEASE COMPLETE message in case of UMTS or BSSMAP-HANDOVER FAILURE in case of GSM or RANAP-RELOCATION FAILURE in case of UMTS. |
SGSN |
Start triggering events |
Stop triggering events |
PDP Context |
Reception of SM-ACTIVATE PDP CONTEXT REQUEST or sending SM-REQUEST PDP CONTEXT ACTIVATION or reception of SM- MODIFY PDP CONTEXT REQUEST |
Reception or sending of SM- DEACTIVATE PDP CONTEXT REQUEST or sending SM-ACTIVATE PDP CONTEXT REJECT |
Mobile Originated SMS |
Receipt of RP-DATA message |
Transmission of RP-ACK/RP-NACK message |
Mobile Terminated SMS |
Transmission of RP-DATA message |
Reception of RP-ACK/RP-NACK message |
GPRS Attach |
Reception of MM-ATTACH-REQUEST |
Sending MM-ATTACH-ACCEPT or MM-ATTACH-REJECT |
Routing Area Update |
Reception of MM-ROUTING AREA UPDATE REQUEST |
Sending MM-ROUTING AREA UPDATE ACCEPT or MM-ROUTING AREA UPDATE REJECT |
GPRS Detach |
Reception MM-DETACH REQUEST |
Reception of MM-DETACH ACCEPT |
MBMS Context |
Sending SM-Request MBMS Context Activation or reception of SM-Update MBMS Context Request |
Sending of SM-Deactivate MBMS Context Request or sending of SM-Activate MBMS Context Reject |
GGSN |
Start triggering events |
Stop triggering events |
PDP Context |
Reception of GTP Create PDP context request or reception of GTP Update PDP context request |
Sending of GTP Delete PDP context response |
MBMS Context |
Reception of GTP Create MBMS Context Request or reception of GTP Update MBMS Context Request |
Sending of GTP Delete MBMS Context Response |
MGW |
Start triggering events |
Stop triggering events |
Context |
Reception of H.248-ADD command, or reception of H.248 MODIFY command |
Sending of H.248- SUBTRACT reply |
MME |
Start triggering events |
Stop triggering events |
Service request |
Reception of NAS: Service Request message or S11: Downlink Data Notification Note: The Service Request message shall not start a new Trace Recording Session when received after a Downlink Data Notification for the same service request instance. |
Reception of S11: Modify Bearer Response or sending of NAS: SERVICE REJECT Note: Modify Bearer Response shall stop the Trace Recording Session only if it has been sent as part of the Service Request procedure |
UE initiated PDN connectivity |
Reception of NAS: PDN connectivity Request message |
Reception of NAS PDN Connectivity Complete |
Initial Attach, Tracking area update, Detach |
Initial Attach: Reception of the NAS: ATTACH REQUEST or of S6a Update Location Answer Tracking Area Update: Reception of the NAS: TRACKING AREA UPDATE REQUEST Detach:
Reception of the NAS: DETACH REQUEST or S3 Detach Notification
or S6a Cancel Location Request or sending
of S11 Delete Session Request. Note: Cancel location location shall not trigger new Trace Recording Session if it is sent as part of the tracking area update procedure. Note: The Delete Session Request message shall trigger a new Trace Recording Session only if sent as part of a Detach procedure and only if a Detach Request has not been received for the same instance of the procedure. Note: Update Location Answer shall be a start trigger for a Trace Recording Session only if sent as part of Attach procedure and if containing Trace Data. |
Initial Attach: Reception of the NAS: ATTACH COMPLETE or sending of the NAS: ATTACH REJECT Tracking Area Update: Sending of the NAS: TRACKING AREA UPDATE ACCEPT or sending of NAS: TRACKING AREA UPDATE REJECT Detach: Sending of NAS: DETACH ACCEPT or S3 Detach Acknowledgement message or S6a Cancel Location Answer message or reception S11 Delete Session Response
Note: Cancel Location Answer shall not stop a Trace Recording Session if it is sent as part of the TAU procedure.
Note: The Delete Session Response message shall stop a Trace Recording Session only if sent as part of a Detach procedure and only if a Detach Request has not been received for the same instance of the procedure. |
UE initiated PDN disconnection |
Sending of the S11: Delete Session Request Note: The S11 Delete Session Request message shall trigger a new Trace Recording Session only if it is sent as part of the UE initiated PDN disconnection procedure. |
Reception of NAS Deactivate EPS Bearer Context Accept |
Bearer Activation/Modification/Deactivation |
Bearer Activation: Reception of S11: Create Bearer Request Bearer Modification: Reception of S11: Update Bearer Request Bearer Deactivation: Reception of S11 Delete Bearer Request Note: Create Bearer Request shall not trigger a new trace recording session if it is sent due to Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures |
Bearer Activation: Sending of S11: Create Bearer Response Bearer Modification: Sending of S11: Update Bearer Response Bearer Deactivation: Sending of S11: Delete Bearer Response |
Handover |
Inter-eNB/Intra-MME: Reception of S1AP: Path Switch Request or S1AP Handover Required
Inter-eNB/Inter-MME - Inter RAT (source MME): Reception of S1AP: Handover Required Inter-eNB/Inter-MME – Inter RAT (target MME): Reception of S10/S3: Forward Relocation Request |
Inter-eNB/Intra-MME: Sending of S1AP: Path Switch Request Acknowledge or S1AP: Path Switch Request Failure, or S1AP: Handover Preparation Failure or S1AP: Handover Cancel Acknowledge or receiving Handover Notify Inter eNB - Inter MME / Inter RAT (source MME): Reception of S10/S3 Forward Relocation Complete Notification or sending of S1AP Handover Cancel Acknowledge or S1AP Handover Preparation Failure
Inter eNB - Inter MME /Inter RAT (target MME): Sending of S10/S3 Forward Relocation Complete Notification or of S10/S3 Relocation Cancel Response or of S10/S3 Forward Relocation Response with reject cause value |
PGW |
Start triggering events |
Stop triggering events |
PDN connection creation |
Reception of S5: Create Session Request (GTP) or Proxy Binding Update (PMIP)
Reception of S2b: Create Session Request (GTP) |
Sending of S5: Create Session Response (GTP) or Proxy Binding Update Ack (PMIP)
Sending of S2b: Create Session Response (GTP) |
PDN connection termination |
Reception of the S5: Delete Session Request or Proxy Binding Update
Reception of the S2b: Delete Session Request |
Sending of the S5: Delete Session Response (GTP) or Proxy Binding Update ACK (PMIP)
Sending of the S2b: Delete Session Response (GTP)
|
Bearer Activation/Modification/Deactivation Note: this is applicable only to GTP based S5 interface. |
Bearer Activation: Sending of the S5/S2b: Create Bearer Request Bearer Modification: Reception of the S5: Modify Bearer Request or sending of the S5/S2b: Update Bearer Request Bearer Deletion: Reception of the S5: Delete Bearer Command or sending of S5/S2b: Delete Bearer Request |
Bearer Activation: Reception of the S5/S2b: Create Bearer Response Bearer Modification: Sending of the S5: Modify Bearer Response or reception of the S5/S2b: Update Bearer Response Bearer Deletion: Reception of the S5/S2b: Delete Bearer Response |
SGW |
Start triggering events |
Stop triggering events |
PDN connection creation |
Reception of the S11: Create Session Request |
Sending of the S11: Create Session Response |
PDN connection termination |
Reception of the S11: Delete Session Request |
Sending of the S11: Delete Session Response |
Bearer Activation/Modification/Deactivation |
Bearer Activation: Reception of the S5: Create Bearer Request or S11: Bearer Resource Command Bearer Modification: Reception of the S11: Modify Bearer Request or S5: Update Bearer Request Bearer Deletion: Reception of the S11: Deactivate Bearer Command or S5: Delete Bearer Request |
Bearer Activation: Sending of the S5: Create Bearer Response Bearer Modification: Sending of the S11: Modify Bearer Response or S5: Update Bearer Response Bearer Deletion: Sending of S5: Delete Bearer Response |