1、 ETSI TS 132 352 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.352 version 14
2、.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 352 V14.0.0 (2017-04)13GPP TS 32.352 version 14.0.0 Release 14Reference RTS/TSGS-0532352ve00 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 conten
4、t 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 Docume
5、nt 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 https:/portal.etsi.org/
6、TB/ETSIDeliverableStatus.aspx 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 mechani
7、cal, 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 Telecommunications S
8、tandards Institute 2017. 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. oneM2M logo is prote
9、cted for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 352 V14.0.0 (2017-04)23GPP TS 32.352 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have b
10、een 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: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards
11、“, 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 investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not refere
12、nced 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 (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specific
13、ations 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 reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal
14、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 clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT
15、 allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 352 V14.0.0 (2017-04)33GPP TS 32.352 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions a
16、nd abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 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 Inher
17、itance 9g35.3 IOCs definition . 9g35.3.1 CSIRP . 9g35.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 10
18、g36.3 Interface CSIRPOperations_1 (M) . 11g36.3.1 Operation 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.
19、2.1 Definition 11g36.3.2.2 Input parameters 11g36.3.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
20、.4.1.3 Output parameters . 13g36.4.1.4 Pre-condition . 13g36.4.1.5 Post-condition . 13g36.4.1.6 Exceptions . 13g36.5 Interface CSIRPNotifications (M) 14g3ETSI ETSI TS 132 352 V14.0.0 (2017-04)43GPP TS 32.352 version 14.0.0 Release 146.5.1 Notification notifyHeartbeat (M) 14g36.5.1.1 Definition 14g36
21、.5.1.2 Input parameters 14g36.5.1.3 Triggering Event . 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 Notif
22、ication IRPAgent Internal Configuration . 16g3B.3 The failed communication paths identification process . 17g3Annex C (informative): Change history . 19g3History 20g3ETSI ETSI TS 132 352 V14.0.0 (2017-04)53GPP TS 32.352 version 14.0.0 Release 14Foreword This Technical Specification has been produced
23、 by the 3rdGeneration Partnership Project (3GPP). 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
24、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 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
25、, i.e. technical enhancements, corrections, updates, 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 Servic
26、es and System Aspects; Telecommunication management, 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
27、Surveillance (CS) Integration Reference Point (IRP); 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. Th
28、e other 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
29、(IRPs) 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. Communication Surveillance IRP (CSIRP) is one of these IRPs with special function. To ensur
30、e the availability and reliability of the management, 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 V14.0.0 (2017-04)63GPP TS 32.352 version 14.0.0 Release 141 Scope The prese
31、nt document defines the Information Service (IS) part 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 t
32、he interactions by means of operations and notifications. 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 eit
33、her 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 GSM document),
34、 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 Void 4 3GPP TS 3
35、2.351: “Telecommunication management; Communication Surveillance (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 T
36、S 32.312: “Telecommunication management; Generic Integration 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; Configurati
37、on Management (CM); Notification Integration Reference Point (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 te
38、rms and definitions defined in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.351 4 and the following apply. IRPVersion: See 3GPP TS 32.311 7. ETSI ETSI TS 132 352 V14.0.0 (2017-04)73GPP TS 32.352 version 14.0.0 Release 143.2 Abbreviations For the purposes of the present document, the following abbr
39、eviations apply: CMIP Common Management Information Protocol 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
40、 IS Information Service NE Network ElementNM Network Manager 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
41、 is shown in the two diagrams below. EM IRPAgent NEs NotificationIRP 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 qualifie
42、rs (Mandatory/Optional/Conditional) for operations, notifications and parameters (of operations and notifications) please refer to 3GPP TS 32.102 2. ETSI ETSI TS 132 352 V14.0.0 (2017-04)83GPP TS 32.352 version 14.0.0 Release 145 Information Object Classes (IOCs) 5.1 Information entities imported an
43、d local labels Label reference Local label 3GPP TS 32.622 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,
44、information object class, ManagedGenericIRP ManagedGenericIRP 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
45、 implementation of its operations. This clause provides the 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 V14.0.0 (2017-04)
46、93GPP TS 32.352 version 14.0.0 Release 145.2.2 Inheritance 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 notificatio
47、ns are submitted to NotificationIRP that will distribute 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
48、3GPP TS 32.312 6. There shall be at most one CSIRP instance 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. Fo
49、r example, the IRPManager will not be able to receive the 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 semant
