You are on page 1of 33

3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; (2010-03) TelecommunicationV9.0.

0 management; Technical trace: Specification Subscriber and equipment Trace concepts and requirements !elease "#

3GPP TS 32.421

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational Partners accept no liability for any use of this "pecification. "pecifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Or ani!ational Partners$ Publications Offices.

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

%eywords
UMTS, management

3GPP Postal address 3GPP support office address


650 Route de !u"#o$e - So%&#a 'nt#%o$# Va$(onne - )R'*+, Te$.- .33 4 92 94 42 00 )a/- .33 4 93 65 40 16

&nternet
&tt%-11222.3g%%.o3g

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
)*+,+- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& currently bein re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

+ontent
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 &ntroduction...............................................................................................................................................9 , "cope......................................................................................................................................................: * /eferences..............................................................................................................................................: 3 ;efinitions- symbols and abbreviations..................................................................................................<
3., ;efinitions..............................................................................................................................................................< 3.* .bbreviations.......................................................................................................................................................,+

= Trace concepts and hi h>level architecture..........................................................................................,,


=., Trace concepts......................................................................................................................................................,, =.* Trace hi h level .rchitecture...............................................................................................................................,* =.3 "ervice 5evel Tracin for &M" hi h level .rchitecture.......................................................................................,8

8 Trace re?uirements...............................................................................................................................,:
8., General trace re?uirements..................................................................................................................................,: 8.* /e?uirements for Trace data................................................................................................................................,< 8.3 /e?uirements for Trace activation.......................................................................................................................,@ 8.3., /e?uirements for Trace "ession activation.......................................................................................................,@ 8.3.* /e?uirements for startin a Trace /ecordin "ession......................................................................................*, 8.= /e?uirements for Trace deactivation...................................................................................................................*3 8.=., /e?uirements for Trace "ession deactivation...................................................................................................*3 8.=.* /e?uirements for stoppin a Trace /ecordin "ession....................................................................................*= 8.8 /e?uirements for Trace ;ata reportin ................................................................................................................*8 8.9 /e?uirements for Privacy and "ecurity................................................................................................................*9 8.: /e?uirements for 1har in ..................................................................................................................................*9 8.< 3se cases for Trace..............................................................................................................................................*:

Annex A (informative): Trace use cases......................................................................................28 .., 3se case A,B multi>vendor 32 validation.........................................................................................*<
..,., ;escription.......................................................................................................................................................*< ..,.* 2(ample of re?uired data for this use case.......................................................................................................*<

..* 3se case A*B subscriber complaint....................................................................................................*<


..*., ;escription.......................................................................................................................................................*< ..*.* 2(ample of re?uired data for this use case.......................................................................................................*@

..3 3se case A3B malfunctionin 32......................................................................................................3+


..3., ;escription.......................................................................................................................................................3+ ..3.* 2(ample of re?uired data for this use case.......................................................................................................3+

..= 3se case A=B chec#in radio covera e..............................................................................................3+


..=., ;escription.......................................................................................................................................................3+ ..=.* 2(ample of re?uired data to cover use case A=................................................................................................3+

..8 3se case A8B testin a new feature....................................................................................................3,


..8., ;escription.......................................................................................................................................................3, ..8.* 2(ample of re?uired data to cover use case A8................................................................................................3,

..9 3se case A9B fine>tunin and optimisation of al orithmsCprocedures...............................................3,


..9., ;escription.......................................................................................................................................................3, ..9.* 2(ample of re?uired data to cover use case A9................................................................................................3*

..: 3se case A:B .utomated testin of "ervice Provider services..........................................................3*


..:., ;escription.......................................................................................................................................................3*

3GPP

!elease "

&

3GPP TS 3$%&$' ("%)%) $)')*)3#

..< 3se case A<B /e ression testin followin a networ# fi(.................................................................3*


..<., ;escription.......................................................................................................................................................3*

..@ 3se case A@B "ervice fault locali!ation within a "ervice Provider networ#......................................3*
..@., ;escription.......................................................................................................................................................3*

..,+ 3se case A,+B "ervice fault locali!ation when a service is hosted by a third party "ervice Provider ......................................................................................................................................................3*
..,+., ;escription.....................................................................................................................................................3*

Annex B (informative): Change history......................................................................................33

3GPP

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

)o3e2o3d
This Technical "pecification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e followin formal T"G approval. "hould the T"G modify the contents of the present document- it will be re>released by the T"G with an identifyin chan e of release date and an increase in version number as followsB Dersion (.y.! whereB ( the first di itB , presented to T"G for informationE * presented to T"G for approvalE 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

3GPP

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

4nt3odu"t#on
The present document is part of a T">family coverin the 3rd Generation Partnership ProjectE Technical "pecification Group "ervices and "ystem .spectsE Telecommunication mana ement- as identified belowB TS 32.42 : T" 3*.=**B T" 3*.=*3B !Su"scri"er an# e$ui%ment trace: Trace conce%ts an# re$uirements!& F"ubscriber and e?uipment traceB Trace control and confi uration mana ementFE F"ubscriber and e?uipment traceB Trace data definition and mana ementFE

"ubscriber and e?uipment 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 oin further in monitorin and optimisation operations. 1ontrary 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 malfunctionin mobile- advanced troubleshootin - optimisation of resource usa e and ?uality- /7 covera e control and capacity improvement- dropped call analysis- 1ore 'etwor# and 3T/.' end>to>end 3MT" procedure validation. The capability to lo data on any interface at call level for a specific user (e. . &M"&) or mobile type (e. . &M2& or &M2&"D)- or service initiated by a user allows ettin information which cannot be deduced from Performance measurements such as perception of end>user Go" durin his call (e. . re?uested Go" vs. provided Go")- correlation between protocol messa es and /7 measurements- or interoperability with specific mobile vendors. Moreover- performance measurements provide values a re ated on an observation periodE "ubscriber and 32 Trace ive instantaneous values for a specific event (e. . call- location update- etc.). &f performance measurements are mandatory for daily operations- future networ# plannin and primary trouble shootin E "ubscriber and 32 Trace is the easy way to o deeper into investi ation and 3MT" networ# optimisation. &n order to produce this data- "ubscriber and 32 Trace are carried out in the '2s- which comprise the networ#. The data can then be transferred to an e(ternal system (e. . an Operations "ystem (O") in TM' terminolo y- for further evaluation).

3GPP

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

S"o%e

The present document describes the re?uirements for the mana ement of Trace and the reportin of Trace data (includin 7;; mode and T;; mode) across 3MT" networ#s or 2P" networ#s as it refers to subscriber tracin (tracin of &M"& or Private &;) and e?uipment tracin (tracin of &M2& or &M2&"D). Trace also includes the ability to trace all active calls in a cell or multiple cells (1ell Traffic Trace). The present document also includes the description of "ervice 5evel Tracin (tracin of a specific service). &t defines the administration of Trace "ession activationCdeactivation by the 2lement Mana er (2M)- the networ# or 3ser 2?uipment (32) itself via si nallin - the eneration of Trace results in the 'etwor# 2lements ('2s) and 32 and the transfer of these results to one or more Operations "ystems- i.e. 2M(s) andCor 'etwor# Mana er(s) ('M(s)). The present document is built upon the basic "ubscriber and 32 Trace concept described in clause =. The hi h>level re?uirements for Trace data- Trace "ession activationCdeactivation and Trace reportin are defined in clause 8. 1lause 8 also contains an overview of use cases for Trace (the use cases are described in .nne( .). Trace control and confi uration mana ement are described in 3GPP T" 3*.=** H*I- and Trace data definition and mana ement are described in 3GPP T" 3*.=*3 H3I. The present document does not cover any Trace capability limitations within a '2 (e. . ma(imum number of simultaneous traced mobiles for a iven '2) or any functionality related to these limitations (e. . '2 abortin a Trace "ession due to resource limitations). The objectives of the Trace specifications areB a) to provide the descriptions for a standard set of Trace dataE

b) to produce a common description of the mana ement techni?ue for Trace administration and result reportin E c) to define a method for Trace results reportin across the mana ement interfaces.

The followin is beyond the scope of the present document- and therefore the present document does not describeB > > tracin non>"ubscriber or non>32 related events within an '2E tracin of all possible parties in a multi>party call (althou h multiple calls related to the &M"& specified in the Trace control and confi uration parameters are traceable).

