ETSI TS 124 323-2016 Universal Mobile Telecommunications System (UMTS) LTE 3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO) (V13 0 0 3GPP TS 24 323 v.pdf

1、 ETSI TS 124 323 V13.0.0 (2016-01) 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) TECHNICAL SPECIFICATION ETSI ETSI TS 124 323 V13.0.0 (2016-01)13GPP TS 24.323 version

2、13.0.0 Release 13Reference 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/8

3、8 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search 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 w

4、ritten 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 docu

5、ment 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 foll

6、owing services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx 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

7、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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI re

8、gistered for the benefit of its Members. 3GPPTM 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 ETSI TS 124 323 V13.0.0 (2016-01)23GPP TS 24.323 v

9、ersion 13.0.0 Release 13Intellectual 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

10、: “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 investigatio

11、n, 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

12、 (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

13、 cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. 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 de

14、scribed 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 ETSI TS 124 323 V13.0.0 (2016-01)33GPP TS 24.323 version 13.0.0 Release 13Contents Intellectual Prope

15、rty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 IMS service level tracing management object 6g35 Management object parameters 8g35.1 General . 8g35.2 Node: / 8g35.3 /Name

16、8g35.4 /Debug_info_List/ 8g35.5 /Debug_info_List/ . 8g35.6 /Debug_info_List/Debug_config/ . 8g35.7 /Debug_info_List/Debug_config/Address_of_record . 9g35.8 /Debug_info_List/Debug_config/Session_List/ 9g35.9 /Debug_info_List/Debug_config/Session_List/ . 9g35.10 /Debug_info_List/Debug_config/Session_L

17、ist/Session/ 9g35.11 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/ . 10g35.12 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/From 10g35.13 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/To . 10g35.14 /Debug_info_List/Debug_config/Session_List/S

18、ession/Start_trigger/ICSI 10g35.15 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/IARI . 11g35.16 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/Method . 11g35.17 /Debug_info_List/Debug_config/Session_List/Session/Start_trigger/Time . 11g35.18 /Debug_info_List/Deb

19、ug_config/Session_List/Session/Start_trigger/Debug_ID 12g35.19 /Debug_info_List/Debug_config/Session_List/Session/Stop_trigger/ . 12g35.20 /Debug_info_List/Debug_config/Session_List/Session/Stop_trigger/Time . 12g35.21 /Debug_info_List/Debug_config/Session_List/Session/Stop_trigger/Time_period . 12g

20、35.22 /Debug_info_List/Debug_config/Session_List/Session/Stop_trigger/Reason 13g35.23 /Debug_info_List/Debug_config/Session_List/Session/Control/ . 13g35.24 /Debug_info_List/Debug_config/Session_List/Session/Control/Interface_List/ 13g35.25 /Debug_info_List/Debug_config/Session_List/Session/Control/

21、Interface_List/ . 13g35.26 /Debug_info_List/Debug_config/Session_List/Session/Control/Interface_List/Interface 14g35.27 /Debug_info_List/Debug_config/Session_List/Session/Control/Depth . 14g35.28 /Debug_info_List/Debug_config/Session_List/Session/Control/Debug_ID 14g3Annex A (informative): Managemen

22、t object DDF 15g3Annex B (informative): Change history . 27g3History 28g3ETSI ETSI TS 124 323 V13.0.0 (2016-01)43GPP TS 24.323 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are su

23、bject 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 firs

24、t 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 wh

25、en editorial only changes have been incorporated in the document. ETSI ETSI TS 124 323 V13.0.0 (2016-01)53GPP TS 24.323 version 13.0.0 Release 131 Scope This document defines the IMS service level tracing management object. The management object is compatible with OMA Device Management protocol spec

26、ifications, 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 cap

27、abilities. 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,

28、 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 3GP

29、P 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, htt

30、p:/www.w3.org/TR/xmlschema-2/ 5 draft-dawes-sipping-debug-event-00 (May 2008): “A Session Initiation Protocol (SIP) Event Package for Debugging“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 6 3GPP TS 32.422: “Telecommunication management; Subscribe

31、r 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 abbreviat

32、ions apply: CN Core Network DDF Device Description Framework DM Device Management IMS IP Multimedia core network Subsystem IP Internet Protocol MO Management ObjectOMA Open Mobile Alliance SIP Session Initiation Protocol UE User Equipment ETSI ETSI TS 124 323 V13.0.0 (2016-01)63GPP TS 24.323 version

33、 13.0.0 Release 134 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 o

34、bject 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 ETS

35、I TS 124 323 V13.0.0 (2016-01)73GPP TS 24.323 version 13.0.0 Release 13Ext ?Session_List*Debug_info_List *Name ?Interface+*Session Start_triggerStop_triggerControlFrom?To?ICSI?IARI?Interface_ListDepth?Debug_ID?Time?Time_period?Reason?Debug_configAddress_of_recordMethod?Time?Debug_ID?Figure 1: The 3G

36、PP Service Level Tracing Management Object ETSI ETSI TS 124 323 V13.0.0 (2016-01)83GPP TS 24.323 version 13.0.0 Release 135 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 plac

37、eholder 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

38、 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_Li

39、st 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 c

40、onfiguration 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 ETSI TS 124 323 V13.0.0 (2016-01)93GPP TS 24.3

41、23 version 13.0.0 Release 13- Occurrence: ZeroOrMore - Format: node - Access Types: Get - Values: N/A 5.7/Debug_info_List/Debug_config/Address_of_record The Address_of_record leaf represents one public user identity. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: This public

42、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: 234150999999999ims.mnc015.mcc234.3gppnetwork.org 5.8 /Debug_info_List/Debug_config/Session_List/ The Sessi

43、on_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 sessi

44、ons 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:

45、One - Format: node ETSI ETSI TS 124 323 V13.0.0 (2016-01)103GPP TS 24.323 version 13.0.0 Release 13- 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 loggin

46、g 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, Re

47、place - 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_tr

48、igger/ICSI The ICSI leaf represents an IMS communication service identifier. - Occurrence: ZeroOrOne - Format: node - Access Types: Get, Replace - Values: ETSI ETSI TS 124 323 V13.0.0 (2016-01)113GPP TS 24.323 version 13.0.0 Release 13The format of the IMS commuication service identifier is defined

49、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/