Call Trace Management

8/3/2019 Call Trace Management

http://slidepdf.com/reader/full/call-trace-management 1/14

GSR4 Feature Workshop

Enhanced Call Trace Management

Roadmap ID 30210 & 30470




Presentation Outline

• Call Trace Overview

• Pre-GSR4 Call Trace Management

• GSR4 Call Trace Management via GUI

• Screens Supplied

– Trace View window

– Call Trace Detailed View window

– Invoked Instances dialogue box

– Abort Trace on Call dialogue box

– Trace Record View window

– Confirmation dialogue box

• Summary




Call Trace Overview

Enable operator to trace the activities of various NEs for events associated with a particularsubscriber or equipment.

MSC NMC

BSS OMC

MMI

Activation/Deactivation R1500

Activation/Deactivation R 1600

Trace Record ASN1 Format

Trace Record GSM 12.08 Format

Activation/Deactivation

GUI

R1600




Pre-GSR4 Call Trace Management

• Prior to GSR4, OMC operators could not create or deletea trace from the OMC GUI.

• The BSS notifies the OMC of a trace activation ordeactivation by the operator at the MSC, or BSS, MMI.

• Trace criteria were not stored at the OMC.




GSR4 Call Trace Management via GUI

• GSR4 provides a GUI for the call trace feature. Using this GUI, theoperator can:

– Create a trace.

– Delete a trace.

– View the trace criteria for the active, deactivated, and completed traces. – View the trace records associated with each trace invoked in the BSS.

– Perform other actions such as terminating a trace on a particular call, orpreventing an active trace from triggering any more invoked instances (that is, permanently deactivate the trace).




Screens Supplied

• Trace View window.

• Call Trace Detailed View window.

• Invoked Instances dialogue box.

• Abort Trace on Call dialogue box.

• Trace Record View window.

• Confirmation dialogue boxes.


http://slidepdf.com/reader/full/call-trace-management 7/14GSR4 Feature Workshop

Trace View Window (1 of 2)

• Contains a scrollable list of all active, deactivated, and completed traces.

• Active traces are shown first, followed by deactivated traces, and finallycompleted traces. Can also be sorted by origin, status, or creation time.

• Trace View window contains the following information for each trace:

– Name

– Trace Origin – Record Destination

– Selector

– Selector Value

– Status - The status of the trace;

– Creation Time

– BSS

– Scope



Trace View Window (2 of 2)

• Operator can select one trace from the Trace View window toperform further functions on that trace. The functions which can beperformed:

– View the trace records of one invoked instance of the selected trace.

– Display the Call Trace Detailed View window to view the details of the

trace criteria for the selected trace.

– Deactivate the selected active trace.

– Delete the selected active, deactivated, or completed trace.

– Display the Abort Trace window to abort a trace on a particular call, forthe selected active trace.

– Display the BSS Detailed View to view call trace related attributes of theBSS which contains the selected trace criteria.



Call Trace Detailed View Window

• Helps the user to specify the criteria for a new trace.

• It can also be used to examine the criteria for an existing trace.

• When creating a trace, operator needs to specify the Trace Selector,Selector Value, Triggering Event, Record Destination, Trace Data Type, etc. Once all the criteria is set up, user can activate the traceby clicking the Activate button.

• The Call Trace Detailed View window contains menu options whichenable the operator to perform functions on a particular trace:

– Deactivate a trace.

– Abort a trace on a call. – View all calls, call in progress, or completed calls for the trace criteria.



Invoked Instances Dialogue Box

• This window is displayed by selecting any of the the followingoptions from the Trace View window: View All Calls, View Calls in Progress, View Completed Calls.

• If the Invoked Instances window has been displayed to view tracerecords for a call, the window displays a list of SCCP numbers of

currently invoked instances followed by a list of the completedinstances of the selected trace criteria. The status of each instanceis displayed along with the date & time that the first trace record wasreceived at the OMC.

• If the Invoked Instances window has been displayed to view trace

records for a completed trace, the window displays a list of SCCPnumbers of all traces which were invoked during the lifetime of theselected trace.



Abort Trace on Call Dialogue Box

• This window is displayed by selecting “Options, Abort Trace on Call”

menu options from the Trace View window.

• Enable operator to select one or more calls in order to abort the

active traces on those calls.

• The window will display a list of the calls currently in progress for theselected trace criteria. The data & time that the first trace record wasreceived at the OMC is displayed. The first call in the list is selected

by default.



Trace Record View Window

• Display the trace records for an invoked instance in chronologicalorder.

• Includes both the header & body of the trace records.

• Contains menu options which enable the operator to performfunctions on a particular invoked instance:

– Terminate an invoked instance.

– Display the Trace Criteria window to view the trace criteria associatedwith an invoked instance.

– Save the contents of the Trace Record View window to an ASCII file.

– Print the trace record.

– Enable the integration of external call trace data processing tools. Whenselected, this option displays a list of available tools.



Confirmation Dialogue Box

• Confirmation dialogue boxes are displayed whendeleting or deactivating an individual trace, as supportedin this feature.



Summary

MSC NMC

BSS OMC

MMI



Trace Record ASN1 Format

Trace Record GSM 12.08 Format

Activation/Deactivation

GUI

R1600

Documents

Call Trace Management