1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommCommuniIntegratio(3GPP TS 32.3TECHNICAL SPECIFICATION132 351 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; nication Surveillance (CS) tion Reference Point (IRP); Requirements .351 version 13.0
2、.0 Release 1316-02) hase 2+); (UMTS); 13) ETSI ETSI TS 132 351 V13.0.0 (2016-02)13GPP TS 32.351 version 13.0.0 Release 13Reference RTS/TSGS-0532351vd00 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
3、 623 562 00017 - 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 conte
4、nt 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 Docum
5、ent 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/
6、tb/status/status.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, incl
7、uding 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
8、Institute 2016. 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 Trad
9、e Marks registered and owned by the GSM Association. ETSI ETSI TS 132 351 V13.0.0 (2016-02)23GPP TS 32.351 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 essenti
10、al 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 a
11、re 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) w
12、hich 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
13、 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “
14、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
15、. ETSI ETSI TS 132 351 V13.0.0 (2016-02)33GPP TS 32.351 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34
16、 Communication Surveillance (CS) requirements . 6g34.1 General . 6g34.2 CS Management features 7g34.2.1 CS features from NM perspective . 7g34.2.1.1 Query CS information . 7g34.2.1.2 Modify CS information . 7g34.2.1.3 Emission of CS notifications . 7g34.2.1.4 Trigger CS notification . 7g3Annex A (in
17、formative): Change history . 8g3History 9g3ETSI ETSI TS 132 351 V13.0.0 (2016-02)43GPP TS 32.351 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 subject to continuing work withi
18、n 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 fo
19、r 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
20、 been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: TS 32.351: “Communication Surveillance (CS) Integ
21、ration Reference Point (IRP); Requirements“; TS 32.352: “Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS)“; TS 32.356: “Communication Surveillance (CS) Integration Reference Point (IRP); Solution Set (SS) defintions“. The present document is part of a set o
22、f technical specifications defining the Telecommunication Management (TM) of 3G systems. The TM principles are described in 3GPP TS 32.101 1. The TM architecture is described in 3GPP TS 32.102 2. The other specifications define the interface (Itf-N) between the managing system (manager), which is in
23、 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) defining the information in the agent that is visible for the manager, the operations that the
24、manager may perform on this information and the notifications that are sent from the agent to the manager. To ensure the availability and reliability of the management, an automatic surveillance of the communication between NM and the managed system are required. Communication Surveillance IRP (CSIR
25、P) is defined as a capability to achieve this goal. ETSI ETSI TS 132 351 V13.0.0 (2016-02)53GPP TS 32.351 version 13.0.0 Release 131 Scope The present document describes the requirements of the Communication Surveillance IRP (CSIRP). 2 References The following documents contain provisions which, thr
26、ough 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
27、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 and high level require
28、ments“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 ITU-T Recommendation X.734: “Information technology - Open Systems Interconnection - Systems Management: Event report management function“. 4 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notifi
29、cation Integration Reference Point (IRP): Information Service (IS)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2 and the following apply: Communication Surveillance (CS): capability to
30、 monitor the communication between NM and managed system and to discover their breaks as early as possible Communication Link: facility, which supports the communication between NM and IRPAgent(s) in managed system, including all the resources required for this communication Notification Distributio
31、n Service: in managed system, provides notification controlling and forwarding functions ITU-T Recommendation X.734 3 Element Manager (EM): See 3GPP TS 32.101 1. IRPAgent: See 3GPP TS 32.102 2. IRPManager: See 3GPP TS 32.102 2. Network Manager (NM): See 3GPP TS 32.101 1. managed system: provides a p
32、ackage of IRPs, these IRPs include Notification IRP (notification distribution service) and other IRPs ETSI ETSI TS 132 351 V13.0.0 (2016-02)63GPP TS 32.351 version 13.0.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CS Communication Survei
33、llance CSIRP Communication Surveillance Integration Reference Point EM Element Manager IRP Integration Reference Point NE Network Element NM Network Manager4 Communication Surveillance (CS) requirements 4.1 General The communication between NM and Managed System (NE or EM) shall be monitored, and li
34、nk breaks between NM and Managed System (NE or EM) shall be discovered by NM as early as possible. In the CS context, the NM contains one or more IRPManagers. Figure 1 illustrates the major components in the CS context. NM IRPManager Managed System Notification IRP link-a-1(s) link-a-2 Itf-N other I
35、RP(s) link-b Notification distribution service Figure 1: Communication surveillance context Referring to figure 1, the scope of CS involves the monitoring of the communication between NM entity and EM (or NE) entity at application level. At this application level, there are three parts involved, whi
36、ch are NM, Managed System and the Communication Link(s) between them. From NM side, to monitor the communication, is to know whether the other entity and/or the Communication Link(s) between them are functioning correctly. The behaviour of the IRPManager, after detection of communication failure, is
37、 outside the scope of this standardization. NM can detect whether link-a-1 or link-a-2 is functioning correctly by observing the operation responses. (e.g. invoking getIRPVersions operation against one xxxIRP.) The link-a-1 and link-a-2 are links used by the IRPManager and the various xxxIRPs to exe
38、cute 3GPP Interface IRP defined operations (i.e., operation request and direct response to that request). The receipt of a response corresponding to a managers operations via link-a-1 or link-a-2 implies that the particular link has correctly conveyed the request and delivered the response at the ex
39、act point in time the response was received. The Managed System shall provide a service allowing NM to detect promptly whether link-b (including Notification Distribution Service) and NotificationIRP defined in 3GPP TS 32.302 4 are functioning correctly regarding notification sending. The detection
40、of a heartbeat via link-b implies that the notification distribution service is able to send notifications, and that the link-b is able to deliver notifications at exactly that point in time. ETSI ETSI TS 132 351 V13.0.0 (2016-02)73GPP TS 32.351 version 13.0.0 Release 13For detection of link-a-1 and
41、 link-a-2 failure, no solution is required as existing capability are sufficient. The features to detect the correct functioning of link-b and notification distribution service are described in subclause 4.2. 4.2 CS Management features The Itf-N between IRPManagers (of the NM) and managed system can
42、 include the following CS Management features. 4.2.1 CS features from NM perspective 4.2.1.1 Query CS information This feature allows the NM to query the CS information from the managed system. NM can query information of CS, including: - Frequency of emission of CS notifications. 4.2.1.2 Modify CS
43、information This feature allows the NM to modify the CS information from the managed system, including: - Frequency of emission of CS notifications. - Starting and stopping of Communication Surveillance notifications. 4.2.1.3 Emission of CS notifications This feature allows the managed system to sen
44、d CS notifications to the NM. Managed system will emit CS notifications to NM according to the specified frequency. 4.2.1.4 Trigger CS notification The frequency of emission of CS notifications may not be short for payload consideration. In case NM suspects the link breaks before receiving next CS n
45、otifications and needs to make decision at once, this complementary feature allows NM to ask managed system to send CS notifications to the triggering NM immediately. The triggered CS notification should be emitted only to the triggering NM. In this CS notification, additional description will be gi
46、ven to help NM distinguish it from spontaneous (or scheduled) CS notifications described in subclause 4.2.1.3. This feature has no impact on the spontaneous (or scheduled) CS heartbeat notification feature. ETSI ETSI TS 132 351 V13.0.0 (2016-02)83GPP TS 32.351 version 13.0.0 Release 13Annex A (infor
47、mative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Dec 2003 S_22 SP-030632 - - Submitted to TSG SA#22 for Information 1.0.0 Mar 2004 S_23 SP-040125 - - Submitted to TSG SA#23 for Approval 2.0.0 6.0.0 Jun 2007 SA_36 - - - Automatic upgrade to Rel-7 (no CR) at fr
48、eeze of Rel-7. Deleted reference to CMIP SS, discontinued from R7 onwards. 6.0.0 7.0.0 Jul 2007 Correction to history table. 7.0.0 7.0.1 Dec 2008 SA_42 - - - Upgrade to Release 8 7.0.1 8.0.0 Dec 2009 - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 Mar 2011 - - - - Update to Rel-10 version (MCC) 9.
49、0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-10 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 ETSI ETSI TS 132 351 V13.0.0 (2016-02)93GPP TS 32.351 version 13.0.0 Release 13History Document history V13.0.0 February 2016 Publication
