Добавил:
linker.pp.ua Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
4g - LTE / Rel-08_description_20140924 / Rel-08_description_20140924.doc
Скачиваний:
77
Добавлен:
15.12.2018
Размер:
3.85 Mб
Скачать

13.1.9 Key Performance Indicators (kpIs) for umts/geran uid_360002

Resources: S5

References

Document

Title/Contents

WID(s)

SP-070299

WID on Key Performance Indicator (KPI) for UMTS/GERAN

Impacted Specifications

-

-

New Dedicated Specifications/Reports

TS 32.410

Telecommunication management; Key Performance Indicators (KPI) for UMTS and GSM

UID

Name

Acronym

Resource

Hyperlink

rapporteur

TS_TR

340063

OAM&P 8

OAM8

-

-

-

-

340065

Performance Management

OAM8-PM

S5

-

-

-

360002

Key Performance Indicators (KPIs) for UMTS and GSM

OAM8

S5

SP-070299

China Mobile

32.410

KPIs are very important for operators to monitor their network. Currently, vendors and / or operators define their KPIs in proprietary ways which adds a big overhead on the evaluation of network performance and leads to an unfair rating of different vendors and/or operators. Hence KPIs should be standardized by 3GPP.

KPIs and definition of performance measurements are in the scope of network Performance Management (PM). Currently, performance measurements related to UMTS have been specified in 3GPP as follows:

  • TS 52.402 Performance Management (PM); Performance measurements – GSM

  • TS 32.404 Performance Management (PM); Performance measurements - Definitions and template

  • TS 32.405 Performance Management (PM); Performance measurements UTRAN

  • TS 32.406 Performance Management (PM); Performance measurements Core Network PS domain

  • TS 32.407 Performance Management (PM); Performance measurements Core Network CS domain

  • TS 32.408 Performance Management (PM); Performance measurements Teleservice

  • TS 32.409 Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)

SA5 TR 32.814 UTRAN and GERAN Key Performance Indicators (KPIs) served as basis for this work.

13.1.10 Service Level Tracing in ims (oam8-Trace) uid_11067

Resources: C1,C4,IETF

References

Document

Title/Contents

WID(s)

CP-080315

WID on Service Level Tracing in IMS

Impacted Specifications

TS 24.229

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 - CT1

TS 29.228

IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents - CT4

TS 29.229

Cx and Dx interfaces based on the Diameter protocol; Protocol details - CT4

New Dedicated Specifications/Reports

TS 24.323

Trace Management Object (MO) - CT1

UID

Name

Resource

Hyperlink

Notes

TS_TR

340066

Trace Management

-

-

-

-

11067

CT1 part

C1

CP-080315

CP#42 completed

24.323, 24.229

521028

(IETF)

C1-IETF

CP-080315

CP#58 Removed from Rel-8, Rel-9 and Rel-10 (Not completed internet-draft)

Rel-11 remains draft-dawes-dispatch-debug

531003

(IETF)

C1-IETF

CP-080315

CP#54 Draft removed from 3GPP documentation, covered by draft-dawes-sipping-debug

draft-dawes-sipping-debug-event

400022

CT4 part

C4

CP-080315

CP#42 completed

29.228, 29.229

400021

Deleted - CT3 part

C3

CP-080315

CP#42 stopped (No CT3-impact)

-

This work is linked to SA5 Stage 2 Trace Management (OAM8-Trace) UID_340066, Stage 1 being defined by OMA. The CT WGs Stage 3 work was removed from Rel-7 and is now continued in Rel-8. This work could not proceed without substantial contribution from IETF.

Subscriber and Equipment Trace provide very detailed information at call level on one or more specific mobile(s) or subscribers. This data is an additional source of information to performance measurements and allows going further in monitoring and optimization operations.

Service Level Tracing (SLT) improves and simplifies end-to-end service diagnostics and enhances the operator's ability to manage complex services. SLT is aimed at end-to-end service-level diagnostics, rather than per node tracing. By definition, SLT is the ability to capture and log all relevant information at each component within a service chain, associated with a specific service that is initiated either by an end-user or a component (see OMA-RD-OSPE-V1_0-20050614-C.pdf).

The following tasks for CT WGs were defined in SA5 Rel-7 Trace Management WID:

  • CT1 on trace activation/deactivation over SIP between IMS entities;

  • CT4 on trace activation/deactivation over Cx;

  • CT1, CT3, and CT4 on End-to-end tracing for IMS;

This work updates the above mentioned interface protocols to include the procedures defined in SA5 TS 32.422 "Trace control and configuration management". Protocol updates are needed for both trace activations, Signalling Based (SBA) and Management Based (MBA), and conveying SLT indication.

Соседние файлы в папке Rel-08_description_20140924