4 System Acquisition Data Session Setup V 2 1ca PDF

System
Acquisition &
Data Session
Setup
© 2009 Award Solutions, Inc. www.awardsolutions.com +1-877-47-AWARD

2100 Lakeside Blvd., Suite 300
Richardson, TX 75082
Phone: +1.972.664.0727
Fax: +1.972.664.0729
If you have any questions, concerns or comments regarding this course please write to us at:
friends@awardsolutions.com
© 2009 Award Solutions, Inc.
All rights reserved. This course book and the material and information contained in it ("course material") are
owned by Award Solutions, Inc. ("Award"). The course material shall not be modified, reproduced, dissemi-
nated, or transmitted by or in any medium, form, or means, electronic or mechanical, including photocopying,
recording, or any information retrieval system, in whole or in part, without the prior express written consent of
Award. The unauthorized use, modification, reproduction, dissemination or transmission of the course mate-
rial, in whole or in part, is strictly prohibited.
The course material is designed and distributed as instructional aid for courses taught by Award’s authorized
employees and contractors. Award makes no representations or warranties and disclaims all implied warran-
ties with respect to the information contained herein or products derived from use of such information and
undertakes no obligation to update or otherwise modify the information or to notify the purchaser or user of
any update or obsolescence. Award’s total liability in connection with the course material is the amount actu-
ally received by Award from the purchaser/user for the purchase of the course material.
The 3GPP and LTE logos are the property of Third Generation Partnership Project (3GPP). The 3GPP2 logo is
property of Third Generation Partnership Project (3GPP2) and its organization partners. The content of this
document is based on 3GPP/LTE and 3GPP2 specifications which are available at www.3gpp.org, and
www.3gpp2.org.
4 | System Acquisition & Data Session Setup
Version 2.1c
Award Solutions Proprietary - For Alcatel-Lucent Employees Only 1
2 Award Solutions Proprietary - For Alcatel-Lucent Employees Only






This slide provides an insight into the building blocks off In addition to these the UE might also know the RA-RNTI
the chapter. The SIM card stores Network operators and SI-RNTI to identity itself during the initial access
PLMN id list and subscription. The Subscription procedure & reception of SI messages. The UE knows
information defines the policy for system selection helps a most of the general information about the LTE system.
UE to acquire a particular network. This feature enables a But to acquire an LTE network, the UE requires specific
3G network operator (both 3GPP and Non-3GPP) to deploy information from the system (e.g., System bandwidth).
LTE by configuring the policy to decide the network to
hook on.
on Eg.,
Eg 1xEVDO operator can configure to latch on
an existing 1xRTT network for a simple voice call and to
perform a handover to LTE when the subscriber initiates a
high data rate call. Along with these information stored in
the SIM, the Mobile equipment also stores the list of
frequency band supported by LTE, Primary & Secondary
sync signal sequences. General information on the LTE
radio resources and MIMO parameters like the frame
structures, OFDMA and SC-FDMA symbol timing, CP
length, resource blocks, MIMO precoding matrix, Ranks,
Modulation & coding schemes supported are hard coded
into the mobile equipment. UE category, Algorithms to
generate preamble sequences and cell specific reference
signal positions in Radio resource blocks are also stored.
Besides these certain look up tables for computation of
physical cell id, mapping of cell specific reference signal.

The UE performs the functions (as shown in the slide) in Otherwise, it selects another LTE Cell and restarts the
sequence to acquire an LTE system. With the completion process all over again. With the successful LTE cell
of acquisition procedure, UE will have both downlink and selection, the UE is now downlink synchronized.
uplink synchronization with the eNB. Following the power-
After the UE acquired the LTE cell, it performs RRC
up, the UE undergoes a series of hardware tests to verify
connection setup procedure to establish signaling bearer.
integrity of memory and other peripherals. It selects a
Once the signaling bearers are established the UE can
frequency band to acquire an LTE system based on its
perform initial attach to setup a default EPs bearer. The
configured list.
list At this point,
point the UE still has no knowledge
UE is uplink synchronized with a successful RRC
of any operators’ presence. It simply tries to acquire the
connection setup.
network.
The UE scans for the sync signals to acquire Frequency
and Time synchronization. Once the UE acquires primary
and secondary sync signal information, it gains the
knowledge about both synchronization and physical cell
identity. Now the UE is ready to download the system
information broadcast through System Information Blocks
(SIBs) .
The SIBs contain the operator’s PLMN ID among other
parameters. The UE determines whether the PLMN ID is
configured in its list and whether it is allowed to acquire
the operator. If the UE can obtain service from that
operator, it continues with RRC setup procedure.

