Tech-invite   3GPPspecs   RFCs   Search in Tech-invite
Gen  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Fs  NEs  RPs  SBIs  IDs  Ti+
Top   in Index   Prev   Next

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

3GPP‑Page   ETSI‑search   full‑ToC
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.0  2019/09  49 p.
V13.1.0  2019/09  48 p.
V12.2.0  2019/09  46 p.
V11.8.0  2019/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 Scope  2 References  3 Definitions, symbols and abbreviations  4 Trace concepts and high-level architecture  5 Trace requirements  6 Requirements for managing MDT  7 Requirements for managing RLF and RCEF reports  A Trace use cases  B Change history 

 

1  Scope  Word-p. 7
2  References  Word-p. 8
3  Definitions, symbols and abbreviations  Word-p. 9
3.1  Definitions
3.2  Abbreviations  Word-p. 11
4  Trace concepts and high-level architecture  Word-p. 12
4.1  Trace concepts
4.2  Trace high level Architecture  Word-p. 13
4.3  Service Level Tracing for IMS high level Architecture [R12]  Word-p. 15
5  Trace requirements  Word-p. 17
5.1  General trace requirements  Up
5.2  Requirements for Trace data  Word-p. 18
5.3  Requirements for Trace activation  Word-p. 19
5.3.1  Requirements for Trace Session activation
5.3.2  Requirements for starting a Trace Recording Session  Word-p. 22
5.4  Requirements for Trace deactivation  Word-p. 24
5.4.1  Requirements for Trace Session deactivation
5.4.2  Requirements for stopping a Trace Recording Session
5.5  Requirements for Trace Data reporting  Word-p. 26
5.6  Requirements for Privacy and Security  Word-p. 28
5.7  Requirements for Charging [R12]  Up
5.8  Use cases for Trace [R8]  Word-p. 29
6  Requirements for managing MDT [R10]  Word-p. 30
6.1  Business Level Requirements
6.2  Specification level requirements  Word-p. 31
6.2.1  Logged MDT and Immediate MDT requirements [R13]
6.2.2  Logged MBSFN MDT requirements [R13]  Word-p. 32
7  Requirements for managing RLF and RCEF reports [R11]  Word-p. 34
7.1  Business level requirements
7.2  Specification level requirements
A  Trace use cases  Word-p. 35
A.1  Use case #1: multi-vendor UE validation
A.1.1  Description
A.1.2  Example of required data for this use case
A.2  Use case #2: subscriber complaint
A.2.1  Description
A.2.2  Example of required data for this use case  Word-p. 36
A.3  Use case #3: malfunctioning UE  Word-p. 37
A.3.1  Description
A.3.2  Example of required data for this use case
A.4  Use case #4: checking radio coverage  Up
A.4.1  Description
A.4.2  Example of required data to cover use case #4
A.5  Use case #5: testing a new feature  Word-p. 38
A.5.1  Description
A.5.2  Example of required data to cover use case #5
A.6  Use case #6: fine-tuning and optimisation of algorithms/procedures
A.6.1  Description
A.6.2  Example of required data to cover use case #6  Word-p. 40
A.7  Use case #7: Automated testing of Service Provider services [R12]
A.7.1  Description  Up
A.8  Use case #8: Regression testing following a network fix [R12]
A.8.1  Description
A.9  Use case #9: Service fault localization within a Service Provider network [R12]
A.9.1  Description
A.10  Use case #10: Service fault localization when a service is hosted by a third party Service Provider [R12]
A.10.1  Description
A.11  Use case #11 Analysing drop calls in E-UTRAN [R11]  Word-p. 41
A.11.1  Description
A.11.2  Example of required data to cover use case #11
A.12  Use case #12 Periodical sampling of network performance [R11]  Up
A.12.1  Description
A.12.2  Example of required data to cover use case #12
A.13  Use case #13 Differentiation of area based MDT data by terminal type [R11]  Word-p. 42
A.13.1  Description
A.13.2  Example of required data to cover use case #13
A.14  Use case #14 Subscriber complaint about MBMS service in the eUTRAN network [R13]
A.14.1  Description
A.14.2  Example of required data to cover use case #14
A.15  Use case #15 Check MBMS service quality and performance of the eUTRAN Network [R13]
A.15.1  Description  Up
A.15.2  Example of required data to cover use case #15  Word-p. 43
B  Change history  Word-p. 44

Up   Top