tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 32.421 (SA5)
Telecommunication management –
Subscriber and Equipment Trace – Trace concepts and requirements

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    48 p.
(P) V13.0.0    2015/06    49 p.
(P) V12.1.0    2014/12    45 p.
(P) V11.7.0    2015/06    39 p.
(P) V10.6.0    2013/06    34 p.
(P) V9.2.0    2013/07    33 p.
(P) V8.7.0    2013/07    33 p.
(P) V7.3.0    2013/07    29 p.
(P) V6.7.0    2005/06    24 p.


Rapporteur:  Mr. Toche, Christian
See also:  –


This TS describes the requirements for the management of Trace and the reporting of Trace data (including FDD mode and TDD mode) across UMTS networks as it refers to subscriber tracing (tracing of IMSI or Private ID) and equipment tracing (tracing of IMEI or IMEISV). Trace also includes the ability to trace all active calls in a cell or multiple cells (Cell Traffic Trace).

This TS also includes the description of Service Level Tracing (tracing of a specific service). It defines the administration of Trace Session activation/deactivation by the Element Manager (EM), the network or User Equipment (UE) itself via signalling, the generation of Trace results in the Network Elements (NEs) and UE and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).

This TS is built upon the basic Subscriber and UE Trace concept described in clause 4. The high-level requirements for Trace data, Trace Session activation/deactivation and Trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for Trace (the use cases are described in Annex A). Trace control and configuration management are described in TS 32.422, and Trace data definition and management are described in TS 32.423.

In this 3GPP Release, this TS does not cover any Trace capability limitations within a NE (e.g. maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g. NE aborting a Trace Session due to resource limitations). The objectives of UMTS Trace specifications are:
  • to provide the descriptions for a standard set of Trace data;
  • to produce a common description of the management technique for Trace administration and result reporting;
  • to define a method for Trace results reporting across the management interfaces.


 

Here          Top          None          None          Next
part:    1     2

 

 

1   Scope   PDF-p. 7
2   References   PDF-p. 8
3   Definitions, symbols and abbreviations   PDF-p. 9
4   Trace concepts and high-level architecture   PDF-p. 12
5   Trace requirements   PDF-p. 19
6   Requirements for managing MDT [R10]   PDF-p. 31
7   Requirements for managing RLF reports [R11]   PDF-p. 35

Up          Top          ToC