The LTE frequency and time acquisition procedure

followed by a UE is as shown in the slide. The E-UTRA cell
search procedure supports a scalable overall transmission
bandwidth of 1.4 MHz to 20 MHZ corresponding to six or
more Resource Blocks (RBs). Each RB consists of 12
subcarriers per Time slot. The UE first detects the central
part of the spectrum regardless of receiving bandwidth
capability In this figure,
capability. figure the cell operates at a 20MHz
bandwidth. The UE detects the center spectrum of the
20MHz spectrum. The primary synchronization and
secondary synchronization signals and Broadcast Channel
(BCH) are always spread over six RBs. They carry 62-bit
sequence which occupy the center 62 subcarriers while
five subcarriers on either side are reserved for further
use Once the UE detects primary synchronization and
use.
secondary synchronization signals, it acquires all timing-
related parameters. Since BCH is time-aligned with the
sync signals, the UE acquires the BCH channel and reads
the system information. One essential piece of
information sent on the BCH is the transmission
bandwidth for actual data transmission.

LTE defines 504 unique physical layer cell identities.

These identities are arranged as 168 unique 62-bit
sequences representing unique cell group identities.
Each of these sequence is then scrambled with one of
three 62-bit zadoff-chu sequences to get 168 * 3 = 504
unique cell Identities. Each eNB transmits one of the 168
unique 62-bit sequences on the secondary sync signal
and one of the three unique scrambling sequence on the
primary sync signal ( i.e., secondary sync signals are
scrambled with one of the three unique Zadoff-Chu
sequences transmitted on the primary sync signal). The
UE first acquires primary sync signal to know the unique
62-bit Zadoff-Chu sequence (from a set of three
sequences) and get time synchronized with the system.
Using this information,
information the UE tries detection of secondary
sync information to extract frame timing and physical layer
cell identification. Hence, the UE can easily decode the
secondary sync signal and identify the unique physical
layer cell ID.

All UEs need to read the SIB or System Information Bocks The PDCCH’s SI-RNTI-coded messages points the UEs
that describe the operating characteristics of the system. toward a relatively modest PRB allocation that contains
Key among these is the MIB (Master Information Block), the relevant data, which in the “type 8” case is
which discloses very limited but critical information: it CDMA2000 information.
contains information about the cell bandwidth, some
SIB “Type 1” is especially interesting to UEs; it has lots of
information about the PHICH (Physical HARQ Indicator
general information about the network, information which
Channel) and the SFN. The UE needs this information to
includes the PLMN ID and the scheduling of all the other
find the SIBs which come in “types”
types as suggested in the
SIBs of whatever types.
slide. The SIBs have their own PRBs, the locations of
which are disclosed on the PDCCH. The PDCCH has lots of
user-specific messages having to do with UL and DL
resource allocations. These are made unique to individual
UEs by block coding these messages with a CRC derived
from the C-RNTI (Cell-RNTI). A C-RNTI refers to a specific
radio connection.
connection A UE UE’ss discovers its UL and DL
resources in the PDCCH, which will show that a UE’s
resources are assigned to be in some specific PRBs,
perhaps PRB 0, 1 and 2. The PDCCH resides at the start
of the first slot in a sub-frame.
But since the SIBs are interesting to all UEs, these are
block coded with an SI-RNTI (System Information RNTI).
The SIBs come in “types”
types of SIBs,
SIBs “type
type 8
8” for instance.
instance

Network attachment is basically a registration procedure

where UE needs to register with the network to receive
services . After the UE has acquired the network and has
established signalling radio bearer- SRB1 between UE and
eNB, it performs initial attach procedure where it selects a
MME and then establishes a S1 signalling bearer between
eNB and MME. Next step is authentication. Authentication
in LTE is 2-
2 way authentication i.e.i e UE and network both
authenticate each other. Then S-GW and PDN-GW are
selected. The always-on IP connectivity for users of the
EPS is enabled by establishing a default EPS bearer
during Network Attachment between UE and PDN-GW. The
Attach procedure may trigger one or multiple Dedicated
Bearer Establishment procedures to establish dedicated
EPS bearers for that UE. UE IP address can be allocated
during default bearer set up or it can be allocated after
default bearer set up.

