Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

Gen21222324252627282931323334353637384‑5x
FsNEsRPsSBIsIDs Ti+
Top   in Index   Prev   Next

TS 32.421 (SA5)
Subscriber and Equipment Trace –
Trace Concepts and Requirements

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.2.0 (PDF)2019/09  48 p.
V14.1.02019/09  49 p.
V13.1.02019/09  48 p.
V12.2.02019/09  46 p.
V11.8.02019/09  40 p.
V10.6.0  2013/06  34 p.
V9.2.0  2013/07  33 p.
V8.7.0  2013/07  33 p.
V7.3.0  2013/07  29 p.
V6.7.0  2005/06  24 p.

Rapporteur:  Mr. Toche, Christian

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)).

full Table of Contents for  TS 32.421  Word version:   15.2.0

 

Here   Top

 

 

1  ScopeWord-p. 7
2  ReferencesWord-p. 8
3  Definitions, symbols and abbreviationsWord-p. 9
4  Trace concepts and high-level architectureWord-p. 12
5  Trace requirementsWord-p. 17
6  Requirements for managing MDT [R10]Word-p. 30
7  Requirements for managing RLF and RCEF reports [R11]Word-p. 34
A  Trace use casesWord-p. 35
A.1  Use case #1: multi-vendor UE validation
A.2  Use case #2: subscriber complaint
A.3  Use case #3: malfunctioning UEWord-p. 37
A.4  Use case #4: checking radio coverageUp
A.5  Use case #5: testing a new featureWord-p. 38
A.6  Use case #6: fine-tuning and optimisation of algorithms/procedures
A.7  Use case #7: Automated testing of Service Provider services [R12]
A.8  Use case #8: Regression testing following a network fix [R12]
A.9  Use case #9: Service fault localization within a Service Provider network [R12]
A.10  Use case #10: Service fault localization when a service is hosted by a third party Service Provider [R12]
A.11  Use case #11 Analysing drop calls in E-UTRAN [R11]Word-p. 41
A.12  Use case #12 Periodical sampling of network performance [R11]Up
A.13  Use case #13 Differentiation of area based MDT data by terminal type [R11]Word-p. 42
A.14  Use case #14 Subscriber complaint about MBMS service in the eUTRAN network [R13]
A.15  Use case #15 Check MBMS service quality and performance of the eUTRAN Network [R13]
B  Change historyWord-p. 44

Up   Top