ETSI TS 132 361-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Entry Point (EP).pdf

1、 ETSI TS 132 361 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements (3GPP TS 32.361 version 14.0.0 Release 14) TECHNICAL

2、SPECIFICATION ETSI ETSI TS 132 361 V14.0.0 (2017-04)13GPP TS 32.361 version 14.0.0 Release 14Reference RTS/TSGS-0532361ve00 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 A

3、ssociation 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

4、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) version kep

5、t 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/TB/ETSIDeliverableStatus.as

6、px 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 photocopying

7、 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 2017. Al

8、l 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 protected for the benefit of its

9、 Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 361 V14.0.0 (2017-04)23GPP TS 32.361 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The i

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

11、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 referenced in ETSI SR 000 314 (or

12、 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 specifications or reports using the

13、ir 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 verbs terminology In the pr

14、esent 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 allowed in ETSI deliverabl

15、es except when used in direct citation. ETSI ETSI TS 132 361 V14.0.0 (2017-04)33GPP TS 32.361 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 D

16、efinitions 5g33.2 Abbreviations . 6g34 Entry Point concept and requirements 6g35 Itf-N interface . 8g35.1 Entry point 8g35.1.1 Access point 8g35.1.2 Version negotiation . 8g35.1.3 Changes indication 8g35.1.4 Security . 8g3Annex A (informative): EPIRP knowledge 9g3Annex B (informative): Change histor

17、y . 10g3History 11g3ETSI ETSI TS 132 361 V14.0.0 (2017-04)43GPP TS 32.361 version 14.0.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 and may chang

18、e 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 information; 2 presen

19、ted 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 incorporated in t

20、he 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: 32.361: “Entry Point (EP) Integration Reference Point (IRP): Requirement

21、s“. 32.362: “Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)“. 32.366: “Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions“. The present document is part of a set of technical specifications defining the Telecommunication Management (TM) of

22、 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 general the Network Manager (NM) and the managed system (agent), which is e

23、ither 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 manager may perform on this information and the notifications that are sent

24、from the agent to the manager. EPIRP is one of these IRPs with special function. It is difficult for an NM to discover all IRPs in the environment where there are several managed systems and/or if there are multiple IRPs related to each managed system. This Entry Point is proposed to provide a conve

25、nient mechanism for NM to discover the managed systems and their related IRPs. ETSI ETSI TS 132 361 V14.0.0 (2017-04)53GPP TS 32.361 version 14.0.0 Release 141 Scope The present document describes the requirements of the EPIRP. 2 References The following documents contain provisions which, through r

26、eference 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 3GPP TS 32.111-1: “Telecommunication management; Fault management; Part 1: 3G fault management requirements“. 4 3GPP TS 32.601: “ Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Poin

29、t (IRP): Requirements“. 5 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following

30、terms and definitions apply: Entry Point (EP): access point between NM and the managed systems and provides the way for NM to discover the References of IRPs in the managed systems Reference: defines the IRP network management service access point. The IRPManagers connect to this IRP Reference in or

31、der to request and obtain the network management services (provided by that IRP). The implementation of IRP Reference is technology dependent. For example, in CMIP, this is the address of the CMIP IRPAgent and application context of the CMIP IRP. In CORBA, this is the IOR of the IRP contained by the

32、 IRPAgent. Version negotiation: when the managed system supports more than one IRP versions, there is a mechanism for NM to select the needed IRP version, and invoke the most appropriate management operations ETSI ETSI TS 132 361 V14.0.0 (2017-04)63GPP TS 32.361 version 14.0.0 Release 143.2 Abbrevia

33、tions For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name EP Entry PointEPIRP Entry Point IRP EM Element ManagerEP Entry Point IOC Information Object Class IOR (CORBA) Interoper

34、able Object Reference IRP Integration Reference Point NE Network Element NM Network ManagerNRM Network Resource Model PM Performance Management4 Entry Point concept and requirements In the 3GPP Release 5 specifications and earlier Releases, the IRPs (such as the Basic CM IRP Requirements in 3GPP TS

35、32.601 4, the fault management requirements in 3GPP TS 32.111-1 3, etc.) are defined for specific management domains and are all published. 3GPP specifications do not provide standard mechanism for NM to discover the References of the IRPs in the managed systems. The discovery is a vendor-specific m