The basic steps involved in contention-based access are: 2. Random Access Response: The eNode B
allocates uplink resources for the UE, and sends
1. Random Access Preamble Transmission: Once a
a response on the downlink control channel
UE has selected a cell, it listens to the system
(PDCCH), using the RA-RNTI to identify which UE
overhead information transmitted on the
group the allocation is for. Within each RA-RNTI
downlink. The System Information Blocks (SIBs)
group, RA preamble identifier is used to identify
provide configuration parameters for the
a specific UE. The random access response
network. SIB2, in particular, includes key
contains timing adjustment,
adjustment UL resource
parameters for initial system access. The UE
allocation, and temporary C-RNTI.
selects a random preamble and sends it over the
PRACH. The transmit opportunity is identified by
the Random Access Radio Network Temporary
ID, or RA-RNTI. In LTE FDD, RA-RNTI identifies
subframe number and ranges from 0 to 9. It is
obvious that multiple UEs may transmit in the
same subframe and thus use the same RA-RNTI.

3. Scheduled Transmission: The UE uses the Non-Contention-Based access is used when the UE is
allocated resources to transmit its message already in communication with the eNode B. The network
(such as an RRC Connection Request), and initiates the process by sending an allocated preamble to
includes its assigned temporary Cell RNTI (C- the UE, indicating when it can transmit. Since the eNode B
RNTI) and a 48-bit randomly-chosen UE controls the process, there are no collisions with other
Contention Resolution Identity. UE’s, and latency is significantly reduced.
4. Contention Resolution: The eNode B sends a
contention resolution message on the downlink
and addresses to Temp C-RNTI. If the UE sees its
Temp C-RNTI and contention resolution ID in the
grant, then its transmission was successfully
received. The Temp C-RNTI is promoted to C-
RNTI if the UE has no C-RNTI yet. If the UE has
already has C-RNTI but loses UL synchronization,
the UE’s C-RNTI is kept and the Temp C-RNTI is
discarded. Otherwise, there was a collision or
other failure, and the UE must retry the access
attempt.

This slide explains why different preamble format is The eNB broadcasts root sequence index and cyclic shift,
needed. In LTE, a UE has not synchronized with the as well as # of preambles (default is 64) in a cell. A UE in
network in the uplink when it sends out random access the cell listens to the broadcast, generates the preambles,
preamble. So the random access sequences sent by the and randomly picks one out of 64. The root sequence
UE at the cell edge and the UE near the eNB may arrive at index and the cyclic shift are determined by network
the eNB at different moments. But the preamble should planning. The cyclic shift is related to the size of the cell.
not interfere with the information/subframe the eNB There are total 838 root sequences available. The length
receives before and after the preamble,
preamble i.e.,
i e the non-
non of each root sequence is 839.839 One root sequence can
synchronized preambles are received within a certain generate several preambles by cyclic shift. One or more
window. The difference between the arrival moments is root sequences are needed to generate all preambles in a
the guard time, which is equal to round trip delay plus cell.
delay spread. Obviously, the length of the guard time
determines the cell size. Longer guard time supports
larger cell size. In order to address different cell size, four
preamble formats are defined for LTE FDD. FDD Depending on
the specific format, a preamble may occupies 1, 2, or 3
consecutive subframes. The cyclic extension or preamble
repetition can be used to lengthen the preamble. Note
the preamble format is decided at network planning stage
and only one format is used for a specific cell.

The RRC connection establishment procedure is used to

establish an RRC connection.
The UE sends an RRC Connection Request to the eNB. In
this message, it identifies itself and also includes an
Establishment cause value for any of the purpose as
mentioned in the slide. This message is sent using the
RLC-TM.
The eNB answers, with the RRC Connection Setup. This
message is used to establish Signaling Radio Bearers
(SRBs). It includes the RRC Transaction ID. This message
is sent using the RLC-TM.
The UE now sends a RRC Connection Setup Complete
message to the eNB to confirm the successful completion
off an RRC connectionti establishment.
t bli h t It includes
i l d th
the
selected PLMN identity from the PLMN-Identity list
provided in SIB1, registered MME and also the initial NAS
dedicated information/ message. This message is sent
using the RLC-AM.

A MME pool area is defined as an area consisting of a The Weight Factor is typically set according to the capacity
number of Tracking Areas. It is an area within which a UE of an MME node relative to other MME nodes. e.g., a
may be served without need to change the serving MME. newly installed MME may be given a very much higher
An MME pool area is served by one or more MME’s in weight for an initial period of time making it faster to
parallel. MME pool areas may overlap each other. In this increase its load. The MME Load Re-balancing
pool of MME’s, eNB is connected to multiple MME’s and functionality permits UEs that are registered on an MME
has a choice to select any MME . Pool area concept (within an MME Pool Area) to be moved to another MME
provides network redundancy i.e i e if one core network node eg this can happen when one of MME fail or is brought
eg.
fails then its load can be distributed to other MMEs. It also down during upgradation. In such cases, the Weight factor
provides load balancing concept by connecting eNB’s to for that MME will be set to zero.
multiple MME’s and sharing traffic on these multiple
nodes avoiding network congestions.
Load balancing between MMEs enables the network to
ensure equally loaded MMEs within a pool area. And
permits UEs that are entering into an MME Pool Area to be
directed to an appropriate MME in a manner that
achieves load balancing between MMEs. This is achieved
by setting a Weight Factor for each MME, such that the
probability of the eNodeB selecting an MME is
proportional to its Weight Factor.

