4 Trace overview

12.083GPPSubscriber and equipment traceTS

Figure 1 gives an outline of the subscriber and equipment tracing and shows the relationship between the inputs on activation and deactivation and the trace record outputs.

Figure 1: Subscriber and Equipment Trace for 12.08

Trace Activation and Deactivation are described in clause 5.

The Trace Types are defined in clause 6.

The Trace Records are defined in clause 7.

The following events may invoke a MSC or BSS trace:

‑ Call set‑up within MSC (MOC, MTC) (incl. attempts);

‑ SS‑Action;

‑ Location Update (Normal and Periodic);

‑ SMS‑MO;

‑ SMS‑MT;

‑ IMSI attach and detach.

Additionally, the following event may invoke a BSS trace:

‑ Handover.

An HLR Trace may be invoked by one of the following:

‑ Location updates/cancellations;

‑ Insert/delete subscriber data;

‑ Routing enquiry (speech and SM);

‑ Provide roaming number;

‑ SS activity;

‑ SMS: Alert service centre/Ready for SM.

Trace records are generated within the managed elements by the trace control function according to the trace type. Once a trace has been invoked and a trace record is being compiled, subsequent invoking events relating to that IMSI (parallel events) will not cause new records to be compiled simultaneously but will be contained in the same trace record as the first event.

For operator defined trace types the events on which trace records are generated and their contents are defined within the trace record generation control.

These records are then transferred to the OSF (as defined by OMC‑Id of the Destination OMC or forwarded by the EFD) either as notifications (CMISE), or with bulk transfer (FTAM).