The definition of Trace data is intended to result in comparability of Trace data produced in a multi>vendor wireless 3MT" andCor 2P" networ#(s)- for those Trace control and confi uration parameters that can be standardised across all vendors$ implementations. Dendor specific e(tensions to the Trace control and confi uration parameters and Trace data are discussed in 3GPP T" 3*.=** H*I and 3GPP T" 3*.=*3 H3I.

Re5e3en"e
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or non>specific. 7or a specific reference- subse?uent revisions do not apply. 7or a non>specific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a non>specific reference implicitly refers to the latest version of that document in the same Release as the present document. H,I H*I 3GPP T" 3*.,+,B FTelecommunication mana ementE Principles and hi h level re?uirementsF. 3GPP T" 3*.=**B FTelecommunication mana ementE "ubscriber and e?uipment traceB Trace control and confi uration mana ementF.

The followin documents contain provisions- which- throu h reference in this te(t- constitute provisions of the present document.

3GPP

!elease "

3GPP TS 3$%&$' ("%)%) $)')*)3#

H3I H=I H9I H:I H<I H@I H,+I 'OT2B

3GPP T" 3*.=*3B FTelecommunication mana ementE "ubscriber and e?uipment traceB Trace data definition and mana ementF. 3GPP T" *3.++*B F'etwor# architectureF. 3GPP T" *@.*+:B FPolicy control over Go interfaceF. 3GPP T" 8*.++<B FTelecommunication mana ementE G"M subscriber and e?uipment traceF. 3GPP T/ *,.@+8B FDocabulary for 3GPP "pecificationsF. OM. "ervice Provider 2nvironment /e?uirements- OM.>/;>O"P2>D,J+>*++8+9,=>1- The Open Mobile .lliance4 (3/5BhttpBCCwww.openmobilealliance.or C) 3GPP T" 33.=+,B F"ystem .rchitecture 2volution (".2)E "ecurity architectureF. Overall mana ement principles are defined in 3GPP T" 3*.,+, H,I.

6e5#n#t#on , 7m(o$ and a((3e8#at#on

3.1 6e5#n#t#on
7or the purposes of the present document- the terms and definitions iven in *,.@+8 H<I and the followin applyB Ce'' Traffic Trace: The ability to trace one or more active calls in one or more cells. (n# user visi"'e events: /efer to OM. "ervice Provider /e?uirements H@I. management activation)#eactivation: Trace "ession is activatedCdeactivated in different '2s directly from the 2M usin the mana ement interfaces of those '2s. Signa''ing Base# Activation)*eactivation: Trace "ession is activatedCdeactivated in different '2s usin the si nallin interfaces between those elements so that the '2s may forward the activationCdeactivation ori inatin from the 2M System Context: two different realisations of the telecommunication mana ement architecture. "ystem 1onte(t . has the &tf>' between a 'etwor# Mana er and an 2lement Man er. "ystem 1onte(t 0 has the &tf>' between a 'etwor# Mana er and a 'etwor# 2lement that has an embedded 2lement Mana er. "ee fi ure , in T" 3*.,+, H,I. Trace: eneral term used for "ubscriber- 2?uipment and "ervice Trace. Trace recor#: in the '2 a Trace record is a set of Traceable data collected as determined by the Trace control and confi uration parameters. Trace +ecor#ing Session: time interval within a Trace "ession while trace records are enerated for the "ubscriber32 or "ervice bein traced. The tri erin events startin and stoppin a Trace /ecordin "ession are defined in 3GPP T" 3*.=** H*I (see fi ure ,). Trace +ecor#ing Session +eference: identifies a Trace /ecordin "ession within a Trace "ession (see fi ure ,)

3GPP

!elease "

"

3GPP TS 3$%&$' ("%)%) $)')*)3#

Trace +ecor#ing Session +eference A, 1allC"ession A*

Trace +ecor#ing Session +eference A*

1allC"ession A, Time

"tart tri er event

"top tri er event

"tart tri er event

"top tri er event

Trace Session
/igure ': Trace !ecording Session 'ote that overlappin callsCsessions are possible for e. . 1ell Traffic Trace. Trace +eference: identifies a Trace "ession and is lobally uni?ue (see fi ure *) Trace Session: time interval started with a Trace "ession .ctivation and lasts until the ;eactivation of that specific Trace "ession (see fi ure *)
Activation > &M"& or &M2&("D) or Public &; > Trace /eference > Trace control and confi uration parameters *eactivation > Trace /eference

Trace Session /igure $: Trace Session

Time

Trace ,arameter Configuration: a techni?ue whereby a re?uest for tracin a certain "ubscriber- 32 or "ervice is sent by the 2M to the '2 for e(ecution. Trace ,arameter ,ro%agation: a techni?ue by which the '2 processes the trace confi uration (received from the 2M or another '2) and sends it to the relevant 'etwor# 2lement(s) via si nallin interface(s). Service -eve' Tracing: /efer to OM. "ervice Provider /e?uirements H@I.

3GPP

!elease "

')

3GPP TS 3$%&$' ("%)%) $)')*)3#

3.2 '((3e8#at#on
7or the purposes of the present document- the abbreviations iven in *,.@+8 H<I and 3*.,+, H,I apply.

3GPP

!elease "

''

3GPP TS 3$%&$' ("%)%) $)')*)3#

T3a"e "on"e%t and &#g&-$e8e$ a3"&#te"tu3e

4.1 T3a"e "on"e%t


The diversity of Trace re?uirements ma#es it difficult to identify and anticipate all the operator$s specific needs. Thusthe objective of this T" is not to list an e(haustive set of information to meet all the re?uirements. /ather- Trace data is defined without any limitation on the * followin dimensionsB > > Trace scopeB '2s and si nallin interfaces to Trace. Trace depthB level of details of Trace data.