The UE initiates the Attach procedure by the transmission

of an Attach Request message which contains IMSI, UE
Network Capability, PDN Address Allocation, to the eNB.
The PDN Address Allocation indicates whether the UE
wants to perform the IP address allocation during the
execution of the procedure and, when known, it indicates
the UE IP version capability (IPv4, IPv4/IPv6, IPv6), which
is the capability of the IP stack associated with the UE.
UE
After reception of attach request, eNB selects MME. Still it
does not have S1 bearer between eNB and MME, so it
sends an initial UE message (a S1-AP message) to the
selected MME, with the ‘eNodeB S1-AP UE Identity’. NAS
Attach message is piggy backed on this initial UE
message. MME processes the Attach request message
and sends back a NAS reply like Identity request or
authentication request. The NAS reply from the MME is
carried the S1-AP ‘DL NAS Transport’ message. This
message carriers the MME S1-AP UE Identity. Reception
of ‘MME S1-AP UE Identity’ in the S1-AP message
completes the S1-MME bearer establishment procedure.

This slide depicts the EPS AKA authentication process F1 gets the network’s RAND, SQN (already checked for
which is an adaptation or reuse of the UMTS AKA “freshness”), AMF and the USIM’s Kauth and produces
mechanism and its USIM. The authentication process XMAC (eXpected MAC). The UE checks to see if XMAC is
begins when the network delivers AUTN and RAND to the the same as MAC embedded in AUTN from the network. If
USIM within the UE. The USIM validates AUTN by so, then F2’s RES is sent back to the network. CK (Cipher
generating its own AK (Anonymity Key) with an F5 Key) and IK (Integrity Key) are also generated by their
algorithm and its own copy of the Authentication Key (a respective algorithms, F3 and F4.
shared secret) and the network
network’ss RAND.
RAND The UE computes
(uncovers) SQN (Sequence Number) by simply XOR-ing
SQNHE (the SQN embedded in AUTN sent from the HE or
Home Environment) with own its AK. SQNHE (the home
environment’s SQN) is a counter value manufactured in
the home network’s AuC (Authentication Center). SQNMS
(mobile side SQN) is the highest SQN the UE will accept
from the network.
network The UE compares SQNHE (derived from
the from the network’s AUTN) with its limit value, the last
value used, on the SQN, SQNMS. If SQNHE is not bigger
than SQNMS, then the same authentication vectors have
already been used and are not fresh.

After authentication, MME updates the UE location in the

HSS database. HSS sends Insert Subscriber Data (IMSI,
Subscription Data) message to the new MME. The
Subscription Data contains the list of all APNs that the UE
is permitted to access, an indication about which of those
APNs are the Default APNs. Subscription data also
includes for each APN, if it is allowed to connect to the
visited network PDN GW. GW The acknowledgement
messages follow the first two messages.

A S-GW service area is defined as an area consisting of a Subscription data also includes for each APN, if it is
number of Tracking Areas. It is an area within which a UE allowed to connect to the visited network PDN GW. MME
may be served without need to change the Serving GW. A maps each APN to a particular PDN GW. PDN-GW is
Serving GW Service Area is served by one or more Serving selected based on the subscription data. Please note that
GWs in parallel. S-GW is selected on the bases of network PDN GWs in a network may either support PMIP or GTP.
topology. Serving GW selection can be done such that it The mobility mechanism supported by the PDN GWs
reduce the probability of changing the Serving GW. selected play a role in the selection of the S-GW.
Another selection criteria could be load balancing concept.
concept
Load balancing between S-GW’s enables the network to
ensure equally loaded S-GW’s within a S-GW service
areas.
S-GW selection also depends on selected PDN-GWs. If a
subscriber of a GTP only network roams into a PMIP only
network and he has a mixture of both home PDN-GW and
visited PDN-GW in his selected PDN-GW list then the MME
should select a SAE-GW that supports both GTP and PMIP
based mobility.
After authentication, HSS sends Insert Subscriber Data
(IMSI, Subscription Data) message to the new MME. The
Subscription Data contains the list of all APNs that the UE
is permitted to access, an indication about which of those
APNs are the Default APNs.

