ETSI TS 122 220 V15.0.0 (2019-07)

Universal Mobile Telecommunications System (UMTS); Service requirements for Home Node B (HNB) and Home eNode B (HeNB) (3GPP TS 22.220 version 15.0.0 Release 15)

RTS/TSGS-0122220vf00

General Information

• Status: Published
• Publication Date: 22-Jul-2019
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 23-Jul-2019

Standards Content (Sample)

ETSI TS 122 220 V15.0.0 (2019-07)






TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
Service requirements for Home Node B (HNB)
and Home eNode B (HeNB)
(3GPP TS 22.220 version 15.0.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 1 ETSI TS 122 220 V15.0.0 (2019-07)



Reference
RTS/TSGS-0122220vf00
Keywords
UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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:
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 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 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 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.

© ETSI 2019.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 2 ETSI TS 122 220 V15.0.0 (2019-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
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 22.220 version 15.0.0 Release 15 3 ETSI TS 122 220 V15.0.0 (2019-07)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 General . 7
4.1 Description . 7
5 Common requirements for Home NodeB / Home eNodeB . 7
5.1 HNB and HeNB Installation, identification and location requirements . 7
5.2 OA&M Requirements . 8
5.3 Access Control requirements . 8
5.3.1 General . 8
5.3.2 Closed Subscriber Group . 9
5.4 Display requirements . 10
5.4.1 CSG Type . 10
5.4.2 HNB Name . 10
5.5 Mobility Aspects for Home NodeB and Home eNodeB . 11
5.5.1 PLMN selection . 11
5.5.2 Idle-mode operation . 11
5.5.3 Connected mode operation . 11
5.5.4 Manual CSG selection . 11
5.6 Services support . 12
5.6.1 General . 12
5.6.2 Emergency services . 12
5.6.3 IMS Interworking . 12
5.7 Local IP Access (LIPA) . 12
5.7.1 Description . 12
5.7.2 General requirements . 13
5.8 Managed Remote Access to home based network . 14
5.9 Selected IP Traffic Offload (SIPTO) at Local Networks . 14
5.10 UICC and H(e)NB . 15
5.11 Void . 15
5.11.1 Void . 15
5.11.2 Void . 15
6 Requirements for Home NodeB . 15
6.1 Access Control . 15
6.2 Void . 16
7 Requirements for Home eNodeB . 16
7.1 Services support . 16
7.1.1 Void . 16
8 Quality of Service . 16
8.1 General . 16
8.2 Admission Control . 16
9 Security and privacy . 16
9.1 General . 16
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 4 ETSI TS 122 220 V15.0.0 (2019-07)
9.2 Security Requirements . 16
9.3 Privacy . 16
10 Charging Aspects . 17
Annex A (informative): Use cases . 18
Annex B (informative): Clarification of H(e)NB Access Modes . 21
Annex C (informative): Overview of identifiers and names. . 22
Annex D (informative): Change history . 25
History . 28


ETSI

---------------------- Page: 5 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 5 ETSI TS 122 220 V15.0.0 (2019-07)
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
In Rel-8, 3GPP has specified the basic functionalities for the support of Home Node B (HNB) and Home eNodeB
(HeNB). The requirements for these basic functionalities were captured in TS 22.011.
From Rel-9 onward, it has been agreed to consolidate all the requirements from Rel-8 and further requirements for HNB
and HeNB in a new TS, which is this specification.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 6 ETSI TS 122 220 V15.0.0 (2019-07)
1 Scope
This specification defines the service requirements for the basic functionalities for the support of Home NodeB (HNB)
and Home eNodeB (HeNB) – jointly referred to as H(e)NB – and the further functionalities that will enable the mobile
operators to provide more advanced services as well as improving the user experience.
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] Void
[3] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1".
[4] 3GPP TS 22.101: "Service Aspects; Service Principles".
[5] TR-069 Amendment 2: "CPE WAN Management Protocol v1.1, Broadband Forum”, viewable at
http://www.broadband-forum.org/technical/download/TR-069Amendment2.pdf
[6] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell
reselection in connected mode”.
[7] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode".
[8] 3GPP TS 22.115: "Service aspects; Charging and billing".
[9] 3GPP TS 22.268: "Public Warning System (PWS) requirements".
[10] 3GPP TS 22.011: "Service accessibility".
[11] 3GPP TS 31.115: "Secured packet structure for (Universal) Subscriber Identity Mobule (U)SIM
Toolkit applications".
[12] 3GPP TS 31.116: "Remote APDU Structure for (U)SIM Toolkit applications".
3 Definitions, symbols and abbreviations
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].
Closed access mode: H(e)NB provides services only to its associated CSG members.
Home based network: An IP based network in the same premises as, and is connected to, the H(e)NB.
Hybrid access mode: H(e)NB provides services to its associated CSG members and to non-CSG members.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 7 ETSI TS 122 220 V15.0.0 (2019-07)
Open access mode: H(e)NB operates as a normal NodeB or eNodeB.
HNB: A HNB is a Customer-premises equipment that connects a 3GPP UE over UTRAN wireless air interface to a
mobile operator’s network using a broadband IP backhaul.
HeNB: A HeNB is a Customer-premises equipment that connects a 3GPP UE over EUTRAN wireless air interface to a
mobile operator’s network using a broadband IP backhaul.
H(e)NB Gateway: H(e)NB Gateway is a mobile operator’s equipment (usually physically located on mobile operator
premises) through which the H(e)NB gets access to mobile operator’s core network.
H(e)NB Hosting Party: A H(e)NB Hosting Party has a contractual relationship with the operator, related to the
provision of access to the operator’s network via one or more H(e)NBs.
NOTE: A H(e)NB Hosting Party is likely to have the billing relationship with the operator. A H(e)NB Hosting
Party will typically be the “lead” user in a household but could be e.g. the corporate IT manager in an
enterprise context.
H(e)NB Subsystem: A H(e)NB Subsystem consists of the H(e)NB and the H(e)NB Gateway.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
CSG Closed Subscriber Group
HNB Home NodeB
HeNB Home eNodeB
H(e)NB HNB and HeNB
4 General
4.1 Description
Access to 3G and evolved 3G (EPS) services may be provided via UTRAN or E-UTRAN cellular base stations
belonging to e.g. domestic, business, commercial enterprises. This type of access may be provided by the PLMN by
means of HNB and HeNB (jointly referred to as H(e)NB). The H(e)NB provides services either only to a Closed
Subscriber Group (CSG) or to other mobile subscribers too. The H(e)NB is connected to the mobile operator core
network using IP via any suitable access technology.
5 Common requirements for Home NodeB / Home
eNodeB
5.1 HNB and HeNB Installation, identification and location
requirements
-   H(e)NB shall have a unique equipment identity.
- All the H(e)NBs serving the same CSG share the same unique (within the PLMN) identity called CSG Identity.
NOTE: CSGs of different PLMNs are considered different, even if the PLMNs are indicated to the UE as
"equivalent PLMNs" [10].
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 8 ETSI TS 122 220 V15.0.0 (2019-07)
- It shall be possible to support at least 125 million CSG Identities within a PLMN of an operator.
- The radio transmitter of a H(e)NB shall not be activated until configured and authorised by the operator.
-  When installing, provisioning, configuring or re-configuring an H(e)NB the operator shall be able to:
- verify the H(e)NB's identity.
- obtain the geographical location of the H(e)NB.
NOTE: The scenario where a H(e)NB is connected to one operator’s network and later changed to another
operator’s network is not required.
- The operator shall be able to determine that the H(e)NB is installed and operated in accordance with all relevant
regulatory requirements.
- The operator shall be able to configure the settings of the H(e)NB. In the case where the H(e)NB has detrimental
impact on the spectrum usage, the H(e)NB can be set to out-of-service by the operator.
- Installation and activation of a new H(e)NB shall require no reconfiguration of the operator's network.
- The impact of H(e)NB on the core network should be minimised.
5.2 OA&M Requirements
- H(e)NB shall support the automatic discovery of an operator’s management platform.
- It shall be possible to make use of the operator’s management platform to carry out OA&M functions for
H(e)NB. The management connection between H(e)NB and the operator's management platform shall be end-
to-end secure.
- H(e)NB shall support OA&M procedures which allow the operator to remotely configure the H(e)NB, deploy
software upgrades, detect and report changes in RF conditions and perform general OA&M tasks. The OA&M
procedures shall be as closely aligned as possible with those that are commonly used in broadband access
networks such as defined in TR-069 Amendment 2 [5].
- If the connection between H(e)NB and the rest of the operator network is out of service, then it shall be possible
within an operator’s defined time period for the H(e)NB to deactivate the air-interface.
- When the H(e)NB Hosting Party authentication is required by the MNO, the H(e)NB shall not activate the air-
interface unless the authentication of the H(e)NB Hosting Party has been performed successfully.
5.3 Access Control requirements
5.3.1 General
- Subject to operator and H(e)NB Hosting Party agreement, the operator shall be able to configure the H(e)NB
with open, hybrid or closed access mode.
- When the H(e)NB is configured for open access mode, it shall be possible for the H(e)NB to provide services to
subscribers of any PLMN, subject to roaming agreement.
- When the H(e)NB is configured for hybrid access mode, it shall be possible for the H(e)NB to provide services
to:
- its associated CSG members, and
- subscribers of any PLMN not belonging to its associated CSG, subject to roaming agreement.
- When the H(e)NB is configured for closed access mode, only users that belong to its associated CSG shall be
able to obtain services.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 9 ETSI TS 122 220 V15.0.0 (2019-07)
- CSG members may include subscriber of any PLMN subject to roaming agreement, defined as HPLMN CSG
Roaming.
- The VPLMN may support VPLMN Autonomous CSG Roaming by providing CSG membership to the roaming
subscriber without exchanging any CSG specific information with the HPLMN. The VPLMN shall disable
VPLMN Autonomous CSG Roaming on a per HPLMN basis if requested by the home operator.
NOTE: VPLMN Autonomous CSG Roaming and HPLMN CSG Roaming can be active in the same VPLMN
- The CSG membership granted to the subscriber during his stay in the VPLMN may be retained by the VPLMN
(e.g. in case the subscriber moves to another PLMN and subsequently returns to the VPLMN).
5.3.2 Closed Subscriber Group
- The CSG manager shall be able, under the operator supervision, to add, remove and view CSG membership
NOTE: the interaction of the user with the application that manages the Allowed CSG Lists is out of scope of 3GPP
(e.g. Web interface).
- For each subscriber, the network maintains a single CSG list containing the CSG identities that the subscriber is
allowed to use.
- The UE shall contain a list of allowed CSG identities (Allowed CSG List). It shall be possible to store the
Allowed CSG List in the USIM. When available, the list on the USIM shall be used. It shall be possible for both,
the operator and the UE, to modify the Allowed CSG List.
- The UE shall allow the user to introduce new CSGs to the Allowed CSG List by means of manual CSG selection
only.
- The UE shall maintain an operator-controlled list of allowed CSG identities (Operator CSG list). It shall be
possible to store the Operator CSG list in the USIM. When available, the list on the USIM shall be used. It shall
be possible for the operator to modify the Operator CSG List.
- The two lists are maintained independently from each other. A change in the Operator CSG list shall not trigger
the UE to modify the Allowed CSG list to reflect such change automatically.
- Except during manual CSG selection, all CSG cells belonging to a CSG identity not included in the Allowed
CSG List or Operator CSG list shall be considered not suitable by the UE (“not suitable” as specified in TS
25.304 [6] and TS 36.304 [7]).
- Each CSG identity shall be associated to a subscriber group which identifies the subscribers allowed to access
the CSG.
- When the subscriber group is updated, the affected UE shall be informed accordingly.
- For temporary members, it shall be possible to limit the period of time during which the subscriber is considered
a member of a CSG (granted access rights). It shall be possible to configure a time period for each temporary
member.
- The time period shall be configurable by the CSG manager and/or the operator operating the CSG and shall span
from 1 decihour to several days. Unlimited membership to the CSG is allowed.
- When a CSG is no longer considered available to provide services, except for emergency calls (i.e. due to time
period expiry or removal of the CSG membership), it shall be possible to continue the established
communication in another cell not belonging to this CSG.
- In hybrid access mode when services cannot be provided to a CSG member due to a shortage of H(e)NB
resources it shall be possible to continue the established communication of non-CSG members in another cell.
- In hybrid access mode, to minimise the impact on CSG members from established communication of non-CSG
members, it shall be possible for the network to allow the data rate of established PS communication of non-CSG
members to be reduced.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 22.220 version 15.0.0 Release 15 10 ETSI TS 122 220 V15.0.0 (2019-07)
5.4 Display requirements
5.4.1 CSG Type
The CSG Type is an indicator provided by the UE that is configured by the operator.
- It shall be possible for the operator to associate a CSG identity in the UE’s Allowed CSG List or the Operator
CSG List with a CSG Type. Therefore, it is possible that a CSG identity stored in different UEs may either be
associated with the same CSG Type or with different CSG Types.
NOTE: The CSG Type allows, for example, information on the applied billing regime to be given to the user.
- When a UE camps on a cell with a CSG identity that is part of the UE’s Allowed CSG List and or the Operator
CSG List has an associated CSG Type, a UE that has a display capability shall provide the user with the
associated CSG Type. A UE that does not have a display capability may provide the CSG Type by other means,
e.g. voice notification.
- If the CSG Type for a CSG identity has not been configured in the UE, the UE may provide the HNB Name
instead. In this case, the user is notified that the UE is providing the HNB Name rather than CSG Type.
- It shall be possible to store the CSG Type in the USIM. As an option, the CSG Type may be stored in the ME.
If the CSG Type is present in the USIM, a CSG Type stored in the ME shall be ignored. If the CSG Type is
present in the Operator CSG list, a CSG Type present in the Allowed CSG list shall be ignored.
- The CSG Type shall be stored in text and/or graphical format. When the CSG Type has a text component, the
CSG Type text length shall not exceed 12 characters in any language.
5.4.2 HNB Name
HNB Name is a common name referring to HNB/HeNB as defined in TR 21.905 [1].
- It shall be possible for a CSG cell and for a hybrid cell to broadcast a HNB Name in free text format. The UE
may display the HNB Name when camping on the cell where it is broadcasted. The HNB Name, if broadcasted
or stored in the UE, shall be available to the user during manual CSG selection. The HNB Name shall be
configurable by the operator or the H(e)NB Hosting Party at the discretion of the operator.
- The HNB Nam
...