32581a00.docx

1、32581a003GPP TS 32.581 V10.0.0 (2010-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Telecommunication management;Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P);Concepts and Requirements for Ty

2、pe 1 interface HNB to HNB Management System (HMS)(Release 10) The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organiza

3、tional Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the

4、3GPP Organizational Partners Publications Offices.KeywordsHome NodeB, management3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduc

5、ed except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2010, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Tra

6、de Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsFo

7、reword 4Introduction 41 Scope 52 References 53 Definitions and abbreviations 53.1 Definitions 53.2 Abbreviations 64 Concepts and background 65 Business level requirements 65.1 Requirements 65.1.1 Configuration Management 65.1.2 Performance Management 75.1.3 Fault Management 75.1.4 Security Managemen

8、t 75.2 Actor roles 75.3 Telecommunications resources 75.4 High level use cases 76 Specification level requirements 76.1 Requirements 76.1.1 Configuration Management 76.1.2 Performance Management 86.1.3 Fault Management 96.1.4 Security Management 106.2 Actor roles 106.3 Telecommunications resources 1

9、06.4 Use cases 10Annex A (informative): Change history 11ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the

10、 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.zwhere:x the first digit:1 presented to TSG for information;2 presented to TSG for approval;3 or greater indicates T

11、SG 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 the document.IntroductionThe present document is par

12、t of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication Management; as identified below:3GPP TS 32.581: Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM

13、&P); 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&P); Information model for Type 1 interface HNB to HNB Management System (HMS).3GPP TS

14、32.583: Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HNB to HNB Management System (HMS). 3GPP TS 32.584: Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance

15、 and Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS).1 ScopeThe present document describes the concepts and requirements of OAM for Home NodeB (HNB). The requirements captured in this document shall be met via Type 1 interface between HNB and HMS.2 Refer

16、encesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific. For a specific reference, subsequent revision

17、s 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-specific 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

18、 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 WAN Management Protocol v1.1, Broadband Forum4 TR-106 Amendment 2 Data Model template for TR-069-Enabled Devices v1.1, Broadband Forum.5 TR-196 FAP Acce

19、ss Point Service Data Model v1.00, Broadband Forum. 6 3GPP TS 32.435: Performance Measurement, eXtensible Markup Language (XML) file format definition.7 3GPPTS32.111-2: Telecommunication management; Fault Management; Alarm Integration Reference Point (IRP): Information Service (IS) .8 3GPP TS 32.101

20、: Telecommunication management; Principles and high level requirements.9 3GPP TS 32.102: Telecommunication management; Architecture.10 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).3 Definitions and abbreviati

21、onsFor the purposes of the present document, the terms and definitions given in TS 32.101 8, TS 32.102 9 and TS21.90510 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 TS21.90510, in that o

22、rder.3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in TR21.90510 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.90510.3.2 AbbreviationsFor the purposes of the present do

23、cument, the following abbreviations apply:HMS Home NodeB Management SystemHNB Home NodeB4 Concepts and backgroundHome NodeB has the following characteristics: The quantity of Home NodeBs is likely to be large There may be many Home NodeB vendors Home NodeB may be purchased easily by end users in mar

24、ket The location of Home NodeB could be in a private residence which may not be accessible for frequent on-site maintenanceBased on the above characteristics, this specification defines the functionalities needed for the management of Home NodeB over a Type 1 interface. 5 Business level requirements

25、5.1 RequirementsREQ-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-specific or operator-specific extension capability. 5.1.1 Confi

26、guration ManagementREQ-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-002 The HNB shall be able to automatically, i.e. without human op

27、erator 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, upgrade its software/firmware and configuration.REQ-OAMP_CM-CON-00

28、4 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 network and changes in the radio environment.REQ-OAMP_CM-CON-006 T

29、he 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 to ensure that the HNB IP address changes as minimally as possible.R

30、EQ-OAMP_CM-CON-009 The operator shall be able to remotely reconfigure the HNB to adapt to changes in the radio environment.5.1.2 Performance ManagementREQ-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 b

31、ased on operator configured policy. REQ-OAMP_PM-CON-003 Operator shall be able to retrieve performance data file from the HNB.5.1.3 Fault ManagementREQ-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 provid

32、e alarm related information only on demand by the operator or based on operator configured policy.5.1.4 Security ManagementREQ-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 rolesNot defined in this version.5.3 Telecommunications r