In the case of GTP-based S5 connections, an EPS bearer The eNB maps an air interface radio bearer to/from the
is composed of the three traffics paths shown in the S1 GTP tunnel in the UL and DL respectively. The eNB also
picture. The S5 interface carries the traffic of an EPS stores this mapping info ( RB ID <-> S1 TEID) as part of
bearer in a GTP tunnel. Similarly the S1 interface between the UE context.
the S-GW and eNB carries the traffic of an EPS bearer in
The S-GW maps the S1 GTP tunnel to/from the S5 GTP
another GTP tunnel. The third leg is the air interface
tunnel bearer tunnel in the UL and DL respectively.
component known as a radio bearer. There is a one-to-one
mapping between the EPS bearer and all three The S-GW also stores this mapping info (S1 TEID <-> S5
component paths. TEID) as part of its UE context information.
The EPS bearer is also characterized by UL and DL filters, Note that if there is a PMIP based S5 interface the EPS
known as traffic flow templates (TFT). One or more packet bearer has a different structure from that described
filters are used to recognize a service data flow. If multiple above. The major difference is that there is a single PMIP
SDFs are mapped into a single EPS bearer then the tunnel for all EPS bearers.
combined set of filters used to recognize the aggregate
set of SDFs constitutes the TFT for the EPS bearer.
At the UE, the Uplink Traffic Flow Template (UL TFT) maps
UL packets to the appropriate Radio Bearer. At the PDN-
GW the Downlink Traffic Flow Template (DL TFT) maps DL
packets to the appropriate S5 GTP tunnel.

The PDN-GW is responsible for mapping IP packets in the

downlink to the appropriate GTP tunnel before it is
forwarded to a S-GW.
The packets arriving from an external Packet Data
Network do not contain any explicit information on the
service data flows they belong to. Therefore the PDN-GW
must use IP network layer and transport layer header
information to classifies incoming traffic and detect which
SDF it belongs to. The PDN-GW will know which EPS
bearer the SDF is associated with and therefore the GTP
tunnel..
Since there is a GTP tunnel for each EPS bearer, the PDN-
GW must classify and map the incoming packets from the
PDN to the correct tunnels. In this case,, the task at the S-
GW is simpler. Since there is a one-to-one mapping
between the S5 tunnel and the corresponding S1 tunnel
the S-GW does not need to perform classification of
packets.

Flow classification in the DL is always done by the P-GW.

At the P-GW, the incoming IP packets are handled by a
packet handler process. It uses the L3/L4 headers in the
IP packet to identify the SDF. As shown in the figure, for
each service data flow, the P-GW keeps a traffic flow
template per EPS bearer. Each SDF is associated with one
or more IP packet filters which are used to identify the
flow that a packet belongs to.
to The incoming packets are
mapped to the appropriate SDF which then maps to a
particular EPS bearer.
The EPS bearer, being composed in part of the S5 bearer,
is mapped to the GTP tunnel to the S-GW. The P-GW
marks the outer IP packet with the appropriate DSCP
corresponding to the QCI of the EPS bearer. The
encapsulated packet is sent to the S-GW.

After selection of S-GW, next important step is to create

default EPS bearer. MME keeps track of all the bearers
created for an UE by bearer identity. MME sends a Create
Default Bearer Request to the S-GW. The Serving GW
creates end points for the default bearer and sends them
to the PDN-GW using the Create Default Bearer Request
message. It also sends UE’s PDN address allocation
parameter This is used by the PDN-GW
parameter. PDN GW to decide if it
should allocate the IP address to the UE during the default
bearer creation. In the example covered here, PDN-GW is
allocating an IP address to the UE during the default
bearer creation. The other scenario where it is done after
the attached procedure is covered later in this topic.

The PDN GW returns a Create Default Bearer Response

message to the S-GW. This message contains the PDN-GW
tunnel IDs for the default bearer and also the IP address.
The S-GW replies to MME with the Create Default Bearer
Response. In this response, S-GW sends the default
bearer tunnel IDs for the default bearer that needs to be
established between the S-GW and the eNodeB. Please
note that the creation of the default bearers between the
S-GW and the eNodeB is co-ordinated by the MME.

MME sends an Attach Accept message which contains

