1、 ETSI TS 1Universal Mobile TelTelecommHome Node B (HNB) andType 2 interfac(3GPP TS 32.5TECHNICAL SPECIFICATION132 571 V13.0.1 (2017elecommunications System (LTE; munication management; n Home eNode B (HeNB) maace concepts and requiremen.571 version 13.0.1 Release 1317-01) (UMTS); nagement; ents 13)
2、ETSI ETSI TS 132 571 V13.0.1 (2017-01)13GPP TS 32.571 version 13.0.1 Release 13Reference RTS/TSGS-0532571vd01 Keywords 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 Association but non
3、 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 versions of
4、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 specific ne
5、twork 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 you find err
6、ors 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 microfilm exc
7、ept 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 rights reserved.
8、 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 logo are Trade Marks registered and owned by the
9、GSM Association. ETSI ETSI TS 132 571 V13.0.1 (2017-01)23GPP TS 32.571 version 13.0.1 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly availab
10、le 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. Latest updates are available on the ETSI Web server
11、(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 Web server) which are, or may be, or may become,
12、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 identities or GSM identities. These should be int
13、erpreted 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“, “shall not“, “should“, “should not“, “may“, “need
14、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 direct citation. ETSI ETSI TS 132 571 V13.0.1 (2017
15、-01)33GPP TS 32.571 version 13.0.1 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Concepts and background 6g34.1 Over
16、view 6g34.2 Architecture 6g34.2.1 Mapping Function . 7g35 Business Level Requirements 8g35.1 Requirements 8g35.2 Actor roles 8g35.3 Telecommunications resources 8g35.4 High-level use cases . 8g36 Specification level requirements 9g36.1 Requirements 9g36.1.1 Configuration management . 9g36.1.2 Fault
17、management . 9g3Annex A (informative): Change history . 10g3History 11g3ETSI ETSI TS 132 571 V13.0.1 (2017-01)43GPP TS 32.571 version 13.0.1 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are sub
18、ject 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 as follows: Version x.y.z where: x the first
19、 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, etc. z the third digit is incremented whe
20、n 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; as identified below: 32.571 Telecommunicat
21、ion management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements 32.572: Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions ETSI ETSI TS 132 571 V13.0.1 (2017-01)53GPP TS 32
22、.571 version 13.0.1 Release 131 Scope The present document describes requirements and concepts including architecture supporting Home Node B and Home eNode B OAM Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.581: Telecommunicati
23、ons management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM Concepts and requirements for Type 1 interface HNB to HNB Management System (HMS)“. 5 3GPP TS 32.591: Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provisi
24、oning (OAM Concepts and requirements for Type 1 interface HeNB to HeNB Management System (HMS)“. 6 3GPP TS 22.220: Service Requirements for Home NodeBs and Home eNodeBs 7 3GPP TS 32.111-2: Telecommunications management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information S
25、ervice (IS) 8 3GPP TS 32.583: Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM Procedure flows for Type 1 interface HNB to HNB Management System (HMS) 3 Definitions and abbreviations For the purposes of this document, the terms and defini
26、tions given in TS 21.905 1, TS 32.101 2 and TS 32.102 3 and in the following sub-clause 3.1 apply. Same term may be defined in different documents. The precedence rule, applicable to this document, is in the order of: this document, TS 32.101 2, TS 32.102 3, TS 21.905 1. 3.1 Definitions There is no
27、additional definition defined in this subclause. ETSI ETSI TS 132 571 V13.0.1 (2017-01)63GPP TS 32.571 version 13.0.1 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: DM Domain Manager EM Element Manager HeNB Home eNode B HMS HNB Management Sys
28、tem HeMS HeNB Management System HNB Home Node B NM Network ManagerOAM Operations, Administrator and Maintenance 4 Concepts and background 4.1 Overview This clause lays out the logical system architecture for the support of HNB and HeNB management via Type 2 interface. The architecture here takes int
29、o consideration of the Type 1 interface for HNB and Type 1 interface for HeNB. 4.2 Architecture This clause describes the logical system architecture. HNB HeNBIRPManagerType 1 InterfaceType 2 InterfaceACBHMS and/or HeMSIRPAgent: YyyIRP(s)NMEMFigure 1: System context of HNB and HeNB management The “A
30、“ denotes the network management protocols (and associated network management data) whose characteristics are to be defined by this TS series. The “B“ denotes the network management protocols (and associated network management data) whose characteristics are defined in TS series of 4. ETSI ETSI TS 1
31、32 571 V13.0.1 (2017-01)73GPP TS 32.571 version 13.0.1 Release 13The “C“ denotes the network management protocols (and associated network management data) whose characteristics are defined in TS series of 5. The YyyIRPs of the IRPAgent:YyyIRP(s) box denotes the various IRPs such as AlarmIRP, BasicCM
32、IRP, PMIRP, etc. The triangle boxes represent managed devices such as HeNB and HNB. IRPManager uses “A“ to manage all managed devices. In this configuration, IRPAgent:YyyIRP(s) plays the role of network management service provider for IRPManager and the role of consumer for HMS and HeMS. Similarly,
33、HMS and HeMS play the role of service provider for IRPAgent:YyyIRP(s) and the role of device management service consumer for HNB(s) and HeNB(s). The boxes are logical functional entities. Their physical locations and their realization inphysical processors cannot be deduced or implied. For example,
34、an implementation can have IRPAgent:YyyIRP(s) and HMS and/or HeMS implemented in one physical processor. The interaction between IRPAgent:YyyIRP(s) and HMS and/or HeMS is not visible from the perspective of this specification. 4.2.1 Mapping Function IRPManager manages HNB(s) and HNB(s) using “A“. Th
35、is management activities would trigger (result in) interactions between HMS and/or HeMS and HNB(s) and HeNB(s), using “B“ and “C“. The trigger(s) that relates interactions of “A“ and interactions of “B“/“C“ is denoted by “F1“ and “F2“, the Mediation function. Because the interaction between IRPAgent
36、:YyyIRP(s) and HMS and/or HeMS is not visible, it is of no relevance if “F“ should be placed inside one box or another. This document chooses to place “F1“ and “F2“ arbitrary but embedded within IRPAgent:YyyIRP(s) and HMS and/or HeMS boundaries. Figure 2: Mapping (or Mediation) functions The F1 is t
37、he mapping (or mediation) function for network management data exchanged via Type 2 interface and NM data exchanged via Type 1 interface with HNB. The F2 is the mapping (or mediation) function for network management data exchanged via Type 2 interface and NM data exchanged via Type 1 interface with
38、HeNB. ETSI ETSI TS 132 571 V13.0.1 (2017-01)83GPP TS 32.571 version 13.0.1 Release 135 Business Level Requirements 5.1 Requirements REQ-HBT2-FUN-1 The IRPAgent shall have the capability allowing IRPManager to manage HNB and HeNB using existing Interface IRPs. REQ-HBT2-FUN-2 The IRPAgent should have
39、the capability to provide a single point of access allowing IRPManager to manage HNBs, HeNBs and other types of managed entity such as macro eNBs. For example, the IRPAgent could have a single AlarmIRP that holds active alarms from HNBs and HeNBs as well as active alarms from other managed entities
40、such as macro eNBs, etc. REQ-HBT2-FUN-3 Operator shall be able to manage the following deployment scenarios in the most efficient manner: 1. Deployment of HNBs only; 2. Deployment of HeNBs only; 3. Mixed deployment of the two scenarios above. REQ-HBT2-FUN-4 In order to provide efficient management o
41、f mixed HNB/HeNB device deployment scenarios, management over Type-2 interface should be as integrated as possible. REQ-HBT2-FUN-5 For mixed deployment scenarios with a single IRPAgent, the IRPAgent shall provide a capability allowing IRPManager to issue a single network management request to manage
42、 HNB(s) and HeNB(s). 5.2 Actor roles IRPManager plays the Actor role. 5.3 Telecommunications resources OAM network. 5.4 High-level use cases There is no high-level use case defined. ETSI ETSI TS 132 571 V13.0.1 (2017-01)93GPP TS 32.571 version 13.0.1 Release 136 Specification level requirements 6.1
43、Requirements 6.1.1 Configuration management REQ- HBT2-FUN-100 The IRPAgent shall support a capability allowing IRPManager to create and manage profiles of HNB and HeNB configuration parameters; in order to allow HNB and HeNB to complete the registration procedure when turned on (see Registration pro
44、cedure in TS 32.583 8). REQ- HBT2-FUN-101 The IRPAgent shall support a capability allowing IRPManager to install software on a large number of HNB and HeNB. 6.1.2 Fault management REQ- HBT2-FUN-200 The IRPAgent shall support a capability allowing IRPManager to use existing network management service
45、s provided by AlarmIRP to manage alarms categorized as Expedited handling (see REQ-OAMP_FM-FUN-005 of 4) or categorized as Queued handling (see REQ-OAMP_FM-FUN-005 of 4). ETSI ETSI TS 132 571 V13.0.1 (2017-01)103GPP TS 32.571 version 13.0.1 Release 13Annex A (informative): Change history Change hist
46、ory Date TSG # TSG Doc. CR Rev Subject/Comment Old New Dec 2009 SA#46 SP-090731 - - Presentation to SA for information. - 1.0.0 Mar 2010 SA#47 SP-100055 - - Presentation to SA for approval 1.0.0 2.0.0 Mar 2010 - - - - Publication of SA approved version 2.0.0 9.0.0 2011-03 - - - - Update to Rel-10 ve
47、rsion (MCC) 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-10 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 Change history Date Meeting Tdoc CR Rev Cat Subject/Comment New version 2016-12 Correction of LTE logo (MCC) 13.0.1 ETSI ETSI TS 132 571 V13.0.1 (2017-01)113GPP TS 32.571 version 13.0.1 Release 13History Document history V13.0.0 February 2016 Publication (withdrawn) V13.0.1 January 2017 Publication
