1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommCommuniIntegratioInfor(3GPP TS 32.3TECHNICAL SPECIFICATION132 352 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; nication Surveillance (CS) tion Reference Point (IRP); ormation Service (IS) .35
2、2 version 13.0.0 Release 1316-02) hase 2+); (UMTS); 13) ETSI ETSI TS 132 352 V13.0.0 (2016-02)13GPP TS 32.352 version 13.0.0 Release 13Reference RTS/TSGS-0532352vd00 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
3、16 Siret N 348 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 pr
4、int. 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
5、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:/po
6、rtal.etsi.org/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 me
7、chanical, 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 Telecommunicati
8、ons Standards 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
9、 logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 352 V13.0.0 (2016-02)23GPP TS 32.352 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
10、 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. La
11、test 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
12、 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
13、 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“,
14、“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 d
15、irect citation. ETSI ETSI TS 132 352 V13.0.0 (2016-02)33GPP TS 32.352 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbrev
16、iations . 7g34 System Overview . 7g34.1 System Context 7g34.2 Compliance rules 7g35 Information Object Classes (IOCs) 8g35.1 Information entities imported and local labels . 8g35.2 Class diagram . 8g35.2.1 Attributes and relationships 8g35.2.2 Inheritance 9g35.3 IOCs definition . 9g35.3.1 CSIRP . 9g
17、35.3.1.1 Definition 9g35.3.1.2 Attributes . 9g35.3.1.3 Notification . 9g35.4 Information attributes definition . 9g35.4.1 Definitions and legal values 9g36 Interface definition . 10g36.1 Class diagram representing interfaces 10g36.2 Generic rules 10g36.3 Interface CSIRPOperations_1 (M) . 11g36.3.1 O
18、peration getHeartbeatPeriod (M) . 11g36.3.1.1 Definition 11g36.3.1.2 Input parameters 11g36.3.1.3 Output parameters . 11g36.3.1.4 Pre-condition . 11g36.3.1.5 Post-condition . 11g36.3.1.6 Exceptions . 11g36.3.2 Operation triggerHeartbeat (M) 11g36.3.2.1 Definition 11g36.3.2.2 Input parameters 11g36.3
19、.2.3 Output parameters . 12g36.3.2.4 Pre-condition . 12g36.3.2.5 Post-condition . 12g36.3.2.6 Exceptions . 12g36.4 Interface CSIRPOperations_2 (O) 13g36.4.1 Operation setHeartbeatPeriod (M) . 13g36.4.1.1 Definition 13g36.4.1.2 Input parameters 13g36.4.1.3 Output parameters . 13g36.4.1.4 Pre-conditio
20、n . 13g36.4.1.5 Post-condition . 13g36.4.1.6 Exceptions . 13g3ETSI ETSI TS 132 352 V13.0.0 (2016-02)43GPP TS 32.352 version 13.0.0 Release 136.5 Interface CSIRPNotifications (M) 14g36.5.1 Notification notifyHeartbeat (M) 14g36.5.1.1 Definition 14g36.5.1.2 Input parameters 14g36.5.1.3 Triggering Even
21、t . 14g36.5.1.3.1 From-state 14g36.5.1.3.2 To-state 14g3Annex A (normative): IRPAgent behaviour regarding the sending of heartbeat notification 15g3Annex B (informative): Identification of a failed communication path 16g3B.1 Background 16g3B.2 Notification IRPAgent Internal Configuration . 16g3B.3 T
22、he failed communication paths identification process . 17g3Annex C (informative): Change history . 19g3History 20g3ETSI ETSI TS 132 352 V13.0.0 (2016-02)53GPP TS 32.352 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). T
23、he 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 a
24、s 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
25、, 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 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management
26、, as identified below: TS 32.351: “Communication Surveillance (CS) Integration 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)
27、; Solution Set (SS) definitions“. The present document is part of a TS-family 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)
28、 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) defining the information in the agent that i
29、s 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. Communication Surveillance IRP (CSIRP) is one of these IRPs with special function. To ensure the availability and reliability of the managemen
30、t, an automatic surveillance of the communication between NM and the managed system are required. CSIRP is defined as a capability to achieve this goal. ETSI ETSI TS 132 352 V13.0.0 (2016-02)63GPP TS 32.352 version 13.0.0 Release 131 Scope The present document defines the Information Service (IS) pa
31、rt of the Communication Surveillance IRP (CSIRP). It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of Information Object Classes (IOCs) and the interactions by means of operations and notifica
32、tions. The present document does not specify the syntax (encoding) of the information. 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, edit
33、ion 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
34、 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 Void 4 3GPP TS 32.351: “Telecommunication management; Communication Surve
35、illance (CS) Integration Reference Point (IRP): Requirements“. 5 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 6 3GPP TS 32.312: “Telecommunication management; Generic Integrat
36、ion Reference Point (IRP) management: Information Service (IS)“. 7 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements“. 8 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Po
37、int (IRP): Information Service (IS)“. 9 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.101 1, 3GPP TS
38、32.102 2, 3GPP TS 32.351 4 and the following apply. IRPVersion: See 3GPP TS 32.311 7. ETSI ETSI TS 132 352 V13.0.0 (2016-02)73GPP TS 32.352 version 13.0.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CMIP Common Management Information Proto
39、col CORBA Common Object Request Broker Architecture CS Communication Surveillance CSIRP Communication Surveillance Integration Reference Point DN Distinguished Name EM Element ManagerIRP Integration Reference Point IOC Information Object Class IS Information Service NE Network ElementNM Network Mana
40、ger NRM Network Resource Model 4 System Overview 4.1 System Context The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 9 subclause 4.7. In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below. EM IRPAgent NEs Noti
41、ficationIRP NM IRPManager Itf-N IRPAgent CSIRP Figure 4.1: System Context A CSIRP NotificationIRP NM IRPAgent NE IRPManager Itf-N Figure 4.2: System Context B 4.2 Compliance rules For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations, notif
42、ications and parameters (of operations and notifications) please refer to 3GPP TS 32.102 2. ETSI ETSI TS 132 352 V13.0.0 (2016-02)83GPP TS 32.352 version 13.0.0 Release 135 Information Object Classes (IOCs) 5.1 Information entities imported and local labels Label reference Local label 3GPP TS 32.622
43、 5, information object class, Top Top 3GPP TS 32.622 5, information object class, IRPAgent IRPAgent 3GPP TS 32.622 5, information attribute, systemDN systemDN 3GPP TS 32.622 5, information object class, GenericIRP GenericIRP 3GPP TS 32.312 6, information object class, ManagedGenericIRP ManagedGeneri
44、cIRP 5.2 Class diagram 5.2.1 Attributes and relationships This clause introduces the set of Information Object Classes (IOCs) that encapsulate information within the IRPAgent. The intention is to identify the information required for the CSIRP implementation of its operations. This clause provides t
45、he overview of all support object classes in UML. Subsequent clauses provide more detailed specification of various aspects of these support object classes. CSIRP+ heartbeatPeriod- countDownTimerIRPAgent01ETSI ETSI TS 132 352 V13.0.0 (2016-02)93GPP TS 32.352 version 13.0.0 Release 135.2.2 Inheritanc
46、e 5.3 IOCs definition 5.3.1 CSIRP 5.3.1.1 Definition This information object represents a capability that can emit heartbeat notification periodically. The emission frequency is controlled by an attribute named heartbeatPeriod. The notifications are submitted to NotificationIRP that will distribute
47、them to NtfSubscriber(s) according to their related NtfSubscription(s). In addition, the CSIRP provide a method for IRPManager to trigger a heartbeat notification at any time. The IOC CSIRP inherits from the IOC ManagedGenericIRP specified in 3GPP TS 32.312 6. There shall be at most one CSIRP instan
48、ce per IRPAgent instance. The heartbeat notifications are submitted via established notification subscriptions, to IRPManagers. The distribution of notifications is subject to the status of the related established notification subscription. For example, the IRPManager will not be able to receive the
49、 heartbeat notification if the notification subscription state is suspended or if the notification filter is in effect that discards heartbeat notification. See Annex A for more information. 5.3.1.2 Attributes Attribute name Visibility Support Qualifier Read Qualifier Write Qualifier heartbeatPeriod + M M M countDownTimer - M - - 5.3.1.3 Notification Name Qualifier Notes notifyHeartbeat M See clause 6.5.1. 5.4 Information attributes definition This clause defines the semantics of the Attributes used in Information Object Cl
