Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 32.422SA5
Subscriber and Equipment Trace –
Trace Control and Configuration Management

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/06  185 p.
V14.0.0  2017/03  153 p.
V13.0.0  2015/06  153 p.
V12.4.0  2014/12  142 p.
V11.12.0  2015/06  125 p.
V10.13.0  2014/06  112 p.
V9.6.0  2013/06  72 p.
V8.9.0  2013/06  71 p.
V7.3.0  2013/06  49 p.
V6.5.0  2005/12  46 p.

Rapporteur:  Mr. Toche, Christian

This TS describes the mechanisms used for the control and configuration of the Trace functionality at the EMs, NEs and UEs. It covers the triggering events for starting/stopping of subscriber/UE activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of Trace results in the Network Elements (NEs) and User Equipment (UE) and the transfer of these results to one or more EM(s) and/or Network Manager(s) (NM(s)).
The mechanisms for Trace activation/deactivation are detailed in clause 4; clause 5 details the various Trace control and configuration parameters and the triggering events that can be set in a network. Trace concepts and requirements are covered in TS 32.421 while Trace data definition and management is covered in TS 32.423.

full Table of Contents for  TS 32.422  Word version:   15.2.0

 

Here   Top

 

 

1  ScopeWord-p. 12
2  References
3  Definitions and abbreviationsWord-p. 14
4  Trace/UE measurements activation and deactivationWord-p. 15
4.1  Trace Session activation / deactivation for Trace and MDT
4.1.1  Management activation
4.1.2  Signalling activationUp
4.1.2.1  General
4.1.2.2  Intra PLMN signalling activationWord-p. 31
4.1.2.3  Inter PLMN Signalling ActivationWord-p. 32
4.1.2.4  UTRAN activation mechanismsWord-p. 34
4.1.2.5  PS Domain activation mechanisms
4.1.2.6  CS Domain activation mechanismsWord-p. 38
4.1.2.7Void
4.1.2.8  Tracing roaming subscribersWord-p. 39
4.1.2.9  Service Level Tracing for IMS activation mechanisms [R12]
4.1.2.10  EPC activation mechanism [R8]Word-p. 47
4.1.2.11  E-UTRAN activation mechanisms [R8]Word-p. 55
4.1.2.12  EPC and E-UTRAN Activation mechanism for MDT [R10]Word-p. 56
4.1.2.13  PS domain activation mechanism for MDT [R10]Word-p. 64
4.1.2.14  CS domain activation mechanism for MDT [R10]Word-p. 69
4.1.2.15  5GC activation mechanism [R15]
4.1.2.16  NG-RAN activation mechanisms [R15]Word-p. 90
4.1.3  Management deactivationWord-p. 92
4.1.4  Signalling deactivationWord-p. 95
4.1.5  MDT Trace selection conditions [R10]Word-p. 106
4.2  Trace Recording Session Start / Stop triggering for Trace and MDTWord-p. 107
4.2.1  GeneralUp
4.2.2  Starting a trace recording session - management based
4.2.3  Starting a trace recording session - signalling basedWord-p. 113
4.2.4  Stopping a trace recording session - management basedWord-p. 127
4.2.5  Stopping a trace recording session - signalling basedWord-p. 131
4.2.6Void
4.2.7Void
4.2.8Void
4.2.9Void
4.3  RLF reporting [R11]Word-p. 139
4.4  Handling of MDT Trace sessions at handover for Immediate MDT [R10]
4.5  Handling of MDT Trace sessions at handover for Logged MDT and Logged MBSFN MDT [R10]Word-p. 144
4.6  User consent handling in MDT [R10]Up
4.7  Anonymization of MDT data for area based MDT [R10]Word-p. 147
4.8  RCEF reporting [R11]
5  Trace/UE measurement control and configuration parametersWord-p. 150
6  MDT Reporting [R10]Word-p. 175
7  Trace reporting [R12]Word-p. 178
8  RLF Reporting [R12]Word-p. 180
9  RCEF Reporting [R12]
A (Normative)  Trace failure notification file format [R8]Word-p. 181
B  Examples for alternative ways to route the Trace file to the TCE [R12]Word-p. 183
C  Change historyWord-p. 185

Up   Top