1、 ETSI TS 132 593 V14.0.0 (2017-04) LTE; Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM Procedure flows for Type 1 interface HeNB to HeNB Management System (HeMS) (3GPP TS 32.593 version 14.0.0 Release 14) TECHNICAL SPECIFICATIO
2、N ETSI ETSI TS 132 593 V14.0.0 (2017-04)13GPP TS 32.593 version 14.0.0 Release 14Reference RTS/TSGS-0532593ve00 Keywords LTE 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 lu
3、cratif 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 the
4、 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 netwo
5、rk 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 errors
6、 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 except
7、 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. DE
8、CTTM, 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. oneM2M logo is protected for the benefit of its Members GSM and the
9、GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 593 V14.0.0 (2017-04)23GPP TS 32.593 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining
10、 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 Secretariat.
11、 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 updates on the E
12、TSI 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 identities, U
13、MTS 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 document “shall
14、“, “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 when used i
15、n direct citation. ETSI ETSI TS 132 593 V14.0.0 (2017-04)33GPP TS 32.593 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and Abbreviations 5g33.1 Definitions 6g33.2 Abbre
16、viations . 6g34 Architecture for HeNB Management . 6g34.1 HeNB OAM Functional Architecture. 6g34.1.1 Overview 6g34.2 Functional Elements . 7g34.2.1 HeNB Management System (HeMS) 7g34.2.1.1 Initial HeMS 7g34.2.1.2 Serving HeMS. 7g34.2.2 Home eNB 8g34.2.3 Security Gateway (SeGW) 8g34.2.3.1 Initial SeG
17、W . 8g34.2.3.2 Serving SeGW . 8g34.2.4 MME/HeNB GW 8g35 Procedure Flows . 9g35.1 Discovery and Registration Procedures 9g35.1.1 Overview 9g35.1.2 Serving HeMS discovery procedures 9g35.1.2.1 Overview . 9g35.1.2.2 Serving HeMS Discovery via Initial HeMS accessible inside operators private secure netw
18、ork domain (Conditional Mandatory) 10g35.1.2.3 Serving HeMS discovery via Initial HeMS accessible on the public internet (Conditional Mandatory) 11g35.1.3 HeNB registration with Serving HeMS (Mandatory) . 12g35.2 Configuration Management Procedures (Mandatory) 13g35.2.1 Overview 13g35.2.2 HeNB confi
19、guration using file download procedure (Optional) . 13g35.2.3 HeNB configuration using SetParameterValues RPC method (Mandatory) 14g35.2.4 IPSec tunnel IP address change notification procedure (Conditional Mandatory) . 15g35.3 Alarm Reporting Procedures 16g35.3.1 Alarm reporting mechanism configurat
20、ion . 16g35.3.2 Alarm reporting procedure for expedited and queued alarms (by RPC method) 16g35.4 PM File Upload Procedures 17g35.4.1 PeriodicUploadInterval parameter configuration 17g35.4.2 PM file upload 18g3Annex A (informative): Change History 19g3History 20g3ETSI ETSI TS 132 593 V14.0.0 (2017-0
21、4)43GPP TS 32.593 version 14.0.0 Release 14Foreword 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 and may change following formal TSG approval. Should the TSG modify t
22、he 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 information; 2 presented to TSG for approval; 3 or greater indicates TSG appr
23、oved 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. Introduction The present document is part o
24、f a TS-family covering the 3rdGeneration Partnership Project Technical Specification Group Services and System Aspects, Telecommunication Management; as identified below: 3GPP TS 32.591: “Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM
25、 Concepts and requirements for Type 1 interface HeNB to HeNB Management System“. 3GPP TS 32.592: “Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM Information model for Type 1 interface HeNB to HeNB Management System“. 3GPP TS 32.593: “
26、Telecommunications management; Home Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM Procedure flows for Type 1 interface HeNB to HeNB Management System “. 3GPP TS 32.594: “Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provi
27、sioning (OAM XML definitions for Type 1 interface HeNB to HeNB Management System“. ETSI ETSI TS 132 593 V14.0.0 (2017-04)53GPP TS 32.593 version 14.0.0 Release 141 Scope The present specification describes the procedure flows between network entities involved in HeNB management-related tasks. These
28、procedures are based on the requirements specified in 4. Information model for management-related information exchanged in these procedures is specified in 5 and references therein. XML file formats used to encapsulate the information exchanged in these procedures are specified in 6. The communicati
29、on protocol used for HeNB management is the TR-069 protocol, specified in 7. Management interface affected by these procedures is the Type 1 interface between HeNB and HeMS. Procedures flows over the Type 2 interface (between Element Management and Network Management layer) for the management of HeN
30、B are outside of scope of this document 2 References The 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 non-spec
31、ific. - 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-specific reference implicitly refers to the latest version of that document in the same Rel
32、ease as the present 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.591: “Telecommunications management; Home eNode
33、 B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM Concepts and Requirements for Type 1 interface HeNB to HeNB Management System“. 5 3GPP TS 32.592: “Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM Information mode
34、l for Type 1 interface HeNB to HeNB Management System“ 6 3GPP TS 32.594: “Telecommunications management; Home eNode B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM XML definitions for Type 1 interface HeNB to HeNB Management System“ 7 TR-069 Amendment 2, CPE WAN Management Pro
35、tocol v1.1, Broadband Forum, viewable at http:/www.broadband-forum.org/technical/download/TR-069Amendment2.pdf 8 3GPP TS 36.413: “ Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 9 3GPP TS 33.320: “Sec
36、urity of Home Node B (HNB) / Home evolved Node B (HeNB)“. 3 Definitions and Abbreviations For the purposes of the present document, the terms and definitions given in TS 32.101 2, TS 32.102 3 and TS 21.905 1 and the following apply. A term defined in the present document takes precedence over the de
37、finition of the same term, if any, in TS 32.101 2, TS 32.102 3 and TS 21.905 1, in that order. ETSI ETSI TS 132 593 V14.0.0 (2017-04)63GPP TS 32.593 version 14.0.0 Release 143.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following app
38、ly. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management DNS Domain Name Server EPC Evolved Packet Core FM Fault
39、 ManagementFQDN Fully Qualified Domain Name FTP File Transfer Protocol HMS Home NodeB Management System HeMS Home eNodeB Management System HNB Home NodeB HeNB Home eNodeBHeNB-GW HeNB Gateway HTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure IP Internet Protocol LAN Local Ar
40、ea Network MME Mobility Management Entity MNO Mobile Network Operator OAM Operation, Administration, Maintenance PM Performance Management RPC Remote Procedure Call SeGW Security Gateway SSL Secure Socket LayerSFTP Secure File Transfer Protocol TLS Transport Layer Security 4 Architecture for HeNB Ma
41、nagement 4.1 HeNB OAM Functional Architecture 4.1.1 Overview This section describes the functional architecture for HeNB management over Type 1 management interface and entities involved. The architecture is shown in Figure 4-1 Functionalities of each entity are described in subsequent subclauses. N
42、on-OAM entities, such as SeGW and MME are also shown as they figure in the procedure flows specified in this document. ETSI ETSI TS 132 593 V14.0.0 (2017-04)73GPP TS 32.593 version 14.0.0 Release 14Figure 4-1: HeNB Management Architecture 4.2 Functional Elements 4.2.1 HeNB Management System (HeMS) T
43、he HeMS supports the procedures for: - Configuration Management (CM), Fault management (FM) and Performance Management (PM) of HeNB - Identity and location verification of HeNB - Discovery and assignment of Serving HeMS, Serving SeGW, and MME - File upload/download related to HeNB management. The He
44、MS comprises a TR-069 Manager and an file server. The TR-069 Manager corresponds to the TR-069 Auto-Configuration Server (ACS) function as defined in TR-069 specification 7. The file server may be used for file upload or download related to HeMS management, such as upload of performance measurement
45、files or alarm logs, as configured by TR-069 Manager. The file server may also be used for other purposes by network operator. Typically, HeMS assumes one of the following two roles: - Initial HeMS (subclause x.y.z.w) - Initial Serving HeMS (subclause x.y.z.w) 4.2.1.1 Initial HeMS The Initial HeMS m
46、ay be used to perform identity and location verification of HeNB and assign appropriate Serving HMS, Security Gateway and MME to HeNB. The FQDN of the Initial HeMS may be factory programmed in the HeNB. 4.2.1.2 Serving HeMS Serving HeMS supports the procedures for CM/FM/PM, file upload/download, and
47、 identity verification of the HeNB. Serving HeMS may also support MME discovery and assignment by HeNB. ETSI ETSI TS 132 593 V14.0.0 (2017-04)83GPP TS 32.593 version 14.0.0 Release 14Typically, Serving HeMS is located inside the operators secure network domain and the address of the Serving HeMS is
48、provided to the HeNB via Initial HeMS. 4.2.2 Home eNB The HeNB is the managed device. The HeNB logically comprises a TR-069 Agent and an file client. TR-069 Agent corresponds to the TR-069 Customer Premise Equipment (CPE) function as defined in TR-069 specification 7. The file client may be used for
49、 file upload or download related to HeMS management, such as upload of performance measurement files or alarm logs, as configured by TR-069 Manager via TR-069 Agent. The file client may also be used for other purposes not related to HeNB management. HeNB is associated with a Broadband (BB) device. This is typically a residential gateway providing transport layer connectivity via an access provider domain. The BB device provides routing, NAT and firewall functionality. As shown in Figure 4-1, HeNB can be connected to an external