36、atter. In a large network, multiple IRPs, providing different network management domains services exist. Multiple IRPs providing the same network management services (e.g. fault management) but of different management scope may exist (e.g. one AlarmIRP managing the eastern region while another Alarm

37、IRP manages the western region). Its difficult and fallible for an NM to discover all of them. The matter is further complicated in a multi-vendor environment where each vendor provides different way for NM to discover the References of its IRPAgent and related IRPs. A management service, allowing t

38、he NM to discover the References, in a standard way would eliminate the NMs difficulties mentioned above. The Entry Point is the name of such management service. Entry Point provides the following: 1) It allows NM to discover outline information of IRPs, including the DN of IRPs and the supported IR

39、PVersions and their scope of management (e.g. the set of network resources that it is responsible for) in the managed systems. 2) It supports NM to obtain the References of the IRPs of specific IRPVersion by means of the IRPManager inputting the DN of the IRP which supports the IRPVersion number it

40、needs. Entry Point allows NM to indicate to the managed system the References it will not use again. Whether the managed system should release them or not is outside the scope of this specification. A notification shall be supported for keeping IRPManager timely informed about the changes of Entry P

41、oint contents, e.g. latest IRPAgent register information or latest IRPAgent deregister information or their scope of management stored in EPIRP at run time. The EPIRP provides the References of various IRPs to the IRPManager at run time. That interaction, to be standardised by this IRP specification

42、, is shown as the arrow from EPIRP to IRPManager in the Figure 1. Using the provided Reference, say the Reference to PMIRP, the IRPManager invokes operations to access the PM domain specific management services. The context diagram figure 1 does not show the IRPAgent(s) and their containment relatio

43、ns with IRPs. There can be a single or multiple IRPAgents. Each IRPAgent can contain one or more IRPs. An EPIRP is contained by an IRPAgent. This containing IRPAgent may or may not contain other instances of other IRPs such as AlarmIRP. This is the choice of the vendor producing such product. The IR

44、PAgent containment relation, with respect to other IOCs such as SubNetwork, is defined by the Generic NRM IRP in 3GPP TS 32.622 5. This containment relation has no relation to the EPIRP knowledge regarding IRP ETSI ETSI TS 132 361 V14.0.0 (2017-04)73GPP TS 32.361 version 14.0.0 Release 14References.

45、 To say it in another way, the EPIRP knowledge about IRP References has no relationship to its Distinguished Name. An EPIRP, named under one IRPAgent instance can have knowledge of IRP References of IRPs named under other IRPAgent instances. An EPIRP, named under one particular SubNetwork instance c

46、an have knowledge of IRP References of IRPs under other SubNetwork instances. This is the choice of the vendor producing such product. See annex A for example figures to show EPIRP knowledge. All the IRP References provided by one vendors product should be found in at least in one of the EPIRPs impl

47、emented by that vendor, but not necessarily all IRP References in one EPIRP. Each vendor should minimize the number of EPIRPs for the support of all their IRP References. How EPIRP is made aware of IRP References are outside the scope of standardization. NOTE: The * depicts the IRP Reference returne

48、d by EPIRP. See Reference definition. Figure 1: EPIRP context EPIRP IRPManager NM AlarmIRP Performance Management IRP Configuration (Basic, Bulk) Management IRP Itf-N * ETSI ETSI TS 132 361 V14.0.0 (2017-04)83GPP TS 32.361 version 14.0.0 Release 145 Itf-N interface 5.1 Entry point 5.1.1 Access point

49、 Before IRPManager can interact with an IRP to obtain network management services, say AlarmIRP, it must know the IRPs Reference. Without the EPIRP, the IRPManager shall get information about these IRP References in a vendor-specific way. With the EPIRP, the IRPManager can discover these IRP References using the EPIRP defined protocol. Before the IRPManager can interact with the EPIRP, it must know the EPIRP Reference. How the IRPManager acquire this knowledge is outside the scope of this specification. 5.1.2 Version negotiation The version of IRPs m