&n order not to have any limitation of Trace data- there are si( levels of details definedB Ma(imum- Minimum- MediumMa(imumKithoutDendor"pecific2(tension- MinimumKithoutDendor"pecific2(tension and MediumKithoutDendor"pecific2(tension. The first three levels allow for vendor specific information to be traced and sent in the trace report file. The Ma(imum (or Ma(imumKithoutDendor"pecific2(tension) 5evels allow all Trace data to be recorded. The other 5evels provide a decoded subset of the data in the Ma(imum 5evel and allow an operator the fle(ibility in selectin the appropriate Trace data to record. The Trace ;epth- specified at the Trace "ession activation- is used to choose the level of detail of information to retrieve on the &tf>'. The Ma(imum (or Ma(imumKithoutDendor"pecific2(tension) 5evels of detail allow for retrieval of si nallin interface messa es within the Trace "cope in encoded format (see fi ure =.,.,).
Trace sco%e 2ncoded messa es ;ecoded &2s

.aximum level of detailsB .ll messa es are provided in their encoded format.

Trace #e%th

"pecific set of &2s from encoded messa es can be decoded by an e(ternal system.

/igure &%'%': 0a1imum or 0a1imum2ithout(endorSpecific31tension# 4evels of details of Trace

3GPP

!elease "

'$

3GPP TS 3$%&$' ("%)%) $)')*)3#

The Minimum (or MinimumKithoutDendor"pecific2(tension) 5evels of detail allow for retrieval of a decoded subset of the &2s contained in the si nallin interface messa es (see fi ure =.,.*).

Trace sco%e 2ncoded messa es ;ecoded &2s

.inimum level of detailsB . subset of decoded &2s is provided to cover the most usual use cases.

Trace #e%th
/igure &%'%$: 0inimum or 0inimum2ithout(endorSpecific31tension# 4evels of detail of Trace The Medium (or MediumKithoutDendor"pecific2(tension) 5evels of detail allow for retrieval of the decoded subset of the &2s contained in the si nallin interface messa es in the Minimum 5evel plus a selected set of decoded radio measurement &2s. The Trace data recorded at each 5evel is defined in 3GPP T" 3*.=*3 H3I.

4.2

T3a"e &#g& $e8e$ '3"&#te"tu3e

There are two types of activation- mana ement based activation and si nallin based activation. 7i ure =.*., represents the hi h>level view of the architecture of Trace Mana ement 0ased .ctivationC;eactivation. 7i ure =.*., is only showin the interfaces in principle a hi h>level view. ;etails of Trace activationCdeactivation are defined in 3GPP T" 3*.=** H*I.

,$ement Manage3
1

*et2o39 ,$ement

/igure &%$%': Architecture for 0anagement 5ased Activation67eactivation

3GPP

T3a"e Pa3amete3 +on5#gu3at#on

!elease "

'3

3GPP TS 3$%&$' ("%)%) $)')*)3#

7i ure =.*.* represents the hi h>level view of the architecture of "i nallin 0ased .ctivationC;eactivation. 7i ure =.*.* is only showin the interfaces in principle. ;etails of Trace activationCdeactivation are defined in 3GPP T" 3*.=** H*I.

,$ement Manage3 T3a"e Pa3amete3 +on5#gu3at#on


1

*et2o39 ,$ement

0 ... :

*et2o39 ,$ement

0 ... :

*et2o39 ,$ement

T3a"e Pa3amete3 P3o%agat#on

/igure &%$%$: Architecture for Signalling 5ased Activation67eactivation

3GPP

!elease "

'&

3GPP TS 3$%&$' ("%)%) $)')*)3#

7i ure =.*.3 represents the hi h>level view of the architecture of Trace /eportin for "ystem 1onte(t .. 7i ure =.*.3 is only showin the interfaces in principle.

Trace :ollection 3ntity

3lement 0anager

;et9or< 3lement

;et9or< 3lement

;et9or< 3lement

/igure &%$%3: Architecture for 8igh*level vie9 of Trace !eporting in System :onte1t A 7i ure =.*.= represents the hi h>level view of the architecture of Trace /eportin for "ystem 1onte(t 0. 7i ure =.*.= is only showin the interfaces in principle.

Trace Co''ection (ntity

2M 'etwor# 2lement

/igure &%$%&: Architecture for Trace !eporting in System :onte1t 5 2ditor$s noteB The placement of the Trace 1ollection 2ntity is a deployment matter for the operator. &f it is placed outside the operator$s secure !one- it is up to the operator to use secure connections to and from the Trace 1ollection 2ntity.

3GPP

!elease "

'+

3GPP TS 3$%&$' ("%)%) $)')*)3#

4.3
a)

Se38#"e !e8e$ T3a"#ng 5o3 4MS &#g& $e8e$ '3"&#te"tu3e


Trace activation at the 32- and

There are two ways in which to activate service level trace for &M"B

b) Trace activation at an &M" '2. 7i ure =.3., represents the hi h>level view of the architecture of "i nallin 0ased .ctivationC;eactivation at the 32 re?uired to support "ervice 5evel Tracin for &M". 7i ure =.3., is only showin the interfaces in principle. ;etails of "ervice 5evel Trace .ctivationC;eactivation are defined in 3GPP T" 3*.=** H*I.

,$ement Manage3
1

*et2o39 ,$ement
1

0...

T3a"e Pa3amete3 +on5#gu3at#on

U,
1 0...

*et2o39 ,$ement

0...

*et2o39 ,$ement

U,
0...

T3a"e Pa3amete3 P3o%agat#on

/igure &%3%': Architecture for Signalling 5ased Activation67eactivation required for Service 4evel Tracing for =0S at the >3

3GPP

!elease "

',

3GPP TS 3$%&$' ("%)%) $)')*)3#

7i ure =.3.* represents the hi h>level view of the architecture of "i nallin 0ased .ctivationC;eactivation at an &M" '2 re?uired to support "ervice 5evel Tracin for &M". 7i ure =.3.* is only showin the interfaces in principle. ;etails of "ervice 5evel Trace .ctivationC;eactivation are defined in 3GPP T" 3*.=** H*I.

,$ement Manage3
1

*et2o39 ,$ement

T3a"e Pa3amete3 +on5#gu3at#on

0 ... :

*et2o39 ,$ement

U,
1 0 ... :

T3a"e Pa3amete3 P3o%agat#on

/igure &%3%$ : Architecture for Signalling 5ased Activation67eactivation required for Service 4evel Tracing for =0S at the =0S ;3 7i ure =.3.3 represents the hi h>level view of the architecture of Trace /eportin for "ystem 1onte(t .. 7i ure =.3.3 illustrates the reportin conte(t for "ervice 5evel Tracin for &M" from the 32 and is only showin the interfaces in principle. The reportin conte(t for "ervice 5evel Tracin for &M" from the &M" '2 is illustrated in 7i ure =.*.3B .rchitecture for Li h>level view of Trace /eportin in "ystem 1onte(t .

*et2o39 Manage3

U,

/igure &%3%3: Architecture for Trace !eporting from >3 to support Service 4evel Tracing for =0S

3GPP

!elease "

'-

3GPP TS 3$%&$' ("%)%) $)')*)3#

T3a"e 3e;u#3ement

5.1 Gene3a$ t3a"e 3e;u#3ement


