LTE Overview PDF

Welcome to course TMO21054W – LTE Overview
Copyright © 2012 Alcatel-Lucent. All rights reserved.

TMO21054W Issue 1
Page i:1
Please take a moment and read the legal information on this screen.

TMO21054W Issue 1
Page i:2
If you have any questions about your computer being compatible with this course, call our Technical
Support Hotline at the numbers listed. Be sure to have the information listed on the slide ready for them
in order to expedite the help they will give you.

TMO21054W Issue 1
Page i:3
Before we get started, please have a quick look at the controls for this web-based training [1] :
[2] The side panel allows you to [3] see the outline, [4] view the voice-over script, or [5] search for a
topic.
[6] The control bar along the bottom allows you to [7] play or pause, [8] go to next or previous page, [9]
indicates current page and total pages and [10] shows the course status. You will also see [11] audio
length
g byy minute and seconds,, and [[12]] a volume and mute control. In addition,, [[13]] the p
panels can be
minimized. [14,15] Glossary and Attachments like a PDF or podacst version of this course are options.
When you are ready, select the “Next page” button from below to continue.

TMO21054W Issue 1
Page i:4
Knowledge Checks will appear throughout each module. These questions are included to reinforce your
understanding of the material and to help you prepare for the end-of-course assessment. Click on the
appropriate answer or answers for each question, then click Submit. Comments and feedback will appear
to help you along.
Knowledge Checks are optional aids to help students check themselves but are not tests. They are not
scored and the results are not stored.

TMO21054W Issue 1
Page i:5
TMO21054W Issue 1
Page i:6
This course provides useful appendices to help you on your journey as you learn about LTE.

TMO21054W Issue 1
Page i:7
TMO21054W Issue 1
Page i:8
TMO21054W Issue 1
Page i:9
TMO21054W Issue 1
Page i:10
Welcome to Module 1: Overview. This module identifies the LTE networks and their components.

TMO21054W Issue 1
Page 1:1
[1] After you finish this module, you will be able to:
• [2,3] Identify LTE networks and their respective components.
Please click Next to continue.

TMO21054W Issue 1
Page 1:2
This module provides an overview of LTE and explains the goals, trends, and standards requirements of
LTE.
User demand for an enriched quality of experience has been proven. According to 4G market research, this
trend will continue and grow.

TMO21054W Issue 1
Page 1:3
The demand for service, including enriched quality of experience, is now proven. Advanced users of
iphones and gaming devices such as the Samsung Player Addict are massively consuming web applications
(video, social networks), as well as location-enriched applications.
User willingness to pay directly (as a subscription, or fees) or indirectly (with no-churn commitment, or
advertising) is also proven. These trends will continue and grow as proven by 4G market research.
The compelling conditions are:
Next-generation devices (better ergonomics, multi-function, etc.)
Openness to web content and communities
Simplicity (applications can be enabled seamlessly)
Operators and their business models must unleash this openness to the web, and must provide seamless
application enablement.

TMO21054W Issue 1
Page 1:4
These charts show that LTE uses spectrum more efficiently than 3G. LTE also has a lower cost per bit.
Faster bit rates and QoS are needed to offer the real-time services end users are demanding and willing to
pay a premium for.

TMO21054W Issue 1
Page 1:5
LTE is the name given to a common standard for next generation evolution for both CDMA and WCDMA
operators.
LTE is being developed by the 3rd Generation Partnership Project (3GPP). The 3GPP is the standards body
that is also responsible for GSM and WCDMA.
LTE provides a new, IP-based mobile core referred to as the EPC. The EPC (Evolved Packet Core) is
described later in this module and throughout
g the course.
When we say “end-to-end” IP we're talking about the connection from your cell phone, or mobile
device……. to whatever application or service to which you are trying to connect. All services will be
provided using IP.

TMO21054W Issue 1
Page 1:6
The goals of LTE are listed on this slide.
LTE is the next evolution for all wireless radio access technologies. Users want more services with faster
data rates. Service providers want to improve bandwidth and spectral efficiency. LTE provides
opportunities to offer enriched wireless broadband services, expand service providers’ businesses
significantly,
g y, and achieve a stronger
g competitive
p p
position. Another keyy g
goal of LTE is to support
pp and
provide convergence with other networks and technologies.

TMO21054W Issue 1
Page 1:7
Traditionally, voice traffic goes to the circuit switched network, and packet data goes to the packet
network. 3G has separate channels for voice and data which is not an efficient use of spectrum.
For LTE, there is a single IP channel which uses spectrum more efficiently. LTE networks include a new
base station (eNodeB) and a single core network EPC (Evolved Packet Core) that provide access to both IP
based voice AND data services on the packet data network.
LTE eNodeBs have much more intelligenceg than the 3G base stations. The 3G RNC is eliminated in LTE.
Some RNC functionality is incorporated into the eNodeB, which reduces latency for user traffic and
reduces the time required for many procedures, such as handovers.

TMO21054W Issue 1
Page 1:8
The LTE architecture consists of two networks:
• eUTRAN - The Evolved Universal Terrestrial Radio Access Network (eUTRAN) consists of one
component; the evolved NodeB (eNodeB). The eNodeB combines the functions of a NodeB and a
Radio Network Controller (RNC). The eNodeB communicates with the User Equipment (UE) and the
Evolved Packet Core (EPC). The eNodeB is the component that connects the subscriber’s mobile
device ((User Equipment,
q p , UE)) to the network.
• EPC - The Evolved Packet Core (EPC) is an all-IP network that carries all types of traffic. The four
components of the EPC include the following:
• SGW – gateway for packet routing
• PGW – gateway for packet routing
• MME – mobility management and session control
• PCRF – for charging policy

TMO21054W Issue 1
Page 1:9
TMO21054W Issue 1
Page 1:12
LTE Solution networks include the eUTRAN and the EPC.
The Evolved Universal Terrestrial Radio Access Network (eUTRAN) improves end-user throughputs. The
eUTRAN contains an evolved NodeB, which combines the functions of a NodeB and a Radio Network
Controller. The eNodeB communicates with the User Equipment (UE) and the Evolved Packet Core (EPC).
The EPC is an all-IP network that carries all types of traffic.
eUTRAN - Evolved Universal Terrestrial Radio Access Network
EPC - Evolved Packet Core
RNC – Radio Network Controller
The eUTRAN and EPC together are referred to as the Evolved Packet System (EPS).
LTE eUTRAN access is provided by the eNodeB. The GSM/UMTS/CDMA RAN will also evolve to allow for
access to a common 3GPP network using the EPC and to allow for a smooth migration from any network to
LTE.
UE – user equipment (mobile device)

eNodeB – Provides radio access functions for the UE
MME – Control plane element that manages network access and mobility
SGW – Local mobility anchor for UE; Performs IP routing and forwarding functions
PGW – IP anchor for bearers
PCRF - Provides central policy control for IP bearer resources
These components will be described in the next few modules.

TMO21054W Issue 1
Page 1:13
TMO21054W Issue 1
Page 1:15
TMO21054W Issue 1
Page 2:1
[1] After you finish this module, you will be able to:
• [2,3] Describe the LTE network architecture.

TMO21054W Issue 1
Page 2:2
Click on the Next button to follow the recommended learning path.

TMO21054W Issue 1
Page 2:3
TMO21054W Issue 1
Page 2:4
LTE Solution consists of two groups of network elements:
• eUTRAN (Evolved Universal Terrestrial Radio Access Network)
• EPC (Evolved Packet Core)
The eNodeB is the key component of the eUTRAN. The eNodeB sends and receives data to/from the UE (user
equipment,
q p , or mobile device)) and p
provides the Ethernet links to the network. The eUTRAN components
p are
described in a later module.
The EPC consists of the:
• Mobility Management Entity (MME) The MME is a control-plane element responsible for mobility
management and session control. The MME manages connections handled by thousands of eNodeBs.
Control functions include authentication, tracking, paging, choosing the SGW, bearer activation.
• Serving Gateway (SGW) The SGW routes and forwards user data packets and is the anchor point for inter-
eNodeB handover, and the anchor for mobility between LTE and other 3GPP networks.
• Packet Data Network Gateway (PGW) The PGW connects the UE to external data networks. The PGW is
the anchor for mobility between 3GPP and non-3GPP technologies. The PGW performs policy
enforcement packet filtering
enforcement, filtering, charging support,
support and packet screening
screening.
• Policy and Charging Rule Function (PCRF) The PCRF provides network control of flows, including:
detection, Quality of Service (QoS), gating, and flow-based charging, and authorizes network-wide use
of QoS resources. The PCRF enforces authorized QoS for each service data flow (SDF), and decides how
SDFs should be treated by the SGW and PGW.
Legend:
The solid red and dashed blue lines are used in many of our network diagrams.
The solid red line refers to user data. The user plane provides bearer functions and carries user data packets. For
example, the user plane (represented by the red line) is used to carry bearers.
The blue dashed lines refer
f to control data. The control p plane is the p
portion off a channel or p
protocol that carries
signaling and control data. For example, the control plane (represented by the blue lines), would be used to authenticate
users.

TMO21054W Issue 1
Page 2:5
The Home Subscriber Server (HSS) is required for LTE. The HSS is the database with the permanent store
of LTE subscriber profiles and enables authentication and downloading of user profiles to the network.
If the HSS has been previously deployed for IMS, it is possible to use the same HSS for LTE.

TMO21054W Issue 1
Page 2:6
There are a few terms you should be familiar with before we continue with this module.
User equipment (UE) is any wireless device that connects to the eUTRAN.
The user plane, or data plane, carries user data packets.
The control plane, or network control, carries signaling and control data.
Approcedure is a term used for events of sequences
q of activities that are p
performed in an LTE network.
Examples of a procedure are Attach, handover, and Service Request
Legend:
The solid red and dashed blue lines are used in many of our network diagrams.
The solid red line refers to user data. The user plane provides bearer functions and carries user data
packets. For example, the user plane (represented by the red line) is used to carry bearers.
The blue dashed lines refer to control data. The control plane is the portion of a channel or protocol
that carries signaling and control data. For example, the control plane (represented by the blue lines),
would be used to authenticate users.

