1、 ETSI TS 132 150 V14.1.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Integration Reference Point (IRP) Concept and definitions (3GPP TS 32.150 version 14.1.0 Release 14) TECHNICAL SPECIFI
2、CATION ETSI ETSI TS 132 150 V14.1.0 (2017-04)13GPP TS 32.150 version 14.1.0 Release 14Reference RTS/TSGS-0532150ve10 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 Associat
3、ion 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 print v
4、ersions 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 on a
5、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.aspx If y
6、ou 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 and mi
7、crofilm 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 2017. All right
8、s 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 protected for the benefit of its Member
9、s GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 150 V14.1.0 (2017-04)23GPP TS 32.150 version 14.1.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The informat
10、ion 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“, which is available from the ETS
11、I 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 referenced in ETSI SR 000 314 (or the up
12、dates 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 specifications or reports using their 3GPP
13、 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 verbs terminology In the present d
14、ocument “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 allowed in ETSI deliverables exce
15、pt when used in direct citation. ETSI ETSI TS 132 150 V14.1.0 (2017-04)33GPP TS 32.150 version 14.1.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definiti
16、ons 6g33.2 Abbreviations . 7g34 Integration Reference Points (IRPs) . 8g34.1 Introduction 8g34.1.1 General 8g34.1.2 IRP Specifications Approach 9g34.2 Integration levels 10g34.2.1 Application integration . 10g34.3 Application of IRPs 11g34.4 Defining the IRPs . 12g34.5 Void 12g34.6 Mandatory, Option
17、al and Conditional qualifiers 13g34.7 System context for Interface IRPs 15g34.8 Object instance visibility 16g3Annex A (informative): Void . 17g3Annex B (normative): Void . 18g3Annex C (informative): Void . 19g3Annex D (informative): Void . 20g3Annex E (normative): Void . 21g3Annex F (informative):
18、Void . 22g3Annex G (normative): IOC Properties and Inheritance . 23g3G.1 Property 23g3G.2 Inheritance 24g3Annex H (normative): Interface Properties and Inheritance . 25g3H.1 Property 25g3H.2 Inheritance 25g3Annex I (normative): Entity (Interface, IOC and Attribute) Import 26g3Annex K (informative):
19、Change history . 27g3History 28g3ETSI ETSI TS 132 150 V14.1.0 (2017-04)43GPP TS 32.150 version 14.1.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG
20、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 for informat
21、ion; 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 been inco
22、rporated 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.150: Integration Reference Point (IRP) Concept and de
23、finitions TS 32.151: Integration Reference Point (IRP) Information Service (IS) template TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire TS 32.153 Integration Reference Point (IRP) technology specific templates TS 32.154 Backward and
24、Forward Compatibility (BFC); Concept and definitions TS 32.155 Telecommunication management; Requirements template TS 32.156 Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire TS 32.157 Telecommunication management; Integration Reference Point (IRP) Information Service (IS
25、) template ETSI ETSI TS 132 150 V14.1.0 (2017-04)53GPP TS 32.150 version 14.1.0 Release 141 Scope The present document provides the overall concept for all Integration Reference Point (IRP) specifications. Relevant IRP overview and high-level definitions are already provided in 3GPP TS 32.101 1 and
26、TS 32.102 2. IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference Point in subclause 3.1). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. -
27、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 version applies. In the case of a reference to a 3GPP document (includin
28、g 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 requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“.
29、3 3GPP TS 32.151: “Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template“. 4 Void. 5 ITU-T Recommendation M.3020 (05/2009): “TMN Interface Specification Methodology“. 6 OMG IDL Style Guide, ab/98-06-03, June 17, 1998. 7 3GPP TS 32.111-2: “Telecommunication
30、 management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service (IS)“. 8 3GPP TS 32.601: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements“. 9 3GPP TS 32.602: “Telecommunication management; Configurati
31、on Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. 10 3GPP TS 32.606: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions“. 11 3GPP TS 28.621: “Telecommunication management; Ge
32、neric Network Resource Model (NRM) Integration Reference Point (IRP); Requirements“. 12 3GPP TS 28.622: “Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP) ; Information Service (IS)“. 13 3GPP TS 28.623: “Telecommunication management; Generic Network
33、 Resource Model (NRM) Integration Reference Point (IRP) ; Solution Set (SS) definitions“. 14 3GPP TS 28.624: “Telecommunication management; State Management Data Definition Integration Reference Point (IRP) ; Requirements“. 15 3GPP TS 28.625: “Telecommunication management; State Management Data Defi
34、nition Integration Reference Point (IRP) ; Information Service (IS)“. ETSI ETSI TS 132 150 V14.1.0 (2017-04)63GPP TS 32.150 version 14.1.0 Release 1416 3GPP TS 28.626: “Telecommunication management; State Management Data Definition Integration Reference Point (IRP); Solution Set (SS) definitions“. 1
35、7 3GPP TS 32.107 Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) 18 3GPP TS 32.156 Fixed Mobile Convergence (FMC) Model Repertoire 19 3GPP TS 32.157 Integration Reference Point (IRP) Information Service (IS) template 20 3GPP TS 28.620 Fixed Mobile Convergence (FMC) Federate
36、d Network Information Model (FNIM) Umbrella Information Model (UIM) 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, 3GPP TS 32.151 3 , 3GPP TS 32.107 17, 3GPP TS 32.157 19, 3GPP TS 28.620
37、 20 and the following apply: Data Definition IRP: 3GPP publishes IRP specifications relating to commonly used data definitions that can be imported for use by Interface IRP and/or NRM IRP. This term represents all such specifications. NOTE 1: An example of a Data Definition IRP is the State Manageme
38、nt IRP (32.671 14, 32.672 15, 32.676 16). Information Object Class (IOC): information that can be passed/used in management interfaces and is modelled using the stereotype “Class“ in the UML meta-model. For a formal definition of Information Object Class and its structure of specification, see 3GPP
39、TS 32.1513. Integration Reference Point (IRP): An architectural concept that is described by a set of specifications for definition of a certain aspect of a management interface, comprising a Requirements specification, an Information Service specification, and one or more Solution Set specification
40、s. Interface IRP: 3GPP publishes a number of IRP specifications each of which is related to a set of operations and notifications for a specific telecom management domain such as alarm management, configuration management, etc. Interface IRPs also contain definitions of SupportIOCs. This term repres
41、ents all such specifications. NOTE 2: An example of an Interface IRP is the Basic CM IRP (the set of TSs 32.601 8, 32.602 9, 32.606 10). IRPAgent: Encapsulation of a well-defined subset of network (element) functions. It interacts with IRPManagers using one or more IRPs. From the IRPManagers perspec
42、tive, the IRPAgent behaviour is only visible via the IRP(s). Information Service (IS): description of the information related to the entities (either network resources or support objects) to be managed and the way that the information may be managed for a certain functional area (e.g. the Alarm IRP
43、Information Service in the fault management area). Information Services are defined for all IRPs. IRPManager: Modeling of a user of IRPAgent(s) which interacts directly with the IRPAgent(s) using IRP(s). Since the IRPManager represents an IRPAgent user, it gives a clear picture of what the IRPAgent
44、is supposed to do. From the IRPAgent perspective, the IRPManager behaviour is only visible via the IRP. Managed Object Class (MOC): information that can be passed/used in management interfaces in a similar way to IOC. NOTE 3: See subclause 7.3.4.3 of 5 on Guidelines for definitions of Managed Object
45、. Network Resource Model (NRM): description of Information Object Classes representing the manageable aspects of network resources. NOTE 4: Examples of network resources are RNC and NodeB. ETSI ETSI TS 132 150 V14.1.0 (2017-04)73GPP TS 32.150 version 14.1.0 Release 14NRM IRP: 3GPP publishes a number
46、 of IRP specifications each of which is related to a particular NRM (Network Resource Model) as defined in 3GPP TS 32.101 1. NRM IRPs do not define any operations or notifications. This term represents all such specifications. NOTE 5: In some NRM IRP titles, for historic reasons, they are named “net
47、work resources IRP“). NOTE 6: An example of an NRM IRP is the Generic NRM IRP (32.621 11, 32.622 12, 32.626 13). Solution Set (SS): mapping of the IRP Information Service (IS) defined entities (that are technology-agnostic) to technology specific termed entities. NOTE7: SS does not contain specifica
48、tion of the entities semantics which can be found in the corresponding IS.One IS can be mapped to one or several SSs. NOTE 8: Examples of an IS defined entity and technology specific termed entity are IOC and MOC respectively. SupportIOC: representation of a particular capability, introduced to mode
49、l a management service. NOTE 9: As an example of SupportIOC, in the Alarm IRP Information Service 59 there are the AlarmInformation and AlarmList IOCs. NOTE 10: See Annex F of 18 for information about the difference between IOC and SupportIOC. Yyy IRP: For a specific Interface IRP such as the Basic CM IRP, when the letters Yyy are replaced by the specific key words naming that IRP (in the given example the Yyy is replaced by “Basic CM”), this term represents all specifications that are p
