|
TECHNICAL SPECIFICATIONION
LTE;
Telecommmunication management;
Home enhanced Node e B (HeNB) Operations, Admininistration,
Maintenance e and Provisioning (OAM&P);P);
Concepts and requiremements for Type 1 interface HeeNBN to HeNB
Managegement System (HeMS)
3GPP TS 32.5.591 version 13.0.0 Release 13 13
---------------------- Page: 1 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 1 ETSI TS 132 591 V13.0.0 (2016-03)
Reference
RTS/TSGS-0532591vd00
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 lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 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 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
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:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic 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 Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 2 ETSI TS 132 591 V13.0.0 (2016-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared 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", which 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 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 specifications 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
.
Modal verbs 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 allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 3 ETSI TS 132 591 V13.0.0 (2016-03)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 5
4 Concepts and background . 6
5 Business level requirements . 6
5.1 Requirements . 6
5.1.1 Configuration Management . 6
5.1.2 Performance Management . 7
5.1.3 Fault Management . 7
5.1.4 Security Management . 7
5.2 Actor roles . 7
5.3 Telecommunications resources . 7
5.4 High level use cases . 7
5.4.1 HeNB Energy Saving use cases . 7
6 Specification level requirements . 8
6.1 Requirements . 8
6.1.1 Configuration Management . 8
6.1.2 Performance Management . 9
6.1.3 Fault Management . 9
6.1.4 Security Management . 10
6.2 Actor roles . 11
6.3 Telecommunications resources . 11
6.4 Use cases . 11
6.4.1 Energy saving activation on selected network elements (Centralized ES) . 11
6.4.2 Deactivation of energy saving on selected network elements (Centralized ES ) . 12
6.4.3 Energy saving activation on selected network elements (Distributed ES) . 13
6.4.4 Energy saving deactivation on selected network elements (Distributed ES) . 14
Annex A (informative): Energy Saving use cases for HeNB . 15
A.1 UC1a: Capacity-Limited Networks . 15
A.2 UC 1b: Hybrid E-UTRAN Macro Cell and HeNB Cell Coverage . 16
Annex B (informative): Change history . 18
History . 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 4 ETSI TS 132 591 V13.0.0 (2016-03)
Foreword
rd
This Technical Specification has been produced by the 3 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 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 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 the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
rd
The present document is part of a TS-family covering the 3 Generation 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&P); Concepts and requirements for Type 1 interface HeNB
to HeNB Management System (HeMS)".
3GPP TS 32.592: "Telecommunications management; Home eNode B (HeNB) Operations, Administration,
Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HeNB to
HeNB Management System (HeMS) ".
3GPP TS 32.593: "Telecommunications management; Home eNode B (HeNB) Operations, Administration,
Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HeNB to HeNB
Management System (HeMS)".
3GPP TS 32.594: "Telecommunications management; Home eNode B (HeNB) Operations, Administration,
Maintenance and Provisioning (OAM&P); Data definitions for Type 1 interface HeNB to HeNB
Management System (HeMS)".
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 5 ETSI TS 132 591 V13.0.0 (2016-03)
1 Scope
The present document describes the concepts and requirements of OAM for Home eNodeB (HeNB). The requirements
captured in this document shall be met via Type 1 interface between HeNB and HeMS.
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-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-specific reference implicitly refers to the latest version of that document in the same
Release 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] TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum.
[5] 3GPP TS 32.435: "Performance Measurement, eXtensible Markup Language (XML) file format
definition".
[6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Alarm Integration
Reference Point (IRP): Information Service (IS) ".
[7] 3GPP TS 22.220: " Service requirements for Home Node B (HNB) and Home eNode B (HeNB)".
[8] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)".
[9] 3GPP TS 32.551: " Energy Saving Management (ESM); Concepts and requirements ".
[10] 3GPP TR 32.826: " Study on Energy Savings Management (ESM) ".
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 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, the 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].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
HeMS Home eNodeB Management System
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 6 ETSI TS 132 591 V13.0.0 (2016-03)
HeNB Home eNodeB
4 Concepts and background
Home eNodeB has the following characteristics:
- The quantity of Home eNodeBs is likely to be large
- There may be many Home eNodeB vendors
- The location of Home eNodeB 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
eNodeB over a Type 1 interface.
5 Business level requirements
5.1 Requirements
5.1.1 Configuration Management
REQ-OAMP_CM-CON-001 The HeNB 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 HeMS.
REQ-OAMP_CM-CON-002 The HeNB 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 HeMS.
REQ-OAMP_CM-CON-003 The HeNB 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-004 The HeNB 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 HeNB auto-configuration function should be adaptive to react to change in the
network and changes in the radio environment.
REQ-OAMP_CM-CON-006 The operator shall be able to remotely reboot the HeNB.
REQ-OAMP_CM-CON-007 The operator shall be able to remotely start/stop the radio transmission of the HeNB.
REQ-OAMP_CM-CON-008 In case IPsec is used, the system should be engineered to ensure that the HeNB IP
address changes as minimally as possible.
REQ-OAMP_CM-CON-009 The operator shall be able to remotely reconfigure the frequency and radio bandwidth of
HeNB to adapt to changes in the radio environment and required bandwidth.
REQ-OAMP_CM-CON-010 The HeNB should allow configuration of the IPsec or non-IPsec usage option based on
the operator"s policy [8].
REQ-OAMP_CM-CON-011 The operator shall be able to activate/deactivate energy savings on one or multiple
HeNBs in the network [9][10].
REQ-OAMP_CM-CON-012 The operator shall be able to configure energy saving policy for the one or more HeNBs
in the network [9][10].
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 7 ETSI TS 132 591 V13.0.0 (2016-03)
5.1.2 Performance Management
REQ-OAMP_PM-CON-001 The HeNB may have the capability to collect its performance related data.
REQ-OAMP_PM-CON-002 The HeNB shall send performance data based on operator configured policy.
REQ-OAMP_PM-CON-003 Operator shall be able to retrieve performance data file from the HeNB.
5.1.3 Fault Management
REQ-OAMP_FM-CON-001 The HeNB shall support Fault Management to enable the operator to monitor and
manage the HeNB.
REQ-OAMP_FM-CON-002 The HeNB shall provide alarm 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 HeNB 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 Telecommunications resources
Not defined in this version.
5.4 High level use cases
5.4.1 HeNB Energy Saving use cases
UC1a: Capacity-Limited Networks
Capacity-limited networks are normally dimensioned to cope with peak time traffic demand and can hence be under-
utilized in off-peak times peak time traffic demand e.g. at certain hours of the night, when the overall load as well as the
load distribution onto the different cells may differ significantly from peak times.
For energy saving management in such networks, the objective is therefore to adapt the network to these changing
conditions by activating energy saving on selected cells. One approach is to concentrate the load into a few selected
cells that remain active during low traffic demand periods with increased coverage area and to deactivate the remaining
less loaded cells.
UC1b: Hybrid E-UTRAN Macro Cell and HeNB Cell Coverage
A variation of the above use case is to have all cells in the building can be shut down. The overlay macro cell can
provide coverage for all the HeNBs in that area.
Depending on the architecture, energy saving decisions and corresponding state transfers are made by network elements
(or element / domain managers) or by network management systems.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.591 version 13.0.0 Release 13 8 ETSI TS 132 591 V13.0.0 (2016-03)
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 HeNB configuration shall be administered by the HeMS utilising the TR-069 CWMP
Protocol, reference [4].
REQ-OAMP_CM-FUN-002 HeMS shall be able to reboot the HeNB.
REQ-OAMP_CM-FUN-003 HeMS shall have remote access to the HeNB to start/stop the radio transmission.
REQ-OAMP_CM-FUN-004 HeMS shall have remote access to the HeNB to start/stop the radio transmission on the
frequencies specified by HeMS.
REQ-OAMP_CM-FUN-005 HeMS shall maintain the configuration data of the HeNB.
REQ-OAMP_CM-FUN-006 When the HeNB is initially powered up and connected to the HeMS, HeMS shall send
the initially needed configuration data to the HeNB.
REQ-OAMP_CM-FUN-007 If the inner IPsec tunnel IP address of the HeNB changes and HeNB is connected to
HeMS via IPsec Tunnel then the HeNB shall notify the HeMS using TR-069.
REQ-OAMP_CM-FUN-008 The HeMS shall specify which parameters it needs to be notified of when the HeNB
changes their values through auto-configuration. The HeNB shall notify the HeMS of changes in the values of any such
auto-configured parameters.
REQ-OAMP_CM-FUN-009 The HeNB shall inform the HeMS of its ability to auto-configure parameters or groups of
parameters that are relevant to the HeMS.
REQ-OAMP_CM-FUN-010 HeMS shall be able to specify a value, or a valid range of values, for any parameter that
is auto-configurable by the HeNB.
REQ-OAMP_CM-FUN-011 Configuration management capability for the HeNB shall be supported by means of TR-
069 RPCs SetParameterValues, AddObject and DeleteObject . Optionally a bulk configuration management file may be
supported. In this case the TR-069 manager uses the RPC download method to trigger a CM file download from a file
server.
REQ-OAMP_CM-FUN-012 The HeNB shall provide a capability allowing
...