ETSI TS 122 278 V14.5.0 (2018-10)

LTE; Service requirements for the Evolved Packet System (EPS) (3GPP TS 22.278 version 14.5.0 Release 14)

RTS/TSGS-0122278ve50

General Information

• Status: Published
• Publication Date: 03-Oct-2018
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 04-Oct-2018

Standards Content (Sample)

TECHNICAL SPECIFICATION
LTE;
Service requirements for the Evolved Packet System (EPS)
(3GPP TS 22.278 version 14.5.0 Release 14)

3GPP TS 22.278 version 14.5.0 Release 14 1 ETSI TS 122 278 V14.5.0 (2018-10)

Reference
RTS/TSGS-0122278ve50
Keywords
LTE
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
3GPP TS 22.278 version 14.5.0 Release 14 2 ETSI TS 122 278 V14.5.0 (2018-10)
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
3GPP TS 22.278 version 14.5.0 Release 14 3 ETSI TS 122 278 V14.5.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 General description. 9
4.1 Objectives . 9
5 High-level requirements – user and operational aspects . 10
5.0 General . 10
5.1 Requirements for Fixed Mobile Interworking . 11
5.2 Requirements for Fixed Mobile Convergence . 12
5.3 Requirements for Interworking with Data Application Providers . 12
6 Basic capabilities . 13
6.1 Support of IP traffic . 13
6.1.1 Support of increased IP traffic demand. 13
6.1.2 Void . 13
6.1.3 Void . 13
6.1.4 Support of basic IP connectivity . 13
6.1.5 Support of IP multicast service . 13
6.2 IP session control . 13
6.3 Quality of Service . 14
6.4 Support of Multicast and Broadcast Services . 15
6.5 Support of Emergency Calls . 15
6.6 Differentiated paging for voice over E-UTRAN terminations . 15
6.7 IoT resource efficiency . 15
7 Multi-access and seamless mobility . 16
7.1 Mobility management . 16
7.1.1 Heterogeneous access systems mobility . 16
7.1.2 Local breakout . 16
7.1.3 Fixed Access Systems . 17
7.1.4 Service continuity . 17
7.1.4.1 General . 17
7.1.4.2 Service continuity at domain and RAT change for TS 11, TS 12 and equivalent PS service . 17
7.1.4.2A Voice Call Service continuity between 3GPP defined RATs and non 3GPP defined RATs . 18
7.1.4.3 Service continuity between E-UTRAN and 3GPP2 accesses on Evolved Packet Core . 18
7.1.4.4 Service continuity between 3GPP and WiMAX access on Evolved Packet Core . 18
7.1.5 Access network discovery . 18
7.1.6 Steering of access . 18
7.1.7 CS fallback. 19
7.1.7.1 General . 19
7.1.7.2 Roaming in a VPLMN not supporting CS fallback . 19
7.1.8 Service Reachability . 19
7.2 IFOM Service requirements . 20
7A Requirements for Proximity Services . 21
7A.0 General . 21
7A.0A Feature description (Informative) . 21
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 4 ETSI TS 122 278 V14.5.0 (2018-10)
7A.0A.1 ProSe Discovery . 21
7A.0A.2 ProSe Communication . 21
7A.1 General Requirements for Proximity Services . 21
7A.2 Public Safety Specific Requirements for Proximity Services. 24
7A.3 ProSe-assisted WLAN direct communication . 26
7B Void . 28
7B.1 Void . 28
7B.2 Void . 28
7C Void . 28
7C.1 Void . 28
7C.2 Void . 28
8 Performance requirements for the Evolved Packet System. 28
9 Security and privacy . 29
9.1 General . 29
9.2 Security requirements . 29
9.3 Privacy requirements . 29
9.4 ProSe Security, Authorization and Privacy Requirements . 29
9.5 Void . 31
10 Charging Aspects . 31
Annex A (informative): Requirements for further study . 32
A.1 Management of access networks . 32
A.2 Use cases for Fixed Mobile Convergence . 32
Annex B (Normative): Void . 34
Annex B1 (Informative): Interworking between Mobile Operators and Data Application
Providers . 35
B1.1 Scenarios . 35
B1.2 Use cases . 37
B1.2.1 Use cases for owned / collaborated scenarios. . 37
B1.2.2 Use cases for non-collaborated scenarios. . 38
B1.2.2.1 UE initiates and requests MNO for preferential traffic handling . 38
B1.2.2.2 UE initiates and Data Application Provider requests MNO for preferential traffic handling . 39
Annex B2 (Informative): Service Reachability . 40
B2.1 Use case: Blocking Service Reachability . 40
B2.1.1 Description . 40
B2.1.2 Pre-conditions . 40
B2.1.3 Service Flow . 40
B2.1.4 Post-conditions . 40
Annex C (informative): Change history . 41
History . 45