TMO21054W Issue 1
Page 2:7
TMO21054W Issue 1
Page 2:8
Every bearer must be assigned a QCI to allow QoS enforcement.
3GPP has defined 9 QoS class identifiers with values assigned for latency and loss rates.
QCI - QoS class identifier
A scalar that is used as a reference to a specific
p p
packet forwarding
g behavior ((e.g.
g ppacket loss rate,, p
packet
delay budget) to be provided to a SDF. This may be implemented in the access network by the QCI
referencing node specific parameters that control packet forwarding treatment (e.g. scheduling weights,
admission thresholds, queue management thresholds, link layer protocol configuration, etc.), that have
been pre-configured by the operator at a specific node(s) (e.g. eNodeB).

TMO21054W Issue 1
Page 2:9
TMO21054W Issue 1
Page 2:10
TMO21054W Issue 1
Page 2:11
Packet marking needs to be consistent from an end-to-end perspective
QoS enforcement must occur at all layers of the transport network. All LTE bearers have a QCI, which
must map to DSCP for QoS at the IP layer, which may map to p-bit at the Ethernet layer.
The table shows an example
p of how the different LTE QoS levels are mapped
pp to other layers.
y

TMO21054W Issue 1
Page 2:12
This table is from http://www.3gpp.org/article/lte
The UE categories are specified in 3GPP TS 36-306.

There are five categories in 3GPP release 8 & 9. 3GPP release 10 (LTE Advanced) defines 8 UE categories.

TMO21054W Issue 1
Page 2:13
Some of the techniques used by LTE to increase bandwidth and efficiency include:
• MIMO - User equipment (UEs) and eNodeBs will have more than one antenna.
• OFDMA – OFDMA is used on the downlink for minimal interference. OFDMA allows simultaneous data
rate transmission from several users.
• SC-FDMA – SC-FDMA is used on the uplink because it uses less power than OFDMA.
Refer to Appendix A to look up any unknown acronyms and abbreviations. The following acronyms and
abbreviations are used on this slide:
• OFDMA - Orthogonal Frequency Division Multiple Access
• MIMO – Multiple-Input Multiple-Output
• SC-FDMA - Single Carrier - Frequency Division Multiple Access
• eUTRAN – Evolved Universal Terrestrial Radio Access Network
• EPC - Evolved Packet Core
• DL – downlink (OFDMA)
• UL – uplink (SC-FDMA)
• UE – user equipment

TMO21054W Issue 1
Page 2:14
LTE air interface characteristics include the following:
• Supports both FDD and TDD modes:
Provides deployment flexibility in spectrum allocation.
• With FDD, DL and UL transmissions are performed simultaneously in two different frequency bands.
• With TDD, DL and UL transmissions are performed at different time intervals within the same
frequency
q y band.
DL - downlink
UP - uplink

TMO21054W Issue 1
Page 2:15
This table illustrates some of the LTE bands defined by 3GPP
The information in this table is a partial listing of the bands defined in 3GPP TS 36-101. For a complete
list, refer to TS 36-101.
The 3GPP TS 36-101 defines these frequency bands for use with LTE, however all of these bands will be
not available for LTE in each country.
y

TMO21054W Issue 1
Page 2:16
TMO21054W Issue 1
Page 2:19
LTE Solution networks include the eUTRAN and the EPC.
The Evolved Universal Terrestrial Radio Access Network (eUTRAN) improves end-user throughputs. The
eUTRAN contains an evolved NodeB, which combines the functions of a NodeB and a Radio Network
Controller. The eNodeB communicates with the User Equipment (UE) and the Evolved Packet Core (EPC).
The EPC is an all-IP network that carries all types of traffic.
eUTRAN - Evolved Universal Terrestrial Radio Access Network
EPC - Evolved Packet Core
RNC – Radio Network Controller
LTE eUTRAN access is provided by the eNodeB. The GSM/UMTS/CDMA RAN will also evolve to allow for
access to a common 3GPP network using the EPC and to allow for a smooth migration from any network to
LTE.
UE – user equipment (mobile device)

eNodeB – Provides radio access functions for the UE
MME – Control plane element that manages network access and mobility
SGW – Local mobility anchor for UE; Performs IP routing and forwarding functions
PGW – IP anchor for bearers
PCRF - Provides central policy control for IP bearer resources

TMO21054W Issue 1
Page 2:20
TMO21054W Issue 1
Page 2:21
TMO21054W Issue 1
Page 2:23
In Module 3 - LTE Solution eUTRAN, you will learn about the eNodeB - the key component of the eUTRAN
- and the technologies and techniques used in the eUTRAN.

TMO21054W Issue 1
Page 3:1
After you finish this module, you will be able to:
• Identify the technologies and techniques used in the eUTRAN.
• Describe the basic Radio Access Network (RAN) LTE air interface principles.
• Describe the main functionalityy of the eNodeB.
Click Next to continue.

TMO21054W Issue 1
Page 3:2

TMO21054W Issue 1
Page 3:3
TMO21054W Issue 1
Page 3:4
The LTE RAN is known as the eUTRAN (Evolved Universal Terrestrial Radio Access Network).
The key eUTRAN component is the base station. In an LTE network, this is the Evolved NodeB (eNodeB).
The eNodeB performs the base station function of the radio access network (RAN).

TMO21054W Issue 1
Page 3:5
The eNodeB receives and sends radio signals to/from the antennas, and schedules uplink and downlink
data to/from the UE. The eNodeB also provides Ethernet links to the backhaul network to allow the
transmission of signaling and user traffic to the EPC elements and other eNodeBs.
eNodeB logical links to the network:
• S1 interfaces to EPC
• X2 interfaces to other eNodeBs
Note that the lines connecting the network elements are representing logical links, not physical links.
Some detail about logical interfaces will be presented later.
S1 interfaces are used for signaling and data. The X2s are used for signaling and data transfer during an
inter-eNodeB handover.
The CSR (cell site router) can be co-located at the cell site with the eNodeB. It may already be present
in upgraded 3G sites. The CSR takes the eNodeB Ethernet link towards the network.
The MLS (multi-layer switch) is a larger service router which aggregates traffic from the cell sites.
CSR – Cell Site Router

MLS – Multi-Layer Switch

TMO21054W Issue 1
Page 3:6
In LTE, mobile devices are referred to as user equipment or UEs.
LTE UEs will have multiple antennas. The 3GPP R8 and R9 specifications allow for up to four antennas.
Multiple antennas in phones are a challenge because of space limitations, cost, and heat from additional
transmitters. Advanced multi-antenna solutions are the key tools to achieve capacity, coverage, and
peak data rates in LTE networks.
networks
UEs may be dual mode, meaning they can maintain a session on either a 3G or LTE RAN. When voice is
carried over LTE, the UEs will use a voice over IP (VoIP) client for voice calls.
UE will use LTE whenever possible (priority), but can connect to 1xEvDO or UMTS if no LTE is available or
fallback to CDMA or UMTS for voice.
UE IPv4 and IPv6 support is sometimes referred to as “dual stack”. The UE could have both types of
addresses.
CDMA eBTS, UMTS NodeB, and LTE eNodeB are on the same side of the drawing to reflect that they will
likely be co-located at the same site.

TMO21054W Issue 1
Page 3:7
TMO21054W Issue 1
Page 3:8
One of the design goals of LTE is to make data rates faster. The data rates shown on this slide assume
2x2 antennas. Rates will be higher with 4x4 antennas.
UMTS is 5MHz
CDMA is 1.25MHZ channel
LTE uses a scalable channel bandwidth, unlike 2G/3G systems.

TMO21054W Issue 1
Page 3:9
To achieve LTE eUTRAN design goals (for the purpose of providing new real-time services), networks will
reduce user plane latency by integrating RNC functions into the eNodeB. “Flattening” the network
architecture refers to combining functionalities into single components, and separating the user and
control planes.
New signal modulation,
modulation transmission
transmission, and encoding techniques
techniques, such as MIMO,
MIMO OFDMA,
OFDMA and SC-FDMA,
SC FDMA are
used to increase data rates, efficiency, and mobile speeds.

TMO21054W Issue 1
Page 3:10
UMTS network components are shown on this slide to illustrate how LTE networks are “flattening” the
eUTRAN - reducing the number of network elements. In the eUTRAN, the RNC is integrated into the
eNodeB, eliminating an element on both the control and user planes. In the evolved packet core (EPC),
the Mobility Management Entity (MME) assumes the role of the SGSN for the control plane, and the SGW
and PGW ensure the role of user plane, routing user data traffic to the network edge, replacing the
GGSN.
C-plane – control plane

U-plane – user plane
User plane (data plane) – Portion of a channel or protocol that carriers user data packets
Control plane (application control or network control) – Portion of a channel or protocol that carries
signaling and control data

TMO21054W Issue 1
Page 3:11
Multiple Input Multiple Output (MIMO), pronounced “my moh,” is a form of smart antenna technology in
which multiple antennas are used at both the transmitter and receiver to improve communication
performance. This graphic illustrates 2x2 single user MIMO (SU-MIMO).
In the graphic, a single data stream is brought to the eNodeB, and split. Half is transmitted from one
antenna (blue), and the other half is transmitted from the other antenna (pink). Blue and pink are the
separation of the data streams. Splitting the data stream greatly increases throughput; twice the data in
the same amount of time.

TMO21054W Issue 1
Page 3:12
LTE modulation techniques include OFDMA and SC-FDMA.
OFDMA (Orthogonal Frequency Division Multiple Access) provides higher throughput in the same
bandwidth by overlapping frequencies (also called subcarriers). It is used in the downlink of data to the
UE.
OFDMA is used in 802.11 (Wifi) and 802.16e/d WiMax.
OFDMA requires more power than SC-FDMA (Single Carrier Frequency Division Multiple Access), which is
why SC-FDMA is used in the uplink from the UE to the eNodeB. Using SC-FDMA conserves the UE battery.

TMO21054W Issue 1
Page 3:13
With OFDMA, subcarriers are orthogonal (which prevents cross-talk), while overlapping the subcarriers.
This saves bandwidth and transmits data in half the time as FDMA.
OFDMA - Orthogonal Frequency Division Multiple Access

TMO21054W Issue 1
Page 3:14
TMO21054W Issue 1
Page 3:15
Logical interfaces on the Gigabit Ethernet port of the eNodeB connect the eNodeB to the network.
All interfaces are IP based and traverse the backhaul. The eNodeBs do not communicate via RF.
The S1-MME to the MME is for signaling and authentication. The S1-MME interface supports the eNodeB
sending PCMD (per call measurement data) to the MME.
S1-U is used to transmit user traffic to the SGW, establishing the user plane.
The X2 interfaces link the eNodeBs together and are used to send signaling messages between eNodeBs
to initiate and
d support X2 b
based
dhhandovers.
d
Refer to Appendix B for more details on the various interfaces.
Note that the lines in the drawing depict logical IP connections, not physical. The eNodeBs are not
physically connected. eNodeBs connect through the IP backhaul network.

TMO21054W Issue 1
Page 3:16
TMO21054W Issue 1
Page 3:19
LTE reduces user plane latency by integrating RNC functions into the eNodeB. This is known as flattening
the network architecture.
LTE provides an increase in data rates, efficiency, and mobile speeds by using new signal modulation,
transmission, and encoding techniques, such as:
• MIMO
• OFDMA
• SC-FDMA
• Transmit and receive diversity

TMO21054W Issue 1
Page 3:20
• The eNodeB schedules the reception and transmission of radio signals from/to the UE antennas, and
provides Ethernet links to the EPC elements and other eNodeBs.
• eNodeB logical links to the network include the S1 interfaces to the EPC and the X2 interfaces to
other eNodeBs.

TMO21054W Issue 1
Page 3:21
TMO21054W Issue 1
Page 3:23
TMO21054W Issue 1
Page 4:1
Identify the LTE Evolved Packet Core (EPC) components.
Describe the main functionality of the MME, PCRF, PGW, and SGW.

TMO21054W Issue 1
Page 4:2
TMO21054W Issue 1
Page 4:3
TMO21054W Issue 1
Page 4:4
LTE is end-to-end IP: from mobile devices, or UEs, to other UEs, the Internet, servers, or from wherever
users upload and download data. The EPC is essential for end-to-end IP service delivery across the LTE
network.
The LTE network consists of the eUTRAN and the Evolved Packet Core (EPC). The eUTRAN and the EPC
are referred to as the Evolved Packet System (EPS). This module describes the EPC components.
The EPC (Evolved Packet Core) is a new, all-IP mobile core network for the LTE. The EPC network is
based on all-IP.

TMO21054W Issue 1
Page 4:5
The EPC connects the eNodeB to packet data networks. All LTE data traverses through the EPC.

TMO21054W Issue 1
Page 4:6
The EPC provides mobile core functionality that, in previous mobile generations (2G, 3G), has been
realized through two separate sub-domains: circuit-switched for voice and packet-switched for data. In
LTE, these two distinct mobile core sub-domains, used for separate processing and switching of mobile
voice and data, are unified as a single IP domain.
The EPC has a p
packet-onlyy architecture. It is the first 3GPP system
y without a circuit switch domain.
Communication services (for example, voice service) are provided over the IMS architecture.
The EPC provides a very low end-to-end latency for both user and control plane traffic.

TMO21054W Issue 1
Page 4:7
The EPC consists of four elements:
• Mobility Management Entity - The MME provides mobility and session control management and
authenticates UEs.
• Serving Gateway (SGW) - The SGW routes and forwards user packets, and acts as the local
mobility anchor for the user plane for LTE handovers and inter-RAT handovers (e.g. LTE to UMTS).
• Packet Data Network ((PDN)) Gatewayy ((PGW)) - The PGW pprovides UE session connectivityy to
external packet data networks. The UE may have more than one session active with a PGW for
accessing multiple PDNs. The PGW also acts as the anchor point for non-3GPP networks (e.g.,
CDMA 1X/EVDO, or UMTS).
• Policy and Charging Rule Function (PCRF) - The PCRF supports service data flow detection, policy
enforcement, and flow-based charging.

TMO21054W Issue 1
Page 4:8
This slide lists some of the functions of the EPC. One key characteristic of the EPC is that it supports
interfacing with other access systems.

TMO21054W Issue 1
Page 4:9
The EPC separates control plane functionality from data plane functionality. The data plane is also
referred to as the user plane. The control plane is the portion of a channel or protocol that carries
signaling and control data. The user plane provides bearer functions and carries user data packets. The
separation of control and bearer functions allows each element to be optimized for its function and to
be scaled independently. For example, the MME provides only control and signaling functions.
Control plane:
• Highly scalable, secure dynamic mobility and connection management
• Network-wide, real-time policy control
Data plane:
• High aggregate throughput (over 100 Gbps) for high bandwidth on-demand services
• Per-subscriber, per-application, per-session QoS and policy enforcement
Data plane – needs to address requirements for high bandwidth, high availability and scalability, with
aggregate throughput (per gateway) easily reaching over 100 Gb/s. At the same time, the data plane
needs to allow unaffected performance with sophisticated processing of millions of service data flows
and data bearers turned on, while being able to provide sophisticated, fine-granular (per-application,
per-service, per-user) QoS
Control plane – needs to address the requirements for high scalability and high availability of secure
mobility and connection management, along with highly reliable and scalable network-wide policy and
subscriber management.

TMO21054W Issue 1
Page 4:10
TMO21054W Issue 1
Page 4:11
The MME is the control plane element that manages network access and mobility. The MME controls
how UEs interact with the network.

TMO21054W Issue 1
Page 4:12
The MME communicates with the HSS for user authentication. The MME communicates with the eNodeB
and SGW for session control and bearer setup.
MME functions support the LTE procedures. LTE procedures include attach, detach, service request,
handover, etc…
MME functions/procedures include:
• UE authentication
• Assigning temporary IDs to UEs
• Bearer management functions (create, modify, delete)
• Location tracking and paging UEs
• PGW and SGW selection – The MME selects the SGW at initial UE attach and intra-LTE handover.

TMO21054W Issue 1
Page 4:13
A key function of the MME is to authenticate mobile devices (UEs). The MME always performs
authentication upon initial attach (and as needed).
The first step in authorization is to check the user’s identity and services at the HSS. The HSS stores the
UE IMSI and MSISDN as well as a profile of the user’s subscription and the QoS level they have
bought.
g The MME sends an authorization request
q to the HSS and includes various information elements
(IEs) like the IMSI, User Name, Supported Features, Requested EUTRAN-Authentication Info, Visited
PLMN ID, Requesting Node Type.
If the UE identity is in the database and the UE has paid for the requested services, the HSS will
respond to the MME with some authentication and security vectors (basically, security keys). If the UE
is not in the HSS database, the UE gets a reject message and is purged from the MME.
The MME will derive a key from the security vectors and send it to the UE and request the UE to
perform some authorization calculations. This helps ensure the UE is who it says it is, and it also helps
the UE ensure that it is attaching to the real operator network. The UE responds with its
authentication/security information and calculations,
calculations which the MME verifies with the information it
received from the HSS. If it’s OK, then the NAS security is set up (authorization part is done). The MME
will send the GUTI (temporary ID) when the attach is accepted. If the UE does not have a GUTI when it
requests services, then it has to be re-authorized.

TMO21054W Issue 1
Page 4:14
MME interfaces are listed on this slide. MME pooling is available over the S10 interface. MME pooling
refers to having several MMEs in the network. MME pooling requires the eNodeBs to associate with all of
the MMEs in the pool (over the S1-MME interface).
X1_1 and X2 are used for lawful interception and provide an interface to the LIG (lawful intercept
gateway).
LTE-UMTS and LTE-CDMA interworking g interfaces for the MME are described in a later module.
There is also an SBc interface to the Cell Broadcasting Center (CBC). The CBC sends warning messages
to the MME, who forwards them to the eNodeB, and on to the UE.

TMO21054W Issue 1
Page 4:15
S1-MME is the reference point between the MME and the eNodeB. S1-MME is used by the MME to
exchange information to control and set up user data sessions.

TMO21054W Issue 1
Page 4:16
S6a is the interface between the MME and the HSS (Home Subscriber Server), which maintains user profile
information.

TMO21054W Issue 1
Page 4:17
TMO21054W Issue 1
Page 4:19
The SGW maintains data paths between eNodeBs and the PGW.

TMO21054W Issue 1
Page 4:20
The SGW (Serving Gateway) serves as the local mobility anchor for the UE and terminates the packet
data network interface towards the eUTRAN. The SGW is a data plane element whose primary function
is to support user-plane mobility. This means that packets are routed through the SGW for intra-
eUTRAN mobility and mobility with other 3GPP technologies, such as 2G/GSM and 3G/UMTS. All EPS
bearers associated with an UE are established on the same SGW.
Additional SGW functions are listed here:
• Local mobility anchor point for inter-eNodeB and inter-3GPP handovers
• Mobility anchoring for inter-3GPP mobility
• Session supervision of the availability of the eNodeB
• IDLE mode downlink packet buffering and initiation of network triggered service request
procedure
• Packet routing and forwarding
• Accounting on user and QoS Class Identifier (QCI) granularity for inter-operator charging
• Uplink and Downlink charging per UE and per PGW

TMO21054W Issue 1
Page 4:21
The SGW and PGW are in charge of the user data plane. Both have the ability to participate in the
global Quality of Service (QoS) and flow-based charging infrastructure.
With regard to QoS, the PCRF (Policy and Charging Rule Function) provides policy information (to the
PGW, who relays it to the SGW) for establishing default bearer and service-specific bearers. The PCRF
is used to p
provide better network utilization and control byy establishing
gppolicies ((bandwidth
constraints, QoS markings, etc.) for the bearer flows. The PCRF is described later in this module.
Refer to Appendix B (in the back of the student guide) for a description of each interface.

TMO21054W Issue 1
Page 4:22
TMO21054W Issue 1
Page 4:24
TMO21054W Issue 1
Page 4:25
As an IP access gateway, the PGW (Packet Gateway) provides the user with an IP address.
The PGW is the gateway that terminates the SGi interface towards the PDN (packet data network), or IP
network.

TMO21054W Issue 1
Page 4:26
The PGW provides Flow Based Charging under control of the PCRF, which is described in the next
section. The PGW is also an enforcement point for the policy decisions coming from the PCRF. The PGW
can perform some per-user based packet filtering.
The PGW supports mobility between 3GPP access and non-3GPP access and between different non-3GPP
accesses.
SDF – Service Data Flow

TMO21054W Issue 1
Page 4:27
Interfaces to and from the PGW are illustrated on this slide.
In the EPC (Evolved Packet Core), the SGW and PGW are in charge of the user data plane. Both have the
ability to participate to the global Quality of Service (QoS) and flow-based charging infrastructure. The
PGW provides Flow Based Charging under control of the PCRF.

TMO21054W Issue 1
Page 4:28
TMO21054W Issue 1
Page 4:30
The PCRF (Policy and Charging Rule Function) is the policy management entity. PCRF is a Control Plane
device designed to manage the QoS policies and charging rules for user traffic.
The Subscriber Profile Repository (SPR) is described on the next slide.

TMO21054W Issue 1
Page 4:31
The PCRF performs the following functions:
• Enables service-based policy control
• Provides charging information and rating parameters
• Enables more flexibility in engineering and policy control of LTE resources
• Decides, based on subscription and network parameters, what policies to install in the network
• Relays
y network events that are of interest to the applications
pp
On UE attachment, the PCRF:
1. Receives a request for policies for the default bearer
2. Retrieves the user profile from the SPR (Subscription Profile Repository) and executes the rule-
set for the decision for policy and charging
3. Responds to the PGW with the PCC (policy control/charging) rule
• Service Data Flow filters (traffic flow template)
• Charging profile(s)
• Default Bearer QoS profile
Online charging is often known as prepaid. Offline charging is often known as postpaid.
SDF – Service Data Flow – Set of IP packets. SDFs are defined by the PGW.
PCC – Policy Control and Charging
SPR – Subscriber Profile Repository - Responsible for storing the subscriber profiles including all details
required for determining the QoS
The SPR database can be connected to the PCRF or can be the HSS (the HSS is an example SPR for the
IMS).

TMO21054W Issue 1
Page 4:32
Interfaces to and from the PCRF are illustrated on this slide.
LBO - Local Breakout (roaming)
Not shown in the diagram are two additional interfaces to the PCRF:
• S9 between Home and Visiting PCRFs (for LBO roaming) (not shown in diagram)
• Syy to the online charging
g g system
y ((not shown in diagram)
g )
Sp is the 3GPP standards interface between the SPR and the PCRF. Either the Sh or the LDAP protocol
is used for this interface.

TMO21054W Issue 1
Page 4:33
TMO21054W Issue 1
Page 4:37
The Mobility Management Entity (MME) provides mobility and session control management.
The Serving Gateway (SGW) routes and forward user packets.
The Packet Data Network Gateway (PGW) provides UE session connectivity to external packet data
networks.
The Policy and Charging Rule Function (PCRF) supports service data flow (SDF) detection, policy
enforcement,, and flow-based charging.
g g

TMO21054W Issue 1
Page 4:38
TMO21054W Issue 1
Page 5:1
• Describe the functions performed by the MME, PGW, SGW, and eNodeB during end-to-end LTE data
call flow in the LTE Solution.
Click Next to continue.

TMO21054W Issue 1
Page 5:2

TMO21054W Issue 1
Page 5:3
TMO21054W Issue 1
Page 5:4
The Evolved Packet System (EPS) consists of the eUTRAN and EPC.
EPS – Evolved Packet System
UE – user equipment
Additional components of the LTE solution are the UE, HSS, and PDN.
In this module, we will describe the functions that each of these network elements performs during a data
session.

TMO21054W Issue 1
Page 5:5
The concept of pool area (23.401) is a RAN based definition that comprises one or more Tracking Areas
(TAs) that, from a RAN perspective, are served by a certain group of MMEs.
MMEs have S1-MME (e.g., SCTP) connectivity to all eNodeBs within the pool area, and S10 connectivity to
all MMEs in all pools.
All eNodeBs
N d B within
ithi th
the pooll area mustt h
have S1
S1-U
U ((e.g., IP/UDP) connectivity
ti it tto SGW
SGWs.
The UE is served by any of the MME/SGWs within a pool. No MME/SGW relocation required within the
MME/SGW pool during handover.
The eNodeBs must support S1-flex, which provides the capability for the eNodeB to perform the MME
selection function.
The PGWs are not grouped into pools since there is no relocation of the PGW during a connection.
(However, there may be multiple PGWs in the network.)
S1 flex
S1-flex means that the eNodeBs are connected to more than one MME simultaneously, so that the control
traffic from one eNodeB can be distributed across MMEs. A Relative MME Capacity, or “Weight Factor” is
assigned for each MME. Each eNodeB then assigns a UE to an MME proportional to its relative capacity.
This capability is known as S1-Flex. Relative MME Capacity and how it is determined is described in the
TMO21024 MME Overview course.

TMO21054W Issue 1
Page 5:6
The Attach procedure is described later in this module.
Examples of PDNs are:
• Operator’s managed services network (for example, IMS VoIP)
• Enterprise/corporate network
• Public Internet
An APN is used to identify the PDN from which to provide the user’s IP address. It is also used to select a
PGW from which the PDN is accessible.

TMO21054W Issue 1
Page 5:7
The UE sends initial attach requests to the eNodeB and registers with the network to request services.
The eNodeB handles the scheduling of uplink and downlink data to the UE, and connects the UE to the
EPC.
The MME tracks, pages, and authenticates UEs. The MME controls how UEs interact with the network.

TMO21054W Issue 1
Page 5:8
The PGW provides the UE with an IP address and terminates the SGi interface towards the PDN (packet
data network). The PGW also provides Flow Based Charging under control of the PCRF and serves as a
cross-technology mobility anchor.
The SGW serves as the local mobility anchor for UE and terminates the packet data network interface
towards the eUTRAN.
eUTRAN The SGW also performs IP routing and forwarding functions and maintains data paths
between eNodeBs and the PGW.
The PCRF supports per session QoS and associated billing and provides policy information to the SGW, via
the PGW, for establishing default bearer and service-specific bearers.

TMO21054W Issue 1
Page 5:9
TMO21054W Issue 1
Page 5:10
A UE needs to register with the network to receive services that require registration. This registration is
described as network attachment. The always-on IP connectivity for the UE of the EPS is enabled by
establishing a default EPS bearer during network attachment. The attach procedure may trigger one or
multiple dedicated bearer establishment procedures to establish a dedicated EPS bearer for that UE.
During
g the attach procedure,
p , the UE mayy request
q for an IP address allocation.
Attach types:
• International Mobile Station Identifier (IMSI) Attach – The UE sends IMSI in the Attach Request
message as UE identity. The eNodeB selects the MME to forward the Attach Request to.
• Attach with Globally Unique Temporary Identity (GUTI) to the same MME – The UE sends a valid GUTI
in the Attach Request message to the MME identified by the GUTI. The eNodeB derives the MME
from the Globally Unique MME ID (GUMMEI) portion of the ID.
ID
• Combined Evolved Packet System/IMSI (ePS/IMSI), which is used by a Circuit Switch Fallback (CSFB)
enabled UE and Short Message Service (SMS) interworking with UMTS/GSM.
The MME attach procedure differs depending on the UE identity received in the Attach Request message
from the UE. The MME can identify the type of UE identity by examining the EPS mobile identity IE in the
Attach Request message.
IE - information element

TMO21054W Issue 1
Page 5:11
An initial attach procedure begins when the UE is turned on.
The UE is turned on and establishes a radio connection to the eNodeB. The UE is authenticated, and the
PGW assigns an IP address for the UE. Bearers are created through the EPC and through the eUTRAN. The
radio bearer is a data plane through the radio network. Once the radio bearer is established, the UE
receives its IP address
address, and the UE can then use network services
services.

TMO21054W Issue 1
Page 5:12
This scenario is a basic, initial Attach procedure. There are additional Attach scenarios.
Note: If message piggybacking is supported by the MME, SGW, and PGW; and the UE requests a dedicated
bearer before Step 12 (Attach Accept), the request for a dedicated bearer is combined in the default EPS
b
bearer requestt message (St
(Step 7).
7) Thi
This reduces
d network
t k element
l t messaging.
i
1.The user powers on equipment (UE).
2.The UE and eNodeB exchange messages to set up a Radio Resource Control (RRC) connection.
3.The UE sends an Attach Request to the eNodeB with a PDN connectivity Request. The request includes
an International Mobile Station Identifier (IMSI), and the UE Tracking Area Identity (TAI). The eNodeB
sends a S1AP Initial UE Message with the Attach Request to the MME.
4.If the UE does not provide a GUTI or if local MME policy requires it, the MME sends an Authentication
Request to the Home Subscriber Server (HSS). In the power-on case, authentication is always required. If
the UE is authentic, the HSS response includes key information, including: subscriber data, the IP address
of the PGW that serves the APN, and authentication keys that will be used to help provide UE security.
5.The MME sends an Authentication Request message to the UE. The message includes the authentication
key information provided by the HSS so that the MME can verify the UE is valid, and the UE can verify that
the connection is safe.
6.The MME informs the HSS that it is serving the user and provides location information.

TMO21054W Issue 1
Page 5:13
7. The MME selects a Serving Gateway (SGW) and requests a default EPS bearer. The request includes the
IP address for the PGW control plane and the Access Point Name (APN) to identify the external
network and bearer context.
8. The SGW registers with the PGW and sends a Create Default Bearer Request.
9 Th
9. The PGW establishes
t bli h a QQoSS and
dGGateway
t C
Control
t l session
i with
ith th
the P
Policy
li andd Ch
Charging
i RRule
l FFunction
ti
(PCRF). In the response to the SGW, the PGW sends the IP addresses to be used as endpoints to the
connection: IP addresses of the UE and the APN.
10. The PGW begins to forward downlink data. The data is buffered until the Modify Bearer Request is
received (step 16).
11. The SGW sends the UE IP address to the MME.
12. The MME sends an Attach Accept message to the eNodeB, and then on to the UE.
13. eNodeB sends a message that includes the EPS Radio Bearer Identity and the MME Identifier (MMEI) to
the UE.
The request to the SGW for a dedicated bearer may be piggybacked with the request for a default bearer.
Piggybacking is only applicable if all nodes in the chain (MME, SGW, and PGW) support piggybacking.

TMO21054W Issue 1
Page 5:14
14. The MME receives the IP address of the eNodeB.
15. The UE sends an Attach Complete message to MME.
16. The UE can send uplink packets towards the eNodeB, which will be tunnelled to the SGW and PGW,
and on to the PDN.
17. Upon receiving the Attach Complete, the MME sends a Modify Bearer Request to the SGW. The request
includes user location information, any bearer contexts to be modified or removed.
18. The SGW sends a response and begins sending downlink data.
Procedure references
For detailed 3GPP procedure specifications, see 3GPP TS 23.401.
http://www 3gpp org/ftp/Specs/html info/23401 htm
http://www.3gpp.org/ftp/Specs/html-info/23401.htm
Operators may also have modified call flows that are specific to their network and equipment.

TMO21054W Issue 1
Page 5:15
TMO21054W Issue 1
Page 5:16
The EPS bearer is an equivalent of the ‘PDP Context’ used in 2G/GPRS and 3G/UMTS standards. It is a
logical association between the UE and the PGW, and aggregates one or several data flows transported
between the two entities.
An EPS bearer
A b is
i composed d off three
th segments:S5/S8
t S5/S8 bbearer – a tunnel
t l th
thatt ttransports
t packets
k t bbetween
t th
the
SGW and PGW.
S8 is required/used for roaming.
This bearer remains up when the UE is in the IDLE state.
S1 bearer – a tunnel that transports packets between the SGW and eNodeB. This bearer is not up when the
UE is in the IDLE state.
Radio bearer – a Radio Link Control (RLC) connection between the eNodeB and the UE. There is one RLC
protocol
t l machine
hi per radio
di bbearer. Thi
This b
bearer iis nott up when
h ththe UE iis iin th
the IDLE state.
t t

TMO21054W Issue 1
Page 5:17
Default Bearer
An EPS bearer that is established when the UE initially attaches to the network and connects to a PDN is
called a Default Bearer (always with a non-guaranteed bit-rate (non-GBR)). A Default Bearer remains
established throughout the lifetime of the PDN connection to provide the UE with always-on IP
connectivity to that PDN.
PDN Default Bearers can be activated or deactivated independently from one
another.
The default bearer occurs during initial attach and provides the “always on” experience for the user.
Dedicated Bearer
Any additional EPS bearer established to the same PDN by the UE is referred to as a dedicated bearer
(may be GBR or non-GBR). A dedicated Bearer is always associated with a Default Bearer. Default and the
associated
i t dDDedicated
di t d bbearer provide
id connections
ti tto th
the same PDN with
ith diff
differentt guaranteed
t dQ QoS.
S OOne
primary Default bearer might have multiple dedicated bearers assigned.
Each bearer is associated with Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) QoS attributes.
Depending on the UE capability, multi-bearer connections with dedicated QoS-policy on a per bearer basis
can be provided.

TMO21054W Issue 1
Page 5:18
Default Bearers are created on a per PDN basis. Therefore, if a UE is connecting to two PDNs it will need
to establish two default bearers.
EPS Bearer ID
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN (eNodeB). The
EPS Bearer Identity is allocated by the MME. There is one to one mapping between EPS radio bearer (RB)
and EPS Bearer, and the mapping between EPS Radio Bearer (RB) Identity and EPS Bearer Identity is made
by eUTRAN.

TMO21054W Issue 1
Page 5:19
TMO21054W Issue 1
Page 5:20
Either the eNodeB or the MME can initiate the procedure for the UE to change its state to ECM-IDLE. The
eNodeB triggers the change due to UE inactivity, which is the most common reason. The MME is responsible
for signaling the eNodeB and SGW to release the radio and S1 bearers for the UE.
S1 Release Procedure
1. If the eNodeB detects a need to release the UE's signaling connection and all radio bearers for the UE,
the eNodeB sends a message to the MME indicating the reason for the release (e.g.(e g O&M intervention,
intervention
unspecified failure, user inactivity, repeated integrity checking failure, or release due to UE generated
signaling connection release).
2. The MME sends a Release Access Bearers Request message to the SGW that requests the release of all
S1-U bearers for the UE.
3. The SGW releases all eNodeB related information for the UE. Other elements of the UE's SGW context
are not affected. The SGW retains the S1-U configuration that the SGW allocated for the UE's bearers.
4. The MME releases S1 by sending the S1 UE Context Release Command message to the eNodeB.
5. If the RRC C connection is not alreadyy released,, the eNodeB sends an RRC CCConnection Release message g to
the UE in Acknowledged Mode. Once the message is acknowledged by the UE, the eNodeB deletes the
UE's context.
6. The eNodeB confirms the S1 Release by message to the MME. The signaling connection between the
MME and the eNodeB for that UE is then released.
7. The MME deletes any eNodeB related information from the UE's MME context, but, retains the rest of
the UE's MME context including the SGW's S1-U configuration information. All EPS bearers established
for the UE are preserved in the MME and in the SGW.
8. If the cause of S1 release is different from User inactivity, for example, loss of RRC connection, the
MME shall trigger the MME Initiated Dedicated Bearer Deactivation procedure for the GBR bearer(s) of
the UE after the S1 Release procedure is completed.

TMO21054W Issue 1
Page 5:21
When the UE is idle, the EPS bearer is incomplete. If there is an incoming message, the network must
signal the UE to make a service request so that the radio and S1 bearers can be activated, allowing the
message to be delivered.
Here is what happens with an incoming call to an idle UE:
1 A
1. An iincoming
i message ffor th
the UE from
f the
th PDN iis received
i db by th
the PGW and
d fforwarded
d d tto th
the SGW
SGW.
2. The SGW detects that there is no S1 bearer for the UE and sends a downlink data notification to the
MME, triggering a page to be sent to the UE.
3. The MME pages the UE.
4. The UE responds to the page with a NAS service request to establish the required bearers.
5. MME signals the SGW and eNodeB to build the radio and S1 bearers
6. Once the data plane is complete, the message can be delivered to the UE.
Reference for service request is 3GPP TS 23.401 section 5.3.4

Reference for S1 Release (changing to ECM-IDLE) is 3GPP TS 23.401 section 5.3.5

TMO21054W Issue 1
Page 5:22
TMO21054W Issue 1
Page 5:23
The 3GPP standards support two mechanisms to accomplish handovers:
• X2 based handovers make use of X2 connectivity between eNodeBs to directly exchange handover
messages between source and target eNodeBs.
• S1 based handovers are used when there is not a direct forwarding path (X2 interface) between
source eNodeB
N d B andd ttargett eNodeB.
N d B Th
The h
handover
d b
between
t th
the source eNodeB
N d B andd ttargett eNodeB
N d B iis
coordinated by the source MME and target MME (if there is MME relocation).
ANR – Automatic Neighbor Relations

Automatic Neighbor Relations (ANR) is used to construct neighbor lists for LTE eNodeBs. ANR eliminates
the need to manually provision a list of eNodeB and cell neighbors.

TMO21054W Issue 1
Page 5:24
Active handover from eNodeB to eNodeB (without MME or SGW relocation/change)
An active handover from one eNodeB to another eNodeB is shown in this simplified diagram of the LTE
network. Several LTE network elements have been removed from this diagram.
1. The UE (user equipment) is engaged in a 2-way data session with a “terminal.”
2 The eNodeBs agree to prepare to handover based on measurements from the UE.
2. UE
3. Source eNodeB begins forwarding downlink data to the target eNodeB in preparation for the
handover.
4. Source eNodeB instructs the UE to re-tune to the target eNodeB.
5. Target eNodeB sends a path switch request to the MME.
6. The MME sends a User Plane Update Request to the SGW.
7. The path change messages are acknowledged.
8 Target
8. T t eNodeB
N d B iinstructs
t t source eNodeB
N d B tto release
l resources. Th
The h
handover
d iis complete.
l t
This intra-LTE handover is possible while maintaining the MME and SGW, relocating the MME to another
MME, relocating the SGW to another SGW, or both. In addition, the data flows may go to the same PGW
or different PGWs depending upon the services. To maintain the session, the session is anchored on the
PGW despite the changes in the eUTRAN.
As part of handover execution, downlink packets are forwarded from the source eNodeB to the target
eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from the source
eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) SGW to the PGW.
Only the handover completion phase is affected by a potential change of the SGW
SGW. The handover
preparation and execution phases are identical.

TMO21054W Issue 1
Page 5:25
The purpose of an S1 handover is to move the connection from the source cell to target cell. S1 handovers
are used when the X2 control path is not available, or the operator has provisioned (at the eNodeB) the S1
handover.

TMO21054W Issue 1
Page 5:26
1. The UE measures the eNodeBs in its neighborhood and provides a measurement report to the source
eNodeB.
2. The source eNodeB decides that a handover (HO) is warranted and selects the target cell. If the target
cell belongs to a different eNodeB, the eNodeB determines if an X2-based or S1-based handover is
needed In this case,
needed. case the source eNodeB initiates an S1-based
S1 based handover with direct forwarding to the
target eNodeB, and sends a message to the MME that includes the target eNodeB’s identity.
3. The MME sends a request to the target eNodeB.
4. The target eNodeB acknowledges the request. Since this is a direct forwarding case, the target eNodeB
establishes one downlink (DL) X2 tunnel to the source eNodeB.
5. The MME sends a message to the source eNodeB that includes a message from the target eNodeB and
DL data information.
6 Th
6. The source eNodeB
N d B fforwards
d th
the message tto th
the UE
UE. The
Th UE removes any EPS bearers
b for
f which
hi h it did
not receive the corresponding EPS radio bearers in the target cell.
7. The source eNodeB sends a Status Transfer message to the MME.

TMO21054W Issue 1
Page 5:27
8. The MME forwards the Status Transfer to the target eNodeB.
9. The source eNodeB begins a direct forwarding of DL data to the target eNodeB (assuming direct
forwarding is activated at both eNodeBs).
10.After the UE synchronizes to the target cell, it sends a Handover Confirm message to the target
eNodeB.
N d B D Downlink
li k packets
k t fforwarded
d d ffrom th
the source eNodeB
N d B can b
be sentt tto th
the UE
UE. Al
Also, uplink
li k
packets can be sent from the UE, which are forwarded to the target SGW and on to the PGW.
11.The target eNodeB sends a Handover Notify message to the MME.
12.The MME sends a Modify Bearer Request (eNodeB address) to the target SGW for each PDN connection.
The MME also starts a timer to supervise when resources in the source eNodeB can be released.
13.The SGW sends a Modify Bearer Response to MME.
14.Downlink packets from the SGW are sent on to the target eNodeB.
15.The UE initiates a Tracking Area Update (TAU) procedure. The MME knows that it is a Handover
procedure (as it received the bearer contexts by handover messages) and therefore the target MME
performs only a subset of the TA update procedure.
16.When the timer started in step 12 expires, the source MME sends a UE Context Release Command
message to the source eNodeB (to release resources in the source eNodeB).
17.The source eNodeB releases its resources related to the UE and responds with a UE Context Release
Complete message.

TMO21054W Issue 1
Page 5:28
TMO21054W Issue 1
Page 5:29
LTE is an access network that allows UEs to connect to network services. IMS is a network that can provide
VoIP services to the UEs.
This slide show that LTE and IMS are two distinct networks. LTE provides the UE access to the IMS
network,
t k b
butt th
the access it provides
id mustt iinclude
l d bbearers with
ith a Q
QoSS tto supportt IMS signaling
i li and
d media
di
(voice).
This slide identifies some of the interfaces used between the EPC and the IMS components:
• S6b – AAA from the PGW
• S6a - HSS to the MME
• SGi – IP network to the PGW
• Rx - PCRF from the ISC
ISC - IP Session Controller

TMO21054W Issue 1
Page 5:30
Voice is an IMS application. SIP signaling is used for voice call signaling (yellow line), and RTP is used for
voice traffic. There is no circuit switched voice carried across the LTE network. IMS must provide the
gateway between the IP and circuit switched networks (between the MGW and the MGC (which is not
shown)).
LTE provides access to the PDN containing the IMS applications.
applications
VoIP signaling and voice media require a better QoS than the default bearer provides and will typically
require additional bearers. However, it is not mandatory and is up to the carriers to decide which bearers
will carry which traffic.

TMO21054W Issue 1
Page 5:31
In this VoIP to VoIP example, the voice media traffic is transmitted directly to the other UE in the call. It
does not go through the IMS network.
Notice that the packets are routed to the other UE by the PGW even though the UEs are using the same
SGW This
SGW. Thi iis b
because th
the eNodeB
N d B andd SGW are ttunneling
li ththe d
data
t th
through
h LTE and
d only
l consider
id ththe IP
addresses in the GTP tunnel headers, not the payload.

TMO21054W Issue 1
Page 5:32
The following procedure illustrates an IMS emergency service example.
1. UE detects emergency number is dialed and initiates Emergency Attach. (Emergency numbers are stored in the
UE (i.e., 911 default). The network may optionally download a list of additional emergency numbers to the UE so
the UE can detect if additional emergency numbers are dialed. Up to 8 emergency numbers can be provisioned at
the MME for this purpose).
2. eNodeB sets the Radio Resource Control (RRC) establishment cause to “Emergency” for these cases:
• Emergency Attach (Attach request with Attach type to “EPS Emergency”.
• Emergency PDN connectivity for normally attached UEs (PDN connectivity request type set to “Emergency”).
• Service Request to set up Emergency call.
3. MME recognizes that this is a priority emergency call.
• MME uses Emergency configuration data to establish emergency bearer services and select the PGW associated
with the Emergency APN.
• The Emergency APN, Emergency QoS profile, and Emergency APN-AMBR (QoS parameters that are applied
to aggregated set of EPS Bearers) are previously provisioned on the MME.
• The MME records the existence of an active Emergency call in the UE Context.
Context
• If the UE becomes IDLE, the MME starts a special emergency reachable timer (provisioned with a similar value
to the UE’s periodic TAU timer).
4. The IMS handles emergency IMS registration.
5. The Emergency Call State Control Function (E-CSCF) in the IMS routes UE location information to a Public Safety
Answering Point (PSAP).
6. A user plane is established for voice.
7. PSAP may inquire UE location information from the Gateway Mobile Location Center (GMLC) and Location
Retrieval Function (LRF) in order to dispatch emergency services to the correct address.
Call-back from a PSAP is supported for UEs that are not operating in the limited service state,
state but priority paging
for Emergency Bearer Services is not supported.

TMO21054W Issue 1
Page 5:33
The MME Warning Message Delivery function supports a Commercial Mobile Alert System (CMAS) and allows
warning messages to be sent to a UE in a particular area. The MME receives warning messages from a Cell
Broadcasting Center (CBC) using the SBc interface, and the MME forwards these messages to the eNodeBs.
Control and provisioning
P i i i iincludes
Provisioning l d setting
tti up th
the SB
SBc iinterface
t f tto th
the CBC.
CBC
This functionality also uses the TAI to eNodeB mapping that is already contained on the MME for normal
call processing.
Network requirements
CMAS support on the eNodeB and Cell Broadcast Center is required. The CMAS service is applicable to
mobiles that support Warning Message Delivery.
Notes: The public warning system is intended to alert the general public of public threats such as flu
pandemics, toxic spills, terrorist threats, and natural disasters from tsunamis, earthquakes, or wildfires.
Recipients do not have to sign up to receive alerts on the SIB12 cell broadcast channel, but they can opt-
out by turning off the broadcast channel on their handsets. Whereas SMS messages are sent point-to-
point, Cell Broadcast messages are sent point-to-area. Cell Broadcast is not as affected by traffic load and
it may be usable during a disaster when load spikes occur.

TMO21054W Issue 1
Page 5:34
1. CBC receives notice of warning alert to be sent to a regional area.
2. CBC sends the MME (or pool of MMEs) a Write-Replace Warning Request over the SBc interface. The
request includes a TAI list, the warning message, and number of times to repeat the broadcast.
3. The MME determines which eNodeBs are within the TAI list and sends S1 Write-Replace Warning
R
Request
t messages tto each
h off th
them.
4. The eNodeBs send the broadcast message to UEs in serving area.
• The MME verifies receipt and validation of the Request at the eNodeBs – it does not depend on a
positive response from UEs.
• Broadcast continues at repetition interval until:
1. Number of Broadcast Requested is achieved
2. Broadcast is cancelled by the CBC (using Stop Warning request)
3. Broadcast is replaced with different content by the CBC (using another Write-Replace Warning
Request ).

TMO21054W Issue 1
Page 5:35
TMO21054W Issue 1
Page 5:38
TMO21054W Issue 1
Page 5:39
TMO21054W Issue 1
Page 5:41
TMO21054W Issue 1
Page 6:1
• Compare HxPA+ to LTE.
• Compare CDMA/EvDO to LTE.
• Compare WiMAX to LTE.
• Describe basic interworking of LTE with 3GPP and non-3GPP networks.

TMO21054W Issue 1
Page 6:2
This module contains sections specific to CDMA and UMTS.
These sections are optional.

TMO21054W Issue 1
Page 6:3
This CDMA section is optional. The final assessment will NOT contain questions on this section of this
module.

TMO21054W Issue 1
Page 6:4
1. LTE VoIP interworking with 3G1X Circuit Networks – Call Delivery only
• LTE is used for Voice (IMS VoIP) and data, and 3G1X circuit voice is used when a user is roaming;
handover is not required because the home network is well covered with LTE access. A single
mobile number, IMS VCC (Voice Call Continuity) application server, and 7510 MGW call anchor
assure that calls are delivered to a user regardless of the network they are in.
in
2. LTE VoIP Interworking with 3G1X Circuit Networks – Voice Call Continuity
• LTE is used for Voice (IMS VoIP) and data, and 3G1X circuit voice is used when a user drops out of
LTE coverage; handover is required in this example scenario because LTE coverage is spotty within
the home network area, to assure uninterrupted calls for users. In addition to call delivery as in
Case 1, call will handover from VoIP in LTE to the 3G1X Circuit MSC.
3. 3G1X Circuit Switched Fallback
• LTE iis used
d ffor d
data
t only,
l and
d 3G1X circuit
i it voice
i iis used
d ffor all
ll voice
i calls.
ll LTE coverage overlaps
l
3G1X coverage. No IMS VoIP is required, however dual mode handsets will not be capable of
simultaneous voice and data service.

TMO21054W Issue 1
Page 6:5
An LTE data overlay solution allows service providers to expand their data services by adding the LTE
network and interworking it with existing 2G and 3G networks. Base networks can interwork with LTE and
use LTE as a means to expand and improve data services and take advantage of new spectrum.
The user equipment (UE) will initially be a separate device for data services only (for example, a laptop
card or PDA)
PDA). UEs will be dual
dual-mode
mode to support both LTE and CDMA.
CDMA The dual-mode
dual mode UE can access the LTE
network when available, and the CDMA network if perhaps there is no LTE network coverage.

TMO21054W Issue 1
Page 6:6
This diagram illustrates CDMA and LTE interworking, with voice over IP using the IMS network.
The diagram also identifies interfaces that can be used in the future for handovers. To support handovers,
the MME can signal the eHRPD Radio Network Controller (eRNC, which is a CDMA RNC enhanced to support
the LTE network) in the CDMA network over the S101 interface (or to the 3G1X MSC over the S102
interface).
interface)

TMO21054W Issue 1
Page 6:7
CDMA and LTE networks are shown in this diagram of an LTE data overlay with the Circuit Switched
Fallback solution.
Like the data overlay case, this offer allows data services to interwork with existing 2G and 3G networks.
In addition, the UE will be alerted of pending circuit voice calls. This is referred to as “Circuit Switched
Fallback ” The mobile will receive the alert for an incoming voice call.
Fallback. call (The alert of the incoming voice
call comes over the LTE network.) If the user elects to accept the call, the mobile will handover to the
2G/3G network for the circuit voice. For circuit voice on the 2G network, the data session is suspended.
For circuit voice on the 3G network, the data session is handed over to the 3G network for both the circuit
voice and data sessions.
• The AAA is required when interworking with a CDMA or UMTS network.
• New or evolved components in the CDMA network:
• eHRPD
• eRNC
• eBTS
• HSGW

TMO21054W Issue 1
Page 6:8
Data sessions can be handed over from LTE to eHRPD in active or idle mode, and from eHRPD to LTE in
idle mode.
The MME supports UEs that are designed to use a 3G1X network for voice and SMS and to use an overlying
LTE network for data. The UEs supported by this feature are equipped with dual transceivers (DTR), so
that the UE can monitor the 3G1X network overhead channels while actively connected to LTE.
LTE A DTR UE
can originate and terminate voice calls and SMS messages on the 3G1X network without the use of an S102
interface between the LTE and 3G1X networks.
Call flow for a non-optimized LTE to eHRPD handover is shown on the next slide.
Idle mode cell reselection and handover between different LTE frequency bands is supported.

TMO21054W Issue 1
Page 6:9
Non-optimized handover involves the movement of the UE from the eUTRAN to the eHRPD (or vice-versa)
without the use of tunneled signaling (that is, without the use of the S101 interface between the MME and
the eRNC). The UE leaves the radio environment of the source access network and performs a radio-level
attachment to the target access network. For example, the UE creates an eHRPD session when it moves from
the eUTRAN to the eHRPD, and then performs a handover attach procedure to the Packet Data Network(s) it
had been communicating with over the source access network.
network Non-optimized handover applies to both
active and idle UEs.
The latency (or gap in packet flow) can be several seconds in a non-optimized handover for active UEs.
1. The dual-mode UE in LTE mode moves toward the eHRPD-only coverage area.
2. The border eNodeB cells are provisioned with eHRPD information and the eNodeB sends SIB-8 containing
the eHRPD
information to the UE over the BCCH.
3a. In RRC_Idle mode the UE performs inter-RAT cell reselection based on cell signal quality measurements
and retunes from LTE radio access technology gy ((RAT)) to eHRPD RAT.
OR
3b. In RRC_Connected mode the UE sends a measurement report to the eNodeB associated with a
configured inter-RAT measurement. The eNodeB releases the RRC connection with inter-RAT redirection
information and the UE reselects eHRPD.
4. The UE establishes an eHRPD session (if none was previously established) and triggers a handover attach.
After the handover, the UE session with the PGW(s) is maintained (e.g., the same IP address is assigned).
Note that for the active case the non-optimized inter-RAT mobility is non-seamless (packets are lost and
there will be a gap in packet delivery). This is service affecting to applications like VoIP. Optimized handover
(using pre-registration, S101 tunneling,
l and
d S103 packetk fforwarding)
d would
ld b
be requiredd ffor seamless
l mobility.
bl

TMO21054W Issue 1
Page 6:10
This UMTS section is optional. The final assessment will NOT contain questions on this section of this
module.

TMO21054W Issue 1
Page 6:11
The EPC supports an interface between the MME and the SGSN in a pre-Release 8 and a Release 8
GPRS/WCDMA network.
GPRS - General Packet Radio Service

WCDMA – Wideband CDMA (i.e., UMTS)
I-RAT - Inter-Radio Access Technology

TMO21054W Issue 1
Page 6:12
TMO21054W Issue 1
Page 6:13
TMO21054W Issue 1
Page 6:14
This diagram illustrates the interworking between the LTE network and the UMTS/GSM network. Mobility
support includes 2G (GPRS/EDGE) support as well as 3G (WCDMA). The UMTS and GSM networks have been
combined into one diagram for simplicity (they are closely related – much of UMTS was built on GSM
technology).
y used—some are for 3GPP p

Not all the interfaces shown are always pre-release 8 scenarios,, others are for
release 8 scenarios.
The MME can support both pre-release 8 SGSN and release 8 SGSN. Pre-R8 uses the Gn interface between
the SGSN and MME and between the SGSN and PGW.
In Release 8, the S3 interface between the MME and SGSN, and the S4 interface between the SGSN and
SGW, are supported. S3/Gn and S4/Gn can coexist.
The PGW is required to be a GGSN and a legacy GGSN remains in place for non-LTE capable mobiles.
Interworking exists between S6a and Gr for a legacy HLR/HSS in roaming cases.
GERAN – GSM-EDGE (Global System for Mobile Communications - Enhanced Data rates for GSM Evolution)
R di A
Radio Access NNetworkk
UTRAN = UMTS Terrestrial Radio Access Network BSC = Base Station Controller
RNC = Radio Network Controller WCDMA – Wideband CDMA (i.e., UMTS)
SGSN = Serving GPRS Support Node MSC = Mobile Switching Center
VLR = Visitor Location Register GGSN = Gateway GPRS Support Node
GPRS = General Packet Radio Service EDGE = Enhanced Data Rates for GSM Evolution
The UMTS and GSM networks have been combined into one diagram for simplicity (they are closely related
– much of UMTS was built on GSM technology). Interface names with slashes (Iu_cs/A for example)
represent the UTRAN and GERAN interface names respectively.
respectively

TMO21054W Issue 1
Page 6:15
Mobility in idle mode uses cell reselection in which a 2G, 3G, or LTE cell is selected using cell
measurements.
Mobility in active mode uses cell reselection when the UE is transferring packets, and uses cell redirection
to push the UE to, or from, LTE coverage.
Packet
P k t switched
it h d h
handovers
d are supported
t d with
ith b
both
th P
Pre-Release
R l 8 and
dRRelease
l 8 versions
i off th
the llegacy
core network.
Voice call continuity is provided between 2G/3G and LTE via circuit switched fallback, IMS, or VOLGA.
VOLGA - Voice over LTE via Generic Access

TMO21054W Issue 1
Page 6:16
UMTS and LTE networks are shown in this LTE data overlay network diagram. UMTS components are at the
top of the diagram. Similar to the CDMA data overlay solution, this offer allows data services to interwork
with existing 2G/3G networks. The mobile device will be alerted of pending circuit voice calls. (The alert
of the incoming voice call comes over the LTE network.) This is referred to as “Circuit Switched Fallback”.
The mobile will receive the alert for an incomingg call and,, if the user elects to accept
p the call,, the mobile
will handover to the 2G/3G network for the circuit voice. For circuit voice on the 2G network, the data
session is suspended. For circuit voice on the 3G network, the data session is handed off to the 3G
network for both the circuit voice and data sessions.
The AAA is required when interworking with a CDMA or UMTS network.

TMO21054W Issue 1
Page 6:17
Options for supporting voice services in LTE are described here: Circuit Switched Fallback and Voice over
IMS.
MT - Mobile Termination - means that someone is calling the UE.

MO - Mobile Origination - means that the UE is calling someone.

TMO21054W Issue 1
Page 6:18
18
UMTS and LTE networks are shown in this diagram of an LTE data overlay with the Circuit Switched
Fallback solution.
Like the data overlay case, this offer allows data services to interwork with existing 2G and 3G networks.
In addition, the UE will be alerted of pending circuit voice calls. This is referred to as “Circuit Switched
Fallback”. The mobile will receive the alert for an incoming voice call.
Fallback call (The alert of the incoming voice
call comes over the LTE network.) If the user elects to accept the call, the mobile will handover to the
2G/3G network for the circuit voice. For circuit voice on the 2G network, the data session is suspended.
For circuit voice on the 3G network, the data session is handed over to the 3G network for both the circuit
voice and data sessions.
The 8950 AAA is required when interworking with a CDMA or UMTS network.
• New or evolved components in the UMTS network:
• The Gn interface is used for interworking the SGSN with the PGW. To support this interface, the
PGW provides the functional equivalency of the GGSN.
• New or evolved components in the LTE network:
• AAA (required for interworking with UMTS)
A circuit switch fallback enabled terminal, connected to eUTRAN, may use the GERAN or UTRAN to
establish one or more circuit switch domain services. The initiation of circuit switch fallback in the
eNodeB is at the UE Context Management level (S1AP Initial Context Setup and S1AP UE Context
Modification).

TMO21054W Issue 1
Page 6:19
Inter-RAT Mobility – Cell reselection and redirection
LTE-to-UMTS/GSM mobility of a multi-mode UE in RRC_IDLE mode refers to a UE leaving LTE coverage to
recover service in UMTS/GSM coverage as soon as it gets available (that is, when radio conditions are
sufficient). It also enables LTE-to-UMTS/GSM mobility in RRC_CONNECTED mode when a UE with an on-
going packet data session leaves LTE coverage via RRC release and redirection.
redirection RRC release/redirection
provides a network based mobility control for an RRC_CONNECTED UE when packet switch handover is not
supported by the UE and the network. RRC redirection capability allows the eNodeB to perform a cell
reselection to a target cell based on target cell measurements or configuration when LTE radio conditions
have degraded below a pre-defined threshold, and the UMTS/GSM neighbor cell provides better radio
conditions.
PS handover
LTE-to-UMTS/GSM mobilityy of a multi-mode UE in RRC_CONNECTED mode refers to a UE with an on-going g g
packet data session that is leaving LTE coverage via packet switch handover. The triggering condition for
packet switch handover is the LTE radio condition degradation below a pre-defined threshold. A pre-
configured target cell in the UMTS/GSM layer (specifically for mobility continuity purposes) is used for the
handover. Packet switch handover is supported without the target UMTS cell measurement support. EPC
supports packet switch handover to Pre-Release 8 and Rel. 8 WCDMA packet core networks. Indirect data
forwarding with indirect tunneling over S4 (Rel. 8+) or Gn (Pre-Release 8).
SMS - Short Message Service CSFB - Circuit-Switched Fallback
NACC – Network
k Assisted
d Cell
ll Change
h IRAT - Inter-Radio
d Access Technology
h l
UTRAN – UMTS RAN

TMO21054W Issue 1
Page 6:20
CSFB with UE in idle mode
Circuit-switched fallback for a UE in idle mode is illustrated in this diagram.
1. The GMSC gets an IAM message from the network that a voice call is incoming. The GMSC sends a
message to the MSC.
2. The MME receives a Paging Request message from the MSC.
3. The MME sends a Paging Request message to each eNodeB that includes the UE Identity (S-TMSI or
IMSI) and indicates that the CS domain initiated the paging message.
4. The eNodeB pages the UE.
5. The UE responds to the MME with an Extended Service Request.
6. The MME sends a request message to the MSC containing an indication that the UE was in idle mode
(i.e. the UE has not received any Calling Line Identification information).
7. The MME sends a message to the eNodeB to direct the eNodeB to move the UE to the
UTRAN/GERAN.
8. The UE responds to the eNodeB, and Inter-RAT mobility begins at this point.
IAM = Initial Address Message

TMO21054W Issue 1
Page 6:21
The Gn interface (for Pre-Rel. 8 SGSN) is implemented in the MME to allow the MME to effectively
handover for a user who transitions from:
• 3GPP UMTS network to the LTE network
• LTE network to a 3GPP UMTS network
As per 3GPP TS 25.304 (v8.6.0, June 2009), stored information for several Radio Access Technologies
(RATs) may be available in the UE. In idle mode, the UE regularly searches for a better cell as per cell
selection criteria. When a better cell is found, inter-RAT redirection begins - the eNodeB requests that
the MME release UE context, and the MME and SGW begin a dialogue in order to release access bearers
and delete bearers for the UE.
Release 8 SGSN uses the S3 interface.

TMO21054W Issue 1
Page 6:22
Inter-Radio Access Technology (IRAT) Packet Switch Handover
User Traffic is flowing in both the uplink and downlink. The UE is in ECM-CONNECTED state over LTE
eUTRAN access.
1. The source eNodeB decides to initiate an Inter-RAT mobility event to the target UTRAN system using
PSHO If the
PSHO. th UE supports
t measurements, t the
th UE will
ill be
b directed
di t d tto gett th
the UTRAN measurements.
t
The RNC sends a Handover Required message to the MME to establish resources on the RNC, SGW,
and SGSN.
2. The MME determines that this is an IRAT request and initiates resource allocation using the Forward
Relocation Request.
3. The SGSN requests the RNC to allocate radio network resources (RABs).
4. The RNC allocates resources and returns RAB information to the SGSN.
5. The SGSN returns the Forward Relocation Response message to the MME, including the RABs and
SGSN information.
6. The MME sends the HO command to the eNodeB for a PSHO IRAT handover. The HO command
includes the UTRAN bearer and control information.

TMO21054W Issue 1
Page 6:23
7. The eNodeB requests the UE to handover to the target UTRAN network. The message includes the
radio bearer information provided by the RNC.
8. UE detaches from the eNodeB and retunes to the UTRAN using the radio resources that were
established.
9 The
9. Th RNC sends
d aR
Relocation
l ti C Complete
l t message tto th
the SGSN
SGSN.
10. The SGSN sends a Relocation Complete message to the MME.
11. The MME acknowledges that the relocation is complete.
User Traffic is flowing in both uplink and downlink directions.

TMO21054W Issue 1
Page 6:24
TMO21054W Issue 1
Page 6:25
TMO21054W Issue 1
Page 6:26
TMO21054W Issue 1
Page 6:27
TMO21054W Issue 1
Page 6:30
TMO21054W Issue 1
Page 6:31
TMO21054W Issue 1
Page 6:32
TMO21054W Issue 1
Page s:1
TMO21054W Issue 1
Page s:2
TMO21054W Issue 1
Page s:3
TMO21054W Issue 1
Page s:4
• This completes the course TMO21054W - LTE Overview.

TMO21054W Issue 1
Page s:5
Appendix A: LTE acronyms and abbreviations
Numbers
1X CDMA2000 1X
1X RNC 1X Radio Network Controller
2G 2nd Generation (GSM, TDMA, IS95A)
3G 3rd Generation (CDMA2000, UMTS)
3GPP Third Generation Partnership Project
3GPP2 Third Generation Partnership Project 2
4G 4th Generation
A
AAA Authentication, Authorization, and Accounting
AAT Average Aggregate Throughput
ACK Acknowledgement
ACL Access Control List
ACLR Adjacent Channel Leakage Ratio
ADMF Administrative Function
AF Assured Forwarding
AF Application Function
AGW Access Gateway
aIMS Advances to IP Multimedia Services
AKA Authentication and Key Agreement
ALU Alcatel-Lucent
AM Acknowledge Mode
AMBR Aggregate Maximum Bit Rate
AM Access Manager
AM Accounting Management
AMC Advanced Mezzanine Card
AN Access Network
AN Access Node
ANDSF Access Network Discovery and Selection Function

TMO21054 Issue 1
Page A:1
ANR Automatic Neighbor Relationship
AP Application Processor
AP Application Protocol
APB Active Phone Book
APN Access Point Name
AR Access Router
AR Aggregation Router
ARP Allocation and Retention Priority
ARQ Automatic Repeat Request
AS Access Stratum
AS Application Server
ASN.1 Abstract Syntax Notation 1
ASN-GW Access Service Network Gateway
AT Access Terminal
ATCA Advanced Telecommunications Computing Architecture
ATCA-LCP Advanced Telecommunications Computing Architecture –
Liquid Cooling Package
AVP Attribute Value Pair
AWS Advanced Wireless Services
B
BCCH Broadcast Control Channel
BCH Broadcast Channel
BE Best Effort
BHCA Busy Hour Call Attempts
BHL Back Haul
BM Bearer Manager
BM-SC Broadcast-Multicast Service Center
B-PCF 1X RNC Blade PCF
BRC Baseband Resources Controller
BS (BTS) Base Station
BSR Base Station Router
BSC Base Station Controller
BTS (BS) Base Transceiver Station
TMO21054 Issue 1
Page A:2
C
CAC Call Admission Control
CALEA Communications Assistance for Law Enforcement Act
CAZAC Constant Amplitude Zero Auto-Correlation
CB Controler Board
CBC Cell Broadcasting Center
CC Content of Communication
CC Cumulative Counter
CCCH Common Control Channel
CCM Common Chassis Management
CDMA Code Division Multiple Access
CER Capabilities Exchange Request (Diameter Setup)
CFC Call Final Class
CFCQ Call Final Class Qualifier
C/I Carrier-to-Interference Power Ratio
CIM Circuit Interface Module
CLI Command Line Interface
CM Configuration Management
CMAS Commercial Mobile Alert System
CMC Connection Mobility Control
CMIP Client Mobile IP
CN Core Network
CNFG Configuration
CORBA Common Object Request Broker Architecture
CP Cyclic Prefix
C-plane Control Plane
CPRI Common Public Radio Interface
CPU Central Processing Unit
CQI Channel Quality Indicator
CRC Cyclic Redundancy Check
C-RNTI Cell RNTI
CS Circuit Switched

TMO21054 Issue 1
Page A:3
CTM-HSSPC Controller Turbo Mode - High Speed Serial Protocol
Controller (Xilinx IP)
CU Controller Unit
D
d2U Digital 2 Unit
d4U Digital 4 Unit
DCCH Dedicated Control Channel
DCI Downlink Control Information
DER Discrete Event Registration
DF Delivery Function
DHCP Dynamic Host Configuration Protocol
DL Downlink
DL-SCH Downlink Shared channel
DO CDMA Data Only
DNS Domain Name Server
DPH Data Protocol Handler
DPI Deep Packet Inspection
DRA&PS Dynamic Resource Allocation & Packet Scheduling
DRB Data Radio Bearer carrying user plane data
DRX Discontinuous Reception
DS1 Digital Signal level 1 (1.544 Mbit/s)
DSC Dynamic Service Controller
DSCH Downlink Shared Channel
DSCP Differentiated Services Code Point
DTCH Dedicated Traffic Channel
DTR Dual Transceiver
DTX Discontinuous Transmission
DWR Device Watchdog Request (heartbeat)
E
E1 Standard European PCM link (2.048 Mbit/s)
eAT Evolved Access Terminal
EBI EPS Bearer ID
TMO21054 Issue 1
Page A:4
eBTS Enhanced Base Transceiver Station
ECM EPS Connection Management
E-DCH Enhanced Dedicated Channel
EDGE Enhanced Data rates for GSM Evolution
EF Expedited Forwarding
eHRPD Evolved High Rate Packet Data
EIR Equipment Identity Register
ELP ECP Location Services Protocol
EML Element Management Level
EMM EPS Mobility Management
EMS Element Management System
eNodeB (eNB) Evolved NodeB
EPC Evolved Packet Core
ePDSN Evolved Packet Data Serving Node
EPS Evolved Packet System
eRNC Evolved Radio Network Controller
ESD Electrostatic Discharge
ESM Evolved Session Management
E-SMLC EPS Serving Mobile Location Center
eUTRAN Evolved Universal Terrestrial Radio Access Network
EVDO Evolution-Data Optimized or Evolution-Data Only
F
FA Foreign Agent
FBC Flow Based Charging
FCAPS Fault, Configuration, Accounting, Performance, and Security
FDD Frequency Division Duplex
FDM Frequency Division Multiplexing
FFS For Future Study
FM Fault Management
FRS Feature Requirements Specification
FRU Field Replaceable Unit
FQDN Fully Qualified Domain Name
FS Frame Selection
TMO21054 Issue 1
Page A:5
FTP File Transfer Protocol
G
GBR Guaranteed Bit Rate
GERAN GSM EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GMLC Gateway Mobile Location Center
GNSS Global Navigation Satellite System
GPRS General Packet Radio Service
GRE Generic Routing Encapsulation
GSM Global System for Mobile
GTP GPRS Tunneling Protocol
GTP-C GPRS Tunneling Protocol - Control
GTP-U GPRS Tunneling Protocol - User
GUI Graphical User Interface
GUMMEI Globally Unique MME Identifier
GUTI Globally Unique Temporary Identity
H
HA Home Agent
HARQ Hybrid ARQ
HO Handover
H-PCRF Home PCRF
H-PLMN Home PLMN
HRPD High Rate Packet Data
HSDPA High Speed Downlink Packet Access
HSGW HRPD Serving Gateway
HSPD High Speed Packet Data
HSPP High Speed Packet Processor
HSRP Hot Standby Router Protocol
HSS Home Subscriber Server
HSSL High Speed Serial Link
HSSPC High Speed Serial Protocol Controller

TMO21054 Issue 1
Page A:6
HW Hardware
I
ICIC Inter-Cell Interference Coordination
IE Information element
IETF Internet Engineering Task Force
IM Instant Messaging
IMEI International Mobile Equipment Identifier
IMS IP Multimedia Subsystems
IMSI International Mobile Station Identifier
IP Internet Protocol
IPBH Internet Protocol Back Haul
IPM IP Manager
IPMI Intelligent Platform Management Interface
IPSec Internet Protocol Security
I-RAT Inter-Radio Access Technology
IRI Intercept Related Information
ITU International Telecommunication Union
J
JMS Java Message Service
K
KPI Key Performance Indicator
L
L1 Layer 1
L2 Layer 2
L3 Layer 3
LA Location Area
LAI Location Area Identity
LB Load Balancing
LVI LVI Application Function
TMO21054 Issue 1
Page A:7
LBI Linked EPS Bearer Identity
LBO Local Break Out
LBS Location Based Service
LCID Logical Channel Identifier
LCP Linux Control Platform
LCR Low Chip Rate
LCS Location Services
LDAC Load Distribution and Access Control
LEA Law Enforcement Agency
LED Light-emitting Diode
LEMF Law Enforcement Monitoring Function
LI Lawful Interception
LIF LVI Interface Function
LMA Local Mobility Anchor
LMT Local Maintenance Terminal
LPP LTE Positioning Protocol
LR Location Request
LRF Location Retrieval Function
LSN Local Secure Network
LTE Long Term Evolution
LVI LTE Voice Interworking
M
MAC Medium Access Control
MAF MME Application Function
MAG Mobility Access Gateway
MBMS Multimedia Broadcast Multicast Service
Mbps Megabits per second
MBR Maximum Bit Rate
MCC Mobile Country Code
MCCH Multicast Control Channel
MCE Multicast Control Entity
MCM Media Conversion Module
MCS Modulation and Coding Scheme
TMO21054 Issue 1
Page A:8
MEI Mobile Equipment Identifier
META Mobile Evolution Transport Architecture
MGW Media Gateway
MI Management Interface
MIB Management Information Base
MIF MME Interface Function
MIMO Multiple Input Multiple Output
MIP Mobile Internet Protocol
MLS Multi-Layer Switch
MM Mobility Management
MME Mobility Management Entity
MMEC MME Code
MMEGI MME Group Id
MMEI MME Identifier
MNC Mobile Network Code
MO Mobile Origination
MO Managed Object
MPLS Multi-Protocol Label Switching
MSC Mobile Switching Center
MSIN Mobile Subscriber Identification Number
MT Mobile Termination
MTCH MBMS Traffic Channel
MTU Maximum Transmission Unit
MU Modem Unit
N
NACK Non-Acknowledgement
NAPTR Name Authority Pointer
NAS Non-Access Stratum
NBI Northbound Interface
NE Network Element (AGW or ENB)
NEL Network Element Level
NEM Network Element Manager
NML Network Management Level
TMO21054 Issue 1
Page A:9
NMS Network Management System
NSA National Security Agreement
NTP Network Time Protocol
O
OA&M (OAM) Operations, Administration, and Maintenance
OCAN Offline Configuration of Access Networks
OCS Online Charging System
OFCS Offline Charging System
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OMC Operations Management Centre
OMC-RAN Operations and Maintenance Center – Radio Access Network
OMP Operations and Management Platform
OOS Out of Service
OS Operating System
OSS Operations Support System
P
PA Power Amplifier
PAPR Peak-to-Average Power Ratio
PBCH Physical Broadcast Channel
PBR Prioritized Bit Rate
PCC Policy and Charging Control/Policy Control and Charging
PCCH Paging Control Channel
PCEF Policy and Charging Enforcement Function
PCFICH Physical Control Format Indicator Channel
PCI Physical Cell Identifier
PCMD Per Call Measurement Data
PCRF Policy and Charging Rules Function
PDCCH Physical Downlink Control Channel
PDCP Packet Data Context Protocol
PDN Packet Data Network

TMO21054 Issue 1
Page A:10
PDP Packet Data Protocol
PDSN Packet Data Serving Node
PDU Packet Data Unit
PEF Policy Enforcement Function
PEM Power Entry Module
PGW (P-GW) Packet Gateway (Packet Data Network Gateway)
PHICH Physical Hybrid ARQ Indicator Channel
PHY Physical layer
PIM Packet Interface Module
PLMN Public Land Mobile Network
PM Performance Management
PM Performance Measurements
PMC Performance Measurement Counter
PMIP Proxy Mobile IP
PO Processor Occupancy
PPP Point to Point Protocol
PRB Physical Resource Block
PS Packet Switched
PSAP Public Safety Answering Point
PSC Packet Scheduling
PSTN Public Switched Telephone Network
PTM-MC Point-to-Multipoint, Multi-Cell
PTM-SC Point-to-Multipoint, Single-Cell
Q
QAM Quadrature Amplitude Modulation
QCI QoS Class Identifier
QoS Quality of Service
QRM Quality and Reliability Measurements
R
RA Routing Area
RAC Radio Admission Control

TMO21054 Issue 1
Page A:11
RACH Random Access Channel
RA-RNTI Random Access RNTI
RAN Radio Access Network
RAT Radio Access Technology
RAU Routing Area Update
RB Radio Bearer
RBAC Role-Based Access Control
RBC Radio Bearer Control
RBP Rack Back Plane
RCC Reliable Cluster Computing
ReM Redundancy Manager
RF Radio Frequency
RFC Request For Comments
RLC Radio Link Control
RMT Remote Maintenance Terminal
RNC Radio Network Controller
RNL Radio Network Layer
RNTI Radio Network Temporary Identifier
R-OCM Reverse - Optical Control Module
ROHC Robust Header Compression
RQMS Reliability and Quality Measurements for
Telecommunications Systems
RRC Radio Resource Control
RRH Remote Radio Head
RRM Radio Resource Management
RTM Rear Transmission Module
RTT Radio Transmission Technology
RU Resource Unit
RUC Rack User Commissioning
RX Receive
S
S1-MME S1 for the control plane
S1-U S1 for the user plane
TMO21054 Issue 1
Page A:12
SACK SCTP Acknowledgement
SAE System Architecture Evolution
SAM Service Aware Manager
SAP Service Access Point
SAR Service Aggregation Router
SC-FDMA Single Carrier - Frequency Division Multiple Access
SCH Synchronization Channel
SCM System Control Module
SCP Secure Copy
SCTP Stream Control Transmission Protocol
SDF Service Data Flow
SDM Subscriber DB Manager
SDMA Spatial Division Multiple Access
SDU Service Data Unit
SFM Switch Fabric Module
SFN Single Frequency Network
sFTP Secure File Transfer Protocol
SGSN Serving GPRS Support Node
SGW (S-GW) Serving Gateway
SGW Signaling Gateway
ShMC Shelf Management Controller
SIP Session Initiation Protocol
SLOAM Slave Operation and Administration
SM Security Management
SM Session Management
SMC Security Mode Command
SMS Short Message Service
S-NAPTR Straightforward Name Authority Pointer
SNMP Simple Network Management Protocol
SNS Shared Network Services
SOAP Simple Object Access Protocol
SOL Serial Over LAN
SON Self-Organizing Network
SPR Subscription Profile Repository
TMO21054 Issue 1
Page A:13
SR Service Router
SRNS Serving Radio Network Subsystem
SRS Sounding Reference Signal
SRV DNS Service Record
SRVCC Single Radio Voice Call Continuity
SSH Secure Shell
S-TMSI S-Temporary Mobile Subscriber Identity
SU Scheduling Unit
SU Software Update
SW Software
T
TA Tracking Area
TAC Tracking Area Code
TAI Tracking Area Identity
TAS Telephony Application Server
TAU Tracking Area Update
TB Transport Block
TCP Transmission Control Protocol
TDD Time Division Duplex
TEID Tunnel Endpoint Identifier
TFT Traffic Flow Template
TIPC Transparent Inter Process Communication
TM Transparent Mode
TMN Telecommunication Management Network
TMSI Temporary Mobile Station Identity
TNL Transport Network Layer
TRDU Transmit Receive Duplex Unit
TTI Transmission Time Interval
TX Transmit
U
UDP User Datagram Protocol

TMO21054 Issue 1
Page A:14
UE User Equipment
UL Uplink
ULBO Uplink Buffer Occupancy
ULR Update Locate Request
UM Un-acknowledge Mode
UMB Ultra Mobile Broadband
UMTS Universal Mobile Telecommunications System
UPA User plane Application
U-plane User plane
USIM Universal Subscriber Identity Module
UTC Coordinated Universal Time
UTRAN Universal Terrestrial Radio Access Network
V
VCC Voice Call Continuity
VLAN Virtual Local Area Network
VLR Visitor Location Register
VoIMS Voice over IMS
VoIP Voice over IP
V-PCRF Visited PCRF
V-PLMN Visited PLMN
VRB Virtual Resource Block
VRRP Virtual Router Redundancy Protocol
W
WAP Wireless Access Protocol
W-CDMA Wideband Code Division Multiple Access
WiMAX Worldwide Interoperability for Microwave Access
X
X2-C X2-Control plane
X2-U X2-User plane
xCCM-U Extended Core Controller Module Unit

TMO21054 Issue 1
Page A:15
xCEM-U Extended Channel Element Module Unit
XML Extensible Markup Language
XMS Extended Management System
Y
Z

TMO21054 Issue 1
Page A:16
Appendix B: LTE Interfaces
Key LTE Interfaces
NOTE: This document is not a complete listing of all available interfaces, and does not provide
extensive descriptions of each. The purpose of this appendix is to provide basic
information about some of the main interfaces used, that were mentioned in this
course.
For additional information on interfaces, refer to the 3GPP specifications.

TMO21054 Issue 1
Page B:1
Key LTE Interface Descriptions
Interface Description
Gx PCRF-PGW (PCEF)
Provides transfer of (QoS) policy and charging rules from the PCRF to Policy and
Charging Enforcement Function (PCEF) in the PGW.
The Gx interface enables the signaling of the PCC decision, which governs the PCC
behavior. The Gx interface is used for provisioning and removal of PCC rules from the
PCRF to the PGW and the transmission of traffic plane events from the PGW to the
PCRF.
The Gx interface is a Diameter application.
SWx HSS-AAA
The SWx reference point is defined between the AAA and the HSS. The SWx
reference point is used to authorize the UE and to transport PMIPv6 related mobility
parameters in the chained tunnel cases.
The SWx is used to authenticate and authorize the UE when the S2a, S2b or S2c
reference points are used to connect to EPC. This reference point is also used to
update the HSS with the PGW address information. Additionally, this reference point
may be used to retrieve and update other mobility related parameters including
static QoS profiles for non-3GPP accesses.
S1 It provides access to Evolved RAN radio resources for the transport of user plane and
control plane traffic.
S1-MME MME-eNodeB
The S1-MME is the reference point for the control plane protocol between eNodeB in
the eUTRAN and the MME.
S1-U SGW-eNodeB
The S1-U Interface is the user plane reference point between the eNodeB and SGW
for per-bearer user plane tunneling and inter-eNodeB path switching during
handover.
The S1-U uses the GTP-U to tunnel user data between the elements.

TMO21054 Issue 1
Page B:2
S5 SGW-PGW
Provides user plane tunneling and tunnel management between the SGW and the
PGW. S5 is used for SGW relocation due to UE mobility and if the SGW needs to
connect to a non-collocated PGW for the required PDN connectivity.
The S5/S8 interface provides control of bearer establishment, modification, and
release in the PGW. It also enables the PGW to request the activation, de-activation,
and modification of bearers to the SGW when there is a PCRF interface.
The S5/S8 control plane interface is based on GTPv2-C or PMIPv6.
S5/S8 user plane interface is based on GTPv1-U or PMIPv6.
S5a PGW-SGW
(GTP based; Non-Roaming)
Provides the user plane with related control and mobility
support between the MME and 3GPP anchor.
S5b PGW-SGW
(PMIPv6 based; Non-Roaming)
Provides the user plane with related control and mobility
support between 3GPP anchor and SAE anchor.

TMO21054 Issue 1
Page B:3
S6 AAA interface
Enables the transfer of subscription and authentication data for authenticating and
authorizing user access to the evolved system.
S6a MME-HSS
The S6a reference point is the interface between the MME and
the HSS. It enables the transfer of subscription and
authentication data for authenticating and authorizing user
access to the evolved system (AAA interface).
The HSS maintains roaming location information. The HSS
stores both the MME-identity and the SGSN-identity. If the UE
is reselecting an MME (target MME), the HSS sends a Cancel
Location to the source MME. In case the UE is changing the
SGSN (target SGSN, the HSS sends a Cancel Location to the
source SGSN. The HSS may also send a Cancel Location to the
source SGSN when a UE is changing from SGSN to MME.
Diameter is the protocol used for S6a.
S6b PGW-AAA
S6b is the reference point between PGW and AAA
server/proxy for mobility related authentication if needed.
This reference point may also be used to retrieve and request
the storage of mobility parameters. This reference point may
also be used to retrieve a static QoS profile for a UE for non-
3GPP access in case dynamic PCC is not supported.
Diameter is the protocol used for S6a.
S8 (future) S8 is the inter-PLMN reference point that provides the user and control plane
between the SGW in the VPLMN and the PGW in the HPLMN. S8 is the inter-PLMN
variant of S5. S8 is the roaming interface in case of roaming with home routed
traffic. It provides the user plane with related control between Gateways in the
VPLMN and HPLMN.
S8a PGW-SGW
(GTP based; Inter-Vendor Roaming)
S8b PGW -to- SGW

(PMIPv6 based)

TMO21054 Issue 1
Page B:4
S10 MME-MME
The S10 interface is the reference point between two MMEs. It provides the
capability to move the UE context from one MME to another in case of MME
relocation. The relocation of MME may be required during intra-eUTRAN mobility
procedures:
 Tracking Area Update (TAU) in IDLE mode with MME relocation. The new
Tracking Area where the UE is camping is now handled by an eNodeB that is
connected to a new MME.
 S1 handover with MME relocation. In CONNECTED mode the UE moves from one
source eNodeB to a target eNodeB and the target eNodeB is connected to
another MME.
S10 is a control plane interface and the protocol is GTPv2-C.
S11 MME-SGW
The S11 interface is the reference point between MME and SGW. It provides control
of bearer establishment, modification, release, and suspension in the SGW.
S11 is a control plane interface and the protocol is GTPv2-C.
S13 MME-EIR
It enables a UE identity check procedure between MME and EIR.
The S13 enables UE identity check procedure between MME and EIR. The Equipment
Identity Register (EIR) is the logical entity which is responsible for storing in the
network the International Mobile Equipment Identities (IMEIs), used in the
GERAN/UTRAN/eUTRAN system. The equipment is classified as "white listed", "grey
listed", "black listed" or it may be unknown (see TS 22.016 and TS 29.002). This
interface is used to verify the status of the equipment in the event of loss or thief.
When the EIR is integrated into the HSS, the S13 function is implemented on the S6a
interface, which uses the same protocol stack.
SGi PGW-PDN
The SGi interface is the reference point between the PGW and the packet data
network (PDN). PDN may be an operator external public, private PDN, or an intra-
operator PDN (for example, IMS services). Uplink user PDUs are plain IP packets with
a source IP address equal to the IP address assigned to the UE, and a destination IP
address equal to the IP address of the destination node inside the PDN. Uplink user
PDUs are forwarded or routed on the SGi interface to the next hop. Downlink user
PDU received on the SGi interface are plain IP packets with a source IP address equal
to the IP address of the destination node inside the PDN, and destination IP address
equal to IP address assigned to the UE.

TMO21054 Issue 1
Page B:5
X2 eNodeB-eNodeB
This interface is for eNodeB-to-eNodeB handover. During eNodeB handover to
another eNodeB, the downlink data is forwarded from the source eNodeB to the
target eNodeB over the X2 (direct forwarding). The X2 interface uses the GPRS
Tunneling Protocol for the control plane (GTP-C).
When the UE receives the handover command it will remove any EPS bearers for
which it did not receive and corresponding EPS radio bearers in the target cell. As
part of handover execution, downlink packets are forwarded from the source eNodeB
to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data
forwarded from the source eNodeB can be sent to it. Uplink data from the UE can be
delivered via the (source) SGW to the PGW.
The X2 user plane interface (X2-U) is defined between eNodeBs. The X2-U
interface provides non-guaranteed delivery of user plane PDUs.
The transport network layer is built on IP transport.
GTP-U is used on top of UDP/IP to carry the user plane PDUs.
The X2-UP interface protocol stack is identical to the S1-UP protocol stack.
The X2 control plane interface (X2-CP) is defined between two neighbor
eNodeBs.
The transport network layer is built on SCTP on top of IP. The application layer
signaling protocol is referred to as X2-AP (X2 Application Protocol).
The eNodeBs are not physically connected. eNodeBs connect through the IP/MPLS
backhaul Ethernet network.
Application
IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U
GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
LTE-Uu S1-U S5/S8 SGi
UE eNodeB Serving GW PDN GW
UE to PGW bearer plane

TMO21054 Issue 1
Page B:6
Eme
ergency and
a locatiion based
d servicess interfac
ces
Emergency and lo
ocation based
d services intterfaces
Interrface Descrriptions
Interfface Description
SLg The SLg

S interface supports com mmunication between the 9471 MME an
nd the Gatew
way
Mobille Location Center (GMLC)).
 Trransports possitioning requ
uests and resp
ponses for Loccation Service
es
(L
LCS) between GLMC and MME. M
SLg in
ncludes the following prottocols:
 Diiameter EPC LCS Protocol (ELP)
 SC
CTP over IPv4
4 or IPv6 for transport
t
The SLg
S interface supports com
mmunication between the 9471 MME an
nd the Gatew
way
Copyrightt © 2012 Alcatel--Lucent. All rights reserved.

TMO210
054 Issue 1
Pag
ge B:7
Mobille Location Center (GMLC)) to support transport
t positioning requests and
respo
onses for Locaation Servicess (LCS). The MME
M acts as client
c to the GMLC.
G The GMLC
suppo
orts verificatiion of identitty of a client and the clien
nt’s subscripttion data.
The GMLC
G forwardds a validated
d request to MME
M over the
e SLg interfacce to obtain UE
U
positioning data.
The EPC
E LCS defin nes procedure es and codingg of messagess between GM MLC and MME..
Semi-permanent SCTP
S associattions are set up
u between thet GMLC and d MME. The GMLC
G
blishes SCTP association
estab a w
with MME eitheer at GMLC innitialization time
t (MME alllows
conne
ections from a list of provvisioned GMLCC) or at the tiime GMLC sen nds a position
ning
reque
est to MME. Note
N that the SLg interface e is not allow
wed between a GMLC in on ne
netw
work to an MMME in a differeent network.
Diam
meter ELP
The EPC
E LCS Proto ocol (ELP) defines proceduures and codiing of messagges between
GMLCC and MME. The protocol is specified in n 3GPP TS 29..172 and proccedures are
speciified in 3GPP TS 23.271. The
T ELP is a ve endor-specifiic Diameter application.
a Itt
reuse
es the basic mechanisms
m d
defined by the
e Diameter ba ase protocol and it define
es
addittional commaands to support SLg specifiic proceduress.
SLs The SLs

