ETSI TS 132 581-2016 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Home Node B (HNB) Operations Administration Maintenance and Provisioning (OA.pdf

1、 ETSI TS 1Universal Mobile TelTelecommHome Node B (HNMaintenance Concepts and requto HNB Ma(3GPP TS 32.5TECHNICAL SPECIFICATION132 581 V13.0.0 (2016elecommunications System (LTE; munication management; ( NB) Operations, Administrate and Provisioning (OAMuirements for Type 1 interfacanagement System

2、(HMS) .581 version 13.0.0 Release 1316-02) (UMTS); ration, P); ace HNB 13) ETSI ETSI TS 132 581 V13.0.0 (2016-02)13GPP TS 32.581 version 13.0.0 Release 13Reference RTS/TSGS-0532581vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax:

3、+33 4 93 65 47 16 Siret N 348 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 versio

4、ns and/or in print. The content 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 th

5、e print of the Portable Document 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 availa

6、ble at http:/portal.etsi.org/tb/status/status.asp 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, e

7、lectronic or mechanical, 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

8、Telecommunications Standards Institute 2016. 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.

9、GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 581 V13.0.0 (2016-02)23GPP TS 32.581 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The informatio

10、n 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 ETSI

11、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 upda

12、tes 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 i

13、dentities, 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 doc

14、ument “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 except

15、 when used in direct citation. ETSI ETSI TS 132 581 V13.0.0 (2016-02)33GPP TS 32.581 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definition

16、s 5g33.2 Abbreviations . 6g34 Concepts and background 6g35 Business level requirements . 6g35.1 Requirements 6g35.1.1 Configuration Management 6g35.1.2 Performance Management 7g35.1.3 Fault Management 7g35.1.4 Security Management . 7g35.2 Actor roles 7g35.3 Telecommunications resources 7g35.4 High l

17、evel use cases . 7g36 Specification level requirements 7g36.1 Requirements 7g36.1.1 Configuration Management 7g36.1.2 Performance Management 8g36.1.3 Fault Management 9g36.1.4 Security Management . 10g36.2 Actor roles 10g36.3 Telecommunications resources 10g36.4 Use cases 10g3Annex A (informative):

18、Change history . 11g3History 12g3ETSI ETSI TS 132 581 V13.0.0 (2016-02)43GPP TS 32.581 version 13.0.0 Release 13Foreword 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

19、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

20、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

21、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: 3GPP TS 32.581: “Telecommunications management; Home Node B

22、(HNB) Operations, Administration, Maintenance and Provisioning (OAM Concepts and requirements for Type 1 interface HNB to HNB Management System (HMS)“. 3GPP TS 32.582: “Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM Information model fo

23、r Type 1 interface HNB to HNB Management System (HMS)“. 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)“. 3GPP TS 32.584: “Telecommunications manage

24、ment; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM XML definitions for Type 1 interface HNB to HNB Management System (HMS)“. ETSI ETSI TS 132 581 V13.0.0 (2016-02)53GPP TS 32.581 version 13.0.0 Release 131 Scope The present document describes the concepts and requi

25、rements of OAM for Home NodeB (HNB). The requirements captured in this document shall be met via Type 1 interface between HNB and HMS. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either s

26、pecific (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), a non-sp

27、ecific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 32.821: “Study of Self-Organizing Network (SON) related OAM for Home NodeB“. 2 3GPP TS 25.467: “UTRAN architecture for 3G Home NodeB, stage 2“. 3 TR-069 Amendment 2, CPE W

28、AN Management Protocol v1.1, Broadband Forum 4 TR-106 Amendment 2 Data Model template for TR-069-Enabled Devices v1.1, Broadband Forum. 5 TR-196 FAP Access Point Service Data Model v1.00, Broadband Forum. 6 3GPP TS 32.435: “Performance Measurement, eXtensible Markup Language (XML) file format defini

29、tion“. 7 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP): Information Service (IS) “. 8 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 9 3GPP TS 32.102: “Telecommunication management; Architecture“. 1

30、0 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 11 3GPP TS 22.220: “Service requirements for Home Node B (HNB) and Home eNode B (HeNB)“. 12 3GPP TS 33.320: “Security of Home Node B (HNB) / Home evolved Node B (HeNB)“. 3 Definitions and abbreviations For the purposes of the present document,

31、the terms and definitions given in TS 32.101 8, TS 32.102 9 and TS 21.905 10 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TS 32.101 8, TS 32.102 9 and TS 21.905 10, in that order. 3.1 Definitions For the purposes of

32、 the present document, the terms and definitions given in TR 21.905 10 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 10. ETSI ETSI TS 132 581 V13.0.0 (2016-02)63GPP TS 32.581 version 13.0.0 Release 133.2 Ab

33、breviations For the purposes of the present document, the following abbreviations apply: HMS Home NodeB Management System HNB Home NodeB 4 Concepts and background Home NodeB has the following characteristics: - The quantity of Home NodeBs is likely to be large - There may be many Home NodeB vendors

34、- Home NodeB may be purchased easily by end users in market - The location of Home NodeB could be in a private residence which may not be accessible for frequent on-site maintenance Based on the above characteristics, this specification defines the functionalities needed for the management of Home N

35、odeB over a Type 1 interface. 5 Business level requirements 5.1 Requirements REQ-OAMP-CON-001 The HNB shall be able to be managed in all management domain aspects defined below as Configuration management, Security management, Performance management and Fault management, without the use of vendor-sp

36、ecific or operator-specific extension capability. 5.1.1 Configuration Management REQ-OAMP_CM-CON-001 The HNB shall be able to automatically, i.e. without human operator on-line interaction or attention, configure itself to be ready for service when powered up and connected to HMS. REQ-OAMP_CM-CON-00

37、2 The HNB shall be able to automatically, i.e. without human operator on-line interaction or attention, configure itself to be in service when powered up and connected to HMS. REQ-OAMP_CM-CON-003 The HNB shall be able to automatically, i.e. without human operator on-line interaction or attention, up

38、grade its software/firmware and configuration. REQ-OAMP_CM-CON-004 The HNB auto-configuration shall be done in such way that the performance of the surrounding macro cells is not adversely affected. REQ-OAMP_CM-CON-005 The HNB auto-configuration function should be adaptive to react to change in the

39、network and changes in the radio environment. REQ-OAMP_CM-CON-006 The operator shall be able to remotely reboot the HNB. REQ-OAMP_CM-CON-007 The operator shall be able to remotely start/stop the radio transmission of the HNB. REQ-OAMP_CM-CON-008 In case IPsec is used, the system should be engineered

40、 to ensure that the HNB IP address changes as minimally as possible. REQ-OAMP_CM-CON-009 The operator shall be able to remotely reconfigure the HNB to adapt to changes in the radio environment. REQ-OAMP_CM-CON-010 The HNB should allow configuration of the IPsec or non-IPsec usage option based on the

41、 operators policy TS 33.320 12. ETSI ETSI TS 132 581 V13.0.0 (2016-02)73GPP TS 32.581 version 13.0.0 Release 135.1.2 Performance Management REQ-OAMP_PM-CON-001 The HNB may have the capability to collect its performance related data. REQ-OAMP_PM-CON-002 The HNB shall send performance data based on op

42、erator configured policy. REQ-OAMP_PM-CON-003 Operator shall be able to retrieve performance data file from the HNB. 5.1.3 Fault Management REQ-OAMP_FM-CON-001 The HNB shall support Fault Management to enable the operator to monitor and manage the HNB. REQ-OAMP_FM-CON-002 The HNB shall provide alarm

43、 related information only on demand by the operator or based on operator configured policy. 5.1.4 Security Management REQ-OAMP_SM-CON-001 The HNB shall have the capability to protect itself against Denial of Service attack over the Type 1 interface. 5.2 Actor roles Not defined in this version. 5.3 T

44、elecommunications resources Not defined in this version. 5.4 High level use cases Not defined in this version. 6 Specification level requirements 6.1 Requirements 6.1.1 Configuration Management The requirements for configuration management are as follows: REQ-OAMP_CM-FUN-001 The HNB configuration sh

45、all be administered by the HMS utilising the TR-069 CWMP Protocol, reference 3. REQ-OAMP_CM-FUN-002 The HNB Information Model used by the HMS for Configuration Management shall be based on the following: a. Broadband Forum TR-106 Amendment 2 Data Model 4 b. FAP Access Point Service Data Model 5 REQ-

46、OAMP_CM-FUN-003 HMS shall be able to reboot the HNB. REQ-OAMP_CM-FUN-004 HMS shall have remote access to the HNB to start/stop the radio transmission. ETSI ETSI TS 132 581 V13.0.0 (2016-02)83GPP TS 32.581 version 13.0.0 Release 13REQ-OAMP_CM-FUN-005 HMS shall have remote access to the HNB to start/s

47、top the radio transmission on the frequencies specified by HMS. REQ-OAMP_CM-FUN-006 HMS shall maintain the configuration data of the HNB. REQ-OAMP_CM-FUN-007 When the HNB is initially powered up and connected to the HMS, HMS shall send the initially needed configuration data to the HNB. REQ-OAMP_CM-

48、FUN-008 If the inner IPsec tunnel IP address of the HNB changes and HNB is connected to HMS via IPsec Tunnel then the HNB shall notify the HMS using TR-069. REQ-OAMP_CM-FUN-009 The HMS shall specify which parameters it needs to be notified of when the HNB changes their values through auto-configurat

49、ion. The HNB shall notify the HMS of changes in the values of any such auto-configured parameters. REQ-OAMP_CM-FUN-010 The HNB shall inform the HMS of its ability to auto-configure parameters or groups of parameters that are relevant to the HMS. REQ-OAMP_CM-FUN-011 HMS shall be able to specify a value, or a valid range of values, for any parameter that is auto-configurable by the HNB. REQ-OAMP_CM-FUN-012 Configuration management capability for the HNB shall be supported by means of TR-069 RPCs SetParameterValues, AddObje