ETSI TS 132 321-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Test management Integr.pdf

《ETSI TS 132 321-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Test management Integr.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 321-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Test management Integr.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommTest management I(3GPP TS 32.3TECHNICAL SPECIFICATION132 321 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; t Integration Reference Point Requirements .321 version 13.0.0 Release 1316-02) hase

2、2+); (UMTS); nt (IRP); 13) ETSI ETSI TS 132 321 V13.0.0 (2016-02)13GPP TS 32.321 version 13.0.0 Release 13Reference RTS/TSGS-0532321vd00 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

3、- NAF 742 C Association 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 elect

4、ronic 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

5、) 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/statu

6、s.asp 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 photocopy

7、ing 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.

8、 All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered 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 registe

9、red and owned by the GSM Association. ETSI ETSI TS 132 321 V13.0.0 (2016-02)23GPP TS 32.321 version 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

10、, 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

11、 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 ma

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

13、. 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “shoul

14、d 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 ETSI TS

15、132 321 V13.0.0 (2016-02)33GPP TS 32.321 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Purpose . 6g35

16、 Requirements 7g35.1 Overview 7g35.2 Test . 7g35.2.1 Test Initiation 7g35.2.2 Test Termination . 8g35.2.2.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

17、 Test 10g35.4.2 Connection Test 10g35.4.3 Loopback Test 10g3Annex A (informative): Change history . 11g3History 12g3ETSI ETSI TS 132 321 V13.0.0 (2016-02)43GPP TS 32.321 version 13.0.0 Release 13Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3G

18、PP). 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 nu

19、mber 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, u

20、pdates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication man

21、agement; as identified below: 32.321: “Test management Integration Reference Point (IRP): Requirements“; 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 telecommuni

22、cation network is composed of a multitude of different network elements (NE). For a successful operation 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 man

23、agement, performance management, accounting management and security management. A management function assisting 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 pe

24、rformance of the 3G managed network subject to the test. The present document is part of a set of technical 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 othe

25、r specifications define the interface (ITf-N) between the managing system (manager), which is in general 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)

26、 defining the information in the agent that is visible for the manager, the operations that the manager may 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

27、, Information Service, CORBA SS, etc. ETSI ETSI TS 132 321 V13.0.0 (2016-02)53GPP TS 32.321 version 13.0.0 Release 131 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

28、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 r

29、eference, 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 TS 32.101: “Telecommunication management; Principles a

30、nd high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 ITU-T Recommendation X.745: “Information technology - Open Systems Interconnection - Systems Management: Test management function“. 4 3GPP TS 32.301: “Telecommunication management; Configuration Management

31、 (CM); Notification Integration Reference Point (IRP): Requirements“. 5 Void 6 ITU-T Recommendation 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 Pa

32、cket Delay Variation Metric for IP Performance Metrics (IPPM)“. 9 IETF RFC2680: “A One-way Packet Loss Metric for IPPM“. 10 IETF RFC2681: “A Round-trip Delay Metric for IPPM“. ETSI ETSI TS 132 321 V13.0.0 (2016-02)63GPP TS 32.321 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitio

33、ns For the purposes of the present document, the following terms and definitions apply: test category: 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 t

34、est invocation has one associated TO. TOs are created and deleted by managed objects with TARR functionality. 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 Obj

35、ect 4 Purpose The purpose of testing is to get information about the functionality and performance 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 m

36、anaging system (the OS) and the managed system (the NE). Generally the operator requests the execution 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 tes

37、ted are locked prior to test execution. During the test execution the telecommunication service provided 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

38、 should be provided over the Itf-N in order to allow the NM operator to perform tests on network resources. 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 op

39、erator may use the testing capabilities over the Itf-N for numerous purposes: When a fault has been 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

40、 if the information provided in the alarm report specifies the faulty resource, tests can be executed 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

41、has been repaired or replaced and before it is restored to service, tests can be executed on 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 per

42、forms properly and, in case it happens to be faulty, provide all the information to help the 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 V13.0.0 (2016-02)73GPP TS 32.321 version 13.0

43、.0 Release 135 Requirements 5.1 Overview The IRPManager (test conductor) must be able to initiate 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 m

44、ay be created for the purpose of monitoring and control of the test execution. During test 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.

45、 This gives rise to the following requirements for the test management function to be satisfied: 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 te

46、st results to the manager; the specification of a mechanism to log test results in 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 IRPA

47、gent. The IRPAgent must have at least one object instance capable of receiving these 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

48、 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 executio

49、n. Any other information useful for the test execution. In response to the test request the IRPAgent shall send a test request response to the IRPManager. For a successful test request this response shall contain the following information: A unique identifier for each test initiated by the test request. Information about the managed objects assisting to execute the test. For a failed test request the response shall contain the following information: Information about the reason for the failure. ETSI ETSI TS 13