S interface supports com mmunication between the 9471 MME an nd the EPC
Serving Mobile Loccation Centerr (E-SMLC ) to
o obtain a UE
E's position.
 Suppo
orts of Emerge
ency Location
n Services (LC
CS).
ncludes the fo
SLs in ollowing prottocols:
 LCS-A
AP
 SCTP over IPv4 or IPv6 for transsport
The SLs
S interface supports com mmunication between the 9471 MME an nd the EPC
Serving Mobile Loccation Centerr (E-SMLC ) to
o obtain a UE
E's position. The E-SMLC
acts with the
intera e UE in order to exchange location information applicable to UE--

TMO210
054 Issue 1
Pag
ge B:8
assistted and UE-baased position
n methods andd interacts with
w the eUTRAAN to exchannge
locattion informatiion applicable
e to network-assisted and network-bassed position
methhods. E-SMLC uses LTE Positioning Proto ocol (LPP and
d LPPa) to UE and eNodeB
respeectively for UE positioning
g.
Down
nlink Generic NAS Transpoort messages and
a Uplink Ge eneric NAS Trransport
messages are used
d to transportt transparentt LPP message
es between a UE and the E-
E
C.
SMLC
LCP-A
AP
The Location
L Servvices Applicattion Protocol (LCS-AP) is used between the MME andd
the E_SMLC.
E LCS-A AP messages are carried over
o SCTP/IP. The MME esttablishes sem
mi-
perm
manent connecctions with a set of E-SMLCs at the inittialization tim
me.
An MMME serving arrea may consiist of several E-SMLCs, whhich are assocciated with
track
king areas. E-SMLC selectio
on is based up pon the last seen
s Trackingg Area Identitty
(TAI).
SLh GMLC
C – HSS
The SLh
S interface is used by th
he GMLC to re equest routing information
n from the HSSS
(i.e. the address of
o the H-GMLC, and/or the e address of the
t visited MSSC/MSC serveer,
SGSN, 3GPP AAA server
s or MME
E for a particu
ular target UE
E whose location has been
n
requeested).
M1 M1 is the referencce point betw

