ETSI TS 132 154-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Backward and For.pdf

《ETSI TS 132 154-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Backward and For.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 154-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Backward and For.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 154 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions (3GPP TS 32.154 version 15.0.0 Release 15) TECHNICAL

2、 SPECIFICATION ETSI ETSI TS 132 154 V15.0.0 (2018-07)13GPP TS 32.154 version 15.0.0 Release 15Reference RTS/TSGS-0532154vf00 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

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

5、pt 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.a

6、spx 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 photocopyin

7、g 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UM

8、TSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademark

9、s registered and owned by the GSM Association. ETSI ETSI TS 132 154 V15.0.0 (2018-07)23GPP TS 32.154 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables 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. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the proper

13、ty of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has

14、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 GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross ref

15、erence 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“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in

16、 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. ETSI ETSI TS 132 154 V15.0.0 (2018-07)33GPP TS 32.154 version 15.0.0 Release 15Contents Intellectual Property Rights

17、 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 BC between 3GPP TS 32-series specifications 6g34.1 Prerequisite . 6g34.2 Rules . 7g35 BC context 8g35.1 General . 8g3

18、5.2 IRP level . 9g35.3 IRPAgent level . 10g36 BC Recommendations 12g36.1 Requirement . 12g36.2 IS-level . 12g36.3 SS-level 12g36.3.1 CORBA 12g36.3.2 Void 12g36.3.3 File format description XML 12g36.3.4 File format description ASN.1 12g36.3.5 SOAP 12g3Annex A (informative): BC and Conformance Tests 1

19、3g3Annex B (informative): Change history 14g3History 15g3ETSI ETSI TS 132 154 V15.0.0 (2018-07)43GPP TS 32.154 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continu

20、ing 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 as follows: Version x.y.z where: x the first digit: 1 prese

21、nted 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, etc. z the third digit is incremented when editorial onl

22、y changes have been incorporated in the document. Introduction The Itf-N partitions two groups of interacting entities called IRPManager(s) and IRPAgent(s). The interactions between an IRPManager and IRPAgent are specified by the set of IRP specifications the IRPAgent supports, and which the IRPMana

23、ger uses. Each YyyIRP (where “Yyy“ stands for Alarm, BasicCM, etc.) permits a manager to, via getIRPVersion, inspect its supported IRPVersion(s). Each such IRPVersion uniquely identifies one supported Interface IRP SS. Each YyyIRP may also permit an IRPManager to, via getNRMIRPVersions, inspect its

24、supported NRM IRPVersion(s). Each such IRPVersion uniquely identifies one supported NRM IRP SS. The 3GPP IRP specifications are expected to evolve. For example, 3GPP Release 6 specifications include more or modified features compared to the corresponding set in Release 5. An IRPManager and IRPAgent,

