ETSI TS 122 129 V15.0.0 (2018-07)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Handover requirements between UTRAN and GERAN or other radio systems (3GPP TS 22.129 version 15.0.0 Release 15)

RTS/TSGS-0122129vf00

General Information

• Status: Published
• Publication Date: 12-Jul-2018
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 13-Jul-2018

Standards Content (Sample)

ETSI TS 122 129 V15.0.0 (2018-07)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Service aspects;
Handover requirements between UTRAN
and GERAN or other radio systems
(3GPP TS 22.129 version 15.0.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 1 ETSI TS 122 129 V15.0.0 (2018-07)



Reference
RTS/TSGS-0122129vf00
Keywords
GSM,LTE,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 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
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 2018.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks 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 GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 2 ETSI TS 122 129 V15.0.0 (2018-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.
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
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.129 version 15.0.0 Release 15 3 ETSI TS 122 129 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
1.1 Situations in which Service Requirements apply . 6
2 References . 7
3 Definitions and Abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 General Principles governing service continuity . 8
4.0 General Principles for service continuity . 8
4.1 Service Continuity Scenarios . 8
4.2 Service Continuity requirements . 8
4.2.1 Service continuity for CS . 8
4.2.2 Service continuity for GPRS . 9
4.2.3 Service continuity for IM Services . 9
4.3 General Operational Considerations . 9
4.3.1 Coverage environment . 9
4.3.2 Inter PLMN Handover Issues . 9
4.3.3 Charging and Network Management . 10
4.3.4 Cost and efficiency . 10
4.3.5 Security . 10
4.4 Performance Requirements . 10
4.4.1 Temporary degradation of service caused by handover . 10
5 Requirements for Handover . 10
5.1 Handover due to UE Movement . 10
5.2 Handover due to negotiated service requirement . 10
5.3 Handover between Radio Access Modes . 11
5.4 Cell capacity . 11
5.5 Handover of a Multicall . 11
5.6 Access Rights . 11
5.7 Handover for shared networks . 11
6 Requirements for Handover from UTRAN to GERAN . 12
6.1 Operational Requirements . 12
6.1.2 GERAN bands . 12
6.2 Performance Requirements . 12
6.2.1 Detection Time of Potential GERAN Handover Candidates . 12
6.2.2 Number of GERAN handover candidates to detect . 12
6.2.3 Probability of Connection Loss . 12
6.3 Specific Requirements for Individual Services from UTRAN to GERAN . 12
6.3.1 Speech . 12
6.3.2 Short Message Service . 12
6.3.3 Cell Broadcast . 12
6.3.4 USSD . 13
6.3.5 Facsimile . 13
6.3.6 Data Bearer Services . 13
6.3.6.1 Circuit Switched Data . 13
6.3.6.2 Packet Switched Data . 13
6.3.7 Supplementary Services . 13
6.4 Requirements on multiple bearer services handover from UTRAN to GERAN . 13
7 Requirements for Handover from GERAN to UTRAN . 13
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 4 ETSI TS 122 129 V15.0.0 (2018-07)
7.1 Operational Requirements . 13
7.1.2 GERAN bands . 13
7.2 Performance Requirements . 14
7.3 Specific Requirements for Individual Service Handover from GERAN to UTRAN . 14
7.3.1 Speech . 14
7.3.2 Short Message Service . 14
7.3.3 Cell Broadcast . 14
7.3.4 USSD . 14
7.3.5 Facsimile . 14
7.3.6 Data Bearer Services . 14
7.3.6.1 Circuit Switched Data . 14
7.3.6.2 Packet Switched Data . 14
7.3.7 Supplementary services . 14
7.4 Requirements on multiple bearer services handover from GERAN to UTRAN . 14
8 Cross Phase Compatibility for this release . 15
8.1 Compatibility with Existing Specifications . 15
8.2 Compatibility with Future 3GPP specifications . 15
8.2.1 Requirements for Service Capabilities . 15
8.2.2 Inter PLMN Handover Issues . 15
8.2.3 Handover between Environments . 16
8.3 Support of Multicall with Simultaneous Voice Calls . 16
Annex A (informative): Illustration of elements in inter-PLMN handover . 17
Annex B (informative): Open Points on Inter-Operator Handover . 18
B.2 Selection of Target Cells for Handover . 18
B.3 Network Information Exchange . 18
B.4 Service Requirements . 18
B.5 Billing, Accounting and Charging Requirements . 18
Annex C (informative): Change history . 19
History . 21

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 5 ETSI TS 122 129 V15.0.0 (2018-07)
Foreword
This Technical Specification has been produced by the 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 this TS, 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 specification;
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 6 ETSI TS 122 129 V15.0.0 (2018-07)
1 Scope
The scope of this document includes service requirements for handover maintaining continuity of service to a wireless
terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This
functionality is called "handover". Handover can also occur due to change of radio resource providing a service without
necessarily any change of the base stations involved. In particular, when the radio resources providing a service change
from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover.
Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and
between UTRAN and GERAN.
It is a key requirement to allow for dual or multi-mode terminals to handover traffic from UTRAN to GERAN and vice
versa. This document describes the service requirements for intra- and inter- system handover.
The following subject areas are within the scope of these service requirements:
- User perceived performance that may be influenced by handover;
- Operational requirements relating to handover;
- Security requirements.
The requirements set forth in this document are service requirements, in that they fulfil the following:
- The requirements are independent of the implementation of the UTRAN;
- The extent to which the requirements are met are in principle verifiable using observables that are not internal to
the UTRAN.
1.1 Situations in which Service Requirements apply
The service requirements in this document are as far as possible independent of the implementation. They therefore
apply to situations where handover would occur regardless of how the radio access network is implemented. Situations
envisaged are:
- Handover within UTRAN due to change of radio resource caused by UE movement between areas covered by
different transmitters;
- Handover within UTRAN due to change of UTRA radio access mode;
- Handover due to change of radio system.
It is possible that handover (i.e. change of radio resource) will occur in other situations, for example the technical
implementation of the UTRAN may necessitate it or O&M procedures initiated by the operator may force it.
Requirements for these situations are not within the scope of this document, with the exception of two remarks:
- Where the technical implementation of the UTRAN necessitates handover as a matter of normal operation (i.e.
not related to the above situations), then services shall in no way be degraded or adversely affected;
- The service requirements for handover occurring in situations such as O&M activity are outside the scope of this
document.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 7 ETSI TS 122 129 V15.0.0 (2018-07)
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 22.278: "Service requirements for the Evolved Packet System (EPS)"
3 Definitions and Abbreviations
3.1 Definitions
In addition to the following, abbreviations used in the present document are listed in TR 21.905 [1].
For the purposes of the present document, the following definitions apply:
Connection mode (for a bearer service): characterises the type of association between two endpoints as required by
the bearer service for the transfer of information. A bearer service is either connection-oriented or connectionless. In a
connection oriented mode, a logical association called connection needs to be established between the source and the
destination entities before information can be exchanged between them. Connection oriented bearer services lifetime is
the period of time between the establishment and the release of the connection.
Connectionless (for a bearer service): In a connectionless bearer, no connection is established beforehand between the
source and the destination entities; the source and destination network addresses need to be specified in each message.
Transferred information cannot be guaranteed of ordered delivery. Connectionless bearer services lifetime is reduced to
the transport of one message.
GERAN coverage: an area where mobile cellular services are provided by a GERAN in accordance with GERAN
specifications.
UTRAN coverage: an area where mobile cellular services are provided by a UTRAN in accordance with UTRAN
specifications.
Multi mode terminal: UE that can obtain service from at least one UTRA radio access mode, and one or more different
systems such as GERAN bands or possibly other radio systems such IMT-2000 family members.
Handover: The process in which the radio access network changes the radio transmitters or radio access mode or radio
system used to provide the bearer services, while maintaining a defined bearer service QoS.
Intra PLMN handover: Handover within the same network, i.e. having the same MCC-MNC regardless of radio
access system. Note: this includes the case of UTRAN <>GERAN handover where MCC-MNC are the same in both
cases.
Inter PLMN handover: Handover between different PLMNs, i.e. having different MCC-MNC.
Inter system handover: Handover between networks using different radio systems , e.g. UTRAN – GERAN.
UTRA Radio access mode: the selected UTRA radio access mode i.e. UTRA-FDD; UTRA-TDD.
nd rd
Radio system: the selected 2 or 3 generation radio access technology.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 8 ETSI TS 122 129 V15.0.0 (2018-07)
Service Continuity: The means for maintaining active services during changes in the coverage areas or their
characteristics without, as far as possible, the user noticing. Note that Service Continuity can be achieved by handover,
cell re-selection or other mechanisms.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
UE User equip me nt
4 General Principles governing service continuity
4.0 General Principles for service continuity
The general principles for service continuity described in this specification refer to service continuity within the
UTRAN, within the GERAN and between the UTRAN and GERAN. As a principle, the requirements on service
continuity characteristics should be according to the target network on which the service is maintained.
Service requirements for seamless mobility between multiple heterogeneous access systems beyond only UTRAN and
GERAN are contained within TS 22.278 [2].
4.1 Service Continuity Scenarios
Service continuity shall support the following scenarios:
1. Continuity of active CS services when moving within UTRAN, within GERAN and between UTRAN and
GERAN coverage areas.
2. Continuity of active GPRS sessions when moving within UTRAN, within GERAN and between UTRAN and
GERAN coverage areas.
3. Continuity of active IM Services when moving within UTRAN, within GERAN and between UTRAN and
GERAN coverage areas (that support those IM services).
Service continuity is not applicable for any call or session using resources specific to the source domain that cannot be
maintained using resources in the target domain.
4.2 Service Continuity requirements
For all scenarios, the specifications shall cover both service continuity within the same PLMN (intra-PLMN) and
between PLMNs (inter-PLMN), including the case where the PLMNs involved are operated by different network
operators.
It shall be possible for a user to roam between the different parts of a shared network without requiring any user
intervention. The user experience while roaming in a shared network shall be comparable to the user experience while
roaming in a non-shared network.
4.2.1 Service continuity for CS
The scenario numbers in this table refer to the scenarios in section 4.1.

To CS services

UTRAN GERAN
From CS UTRAN
Yes - Yes -
services Scenario 1 Scenario 1
GERAN Yes – Scenario 1 Yes – Scenario 1


ETSI

---------------------- Page: 9 ----------------------
3GPP TS 22.129 version 15.0.0 Release 15 9 ETSI TS 122 129 V15.0.0 (2018-07)
4.2.2 Service continuity for GPRS
Service continuity of GPRS sessions (conversation, streaming, interactive and background) is required within the
GERAN, within the UTRAN, and between the UTRAN and GERAN (scenario 2 in section 4.1 above).
Note: Service continuity for conversational, streaming and interactive GPRS sessions is not applicable to and
from GERAN Release 4 or earlier, due to the lack of support for the conversational, streaming and
interactive GPRS within GERAN Release 4 or earlier. In these cases, although the QoS required may not
be available in the target, the bearer shall be maintained as long as possible. If the QoS supported by
GERAN is not acceptable, the user/application may terminate the session.
4.2.3 Service continuity for IM Services
Service continuity of IM services is required within the GERAN, within the UTRAN, and between the UTRAN and
GERAN (scenario 3 in section 4.1 above).
Note: Service continuity of IM Services is not applicable to and from GERAN Release 4 or earlier as the IM
Services service classes are not supported by GERAN Release 4 or earlier. In these cases, although the
QoS required may not be available in the target, the bearer shall be maintained as long as possible. If the
QoS supported by GERAN is not acceptable, the user/application may terminate the session.
4.3 General Operational Considerations
4.3.1 Coverage environment
Mechanisms defined to support service continuity between different radio systems or radio access modes should
effectively cope with a number of coverage scenarios:
- Limited coverage in a 'sea' of coverage provided by another radio system or radio access mode, or vice versa;
- Selective operation at a geographical boundary, with extensive UTRAN coverage on one side and extensive
coverage from another radio system on the other side;
- Geographically co-located areas of UTRAN coverage and another radio system.
However the specifications should impose no restrictions or assumptions on how an operator might deploy or operate
the network in both GERAN and UTRAN.
4.3.2 Inter PLMN Handover Issues
Handovers to support service continuity between PLMNs should remain an optional feature to implement. It is
envisaged that handover would take place due to changing radio conditions caused e.g. by movement of the terminal
causing it to leave the coverage area of a PLMN.
The following networks may be involved with an inter-PLMN handover procedure. These con
...