Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 32.422  Word version:  17.4.0

Top   Top   None   None   Next
0…   4…   5…

 

0  IntroductionWord‑p. 12

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below:
TS 32.421 [2]:
"Subscriber and equipment trace: Trace concepts and requirements";
TS 32.422:
"Subscriber and equipment trace: Trace control and configuration management";
TS 32.423 [3]:
"Subscriber and equipment trace: Trace data definition and management";
Additionally, there is a GSM only Subscriber and Equipment Trace specification: TS 52.008.
Subscriber and Equipment Trace provide very detailed information at call level on one or more specific mobile(s). This data is an additional source of information to Performance Measurements and allows going further in monitoring and optimisation operations.
Contrary to Performance Measurements, which are a permanent source of information, Trace is activated on user demand for a limited period of time for specific analysis purposes.
Trace plays a major role in activities such as determination of the root cause of a malfunctioning mobile, advanced troubleshooting, optimisation of resource usage and quality, RF coverage control and capacity improvement, dropped call analysis, Core Network, UTRAN, EPC, 5GC, E-UTRAN and NG-RAN procedure validation.
The capability to log data on any interface at call level for a specific user (e.g. IMSI or SUPI) or mobile type (e.g. IMEI or IMEISV), or service initiated from a UE allows getting information which cannot be deduced from Performance Measurements such as perception of end-user QoS during his call (e.g. requested QoS vs. provided QoS), correlation between protocol messages and RF measurements, or interoperability with specific mobile vendors.
Moreover, Performance Measurements provide values aggregated on an observation period, Subscriber and Equipment Trace give instantaneous values for a specific event (e.g., call, location update, etc.).
If Performance Measurements are mandatory for daily operations, future network planning and primary trouble shooting, Subscriber and Equipment Trace is the easy way to go deeper into investigation and network optimisation.
In order to produce this data, Subscriber and Equipment Trace are carried out in the NEs, which comprise the network. The data can then be transferred to an external system (e.g. an Operations System (OS) in TMN terminology, for further evaluation).
Up

1  ScopeWord‑p. 14

The present document describes the mechanisms used for the control and configuration of the Trace, Minimization of Drive Test (MDT) and Radio Link Failure (RLF) reporting functionality at the management system (at the Element Manager (EM) and or Network Manager (NMs) in UMTS and EPS), Network Elements (NEs) and User Equipment (UEs). For Trace functionality, 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 NEs and UE and the transfer of these results to management system. For MDT, it also covers logged MDT and immediate MDT mechanims in both management based and signalling based scenarios. GSM is excluded from the RAT systems which the present document can be applied to.
The mechanisms for Trace, MDT and RLF reporting activation/deactivation are detailed in clause 4; clause 5 details the various Trace, MDT and RLF reporting control and configuration parameters and the triggering events that can be set in a network. Trace, MDT and RLF reporting concepts and requirements are covered in TS 32.421 while Trace and MDT data definition and management is covered in TS 32.423.
The conditions for supporting Network Sharing are stated in TS 32.421.
Up

2  ReferencesWord‑p. 14

The following documents contain provisions, which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]
TS 32.421: "Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements".
[3]
TS 32.423: "Telecommunication management; Subscriber and equipment trace: Trace data definition and management".
[4]
TR 21.905: "Vocabulary for 3GPP Specifications".
[5]
TS 52.008: "Telecommunication management; GSM subscriber and equipment trace".
[6]
TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".
[7]
TS 23.205: "Bearer-independent circuit-switched core network; Stage 2".
[8]
TS 23.108: "Mobile radio interface layer 3 specification, core network protocols; Stage 2 (structured procedures)".
[9]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[10]
TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW); interface; Stage 3".
[11]
TS 29.002: "Mobile Application Part (MAP) specification".
[12]
TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
[13]
TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".
[14]
TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[15]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[16]
TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
[17]
TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents".
[18]
Enabler Release Definition for OMA Device Management Specifications, version 1.2, The Open Mobile Alliance™ (URL:http://www.openmobilealliance.org/).
[19]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[20]
TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[21]  Void
[22]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[23]  Void
[24]
TS 32.442: "Telecommunication management; Trace management Integration Reference Point (IRP); Information Service (IS)".
[25]
TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[26]
TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
[27]
3GPP TS 32.615: "Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions".
[28]
TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)".
[29]
TS 29.212: " Policy and Charging Control (PCC);Reference points".
[30]
TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);Overall description; Stage 2".
[31]
TS 25.331: "Radio Resource Control (RRC); Protocol specification"
[32]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[33]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[34]
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[35]
3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[36]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol".
[37]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN): Overall description stage 2".
[38]
TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer - Measurements".
[39]  Void
[40]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[41]
TS 23.502: "Procedures for the 5G System; Stage 2"
[42]
TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
[43]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[44]
TS 38.401: "NG-RAN; Architecture Description".
[45]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[46]
TS 28.541: "5G Network Resource Model (NRM); Stage 2 and stage 3".
[47]
TS 28.532: "Management and orchestration; Generic management services"
[48]
TS 28.533: "Management and orchestration; Architecture framework".
[49]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[50]
TS 38.314: "NR; Layer 2 measurements".
[51]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[52]
TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".
[53]
TS 32.158: "Management and orchestration; Design rules for Representational State Transfer (REST) Solution Sets (SS)".
[54]
TS 25.215: "Physical layer; Measurements (FDD)".
[55]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[56]
TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements".
[57]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[58]
TS 28.552: "Management and Orchestration; 5G performance measurements".
Up

3  Definitions and abbreviationsWord‑p. 16

3.1  Definitions |R10|Word‑p. 16

For the purposes of the present document, the terms and definitions given in TR 21.905 , TS 23.501, TS 38.300 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 , TS 23.501 or TS 38.300.
Management based MDT:
MDT data is collected from UEs in a specified area. The area is defined as a list of cells (UTRAN or E-UTRAN) or as a list of tracking/routing/location areas. The management based MDT is an enhancement of the management based trace functionality. Management based MDT can be either a logged MDT or Immediate MDT.
Immediate MDT:
Logged MDT:
Logged MBSFN MDT:
Collection of MBSFN measurements in idle and connected mode. Applicable only for eUTRAN.
Signalling based MDT:
MDT data is collected from one specific UE. The UE that is participating in the MDT data collection is specified as IMEI(SV) or as IMSI. The signalling based MDT is an enhancement of the signalling based subscriber and equipment trace. A signalling based MDT can be either a logged MDT or Immediate MDT.
MBSFN Area:
MBSFN Area Reserved Cell:
Up

3.2  Abbreviations |R10|Word‑p. 17

For the purposes of the present document, the abbreviations given in TR 21.905, TS 32.101 , TS 23.501, TS 38.300 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
AS
Application Server
BGCF
Breakout Gateway Control Function
CSCF
Call Session Control Function
I-CSCF
Interrogating-CSCF
IM CN SS
IP Multimedia Core Network Subsystem
IMEI-TAC
IMEI Type Allocation Code
P-CSCF
Proxy - CSCF
RCEF
RRC Connection Establishment Failure
RLF
Radio Link Failure
S-CSCF
Serving-CSCF
TAU
Tracking Area Update
Up

Up   Top   ToC