25、 with implementations conformant to the same IRP specification (at the same IRPVersion(s) will be able to communicate. However, an upgrade of the IRPVersion, if not performed by both IRPAgent and IRPManager, can result in inter-working failure if Backward Compatibility (BC) issues are not addressed.

26、 The present document is applicable/relevant to a system context of a group of interacting IRPManagers and IRPAgents where some members are using one IRPVersion while others are using an upgraded IRPVersion. ETSI ETSI TS 132 154 V15.0.0 (2018-07)53GPP TS 32.154 version 15.0.0 Release 151 Scope The p

27、resent document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step. The business case for supporting such group, as described above, is complex. It may not relate t

28、o the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific. Clause 4 sp

29、ecifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable. Editors Note: The “forward compatability” part is FFS. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present d

30、ocument. - References are either specific (identified by date of publication and/or edition number or version number) 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 docum

31、ent (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 requirements“. 2 3GPP TS 32.102: “Telecommunication management; Ar

32、chitecture“. 3 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 4 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 3 Definitions and abbrev

33、iations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Element Manager (EM): See 3GPP TS 32.101 1. IRPAgent: See 3GPP TS 32.102 2. IRPManager: See 3GPP TS 32.102 2. IRPVersion: See “IRP document version number string“ or “IRPVersion“ in 3GPP TS 3

34、2.311 4 clause 3.1. Network Manager (NM): See 3GPP TS 32.101 1. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One BC Backward Compatible or Backward Compatibility CMIP Common Management Information Protocol ETSI ETSI TS

35、132 154 V15.0.0 (2018-07)63GPP TS 32.154 version 15.0.0 Release 15CORBA Common Object Request Broker Architecture EM Element Manager IS Information ServiceIRP Integration Reference Point NE Network Element NM Network ManagerNRM Network Resource Model VSE Vendor Specific Extension (to 3GPP IRP specif

36、ication) SS Solution Set XML eXtensible Markup Language 4 BC between 3GPP TS 32-series specifications 4.1 Prerequisite The words old and new, when qualifying an IRPVersion, refer to a single Interface IRPVersion of the same kind, e.g. Alarm IRP. They also refer to NRM IRPVersion of the same kind, e.

37、g. Core NRM. The new refers to a later release compared to the old. The words old and new, when qualifying an IRPManager, refer to an entity that is using the old or the new (Interface or NRM) IRPVersion. The words old and new, when qualifying an IRPAgent, refer to an entity that contains an IRP tha

38、t is supporting the old or the new (Interface or NRM) IRPVersion. In majority cases, an IRPAgent instance contains multiple IRPs, each of which is using a particular Interface IRPVersion. In these cases, each Recommendation statement should be repeated to cover all IRPs involved. The Recommendations

39、 do not imply that equipment vendors shall always supply their new IRPAgents in compliance to the solutions satisfying the Recommendations. The Recommendations simply identify the expected behaviours of a new system when it, claiming BC, interacts with an old system. Whether or not an IRPAgent shoul

40、d satisfy the Recommendations is a decision of the equipment vendor/supplier. The Recommendations do not imply that the next release of 3GPP Interface IRP or NRM IRP specification must be BC (to the older one). Whether or not a new release of an Interface IRP or NRM IRP should be BC to its older ver

41、sion is a decision of the 3GPP specification author, on a case-by-case basis. ETSI ETSI TS 132 154 V15.0.0 (2018-07)73GPP TS 32.154 version 15.0.0 Release 154.2 Rules REC-1 An old IRPManager inter-operates with an old IRPAgent-A and a new IRPAgent-B. The interaction shall be successful in that the I

42、RPManager can obtain the network management services (capabilities and features) defined by the old IRPVersion from both IRPAgents. The IRPManager needs not have knowledge of new network management services defined by the new IRPVersion. REC-2 A new IRPManager inter-operates with a new IRPAgent-A an

43、d an old IRPAgent-B. The interaction shall be successful in that the IRPManager can obtain the network management services defined by (a) the new IRPVersion from IRPAgent-A and (b) the old IRPVersion from IRPAgent-B. NOTE: If the next minor and/or major release of 3GPP Interface IRP or NRM IRP speci

44、fication is BC (to the older one), one could reduce or eliminate the difficult coordination task to introduce IRPVersion upgrades in a large management domain containing multiple IRPManagers and IRPAgents. It can be more cost-effective if IRPVersion upgrades to individual entity (i.e. IRPManager and

45、 IRPAgent) are done at different times. ETSI ETSI TS 132 154 V15.0.0 (2018-07)83GPP TS 32.154 version 15.0.0 Release 155 BC context 5.1 General This clause defines the context under which the requirements specified in the present document are applicable. The word old qualifies the related entity (i.

46、e. the AlarmIRP of an IRPAgent instance or Alarm IRPManager) that is using an older 3GPP IRPVersion (called old version). The word new qualifies the related entity that is using a newer (upgraded) 3GPP IRPVersion. EXAMPLE: A hypothetical 3GPP TS 32.123 V6.0.0 is considered the old version with refer

47、ence to 3GPP TS 32.123 V6.1.0. The two versions in question can belong to the same or different major releases (e.g. Rel-5 or Rel-6). The box labelled EM in figure 5.1 conveys the same idea as the box of the same label in the System Context-A of other IRP specifications such as Alarm IRP IS 3GPP TS

48、32.111-2 3. One or all EM-labelled boxes of figure 5.1 can be interchanged with the NE-labelled box (see System Context-B of other IRP specifications such as Alarm IRP IS 3GPP TS 32.111-2 3). The NE entities are not shown in order to make the figure easier to read. NewIRPAgentItf-NEMOldIRPManagerNMN

49、ewIRPManagerNMOldIRPAgentEMFigure 5.1: Overall BC System Context In general, an IRPAgent instance may contain several Interface YyyIRP instances and associated supporting Yyy NRM IRPs (where one IRP can be for example Alarm IRP, Test Management IRP, or “Notification IRP“, etc and where the other IRP can be for example Generic IRP). The Interface and NRM YyyIRP specifications of particular IRPVersion(s) together specify the behaviour of an Interface IRP and the supporting NRM IRP (s). NOTE: The IRPVersion concept is related to the IRP. The