The eneral hi h>level re?uirements for Trace- common to both Mana ement activationCdeactivation and "i nallin 0ased .ctivationC;eactivation- are as followsB > for the Ma(imum 5evelB Trace data encompassin all si nallin messa es on the different interfaces dedicated to the events of the traced subscriber or 32 with their entire content (all &2s) shall be retrieved. The operator can then use an e(ternal system (e. . an Operations "ystem (O") in TM' terminolo y) and decode specific information in line with operator re?uirements. for the Minimum 5evelB a selected subset of &2s shall be retrieved from the si nallin interface messa es. The Minimum 5evel provides support for the most common use cases (described in anne( .). for the Medium 5evelB a selected Minimum 5evel subset of &2s from the si nallin interface messa es and a selected set of radio measurement &2s shall be retrieved. for the Ma(imumKithoutDendor"pecific2(tension 5evelB it is the same as for Ma(imum level without vendor specific data. for the MediumKithoutDendor"pecific2(tension 5evelB it is the same as for Medium level without vendor specific data. for the MinimumKithoutDendor"pecific2(tension 5evelB it is the same as for Minimum level without vendor specific data.

> > > > >

The hi h>level re?uirements for Trace- specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply. (refer to OM. "ervice Provider 2nvironment /e?uirements H@I). 'OT2B 2ach referenced OM. re?uirement utili!es its OM. uni?ue identifier within s?uare brac#ets. 1larification provided to each re?uirement should be considered applicable to other OM. re?uirements usin the same concepts.

>

H"5T>L5>,I with the followin clarificationB > The OM. term OMA Service Provider Environment (OSPE) shall be understood as P5M'.

>

H"5T>L5>8I with the followin clarificationB > &n the conte(t of "ervice 5evel Tracin for &M" a Minimum and Ma(imum level of detail of trace only applies. Trace data for "ervice 5evel Tracin at Minimum and Ma(imum level of detail shall include information associated to end user visible events

>

H"5T>L5>9I with the followin clarificationB > > The OM. term service chain shall be understood as the relationship between appropriate &M" elements needed to support a service. The term service chain does not imply a strict se?uence of events. The source of the lo ed trace information (e. . &M" element includin ">1"17) shall be identifiable when the retrieved trace information is analy!ed.

>

H"5T>L5>,+I with the followin clarificationB > &M" elements that do not support "ervice 5evel Tracin shall not prohibit the propa ation of the Trace Parameter Propa ation.

>

H"5T>O"/>, > Multiple "ervice 5evel Trace instances shall be simultaneously supported by the P5M' and the 32 (e. . several services initiated from the same 32 may each have a Trace /ecordin "ession /eference)

3GPP

!elease "

'.

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.2 Re;u#3ement 5o3 T3a"e data


The hi h level re?uirements for Trace data- common to both Mana ement activationCdeactivation and "i nallin 0ased .ctivationC;eactivation- are as followsB > The Trace records have to contain &nformation 2lements or si nallin messa es from control si nallin andCor the characteristics of the user data. The followin list contains the 'etwor# 2lements and the Traceable interfaces in the '2s where tracin is neededB > > > > > > > > > > > > > > M"1 "erverB .- &u>1"- Mc and M.P (G- 0- 2- 7- ;- 1) interfacesE 1.P MGKB Mc- 'b>3P- &u>3P L""B M.P (1- ;- Gc- Gr) 1(- "9a and "9d interfaces and location and subscription information "G"'B Gb- &u>P"- Gn- M.P (Gr- Gd- Gf)- 1.P (Ge) Gs- "9d- "= and "3 interfaces GG"'B Gn- Gi and Gmb interfaces ">1"17B Mw- M - Mr and Mi interfaces P>1"17B Gm and Go interfaces /'1B &u>1"- &u>P"- &ur- &ub and 3u interfaces 0M>"1B Gmb interface e>'ode0B ",>MM2- M*- 3u MM2B ",>MM2- "3- "9a- ",+- ",, "ervin GatewayB "=- "8- "<- ",, P;' GatewayB "*a- "*b- "*c- "8- "9b- G(- "<- "Gi

. uni?ue &; within a Trace "ession shall be enerated for each Trace /ecordin "ession. This is called the Trace /ecordin "ession /eference.

The hi h level re?uirements for Trace data applicable for "i nallin 0ased .ctivationC;eactivation for "ervice 5evel Tracin for &M"- are as followsB > &n the conte(t of "ervice 5evel Tracin for &M" Trace records have to contain &nformation 2lements or si nallin messa es or end user visible event from control si nallin andCor the characteristics of the user data. The followin list contains the &M" '2s and the Traceable interfaces in the '2s where tracin is neededB > > > > > > > > > L""B "h and 1( interfaces and location and subscription informationE ">1"17B &"1- Mw- M - Mr and Mi interfacesE P>1"17B Gm and Go interfacesE &>1"17B Mw and 1( interfacesE "&P ."B &"1 interfaceE M/7B Mr interfacesE MG17B M interfacesE 0G17B Mi interfacesE

. uni?ue &; within a Trace "ession shall be enerated for each Trace /ecordin "ession. This is called the Trace /ecordin "ession /eference. &n the conte(t of "ervice 5evel Tracin for &M" the Trace /ecordin "ession shall be uni?ue across all &M" '2s within a P5M'.

3GPP

!elease "

'"

3GPP TS 3$%&$' ("%)%) $)')*)3#

1han es to e(istin '2s and interfaces above may be re?uired. These chan es would be dependent upon various 3GPP wor#in roups and possibly other non>3GPP industry roups for completion of Trace "ession .ctivationC;eactivation. 7or a detailed description of '2s and interfaces above see 3GPP T" *3.++* H=I.

5.3 Re;u#3ement 5o3 T3a"e a"t#8at#on


5.3.1 Re;u#3ement 5o3 T3a"e Se #on a"t#8at#on
The hi h level re?uirements for Trace "ession activation- common to both Mana ement activation and "i nallin based activation)- are as followsB > &n the case of a subscriber Trace- the Trace "ession will be activated for a certain subscriber whose identification (&M"& in 3T/.'C1"CP") shall be #nown in the '2s where subscriber Trace is needed. &n the case of 2>3T/.' the &M"& shall not be included in the Trace Parameter Propa ation data to the e>'ode0. &n the case of a 32 Trace- the Trace "ession will be activated for a certain 32 whose identification (&M2& or &M2&"D) shall be #nown in the '2s where 32 Trace is needed. &n the case of 2>3T/.'- neither the &M2& nor &M2&"D shall be included in the Trace Parameter Propa ation data to the e>'ode0 > Trace "ession activation shall be possible for both home subscribers and visitin subscribers. There are two methods for Trace "ession activationB Mana ement activation and "i nallin activation. 7or an established callCsession within a 'etwor# 2lement- it is optional for the 'etwor# 2lement to start a Trace /ecordin "ession for the associated "ubscriber or 32 upon receipt of the Trace activation re?uest from the 2M. . lobally uni?ue &; shall be enerated for each Trace "ession to identify the Trace "ession. This is called the Trace /eference. The method for achievin this is to divide the Trace reference into 1ountry- Operator- and trace &d. Trace "ession may be activated from the 2M simultaneously to multiple '2s with the same Trace /eference (i.e. same Trace "ession). The Trace "cope and ;epth shall be specified within the control and confi uration parameters durin Trace "ession activation. There can be cases in a '2 when it receives multiple Trace "ession activations for the same connection (e. . simultaneous 1"CP" connections). &n these cases the startin time of the Trace "ession .ctivation and the startin time of the first Trace /ecordin "ession is the same usin si nallin based activation. 7or these cases there are two different cases for the Trace "ession activation in a 'etwor# 2lement when it receives another Trace "ession activation to the same subscriber or M"B > > > > &f the Trace /eference is e?ual to an e(istin one- a new Trace "ession shall not be startedE &f the Trace /eference is not e?ual to an e(istin one- a new Trace "ession may be started.

>

> > >

> > >

The 2M shall always provide the trace control and confi uration parameters to the appropriate '2s at the time of Trace "ession activation. The Trace collection entity shall be notified- in case of theTrace "ession activation has failed- by the response messa e with the specific cause (e. . overload) from the '2 on which the Trace "ession activation failure happened.

The hi h>level re?uirements for Trace "ession activation- specific to "i nallin 0ased activation- are as followsB > "i nallin based activation shall be able to capture si nallin messa es as early in a session as possible- e. . by means of a pi ybac#ed trace invocation messa e in the case of a new connection or new bearer setup 7or active users- it shall be possible to start trace recordin when the trace order is received- by means of a distinct trace invocation messa e.

3GPP

!elease "

$)

3GPP TS 3$%&$' ("%)%) $)')*)3#

The hi h>level re?uirements for Trace "ession activation- specific to Mana ement activation- are as followsB > &n the case of a subscriber Trace- the Trace "ession will be activated for a certain subscriber whose identification (&M"& in 3T/.'C1"CP" or Private &; in &M") shall be #nown in the '2s where subscriber Trace is needed. &n the case of a 1ell Traffic Trace- Trace "ession activation should be possible for all calls active in a cell or multiple cells without #nowled e of the 32sN identification (&M2& or &M2&"D). > &n the case of a 1ell Traffic Trace- Trace "essions should be activated for all the '2s where 1ell Traffic Trace is specified.

The hi h>level re?uirements for Trace "ession activation specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@IB > H"5T>1OM>*I with the followin clarificationB > > The OM. term component in the conte(t of "ervice 5evel Tracin for &M" shall be understood as &M" '2 and 32.

H"5T>L5>*I with the followin clarificationB > > The OM. terms device and component shall be understood as 32 and &M" '2- respectivelyE The &M" '2s L""- PC&C">1"17- ." and 32- apply only.

>

H"5T>.1>,I with the followin clarificationB > > The OM. term Authorised Actor shall be understood as '2- 2M or 'ME The OM. term trace indication shall be understood as "tart Tri er 2vent.

>

H"5T>.1>*I with the followin clarificationB > > The OM. term Service Provider shall be understood as "ervice ProviderE The OM. term marking request shall be understood as the ability to send the Trace Parameter 1onfi uration to either the 32 or &M" '2.

> >

H"5T>.1>9I H"5T>.1>:I with the followin clarificationB > The OM. term criteria shall be understood as Trace 1onfi uration Parameters.

3GPP

!elease "

$'

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.3.2 Re;u#3ement 5o3 ta3t#ng a T3a"e Re"o3d#ng Se

#on

The hi h level re?uirements for startin a Trace /ecordin "ession- common to both Mana ement activation and "i nallin based activation)- are as followsB > > > &t is optional for the '2 to start a Trace /ecordin "ession if there are insufficient resources available within the '2. The Trace /ecordin "ession /eference shall be uni?ue within a Trace "ession. The Trace /ecordin "ession should be started after appropriate start tri er events are detected.

The hi h level re?uirements for startin a Trace /ecordin "ession- specific to Mana ement activation- are as followsB > > > > 2ach '2 shall enerate its own Trace /ecordin "ession /eference (i.e.- independent Trace /ecordin "essions). 2ach '2 shall start the Trace /ecordin "ession based upon the Trace control and confi uration parameters received by the '2 in the Trace "ession activation. &n the case of a trace other than 1ell Traffic Trace- the correlation of Trace data will be done with a Trace /eference and &M"& C &M2& C &M2&"D C Private &;. The Trace /ecordin "ession can start only when the &M"& (in the case of a subscriber trace)- the &M2& C &M2&"D (in case of 32 trace) or Private &; (in the case of &M") is made available in the '2. &n order to trace the early phases of the call the &M"& (in case of subscriber trace)- the &M2& C &M2&"D (in case of 32 trace) or Private &; (in case of &M") shall be made available to the '2 as soon as practically possible. 2. . the &M"& and &M2& C &M2&"D shall be made available to both "ervin /'1 and ;rift /'1. &n the case of 2>3T/.' the 1ore 'etwor# node that tri ers a Trace /ecordin "ession to 2>3T/.' shall eitherB > provide a trace lo includin Trace /eference- Trace /ecordin "ession /eference and the identity of the 32 (i.e. &M"& or &M2&("D) to the Trace 1ollection 2ntity- or provide a notification includin Trace /eference- Trace /ecordin "ession /eference and the identity of the 32 (i.e. &M"& or &M2&("D)) to the Trace 1ollection 2ntity.

>

&n the case of a 1ell Traffic Trace- the Trace /ecordin "ession should start upon the Trace control and confi uration parameters bein received by the '2s in the Trace "ession activation and the presence of call activity. 7urthermore- the the 1ore 'etwor# node that handles the traced session should be re?uested toB provide a trace lo includin Trace /eference- Trace /ecordin "ession /eference and the identity of the 32 (i.e. &M"& or &M2&("D) to the Trace 1ollection 2ntity- or provide a notification includin Trace /eference- Trace /ecordin "ession /eference and the identity of the 32 (i.e. &M"& or &M2&("D)) to the Trace 1ollection 2ntity.

The hi h>level re?uirements for startin a Trace /ecordin "ession- specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@IB > H"5T>L5>3I with the followin clarificationB > > > The OM. term marked shall be understood as 32 or &M" '2 that has previously received Trace Parameter 1onfi uration information. The OM. term marking shall be understood as Trace Parameter 1onfi uration.

H"5T>1OM>3I with the followin clarificationB > The OM. term indication for S ! shall be understood as "tart Tri er 2vent

3GPP

!elease "

$$

3GPP TS 3$%&$' ("%)%) $)')*)3#

> The OM. terms inbound and outbound protocols shall be understood as- for e(ample- inbound "&P and outbound ;iameter.

3GPP

!elease "

$3

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.4 Re;u#3ement 5o3 T3a"e dea"t#8at#on


5.4.1 Re;u#3ement 5o3 T3a"e Se #on dea"t#8at#on
The hi h level re?uirements for Trace "ession deactivation- common to both Mana ement deactivation and "i nallin based deactivation- are as followsB > > > The Trace "ession shall be deactivated usin the Trace /eference specified for the Trace "ession activation. The Trace "ession shall be deactivated in all those '2s where it was activated. The deactivation of a Trace "ession durin a Trace /ecordin "ession within a '2 may ta#e place anytime after the '2 receives the deactivation re?uest until the end of the current Trace /ecordin "ession related to the traced "ubscriber or 32. Trace "ession deactivation in a '2 could occur when two simultaneous si nallin connections for a subscriber or 32 e(ist. 2. . fi ure 8.=., shows '2 3 havin two si nallin connections (one of them or both of them are traced with the same Trace /eference) and a Trace deactivation messa e is received. The Trace "ession shall be closed.

>

*,1
T3a"ed "onne"t#on

T3a"e dea"t#8at#on

*,2

*,3

/igure +%&%': Trace Session closure The hi h>level re?uirements for Trace "ession deactivation specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@I. > > H"5T>1OM>*I with the followin clarificationB H"5T>.1>,I with the followin clarificationB > ;eactivation at an &M" '2 formin part of an &M" service chain shall not prohibit the propa ation of the Trace Parameter Propa ation.

3GPP

!elease "

$&

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.4.2 Re;u#3ement 5o3 to%%#ng a T3a"e Re"o3d#ng Se

#on

The hi h level re?uirements for stoppin a Trace /ecordin "ession- common to both Mana ement deactivation and "i nallin based deactivation- are as followsB > > The Trace /ecordin "ession should be stopped after appropriate stop tri er events are detected. Trace "ession deactivation in a '2 could occur when two simultaneous si nallin connections for a subscriber or 32 e(ist. 2. . fi ure 8.=.* shows '23 havin two si nallin connections- but only one connection is traced. &f the non>traced connection is released- the Trace /ecordin "ession shall be #ept in '23. &f the traced connection is released the Trace /ecordin "ession shall be closed.

*,1
T3a"ed "onne"t#on

*,2 3e$ea e

*,3

/igure +%&%$: Trace !ecording Session closure The hi h level re?uirements for stoppin a Trace /ecordin "ession- specific to "i nallin based deactivation- are as followsB > The Trace /ecordin "ession should be stopped after an '2 receives the appropriate si nallin deactivation messa e.

The hi h>level re?uirements for stoppin a Trace /ecordin "ession- specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@I. > H"5T>.1>3I with the followin clarificationB > The implication of un>mar#in a 32 is threefoldB a) &t prohibits the initiation of further trace recordin sessions from that 32 or &M" '2 (i.e. subse?uent services shall not be traced)E

b) &t cancels outstandin Trace Parameter 1onfi uration information on a 32 or &M" '2E c) 2(istin trace recordin sessions active in the P5M' may continue until an appropriate "top 2vent Tri er.

3GPP

!elease "

$+

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.5 Re;u#3ement 5o3 T3a"e 6ata 3e%o3t#ng


The hi h level re?uirements for Trace ;ata reportin - common to both Mana ement activationCdeactivation and "i nallin 0ased .ctivationC;eactivation- are as follows (Trace record contents- file formats and file transfer mechanisms are defined in 3GPP T" 3*.=*3 H3I)B > > > > Trace records should be enerated in each '2 where a Trace "ession has been activated and a Trace /ecordin "ession has been started. 7ormat of the Trace records sent over &tf>' shall be MM5 based on the "chema in T" 3*.=*3 H3I. Trace records should be transferred on the &tf>' to the 'etwor# Mana er usin one of two approachesB direct transfer from '2 to 'M or transfer from '2 to 'M via 2M. Trace records may also be transferred to an e(ternal &P address (received in Trace 1ontrol and 1onfi uration Parameters) in 3 waysB ,. *. 3. ;irect transfer from '2 to &P address Transfer from '2 to &P address via 2M Transfer from '2 to 2M. The 2M notifies the holder of the &P address that collects the files.

The hi h>level re?uirements for stoppin a Trace /ecordin "ession- specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@I. > H"5T>L5>=I with the followin clarificationB > > 2ncoded trace information shall be "tandard 7ile 7ormat. "tandard 7ile 7ormat may not be applicable for encoded trace information at the 32.

H"5T>L5>:I with the followin clarificationB > .n instance of a service level trace across a P5M' shall be uni?uely identifiable usin the Trace /ecordin "ession /eference.

> >

H"5T>L5><I H"5T>1OM>,I with the followin clarificationB > > > Time stampin alone to determine the se?uence of &M" '2s performin trace within the service chain shall not be usedE "tatistical information shall not be included as part of &M" '2 characteristicsE "ervice 5evel Tracin shall apply only to the &M" session layer and not the underlyin transport layers.

>

H"5T>1OM>=I with the followin clarificationB > .n &M" '2- in addition to providin trace information specific to a service that it has traced- may also ma#e available other information- for e(ample- timestamp and throu hput information.

>

H"5T>'&>,I with the followin clarificationB > The 32 shall e(pose a standardised interface for Trace Parameter 1onfi uration and the retrieval of trace information. This interface may not be standardi!ed by 3GPP.

>

H"5T>'&>*I with the followin clarificationB > .n &M" '2 shall transfer Trace records in "tandard 7ile 7ormats via &tf>'.

7or transfer of Trace records via &tf>'- 7TP or secure 7TP shall be used. The transfer of Trace record from the 32 is 7or 7urther "tudy.

3GPP

!elease "

$,

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.6 Re;u#3ement 5o3 P3#8a"7 and Se"u3#t7


The hi h>level re?uirements for privacy and security- specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@I. > H"5T>P/D>,I with the followin clarificationB > > > > Privacy shall be applied across the appropriate Trace &tf>'.

H"5T>"21>,I H"5T>"21>*I H"5T>"21>3I with the followin clarificationB > &t may not be possible to retrieve Trace information from &M" '2s from outside the P5M' where the &M" '2s reside.

>

H"5T>&OP>,I with the followin clarificationB > The propa ation of the Trace Parameter 1onfi uration and the "tart Tri er event shall be prohibited by the P5M' when e. . the "&P ." is hosted outside a P5M'.

.s the radio access nodes in 2>3T/.' are outside an operatorNs secure domain- the followin re?uirement applies for 2>3T/.' as described in 3GPP T" 33.=+, H,+IB > H"2T>"21>,I %eys stored inside e'0s shall never leave a secure environment within the e'0. Khen security #ey(s) transported on control si nallin messa es are included in the trace file- the #ey value(s) shall be removed and replaced with the value O3navailableP.

5.0 Re;u#3ement 5o3 +&a3g#ng


The hi h>level re?uirements for char in - specific for "ervice 5evel Tracin for &M" are as followsB The followin hi h>level OM. "ervice 5evel Tracin re?uirements apply H@I. > H"5T>1/G>,I

3GPP

!elease "

$-

3GPP TS 3$%&$' ("%)%) $)')*)3#