GUTI, PDN Address Information, TAI List, EPS Bearer
Identity, and Session Management Configuration IE to the
eNB. Attach Accept is embedded in the S1-MME control
message and sent to the eNodeB. Along with the Attach
Accept message, MME also forwards the S-GW tunnel IDs
to the eNodeB. eNodeB makes a note of the S-GW tunnel
Ids and forwards the Attach Accept message to the UE
using the RRC connection reconfiguration message.
eNodeB sends default radio bearer related parameters in
the RRC connection reconfiguration message. UE now
sends the Attach complete message embedded in the
RRC Connection reconfiguration Complete message to the
eNB. This completes the establishment of the default
radio bearer.
bearer

With the Attach Complete message, the UE starts using

the NAS security algorithm indicated by the MME, i.e. the
Attach Complete message shall be protected by the NAS
security algorithm indicated by the MME. The eNB
forwards the Attach Complete message to the new MME
in an S1 control message. This S1 control message
includes the TEID of the eNB and the address of the eNB
used for downlink traffic on the S1-U
S1 U reference point.
point After
the Attach Accept message and once the UE has obtained
a PDN Address Information, the UE can then send uplink
packets towards the eNB which will then be tunnelled to
the Serving GW and PDN GW. MME sends an Update
Bearer Request (eNodeB address, eNodeB TEID, EPS
bearer ID) message to the Serving GW and finally Serving
GW acknowledges by sending Update Bearer Response
(EPS Bearer Identity) message to the MME. This
completes the establishment of the default S1-U EPS
access bearer. Thus now end to end default EPS bearer
can be realized.

The matter of IP-addressing is deliberately kept very free-

form with very few hard directives, save for the LTE
network having the final say. Though a subscriber may
have his preferences in PCO (Protocol Configuration
Options), the network will retain ultimate control of IP-
addressing. Within all the options we see that addresses
can be assigned by the home network, the visited network
or even an external PDN (Packet Data Network). Network)
Addresses can be assigned during or after default bearer
activation, the addresses can be dynamic or static, and
they can be IPv4, IPv6, or IPv4 within IPv6.
3GPP has defined 3G-like GTP-based the S5 and S8
interfaces between the SGW and the PDN GW (P-GW),
using GTPv1 for the user plane and GTPv2 for the control
plane. The operator has the option of employing IETF-
based protocols in the place of GTP-based tunneling; that
is PMIP or GTP can be employed across the S5 and S8
reference points.

It matters not where the IPv4

4 address comes from,
f the P-
GW or an external PDN, the allocation of the address to
the user is the same.
The UE initiates the Attach procedure by sending its Attach
Request to the eNB. The MME responds with an
Identification Response. The MME uses the UE’s APN for
default bearer activation and then creates a new entry in
its bearer table to map the APN to PDN Gateway (P-GW).
The S-GW (Serving Gateway) sends a Create Default
Bearer Request message to the selected P-GW, which
creates a new entry in its bearer context table, The entry
lets the P-GW route user plane packets between the S-GW
and the packet data network, and, of course, to start
charging for the service.

In order to support DHCP based IP address configuration,

the PDN GW can play the role of a DHCP server. In the
case that services of an external DHCP server are used,
PDN-GW can act as a DHCP client. S-GW plays the role of
a DHCP relay. UE starts the IP address acquisition after
setup of the default bearer setup. First UE discovers the
DHCP server using the DHCP discovery procedure. It gets
the address of the DHCP server using this procedure.
procedure Next
it requests the DHCP server for one or more IP addresses.
Steps 1 through 6 here show the DHCP discovery
procedure. Steps 7 through 12 explain the IP address
assignment to the UE.

The Evolved Packet System (EPS) allows a user to connect

to external IP networks. The public internet is the most
common IP network that comes to mind but there may
also be a need for a user or group of users to connect to
private networks such as corporate networks or to an IMS
services network. In general then, the EPS provides a PDN
Connectivity Service which allows a user to connect to
multiple external IP networks perhaps simultaneously.
simultaneously In
addition a single PDN Connection may support multiple
simultaneous Service Data Flows (SDFs).
A user subscription may allow him to connect to two or
more PDNs. For each of the subscribed PDNs, the user’s
profile in the HSS contains an Access Point Name (APN)
which identifies the PDN. This APN can be used to choose
a suitable PDN GW for the user’s PDN connectivity service.
On initial connection to the EPS, a default APN, identified
in the subscription data, is used during the Attach
procedure for PDN connection.
Subsequently the user may establish connectivity with
another PDN by specifying which APN to connect to.