ween the MBM MS GW and the e eUTRAN/UTTRAN for MBM
MS
data delivery. IP Multicast is used
u on this interface to fo
orward data.
Broad
dcast is over the M1 interfface to the MBMS
M gatewayy.
M3 The M3
M interface supports com mmunication between
b the 9471 MME and the Multica
ast
Contrrol Entity (MC
CE) located in
n the eNodeBs.
 MME transsmits session control messsages toward the appropriate eNodeBs in
the broadcast service area
a using the M3 interfacce.
ncludes the fo
M3 in ollowing proto
ocols:
 M3-AP

TMO210
054 Issue 1
Pag
ge B:9
 SCTP overr IPv4 or IPv6 for transportt
The M3
M interface is the referen
nce point bettween the Mu
ulticast Control Entity (MCE)
in the
e eNodeB nod
des and the 9471
9 MME.
Multimedia Broadccast/Multicasst Service (MB BMS) is a broa
adcast servicee in which da
ata
ansmitted from
is tra m a single source entity to
o multiple recipients. Thee MME providees a
distriibution of con
ntrol message es associated with Broadcaast Session
Start/Update/Stop using the Sm (GTPv2) interface to th he MBMS Gate eway and the M3
(SCTPP) interface to
t the Multica ast Control En
ntity (MCE) th
hat is located
d in the eNodeeBs.
The MME
M determin nes which eNodeB nodes area in the MBM MS Broadcastt Service Areaa
and transmits
t sesssion control messages
m tow
ward the appropriate nodes using the M3M
interfface
M3-A
AP
The M3-AP
M messagges between an MCE and the
t 9471 MME E are transporrted over
SCTP/IP. The M3 Application
A Protocol (M3-A
AP) supports the
t signaling control
functtions such as session mana
agement, reseet, and error indication.
The MCE
M initializees the M3 SCTTP association
n with the MMME. The MME sends
s MBMS
M3APP messages to
o only those MCE
M that have e initialized an
a M3 SCTP asssociation.