ETSI
3GPP TS 22.278 version 14.5.0 Release 14 5 ETSI TS 122 278 V14.5.0 (2018-10)
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
To ensure competitiveness in a longer time frame an evolution of the overall 3GPP system needs to be considered.
This document compiles requirements to ensure that an Evolved Packet System can cope with the rapid growth in IP
data traffic and demanding requirements for new multimedia type of applications in terms of performance and quality,
delivered to the user, whilst at the same time enabling cost effective deployment and operation.
The Evolved Packet System is characterised by:
- Reduced latency
- Higher user data rates equating to broadband performance
- Improved system capacity and coverage
- Lower operational costs
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 6 ETSI TS 122 278 V14.5.0 (2018-10)
1 Scope
The present document describes the service requirements for the Evolved Packet System.
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 TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[2] 3GPP TS 21.905: "Vocabulary for 3GPP specifications".
[3] 3GPP TS 22.258: "Service Requirements for the All-IP Network (AIPN); Stage1".
[4] 3GPP TR 25.913: "Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-
UTRAN)".
[5] 3GPP TS 22.115: "Service aspects; Charging and billing".
[6] ETSI TS 102 250-1: "Speech Processing, Transmission and Quality Aspects (STQ); QoS aspects
for popular services in GSM and 3G networks: Part 1: Identification of Quality of Service
aspects".
[7] 3GPP TR 23.882: "3GPP system architecture evolution (SAE): Report on technical options and
conclusions".
[8] C.S0001-A Introduction to cdma2000 Standards for Spread Spectrum Systems - Release A.
[9] C.S0002-A Physical Layer Standard for cdma2000 Spread Spectrum Systems - Release A.
[10] C.S0003-A Medium Access Control (MAC) Standard for cdma2000 Spread Spectrum Systems -
Release A addendum 2.
[11] C.S0004-A Signaling Link Access Control (LAC) Specification for cdma2000 Spread Spectrum
Systems -Addendum 2.
[12] C.S0005-A Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems
- Release A addendum 2.
[13] C.S0006-A Analog Signaling Standard for cdma2000 Spread Spectrum Systems - Addendum 2.
[14] A.S0007 – A.S0009 Interoperability Specification (IOS) for High Rate Packet Data (HRPD).
[15] A.S0011 – A.S0017 Interoperability Specification (IOS) for cdma2000 Access Network
Interfaces.
[16] X.S0011 cdma2000 Wireless IP Network.
[17] C.S0024-A cdma2000 High Rate Packet Data Air Interface Specification.
[18] C.S0024-0 cdma2000 High Rate Packet Data Air Interface Specification.
[19] Void.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 7 ETSI TS 122 278 V14.5.0 (2018-10)
[20] WiMAX Forum Mobile System Profile, Release 1.0 .
[21] 3GPP TS 22.101: "Service Aspects; Service Principles".
[22] "Recommendations and Requirements for Networks based on WiMAX Forum CertifiedTM
Products" (WiMAX stage 1)
[23] "WiMAX Forum Network Architecture (Stage 2: Architecture Tenets, Reference Model and
Reference Points)"
[24] "WiMAX Forum Network Architecture (Stage 3: Detailed Protocols and Procedures)"
[25] Void.
[26] S.R0048-A 3G Mobile Equipment Identifier (MEID)
[27] BBF TR-144 - Broadband Multi-Service Architecture & Framework Requirements
[28] BBF Technical Report TR-126 - Triple-play Services Quality of Experience (QoE) Requirements
[29] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [2] and the following apply.
Communication Range: The range between UEs and /or between UEs and eNBs such that ProSe Communication is
possible.
Evolved Packet System: is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-
optimized system that supports multiple RATs. The Evolved Packet System comprises the Evolved Packet Core
together with the evolved radio access network (E-UTRA and E-UTRAN).
Firewall: a functional entity which blocks or permits the flow of various traffic types based on a set of policy rules and
definitions
EPC Path: the user plane communication path through EPC.
Open ProSe Discovery: is ProSe Discovery without explicit permission from the ProSe-enabled UE being discovered.
ProSe Broadcast Communication: a one-to-all ProSe Communication, between all authorized UEs in proximity, by
means of a common ProSe Communication Path established between these UEs.
ProSe E-UTRA Communication: a ProSe Communication using a ProSe E-UTRA Communication path.
ProSe-assisted WLAN direct communication: a ProSe Communication using a ProSe-assisted WLAN direct
communication path.
ProSe Communication path: the communication path supporting ProSe Communication. The communication path of
a ProSe E-UTRA Communication (ProSe E-UTRA Communication path) could be established e.g. directly between the
ProSe-enabled UEs using E-UTRA, or routed via local eNB(s). The communication path of a ProSe-assisted WLAN
direct communication (ProSe-assisted WLAN direct communication path) is established directly between the ProSe-
enabled UEs using WLAN.
ProSe Group Communication: a one-to-many ProSe Communication, between more than two UEs in proximity, by
means of a common ProSe Communication path established between the UEs.