5.< U e "a e 5o3 T3a"e


The operator can use "ubscriber and 32 Trace for numerous purposes. Lowever- the use cases for Trace can be divided into two basic cate oriesB > > Troubleshootin use cases cover situations where the operator is solvin an e(istin problem in his networ#E Dalidation testin use cases cover situations where the operator is not solvin a #nown problem but merely analysin - fine>tunin or optimisin his networ#.

. more detailed description for the followin use cases for "ubscriber and 32 Trace can be found in anne( .B > > > > > > &nteroperability chec#in between 32 from different vendorsE Go" profile chec#in for a subscriber after a subscriber complaintE Malfunctionin 32E 1hec#in radio covera e in a certain areaE Testin new featuresE 7ine>tunin and optimisation of al orithms or procedures.

The operator can use "ervice 5evel Tracin for &M" for numerous purposes. Lowever- the use cases for Trace can be divided into two basic cate oriesB > > Troubleshootin use cases cover situations where the operator is solvin e(istin problems with services offered to their subscribers. Dalidation testin use cases cover situations where the operator is not solvin a #nown problem but performin service re ression and automated service testin .

. more detailed description of the followin use cases for "ervice 5evel Tracin can be found in anne( .B > > > > .utomated testin of service provider servicesE /e ression testin followin a networ# fi(E "ervice fault locali!ation within a "ervice ProviderNs networ#E "ervice fault locali!ation when a service is hosted by a third party "ervice Provider.

3GPP

!elease "

$.

3GPP TS 3$%&$' ("%)%) $)')*)3#