TMO210
054 Issue 1
Page B:10
TMO21054 Issue 1
Page B:11
UMTS-LTE Interworking Interfaces
UMTS and LTE Interworking diagram identifying some of the interfaces
Interface Descriptions
Gn MME-SGSN
The Gn interface is for the control plane between the MME and the SGSN. Gn allows
the MME to implement handover between LTE and UMTS/GERAN.
Gn/Gp PGW-SGSN
Interface between the PGW and Gn/Gp SGSN (2G-SGSN or 3G-SGSN). GTP (GTP-C and
GTP-U) is defined for the Gn interface (that is, the interface between GSNs within a
PLMN, and for the Gp interface between GSNs in different PLMNs.
S3 SGSN-MME
It enables user and bearer information exchange for inter 3GPP access network
mobility in idle and/or active state.
It enables user and bearer information exchange for inter 3GPP access network
mobility in idle and/or active state. It is based on Gn reference point as defined
between SGSNs.
The S3 is based on GTP protocol.

TMO21054 Issue 1
Page B:12
S4 SGSN-SGW
It provides related control and mobility support between GPRS Core and the 3GPP
Anchor function of SGW. In addition, if Direct Tunnel is not established, it provides
the user plane tunneling. S4 is based on the Gn reference point as defined between
SGSN and GGSN.
The S4 is based on GTP protocol.
S12 SGSN (UTRAN)-SGW

Reference point between UTRAN and SGW for user plane tunneling when Direct
Tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U
protocol as defined between SGSN and UTRAN or respectively between SGSN and
GGSN. Usage of S12 is an operator configuration option.

TMO21054 Issue 1
Page B:13
CDMA-LTE Interworking Interfaces
CDMA and LTE Interworking diagram identifying some of the interfaces
Interface Descriptions
A10/A11 HSGW-eHRPD eRNC
A12 HSS/AAA-eHRPD eRNC
Gxa HSGW-PCRF
It provides transfer of (QoS) policy information from PCRF to the Trusted Non-3GPP
accesses.
SGs MME-3G-MSC/VLR
Interface between the MME and the Visitor Location Register (VLR) to allow location
management coordination and to relay certain messages related to GSM/UMTS circuit
switched services over the EPS.
S2a HSGW-PGW
S2a provides the user plane with related control and mobility support between
trusted non 3GPP IP access and the gateway.
S2b It provides the user plane with related control and mobility support between EPC and
the SAE Anchor.

TMO21054 Issue 1
Page B:14
S101 This interface is the signaling interface between the EPC MME and the evolved HRPD Access
Network (eAN/PCF).
MME -to- eHRPD eRNC
Future (beyond LE3.0)
S102 This interface is the bearer interface between the MME and the 3G1X MSC.
S103 SGW-HSGW
This interface is the bearer interface between the EPC SGW and the HSGW
STa HSGW-AAA

TMO21054 Issue 1
Page B:15
Additional LTE Network Interface Descriptions
Cx ISC-HSS
DNS/Mr
Gxb This interface is not specified within this release of the specification.
Rf/Ro 5420 CTS-8615 IeCCF
Rx PCRF-ISC
The Rx reference point resides between the AF and the PCRF in the TS 23.203 [6].
S7 It provides transfer of (QoS) policy and charging rules from PCRF to Policy and
Charging Enforcement Point (PCEP).
S9 It provides transfer of (QoS) policy and charging control information between the
Home PCRF and the Visited PCRF in order to support local breakout function.
It provides transfer of (QoS) policy and charging control information between the
Home PCRF and the Visited PCRF in order to support local breakout function. In all
other roaming scenarios, S9 has functionality to provide dynamic QoS control policies
from the HPLMN.
SBc Reference point between CBC and MME for warning message delivery and control
functions.
Sp PCRF-HSS
Sh HSS-CTS
PCRF-HSS
Sv Release date TBD
Ta* It connects the Trusted non-3GPP IP Access with the 3GPP AAA Server/Proxy and
transports access authentication, authorization, mobility parameters and charging-
related information in a secure manner.
Wd* It connects the 3GPP AAA Proxy, possibly via intermediate networks, to the 3GPP
AAA Server.
Wx* This reference point is located between 3GPP AAA Server and HSS and is used for
transport of authentication data.

TMO21054 Issue 1
Page B:16
Appendix C: LTE Glossary
Numbers ............................................................................................ 10
3GPP (3rd Generation Partnership Project) .......................................................... 10
3GPP2 (3rd Generation Partnership Project 2) ...................................................... 10
4G ........................................................................................................... 10
5400 Platform ............................................................................................. 10
A ..................................................................................................... 11
AAA ......................................................................................................... 11
Access Network ........................................................................................... 11
Access Manager ........................................................................................... 11
Access Point Name (APN) ............................................................................... 11
Access Stratum (AS) ...................................................................................... 11
Advanced Telecom Computing Architecture (ATCA)................................................ 11
Access Terminal .......................................................................................... 11
AF ........................................................................................................... 11
Aggregate Maximum Bit Rate (AMBR) ................................................................. 11
AF ........................................................................................................... 11
A-Interface ................................................................................................ 11
AKA ......................................................................................................... 11
AMBR ....................................................................................................... 11
AM .......................................................................................................... 12
AMC ......................................................................................................... 12
AN ........................................................................................................... 12
Application Function (AF) ............................................................................... 12
APN ......................................................................................................... 12
AS ........................................................................................................... 12
AT ........................................................................................................... 12
ATCA........................................................................................................ 12
ATCA-LCP .................................................................................................. 12
ATCA Mezzanine Card (AMC)............................................................................ 12
Attribute Value Pair (AVP) .............................................................................. 12
Authentication and Key Agreement (AKA)............................................................ 12
Authentication Authorization and Accounting (AAA) ............................................... 12
Authorized QoS ........................................................................................... 12
AVP ......................................................................................................... 12
B ..................................................................................................... 14
Base Band Unit ............................................................................................ 14
Base Transceiver Station (BTS) ......................................................................... 14
BBU ......................................................................................................... 14
BCCH ....................................................................................................... 14
BE ........................................................................................................... 14
Best Effort (BE) ........................................................................................... 14
BHCA ....................................................................................................... 14
Binding ..................................................................................................... 14
Broadcast Control Channel (BCCH) .................................................................... 14
BS (BTS) .................................................................................................... 14

TMO21054 Issue 1
Page C:1
BTS (BS) .................................................................................................... 14
Busy Hour Connection Attempts (BHCA) .............................................................. 14
C ..................................................................................................... 15
CAC ......................................................................................................... 15
CALEA ...................................................................................................... 15
Call Admission Control (CAC) ........................................................................... 15
Capabilities Exchange Request (CER) ................................................................. 15
CC ........................................................................................................... 15
CCM ......................................................................................................... 15
CDF ......................................................................................................... 15
CDMA ....................................................................................................... 15
CDR ......................................................................................................... 15
Cell site reselection...................................................................................... 15
Central Processing Unit (CPU) .......................................................................... 15
CER ......................................................................................................... 15
CGF ......................................................................................................... 15
Charging Control.......................................................................................... 15
Charging Data Function (CDF) .......................................................................... 16
Charging Data Record (CDR) ............................................................................ 16
Charging Gateway Function (CGF) ..................................................................... 16
Charging key .............................................................................................. 16
Charging Rules Function (CRF) ......................................................................... 16
Client Mobile IP (CMIP) .................................................................................. 16
CMIP ........................................................................................................ 16
Code Division Multiple Access (CDMA) ................................................................ 16
Common Chassis Management (CCM).................................................................. 16
Communications Assistance for Law Enforcement Act ............................................. 16
Content of Communication ............................................................................. 16
Connection ................................................................................................ 16
Core ........................................................................................................ 17
CPU ......................................................................................................... 17
CRF ......................................................................................................... 17
CS (Circuit Switched domain) .......................................................................... 17
D ..................................................................................................... 18
Deadstart .................................................................................................. 18
Deep Packet Inspection (DPI)........................................................................... 18
Default Bearer ............................................................................................ 18
Dedicated Bearer ......................................................................................... 18
Differentiated Services Code Point (DSCP) ........................................................... 18
Diskfull Host ............................................................................................... 18
Diskless Host .............................................................................................. 18
DL ........................................................................................................... 18
DNS ......................................................................................................... 18
DO .......................................................................................................... 18
Domain Name Server (DNS) ............................................................................. 18
Downlink (DL) ............................................................................................. 18
DPI .......................................................................................................... 18
DSCP ........................................................................................................ 19
E...................................................................................................... 20
TMO21054 Issue 1
Page C:2
eCCM-U..................................................................................................... 20
Extended Core Controller Module Unit (eCCM-U) ................................................... 20
eCEM-U ..................................................................................................... 20
Extended Channel Element Module Unit (eCEM-U_ ................................................. 20
ECM ......................................................................................................... 20
ECM-CONNECTED ......................................................................................... 20
ECM-IDLE ................................................................................................... 20
EDGE (Enhanced Data rates for GSM Evolution) ..................................................... 20
eHRPD ...................................................................................................... 20
EIR .......................................................................................................... 20
Element Management System (EMS)................................................................... 20
EMM ......................................................................................................... 20
EMM-DEREGISTERED ...................................................................................... 20
EMM-REGISTERED ......................................................................................... 20
EMS ......................................................................................................... 21
eNodeB (sometimes written as eNB) .................................................................. 21
EPC ......................................................................................................... 21
EPS .......................................................................................................... 21
EPS Connection Management (ECM) ................................................................... 21
EPS Mobility Management (EMM) ....................................................................... 21
Equipment Identity Register (EIR) ..................................................................... 21
eUTRAN .................................................................................................... 21
Evolved High Rate Packet Data (eHRPD) ............................................................. 21
Evolved NodeB (eNodeB) ................................................................................ 21
Evolved Packet Core (EPC).............................................................................. 21
Evolved Packet System (EPS) ........................................................................... 21
Evolved Universal Terrestrial Radio Access Network (eUTRAN)................................... 21
Extended Markup Language (XML) ..................................................................... 21
F...................................................................................................... 23
FA ........................................................................................................... 23
Factory Installation ...................................................................................... 23
Fault, Configuration, Accounting, Performance, and Security Management (FCAPS) ......... 23
FBC ......................................................................................................... 23
FCAPS ...................................................................................................... 23
FFS .......................................................................................................... 23
Field Installation ......................................................................................... 23
Field Replacement/Update (FRU) ..................................................................... 23
Flow Based Charging (FBC) ............................................................................. 23
FQDN ....................................................................................................... 23
Foreign Agent (FA) ....................................................................................... 23
For Future Study (FFS)................................................................................... 23
Fully Qualified Domain Name (FQDN) ................................................................. 23
G ..................................................................................................... 25
Gating Control ............................................................................................ 25
Gateway GPRS Support Node (GGSN) ................................................................. 25
Gateway Mobile Switching Center (GMSC) ........................................................... 25
GBR Bearer ................................................................................................ 25
General Packet Radio Service (GPRS) ................................................................. 25
Generic Routing Encapsulation (GRE) ................................................................. 25

TMO21054 Issue 1
Page C:3
GERAN ...................................................................................................... 25
GGSN ....................................................................................................... 25
Globally Unique Temporary Identity (GUTI) ......................................................... 25
GMSC ....................................................................................................... 25
GPRS EDGE Radio Access Network (GERAN) .......................................................... 25
GSM ......................................................................................................... 25
Global System for Mobile communications (GSM) ................................................... 26
GPRS ........................................................................................................ 26
GPRS Tunneling Protocol (GTP) ........................................................................ 26
GRE ......................................................................................................... 26
GTP ......................................................................................................... 26
GUTI ........................................................................................................ 26
H ..................................................................................................... 27
HA........................................................................................................... 27
Handover .................................................................................................. 27
Handover Interface ...................................................................................... 27
High Speed Downlink Packet Access (HSDPA) ........................................................ 27
High Speed Packet Access (HSPA) ..................................................................... 27
High Speed Packet Processor (HSPP) .................................................................. 27
High Speed Uplink Packet Access (HSUPA) ........................................................... 27
HLR ......................................................................................................... 27
Home Agent (HA) ......................................................................................... 27
Home Location Register (HLR) ......................................................................... 27
Home PLMN (H-PLMN) ................................................................................... 27
Home Subscriber Server (HSS) .......................................................................... 27
H-PLMN ..................................................................................................... 28
HRPD Serving Gateway (HSGW) ........................................................................ 28
HSGW ....................................................................................................... 28
HSPD ........................................................................................................ 28
HSDPA ...................................................................................................... 28
HSPA ........................................................................................................ 28
HSPP ........................................................................................................ 28
HSS.......................................................................................................... 28
HSUPA ...................................................................................................... 28
Hub ......................................................................................................... 28
I ...................................................................................................... 29
IEEE ......................................................................................................... 29
IETF ......................................................................................................... 29
IMEI ......................................................................................................... 29
IMS .......................................................................................................... 29
IMSI ......................................................................................................... 29
IMS Subscriber Identity Module (SIM) .................................................................. 29
IMT-2000 ................................................................................................... 29
Institute of Electrical and Electronics Engineers (IEEE) ............................................ 29
Interception ............................................................................................... 29
Interception Configuration Information .............................................................. 29
Intercept Related Information ......................................................................... 29
International Mobile Subscriber Identity (IMSI) ...................................................... 29
International Mobile Telecommunications 2000 (IMT-2000) ....................................... 29

TMO21054 Issue 1
Page C:4
International Telecommunications Union (ITU) ..................................................... 29
Internet Engineering Task Force (IETF) ............................................................... 29
Inter-Radio Access Technology (I-RAT) ............................................................... 30
Inter-RAT .................................................................................................. 30
IP ............................................................................................................ 30
IP-CAN session ............................................................................................ 30
IPM .......................................................................................................... 30
IP Manager (IPM) .......................................................................................... 30
IP Multimedia Subsystem (IMS) ......................................................................... 30
IPSec........................................................................................................ 30
IRI ........................................................................................................... 30
ISIM ......................................................................................................... 30
ITU .......................................................................................................... 30
IuCS Interface ............................................................................................. 30
J ...................................................................................................... 31
Jumpstart .................................................................................................. 31
Jumpstart Server ......................................................................................... 31
K ..................................................................................................... 32
L ...................................................................................................... 33
LA ........................................................................................................... 33
Label Switched Path (LSP) .............................................................................. 33
Label Switch Router (LSR) .............................................................................. 33
LAF.......................................................................................................... 33
Law Enforcement Agency (LEA) ........................................................................ 33
Law Enforcement Monitoring Facility (LEMF) ........................................................ 33
Lawful Authorization (LA) ............................................................................... 33
LBI .......................................................................................................... 33
LBO ......................................................................................................... 33
LCP ......................................................................................................... 33
LDAC ........................................................................................................ 33
LEA.......................................................................................................... 33
LEMF ........................................................................................................ 33
LI ............................................................................................................ 33
LIF .......................................................................................................... 33
LMA ......................................................................................................... 34
Load Distribution and Access Control (LDAC) ........................................................ 34
Long Term Evolution (LTE).............................................................................. 34
Load Distribution and Access Control (LDAC) ........................................................ 34
LSP .......................................................................................................... 34
LSR .......................................................................................................... 34
LTE.......................................................................................................... 34
LTE Voice Interworking Function (LVI) ................................................................ 34
LVI Application Function (LAF) ......................................................................... 34
LVI .......................................................................................................... 34
M ..................................................................................................... 35
Managed Object (MO) .................................................................................... 35
Management Information Base (MIB) .................................................................. 35
MBMS ....................................................................................................... 35

TMO21054 Issue 1
Page C:5
MCC ......................................................................................................... 35
Media Gateway Control Function (MGCF) ............................................................ 35
Media Gateway (MGW) .................................................................................. 35
MEI .......................................................................................................... 35
MGCF ....................................................................................................... 35
MGW ........................................................................................................ 35
MIB .......................................................................................................... 35
MIF .......................................................................................................... 35
MIMO........................................................................................................ 35
MIP .......................................................................................................... 35
MLS ......................................................................................................... 35
MME ......................................................................................................... 35
MME Application Function (MAF) ....................................................................... 35
MMEC ....................................................................................................... 36
MME Interface Function (MIF) .......................................................................... 36
MMD ........................................................................................................ 36
MNC ......................................................................................................... 36
MO .......................................................................................................... 36
Mobile Internet Protocol (MIP) ......................................................................... 36
Mobile Network Code (MNC) ............................................................................ 36
Mobile Switching Center (MSC) ......................................................................... 36
Mobile Terminal (MT) .................................................................................... 36
Mobility Management Entity ............................................................................ 36
MPLS ........................................................................................................ 36
MSC ......................................................................................................... 36
MT .......................................................................................................... 37
MTU ......................................................................................................... 37
MultiCore .................................................................................................. 37
Multiple Input Multiple Output (MIMO) ............................................................... 37
Multimedia Domain (MMD) .............................................................................. 37
Multimedia Broadcast and Multicast Service ......................................................... 37
Multi-Protocol Label Switch (MPLS) ................................................................... 37
Multithreading ............................................................................................ 37
N ..................................................................................................... 38
NAS ......................................................................................................... 38
Network Time Protocol (NTP) .......................................................................... 38
Next Generation Network (NGN) ....................................................................... 38
NGN ......................................................................................................... 38
NTP ......................................................................................................... 38
Non-GBR bearer .......................................................................................... 38
Non Access Stratum (NAS) .............................................................................. 38
NodeB ...................................................................................................... 38
O ..................................................................................................... 39
OA&M (OAM) .............................................................................................. 39
OCS ......................................................................................................... 39
OFCS ........................................................................................................ 39
OFDM ....................................................................................................... 39
OFDMA ..................................................................................................... 39
OOS ......................................................................................................... 39

TMO21054 Issue 1
Page C:6
Operations, Administration, and Maintenance (OA&M) ............................................ 39
Orthogonal Frequency Division Multiplexing (OFDM) ............................................... 39
Orthogonal Frequency Division Multiple Access (OFDMA) .......................................... 39
P...................................................................................................... 40
Packet Data Convergence Protocol (PDCP)........................................................... 40
Packet Data Network (PDN) ............................................................................ 40
Packet Data Network Gateway (PGW) ................................................................ 40
Packet Data Protocol Context (PDP Context) ........................................................ 40
Packet Switched domain ................................................................................ 40
Paging ...................................................................................................... 40
PCC ......................................................................................................... 40
PCC Rule ................................................................................................... 40
PCEF ........................................................................................................ 40
PCMD ....................................................................................................... 40
PCRF ........................................................................................................ 40
PDCP ........................................................................................................ 40
PDN ......................................................................................................... 40
PDN GW (PGW)............................................................................................ 40
PDSN ........................................................................................................ 40
PDSN ........................................................................................................ 41
PEF.......................................................................................................... 41
Per Call (or Connection) Measurement Data (PCMD) ............................................... 41
PGW ........................................................................................................ 41
PLMN ....................................................................................................... 41
PMIP ........................................................................................................ 41
PoC (Push-to-talk over Cellular) ....................................................................... 41
Point to Point Protocol (PPP) ........................................................................... 41
Policy and Charging Enforcement Function (PCEF) ................................................. 41
Policy and Charging Rules Function (PCRF) .......................................................... 41
Policy Control ............................................................................................. 41
Policy Control and Charging (PCC) Decision.......................................................... 41
Policy Decision Function (PDF) ......................................................................... 41
Procedure.................................................................................................. 41
Proxy Mobile IP (PMIP or Proxy MIP) ................................................................... 41
PPP ......................................................................................................... 42
PSTN (Public Switched Telephone Network) ......................................................... 42
Public Land Mobile Network (PLMN)................................................................... 42
Q ..................................................................................................... 43
QCI .......................................................................................................... 43
QoS ......................................................................................................... 43
QoS Class Identifier (QCI) ............................................................................... 43
QoS rules................................................................................................... 43
Quality of Service (QoS) ................................................................................. 43
R ..................................................................................................... 44
Radio Access Network (RAN) ........................................................................... 44
Radio Access Network Application Protocol.......................................................... 44
Radio Network Control (RNC) .......................................................................... 44
RAN ......................................................................................................... 44

TMO21054 Issue 1
Page C:7
RANAP ...................................................................................................... 44
Rear Transmission Module (RTM) ...................................................................... 44
RNC ......................................................................................................... 44
Rx ........................................................................................................... 44
S ...................................................................................................... 45
SAE.......................................................................................................... 45
SCTP ........................................................................................................ 45
SDF.......................................................................................................... 45
SDM ......................................................................................................... 45
Service Data Flow (SDF) ................................................................................. 45
Service Data Flow Filter ................................................................................. 45
Service Data Flow Template ............................................................................ 45
Session Initiation Protocol (SIP) ........................................................................ 45
Session Management (SM) ............................................................................... 45
Serving Gateway (SGW) ................................................................................. 45
SGi .......................................................................................................... 45
SGSN ........................................................................................................ 45
SGSN (Serving GPRS Support Node) .................................................................... 45
SGW ........................................................................................................ 45
ShMC ........................................................................................................ 45
SIM .......................................................................................................... 46
Short Message Service (SMS) ............................................................................ 46
Shelf Management card (ShMC) ........................................................................ 46
ShMC ........................................................................................................ 46
SIP .......................................................................................................... 46
SM ........................................................................................................... 46
SMS ......................................................................................................... 46
Software Update (or Upgrade) ......................................................................... 46
Software Patching ........................................................................................ 46
Software Update (or Upgrade) ......................................................................... 46
Software Patching ........................................................................................ 46
SPR.......................................................................................................... 46
S-TMSI ...................................................................................................... 46
S-Temporary Mobile Subscriber Identity (S-TMSI) ................................................... 46
Stream Control Transmission Protocol (SCTP) ....................................................... 47
Subscriber Identity Module (SIM)....................................................................... 47
Subscription Profile Repository ........................................................................ 47
Sv ........................................................................................................... 47
System Architecture Evolution (SAE) .................................................................. 47
T ..................................................................................................... 48
TA ........................................................................................................... 48
TAC ......................................................................................................... 48
TAI .......................................................................................................... 48
Target Identity............................................................................................ 48
TAS ......................................................................................................... 48
TAU ......................................................................................................... 48
TCP ......................................................................................................... 48
TDMA ....................................................................................................... 48
TDD ......................................................................................................... 48

TMO21054 Issue 1
Page C:8
TE ........................................................................................................... 48
TEID ........................................................................................................ 48
Telecommunication and Internet converged Services and Protocols for Advanced Networking
(TISPAN) ................................................................................................... 48
Terminal Equipment ..................................................................................... 48
Thread ..................................................................................................... 48
Time Division Duplex .................................................................................... 48
Time Division Multiple Access (TDMA) ................................................................ 49
TISPAN ..................................................................................................... 49
TNL ......................................................................................................... 49
Tracking Area (TA) ....................................................................................... 49
Tracking Area Identity (TAI) ............................................................................ 49
Tracking Area Update (TAU) ............................................................................ 49
Transmission Control Protocol (TCP) .................................................................. 49
Transport Network Layer (TNL) ........................................................................ 49
Tunnel Endpoint Identifier (TEI) ....................................................................... 49
U ..................................................................................................... 50
UDP ......................................................................................................... 50
UE ........................................................................................................... 50
UE Connection ............................................................................................ 50
UE Session ................................................................................................. 50
UE Subscription ........................................................................................... 50
UL ........................................................................................................... 50
Ultra Mobile Broadband (UMB) ......................................................................... 50
UMB ......................................................................................................... 50
UMTS ....................................................................................................... 50
Universal Mobile Telecommunications System (UMTS) ............................................. 50
Universal Terrestrial Radio Access Network (UTRAN) .............................................. 50
Uplink (UL) ................................................................................................ 51
User Datagram Protocol (UDP) ......................................................................... 51
User Equipment (UE)..................................................................................... 51
USIM ........................................................................................................ 51
UTRAN ...................................................................................................... 51
V ..................................................................................................... 52
VCC ......................................................................................................... 52
Visited Location Register (VLR) ........................................................................ 52
Visited PCRF (V-PCRF) ................................................................................... 52
Visited PLMN (V-PLMN) .................................................................................. 52
VLR ......................................................................................................... 52
Voice Call Continuity (VCC) ............................................................................. 52
Voice over IP, Voice over Internet Protocol (VoIP) ................................................. 52
VoIP ......................................................................................................... 52
W ..................................................................................................... 53
W-CDMA (WCDMA) ........................................................................................ 53
WiMAX ...................................................................................................... 53
Worldwide Interoperability Microwave Access (WiMAX) ........................................... 53
Wide band Code Division Multiple Access (WCDMA) ................................................ 53
X ..................................................................................................... 53

TMO21054 Issue 1
Page C:9
XML ......................................................................................................... 53
Y ..................................................................................................... 53
Z ...................................................................................................... 53
Numbers
3GPP (3rd Generation Partnership Project)
The 3rd Generation Partnership Project (3GPP) is a collaboration between groups of
telecommunications associations, to make a globally applicable third generation (3G)
mobile phone system specification within the scope of the International Mobile
Telecommunications-2000 project of the International Telecommunication Union (ITU).
3GPP specifications are based on evolved Global System for Mobile Communications (GSM)
specifications. 3GPP standardization encompasses Radio, Core Network and Service
architecture. 3GPP is a cross-country organization initially in charge of the definition of
the 3G UMTS standard.
3GPP2 (3rd Generation Partnership Project 2)
3GPP2 is a cross-country organization in charge of the definition of the 3G cdma2000
standard and its evolutions.
4G
See Fourth Generation
5400 Platform
An Alcatel-Lucent platform that provides multiple sets of middleware to support differing
applications, and which makes use of the Common Chassis Management (CCM) software to
provide common base software for multiple applications.

TMO21054 Issue 1
Page C:10
A
AAA
See Authentication Authorization and Accounting
Access Network
Network that connects access technologies (such as a Radio Access Network) to the core
network.
Access Manager
A network element that controls the operation of a wireless system and is responsible for
mobility management, call processing, system maintenance, technician interfaces, and
system integrity.
Access Point Name (APN)
Identifies an external network that is accessible from a terminal. An APN has several
attributes associated with it that define how a terminal can access the external network
at that point. An APN defines service in a mobile network. An APN provides routing
information for Serving GPRS Support Nodes (SGSNs) and Gateway GPRS Support Nodes
(GGSNs).
Access Stratum (AS)
The AS is the set of features associated to the radio interface and Access Network.
Advanced Telecom Computing Architecture (ATCA)
An Alcatel-Lucent developed 19-inch rack mounted chassis, supporting open slots, plus
one dedicated slot for the ShMC cards (two in one slot), also featuring a dual-star fabric
backplane and front access fan trays/filters. The blades that populate the ATCA chassis
are also part of the ATCA program.
Access Terminal
Originally, the data terminal used for sending packet data calls over the air interface.
Now, the term also includes equipment for sending and receiving voice calls, and has
come to have the same meaning as Mobile Unit or User Equipment (UE).
AF
See Application Function
Aggregate Maximum Bit Rate (AMBR)
The maximum bit rate that limits the aggregate bit rate of a set of non-GBR EPS Bearers
of a UE belonging to the same PDN connection.
AF
See Application Function
A-Interface
Interface between the LVI-C and the 2G MSC, based on IP/TCP/M3UA/SCCP/BSSAP
AKA
See Authentication and Key Agreement
AMBR
See Aggregate Maximum Bit Rate

TMO21054 Issue 1
Page C:11
AM
See Access Manager
AMC
See ATCA Mezzanine Card
AN
See Access Network
Application Function (AF)
AF is the generic name for the network element that supports applications that require
dynamic policy and/or charging control. For 3GPP IP access types, P-CSCF supports the AF.
APN
See Access Point Name (APN)
AS
See Access Stratum
AT
See Access Terminal
ATCA
See Advanced Telecom Computing Architecture
ATCA-LCP
The term “ATCA-LCP” shall be used to describe the hardware and software deliveries that
comprise the hardware/software platform supporting the MME.
ATCA Mezzanine Card (AMC)
An auxiliary card that can be configured (at the factory). There are multiple types of AMC
cards, such as hard drive disk AMCs, packet processor AMCs, host AMCs, etc.
Attribute Value Pair (AVP)
The Diameter protocol consists of a header followed by one or more Attribute-Value-Pairs
(AVPs). An AVP includes a header and is used to encapsulate protocol-specific data (e.g.,
routing information) as well as authentication, authorization or accounting information.
Authentication and Key Agreement (AKA)
A security protocol used in 3G networks.
Authentication Authorization and Accounting (AAA)
Entities that provide Internet Protocol (IP) functionality to support the functions of
authentication, authorization, and accounting. The AAA server in the CDMA wireless data
network architecture is similar to the HLR in the CDMA wireless voice network
architecture.
Authorized QoS
The maximum QoS that is authorized for a service data flow. In case of an aggregation of
multiple service data flows within one IP-CAN bearer (e.g. for GPRS a PDP context), the
combination of the "Authorized QoS" information of the individual service data flows is the
"Authorized QoS" for the IP-CAN bearer. It contains the QoS class identifier and the data
rate.
AVP
TMO21054 Issue 1
Page C:12
See Attribute Value Pair

TMO21054 Issue 1
Page C:13
B
Base Band Unit
Component of a distributed base station configuration with separate radios. The 9926 BBU
can be used with both remote radio heads (RRH) for distributed deployments and
Transmit/Receive/duplexer Units (TRDUs) for more “classic” BTS deployments.
Base Transceiver Station (BTS)
Contains the equipment for transmitting and receiving of radio signals (transceivers)
antennas, and equipment for encrypting and decrypting communications with the base
station controller (BSC).
BBU
See Base Band Unit
BCCH
See Broadcast Control Channel
BE
See Best Effort
Best Effort (BE)
Describes a network service in which the network does not provide any guarantees that
data is delivered or that a user is given a guaranteed quality of service (QoS) level or a
certain priority. All users obtain best effort service, meaning that they obtain unspecified
variable bit rate and delivery time, depending on the current traffic load.
BHCA
See Busy Hour Connection Attempts
Binding
The association between a service data flow and the IP-CAN bearer (for GPRS the PDP
context) transporting that service data flow.
Broadcast Control Channel (BCCH)
A unidirectional control channel used in a base station to broadcast the data peculiar to
the cell or to neighboring cells to mobile stations.
BS (BTS)
See Base Transceiver Station
BTS (BS)
See Base Transceiver Station
Busy Hour Connection Attempts (BHCA)
The quantity of connection attempts made within an hour, usually under heavy load.

TMO21054 Issue 1
Page C:14
C
CAC
See Call Admission Control
CALEA
See Communications Assistance for Law Enforcement Act
Call Admission Control (CAC)
Prevents oversubscription of VoIP networks. It is used in the call set-up phase and applies
to real-time media traffic as opposed to data traffic.
Capabilities Exchange Request (CER)
The communication between two diameter peers starts the establishment of a transport
connection (TCP or SCTP). The initiator then sends a capabilities-Exchange-Request (CER)
to the other peer, which responds with a Capabilities-Exchange-Answer (CEA). After that,
TLS may be negotiated. (not shown in diagram)
CC
See Content of Communication
CCM
See Common Chassis Management
CDF
See Charging Data Function
CDMA
See Code Division Multiple Access
CDR
See Charging Data Record
Cell site reselection
Cell site reselection is the process that is used to identify which radio transmission sites
(cells) and channels are available for access after a connection has been lost, becomes
unavailable for use, or its quality diminishes. The RRC (radio resource control) performs
cell site reselection by continuously monitoring neighboring cells. The purpose is to
identify the cell that provides the best quality connection.
Central Processing Unit (CPU)
An electronic circuit that can execute computer programs, which are actually a set of
instructions.
CER
See Capabilities Exchange Request
CGF
See Charging Gateway Function
Charging Control
The process of associating packets, belonging to a service data flow, to a charging key and
applying online charging and/or offline charging, as appropriate.

TMO21054 Issue 1
Page C:15
Charging Data Function (CDF)
The CDF controls the building of the CDR whose content and format is specified by 3GPP
standard documents.
Charging Data Record (CDR)
A CDR is a collection of information (connection time, allocated resources.) used in billing
and accounting.
Charging Gateway Function (CGF)
The CGF is a gateway between the Core Network nodes and the Billing Domain. It supports
CDR storage and management (opening, closing).
Charging key
Information used by the online and offline charging system for rating purposes.
Charging Rules Function (CRF)
The CRF is a PS Core Network element introduced in UMTS for IMS flow-based charging.
Client Mobile IP (CMIP)
The mobile device supports a MIP stack and interacts with Mobility Agents in the home and
foreign network.
CMIP
See Client Mobile IP
Code Division Multiple Access (CDMA)
CDMA is a medium-access method in which different users are allocated different code
sequences.
Common Chassis Management (CCM)
A platform organization initiative to identify and implement a common set of platform
related software for system/chassis installation, configuration, and IP management.
Communications Assistance for Law Enforcement Act
A United States wiretapping law passed in 1994 (Pub. L. No. 103-414, 108 Stat. 4279,
codified at 47 USC 1001-1010). In its own words, the purpose of CALEA is:
To amend title 18, United States Code, to make clear a telecommunications carrier's duty
to cooperate in the interception of communications for Law Enforcement purposes, and
for other purposes.
CALEA's purpose is to enhance the ability of law enforcement and intelligence agencies to
conduct electronic surveillance by requiring that telecommunications carriers and
manufacturers of telecommunications equipment modify and design their equipment,
facilities, and services to ensure that they have built-in surveillance capabilities, allowing
federal agencies to monitor all telephone, broadband internet, and VoIP traffic in real-
time.
Content of Communication
Information exchanged between two or more users of a telecommunications service,
excluding intercept related information. This includes information which may, as part of
some telecommunications service, be stored by one user for subsequent retrieval by
another.
Connection
TMO21054 Issue 1
Page C:16
A communications path to send and receive data (voice, data, text) from a near end UE to
a far end UE. For LTE, a connection can be one of the types of voice, data, or text, using
bearer paths set up via SGWs or PGWs.
Core
A single core on a multi-core blade/host.
CPU
See Central Processing Unit
CRF
See Charging Rules Function
CS (Circuit Switched domain)
The CS domain is the subset of the 2G/GSM and 3G/UMTS Core Network domain dedicated
to the support of packet-based services. CSCF (Call Session Control Function). The CSCF is
a SIP-based server in the IMS architecture for establishing, terminating or modifying IMS
sessions.

TMO21054 Issue 1
Page C:17
D
Deadstart
Refers to the capability (procedures and scripts) of bringing up an entire system, including
both the Factory Installation (base configuration plus base software) and the Field
Installation (final configuration and application software). Deadstart is typically only
supported at field sites as a result of a catastrophic system failure.
Deep Packet Inspection (DPI)
The act of any IP network equipment which is not an endpoint of a communication using
any field other than the layer 3 destination IP address for any purpose. This is performed
as the packet passes an inspection point, searching for protocol non-compliance, viruses,
spam, intrusions or predefined criteria to decide what actions to take on the packet,
including collecting statistical information. This is in contrast to shallow packet inspection
(usually called Stateful Packet Inspection) which just checks the header portion of a
packet.
Default Bearer
An EPS bearer that is established when the UE connects to a PDN, and that remains
established throughout the lifetime of the PDN connection to provide the UE with always-
on IP connectivity to that PDN.
Dedicated Bearer
An EPS bearer that is the additional EPS bearer that is established to a PDN for which a
default bearer has already been established for the same UE.
Differentiated Services Code Point (DSCP)
A field in the header of IP packets for packet classification purposes.
Diskfull Host
Host (typically a blade) with a processor and one or more disk drives.
Diskless Host
Host (typically a blade) with one or more processors.
DL
See Downlink
DNS
See Domain Name Server
DO
See CDMA Data Only
Domain Name Server (DNS)
A human-recognizable identifier to a system-internal, often numeric, identification or
addressing component that is used to translate a hostname or a domain name to its
corresponding binary identifier, or vice versa.
Downlink (DL)
The communication link from the base station to the mobile.
DPI

TMO21054 Issue 1
Page C:18
See Deep Packet Inspection
DSCP
See Differentiated Services Code Point

TMO21054 Issue 1
Page C:19
E
eCCM-U
See Extended Core Controller Module Unit
Extended Core Controller Module Unit (eCCM-U)
The eCCM-U is a controller in charge of a part of call processing, OA&M management,
internal/external data flow switching/combining, external/internal alarm connectivity,
and an external synchronization reference interface. The eCCM-U also contains CPRI
interfaces to the RRHs.
eCEM-U
See Extended Channel Element Module
Extended Channel Element Module Unit (eCEM-U_
The 9926 BBU is factory-equipped with one eCEM-U (base package) and can house up to
three eCEMs-U, depending on the configuration requirements. eCEM-U modules are in
charge of part of call processing and baseband transmit/receive digital signal processing.
Up to 6 CPRI links
ECM
See EPS Connection Management
ECM-CONNECTED
For a UE in the ECM-CONNECTED state, there exists a signaling connection between the UE
and the MME. The signaling connection is made up of two parts: an RRC connection and an
S1_MME connection.
ECM-IDLE
A UE is in ECM-IDLE state when no NAS signaling connection between UE and network
exists. In ECM-IDLE state, a UE performs cell selection/reselection.
EDGE (Enhanced Data rates for GSM Evolution)
EDGE is a high bit rate evolution of 2G/GSM networks.
eHRPD
See Evolved High Rate Packet Data
EIR
See Equipment Identity Register
Element Management System (EMS)
User interface located on the 9256 OMP that provides both graphical and command-line
interfaces for management of selected network elements.
EMM
See EPS Mobility Management
EMM-DEREGISTERED
In the EMM-DEREGISTERED state, the EMM context in MME holds no valid location or
routing information for the UE. The UE is not reachable by a MME, as the UE location is
not known.
EMM-REGISTERED
TMO21054 Issue 1
Page C:20
The UE enters the EMM-REGISTERED state by a successful registration procedure which is
either an Attach procedure or a Tracking Area Update procedure. In the EMMREGISTERED
state, the UE can receive services that require registration in the EPS. The UE location is
known in the MME to at least an accuracy of the tracking area list allocated to that UE
(excluding some abnormal cases).
EMS
See Element Management System
eNodeB (sometimes written as eNB)
See Evolved NodeB
EPC
See Evolved Packet Core
EPS
See Evolved Packet System
EPS Connection Management (ECM)
The EPS Connection Management (ECM) states describe the signaling connectivity between
the UE and the EPC.
EPS Mobility Management (EMM)
EMM refers to the set of signaling procedures between the terminal and the MME used for
user attachment and location management. The EPS Mobility Management (EMM) states
describe the Mobility Management states that result from the mobility management
procedures e.g. Attach and Tracking Area Update procedures.
Equipment Identity Register (EIR)
The EIR is a database that contains information about the identity of the mobile
equipment that prevents calls from stolen, unauthorized,or defective mobile stations.
eUTRAN
See Evolved Universal Terrestrial Radio Access Network
Evolved High Rate Packet Data (eHRPD)
Commonly known as 1xEV-DO, eHRPD is a high-speed CDMA-based wireless data
technology developed by Qualcomm. IS-856 is the official international standard
designation)
Evolved NodeB (eNodeB)
eNodeB is the radio transmission and receiver node of eUTRAN Access Network.
Evolved Packet Core (EPC)
The successor to the 3GPP Release 7 packet-switched core network, developed by 3GPP
within the framework of Release 8.
Evolved Packet System (EPS)
The evolved packet system (EPS) or evolved 3GPP packet-switched domain consists of the
evolved packet core network and the evolved universal terrestrial radio access network.
Evolved Universal Terrestrial Radio Access Network (eUTRAN)
eUTRAN is the Access Network evolution for 3GPP 3G standards.
Extended Markup Language (XML)

TMO21054 Issue 1
Page C:21
XML (Extensible Markup Language) is a way of marking up structured documents, that is,
documents in which the markup primarily indicates the content's purpose rather than its
formatting. Like HTML, it uses tags (for example <para>) and attributes (for example
<image file="face.jpg"/>) but there are some very important differences.

TMO21054 Issue 1
Page C:22
F
FA
See Foreign Agent
Factory Installation
The capability (procedures and scripts0 for base configuration and the loading of base
software (typically OS) onto a system (chassis and associated blades) at the factory, prior
to being shipped to a site for installation.
Fault, Configuration, Accounting, Performance, and Security Management
(FCAPS)
The ISO Telecommunications Management Network model and framework for network
management. FCAPS is an acronym for Fault, Configuration, Accounting, Performance,
Security which are the management categories into which the ISO model defines network
management tasks. In non-billing organizations Accounting is sometimes replaced with
Administration.
FBC
See Flow Based Charging
FCAPS
See Fault, Configuration, Accounting, Performance, and Security Management
FFS
See For Future Study
Field Installation
The capability (procedures and scripts) for configuring and loading application software
(typically middleware and application software) onto a system (chassis and associated
blades), typically at a field site following hardware installation. Field installation brings
up a system to a point of being operational and ready for application level provisioning
and processing.
Field Replacement/Update (FRU)
The capability (procedures or scripts) for replacing a defective blade in a shelf, typically
based on the perception of there being a persistent hardware fault on the blade.
Flow Based Charging (FBC)
Usage-based pricing scheme.
FQDN
See Fully Qualified Domain Name
Foreign Agent (FA)
A router that stores information about mobile nodes visiting its network.
For Future Study (FFS)
A term that is typically used in standards to indicate that specific topic is currently being
investigated.
Fully Qualified Domain Name (FQDN)

TMO21054 Issue 1
Page C:23
Domain name that specifies its exact location in the tree hierarchy of the Domain Name
System (DNS). It specifies all domain levels, including the top-level domain, relative to
the root domain. A fully qualified domain name is distinguished by its unambiguity; it can
only be interpreted one way.

TMO21054 Issue 1
Page C:24
G
Gating Control
The process of blocking or allowing packets, belonging to a service data flow, to pass
through to the desired endpoint.
Gateway GPRS Support Node (GGSN)
The GGSN is a 2G/GSM and 3G/UMTS Core Network entity supporting packet data
transmission to and from mobile terminals.
Gateway Mobile Switching Center (GMSC)
The MSC is a specific type of MSC, used as a gateway with the PSTN.
GBR Bearer
An EPS bearer that uses dedicated network resources related to a Guaranteed Bit Rate
(GBR) value, which are permanently allocated at EPS bearer establishment/modification.
General Packet Radio Service (GPRS)
GPRS is an evolution of 2G GSM networks for packet data service support.
Generic Routing Encapsulation (GRE)
A tunneling protocol that can encapsulate a wide variety of network layer protocol packet
types inside IP tunnels, creating a virtual point-to-point link to routers at remote points
over an IP internetwork.
GERAN
See GPRS EDGE Radio Access Network
GGSN
See Gateway GPRS Support Node
Globally Unique Temporary Identity (GUTI)
The MME allocates a GUTI) to the UE. The GUTI has two main components:
(1) One part that uniquely identifies the MME which allocated the GUTI. This part is known
as the Globally Unique MME Identifier (GUMMEI) that is constructed from MCC (Mobile
Country Code), MNC (Mobile network Code) and MME Identifier (MMEI).In turn the MMEI is
constructed from an MME Group ID (MMEGI) and an MME Code (MMEC).
(2) Another part called the M-TMSI that uniquely identifies the UE within the MME that
allocated the GUTI.
The GUTI is used to support subscriber identity confidentiality, and, in the shortened S-
TMSI form, to enable more efficient radio signaling procedures (e.g. paging and Service
Request).
GMSC
See Gateway Mobile Switching Center
GPRS EDGE Radio Access Network (GERAN)
GERAN is the 3GPP name for the GSM access network. It refers to the initial 2G/GSM voice
system, as well as GPRS and EDGE evolutions.
GSM

TMO21054 Issue 1
Page C:25
See Global System for Mobile Telecommunications
Global System for Mobile communications (GSM)
GSM is a well-known 2G cellular telephony system.
GPRS
See General Packet Radio Service
GPRS Tunneling Protocol (GTP)
GTP is an IP-based protocol used in EPC for establishing data sessions. It also provides data
encapsulation between network nodes. GTP was inherited from the 2G/GPRS standard,
and is used within GSM and UMTS networks. It can be used with UDP or TCP. GTP-C is used
within the GPRS core network for signaling between GPRS Support Nodes (GGSNs and
SGSNs). This allows the SGSN to activate a session on the users behalf (PDP context
activation), to deactivate the same session, to adjust quality of service parameters or to
update a session for a subscriber who has just arrived from another SGSN. GTP-U is used
for carrying user data within the GPRS core network and between the Radio Access
Network and the core network. The user data transported can be packets in any of IPv4,
IPv6 or PPP formats.
GRE
See Generic Routing Encapsulation
GTP
See GPRS Tunneling Protocol
GUTI
See Globally Unique Temporary Identity

TMO21054 Issue 1
Page C:26
H
HA
See Home Agent
Handover
During an active communication between an end device and the network, the end device
is able to transfer its network connectivity from one network to another network, without
major degradation of active communication (for example, packet loss, reorder, delay). A
handover is sometimes referred to as a “handoff.”
Handover Interface
Physical and logical interface across which the interception measures are requested from
network operator / access provider / service provider, and the results of interception are
delivered from a network operator / access provider / service provider to a law
enforcement monitoring facility.
High Speed Downlink Packet Access (HSDPA)
HSDPA is a high-speed enhancement of 3G/UMTS networks for network-to-terminal
transmission.
High Speed Packet Access (HSPA)
HSPA designates the combination of HSDPA and HSUPA.
High Speed Packet Processor (HSPP)
An AMC that can be configured on any ATCA asset that supports AMCs.
High Speed Uplink Packet Access (HSUPA)
HSUPA is a high-speed enhancement of 3G/UMTS networks for terminal-to-network
transmission.
HLR
See Home Location Register
Home Agent (HA)
Database that stores the subscriber’s personal information and tells where the
subscriber’s calls usually originate from. The Home Agent is required for Mobile IP.
Packets to a user’s terminal access device are sent to the HA server that stores the user’s
foreign network location.
Home Location Register (HLR)
A central database that contains details of each mobile phone subscriber.
Home PLMN (H-PLMN)
The PLMN to which the customer belongs. A PLMN (public land mobile network) is a
network that is established and operated by an administration or by a recognized
operating agency for the specific purpose of providing land mobile telecommunications
services to the public.
Home Subscriber Server (HSS)
The HSS is the master database of 3G networks containing the user subscription-related
information.

TMO21054 Issue 1
Page C:27
H-PLMN
See Home PLMN
HRPD Serving Gateway (HSGW)
A new network element introduced in the 3GPP2 Standards to support seamless mobility
between LTE and Evolved HRPD (eHRPD) networks.
HSGW
See HRPD Serving Gateway
HSPD
See High Speed Packet Data HSS
HSDPA
See High Speed Downlink Packet Access
HSPA
See High Speed Packet Access
HSPP
See High Speed Packet Processor
HSS
See Home Subscriber Server
HSUPA
See High Speed Uplink Packet Access
Hub
ATCA terminology for the Ethernet switch card.

TMO21054 Issue 1
Page C:28
I
IEEE
See Institute of Electrical and Electronics Engineers
IETF
See Internet Engineering Task Force
IMEI
See International Mobile Equipment Identifier
IMS
See IP Multimedia Subsystem
IMSI
See International Mobile Subscriber Identity
IMS Subscriber Identity Module (SIM)
See SIM.
IMT-2000
See International Mobile Telecommunications 2000 (IMT-2000)
Institute of Electrical and Electronics Engineers (IEEE)
IEEE is a professional association for the advancement of technology. IEEE covers a wide
range of technical areas, including wireless telecommunications.
Interception
Action (based on the law), performed by a network operator / access provider / service
provider, of making available certain information and providing that information to a law
enforcement monitoring facility.
Interception Configuration Information
Information related to the configuration of interception.
Intercept Related Information
Collection of information or data associated with telecommunication services involving
the target identity, specifically communication associated information or data (e.g.
unsuccessful communication attempts), service associated information or data and
location information.
International Mobile Subscriber Identity (IMSI)
The IMSI is a private unique mobile subscriber identifier used in 3GPP networks including
GSM, UMTS and EPS technologies.
International Mobile Telecommunications 2000 (IMT-2000)
IMT-2000 is the ITU name for post-2G network evolutions. 3GPP/UMTS and
3GPP2/cdma2000 are part of the IMT-2000 standard family.
International Telecommunications Union (ITU)
ITU is an international organization controlling global telecom networks and services
coordination.
Internet Engineering Task Force (IETF)
TMO21054 Issue 1
Page C:29
IETF is an international community dedicated to the evolution of Internet and Internet
standards.
Inter-Radio Access Technology (I-RAT)
Inter-Radio Access Technology (or Inter-RAT) refers to the technology to support mobility
between different radio access network types.
Inter-RAT
See Inter-Radio Access Technology
IP
See Internet Protocol
IP-CAN session
The association between a UE represented by an IPv4 and/or an IPv6 address, and UE
identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-
CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers
per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as UE IP addresses
are established and announced to the IP network.
IPM
See IP Manager
IP Manager (IPM)
A Common Chassis Management (CCM) software that provide IP communications software
for IP transport between processors, including layer 2 and 3 protocols, such as TCP, UDP,
and SCTP.
IP Multimedia Subsystem (IMS)
IMS is a 3GPP framework, designed for delivering IP multimedia services to end-users.
IPSec
See Internet Protocol Security
IRI
See Intercept Related Information
ISIM
See IMS Subscriber Identity Module
ITU
See International Telecommunication Union
IuCS Interface
Interface between the LVI-C and the UMTS/3G-MSC based on IP/SCTP/M3UA/SCCP/RANAP

TMO21054 Issue 1
Page C:30
J
Jumpstart
The capability (procedures and scripts) for loading the base OS software onto a diskfull
blade. For example, the Factory Installation procedure makes use of Jumpstart
procedures to put the OS and base configuration onto all diskfull blades in a chassis,
before being shipped to the field site. Jumpstart is also very occasionally used during a
Software Upgrade, where significant changes have occurred to the OS software.
Jumpstart Server
A server which provides the base OS images, binaries, and libraries to be loaded onto
diskfull blades during a jumpstart procedure. In the factory, the “jumpstart server” is a
separate box which is interfaced to the LCP, and which is used to jumpstart each of the
diskfull blades in a chassis. At a field site, if the MI or OAM server has the correct OS
version installed, it can be used as a jumpstart server to jumpstart the other diskfull
blades in a system.

TMO21054 Issue 1
Page C:31
K

TMO21054 Issue 1
Page C:32
L
LA
See Lawful Authorization
Label Switched Path (LSP)
A specific path through MPLS LSRs.
Label Switch Router (LSR)
Sometimes called transit router), is a type of a router located in the middle of a
Multiprotocol Label Switching (MPLS) network. It is responsible for switching the labels
used to route packets.
LAF
See LVI Application Function
Law Enforcement Agency (LEA)
Organization authorized by a lawful authorization based on a national law to request
interception measures and to receive the results of telecommunications interceptions.
Law Enforcement Monitoring Facility (LEMF)
Law enforcement facility designated as the transmission destination for the results of
interception relating to a particular interception subject.
Lawful Authorization (LA)
Permission granted to a LEA under certain conditions to intercept specified
telecommunications and requiring co-operation from a network operator/access
provider/service provider. Typically this refers to a warrant or order issued by a lawfully
authorized body.
LBI
See Linked EPS Bearer Identity
LBO
See Local Break Out
LCP
See Lucent Control Platform
LDAC
See Load Distribution and Access Control (LDAC)
LEA
See Law Enforcement Agency
LEMF
See Law Enforcement Monitoring Function
LI
See Lawful Interception
LIF
The “LVI Interface Function” is a service on the LVI-C that provides the interface function
for the LVI-C.

TMO21054 Issue 1
Page C:33
LMA
See Local Mobility Anchor
Load Distribution and Access Control (LDAC)
A software functionality that provides message distribution to multiple application targets
based on key resource indicators on those targets (for example, processor utilization,
memory utilization, database tuple utilization, etc).
Long Term Evolution (LTE)
The next major step in mobile radio communications. LTE will be introduced in 3rd
Generation Partnership Project Release 8. The primary goal of LTE is to improve the
Universal Mobile Telecommunications System (UMTS) mobile 1 phone standard and 2
provide an enhanced user experience and simplified technology for next generation
mobile 3 broadband.
Load Distribution and Access Control (LDAC)
“Load Distribution and Access Control” is software functionality that provides message
distribution to multiple application targets based on key resource indicators on those
targets (for example, processor utilization, memory utilization, database tuple utilization,
etc).
LSP
See Label Switched Path
LSR
See Label Switch Router
LTE
“Long Term Evolution” is the next major step in mobile radio communications, and will be
introduced in 3rd Generation Partnership Project Release 8. The primary goal of LTE is to
improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard
and provide an enhanced user experience and simplified technology for next generation
mobile broadband.
LTE Voice Interworking Function (LVI)
Alcatel-Lucent product that interworks between the Evolved Packet System (EPS) network
and voice over packet services user equipment to existing circuit switched MSC to allow
the service provider to offer voice over packet service on high speed packet data
networks The LVI is broken into two major components – 1) the controller, known as the
LVI-C (LVI Controller), which interworks signaling and control and – 2) the bearer
interworking function, known as the LVI –B (LVI Bearer Gateway) or MGW, in 7510 Media
Gateway.
LVI Application Function (LAF)
A service on the LVI-C C that provides the interface function for the LVI-C.
LVI
See LTE Voice Interworking Function

