Professional Documents
Culture Documents
Training Manual
1 EPS Architecture
EPS Architecture
Objectives
On completion of this section the participants will be able to:
1.1 State the main functions of the network elements.
1.2 List the EPS interfaces.
Issue 01 (2010-05-01)
1-1
1 EPS Architecture
Whilst UMTS is based upon WCDMA technology, the 3GPP developed new specifications
for the LTE air interface based upon OFDMA (Orthogonal Frequency Division Multiple
Access) in the downlink and SC-FDMA (Single Carrier - Frequency Division Multiple Access)
in the uplink. This new air interface is termed the E-UTRA (Evolved - Universal Terrestrial
Radio Access).
1-2
RR (Radio Resource) - this supports both the Control Plane and User Plane and in so
doing, is responsible for all low level protocols including RRC (Radio Resource Control),
PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium
Access Control) and the PHY (Physical) Layer.
EMM (EPS Mobility Management) - is a Control Plane entity which manages the
mobility management states the UE can exist in; LTE Idle, LTE Active and LTE
Detached. Transactions within these states include procedures such as TAU (Tracking
Area Update) and handovers.
Issue 01 (2010-05-01)
1 EPS Architecture
ESM (EPS Session Management) - is a Control Plane activity which manages the
activation, modification and deactivation of EPS bearer contexts. These can either be
default EPS bearer contexts or dedicated EPS bearer contexts.
Control
Plane
User
Plane
IP Adaptation
Function
Radio Resource
Radio Resource
RRC, PDCP, RLC, MAC &
PHY Layer Protocols
In terms of the Physical Layer, the capabilities of the UE may be defined in terms of the
frequencies and data rates supported. Devices may also be capable of supporting adaptive
modulation including QPSK (Quadrature Phase Shift Keying), 16QAM (16 Quadrature
Amplitude Modulation) and 64QAM (Quadrature Amplitude Modulation).
In terms of the radio spectrum, the UE is able to support several scalable channels including;
1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz and 20MHz whilst operating in FDD (Frequency
Division Duplex) and/or TDD (Time Division Duplex). Furthermore, the UE may also
support advanced antenna features such as MIMO (Multiple Input Multiple Output).
Table 1-1 UE Categories
UE Category
Maximum
Downlink
Data Rate
Number of
Downlink
Data Streams
Maximum
Uplink
Data Rate
Support for
Uplink
64QAM
10.3Mbit/s
5.2Mbit/s
No
51.0Mbit/s
25.5Mbit/s
No
102.0Mbit/s
51.0Mbit/s
No
150.8Mbit/s
51.0Mbit/s
No
302.8Mbit/s
75.4Mbit/s
Yes
Issue 01 (2010-05-01)
1-3
1 EPS Architecture
UE Identities
An LTE capable UE will be allocated / utilize a number of identities during operation within
the network. These include:
l
IMSI (International Mobile Subscriber Identity) - this complies with the standard 3GPP
format and is comprised of the MCC (Mobile Country Code), MNC (Mobile Network
Code) and the MSIN (Mobile Subscriber Identity Number). This uniquely identifies a
subscriber from within the family of 3GPP technologies - GSM, GPRS, UMTS etc.
IMEI (International Mobile Equipment Identity) - is used to uniquely identify the ME. It
can be further subdivided into a TAC (Type Approval Code), FAC (Final Assembly Code)
and SNR (Serial Number).
IP Address - the UE requires a routable IP address from the PDN (Packet Data Network)
from which it is receiving higher layer services. This may either be an IPv4 or IPv6
address.
1-4
RRM (Radio Resource Management) - this involves the allocation to the UE of the
physical resources on the uplink and downlink, access control and mobility control.
Date Compression - is performed in both the eNB and the UE in order to maximize the
amount of user data that can be transferred on the allocated resource. This process is
undertaken by PDCP.
Data Protection - is performed at the eNB and the UE in order to encrypt and integrity
protect RRC signaling and encrypt user data on the air interface.
Routing - this involves the forwarding of Control Plane signaling to the MME and User
Plane traffic to the S-GW (Serving - Gateway).
Packet Classification and QoS Policy Enforcement - this involves the marking of
uplink packets based upon subscription information or local service provider policy. QoS
(Quality of Service) policy enforcement is then responsible for ensuring such policy is
enforced at the network edge.
Issue 01 (2010-05-01)
1 EPS Architecture
Security in LTE is not solely limited to encryption and integrity protection of information passing across
the air interface but instead, NAS encryption and integrity protection between the UE and MME also
takes place. In addition, IPSec may also be used to protect user data within both the E-UTRAN and
EPC.
eNB Identities
In addition to the UE identities already discussed, there are a number of specific identities
associated with the eNB. These include:
l
TAI (Tracking Area Identity) - is a logical group of neighboring cells defined by the
service provider in which UEs in LTE Idle mode are able to move within without
needing to update the network. As such, it is similar to a RAI (Routing Area Identity)
used in 2G and 3G packet switched networks.
ECGI (E-UTRAN Cell Global Identifier) - is comprised of the MCC, MNC and ECI
(Evolved Cell Identity), the later being coded by each service provider.
Femto Cells
In order to improve both network coverage and capacity, the 3GPP have developed a new type
of base station to operate within the home or small business environment. Termed the HeNB
(Home Evolved Node B), this network element forms part of the E-UTRAN and in so doing
supports the standard E-UTRAN interfaces. However, it must be stated that HeNBs do not
support the X2 interface.
The architecture may include an HeNB-GW (Home Evolved Node B - Gateway) which
resides between the HeNB in the E-UTRAN and the MME / S-GW in the EPC in order to
scale and support large numbers of base station deployments.
Issue 01 (2010-05-01)
NAS Signaling and Security - this incorporates both EMM (EPS Mobility Management)
and ESM (EPS Session Management) and thus includes procedures such as Tracking
Area Updates and EPS Bearer Management. The MME is also responsible for NAS
security.
1-5
1 EPS Architecture
l
S-GW and PDN-GW Selection - upon receipt of a request from the UE to allocate a
bearer resource, the MME will select the most appropriate S-GW and PDN-GW. This
selection criterion is based on the location of the UE in addition to current load
conditions within the network.
Tracking Area List Management and Paging - whilst in the LTE Idle state, the UE is
tracked by the MME to the granularity of a Tracking Area. Whilst UEs remain within the
Tracking Areas provided to them in the form of a Tracking Area List, there is no
requirement for them to notify the MME. The MME is also responsible for initiating the
paging procedure.
Inter MME Mobility - if a handover involves changing the point of attachment within the
EPC, it may be necessary to involve an inter MME handover. In this situation, the
serving MME will select a target MME with which to conduct this process.
Authentication - this involves interworking with the subscribers HSS (Home Subscriber
Server) in order to obtain AAA (Access Authorization and Accounting) information with
which to authenticate the subscriber. Like that of other 3GPP system, authentication is
based on AKA (Authentication and Key Agreement).
1-6
Mobility Anchor - for inter eNB handovers, the S-GW acts as an anchor point for the
User Plane. Furthermore, it also acts as an anchor for inter 3GPP handovers to legacy
networks - GPRS and UMTS.
Downlink Packet Buffering - when traffic arrives for a UE at the S-GW, it may need to
be buffered in order to allow time for the MME to page the UE and for it to enter the
LTE Active state.
Packet Routing and Forwarding - traffic must be routed to the correct eNB on the
downlink and the specified PDN-GW on the uplink.
Lawful Interception - this incorporates the monitoring of VoIP (Voice over IP) and other
packet services.
GTP/PMIP Support - if PMIP (Proxy Mobile IP) is used on the S5/S8 Interfaces, the
S-GW must support MAG (Mobile Access Gateway) functionality. Furthermore, support
for GTP/PMIP chaining may also be required.
Issue 01 (2010-05-01)
1 EPS Architecture
Packet Filtering - this incorporates the deep packet inspection of IP datagrams arriving
from the PDN in order to determine which TFT (Traffic Flow Template) they are to be
associated with.
Lawful Interception - as with the S-GW, the PDN-GW may also monitor traffic as it
passes across it.
Transport Level Packet Marking - this involves the marking of uplink and downlink
packets with the appropriate tag e.g. DSCP (Differentiated Services Code Point) based
on the QCI (QoS Class Identifier) of the associated EPS bearer.
Accounting - through interaction with a PCRF (Policy Rules and Charging Function), the
PDN-GW will monitor traffic volumes and types.
Issue 01 (2010-05-01)
1-7
1 EPS Architecture
Uu Interface
The Uu Interface supports both a Control Plane and a User plane and spans the link between
the UE and the eNB / HeNB. The principle Control Plane protocol is RRC (Radio Resource
Control) while the User Plane is designed to carry IP datagrams.
X2 Interface
The X2 interface interconnects two eNBs and in so doing supports both a Control Plane and
User Plane. The principle Control Plane protocol is X2AP (X2 Application Protocol).
S1 Interface
The S1 interface can be subdivided into the S1-MME interface supporting Control Plane
signaling between the eNB and the MME and the S1-U Interface supporting User Plane traffic
between the eNB and the S-GW. The principle Control Plane protocol is S1AP (S1
Application Protocol).
1-8
Issue 01 (2010-05-01)
1 EPS Architecture
Issue 01 (2010-05-01)
1-9
1 EPS Architecture
1-10
HSS (Home Subscriber Server) - this can be considered a master database within the
PLMN. Although logically it is considered as one entity, the HSS in practice is made up
of several physical databases depending upon subscriber numbers and redundancy
requirements. The HSS holds variables and identities for the support, establishment and
maintenance of calls and sessions made by subscribers. It is connected to the MME via
the S6a Interface which uses the protocol Diameter.
PCRF (Policy and Charging Rules Function) - this supports functionality for policy
control through the PDF (Policy Decision Function) and charging control through the
CRF (Charging Rules Function). As such, it provides bearer network control in terms of
QoS and the allocation of the associated charging vectors. The PCRF downloads this
information over the Gx Interface using the Diameter protocol.
ePDG (evolved Packet Data Gateway) - which is used when connecting to Untrusted
Non 3GPP IP Access networks. It provides functionality to allocate IP addresses in
addition to encapsulating / de-encapsulating IPSec (IP Security) and PMIP tunnels. It
connects to the PDN-GW via the S2b Interface.
RNC (Radio Network Controller) - which forms part of the 3GPPs UTRAN (Universal
Terrestrial Radio Access Network), the RNC connects to the S-GW to support the
tunneling of User Plane traffic using GTP-U. The interface linking these network
elements is the S12 Interface.
SGSN (Serving GPRS Support Node) - this forms part of the 3GPPs 2G and 3G packet
switched core domain. It connects to both the MME and S-GW in order to support
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
Issue 01 (2010-05-01)
1 EPS Architecture
packet switched mobility and uses the GTPv2-C and GTP-U protocols respectively. The
SGSN connects to the MME via the S3 Interface and the S-GW via the S4 Interface.
l
Issue 01 (2010-05-01)
EIR (Equipment Identity Register) - this database enables service providers to validate a
particular IMEI (International Mobile Equipment Identity) against stored lists. It
connects to the MME via the S13 Interface and uses the Diameter protocol for message
transfer.
1-11
1 EPS Architecture
1-12
Issue 01 (2010-05-01)
2 EPS Protocols
EPS Protocols
Objectives
On completion of this section the participants will be able to:
2.1 Explain how signaling takes place between the UE and the EPC.
2.2 State the main functions of Radio Resource Control, Packet Data Convergence Protocol,
Radio Link Control, Medium Access Control, the Physical Layer and their relations.
2.3 Explain the interaction of the E-UTRAN protocols and the mapping of logical, transport
and physical channels.
Issue 01 (2010-05-01)
2-1
2 EPS Protocols
Control Plane
Figure 2-1 illustrates the concept of NAS and AS signaling, i.e. the Control Plane. It is worth
noting that the NAS signaling is effectively transparent to the E-UTRAN. Access Stratum
signaling provides a mechanism to deliver NAS signaling, as well as the lower layer signaling
required to setup, maintain and manage the connections. The X2 interfaces are also part of
this methodology and as such it also is part of Access Stratum signaling.
Figure 2-1 NAS and AS Control Plane
User Plane
The User Plane focuses on the delivery of IP datagrams to and from the EPC, namely the
S-GW and PDN-GW. Figure 2-2 illustrates this concept.
Figure 2-2 NAS and AS User Plane
2-2
Issue 01 (2010-05-01)
2 EPS Protocols
In the case of the User Plane the higher layer NAS is an IP datagram. This effectively is
delivered between the UE and the PDN-GW, with the eNB and S-GW acting as lower layer
relaying devices.
ESM Procedures
Attach
Detach
Service Request
Issue 01 (2010-05-01)
2-3
2 EPS Protocols
GUTI Reallocation
Authentication
Identification
EMM Status
ESM Status
EMM Information
NAS Transport
Paging
EMM Procedures
The key EMM procedures include:
2-4
Attach - this is used by the UE to attach to an EPC (Evolved Packet Core) for packet
services in the EPS (Evolved Packet System). Note that it can be also used to attach to
non-EPS services.
Detach - this is used by the UE to detach from EPS services. In addition, it can also be
used for other procedures such as disconnecting from non-EPS services.
Tracking Area Updating - this procedure is always initiated by the UE and is used for the
various purposes. The most common include normal and periodic tracking area updating.
Service Request - this is used by the UE to get connected and establish the radio and S1
bearers when uplink user data or signaling is to be sent.
Extended Service Request - this is used by the UE to initiate a Circuit Switched fallback
call or respond to a mobile terminated Circuit Switched fallback request from the
network.
Authentication - this is used for AKA (Authentication and Key Agreement) between the
user and the network.
Security Mode Control - this is used to take an EPS security context into use, and
initialize and start NAS signaling security between the UE and the MME with the
corresponding NAS keys and security algorithms.
EMM Status - this is sent by the UE or by the network at any time to report certain error
conditions.
EMM Information - this allows the network to provide information to the UE.
Transport of NAS messages - this is to carry SMS (Short Message Service) messages in
an encapsulated form between the MME and the UE.
Paging - this is used by the network to request the establishment of a NAS signaling
connection to the UE. Is also includes the Circuit Switched Service Notification
Issue 01 (2010-05-01)
2 EPS Protocols
EMM Procedures
The key ESM procedures include:
l
Default EPS Bearer Context Activation - this is used to establish a default EPS bearer
context between the UE and the EPC.
Dedicated EPS Bearer Context Activation - this is to establish an EPS bearer context
with specific QoS (Quality of Service) and TFT (Traffic Flow Template) between the UE
and the EPC. The dedicated EPS bearer context activation procedure is initiated by the
network, but may be requested by the UE by means of the UE requested bearer resource
allocation procedure.
EPS Bearer Context Modification - this is used to modify an EPS bearer context with a
specific QoS and TFT.
EPS Bearer Context Deactivation - this is used to deactivate an EPS bearer context or
disconnect from a PDN by deactivating all EPS bearer contexts to the PDN.
ESM Information Request - this is used by the network to retrieve ESM information, i.e.
protocol configuration options, APN (Access Point Name), or both from the UE during
the attach procedure.
ESM Status - this is used to report at any time certain error conditions detected upon
receipt of ESM protocol data.
Issue 01 (2010-05-01)
2-5
2 EPS Protocols
In the Control Plane, PDCP facilitates encryption and integrity checking of signaling
messages, i.e. RRC and NAS. The User Plane is slightly different since only encryption is
performed. In addition, the User Plane IP datagrams can also be subjected to IP header
compression techniques in order to improve the systems performance and efficiency. Finally,
PDCP also facilitates sequencing and duplication detection.
2-6
Issue 01 (2010-05-01)
2 EPS Protocols
TM (Transparent Mode) - this is utilized for some of the air interface channels, e.g.
broadcast and paging. It provides a connectionless service for signaling.
These modes, as well as the other RLC features are illustrated in Figure 2-6. In addition to
ARQ, RLC offers segmentation, re-assembly and concatenation of information.
Figure 2-6 RLC Modes and Functions
Mapping - MAC maps the information received on the LTE Logical Channels into the
LTE transport channels.
Multiplexing - the information provided to MAC will come from a RB (Radio Bearer) or
multiple Radio Bearers. The MAC layer is able to multiplex different bearers into the
same TB (Transport Block), thus increasing efficiency.
HARQ (Hybrid Automatic Repeat Request) - MAC utilizes HARQ to provide error
correction services across the air. HARQ is a feature which requires the MAC and
Physical Layers to work closely together.
Radio Resource Allocation - QoS (Quality of Service) based scheduling of traffic and
signaling to users is provided by MAC.
In order to support these features the MAC and Physical Layers need to pass various
indications on the radio link quality, as well as the feedback from HARQ operation.
Issue 01 (2010-05-01)
2-7
2 EPS Protocols
2.2.8 X2 Interface
As previously mentioned, the X2 interface interconnects two eNBs and in so doing supports
both a Control Plane and User Plane. The principle Control Plane protocol is X2AP (X2
Application Protocol). This resides on SCTP (Stream Control Transmission Protocol) where
as the User Plane IP is transferred using the services of GTP-U (GPRS Tunneling Protocol User) and UDP (User Datagram Protocol).
Figure 2-9 illustrates the X2 User Plane and Control Plane protocols.
2-8
Issue 01 (2010-05-01)
2 EPS Protocols
Mobility Management - this enables the serving eNB to move the responsibility of a
specified UE to a target eNB. This includes Forwarding the User Plane, Status Transfer
and UE Context Release functions.
Load Management - this function enables eNBs to communicate with each other in order
to report resource status, overload indications and current traffic loading.
Error Reporting - this allows for the reporting of general error situations for which
specific error reporting mechanism have not been defined.
Setting / Resetting X2 - this provides a means by which the X2 interface can be setup /
reset by exchanging the necessary information between the eNBs.
Configuration Update - this allows the updating of application level data which is needed
for two eNBs to interoperate over the X2 interface.
Flow Control.
Improved Security.
SCTP is also found on the S1-MME Interface which links the eNB to the MME.
Issue 01 (2010-05-01)
2-9
2 EPS Protocols
2.2.12 S1 Interface
The S1 interface can be subdivided into the S1-MME interface supporting Control Plane
signaling between the eNB and the MME and the S1-U Interface supporting User Plane traffic
between the eNB and the S-GW.
Figure 2-10 S1 Interface Protocols
2-10
E-RAB (E-UTRAN - Radio Access Bearer) Management - this incorporates the setting
up, modifying and releasing of the E-RABs by the MME.
Initial Context Transfer - this is used to establish an S1UE context in the eNB, setup the
default IP connectivity and transfer NAS related signaling.
Paging.
Issue 01 (2010-05-01)
2 EPS Protocols
NAS Signaling Transport - this is used for the transport of NAS related signaling over
the S1-MME Interface.
UE Context Modification and Release - this allows for the modification and release of
the established UE Context in the eNB and MME respectively.
Location Reporting - this enables the MME to be made aware of the UEs current
location within the network.
GTPv2-C is also found on the S5/S8 Interface between the S-GW and PDN-GW and the S10 Interface
between MMEs. Furthermore, it can also be found on the S3 and S4 interfaces when interconnecting
with an SGSN (Serving GPRS Support Node).
Path Management - this incorporates Echo Request and Echo Response messages to
ensure ongoing connectivity across the link.
Tunnel Management - these messages are used to activate, modify and delete the EPS
bearers and sessions spanning the network.
Issue 01 (2010-05-01)
2-11
2 EPS Protocols
l
Non 3GPP Access - these messages support the establishment of tunnels to forward
packet data between the 3GPP and Non 3GPP networks.
2-12
Issue 01 (2010-05-01)
2 EPS Protocols
Issue 01 (2010-05-01)
2-13
2 EPS Protocols
Logical channels are classified as either Control Logical Channels, which carry control data
such as RRC signaling, or traffic Logical Channels which carry User Plane data.
BCCH (Broadcast Control Channel) - this is a downlink channel used to send SI (System
Information) messages from the eNB. These are defined by RRC.
PCCH (Paging Control Channel) - this downlink channel is used by the eNB to send
paging information.
2-14
Issue 01 (2010-05-01)
2 EPS Protocols
CCCH (Common Control Channel) - this is used to establish a RRC (Radio Resource
Control) connection, also known as a SRB (Signaling Radio Bearer). The SRB is
discussed further in Section . The SRB is also used for
re-establishment procedures. SRB 0 maps to the CCCH.
DCCH (Dedicated Control Channel) - this provides a bidirectional channel for signaling.
Logically there are two DCCH activated:
SRB 1 - this is used for RRC messages, as well as RRC messages carrying high
priority NAS signaling.
SRB 2 - this is used for RRC carrying low priority NAS signaling. Prior to its
establishment low priority signaling is sent on SRB1.
The DTCH is a bidirectional channel that can operate in either RLC AM or UM mode. This is
configured by RRC and is based on the QoS (Quality of Service) of the E-RAB (E-UTRAN Radio Access Bearer).
Issue 01 (2010-05-01)
2-15
2 EPS Protocols
l
BCH (Broadcast Channel) - this is a fixed format channel which occurs once per frame
and carries the MIB (Master Information Block). Note that the majority of System
Information messages are carries on the DL-SCH (Downlink - Shared Channel).
PCH (Paging Channel) - this channel is used to carry the PCCH, i.e. paging messages. It
also utilizes DRX (Discontinuous Reception) to improve UE battery life.
DL-SCH (Downlink - Shared Channel) - this is the main downlink channel for data and
signaling. It supports dynamic scheduling, as well as dynamic link adaptation. In
addition, it supports HARQ (Hybrid Automatic Repeat Request) operation to improve
performance. As previously mentioned it also facilitates the sending of System
Information messages.
RACH (Random Access Channel) - this channel carries limited information and is used
in conjunction with Physical Channels and preambles to provide contention resolution
procedures.
UL-SCH (Uplink Shared Channel) - this is similar to the DL-SCH, this channel supports
dynamic scheduling (eNB controlled) and dynamic link adaptation by varying the
modulation and coding. In addition, it also supports HARQ (Hybrid Automatic Repeat
Request) operation to improve performance.
PCFICH (Physical Control Format Indicator Channel) - this is used to indicate the
number of OFDM symbols used for the PDCCH.
PDCCH (Physical Downlink Control Channel) - this channel is used for resource
allocation.
PHICH (Physical Hybrid ARQ Indicator Channel) - this channel is part of the HARQ
process.
PDSCH (Physical Downlink Shared Channel) - this channel carries the DL-SCH.
2-16
Issue 01 (2010-05-01)
2 EPS Protocols
PRACH (Physical Random Access Channel) - this channel carries the Random Access
Preamble. The location of the PRACH is defined by higher layer signaling, i.e. RRC
signaling.
PUCCH (Physical Uplink Control Channel) - this channel carries uplink control and
feedback. It can also carry scheduling requests to the eNB.
PUSCH (Physical Uplink Shared Channel) - this is the main uplink channel and is used
to carry the UL-SCH (Uplink Shared Channel) Transport Channel. It carries both
signaling and user data, in addition to uplink control. It is worth noting that the UE is not
allowed to transmit the PUCCH and PUSCH at the same time.
Issue 01 (2010-05-01)
2-17
2 EPS Protocols
2-18
Issue 01 (2010-05-01)
2 EPS Protocols
In order to facilitate the multiplexing from Logical Channels to Transport Channels, the MAC
Layer typically adds a LCID (Logical Channel Identifier).
Issue 01 (2010-05-01)
2-19
2 EPS Protocols
2-20
Issue 01 (2010-05-01)
Objectives
On completion of this section the participants will be able to:
3.1 Explain the purpose of EPS Bearer Services and E-UTRA Radio Bearers.
3.2 List the different attributes of the E-UTRA Radio Bearer and explain how they are used.
Issue 01 (2010-05-01)
3-1
The main functions associated with QoS in a packet switch (router) are the:
l
Packet Classifier - this function analyses packets and based on a set of filters classifies
the packet. As such, it receives the correct packet forwarding treatment and scheduling.
Packet Scheduler - this schedules packets based on priority. In so doing various methods
are used to ensure low latency data, e.g. voice, is optimally scheduled.
3-2
Issue 01 (2010-05-01)
Issue 01 (2010-05-01)
3-3
transport between the S-GW / PDN-GW and eNB according to the EPS QoS profile
associated with each EPS Bearer.
It is possible for the UE to establish more than one default EPS bearer, however this is via a different
APN (Access Point Name).
3-4
Issue 01 (2010-05-01)
UE AMBR (User Equipment Aggregate Maximum Bit Rate) - this value applies to the
total bit rate that can be allocated to a subscriber for all its non-GBR services.
APN AMBR (Access Point Name Aggregate Maximum Bit Rate) - this value applies to
the total bit rate that can be allocated to the subset of a subscribers services associated
with a particular APN.
Priority
Packet
Delay
Budget (ms)
Packet
Error Rate
Example Service
GBR
100
10-2
Conversational Voice
GBR
150
10-3
Conversational Video
GBR
50
10-3
GBR
300
10-6
Non-Conversational Voice
Non-GBR
100
10-6
IMS Signaling
Non-GBR
300
10-6
Non-GBR
100
10-3
Non-GBR
300
10-6
Non-GBR
300
10-6
Issue 01 (2010-05-01)
Priority Level (0 to 15) - Value 15 means "no priority", whereas values between 1 and 14
are ordered in decreasing order of priority, i.e. 1 is the highest and 14 the lowest, with
value 0 being reserved.
3-5
SRB0 - this is for RRC messages using a CCCH logical channel, e.g. RRC Connection
Request, Setup and Re-establishment.
SRB1 - this is mainly for RRC messages using a DCCH logical channel. It can also be
used for NAS messages prior to the establishment of SRB2.
SRB2 - this is for NAS messages using a DCCH logical channel. Note that SRB2 has a
lower-priority than SRB1 and is always configured by the E-UTRAN after security
activation.
Uu
UE
S1-U
eNB
S5/S8
S-GW
SGi
PDN-GW
SRB 1
RRC (High Priority)
SRB 2
3-6
Issue 01 (2010-05-01)
Issue 01 (2010-05-01)
3-7
E-UTRA Configuration
In order to achieve the QoS for the E-RAB the eNB configures the lower layer protocols,
namely PDCP, RLC, MAC and the Physical Layers.
Figure 3-8 E-UTRA E-RAB QoS
There are various parameters that could be configured/modified to influence the performance
of the E-UTRA and thus aid the eNB QoS scheduling requirements. These include:
3-8
PDCP Compression.
RLC AM or UM.
Issue 01 (2010-05-01)
Objectives
On completion of this section the participants will be able to:
4.1 Explain the main functions and procedures of X2AP signaling protocol.
4.2 Explain the main functions and procedures of S1AP signaling protocol.
4.3 Explain the main functions and procedures of the User Plane protocol GTP.
Issue 01 (2010-05-01)
4-1
The Transport Network Layer Control Plane and User Plane both use the service of IP;
however a reliable robust delivery protocol in the form of SCTP (Stream Control
Transmission Protocol) exists within the Control Plane. In contrast, the User Plane utilizes
GTP-U and the services of the UDP (User Datagram Protocol). Note that an eNB may have
one or multiple IP addresses at the Transport Network Layer for both the Control and User
Planes.
4-2
Mobility Management - this function allows the eNB to move the responsibility of a
certain UE to another eNB. Forwarding of User Plane data, Status Transfer and UE
Context Release function are parts of the mobility management.
Load Management - this function is used by eNBs to indicate resource status, overload
and traffic load to each other.
Reporting of General Error Situations - this function allows reporting of general error
situations, for which function specific error messages have not been defined.
Setting up the X2 - this function is used to exchange necessary data for the eNB for setup
the X2 interface and implicitly perform an X2 Reset.
eNB Configuration Update - this function allows updating of application level data
needed for two eNBs to interoperate correctly over the X2 interface.
Issue 01 (2010-05-01)
The X2AP consists of various EP (Elementary Procedures). Table 4-1illustrates the mapping
between the functions provided by the X2 interface and the actual Elementary Procedure(s)
that are used to support this functionality.
Table 4-1 Mapping between X2AP Functions and X2AP EPs
Function
Elementary Procedure(s)
Mobility Management
a) Handover Preparation.
b) SN Status Transfer.
c) UE Context Release.
d) Handover Cancel.
Load Management
a) Load Indication.
b) Resource Status Reporting Initiation.
c) Resource Status Reporting.
Error Indication.
Resetting the X2
Reset.
Setting up the X2
X2 Setup.
Initiating
Message
Successful Outcome
Unsuccessful Outcome
Response message
Response message
Handover
Preparation
HANDOVER
REQUEST
HANDOVER
REQUEST
ACKNOWLEDGE
HANDOVER
PREPARATION
FAILURE
Reset
RESET REQUEST
RESET RESPONSE
X2 Setup
X2 SETUP
REQUEST
X2 SETUP
RESPONSE
X2 SETUP FAILURE
eNB
Configuration
Update
ENB
CONFIGURATION
UPDATE
ENB
CONFIGURATION
UPDATE
ACKNOWLEDGE
ENB CONFIGURATION
UPDATE FAILURE
Resource
Status
Reporting
Initiation
RESOURCE
STATUS
REQUEST
RESOURCE STATUS
RESPONSE
RESOURCE STATUS
FAILURE
Issue 01 (2010-05-01)
4-3
The X2AP also supports various Class 2 procedures, i.e. EPs without a response message.
Elementary Procedure
Initiating Message
Load Indication
LOAD INFORMATION
Handover Cancel
HANDOVER CANCEL
SN Status Transfer
SN STATUS TRANSFER
UE Context Release
UE CONTEXT RELEASE
Error Indication
ERROR INDICATION
The role of the X2 interface may be divided into two main groups. These are:
l
X2AP Basic Mobility Procedures - these relate to procedures used to handle the UE
mobility within E-UTRAN.
X2AP Global Procedures - these relate to procedures that are not related to a specific
UE.
Presence
The presence of Information Elements within a message depends on a number of factors
including the scenario in which the message has been invoked. Consequently, Information
Elements may be:
l
C (Conditional) - these IE are included in the message only if the condition is satisfied.
Range
The Range indicates the number of copies of repetitive Information Elements that are allowed
in the message. E.g. there may be three cells configured and each has its associated
parameters.
Criticality
In each protocol message, there is criticality information set for individual and/or groups of IE
that comprise it. This criticality information instructs the receiver how to act when receiving
an IE that is in error or not comprehended. This criticality information may be applied as
follows:
l
4-4
Issue 01 (2010-05-01)
Global - the Information Element and all its repetitions have common criticality
information.
Each - each repetition of the Information Element has its own criticality information.
Based on the criticality information, the receiver may take the following action if errors are
encountered in the Information Element:
l
Reject.
Ignore.
Handover Request
The Handover Request message includes the following information:
l
Old eNB UE X2AP ID - this provides the X2 signaling association for future messages
between the source and target eNBs.
Cause - this element indicates to the MME the reason for the handover including reasons
such as the radio network layer, transport network layer etc.
ECGI - this is the global id of the eNB and is expressed as a PLMN identity plus the
entire 28bit cell identity.
GUMMEI (Globally Unique MME Identifier) - this is the identity of the MME that is
currently serving the UE.
MME UE S1AP ID - this provides the target eNB with the signaling association
reference with the MME across the S1-MME interface for specific UE.
UE Aggregate Maximum Bit Rate - this element is used to define the total bandwidth
in Mbit/s that can be allocated to the UE for all E-RABs that are established.
E-RABs to be Setup List - this identifies the E-RAB ID, E-RAB QoS, GTP
information and RRC Context for each EPS Bearer. The latter provides details on the
current configuration and the implementation of the air interface protocols.
UE History Information -this is information about cells that a UE has been served by in
the active state prior to the target cell.
Trace Activation - this O (Optional) parameter is able to start trace procedures on the
Target eNB. In so doing, it indicates which interfaces to trace and where to send the
information.
Issue 01 (2010-05-01)
4-5
SRVCC Operation Possible - this indicates to the target eNB whether SRVCC (Single
Radio Voice Call Continuity) is available, i.e. the UE can be handed over from the
E-UTRAN to CS (Circuit Switched) 2G/3G systems.
4-6
Old eNB UE X2AP ID - this is the X2 signaling association of the source eNB.
New eNB UE X2AP ID - this is the X2 signaling association of the target eNB.
E-RABs Admitted List - this details the list of E-RAB(s) that have been admitted based
on the resources available in the target eNB.
E-RABs Not Admitted List - this identifies the E-RAB(s) which are not admitted.
Issue 01 (2010-05-01)
Target eNB To Source eNB Transparent Container- this includes handover information
for the UE. This, in essence, is an RRC Connection Reconfiguration message defining
the lower layer configuration on the new cell.
Criticality Diagnostics - this is sent by the eNB when parts of a received message have
not been comprehended or were missing, or if the message contained logical errors.
When applicable, it contains information about which parameters were not
comprehended or were missing.
If the target eNB does not admit at least one non-GBR E-RAB.
The target eNB receives a Handover Request message and the RRC Context parameter
does not include required information.
In these instances, the target eNB sends the Handover Preparation Failure message to the
source eNB with the appropriate cause parameter indicated.
Figure 4-3 X2 Handover Preparation Failure
SN Status Transfer
The SN Status Transfer procedure is used to transfer the uplink and downlink PDCP (Packet
Data Convergence Protocol) SN (Sequence Number) and HFN (Hyper Frame Number) status
from the source eNB to the target eNB during an X2 handover for each respective E-RAB for
which PDCP SN and HFN status preservation applies. These E-RAB(s) are identified in the
handover preparation phase based on the RRC Context parameters in the Handover Request.
Issue 01 (2010-05-01)
4-7
The source eNB initiates the SN Status Transfer procedure. In so doing, it stops the
assignment of PDCP SNs to downlink SDUs and stops delivering uplink SDUs towards the
EPC (Evolved Packet Core). Finally it sends the SN Status Transfer message to the target
eNB.
For E-RAB that have had forwarding preservation agreed the source eNB forwards the uplink
packets to the target eNB and routes downlink packets to the target eNB that will assign its
own sequence numbers to the packets based on the value of the PDCP DL Count received
from the target eNB.
The information in the SN Status Transfer message includes:
l
Old eNB UE X2AP ID - this is the X2 signaling association of the source eNB.
New eNB UE X2AP ID - this is the X2 signaling association of the target eNB.
E-RABs Subject to Transfer - this lists the E-RAB that have been identified to have
forwarding applied based on their QoS. Each E-RAB will have the following parameters
detailed for them:
Receive Status of UL PDCP SDUs - this optional parameter provides a bit map of
missing PDCP Sequence Numbers.
UL Count Value - this is the PDCP-SN and HFN of the next uplink SDU (Service
Data Unit) to be forwarded to the EPC.
DL Count Value - this is the PDCP-SN and HFN of the first downlink SDU to be
formatted into a PDCP SU for delivery to the UE.
UE Context Release
The UE Context Release message is sent once a handover has been successfully completed
and enables the source eNB to release all resources associated with the UE.
4-8
Issue 01 (2010-05-01)
UE Context Release
Old eNB UE X2AP ID
New eNB UE X2AP ID
eNB
Source
eNB
Target
UE Context Release
Handover Cancel
The Handover Cancel message is sent from the source eNB to the target eNB to cancel a
handover that is currently in progress.
Figure 4-6 X2 Handover Cancel
Handover Cancel
Old eNB UE X2AP ID
New eNB UE X2AP ID
Cause
eNB
Source
eNB
Target
Handover Cancel
UL Interference Load Indication - this is used to report to a neighbor eNB that specific
PRBs are experiencing interference. This may be defined as high, medium or low. PRB
are listed with PRB 0 being the first in the list, PRB 1 is the second and so on.
RNTP (Relative Narrowband Tx Power) - this indicates, per PRB, whether downlink
transmission power is lower than the value indicated by the RNTP threshold. The
receiving eNB may take such information into account when setting its scheduling policy
and can consider the received RNTP value valid until reception of a new Load
Information message carrying an update.
Issue 01 (2010-05-01)
4-9
Figure 4-8 illustrates how two of the Load Indication message parameters can be set to
indicate the uplink overload and interference requirements on an eNB.
Figure 4-8 X2 Uplink Interference
The Load Indication message also provides the Relative Narrowband Tx Power bitmap and
associated parameters. This effectively indicates to neighboring cells the power levels
transmitted per PRB.
Figure 4-9 Downlink RNTP
4-10
Issue 01 (2010-05-01)
The Reported Characteristics parameter is used to indicate: PRB Periodic, TNL load
Indication Periodic or HW Load Indication Periodic.
Issue 01 (2010-05-01)
4-11
4.1.7 X2 Setup
The purpose of the X2 Setup procedure is to exchange application level configuration data
needed for two eNBs to interoperate correctly over the X2 interface. This procedure erases
any existing application level configuration data in the two nodes and replaces it by the one
received. This procedure also resets the X2 interface in a similar fashion to a Reset procedure.
X2 Setup Request
The X2 Setup Request message includes:
l
Global eNB ID - this is the global id of the eNB and is expressed as the first 20bits of the
cell ID in the case of a macro eNB and for a home eNB it is the entire 28bit cell identity.
Served Cells - this contains a list of the cells supported by the eNB. For each cell the
following information is provided:
4-12
GU Group ID (Globally Unique Group Identifier) - this is all the pools to which the eNB
belongs to.
Issue 01 (2010-05-01)
X2 Setup Request
Global eNB ID
Served Cells
- Served Cell Information
- Neighbor Information
-- ECGI
-- PCI
-- EARFCN
GU Group Id List (C)
eNB
eNB
X2 Setup Request
X2 Setup Response
X2 Setup Response
Global eNB ID
Served Cells
- Served Cell Information
- Neighbor Information
-- ECGI
-- PCI
-- EARFCN
GU Group Id List (C)
Criticality Diagnostics
X2 Setup Response
The X2 Setup Response message simply reflects the information included in the request but
this time the values are associated with the neighbor that received the request message.
Issue 01 (2010-05-01)
4-13
Control Plane
User Plane
RNL
S1AP
IP
GTP-U
4-14
SCTP
UDP
IP
IP
Layer 2
Layer 2
Layer 1
Layer 1
S1-MME
S1-U
Issue 01 (2010-05-01)
E-RAB Management - this overall functionality is responsible for setting up, modifying
and releasing E-RABs, which are triggered by the MME. Note that the release of
E-RABs may be triggered by the eNB as well.
Initial Context Transfer - this is used to establish an S1 UE context in the eNB, to setup
the default IP connectivity, to setup one or more E-RAB(s) if requested by the MME, as
well as to transfer NAS (Non Access Stratum) signaling related information to the eNB if
needed.
Paging - this functionality provides the EPC with the capability to page the UE.
Overload - this is used to indicate the load situation in the Control Plane of the S1
interface.
Load balancing -this is used to ensure equally loaded MMEs within an MME pool
area.
S1 Setup - this is used for initial S1 interface setup for providing configuration
information.
eNB and MME Configuration Update - these are used to update application level
configuration data needed for the eNB and MME to interoperate correctly on the S1
interface.
NAS Signaling Transport - this is between the UE and the MME and is used to:
transfer NAS signaling related information and to establish the S1 UE context in the
eNB.
transfer NAS signaling related information when the S1 UE context in the eNB is
already established.
Status Transfer - this functionality transfers PDCP SN Status information from the
source eNB to target eNB in support of in-sequence delivery and duplication avoidance
for intra LTE handover.
Location Reporting - this functionality allows MME to be aware of the UEs current
location.
Issue 01 (2010-05-01)
4-15
Warning Message Transmission - this functionality provides the means to start and
overwrite the broadcasting of warning messages.
RIM (RAN Information Management) - this functionality allows the request and transfer
of RAN system information (e.g. GERAN system information) between two RAN nodes
via the core network.
Configuration Transfer - this functionality allows the request and transfer of RAN
configuration information (e.g. SON information) between two RAN nodes via the core
network.
4-16
Initiating Message
Successful
Outcome
Unsuccessful
Outcome
Response message
Response message
Handover
Preparation
HANDOVER
REQUIRED
HANDOVER
COMMAND
HANDOVER
PREPARATION
FAILURE
Handover Resource
Allocation
HANDOVER
REQUEST
HANDOVER
REQUEST
ACKNOWLEDGE
HANDOVER
FAILURE
PATH SWITCH
REQUEST
PATH SWITCH
REQUEST
ACKNOWLEDGE
PATH SWITCH
REQUEST
FAILURE
Handover
Cancellation
HANDOVER
CANCEL
HANDOVER
CANCEL
ACKNOWLEDGE
E-RAB Setup
E-RAB SETUP
REQUEST
E-RAB SETUP
RESPONSE
E-RAB Modify
E-RAB MODIFY
REQUEST
E-RAB MODIFY
RESPONSE
E-RAB Release
E-RAB RELEASE
COMMAND
E-RAB RELEASE
RESPONSE
INITIAL
CONTEXT SETUP
REQUEST
INITIAL
CONTEXT SETUP
RESPONSE
Reset
RESET
RESET
ACKNOWLEDGE
INITIAL
CONTEXT SETUP
FAILURE
Issue 01 (2010-05-01)
S1 Setup
S1 SETUP
REQUEST
S1 SETUP
RESPONSE
S1 SETUP
FAILURE
UE Context Release
UE CONTEXT
RELEASE
COMMAND
UE CONTEXT
RELEASE
COMPLETE
UE Context
Modification
UE CONTEXT
MODIFICATION
REQUEST
UE CONTEXT
MODIFICATION
RESPONSE
UE CONTEXT
MODIFICATION
FAILURE
eNB Configuration
Update
ENB
CONFIGURATION
UPDATE
ENB
CONFIGURATION
UPDATE
ACKNOWLEDGE
ENB
CONFIGURATION
UPDATE FAILURE
MME Configuration
Update
MME
CONFIGURATION
UPDATE
MME
CONFIGURATION
UPDATE
ACKNOWLEDGE
MME
CONFIGURATION
UPDATE FAILURE
Write-Replace
Warning
WRITE-REPLACE
WARNING
REQUEST
WRITE-REPLACE
WARNING
RESPONSE
The S1AP also include various Class 2 procedures which are always considered to be
successful and therefore do not require a response.
Table 4-4 S1AP Class 2 Elementary Procedures
Elementary Procedure
Message
Handover Notification
HANDOVER NOTIFY
Paging
PAGING
Initial UE Message
INITIAL UE MESSAGE
Error Indication
ERROR INDICATION
Issue 01 (2010-05-01)
4-17
Deactivate Trace
DEACTIVATE TRACE
Trace Start
TRACE START
Location Report
LOCATION REPORT
Overload Start
OVERLOAD START
Overload Stop
OVERLOAD STOP
4.2.3 S1 Setup
The S1 Setup procedure is used to exchange configured data which is required in the MME
and in the eNB respectively to ensure a proper interoperation. The S1 Setup procedure is
triggered by the eNB and is the first S1AP procedure which will be executed. Figure 4-15
illustrates the S1 Setup Request parameters.
Figure 4-15 S1 Setup Request
4-18
Issue 01 (2010-05-01)
The eNB informs the MME of its Global eNB Identity, supported TA (Tracking Areas),
Broadcasted PLMN(s) and CSG information, as well as Default Paging DRX information.
In response to the S1 Setup Request messages the MME sends a S1 Setup Response. This
includes the served GUMMEI(s) and relative MME capacity. In addition, this message can
also include a MME name, e.g. Primary MME.
Figure 4-16 S1 Setup Response
Initial UE Message
When the eNB has received, from the radio interface, the first Uplink NAS message
transmitted on an RRC connection to be forwarded to an MME, the eNB invokes the NAS
Transport procedure and sends the Initial UE Message to the MME including the NAS
message as a NAS-PDU. Note that the first Uplink NAS message is always received in the
RRC Connection Setup Complete message.
Issue 01 (2010-05-01)
4-19
eNB - UE S1AP ID - the eNB allocates a unique eNB UE S1AP ID to be used for the UE
and this identifies the UE association over the S1 interface.
NAS PDU - this contains the NAS message, e.g. EMM Attach with PDN Connectivity
Request.
TAI - this contains the PLMN Code and TA Code of the TA in which the UE has sent the
NAS message.
E-UTRAN CGI - contains the cell identify from which the UE has sent the NAS
message.
S-TMSI - this is the identity of the UE and is sent to the MME if it was received on the
air interface.
RRC Establishment Cause - indicates to the MME the reason for RRC connection
establishment.
4-20
Issue 01 (2010-05-01)
The Downlink NAS Transport message contains the identifiers referencing the UE, the
NAS-PDU and a possible Handover Restriction List. The latter is used to update the eNB on
roaming area or access restrictions.
The Uplink NAS Transport message is similar, however the current E-UTRAN CGI and TAI
are added.
UE Aggregate Maximum Bit Rate - this indicates to the eNB the total aggregate data rate
assigned to the UE.
RAB to be Setup List - this includes the E-RAB context information. Each E-RAB
includes an E-RAB ID, QoS parameters and User Plane tunnel information, i.e. an IP
address and TEID (Tunnel Endpoint Identifier).
UE Security Capabilities - this indicates the security algorithms supported by the UE.
Security Key - the purpose of the Security Key IE is to provide security related
parameters to the eNB.
Trace Activation - this optional parameter is able to setup RRC, X2 and S1AP tracing for
a UE.
Issue 01 (2010-05-01)
4-21
Handover Restriction List - this optional parameter is used to update the eNB on roaming
area or access restrictions.
UE Radio Capability - this optional parameter provides the eNB with initial UE radio
capability.
CS Fallback Indicator - this optional parameter indicates that a fallback to the CS domain
is needed.
4-22
Issue 01 (2010-05-01)
UE Context Modification
The purpose of the UE Context Modification procedure is to modify the established UE
Context. It enables the MME to modify the:
l
Security Key.
CS Fallback Indicator.
Issue 01 (2010-05-01)
4-23
Figure 4-22 illustrates the E-RAB Setup Response message and the eNB E-RAB address
parameters for downlink data delivery.
Figure 4-22 S1 E-RAB Setup Response
4-24
Issue 01 (2010-05-01)
If the eNB wants to remove all remaining E-RABs e.g. for user inactivity, the UE Context Release
Request procedure is used instead.
4.2.8 S1 Handover
The E-UTRAN supports multiple scenarios for handover, for example intra MME, inter MME,
inter S-GW, inter RAT, etc. For these different scenarios typically the same message set is
used, however the information elements within the messages may be different. A handover
involves three phases:
l
Handover preparation.
Handover notification.
Issue 01 (2010-05-01)
4-25
eNB
Source
MME
Handover Required
Handover Required
MME UE S1AP ID
eNB UE S1AP ID
Handover Type
Cause
Target ID
Direct Forwarding Path Availability (O)
SRVCC HO Indication (O)
Source to Target Transparent Container
Source to Target Transparent Container Secondary (O)
MS Classmark 2 (C) if SRVCC to GERAN
MS Classmark 3 (C) if SRVCC to GERAN
4-26
Issue 01 (2010-05-01)
Handover Type - this defines the type of handover that is required. These include:
Intra LTE.
LTE to UTRAN.
LTE to GERAN.
Cause - this element indicates to the MME the reason for the handover including reasons
with the radio network layer, transport network layer, NAS and protocol.
Target ID - for intra LTE mobility this is the Global eNB ID and is expressed as the first
20bits of the cell ID in the case of macro eNB and for Home eNB it is the entire 28bit
cell identity. For inter-RAT mobility this parameter relates to the target cell, e.g. the CGI
(Cell Global Identifier).
Direct Forwarding Path Availability - this indicates to the MME if traffic can be
forwarded directly from the source to the target eNB or if it must be routed through the
EPC.
SRVCC HO Indication - this indicates that SRVCC (Single Radio Voice Call Continuity)
procedures need to be supported as part of this handover. SRVCC is the architecture
defined to ensure call continuity between IMS, over PS access, and CS access for calls
that are anchored in the IMS when the UE is capable of transmitting/receiving on only
one of those access networks at a given time.
Source to Target Transparent Container - this element contains the transparent container
which includes radio related information that must be passed between the source and
target eNB through the EPC. Note that depending on the mobility scenarios it could
include inter-RAT containers. In addition, when SRVCC is used and the handover is to
GERAN with DTM (Dual Transfer Mode) HO support a secondary Source to Target
Transparent Container is sent.
Issue 01 (2010-05-01)
4-27
4-28
Issue 01 (2010-05-01)
The Request Type parameter is part of Location Reporting and is detailed in Section 4.2.15
Issue 01 (2010-05-01)
4-29
4-30
Issue 01 (2010-05-01)
Issue 01 (2010-05-01)
4-31
4-32
Issue 01 (2010-05-01)
Release of the old UE associated logical S1-connection when two UE-associated logical
S1-connections toward the same UE are detected after the UE has initiated the
establishment of a new UE associated logical S1-connection.
Issue 01 (2010-05-01)
4-33
4.2.13 Reset
The purpose of the Reset procedure is to initialize or re-initialize the E-UTRAN, or part of
E-UTRAN S1AP UE-related contexts, in the event of a failure in the EPC or vice versa.
Figure 4-35 S1 Reset
Trace Start
The purpose of the Trace Start procedure is to allow the MME to request the eNB to start a
trace session for a UE in ECM_Connected mode.
The Trace Activation parameter includes:
4-34
E-UTRAN Trace ID - this is the E-UTRAN Trace ID and is composed of the Trace
Reference (leftmost 6 octets) and Trace Recording Session Reference (last 2 octets).
Interfaces To Trace - this is a bit map with each position represents a eNB interface. The
first bit =S1-MME, second bit =X2, third bit =Uu with all other bits reserved for future
use. The value 1 indicates should be traced and the value 0 indicates should not be
trace.
Trace depth - this indicates the level of the trace, options include:
Minimum.
Medium.
Issue 01 (2010-05-01)
Maximum.
Trace Collection Entity IP Address - this is the Transport Layer Address to send the trace.
Deactivate Trace
The purpose of the Deactivate Trace procedure is to allow the MME to request the eNB to
stop the trace session, for the indicated trace reference.
Event - this can indicate Direct, Change of service cell, Stop Change of service cell.
Issue 01 (2010-05-01)
4-35
4.2.16 Overload
The purpose of the Overload Start procedure is to inform an eNB to reduce the signaling load
towards the concerned MME.
Figure 4-38 Overload Start
The Overload Start message indicates the Overload Action to be performed. This is either:
l
Reject all RRC connection establishments for non-emergency Mobile Originated Direct
Transfer.
Overload Stop
The purpose of the Overload Stop procedure is to signal to an eNB the MME is connected to
that the overload situation at the MME has ended and normal operation can resume.
4-36
Issue 01 (2010-05-01)
4.2.18 Paging
The paging of UEs in Idle Mode is facilitated by the MME to send a Paging message to all
eNBs managing the UEs TAI (Tracking Area Identity) or TAIs. Figure 4-39 illustrates the
Paging message and its parameter.
Figure 4-39 Paging
UE Identity Index Value - this is used by the eNB for calculating the paging occurrence.
The value relates to the IMSI mod 1024.
Paging DRX (O) - this indicates the default Paging DRX value.
List of TAIs - this indicates to the eNB which TAI(s) the paging message should be send.
CSG Id List - this indicates which CSG (Closed Subscriber Group) Identity cells should
be paged.
Issue 01 (2010-05-01)
4-37
Each GTP Tunnel supports one EPS Bearer, i.e. E-RAB. Thus multiple tunnels exist for multiple UEs.
4-38
Version - this field is used to determine the version of the GTP-U protocol, i.e. version 1.
PT (Protocol Type) - this bit is used as a protocol discriminator between GTP (when PT
is '1') and GTP (when PT is '0'). Note GTP is not used in the E-UTRAN.
E (Extension) - this flag indicates the presence of a meaningful value of the Next
Extension Header Type field. When it is set to '1', the Next Extension Header field is
present and interpreted.
Issue 01 (2010-05-01)
S (Sequence) - this flag indicates the presence of a meaningful value of the Sequence
Number field. For the Echo Request, Echo Response, Error Indication and Supported
Extension Headers Notification messages, the S flag is be set to '1'. Since the use of
Sequence Numbers is optional for G-PDUs, the PDN-GW, S-GW and eNB should set the
flag to '0'. However, when a G-PDU is being relayed by the Indirect Data Forwarding for
Inter RAT HO procedure, then if the received G-PDU has the S flag set to '1', then the
relaying entity shall set S flag to '1' and forward the G-PDU.
PN (N-PDU Number) - this flag indicates the presence of a meaningful value of the
N-PDU Number field. When it is set to '1', the N-PDU Number field is present and
interpreted.
Length - this field indicates the length in octets of the payload, i.e. the rest of the packet
following the mandatory part of the GTP header (that is the first 8 octets).
The Error Indication message where the Tunnel Endpoint Identifier is set to all zeros.
Optional Fields
l
Sequence Number - this is used for G-PDUs, an increasing sequence number for the
original IP packets transmitted via GTP-U tunnels, when transmission order must be
preserved.
N-PDU Number - this is used at the Inter SGSN Routing Area Update procedure and
some inter-system handover procedures (e.g. between 2G and 3G radio access networks).
It coordinates the data transmission for acknowledged mode of communication between
the 2G MS (Mobile Station) and the SGSN (Serving GPRS Support Node).
Next Extension Header Type - this defines the type of Extension Header that follows this
field in the GTP-PDU, e.g. PDCP PDU number.
Following the Extension Header Content a Next Extension Header Content is added. This
indicates if an additional extension header is added, if not, it is set to zero.
Currently there are two defined extension headers, namely UDP Port and PDCP PDU number.
Issue 01 (2010-05-01)
4-39
Message
Echo Request
Echo Response
3-25
Reserved
26
Error Indication
27-30
Reserved
31
32-253
Reserved
254
End Marker
255
G-PDU
4-40
Issue 01 (2010-05-01)
For the GTP-U tunnel setup between two nodes for forwarding user traffic, e.g. between eNBs
for direct forwarding over X2, Echo Request path maintenance message are not sent except if
the forwarded data and the normal data are sent over the same path.
Path Failure
A path counter is used to manage each path. This is used in conjunction with a T3-Response
Timer and N3-Requests parameter. The path counter is reset each time an Echo Response is
received on the path and incremented when the T3-Response Timer expires for any Echo
Request message sent on the path. The path is classed as down if the counter exceeds
N3-Requests. In this case, the GTP-U peer may notify the Operation and Maintenance
network element. In addition, the GTP-U peer will also notify the upper layer of the path
failure, so that EPS contexts associated with the path may be deleted. The recommended
value for the N3-Requests parameter is 5 and the T3-Response Timer is usually 20 seconds.
Issue 01 (2010-05-01)
4-41
This message is sent only in case a GTP entity was required to interpret a mandatory
Extension Header but the GTP entity was not yet upgraded to support that extension header.
The peer GTP entity may retry to use all the extension headers with that node, in an attempt to
verify it has been upgraded.
4-42
Echo Request Message - the UDP Destination Port number for GTP-U request messages
is 2152. The UDP Source Port is a locally allocated port number at the sending GTP-U
entity.
Echo Response Message - the UDP Destination Port value is the UDP Source Port of the
corresponding request message. The UDP Source Port is the value from the UDP
Destination Port of the corresponding request message.
Encapsulated T-PDUs - the UDP Destination Port number is 2152. The UDP Source Port
is a locally allocated port number at the sending GTP-U entity.
Error Indication - the UDP destination port for the Error Indication is the User Plane
UDP port (2152). The UDP source port is locally assigned at the sending node.
Issue 01 (2010-05-01)
Issue 01 (2010-05-01)
Supported Extension Headers Notification - the UDP destination port for the Supported
Extension Headers Notification is the User Plane UDP port (2152). The UDP source port
is locally assigned at the sending node.
4-43
Issue 01 (2010-05-01)
4-1
5 Glossary
5
Numerics
16 QAM (Quadrature Amplitude
Modulation)
64QAM (Quadrature Amplitude
Modulation)
2G (Second Generation)
3G (Third Generation)
3GPP (Third Generation
Partnership Project)
4G (Fourth Generation)
A
AAA (Access Authorization and
Accounting)
AC (Access Class)
AES (Advanced Encryption
Standard)
AKA (Authentication and Key
Agreement)
AM (Acknowledged Mode)
AMBR (Aggregate Maximum Bit
Rate)
AMD (Acknowledged Mode
Data)
APN (Access Point Name)
APN AMBR (Access Point Name
Aggregate Maximum Bit Rate)
ARP (Allocation and Retention
Priority)
AS (Access Stratum)
B
BCCH (Broadcast Control
Channel)
BCH (Broadcast Channel)
BI (Backoff Indicator)
BSR (Buffer Status Report)
C
C (Conditional)
Issue 01 (2010-05-01)
Glossary
5-1
5 Glossary
5-2
Issue 01 (2010-05-01)
5 Glossary
Issue 01 (2010-05-01)
RB (Radio Bearer)
RLC (Radio Link Control)
RLF (Radio Link Failure)
RNC (Radio Network Controller)
RNL (Radio Network Layer)
RNTP (Relative Narrowband Tx
Power)
ROHC (Robust Header
Compression)
RR (Radio Resource)
RRC (Radio Resource Control)
RRM (Radio Resource
Management)
RSRP (Reference Signal Received
Power)
RSRQ (Reference Signal
Received Quality)
S
S (Sequence)
S1AP (S1 Application Protocol)
SC-FDMA (Single Carrier Frequency Division Multiple
Access)
SCTP (Stream Control
Transmission Protocol)
SDF (Service Data Flow)
SDU (Service Data Unit)
SGSN (Serving GPRS Support
Node)
S-GW (Serving - Gateway)
SI (System Information)
SIB 1 (System Information Block
1)
SMS (Short Message Service)
SN (Sequence Number)
SNR (Serial Number)
SO (Second-Order)
SO (Segment Offset)
SPS (Semi-Persistent Scheduling)
SRB (Signaling Radio Bearer)
SRNC (Serving RNC)
SRS (Sounding Reference Signal)
SRVCC (Single Radio Voice Call
Continuity)
S-TMSI (Serving - Temporary
Mobile Subscriber Identity)
T
TA (Timing Advance)
TA (Tracking Areas)
TAC (Tracking Area Code)
TAC (Type Approval Code)
TAI (Tracking Area Identity)
5-3
5 Glossary
5-4
Issue 01 (2010-05-01)
Issue 01 (2010-05-01)
5 Glossary
5-1