'nne/ ' (#n5o3mat#8e)T3a"e u e "a e '.1 U e "a e =1- mu$t#-8endo3 U, 8a$#dat#on


'.1.1 6e "3#%t#on
The aim of this use case is to chec# how different vendor$s 32s are wor#in (e. . in field testin ) in the mobile networ# or to et detailed information on the 32. The study can be started by an initiative from operator for verification of 32 from different vendors (e. . testin how the 32 fulfils the re?uirements set by the standards). The operator can perform the test usin test 32s or tracin subscribers$ mobiles.

'.1.2 ,/am%$e o5 3e;u#3ed data 5o3 t&# u e "a e


The Trace parameters re?uired to cover use case A, are listed belowB > > > Tracin is needed in the /adio 'etwor# (/'1) or in the 1ore 'etwor# (M""- "G"')E The identification of the Trace case shall be &M2& or &M2&"D (and possibly &M"&)E The level of details usually is to et the most important &2s from the si nallin messa es (Medium 5evel) or all messa es with their encoded &2s (Ma(imum 5evel).

The traceable protocols areB > > &n /'1B //1- '0.P- /'".P- /.'.P. &n M""C"G"'B ;T.P messa es.

'.2

U e "a e =2- u( "3#(e3 "om%$a#nt

'.2.1 6e "3#%t#on
The aim of this use case is to chec# how the complainin subscriber$s services are wor#in - to et information on the services in order to find out the reason for the complaint. The study can be started after a subscriber is complainin at hisCher home or visited operator that some of the service to which heCshe subscribed is not wor#in . 2. . the subscriberB > > > cannot ma#e callsE cannot use some supplementary serviceE does not et the ne otiated Go" level (e. . Mobile subscriber activates video>streamin application to watch the latest sport events and every time the subscriber tries to connect to the service the system disconnects the subscriber$s 3MT" bearer).

.s the Trace is activated for a subscriber- the si nallin based Trace "ession activation shall be used- as the location of the subscriber is not #nown.

3GPP

!elease "

$"

3GPP TS 3$%&$' ("%)%) $)')*)3#

'.2.2 ,/am%$e o5 3e;u#3ed data 5o3 t&# u e "a e