TMO21054 Issue 1
Page C:34
M
Managed Object (MO)
In telecommunications management, a resource within the telecommunications
environment that may be controlled through the use of operation, administration,
maintenance, and provisioning application protocols.
Management Information Base (MIB)
A type of database used to manage the devices in a communications network. It comprises
a collection of objects in a (virtual) database used to manage entities (such as routers and
switches) in a network.
MBMS
See Multimedia Broadcast and Multicast Service
MCC
See Mobile Country Code
Media Gateway Control Function (MGCF)
The MGCF is an IMS node controlling the signaling interworking with PSTN for voice circuit-
switched services.
Media Gateway (MGW)
The MGW is responsible for media conversion to and from the PSTN, under the control of
the MGCF.
MEI
See Mobile Equipment Identifier
MGCF
See Media Gateway Control Function
MGW
See Media Gateway
MIB
See Management Information Base
MIF
See MME Interface Function
MIMO
See Multiple Input Multiple Output
MIP
See Mobile Internet Protocol
MLS
See Multi-Layer Switch
MME
See Mobility Management Entity
MME Application Function (MAF)

TMO21054 Issue 1
Page C:35
A board type on the MME that provides the mobility management and bearer/session
management functionality on the MME. There are one or more pairs of MAFs per MME (in
M1.0 and beyond), depending on system capacity. The MAFs service 3GPP procedure, such
as attaches, detaches, session setups, etc, that provide the primary MME functionality.
MAFs make use of user data, as retrieved from the S6a interface that describes the user,
their end equipment, and their provisioned services/features.
MMEC
See MME Code
MME Interface Function (MIF)
A board type on the MME that provides the ingress/egress for all signaling traffic on the
MME. The MIF terminates multiple IP interface types, including S1, S6a, S10, S11, and S101
interfaces, from other LTE network elements. There is one pair of MIFs per MME (in M1.0
and beyond).
MMD
See Multimedia Domain
MNC
See Mobile Network Code
MO
See Managed Object
Mobile Internet Protocol (MIP)
An Internet Engineering Task Force (IETF) standard communications protocol that is
designed to allow mobile device users to move from one network to another while
maintaining their permanent IP address. Mobile IP is an enhancement of the Internet
Protocol (IP) that adds mechanisms for forwarding Internet traffic to mobile devices
(known as mobile nodes) when they are connecting through other than their home
network.
Mobile Network Code (MNC)
The MNC is part of the IMSI and uniquely identifies the home operator of the subscriber in
a country.
Mobile Switching Center (MSC)
The MSC belongs to the Circuit Core Network and is responsible for circuit-switched call
control.
Mobile Terminal (MT)
MT is the part of the terminal that supports the radio-related protocols and components,
as well as the UICC module.
Mobility Management Entity
MME is an entity part of the EPC network which controls session and user-mobility
management.
MPLS
See Multi-Protocol Label Switch
MSC
See Mobile Switching Center