A Service Data Flow (SDF) is an end to end application This is known as an SDF aggregate.
level packet flow between a UE and one or more devices
An EPS bearer is the level at which QoS is enforced in the
in an external Packet Data Network (PDN) . A single PDN
network. An SDF aggregate will be “carried “ across the
connection for a UE, associated with an IP address, can
EPS network in an EPS bearer.
support multiple service data flows. A Service Data Flow is
the level at which EPS defines Quality of Service In the slide we see an example where the user is running
parameters. For example lets say a user wants to access three SDFs simultaneously. Two of these require the exact
a home video streaming service.
service The service level QoS same QoS treatment and so form an SDF aggregate.
aggregate A
may be defined with a specific packet delay budget for specific EPS bearer is constructed between the PDN-GW
transit through the operator’s network. It will be assigned and the UE to carry the traffic of these two SDFs. The
a relative priority in comparison to other services and may third service the user is running requires a different
be assigned a guaranteed bit rate. These and other delay budget than the other two and so the network has
characteristics define how this service will operate in a constructed a second EPS bearer to carry this traffic.
congested network. The expected behavior may be In summary, a user may simultaneously establish
absolute or at times relative to other services.
services If the ti it with
connectivity ith multiple
lti l PDNs.
PDN Each
E h off the
th user’s
’ PDN
same user wants also to use video streaming from an connections may support ≥ 1 EPS Bearers and each of
Internet service, the quality requirements may be the the EPS Bearers will carry an SDF aggregate. [An SDF
same or different as the home streaming just discussed. aggregate of one is possible]
If the user wants to experience the same quality for both
video services each will operate under the exact same
QoS parameters. Then the network will treat these two
flows, if theyy are runningg simultaneously,
y as a single
g flow
from the perspective of quality assurance.

The key QoS parameters associated with a service data 3. Allocation and Retention Priority (ARP): This
flow are shown in this figure. parameter will be used in congestion situations
when not all users and their services can be
1. A QoS Class Identifier (QCI): Defines the general
accommodated. The ARP will be used by the
class of the service. There are currently 9
admission control function in the eNB.
defined. A QCI is associated with a priority,
specific delay and packet loss values and For example a user may subscribe to a service such as
whether the service has a guaranteed bit rate. Real Time Gaming. In EPS Real Time Gaming is defined as
These characteristics will be used by the EPS a specific class of service with a defined QCI value and
nodes (eNB, S-GW, P-GW) to guide them in associated parameter values for packet delay etc.. Real
deciding how a particular service data flow is to Time Gaming is a GBR service and will therefore be
be processed. QCI determines such things as assigned a guaranteed and maximum bit rate when the
resource scheduling, rate shaping, and queue user subscribes. These bit rates may depend on the type
management and also maps to a specific DSCP of game in question.
for IP forwarding thru the GTP tunnels. At the
eNB QCI will also be be used to determine RLC
configuration.
2. Bearer type: For GBR bearers the GBR and MBR
parameters will be specified. For Non-GBR
bearers the AMBR parameter will be specified.

The QoS attributes associated with the QoS Class Indices - The packet delay budget associated with an SDF
are shown in the slide. will be one of the inputs used by the scheduler
in the eNB in determining when to deliver
- Service data flows with QCIs of GBR bearer type
packets of the SDF. The PDB values given in the
will be associated with a Guaranteed Bit Rate
table are a measure of the maximum time
parameter, and a Maximum Bit Rate parameter.
allowed for packet delivery from PDN-GW to UE.
The GBR parameter in particular will used in the
The eNB can assume that on average, the delay
admission control function in the eNB.
from PDN-GW
PDN GW to eNB is 20ms and from this
- Each QCI value has a priority which will be used calculate the maximum over the air delay
by EPS traffic nodes during congestion. If packet budget.
queues are close to overflow then SDFs with
lower priority that others (Priority 9 is the lowest)
will have their packets discarded first. Note that
IMS Signaling packets have the highest priority
while QQCI 9 is equivalent
q to best effort service.
Prioritization of SDF aggregates of the same
user will use this value and it should also be
used in the prioritization across users though the
PDB will play a greater role in the scheduling of
one user’s traffic over another.