The Trace parameters re?uired to cover the use case A* are listed belowB > The list of '2s where tracin may be needed depends on the service bein complained about by the subscriber. 7or this use case- tracin should be possible in all networ# elements- such asB L""- M""- /'1- MGK- "G"'GG"'. The identification of the subscriber in a Trace is &M"& in 3T/.'C1"CP". The identification of the 32 in a Trace is &M2& or &M2&"D. The data includes those &nformation 2lements from the si nallin messa es- which are related to the service(s) bein complained about by the subscriber (Medium 5evel).

> >

2(ample cases- which can be the basis for subscriber complaintB ,. The subscriber$s 1" call is misrouted This illustrates an instance where a subscriber complains that his calls are bein cross>connected (or misrouted). "uch a complaint involves settin up a Trace at all the 3GPP standardised interfaces bein handled by the M"1. Lowever- the Trace functionality shall not cover M"1 internal or vendor proprietary interfaces. The Trace record shall need to have the dialled number and connected number. *. The subscriber$s call is dropped Tracin data is re?uired from the radio networ# (3T/.') or from the core networ# (M""- "G"'- GG"'). &n the radio networ# the radio covera e shall be chec#ed. "ee use case A= (chec#in radio covera e). 0eside the radio covera e- other information can be useful as well- li#e /51 parameter- power information (O5P1 or //1 measurement report)- error ratios (052/ C 02/- ";3 error ratio)- etc. Tracin in the core networ# is needed also- if the problem is not in the radio networ#. 2. . in case of P" domain the call can be dropped by the application due to the lon delays or con estions in T1P layer or due to bad Go". Thus in "G"' the re?uested and ne otiated Go" parameters should be included in the Trace record. 3. The received Go" level is less than the ne otiated level. To be able to solve the possible problem Tracin data is re?uired from L""- "G"'- GG"'- and 3T/.'. 7urthermore in case of problem in 1" calls tracin in MGK shall be performed. 7rom L"" Trace data the operator can monitor whether the subscriber$s authentication to the networ# is successful- and what #ind of Go" parameters are allowed to the subscriber. 7rom "G"' Trace data the operator can monitor P;P conte(t creation re?uest from mobile. /e?uest seems to contain le al Go" profile (incl. Ma(imum bandwidth- uaranteed bandwidth etc) and the local resources in "G"' are available to provide the service as re?uested by the subscriber. 7rom 3T/.' Trace data the operator can monitor whether the ma(imum bandwidth and uaranteed bandwidth- re?uested by "G"'- acceptable for 3T/.'. Thus to chec# whether 3T/.' can provide and maintain the re?uested radio access bearer services. 7rom GG"' Trace data the operator can monitor P;P conte(t activation between "G"' and GG"'. &f the problem is in the 1" domain the MGK Trace can provide the Go" data.

3GPP

!elease "

3)

3GPP TS 3$%&$' ("%)%) $)')*)3#

'.3

U e "a e =3- ma$5un"t#on#ng U,

'.3.1 6e "3#%t#on
The aim of this use case is to chec# a 32- which is not wor#in correctly. The study can be initiated by the operator when heCshe suspects that a 32 not wor#in accordin to the specifications or heCshe would li#e to et more information on a specific 32- which is on the rey or blac# 2&/ list.

'.3.2 ,/am%$e o5 3e;u#3ed data 5o3 t&# u e "a e


The Trace parameters re?uired to cover the use case A3 are listed belowB > > > 32 Tracin may be needed in the /adio 'etwor# (3T/.') or in the 1ore 'etwor# (M""- "G"'). The identification of the subscriber in a Trace is &M"&. The identification of the 32 in a Trace is &M2& or &M2&"D. The level of details depends on the operator needs (either Minimum 5evel or Medium 5evel).

The malfunction of 32 in 3T/.' can occur in different places. The problem can be in basic //1 and /.'.P si nallin - /adio 0earer procedures- Landover procedures- Power control etc. Therefore- all //1- /.'.P- '0.P- /'".P si nallin procedures- transmission powers- error ratios (052/ C 02/";3 error ratio) and retransmission can be included in the Trace records.

'.4

U e "a e =4- "&e"9#ng 3ad#o "o8e3age

'.4.1 6e "3#%t#on
This use case aims at chec#in the radio covera e on a particular networ# area. This study can be started by an initiative from operator for testin radio covera e on a particular eo raphical area followin networ# e(tension for instance (e. . new site installation). The operator can perform a drive test on the new site area- and chec# that radio covera e is correct- or may collect 1ell Traffic Trace data on all of the cells active in the area of interest.

'.4.2 ,/am%$e o5 3e;u#3ed data to "o8e3 u e "a e =4


The ;5 radio covera e can be chec#ed usin the values of 1P&1L 2cC'o and /"1P measured by the mobile on the cells in the active set and the monitored set. These measurements are sent to the /'1 trou h the //1 messa e M2."3/2M2'T /2PO/T. The 3T/.' Trace record intra fre?uency measurement contains the re?uired information. The 3T/.' Trace record inter fre?uency- and inter /.T measurements can also be used to chec# radio covera e with other fre?uencies or systems. .fter a networ# e(tension- the operator can chec# that 2cC'o and /"1P levels on the new site area are the e(pected ones- and there is no covera e hole. The followin Trace parameters are re?uired to cover use case A=B > > > The type of '2 to Trace is /'1. The identification of the subscriber in a Trace is &M"&. The identification of the 32 in a Trace is &M2& or &M2&"D. &n the case of a 1ell Traffic Trace- the identification of the cells where Trace data is to be collected.

3GPP

!elease "

3'

3GPP TS 3$%&$' ("%)%) $)')*)3#

>

The Trace data to retrieve shall contain the messa es with all &2s that are relevant for radio covera e.

'.5

U e "a e =5- te t#ng a ne2 5eatu3e

'.5.1 6e "3#%t#on
This use case aims at testin the implementation of a new feature in the networ# before its eneral deployment. The functionality can be either a standard feature or a vendorCoperator specific feature. This study is started by an initiative from the operator. The operator can perform a drive test on the area where the feature is introduced- and chec# its ood behaviour as well as its benefits- in term of ?uality or capacity. Le can also rely on subscribers$ Trace data when they use the feature to be tested.

'.5.2 ,/am%$e o5 3e;u#3ed data to "o8e3 u e "a e =5


;ependin on the feature- the list of '2s to Trace- as well as the level of details can be different. 7or a feature concernin 1ore and 3T/.' networ#s- for instance hard handover- "/'" relocation- or new 3MT" bearer service- the operator needs to activate Trace on several '2s. Then- the operator can be interested inB > > Only the protocol messa es enerated by the featureE or The impact of the new feature introduction on the networ#- for instance- the radio covera e- the capacity- the ?uality- or the behaviour of the e(istin al orithms.

&n this last case- the operator needs more detailed data- for instance messa es with all (Ma(imum 5evel) or part of the &2s (Minimum 5evel). The followin Trace parameters are re?uired to cover use case A8B > > > The types of '2s to Trace are '2s that can be traced related to the feature. The identification of the subscriber in a Trace is &M"&. The identification of the 32 in a Trace is &M2& or &M2&"D. The Trace data to retrieve can be either only the protocol messa es (Ma(imum 5evel) or the messa es with all or part of the &2s (Minimum 5evel).

'.6

U e "a e =6- 5#ne-tun#ng and o%t#m# at#on o5 a$go3#t&m 1%3o"edu3e

'.6.1 6e "3#%t#on
"ubscriber and 32 Trace is part of the optimisation process. Trace data are used to et feedbac# on the networ# ?uality and capacity after optimisation operations li#e parameter fine>tunin - or new networ# desi n. 2ach intervention to improve the networ# behaviour can be confirmed both by measurement data and Trace data. This study is started followin an initiative from the operator. The operator can perform a drive test on the area andCor activate a 1ell Traffic Trace where the optimisation has been performed- and chec# its ood behaviour as well as its impact on the networ#. Le can also rely on subscribers$ Trace data when they use the networ# to be optimised.

3GPP

!elease "

3$

3GPP TS 3$%&$' ("%)%) $)')*)3#

