1、 ETSI TS 132 321 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Test management Integration Reference Point (IRP); Requirements (3GPP TS 32.321 version 15.0.0 Release 15) TECHNICAL S
2、PECIFICATION ETSI ETSI TS 132 321 V15.0.0 (2018-07)13GPP TS 32.321 version 15.0.0 Release 15Reference RTS/TSGS-0532321vf00 Keywords GSM,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 As
3、sociation but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 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 p
4、rint 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
5、 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.asp
6、x If you find errors in the present document, please send your comment to one of the following 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
7、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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTS
8、TMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks
9、registered and owned by the GSM Association. ETSI ETSI TS 132 321 V15.0.0 (2018-07)23GPP TS 32.321 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to t
10、hese 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. Late
11、st 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 W
12、eb server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property
13、 of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has be
14、en 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 refer
15、ence 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 described in c
16、lause 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 132 321 V15.0.0 (2018-07)33GPP TS 32.321 version 15.0.0 Release 15Contents Intellectual Property Rights 2
17、g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Purpose . 6g35 Requirements 7g35.1 Overview 7g35.2 Test . 7g35.2.1 Test Initiation 7g35.2.2 Test Termination . 8g35.2.2
18、.1 Explicit Test Termination . 8g35.2.2.2 Implicit Test Termination . 8g35.2.3 Test Monitoring 8g35.2.4 Test Result Reporting . 9g35.3 Test States 9g35.4 Test Categories . 10g35.4.1 Resource Self Test 10g35.4.2 Connection Test 10g35.4.3 Loopback Test 10g3Annex A (informative): Change history . 11g3H
19、istory 12g3ETSI ETSI TS 132 321 V15.0.0 (2018-07)43GPP TS 32.321 version 15.0.0 Release 15Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change fo
20、llowing 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
21、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 d
22、ocument. Introduction The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.321: “Test management Integration Reference Point (IRP): Requirements“;
23、32.322: “Test management Integration Reference Point (IRP): Information Service (IS)“; 32.326: “Test management Integration Reference Point (IRP): Solution Set (SS) definitions“. A 3G telecommunication network is composed of a multitude of different network elements (NE). For a successful operation
24、of the network the operator must be provided with mechanisms allowing him to manage the network. These management activities can be grouped into several areas: configuration management, fault management, performance management, accounting management and security management. A management function ass
25、isting in different high level management areas such as fault management and performance management is test management. The purpose of testing is to get information about the functionality and performance of the 3G managed network subject to the test. The present document is part of a set of technic
26、al specifications defining the telecommunication management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 5. The TM architecture is described in 3GPP TS 32.102 6. The other specifications define the interface (ITf-N) between the managing system (manager), which is in general
27、the network manager (NM) and the managed system (agent), which is either an element manager (EM) or the managed NE itself. The Itf-N is composed of a number of integration reference points (IRPs) defining the information in the agent that is visible for the manager, the operations that the manager m
28、ay perform on this information and the notifications that are sent from the agent to the manager. One of these IRPs is the Test Management IRP. Each IRP is specified by a set of TSs: Requirements, Information Service, CORBA SS, etc. ETSI ETSI TS 132 321 V15.0.0 (2018-07)53GPP TS 32.321 version 15.0.
29、0 Release 151 Scope The present document describes, in addition to the requirements defined in 1 and 2, the requirements for the Test Management IRP. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - Refere
30、nces 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 GS
31、M document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 ITU-
32、T Recommendation X.745: “Information technology - Open Systems Interconnection - Systems Management: Test management function“. 4 3GPP TS 32.301: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 5 Void 6 ITU-T Recommendation
33、 X.737: “Information technology - Open Systems Interconnection; Systems Management: Confidence and diagnostic test categories“. 7 IETF RFC2679: “A One-way Delay Metric for IPPM“. 8 IETF RFC3393: “IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)“. 9 IETF RFC2680: “A One-way Packet L
34、oss Metric for IPPM“. 10 IETF RFC2681: “A Round-trip Delay Metric for IPPM“. ETSI ETSI TS 132 321 V15.0.0 (2018-07)63GPP TS 32.321 version 15.0.0 Release 153 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: test catego
35、ry: one or more tests sharing a common purpose and similar characteristics Tester Object (TO): managed object that is instantiated for the purpose of monitoring and controlling a test invocation Each test invocation has one associated TO. TOs are created and deleted by managed objects with TARR func
36、tionality. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: NE Network Element NM Network Management Center TARR Test Action Request Receiver TO Tester Object 4 Purpose The purpose of testing is to get information about the functionality and performance
37、of the 3G managed network subject to the test. This information can be used in other network management areas, for instance in fault management. Testing is an activity that involves the operator, the managing system (the OS) and the managed system (the NE). Generally the operator requests the execut
38、ion of tests from the OS and the managed NE autonomously executes the tests without any further support from the operator. In case of intrusive tests it is required that the network resources to be tested are locked prior to test execution. During the test execution the telecommunication service pro
39、vided by the network resources is interrupted. After completion of the test, depending on the test result, the network resources shall be set to the most appropriate state. Test management capabilities should be provided over the Itf-N in order to allow the NM operator to perform tests on network re
40、sources. This capability is especially important at times when only the NM but not the OMC is attended, which might be the case at night or during weekends. In the context of fault management the NM operator may use the testing capabilities over the Itf-N for numerous purposes: - When a fault has be
41、en detected and if the information provided in the alarm report is not sufficient to localise the faulty resource, tests can be executed in order to localise the fault. - When a fault has been detected and if the information provided in the alarm report specifies the faulty resource, tests can be ex
42、ecuted on that resource in order to determine the required repair action. - During normal operation of the NE, tests can be executed for the purpose of discovering undetected faults. - After a faulty resource has been repaired or replaced and before it is restored to service, tests can be executed o
43、n that resource in order to make sure that it is fault free. However, regardless of the context where the testing is used, its target is always the same: verify if a systems physical or functional resource performs properly and, in case it happens to be faulty, provide all the information to help th
44、e operator to localise and correct the fault. The requirements for the test management service shall be based on ITU-T Recommendation X.745 3. ETSI ETSI TS 132 321 V15.0.0 (2018-07)73GPP TS 32.321 version 15.0.0 Release 155 Requirements 5.1 Overview The IRPManager (test conductor) must be able to in
45、itiate and terminate tests. For this purpose special test initiation and termination requests may be used. The IRPAgent (test performer) must be able to receive and react upon these requests. Special objects may be created for the purpose of monitoring and control of the test execution. During test
46、execution the IRPManager shall be able to monitor the test. Test results shall be made available to the IRPManager by test result reports (notifications). It shall be possible to log these test result reports. This gives rise to the following requirements for the test management function to be satis
47、fied: - the ability for the manager to initiate tests; - the ability for the manager to terminate tests; - the ability for the manager to monitor the test execution; - the specification of a mechanism to report the test results to the manager; - the specification of a mechanism to log test results i
48、n the agent. These capabilities are outlined in the following sections in more detail. 5.2 Test 5.2.1 Test Initiation The IRPManager shall be able to initiate a test in the IRPAgent by sending a test request to the IRPAgent. The IRPAgent must have at least one object instance capable of receiving th
49、ese test requests. In response to a test request one or more tests shall be initiated. Each test shall be controlled and monitored individually by special objects instantiated exclusively for this purpose. These objects are called Tester Objects (TOs). Each of the tests initiated in response to a test request shall have a single associated TO. The test request shall include the following information: - The network resources to be tested. - Information about the managed objects (e.g. TOs) assisting in the test execution. - Any other information us