ProSe UE-to-UE Relay: is a form of relay in which a Public Safety ProSe-enabled UE acts as a ProSe E-UTRA
Communication relay between two other Public Safety ProSe-enabled UEs.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 8 ETSI TS 122 278 V14.5.0 (2018-10)
ProSe-enabled Network: a network that supports ProSe Discovery and/or ProSe Communication.
Proximity: proximity is determined ("a UE is in proximity of another UE") when given proximity criteria are fulfilled.
Proximity criteria can be different for discovery and communication.
Range Class: Rough indication of distance for use in ProSe Discovery, for example, based on geographical distance,
radio conditions.
Restricted ProSe Discovery: ProSe Discovery that only takes place with explicit permission from the ProSe-enabled
UE being discovered.
Service Continuity: The uninterrupted user experience of a service that is using an active communication (e.g. an
ongoing voice call) when a UE undergoes a radio access technology change or a CS/PS domain change without, as far
as possible, the user noticing the change.
Note: In particular Service Continuity encompasses the possibility that after a RAT / domain change the user
experience is maintained by a different telecommunication service (e.g. tele- or bearer service) than
before the RAT / domain change.
Service Reachability: Functionality to enable user access to PLMN IP-based services from outside of the PLMN's
domain via non-3GPP access technologies that have IP traffic-flow restrictions (e.g. such as firewall functions that only
allow HTTP traffic).
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [2] and the following apply.
GW Gateway
GWCN Gateway Core Network
HD High Definition
MNO Mobile Network Operator
MOCN Multi-Operator Core Network
ProSe Proximity Services
RCS Rich Communication Services
SGW/PGW Serving Gateway / Packet data network Gateway
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 9 ETSI TS 122 278 V14.5.0 (2018-10)
4 General description
4.1 Objectives
The Evolved Packet System is a higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs.
The focus of the Evolved Packet System work is on enhancement of Packet Switched technology to cope with rapid
growth in IP traffic.
The objectives of the Evolved Packet System are to:
- Provide higher data rates, lower latency, high level of security and enhanced QoS;
- Support a variety of different access systems (existing and future), ensuring mobility and service continuity
between these access systems;
- Support access system selection based on a combination of operator policies, user preference and access network
conditions;
- Realise improvements in basic system performance whilst maintaining the negotiated QoS across the whole
system;
- Provide capabilities for co-existence with legacy systems and migration to the Evolved Packet System.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 10 ETSI TS 122 278 V14.5.0 (2018-10)
5 High-level requirements – user and operational
aspects
5.0 General
The Evolved Packet System shall be capable of accommodating a variety of different access systems thus providing a
multi-access system environment to the user.
The Evolved Packet System shall provide mobility functionality within and across the different access systems.
The Evolved Packet System shall provide capabilities to support the efficient integration of E-UTRAN PS Core
Network Nodes and GERAN/UTRAN PS Core Network Nodes.
The Evolved Packet System shall optimize mobility functionality meaning that it shall offer minimal signalling
overhead, minimal handover interruption time, secure handover procedure and local breakout.
The Evolved Packet System shall provide capabilities to inter-work with a variety of broadband networks based on IP
technologies including those not specified by 3GPP.
The Evolved Packet System shall provide enhanced performance e.g., low communication delay, low connection set-up
time and high communication quality.
The Evolved Packet System shall be able to efficiently support a variety of traffic models e.g. user-to-user, user-to-
group and traffic models generated by ubiquitous services.
The Evolved Packet System shall provide functionality to support outbound roaming subscribers on other Evolved
Packet Systems and legacy networks.
The Evolved Packet System shall provide functionality to support inbound roaming subscribers from other Evolved
Packet Systems and legacy networks.
The Evolved Packet System shall be capable of supporting and inter-working with PS services provided on Rel-7 and
earlier networks. The Evolved Packet System shall be capable of inter-working with CS services provided on Rel-7 and
earlier networks.
The Evolved Packet System shall support service continuity between 3GPP access systems and also between 3GPP
access systems and non 3GPP access systems whether the UE supports simultaneous radio transmission or not.
The Evolved Packet System shall be able to accommodate fixed access systems and to inter-work with fixed networks
in order to provide service continuity over fixed/mobile converged networks.
The Evolved Packet System service capability set shall include, as a minimum, support for the following categories of
services that are likely to be used by the majority of operators:
- Voice
- Video
- Messaging
- Data file exchange
The Evolved Packet System shall provide for efficient usage of system resources, especially of radio resources through
both signalling and transport optimization, e.g. overhead, terminal power, radio resources, mobility state, signalling
load.
The Evolved Packet System shall support efficient delivery of text-based broadcast messages received from a legacy
CBC.
The Evolved Packet System shall support E-UTRAN only operators. The system shall allow these operators to offer
national roaming to their subscribers.
The Evolved Packet System shall be capable of uniquely identifying each device that connects via 3GPP access
networks and 3GPP2 access networks. For a dual mode device supporting both 3GPP and 3GPP2 access technologies,
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 11 ETSI TS 122 278 V14.5.0 (2018-10)
there shall be a single persistent identifier used to identify the device. This device identifier shall be the same even when
the device moves between 3GPP and 3GPP2 access types.
Note: The 3GPP2 device identifier structure is consistent with the IMEI structure [26].
The EPC shall be capable of restricting access of specific 3GPP devices, 3GPP2 devices and dual mode 3GPP/3GPP2
devices.
5.1 Requirements for Fixed Mobile Interworking
The Evolved Packet System shall support the following scenarios: a single Operator offering both fixed and mobile
access; different Operators collaborating to deliver services across both networks. These scenarios will be supported by
interworking between the access networks.
The Evolved Packet System shall support access to services on the mobile network via interworking with a fixed access
network for the following scenarios:
- Residential scenarios for operators that own both wireless and wireline access networks
- Residential scenarios for operators that own wireless access networks only
- Enterprise scenarios with managed connectivity between mobile operators and enterprise networks
The Evolved Packet System shall be able to support the following functions for interworking between the fixed access
in the above scenarios and Evolved Packet Core:
- connectivity,
- subscriber authentication/authorization,
- offline charging
- online charging for traffic routed via the Evolved Packet Core
- Policy Control and
- Quality of Service.
The Evolved Packet Core shall support the following for fixed access:
- policy management,
- authentication for WLAN terminals and fixed devices,
- charging
The EPS shall be capable to set operator policies to support simultaneous access to PLMN services and traffic
offloading to the fixed network.
Interworking shall support the following scenarios:
When traffic is routed via EPC
- When H(e)NB is being used and traffic is offloaded in the local wireline network
- When WLAN is being used and traffic is offloaded in the local wireline network (i.e. non-seamless WLAN
offloading)
Additionally the Evolved Packet System shall be able:
- to minimize QoS and Policy management signalling overhead while interworking between the fixed access and
Evolved Packet Core.
- to route different simultaneously active PDN connections through different accesses while interworking between
the fixed access and Evolved Packet Core.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 12 ETSI TS 122 278 V14.5.0 (2018-10)
- to route different IP flows belonging to the same PDN connection through different accesses while interworking
between the fixed access and Evolved Packet Core.
The requirements for mobility in chapter 7.1.3 apply also to interworking between the fixed access and Evolved Packet
Core.
5.2 Requirements for Fixed Mobile Convergence
The Evolved Packet System shall be able to accommodate fixed access systems to provide services over a converged
network supporting both fixed and mobile accesses. The Evolved Packet System shall support common functions (e.g.
for policy management, accounting) when a single operator operates both fixed and mobile accesses.
The Evolved Packet System shall be capable of providing an equivalent experience to users consuming converged
services on different accesses, subject to different accesses capabilities.
The Evolved Packet System shall provide the following, while providing converged services:
- common operational and management procedures,
- common subscriber profiles,
- common services profiles,
- common charging procedures (e.g. a common post-paid bill).
The Evolved Packet System should optimize QoS and Policy management.
The requirements for mobility in clause 7.1.3 of this specification also apply to a converged network supporting both
fixed and mobile accesses.
The Evolved Packet System shall support requests for allocation and enforcement of QoS for layer 2 and layer 3 in
fixed broadband networks as defined in [27].
The Evolved Packet System shall support operator network policies for application sessions to request QoS in fixed
broadband networks as defined in [27].
The Evolved Packet System shall support user requests for authorization of QoS for application sessions in fixed
broadband access network as defined in [27].
The Evolved Packet System shall support policy management for QoS attributes of fixed broadband access network
services (e.g. voice, VPN, IPTV) as defined in [28].
The Evolved Packet System shall support policy management for unicast and multicast traffic for fixed devices and
IPTV services in fixed broadband access network as defined in [27].
5.3 Requirements for Interworking with Data Application
Providers
The Evolved Packet System shall support the following interworking scenarios between a mobile operator and data
application providers:
- Scenario #1: access/IP connectivity and non-IMS/non-OSA based data applications provided by the same mobile
operator
- Scenario #2: collaboration between mobile operator providing access/IP connectivity and non-IMS/non-OSA
based data applications provided by 3rd party providers
- Scenario #3: no collaboration between mobile operator providing access/IP connectivity and non-IMS/non-OSA
rd
party providers
based data applications provided by 3
The Evolved Packet System shall support all scenarios in non-roaming and roaming configurations.
The Evolved Packet System shall support all scenarios for home routed and local breakout roaming traffic except for
authentication and authorization as identified below.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 13 ETSI TS 122 278 V14.5.0 (2018-10)
For scenario#2, the Evolved Packet System shall enable 3rd party data applications to rely on security derived from the
security provided by the operator.
For scenario#2, the Evolved Packet System shall support authorization and allocation of resources on 3GPP accesses for
3rd party data applications. The home network performs authentication and authorisation in the local-breakout roaming
scenario.
The Evolved Packet System shall support policy control interactions between a mobile operator and data applications
for all scenarios triggered by application layer signalling or by user plane traffic.
For scenario #3, the Evolved Packet System shall support UE initiated requests for prioritised traffic handling through
rd
authorisation and allocation of resources on 3GPP access for 3 party data applications. The Evolved Packet System
shall revert to normal traffic handling if the request is not confirmed by the UE within a specified preview period.
The Evolved Packet System shall support online and offline charging models (e.g., user pays, application provider pays,
etc.) for all scenarios.
6 Basic capabilities
6.1 Support of IP traffic
6.1.1 Support of increased IP traffic demand
The Evolved Packet System shall be able to provide guaranteed QoS for services and use the resources of the Evolved
Packet System with high efficiency i.e. ensure that quality conditions for a particular communication are fulfilled
without deterioration between the communicating end-points.
6.1.2 Void
6.1.3 Void
6.1.4 Support of basic IP connectivity
Following registration on the network, the Evolved Packet System shall maintain an IP connectivity with the UE.
Following registration it shall be possible for an UE to send and receive IP packets.
6.1.5 Support of IP multicast service
The Evolved Packet System shall support IP multicast service.
6.2 IP session control
The Evolved Packet System shall provide for session mobility and session adaptation to terminal capabilities, user
preferences, subscriber priorities, network conditions and/or other operator-defined criteria. Session adaptation shall be
under the control of the operator.
The Evolved Packet System shall support session control for multi-party sessions (e.g. user-to-group) and shall provide
a scalable solution.
In order to support the efficient routing of IP traffic, local breakout (see Section 7.1.2) shall be supported.
The Evolved Packet System shall support a UE having simultaneously more than one active PDN connections
exchanging traffic with more than one peer (external network or other UE), when the network policies and user
subscription allow it.
If a UE is under the coverage of 3GPP access and one or more non-3GPP accesses, it shall be possible for the UE to
communicate using multiple accesses simultaneously.
The Evolved Packet System shall provide the system operator with the means to control the number of simultaneously
active PDN connections and combinations thereof to and from a UE.
A single application running on the UE shall not be required to send and receive traffic through multiple PDNs.
ETSI
3GPP TS 22.278 version 14.5.0 Release 14 14 ETSI TS 122 278 V14.5.0 (2018-10)
6.3 Quality of Service
The Evolved Packet System shall have the ability to provide a quality of service equal to or better than the QoS
requirements specified for GSM and UMTS. Quality of Service from the customer's perspective is to be considered in
phases as specified in ETSI TS 102 250-1[6].
Network Service Service Service
Access Access Retainability Integrity

