|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
3GPP IP Multimedia Subsystem (IMS)
service level tracing Management Object (MO)
(3GPP TS 24.323 version 13.0.0 Release 13)
---------------------- Page: 1 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 1 ETSI TS 124 323 V13.0.0 (2016-01)
Reference
RTS/TSGC-0124323vd00
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 2 ETSI TS 124 323 V13.0.0 (2016-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 3 ETSI TS 124 323 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 5
4 IMS service level tracing management object . 6
5 Management object parameters . 8
5.1 General . 8
5.2 Node: / . 8
5.3 //Name . 8
5.4 //Debug_info_List/ . 8
5.5 //Debug_info_List/ . 8
5.6 //Debug_info_List//Debug_config/ . 8
5.7 //Debug_info_List//Debug_config/Address_of_record . 9
5.8 //Debug_info_List//Debug_config/Session_List/ . 9
5.9 //Debug_info_List//Debug_config/Session_List/ . 9
5.10 //Debug_info_List//Debug_config/Session_List//Session/ . 9
5.11 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/ . 10
5.12 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/From . 10
5.13 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/To . 10
5.14 //Debug_info_List//Debug_config/Session_List//Ses sion/ Start_trigger/ICSI . 10
5.15 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/IARI . 11
5.16 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/Method . 11
5.17 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/Time . 11
5.18 //Debug_info_List//Debug_config/Session_List//Session/Start_trigger/Debug_ID . 12
5.19 //Debug_info_List//Debug_config/Session_List//Session/Stop_trigger/ . 12
5.20 //Debug_info_List//Debug_config/Session_List//Session/Stop_trigger/Time . 12
5.21 //Debug_info_List//Debug_config/Session_List//Session/Stop_trigger/Time_period . 12
5.22 //Debug_info_List//Debug_config/Session_List//Session/Stop_trigger/Reason . 13
5.23 //Debug_info_List//Debug_config/Session_List//Session/Control/ . 13
5.24 //Debug_info_List//Debug_config/Session_List//Session/Control/Interface_List/ . 13
5.25 //Debug_info_List//Debug_config/Session_List//Session/Control/Interface_List// . 13
5.26 //Debug_info_List//Debug_config/Session_List//Session/Control/Interface_List//Interface . 14
5.27 //Debug_info_List//Debug_config/Session_List//Session/Control/Depth . 14
5.28 //Debug_info_List//Debug_config/Session_List//Session/Control/Debug_ID . 14
Annex A (informative): Management object DDF . 15
Annex B (informative): Change history . 27
History . 28
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 4 ETSI TS 124 323 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 5 ETSI TS 124 323 V13.0.0 (2016-01)
1 Scope
This document defines the IMS service level tracing management object. The management object is compatible with
OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device
Description Framework as described in the Enabler Release Definition OMA-ERELD _DM-V1_2 [3].
The IMS service level tracing management object consists of relevant parameters that can be managed for IMS service
level tracing capabilities.
2 References
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.003: "Numbering, addressing and identification".
[3] OMA-ERELD-DM-V1_2-20070209-A: "Enabler Release Definition for OMA Device
Management, Version 1.2".
[4] XML Schema Part 2: Datatypes Second Edition, W3C Recommendation 28 October 2004,
http://www.w3.org/TR/xmlschema-2/
[5] draft-dawes-sipping-debug-event-00 (May 2008): "A Session Initiation Protocol (SIP) Event
Package for Debugging".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[6] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace
control and configuration management".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CN Core Network
DDF Device Description Framework
DM Device Management
IMS IP Multimedia core network Subsystem
IP Internet Protocol
MO Management Object
OMA Open Mobile Alliance
SIP Session Initiation Protocol
UE User Equipment
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 6 ETSI TS 124 323 V13.0.0 (2016-01)
4 IMS service level tracing management object
The IMS service level tracing management object is used to manage configuration settings of the UE for IMS service
level tracing. The management object covers parameters for IMS service level trace related capabilities. The
management object enables the management of the settings on behalf of the end user.
The management object Identifier is: urn:oma:mo:ext-3gpp-ims_slt:1.0.
Protocol compatibility: This MO is compatible with OMA DM 1.2.
The following nodes and leaf objects are possible under the Service Level Tracingnode:
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 7 ETSI TS 124 323 V13.0.0 (2016-01)
Name ?
Debug_info_List * Debug_config
Ext ?
Session_List *
Address_of_record
Session Start_trigger From?
To?
ICSI?
IARI?
Method?
Time?
Debug_ID?
Stop_trigger Time?
Time_period?
Reason?
Control Interface_List * Interface+
Depth?
Debug_ID?
Figure 1: The 3GPP Service Level Tracing Management Object
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 8 ETSI TS 124 323 V13.0.0 (2016-01)
5 Management object parameters
5.1 General
This clause describes the parameters for the IMS service level tracing management object.
5.2 Node: /
This interior node acts as a placeholder for one or more accounts for a fixed node.
- Occurrence: OneOrMore
- Format: node
- Access Types: Get
- Values: N/A
The interior node is mandatory if the UE supports one or more IMS service level tracing capabilities. Support for a UE
is defined by the related roles as defined by the related IMS service level tracing service, as listed in clause 4 of this
specification.
NOTE: One node is normally used.
5.3 //Name
The Name leaf is a name for the 3GPP service level tracing settings.
- Occurrence: ZeroOrOne
- Format: chr
- Access Types: Get
- Values:
5.4 //Debug_info_List/
The Debug-info_List node acts as a placeholder for control and configuration of IMS service level tracing.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: N/A
5.5 //Debug_info_List/
This run-time node acts as a placeholder for one or more debugging configurations containing control and configuration
of IMS service level tracing.
- Occurrence: One
- Format: node
- Access Types: Get
- Values: N/A
5.6 //Debug_info_List//Debug_config/
The Debug-config node acts as a placeholder for control and configuration of IMS service level tracing.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 9 ETSI TS 124 323 V13.0.0 (2016-01)
- Occurrence: ZeroOrMore
- Format: node
- Access Types: Get
- Values: N/A
5.7
//Debug_info_List//Debug_config/Address_of_recor
d
The Address_of_record leaf represents one public user identity.
- Occurrence: One
- Format: chr
- Access Types: Get, Replace
- Values:
This public user identity is the identity used to subscribe to SIP debugging configuration from the debug-event package.
The format of the public user identity is defined by 3GPP TS 23.003 [2].
EXAMPLE: sip: [email protected]
5.8 //Debug_info_List//Debug_config/Session_List/
The Session_List interior node is used to allow a reference to a list of different SIP sessions to be debugged.
- Occurrence: One
- Format: node
- Access Types: Get
- Values: N/A
5.9 //Debug_info_List//Debug_config/Session_List/
This run-time node acts as a placeholder for one or more descriptions of SIP sessions to be debugged.
- Occurrence: One
- Format: node
- Access Types: Get
- Values: N/A
5.10
//Debug_info_List//Debug_config/Session_List//
Session/
The Session interior node is used to allow a reference to events that start and stop logging of SIP signalling, and to
control what is logged.
- Occurrence: One
- Format: node
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 10 ETSI TS 124 323 V13.0.0 (2016-01)
- Access Types: Get, Replace
- Values: N/A
5.11
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/
The Start_trigger interior node is used to allow a reference to events that start logging of SIP signalling.
- Occurrence: One
- Format: node
- Access Types: Get, Replace
- Values: N/A
5.12
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/From
The From leaf represents an address in the From: SIP header field.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: N/A
5.13
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/To
The To leaf represents an address in the To: SIP header field.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: N/A
5.14
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/ICSI
The ICSI leaf represents an IMS communication service identifier.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values:
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 11 ETSI TS 124 323 V13.0.0 (2016-01)
The format of the IMS commuication service identifier is defined by 3GPP TS 24.229 [5].
EXAMPLE: urn:urn-7:3gpp-service.ims.icsi.mmtel
5.15
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/IARI
The IARI leaf represents an IMS application reference identifier.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values:
The format of the IMS application reference identifier is defined by 3GPP TS 24.229 [5].
EXAMPLE: urn:urn-7:3gpp-application.ims.iari.mmtel-app-
5.16
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/Method
The Method leaf represents a SIP method.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values:
The SIP method names are listed in 3GPP TS 24.229 [5].
EXAMPLE: MESSAGE
5.17
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/Time
The Method leaf represents a SIP method.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: DDThh:mm:ss>
Date and time is described by the standard type 'dateTime' for an XML schema [4].
th
EXAMPLE: 2009-05-09T15:00:00-05:00 to indicate 3:00 pm on May 9 , 2009 for Eastern Standard Time,
which is 5 hours behind Coordinated Universal Time (UTC).
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 24.323 version 13.0.0 Release 13 12 ETSI TS 124 323 V13.0.0 (2016-01)
5.18
//Debug_info_List//Debug_config/Session_List//
Session/Start_trigger/Debug_ID
The Debug_ID leaf represents represents an identifier that allows trace logging to be correlated across IMS entities.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: <6-digit hexadecimal number>
The format of the trace reference is 3 octets in hexadecimal format, as defined by 3GPP TS 32.422 [6].
EXAMPLE: 7BA614
5.19
//Debug_info_List//Debug_config/Session_List//
Session/Stop_trigger/
The Stop_trigger interior node is used to allow a reference to events that stop logging of SIP signalling.
- Occurrence: One
- Format: node
- Access Types: Get, Replace
- Values: N/A
5.20
//Debug_info_List//Debug_config/Session_List//
Session/Stop_trigger/Time
The Time leaf represents a time at which SIP logging is stopped.
- Occurrence: ZeroOrOne
- Format: node
- Access Types: Get, Replace
- Values: DDThh:mm:ss>
Date and time is described by the standard type 'dateTime' for an XML schema [4].
th
EXAMPLE: 2009-05-09T15:00:00-05:00 to indicate 3:00 pm on May 9 , 2009 for Eastern Standard Time,
which is 5 hours behind Coordinated Universal Time (UTC).
5.21
//Debug_info_List//Debug_config/Session_List//
Session/Stop_trigger/Time_period
The Time_period leaf represents a time duration o
...