TMO21054 Issue 1
Page C:36
MT
See Mobile Terminal
MTU
See Maximum Transmission Unit
MultiCore
A multicore host possesses multiple processor cores accessing shared memory.
Multiple Input Multiple Output (MIMO)
The use of multiple antennas at both the transmitter and receiver to improve
communication performance. It is one of several forms of smart antenna technology.
Multimedia Domain (MMD)
MMD is the cdma2000 equivalent of the IMS subsystem of UMTS networks.
Multimedia Broadcast and Multicast Service
MBMS is a broadcast/multicast service defined by the 3GPP.
Multi-Protocol Label Switch (MPLS)
A mechanism in high-performance telecommunications networks which directs and carries
data from one network node to the next. MPLS makes it easy to create "virtual links"
between distant nodes. It can encapsulate packets of various network protocols.
Multithreading
On a single processor, Multithreading generally occurs by time-division multiplexing ("time
slicing") in very much the same way as the parallel execution of multiple tasks (computer
multitasking): the processor switches between different threads. On a multiprocessor or
multi-core system, threading can be achieved via multiprocessing, wherein different
threads and processes can run literally simultaneously on different processors or cores.

TMO21054 Issue 1
Page C:37
N
NAS
See Non-Access Stratum
Network Time Protocol (NTP)
NTP is a protocol for synchronizing the clocks of computer systems over packet-switched,
variable-latency data networks. NTP uses UDP as its transport layer.
Next Generation Network (NGN)
NGN refers to the new packet-based converged network architecture.
NGN
See Next Generation Network
NTP
See Network Time Protocol
Non-GBR bearer
An EPS bearer that uses network resources that are not related to a Guaranteed Bit Rate
(GBR) value.
Non Access Stratum (NAS)
The NAS is the set of access-independent network features related to the management
subscriber data and communication contexts. In EPC network, the NAS signaling
terminates in the MME.
NodeB
NodeB is the radio transmission and receiver node of the 3G/UTRAN access network.