PCC
CC or Policy Charging
C and Control
C is an aspect off policy- Event Reporting Function) detects these events, a roamer
based networking. The QoS architecture depicted in this trying to access his serves outside the home network for
slide has, at its heart, the P-GW which acts as the PEP instance, and reports these events to the PCRF so that
(Policy Enforcing Point), which we call the PCRF here. The appropriate charges can be generated, or even
PCRF reserves buffer space and appropriate bandwidth disallowing the services entirely in some cases.
for the actual delivery of packets in accordance with a QoS
specifications. The SPR is a logical function, probably
residing in the HSS (Home Subscriber Server),
Server) which is a
data base of all the QoS particulars for selected services:
precedence, peak data rates, average date rates, etc. the
AF (Application Function) is the “thing” the or the “service”
the UE is exchanging packets with: VoIP, video streaming,
etc.
The PCRF allows (or not) a flow to occur, and will charge a
fee for flows in a prescribed manner, perhaps in time or by
the number of bytes. The OFCS is the “bank” that knows
how much money the subscriber has for services; it knows
the extent of the user’s credit within the domain of
interest of the wireless operator.
PCC sometimes falls outside the control of the home
network. When this happens, the BBERF (Bearer Binding
and

eNB can know the UE’s capability through the UE

capability enquiry message. This message is transmitted
on DCCH/SRB1 in AM mode. The parameter sent on UE
capability enquiry messages are RRC transaction ID and
UE radio access capability request (both EUTRA and other
RAT).
In response to the UE capability enquiry, the UE transmits
UE capability information on DCCH/SRB 1 in AM mode.
Providing the following details of the access stratum:
release supported ( Rel 8), UE category, PDCP profiles
supported, MAX L2 buffer size and physical layer
parameters. Physical layer parameters include support
for UL Transmit diversity, UE specific reference signal and
Half-FDD. ROCH profile and the maximum number of
ROCH supported by the UE forms the PDCP profile. RF
parameters indicates the list of LTE bands supported by
the UE. If the UE supports inter RAToperations, then it lists
Inter RAT frequency Band info and the measurement
parameter. Max L2 buffer size indicates RLC buffer size
for all the radio bearers.
The eNB forwards these UE radio capabilities to MME via
UE CAPABILITY INFO INDICATION message.

Here are some examples of the capabilities of LTE

subscriber devices arrayed in five categories in the uplink
and the downlink instances. Note that the 300 Mbps DL
capability requires four antennas, or four spatial paths
between the eNB and the UE.
The latest specifications can be found in 36.306, which is
available in the specifications section of at www.3gpp.org.

The figure shows a high level message flow for dedicated

bearer establishment.
After the UE registers, authenticates, obtains an IP
address and has a default bearer established, the user
can start various services applicable to the QoS defined
for the default bearer.
When the user decides to start a service that requires a
different QoS than the default, then a new EPS Bearer
must be established to carry the traffic. In the example
shown in the slide, SIP signaling is carried out on the
Default Bearer. SIP is being used to establish a service.
The PCRF is controlling the establishment of the service
and passes its QoS policy decision to the PDN-GW. The
PDN GW will
PDN-GW ill interpret
i t t the
th PCC rules
l andd applyl the
th policies
li i
to the new SDF and Dedicated Bearer. It then
communicates with the S-GW which in turn get s MME
involved which in turn get the eNB involved in establishing
the S5 and S1 bearers. The eNB performs admission
control to determine if enough bandwidth is available for
the service data flow. If admission control is successful, it
uses RRC procedures to establish a radio bearer.
bearer








4 System Acquisition Data Session Setup V 2 1ca PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

4 System Acquisition Data Session Setup V 2 1ca PDF

Caricato da

Copyright:

Formati disponibili

System

© 2009 Award Solutions, Inc. www.awardsolutions.com +1-877-47-AWARD

© 2009 Award Solutions, Inc.

2 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 3

4 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 5

6 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 7

8 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 9

The LTE frequency and time acquisition procedure

10 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

LTE defines 504 unique physical layer cell identities.

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 11

12 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Network attachment is basically a registration procedure

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 13

14 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 15

16 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

The RRC connection establishment procedure is used to

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 17

18 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

The UE initiates the Attach procedure by the transmission

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 19

20 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

After authentication, MME updates the UE location in the

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 21

22 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 23

The PDN-GW is responsible for mapping IP packets in the

24 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Flow classification in the DL is always done by the P-GW.

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 25

After selection of S-GW, next important step is to create

26 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

The PDN GW returns a Create Default Bearer Response

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 27

MME sends an Attach Accept message which contains

28 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

With the Attach Complete message, the UE starts using

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 29

The matter of IP-addressing is deliberately kept very free-

30 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

It matters not where the IPv4

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 31

In order to support DHCP based IP address configuration,

32 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

The Evolved Packet System (EPS) allows a user to connect

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 33

34 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 35

36 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 37

38 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

eNB can know the UE’s capability through the UE

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 39

Here are some examples of the capabilities of LTE

40 Award Solutions Proprietary - For Alcatel-Lucent Employees Only

The figure shows a high level message flow for dedicated

Award Solutions Proprietary - For Alcatel-Lucent Employees Only 41

42 Award Solutions Proprietary - For Alcatel-Lucent Employees Only