Figure 2: Phases of service use from customer's point of view
Figure 2 shows the different phases (Quality of Service aspects) during service use from the customer's point of view.
The meaning of these QoS aspects are:
1) Network Access: The network indication on the display of the mobile is a signal to the customer that he can use the
service of this network operator (or any other means to indicate to the user that a network is available).
2) Service Access: If the customer wants to use a service, the network operator should provide him as fast as possible
access to the service.
3) Service Integrity: This describes the Quality of Service during service use.
4) Service Retainability: Service Retainability describes the termination of services (in accordance with or against the
will of the user).
In particular the Evolved Packet System shall provide for the following:
- There should be no perceptible deterioration of audio quality of a voice call during and following handover
between dissimilar CS and PS access networks, and transitions between PS access networks supporting different
IP protocol versions.
- There should be no loss of data, as a result of handovers between dissimilar fixed and mobile access systems,
including those that support different versions of the IP protocol.
- There should be no discernable difference in perceived service quality for users receiving services via unicast
and users receiving the same service via multicast.
- The Evolved Packet System shall support QoS differentiations for unicast bearers.
- The Evolved Packet System shall support QoS backwards compatibility to earlier 3GPP QoS releases.
- It shall be possible for the Evolved Packet System to maintain end-to-end QoS without modification when the
terminal moves from one access system to a new access system, and the new access system supports the required
QoS.
- It shall be possible for the Evolved Packet System to change QoS, when the terminal moves from one access
system to a new access system and the new access system can not provide the same QoS as the old access system
or the new access system can provide higher QoS.
- It shall be possible for the Evolved Packet System to support service continuity for a terminal changing access
system and the new access system cannot provide the same QoS as the old one.
- The Evolved Packet System shall support transport QoS differentiations for multicast bearers.
- It shall be possible for the Evolved Packet System to maintain QoS within a multicast session without QoS
changes for other members of the session when a terminal joins or leaves the multicast session or moves to a
new access system.
- The Evolved Packet System network shall support a minimum of 8 levels of QoS in parallel.
- The Evolved Packet System network shall
...