'.6.2 ,/am%$e o5 3e;u#3ed data to "o8e3 u e "a e =6


;ependin on the optimisation operation- the list of '2s to Trace- as well as the level of details can be different. 0ut enerally- fine>tunin activities li#e scramblin code plan- handover and relocation al orithms- or call admission al orithm optimisation concern a very specific part of the networ#. To cover this use case- the operator is usually searchin for the hi hest level of details- on specific '2s. The followin Trace parameters are re?uired to cover use case A9B > > > > The types of '2s to Trace are any '2 that can be traced related to the networ# to be optimised. The identification of the subscriber in a Trace is &M"&. The identification of the 32 in a Trace is &M2& or &M2&"D. &n the case of a 1ell Traffic Trace- the identification of the cells where Trace data is to be collected. The Trace data to retrieve are the messa es in encoded format with all (Ma(imum 5evel) or part of the &2s (Minimum 5evel).

'.0

U e "a e =0- 'utomated te t#ng o5 Se38#"e P3o8#de3 e38#"e

'.0.1 6e "3#%t#on
7or a detailed description of this use>case see OM. "ervice Provider 2nvironment /e?uirements H@I.

'.<

U e "a e =<- Reg3e 5#/

#on te t#ng 5o$$o2#ng a net2o39

'.<.1 6e "3#%t#on
7or a detailed description of this use>case see OM. "ervice Provider 2nvironment /e?uirements H@I.

'.9

U e "a e =9- Se38#"e 5au$t $o"a$#>at#on 2#t&#n a Se38#"e P3o8#de3 net2o39

'.9.1 6e "3#%t#on
7or a detailed description of this use>case see OM. "ervice Provider 2nvironment /e?uirements H@I.

'.10

U e "a e =10- Se38#"e 5au$t $o"a$#>at#on 2&en a e38#"e # &o ted (7 a t&#3d %a3t7 Se38#"e P3o8#de3

'.10.1 6e "3#%t#on
7or a detailed description of this use>case see OM. "ervice Provider 2nvironment /e?uirements H@I.

3GPP

!elease "

33

3GPP TS 3$%&$' ("%)%) $)')*)3#

'nne/ ? (#n5o3mat#8e)+&ange &# to37


:hange history
7ate TSG ? TSG 7oc% @un 2002 S'A16 SP-020330 6e" 2002 S'A1< SP-020055 Ma3 2003 S'A19 SP-030140 6e" 2003 S'A22 SP-030612 Ma3 2004 S'A23 SP-040116 Se% 2004 S'A25 SP-040542 6e" 2004 S'A26 SP-040000 6e" 2004 S'A26 SP-040000 Ma3 2005 S'A20 SP-050043 Ma3 2005 S'A20 SP-050043 Ma3 2005 S'A20 SP-050043 @un 2005 S'A2< SP-050294 Se% 2005 S'A29 SP-050623 Ma3 2006 S'A31 SP-060100 Se% 2006 S'A33 SP-060552 Se% 2000 S'A30 SP-000614 Se% 2000 S'A30 SP-000614 Ma3 200< SP-39 SP-0<0069 Ma3 200< SP-39 SP-0<0069 @un 200< SP-40 SP-0<0329 Se% 200< SP-41 SP-0<1260 6e" 200< SP-42 SP-0<0<46 @un 2009 SP-44 SP-0902<9 6e" 2009 :! --000 1 000 2 000 3 000 4 000 5 000 6 000 0 000 < 000 9 001 0 001 1 001 2 001 3 001 4 001 5 001 6 001 0 001 < 001 9 002 0 002 2 002 4 !ev Subject6:omment -Su(m#tted to S' =16 5o3 4n5o3mat#on ---------------------+o33e"t#on o5 t3a"e de%t& e/ten #on -'dd m# U%date to Re$-9 8e3 #on (M++) Ma3 2010 SP-40 SP-100034 -'$#gn t&e &and$#ng o5 e"u3#t7 9e7 5o3 ,-UTR'* 2#t& 33.401 #ng T3a"e 4nte35a"e 5o3 SGS* and DSS $# t Su(m#tted to S' =1< 5o3 '%%3o8a$ +o33e"t#on to T3a"e 3e;u#3ement - a$#gnment 2#t& S'2B 23.002 +o33e"t#on o5 4MS u( "3#(e3 #dent#5#"at#on 5o3 T3a"e +o33e"t#on #n T3a"e &#g& $e8e$ a3"&#te"tu3e Remo8a$ o5 G,R'* 53om Re$-6 32.42/ e3#e o5 T3a"e %e"#5#"at#on Remo8e 3e;u#3ement 5o3 &a8#ng 'S*.1 a T3a"e 3e"o3d 5o3mat Remo8e #n Re$-6 t&e #gna$$#ng (a ed T3a"e #n 4MS due to m# #ng S4P #gna$$#ng u%%o3t 53om +*114,T) Remo8e am(#gu#t7 on t&e 5#$e 5o3mat 5o3 t3a"e data at t&e *et2o39 ,$ement (*, ) +o33e"t#on to t&e S"o%e +o33e"t t&e $# t o5 #nte35a"e t3a"e %a3amete3 C '$#gn 2#t& 32.422 and 32.423 ?M-S+ *et2o39 ,$ement and Gm( #nte35a"e add#t#on 5o3 M?MS t3a"#ng 'dd u%%o3t 5o3 UTR'* T66 - 6e"$a3e R'T T7%e 4nt3odu"t#on o5 Se38#"e !e8e$ T3a"#ng 5o3 4MS 'dd +e$$ T3a55#" T3a"e "a%a(#$#t7 to 32.421 T3a"e "on"e%t and 3e;u#3ement 'dd e/tended t3a"e de%t& to #n"$ude Vendo3 S%e"#5#" ,/ten #on (VS,) 'dd !T, node and #nte35a"e 'dd t3a"e 5un"t#ona$#t7 5o3 ,-UTR'* 'dd t3a"e a"t#8at#on 5a#$u3e 3e %on e 4nt3odu"t#on o5 U, #dent#5#e3 5o3 t3a"e #n ,-UTR'* +&ange t&e de "3#%t#on 5o3 T3a"e Re"o3d#ng Se #on Re5e3en"e :at @ld -- 1.0. 0 -- 2.0. 0 ) 6.0. 0 ) 6.1. 0 ) 6.2. 0 ) 6.3. 0 + 6.4. 0 + 6.4. 0 ) 6.5. 0 ) 6.5. 0 ) 6.5. 0 ? 6.6. 0 ? 6.0. 0 ? 0.0. 0 + 0.1. 0 + 0.2. 0 + 0.2. 0 ? <.0. 0 ? <.0. 0 + <.1. 0 + <.2. 0 <.3. ) 0 <.4. ) 0 <.5. -- 0 9.0. ' 0 ;e9

6.0.0 6.1.0 6.2.0 6.3.0 6.4.0 6.5.0 6.5.0 6.6.0 6.6.0 6.6.0 6.0.0 0.0.0 0.1.0 0.2.0 <.0.0 <.0.0 <.1.0 <.1.0 <.2.0 <.3.0 <.4.0 <.5.0 9.0.0 9.1.0

3GPP