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

1、 ETSI TS 132 583 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication 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.583 version 14.

2、0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 583 V14.0.0 (2017-04)13GPP TS 32.583 version 14.0.0 Release 14Reference RTS/TSGS-0532583ve00 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 5

3、62 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 versions and/or in print. The content of

4、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 the print of the Portable Document Fo

5、rmat (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 available at https:/portal.etsi.org/TB/ET

6、SIDeliverableStatus.aspx 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, electronic or mechanical,

7、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 Telecommunications Standa

8、rds Institute 2017. 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. oneM2M logo is protected

9、for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 583 V14.0.0 (2017-04)23GPP TS 32.583 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been d

10、eclared to ETSI. The information 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“, wh

11、ich is available from the ETSI 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

12、in ETSI SR 000 314 (or the updates 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 specification

13、s or reports using their 3GPP identities, 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

14、 terminology In the present document “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 allo

15、wed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 583 V14.0.0 (2017-04)33GPP TS 32.583 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and ab

16、breviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Architecture for HNB Management . 6g34.2 Functional Elements . 7g34.2.1 HNB Management System (HMS) . 7g34.2.1.1 Initial HNB Management System (HMS) . 7g34.2.1.2 Serving HNB Management System (HMS) 7g34.2.2 Security Gateway (SeGW) 7g34.2.2

17、.1 Initial Security Gateway (SeGW) . 8g34.2.2.2 Serving Security Gateway (SeGW) . 8g34.2.3 HNB Gateway (HNB-GW) . 8g35 Procedure Flows . 8g35.1 Discovery procedures (Mandatory) 8g35.1.1 Discovery procedures via HMS (initial) accessible on the MNO Intranet (Mandatory) . 9g35.1.2 Discovery procedures

18、via HMS (initial) accessible on the public Internet (Mandatory) 10g35.2 HNB Registration (Mandatory) 11g35.2.1 HNB registration Procedure (Mandatory) . 11g35.2.2 HNB IPSec IP address change procedure (Conditional Mandatory) 12g35.3 HNB Configuration Management (Mandatory) . 13g35.3.1 HNB configurati

19、on management by means of file download (Optional) . 14g35.3.2 HNB configuration management using RPC Set Parameter Value method (Mandatory) 15g35.4 HNB De-Provisioning (Mandatory) . 15g35.5 Alarm Reporting (Mandatory) 17g35.5.1 Alarm Reporting Mechanism Configuration (Mandatory) . 17g35.5.2 Alarm R

20、eporting Procedure (by RPC method) (Mandatory) 17g35.6 PM File Upload (Mandatory) . 18g35.6.1 PM File Upload Period Set Procedure (Mandatory) . 18g35.6.2 PM File Uploading Procedure (Mandatory) . 19g3Annex A (informative): Change history 20g3History 21g3ETSI ETSI TS 132 583 V14.0.0 (2017-04)43GPP TS

21、 32.583 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 the content

22、s 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 approved docum

23、ent 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 of a TS-fam

24、ily 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 (HNB) Operations, Administration, Maintenance and Provisioning (OAM Concepts an

25、d 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 for Type 1 interface HNB to HNB Management System (HMS)“. 3GPP TS 32.583: “Teleco

26、mmunications 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 management; Home Node B (HNB) Operations, Administration, Maintenance and Provisionin

27、g (OAM XML definitions for Type 1 interface HNB to HNB Management System (HMS)“. ETSI ETSI TS 132 583 V14.0.0 (2017-04)53GPP TS 32.583 version 14.0.0 Release 141 Scope The present document describes the procedure flows between HNB Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommu

28、nication management; Architecture“. 4 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name 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 Report 7

29、3GPP TS 25.401 Radio Access Network UTRAN Overall Description 8 3GPP TR 32.821: “Study of Self-Organizing Network (SON) related 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, Adm

30、inistration, Maintenance and Provisioning (OAM Information model for Type 1 interface HNB to HNB Management System (HMS)“. 11 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, the terms and definiti

31、ons 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 definition of the same term, if any, in TS 32.101 2, TS 32.102 3 and TS 21.905 1, in that order. 3.1 Definitions For the purposes of the present document, t

32、he terms and definitions given in TR 21.905 1 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 1. ETSI ETSI TS 132 583 V14.0.0 (2017-04)63GPP TS 32.583 version 14.0.0 Release 143.2 Abbreviations For the purpos

33、es of the present document, the following abbreviations apply: DNS Domain Name Server FTP File Transfer Protocol HMS Home NodeB Management System HNB Home NodeB HNB-GW Home NodeB Gateway HTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure IP Internet Protocol LAN Local Area N

34、etwork MNO Mobile Network Operator RNC Radio Network Controller RPC Remote Procedure Call SeGW Security Gateway SSL Secure Socket LayersFTP Secure File Transfer Protocol TLS Transport Layer Security URL Unified Resource Locator 4 Architecture for HNB Management 4.1 HNB OAM functional architecture Th

35、is section provides the 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 w

36、ith an integrated HNB functionality. The 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

37、 MNO domain. ETSI ETSI TS 132 583 V14.0.0 (2017-04)73GPP TS 32.583 version 14.0.0 Release 14SeGSecGW HNB GW StandaloneHN(TR-069) Manager File Server TR-069 File transfer protocol IPSec Tunnel IPSec Tunnel Type 1 interface HNB (TR-069) Agent File transfer protocol TR-069 HMS Standalone HNB Co-located

38、 BB device Figure 4.1.1-1: Architecture for HNB Management 4.2 Functional Elements 4.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

39、 functionalities to the HNB. The file server may be used for file upload or download, as instructed by TR-069 manager 4.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-G

40、W). 4.2.1.2 Serving HNB Management System (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 discovery. 4.2.2 Security Gat

41、eway (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. ETSI ETSI TS 132 583 V14.0.0 (2017-04)83GPP TS 32.583 version 14.0.0 Release 144.2.2.1 Initial Security Gateway (SeGW) The URL of the Initial SeGW may be

42、 factory programmed in the HNB so as to allow initial establishment of an IPSec security association and communication with the initial HMS. 4.2.2.2 Serving Security Gateway (SeGW) Terminates IPSec security association and implements a forwarding function to allow forwarding IP packets upstream and

43、downstream: - Downstream: packets are forwarded on appropriate IPSec tunnels towards the HNB based on their destination IP addresses - Upstream: forwarding IP traffic to the appropriate HNB-GW, HMS or other network elements based on destination IP addresses 4.2.3 HNB Gateway (HNB-GW) Terminates Iuh

44、from HNB. Appears as a RNC to the existing Core network using existing Iu interface. 5 Procedure Flows 5.1 Discovery procedures (Mandatory) When the HNB is initially powered up, it shall contact with HMS (initial) to discover HNB-GW for the first step. HMS (initial) assigns the HNB corresponding loc

45、al access information of Security Gateway (serving), HMS (serving) and optionally HNB-GW according to the HNBs location information. The HNB-GW information shall be provided either by the HMS (initial) or the HMS (serving). The HNB is pre-configured with the address information of HMS (initial) and

46、Security Gateway (initial) and with an operator trusted root CA certificate allowing the validation of the certificate presented by HMS (as TLS server) or Security Gateway (as IKEv2 responder), while HMS (serving) may be physically different from HMS (initial). The address information of Security Ga

47、teway (initial) should be consistent with that in the certificate presented by Security Gateway (initial). When authentication between HNB and HMS (initial) is needed, the address information of HMS (initial) should be consistent with that in the certificate presented by HMS (initial). There are two

48、 scenarios that need to be distinguished for the HNB-GW discovery: - HMS (initial) is accessible via IPSec to the Security Gateway (initial) on the MNO Intranet. - HMS (initial) is accessible on the public Internet. ETSI ETSI TS 132 583 V14.0.0 (2017-04)93GPP TS 32.583 version 14.0.0 Release 145.1.1

49、 Discovery procedures via HMS (initial) accessible on the MNO Intranet (Mandatory) Figure 5.1.1-1: HNB-GW discovery via HMS (initial) accessible on the MNO Intranet 1. The HNB establishes a LAN connectivity to the Internet when it is initially powered up. 2. The HNB initiates a process to get IP address of Security Gateway (initial). 2.1 The HNB requests outer DNS (Domain Name Server) server for the address of Security Gateway (initial)s URL. 2.2.DNS responds to the HNB with the IP addresses of Security Gateway (initial) URL. 2.3 The secur