TS 32583 HNB的操作过程规范.docx

1、TS 32583 HNB的操作过程规范3GPP TS 32.583 V9.2.0 (2009-12)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);Procedure flows for Typ

2、e 1 interface HNB to HNB Management System (HMS)(Release 9) 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 Organizati

3、onal 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 3G

4、PP 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 reproduced

5、 except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2009, 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 Trade

6、 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 AssociationContentsFore

7、word 5Introduction 51 Scope 62 References 63 Definitions and abbreviations 63.1 Definitions 63.2 Abbreviations 64 Architecture for HNB Management 74.2 Functional Elements 84.2.1 HNB Management System (HMS) 84.2.1.1 Initial HNB Management System (HMS) 84.2.1.2 Serving HNB Management System (HMS) 84.2

8、.2 Security Gateway (SeGW) 94.2.2.1 Initial Security Gateway (SeGW) 94.2.2.2 Serving Security Gateway (SeGW) 94.2.3 HNB Gateway (HNB-GW) 95 Procedure Flows 95.1 Discovery procedures (Mandatory) 95.1.1 Discovery procedures via HMS (initial) accessible on the MNO Intranet (Mandatory) 95.1.2 Discovery

9、procedures via HMS (initial) accessible on the public Internet (Mandatory) 115.2 HNB Registration (Mandatory) 125.2.1 HNB registration Procedure (Mandatory) 125.2.2 HNB IPSec IP address change procedure (Mandatory) 135.3 HNB Configuration Management (Mandatory) 145.3.1 HNB configuration management b

10、y means of file download (Optional) 155.3.2 HNB configuration management using RPC Set Parameter Value method (Mandatory) 165.4 HNB De-Provisioning (Mandatory) 165.5 Alarm Reporting (Mandatory) 185.5.1 Alarm Reporting Mechanism Configuration (Mandatory) 185.5.2 Alarm Reporting Procedure (by RPC meth

11、od) (Mandatory) 185.6 PM File Upload (Mandatory) 195.6.1 PM File Upload Period Set Procedure (Mandatory) 195.6.2 PM File Uploading Procedure (Mandatory) 20Annex A (informative): Change history 21ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).T

12、he contents of the present document are subject 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 a

13、s 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 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

14、 the third digit is incremented when editorial only changes have been incorporated in the document.IntroductionThe present document is part of a TS-family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Telecommunication Management; as ident

15、ified below:3GPP TS 32.581: Telecommunications management; Home Node B (HNB)Operations, Administration, Maintenance and Provisioning (OAM&P); Conceptsand requirements for Type 1 interface HNB to HNB Management System (HMS).3GPP TS 32.582: Telecommunications management; Home Node B (HNB)Operations, A

16、dministration, Maintenance and Provisioning (OAM&P);Information model for 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&P); Procedureflows for Type 1 interface HNB to H

17、NB Management System (HMS). 3GPP TS 32.584: Telecommunications management; Home Node B (HNB)Operations, Administration, Maintenance and Provisioning (OAM&P); XMLdefinitions for Type 1 interface HNB to HNB Management System (HMS).1 ScopeThe present document describes the procedure flows between HNB &

18、 HMS for the OAM of HNB Management.2 ReferencesThe 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

19、 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-specific reference implicitly refers to the latest version of that document in the same Release as the p

20、resent document.1 3GPP TR 21.905: Vocabulary for 3GPP Specifications.2 3GPP TS 32.101: Telecommunication management; Principles and high level requirements.3 3GPP TS 32.102: Telecommunication management; Architecture.4 3GPP TS 32.300: Telecommunication management; Configuration Management (CM); Name

21、 convention for Managed Objects.5 TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum, viewable at 6 3GPP TR 25.820 3G Home NodeB Study Item Technical Report7 3GPP TS 25.401 Radio Access Network UTRAN Overall Description8 3GPP TR 32.821: Study of Self-Organizing Network (SON) relat

22、ed OAM for Home NodeB.9 3GPP TS 25.467: UTRAN architecture for 3G Home NodeB, stage 2.10 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)3 Defin

23、itions and abbreviationsFor the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TS21.9051 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 2, TS 32.102 3 and T

24、S21.9051, in that order.3.1 DefinitionsFor the purposes of the present document, the terms and definitions given in TR21.9051 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.9051.3.2 AbbreviationsFor the purposes

25、of the present document, the following abbreviations apply:DNS Domain Name ServerFTP File Transfer ProtocolHMS Home NodeB Management SystemHNB Home NodeBHNB-GW Home NodeB GatewayHTTP Hyper Text Transfer ProtocolHTTPS Hyper Text Transfer Protocol SecureIP Internet ProtocolLAN Local Area NetworkMNO Mo

26、bile Network OperatorRNC Radio Network ControllerRPC Remote Procedure CallSeGW Security GatewaySSL Secure Socket LayersFTP Secure File Transfer ProtocolTLS Transport Layer SecurityURL Unified Resource Locator4 Architecture for HNB Management4.1 HNB OAM functional architectureThis section provides th

27、e HNB OAM functional architecture. We distinguish the two following cases: A HNB is connected to a BB device (typically a residential gateway providing connectivity via an access provider domain). The BB device provides routing, NAT and firewall functionality. A BB device with an integrated HNB func

28、tionalityThe HNB Management System (HMS) main tasks are to provision configuration data on the HNB. It provides the following functional entities: A file server A TR-069 auto-configuration server (ACS)However the file server may be used by other applications in the MNO domain.Figure 4.1.1-1: Archite

29、cture for HNB Management4.2 Functional Elements4.2.1 HNB Management System (HMS)The HMS is composed of a TR-069 manager and a file server. The TR069 manager implements the Auto-Configuration Server function as defined in TR-069 standard and performs CM, FM and PM functionalities to the HNB. The file

30、 server may be used for file upload or download, as instructed by TR-069 manager4.2.1.1 Initial HNB Management System (HMS)The initial HMS may provide location verification of HNB and assigns appropriate serving elements (Serving HMS, Security Gateway and HNB-GW).4.2.1.2 Serving HNB Management Syste

31、m (HMS)Provides the following functionalities: TR-069 Auto-configuration server File server for file upload or download Provisioning of configuration data to the HNB Performance & Fault updates Provides Serving SeGW discovery4.2.2 Security Gateway (SeGW)SeGW terminates Secure tunnelling for TR-069 as well as Iuh. It is used for authentication of HNB & provides access to HMS and HNB-GW.4.2.2.1 Initial Security Gateway (SeGW)The URL of the Initial SeGW may be factory programmed in the HNB so as to allow initial establishment of an IPSec security association and