TMO21054 Issue 1
Page C:38
O
OA&M (OAM)
See Operations, Administration, and Maintenance
OCS
See Online Charging System
OFCS
See Offline Charging System
OFDM
See Orthogonal Frequency Division Multiplexing
OFDMA
See Orthogonal Frequency Division Multiple Access (OFDMA)
OOS
See Out of Service
Operations, Administration, and Maintenance (OA&M)
General term used to describe the processes, activities, tools, standards, etc involved
with operating, administering, managing, and maintaining any system.
Orthogonal Frequency Division Multiplexing (OFDM)
OFDM is the radio technology family chosen for the eUTRAN physical layer. It is based on
the mapping of a wide-band signal for transmission onto large numbers of narrow-band
modulated subcarriers.
Orthogonal Frequency Division Multiple Access (OFDMA)
OFDMA is a multi-user multiplexing technique based on OFDM subcarrier arrangement.

TMO21054 Issue 1
Page C:39
P
Packet Data Convergence Protocol (PDCP)
PDCP is the radio interface protocol layer that controls the header compression and
security protection.
Packet Data Network (PDN)
A network based on a Packet Transport technology.
Packet Data Network Gateway (PGW)
The Packet Data Network Gateway is part of the EPC. It is the functional network entity
that terminates the SGi interface towards the PDN.
Packet Data Protocol Context (PDP Context)
PDP is the name for the 2G/GPRS or 3G/UMTS packet session context that is set up
between the terminal and the Packet Core Network. In EPS networks, EPS bearer is
equivalent to the PDP context.
Packet Switched domain
The PS domain is the subset of the 2G/GSM and 3G/UMTS Core Network domain dedicated
to the support of packet-based services.
Paging
Paging is the act of seeking user equipment via radio transmissions. It is typically the
procedure by which the fixed infrastructure of a mobile network attempts to reach a
mobile station within its location area, before any other network-initiated procedure can
take place.
PCC
See Policy and Charging Control / Policy Control and Charging
PCC Rule
A set of information enabling the detection of a service data flow and providing
parameters for policy control and/or charging control.
PCEF
See Policy and Charging Enforcement Function
PCMD
See Per Call (or Connection) Measurement Data
PCRF
See Policy Charging Rules Function
PDCP
See Packet Data Convergence Protocol
PDN
A Packet Data Network is a network based on a Packet Transport technology.
PDN GW (PGW)
See Packet Data Network Gateway (H=Home or V=Visited)
PDSN
TMO21054 Issue 1
Page C:40
See Packet Data Serving Node
PDSN
See Packet Data Serving Node
PEF
See Policy Enforcement Function
Per Call (or Connection) Measurement Data (PCMD)
Detailed data collected on the major events associated with the processing of each
connection within a session, processed by the MME. This data is typically collected via
count mechanisms in the session/connection management software and forwarded to
static store on the network node, and then ultimately forwarded to a northbound
interface which collects, stores, and analyzes the PCMD data.
PGW
See Packet Data Network Gateway (H=Home or V=Visited)
PLMN
See Public Land Mobile Network (H=Home or V=Visited)
PMIP
See Proxy Mobile IP
PoC (Push-to-talk over Cellular)
PoC is a walkie-talkie-like speech service defined by the OMA.
Point to Point Protocol (PPP)
A data link protocol commonly used to establish a direct connection between two
networking nodes. It can provide connection authentication, transmission encryption
privacy, and compression.
Policy and Charging Enforcement Function (PCEF)
PCEF is the generic name for the functional entity which supports service data flow
detection, policy enforcement and flow-based charging. For 3GPP IP access types, the
GGSN supports the PCEF.
Policy and Charging Rules Function (PCRF)
The PCRF is a concatenation of PDF and CRF network nodes.
Policy Control
The process whereby the PCRF indicates to the PCEF how to control the IP-CAN bearer.
Policy control includes QoS control and/or gating control.
Policy Control and Charging (PCC) Decision
A decision consists of PCC rules and IP-CAN bearer attributes, which is provided by the
PCRF to the PCEF for policy and charging control.
Policy Decision Function (PDF)
The PDF is a PS Core Network element introduced in UMTS for IMS flow policy control.
Procedure
A fixed, step-by-step sequence of activities or course of action (with definite start and end
points) that must be followed in the same order to correctly perform a task.
Proxy Mobile IP (PMIP or Proxy MIP)
TMO21054 Issue 1
Page C:41
A new standard currently being worked on at Internet Engineering Task Force (IETF).
Sometimes referred to as Network-based mobility management, it provides similar
functionality to that of Mobile IP, however it does not require any modifications to the
mobile host's network stack, i.e. the mobility is taken care of by the network.
PPP
See Point to Point Protocol
PSTN (Public Switched Telephone Network)
PSTN is the public worldwide circuit switched-based telephone network.
Public Land Mobile Network (PLMN)
A PLMN is a public mobile network owned by an operator. It is uniquely identified by a
concatenation of MNC and MCC codes.

TMO21054 Issue 1
Page C:42
Q
QCI
See QoS Class Identifier
QoS
See Quality of Service
QoS Class Identifier (QCI)
An identifier representing QoS parameters, excluding the bitrates, of the IP-CAN. A
network may be configured to provide corresponding QoS, given the same QoS class
identifier value, in multiple IP-CAN types.
QoS rules
A set of information enabling the detection of a service data flow and for performing
bearer binding and uplink bearer binding verification. The QoS rules contain QoS
parameters.
Quality of Service (QoS)
A set of quality requirements on the collective behavior of one or more objects.

TMO21054 Issue 1
Page C:43
R
Radio Access Network (RAN)
Part of a mobile Telecommunication system. It implements a radio access technology.
Conceptually, it sits between the Mobile phone and the core network.
Radio Access Network Application Protocol
Protocol that encapsulates and carries higher-layer signaling, handles signaling between
the SGSN and UTRAN (Iu interface), and manages the GTP connections on the Iu
interface.
Radio Network Control (RNC)
The RNC belongs to the UTRAN and controls radio protocols and the UTRAN Base Stations.
RAN
See Radio Access Network
RANAP
See Radio Access Network Application Protocol
Rear Transmission Module (RTM)
A hardware component that may be used to provide additional card/blade external
connectivity.
RNC
See Radio Network Controller
Rx
Interface between the PCRF and the LVI-C, based on IP/SCTP/Diameter protocol stack.

TMO21054 Issue 1
Page C:44
S
SAE
See System Architecture Evolution
SCTP
See Stream Control Transmission Protocol
SDF
See Service Data Flow
SDM
See Subscriber DB Manager
Service Data Flow (SDF)
An aggregate set of packet flows that matches a service data flow template.
Service Data Flow Filter
A set of IP header parameter values/ranges used to identify one or more of the packet
flows constituting a service data flow. A service data flow filter of a PCC rule that is
predefined in the PCEF may use parameters that extend the packet inspection beyond the
IP 5 tuple.
Service Data Flow Template
The set of service data flow filters in a PCC rule, required for defining a service data flow.
Session Initiation Protocol (SIP)
SIP is an application-layer control protocol developed by the IETF that is used for
establishing IP-based multimedia services such as Voice over IP.
Session Management (SM)
SM refers to the set of signaling procedures between the terminal and the MME that is
used for bearer management.
Serving Gateway (SGW)
The Serving GW is part of the EPC. It is the functional network entity that terminates the
interface towards eUTRAN.
SGi
3GPP standard interface between LVI-C and LVI-B. Based on H.248 protocol.
SGSN
See Serving GPRS Support Node
SGSN (Serving GPRS Support Node)
The SGSN is a 2G/GSM and 3G/ UMTS Core Network entity supporting packet data
transmission to and from mobile terminals.
SGW
See Serving Gateway
ShMC
See Shelf Management Card

TMO21054 Issue 1
Page C:45
SIM
See Subscriber Identity Module
Short Message Service (SMS)
SMS is the well-known text-message service introduced in 2G/GSM networks.
Shelf Management card (ShMC)
The ATCA card with primary function of shelf hardware management based on open
standard HPI. One pair of ShMC cards is required per shelf, occupying a single slot.
ShMC
The ATCA Shelf Management card with primary function of shelf hardware management
based on open standard HPI. One pair of ShMC cards is required per shelf, occupying a
single slot.
SIP
See Session Initiation Protocol
SM
See Session Management
SMS
See Short Message Service
Software Update (or Upgrade)
The term used to describe the procedures, scripts, and software to upgrade all software
on an in-service ATCA-LCP. The term “in-service” is used to denote that there is minimal
outage associated with the upgrade.
Software Patching
The term used to describe the procedures, scripts, and software to upgrade a subset of
software components on an in-service ATCA-LCP. The term “in-service” is used to denote
that the patch is to be applied with minimal outage.
Software Update (or Upgrade)
The term used to describe the procedures, scripts, and software to upgrade all software
on an in-service ATCA-LCP. The term “in-service” is used to denote that there is minimal
outage associated with the upgrade.
Software Patching
The term used to describe the procedures, scripts, and software to upgrade a subset of
software components on an in-service ATCALCP. The term “in-service” is used to denote
that the patch is to be applied with minimal outage.
SPR
See Subscription Profile Repository
S-TMSI
See S-Temporary Mobile Subscriber Identity
S-Temporary Mobile Subscriber Identity (S-TMSI)
This temporary identity of the mobile subscriber is used for paging the mobile. The S-TMSI
is constructed from the MMEC and the M-TMSI and is a shortened version of the GUTI
(please see GUTI in this section for further details). S-TMSI = MMEC + M-TMSI.

TMO21054 Issue 1
Page C:46
Stream Control Transmission Protocol (SCTP)
A Transport Layer protocol, serving in a similar role as the popular protocols TCP and UDP.
It provides some of the same service features of both, ensuring reliable, in-sequence
transport of messages with congestion control. Whereas TCP is stream oriented, i.e.,
transports byte streams, SCTP is transaction-oriented, meaning it transports data in one or
more messages. A message is a group of bytes sent in one transaction (transmit
operation). Although TCP correctly reorders data that arrives out of order, it is concerned
only with bytes. It does not honor message boundaries, i.e., the structure of data in terms
of their original transmission units at the sender. SCTP, in contrast, conserves message
boundaries by operating on whole messages in a fashion similar to the User Datagram
Protocol (UDP). This means that a group of bytes that is sent in one transmission operation
(transaction) is read exactly as that group, called message, at the receiver.
Subscriber Identity Module (SIM)
Like the USIM (for UMTS) and ISIM (for IMS), the 2G/SIM is an application of the UICC card
within the user terminal. It supports user-related information such as identity, security
credentials, phonebook, and application-specific information.
Subscription Profile Repository
A logical entity that contains subscriber/subscription related information needed for
subscription-based policies.
Sv
3GPP standard interface between an MME and an LVI-C.
System Architecture Evolution (SAE)
A 3GPP work item which helps define 3G Packet Core network evolution (also known as
EPC).

TMO21054 Issue 1
Page C:47
T
TA
See Tracking Area
TAC
See Tracking Area Code
TAI
See Tracking Area Identity
Target Identity
A technical identity that uniquely identifies a target of interception. One target may have
one or several identities.
TAS
See Telephony Application Server
TAU
See Tracking Area Update
TCP
See Transmission Control Protocol
TDMA
See Time Division Multiple Access
TDD
See Time Division Duplex
TE
See Terminal Equipment
TEID
See Tunnel Endpoint Identifier
Telecommunication and Internet converged Services and Protocols for
Advanced Networking (TISPAN)
ETSI technical body controlling next-generation converged network definition.
Terminal Equipment
TE is the part of the terminal that supports user applications and application level
protocols, as well as user interface.
Thread
A thread is short for a thread of execution. Threads are a way for a program to split itself
into two or more simultaneously (or pseudo-simultaneously) running tasks. Threads and
processes differ from one operating system to another but, in general, a thread is
contained inside a process and different threads in the same process share some resources
while different processes do not.
Time Division Duplex
TDD is a duplex transmission method based on time separation.

TMO21054 Issue 1
Page C:48
Time Division Multiple Access (TDMA)
TDMA is a medium-access method in which different users are allocated different time
periods.
TISPAN
See Telecommunication and Internet converged Services and Protocols for Advanced
Networking
TNL
See Transport Network Layer
Tracking Area (TA)
The TA is a group of contiguous cells that helps track terminal locations in IDLE mode.
Tracking Area Identity (TAI)
This is the identity used to identify tracking areas. The Tracking Area Identity is
constructed from the MCC (Mobile Country Code), MNC (Mobile Network Code) and TAC
(Tracking Area Code).
Tracking Area Update (TAU)
The UE performs this procedure periodically as well as upon its entry to an unregistered
new tracking area (with new TAI) to notify its availability/location to the network and/or
to obtain the new local identity (S-TMSI).
Transmission Control Protocol (TCP)
One of the core protocols of the Internet Protocol Suite. TCP is so central that the entire
suite is often referred to as "TCP/IP." Whereas IP handles lower-level transmissions from
computer to computer as a message makes its way across the Internet, TCP operates at a
higher level, concerned only with the two end systems, for example a Web browser and a
Web server. In particular, TCP provides reliable, ordered delivery of a stream of bytes
from one program on one computer to another program on another computer. Among its
management tasks, TCP controls message size, the rate at which messages are exchanged,
and network traffic congestion.
Transport Network Layer (TNL)
A group of methods and protocols within a layered architecture of network components
within which it is responsible for encapsulating application data blocks into data units
(datagrams, segments) suitable for transfer to the network infrastructure for transmission
to the destination host, or managing the reverse transaction by abstracting network
datagrams and delivering their payload to an application.
Tunnel Endpoint Identifier (TEI)
A 32-bit field used to multiplex different connections in the same GTP tunnel.

TMO21054 Issue 1
Page C:49
U
UDP
See User Datagram Protocol
UE
See User Equipment
UE Connection
a set of run-time constructs and associated dynamic data structures representing an
established connection between a UE and the MME, or a network connection to the MME as
a result of network initiated activity on behalf of a UE (for example, paging). UE
Connections are maintained only while a UE Session is actively signaling (that is,
attaching, setting up or tearing down bearer paths, etc.). Hence a UE Connection will be
instantiated and removed with some degree of frequency. UE Connections are removed
when the UE Session is idle (no signaling traffic) for a period of time. Note that an active
UE Session will have only one UE Connection, and an idle UE Session will not have any UE
Connection.
UE Session
A set of run-time constructs and associated static/dynamic data structures representing
an established and active relationship between a UE and a serving MME, as a result of an
“attach” procedure initiated by an UE via an eNodeB associated with an MME. A UE session
may have one or more bearers associated with it, representing voice, text, or data
paths/flows with other UEs in the network. A UE Session is discontinued with a “detach”
procedure or a UE power-down.
UE Subscription
A set of static/dynamic data structures representing a subscription relationship between a
UE and a serving MME, as a result of an initial “attach” procedure initiated by an UE via an
eNodeB associated with an MME. A UE Subscription lives from the point of the initial
attach until the UE session is terminated as a result of a “cancel” procedure, which may
result from a UE roaming out of the service area of an MME, or from a cancellation of the
UE subscription. Internally, this data structure is represented as a VLR record.
UL
See Uplink
Ultra Mobile Broadband (UMB)
UMB is the 3GPP2 equivalent of the EPS standard (now practically abandoned).
UMB
See Ultra Mobile Broadband
UMTS
See Universal Mobile Telecommunications System
Universal Mobile Telecommunications System (UMTS)
UMTS is the 3G standard developed by the 3GPP consortium.
Universal Terrestrial Radio Access Network (UTRAN)
Represents the access network (or the radio-specific part) of a 3G UMTS network.

TMO21054 Issue 1
Page C:50
Uplink (UL)
A communication link from a mobile to a base station.
User Datagram Protocol (UDP)
One of the core protocols of the Internet Protocol Suite. Using UDP, programs on
networked computers can send short messages sometimes known as datagrams (using
Datagram Sockets) to one another. UDP is sometimes called the Universal Datagram
Protocol.
User Equipment (UE)
UE is the 3GPP name for a mobile terminal. Typically refers to a user’s Mobile Equipment,
but may also include other user equipment, such as a laptop.
USIM
(Universal Subscriber Identity Module). See SIM.
UTRAN
See Universal Terrestrial Radio Access Network

TMO21054 Issue 1
Page C:51
V
VCC
See Voice Call Continuity
Visited Location Register (VLR)
A database where mobile subscriber data are registered according to their actual
localization. For LTE, a VLR is associated with one MME, and contains all subscribers/UEs
that are located in the geographical area served by the MME and that have previously
attached to the MME.
Visited PCRF (V-PCRF)
The Visited GW requests the policy and charging rules from local PCRF, which is V-PCRF.
Visited PLMN (V-PLMN)
This is a PLMN, different from the home PLMN, where the MCC part of the PLMN identity is
the same as the MCC of the IMSI. A Visited PLMN is the PLMN on which the mobile
subscriber has roamed in.
VLR
See Visited Location Register
Voice Call Continuity (VCC)
The process in which a voice call can be persisted, as a mobile phone moves between
circuit switched and packet switched radio domains.
Voice over IP, Voice over Internet Protocol (VoIP)
Voice over Internet Protocol (VoIP) is a general term for a family of transmission
technologies for delivery of voice communications over IP networks such as the Internet or
other packet-switched networks. Other terms frequently encountered and synonymous
with VoIP are IP telephony, Internet telephony, voice over broadband (VoBB), broadband
telephony, and broadband phone.
VoIP
See Voice over IP

TMO21054 Issue 1
Page C:52
W
W-CDMA (WCDMA)
See Wideband Code Division Multiple Access
WiMAX
See Worldwide Interoperability for Microwave Access
Worldwide Interoperability Microwave Access (WiMAX)
The IEEE packet radio standard for short and long-range wireless Internet.
Wide band Code Division Multiple Access (WCDMA)
The chosen radio technology for 3GPP UTRAN. W-CDMA (Wideband Code Division Multiple
Access), UMTS-FDD, UTRA-FDD, or IMT-2000 CDMA Direct Spread is an air interface found
in 3G mobile telecommunications networks. It is the most-commonly used member of the
UMTS family and sometimes used as a synonym for UMTS. It utilizes the DS CDMA channel
access method and the TDD duplexing method to achieve higher speeds and support more
users compared to most time division multiple access (TDMA) schemes used today.
X
XML
See extended Markup Language
Y
Z

TMO21054 Issue 1
Page C:53
TMO21054 Issue 1
Page C:54
TMO21054W Issue 1
Page D:1
TMO21054W Issue 1
Page D:2
TMO21054W Issue 1
Page D:3
TMO21054W Issue 1
Page D:4
TMO21054W Issue 1
Page D:5
TMO21054W Issue 1
Page D:6
TMO21054W Issue 1
Page D:7
TMO21054W Issue 1
Page D:8
TMO21054W Issue 1
Page D:9
TMO21054W Issue 1
Page D:10
TMO21054W Issue 1
Page D:11
TMO21054W Issue 1
Page D:12

LTE Overview PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LTE Overview PDF

Загружено:

Авторское право:

Доступные форматы

Welcome to course TMO21054W – LTE Overview

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

UE – user equipment (mobile device)

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

The UE categories are specified in 3GPP TS 36-306.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

UE – user equipment (mobile device)

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

CSR – Cell Site Router

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

C-plane – control plane

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

OFDMA - Orthogonal Frequency Division Multiple Access

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Refer to Appendix B for more details on the various interfaces.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.

Copyright © 2012 Alcatel-Lucent. All rights reserved.