AfriCell Day 2
AfriCell Day 2
AfriCell Day 2
Day 2
Day Contents
• Interfaces, Bearers and Protocols
• LTE Key Technologies
• OFDMA
• SCFDAM
• HARQ
• AMC
• MIMO
2/38
Air Interface - RRC
As with other E-UTRA protocols, the RRC layer, which previously resided
in the RNC, has been relocated to the eNB. In addition, the functionality
and complexity of RRC has been significantly reduced relative to that in
UMTS. The main RRC functions for LTE include creation of BCH system
information; creation and management of the PCH (Paging Channel);
RRC connection management between eNB and UEs, including
generating temporary identifiers such as the C-RNTI; mobility-related
functions such as measurement reporting, inter-cell handover and
inter-eNB UE context handover; QoS management; and direct transfer
of messages from the NAS to the UE.
3/38
Air Interface – L2 Overall view
There are three sublayers within the E-UTRA layer 2, PDCP, RLC
and MAC (Medium Access Control). All the sublayers, including
PDCP, span both the control and user planes of the protocol
stack, although in most cases the functions provided in each
plane differ.
4/38
Air Interface - PDCP
A PDCP entity is created for each SRB and/or DRB on a per-UE basis. All PDCP
entities are bidirectional, thus when the AM mode of RLC is being used there is a
one-to-one mapping between a PDCP entity and AM SAP in RLC. However, for
the UM mode of RLC one PDCP entity will be associated with two UM SAPs, one
configured for transmit functions and the other configured for receive functions.
Within a PDCP entity sequence numbering is applied for higher layer PDUs. This
ensures in-order delivery at the receiving end. In the user plane PDCP control
PDUs can be used to indicate missing PDUs.
In the control plane, integrity protection is provided for RRC signalling messages.
Ciphering is then applied in both control and user planes, although separate
cipher keys are applied for a given UE in the two planes.
5/38
Air Interface - RLC
The transparent mode has no functions, only providing a buffer for Unacknowledged mode entities are accessed through a
higher-layer packets that are to be transmitted over the air interface. UM-SAP. Unacknowledged mode reorganizes RLC SDUs
Transparent mode entities are accessed via a TM-SAP. into a size requested by the MAC layer.
Unacknowledged mode also provides sequence
The application of transparent mode is limited to the downlink numbering for in-order delivery to higher layers at the
transmission of system information and paging messages as well as the receiving end. Reordering in the RLC layer is used in
exchange of RRC connection establishment messages associated with support of the HARQ functions provided by the MAC
the CCCH (Broadcast Control Channel). layer.
6/38
Air Interface - RLC
The acknowledged mode of RLC is applicable in the control plane for
RRC signalling messages carried in DCCH and for user plane traffic
carried in DTCH. Acknowledged mode entities are accessed through an
AM-SAP.
The MAC layer is accessed through logical channels as well as a control SAP. It maps
information flows into the physical layer through transport channels. The mapping
of logical channels to transport channels is a key function of the MAC layer.
In addition to channel mapping, the MAC layer has important control functionality
including management of multiple HARQ processes for each information flow and
the random access process.
Most significantly, the MAC layer is responsible for channel prioritization and
scheduling of resources on the physical layer.
The MAC layer has a null function for paging and for system information that will be
transmitted in the BCH (Broadcast Channel) transport channel.
8/38
LTE Interfaces – LTE bearers
The EPS Bearer ID (EBI) is assigned by the MME upon bearer establishment.
The EBI consists of 4 bits which in theory allows a maximum of 16 EPS bearers
to be created for each UE. However, the relevant specification indicates that 5
values are reserved which limits the number of EPS Bearers per UE to 11. EBI
values are always assigned by the MME which sets the EBI value for the default
bearer and sends it to the S-GW. In the same way, the MME also assigns the EBI
value to dedicated bearers. In UMTS networks the equivalent of an EBI is the
NSAPI (Network Layer Service Access Point Identifier) which is used to identify a
PDP context. When the UE moves from LTE to UMTS, the EBI is mapped to an
NSAPI – this mapping is not complex as both NSAPI and EBI are 4 bit values.
The EPS Bearer travels between the UE and the PDN-GW; during handovers it
may also extend over the X2 interface between source and target eNBs.
9/38
LTE Interfaces – LTE bearers
To allow the S1 and X2 protocols to identify the UEs that form the endpoint of each transport tunnel,
terminals are assigned identities that are unique within the eNBs or MMEs that support those
endpoints.
The UE S1-AP ID and MME S1-AP ID are unique within the eNB and MME respectively that are handling
the E-RAB/EPS Bearer to an Attached UE. The IDs are simple numerical identifiers (24-bits in the eNB
and 32-bits in the MME) and are not associated with a specific instance of the S1 interface in each
device. An eNB can therefore support a maximum of 224 (16.7 million) UE S1 connections and an MME
232 (4.3 billion).
The UE X2-AP ID performs the same basic function as the S1-related identities, but for the X2 interface.
The X2 is optional and is only used to pass handover-related traffic between source and target eNBs, so
the X2-AP ID will only be created as required when a handover is initiated. The ID is 12 bits long and
provides a maximum of 4096 UE X2 handover identities per eNB.
The 4-byte GTP TEID is used in the EPS the same way as it is in legacy networks. Each device that
supports a GTP tunnel refers to it in terms of the TEID assigned to the tunnel plus the IP address and
UDP port number of the interface that handles it. TEIDs are assigned by the receiving side of each
connection and are exchanged using S1-AP during tunnel establishment.
10/38
LTE Interfaces – LTE bearers
Each UE will establish an initial or default EPS Bearer as part of
the attach process. This will provide the required ‘always on’ IP
connectivity to the UE and may be to a default APN (Access
Point Name), if one is stored in the user’s subscriber profile, or
to an APN selected by the network.
In networks that interconnect to an IMS, the default bearer allows the UE to perform SIP
registration and thereafter to provide a path for session initiation messaging. In these
circumstances, the data rate and QoS assigned initially to the default bearer is commensurate
with the expected low level of SIP-based traffic flow, but these parameters could be modified to
accommodate the requirements of application traffic flows when a connection is established. In
reality, however, a separate EPS Bearer is established to carry LTE call media traffic, so the Default
EPS Bearer would only need to be adjusted if the level of SIP traffic exceeded the capacity
provided by the original QoS settings.
11/38
LTE Interfaces – LTE bearers
12/38
LTE Interfaces – LTE bearers
QoS in the EPC is currently defined by three levels: GBR, MBR and AMBR (Aggregate Maximum
Bit Rate).
GBR connections are assigned a guaranteed data rate and are therefore useful for carrying
certain types of real-time and delay-sensitive traffic. MBR connections are non-guaranteed,
variable-bit-rate services with a defined maximum data rate. If a connection’s data rate goes
beyond the set maximum the network may decide to begin discarding the excess traffic.
GBR and MBR parameters are applied on a ‘per bearer’ basis, whereas AMBR is applied to a
group of bearers; specifically, a group of non-GBR bearers that terminate on the same UE.
AMBR allows the EPS to set a maximum aggregate bit rate for the whole group of bearers that
can then be shared between them.
The APN-AMBR parameter sets the shared bit rate available to a group of non-GBR bearers
that terminate on the same APN and can therefore be seen to be applied on a ‘per PCS’ basis;
the UE-AMBR parameter aggregates all non-GBR bearers associated with one UE.
Dedicated bearers can be established as GBR or non-GBR (i.e. MBR) as required. Default
bearers, due to the probable need to adjust their bandwidth after the initial Attach has taken
place, must be non-GBR.
13/38
LTE Interfaces – LTE bearers
An EPS bearer provides a data path between a UE and an APN located in a PDN-GW.
Once created, an EPS bearer can be in one of two states – active or inactive.
When active, the EPS bearer is assigned bearer resources that amount to a radio
bearer and GTP tunnels, with assigned TEIDs (Tunnel Endpoint IDs) that will carry the E-
RAB (E-UTRAN Radio Access Bearer) and EPS Bearer over the Uu, S1-U and S5/S8
interfaces.
Each PDN connection and default and dedicated EPS bearer is described by a Bearer
Context stored in the UE and MME and in other devices required to serve each bearer.
Default and dedicated bearer contexts describe the UE’s current ECM state (idle or
connected) plus the bearer’s EPS bearer ID and QoS parameters, and can be either
active or inactive.
An active Bearer Context is deemed to be in the ESM BEARER CONTEXT ACTIVE state.
14/38
Day Contents
• Interfaces, Bearers and Protocols
• LTE Key Technologies
• OFDMA
• SCFDAM
• HARQ
• AMC
• MIMO
15/38
OFDMA – Principle of OFDM
•OFDM is a type of Multi-Carrier Transmission.
16/38
OFDMA – Principle of OFDM
Consider a radio carrier being modulated by a 10 kbit/s bit steam using QPSK
(Quadrature Phase Shift Keying). It could be expected to see a spectral envelope
following a (sin x)/ x function, as shown in the diagram, with the first null located 5
kHz from the centre frequency.
In a classic FDM (Frequency Division Multiplexing) system, other radio carriers would
be allocated and spaced far enough away from the first to ensure minimal adjacent
channel interference. The size of the guard band required would depend on the
transmitter and receiver characteristics as well as the relative powers.
17/38
OFDMA – Principle of OFDM
Considering again the two overlapping QPSK radio carriers, it can be seen that there is
a relatively large spectral efficiency gain. If the effective bandwidth of the transmitted
signal is considered to be the frequency separation of the first nulls then a single QPSK
carrier modulated with 10 kbit/s would have a null-to-null bandwidth of 10 kHz.
However, here there are two subcarriers, each of which is carrying 10 kbit/s using
QPSK. Their
respective null-to-null spectra overlap by 5 kHz. This gives a collective null-to-null
bandwidth for the pair of subcarriers of 15 kHz. Thus QPSK is being used to carry 20
kbit/s in a radio bandwidth of 15 kHz.
Note that a single QPSK modulated carrier carrying 20 kbit/s would result in a null-to-
null bandwidth of 20 kHz.
This results in a very spectrally efficient channel that can carry high bit rates.
18/38
OFDMA – Principle of OFDM
Time
Modulated
OFDM
Symbol
Amplitude
Cyclic
Prefix
Frequency
OFDM
Symbol
19/38
OFDMA – Principle of OFDM
20/38
OFDMA in LTE
BW Sub_Carriers N_IFFT Sampling Frequenncy N_used Actual BW Guard
Spacing Band
5 MHZ 512 ??? 300 4.5 MHZ 0.5 MHZ
10 MHZ 15 KHZ 1024 ??? 600 9 MHZ 1 MHZ
15 MHZ 1024 ??? 900 13.5 MHZ 1.5 MHZ
20 MHZ 2048 ??? 1200 18 MHZ 2 MHZ
21/38
OFDMA Pros. & Cons.
PROS.
CONS.
22/38
OFDMA Pros. & Cons.
Frequency
CP CP CP CP
CP CP CP CP
CP CP CP CP
Cyclic Prefix To combat the ISI and multipath delay issues the cyclic prefix is
Bit Period T(b)
used in the most ofdm systems , effectivaly a CP is a copy from
the back of the original symbol wich then placed in the front of
symbol to make a OFDM symbole Ts
T(g)
Symbol Period T(s)
23/38
SC-FDMA
24/38
SC-FDMA
The nominal bandwidth of the transmitted signal will be BW =M/N ·fs.
M the instantaneous bandwidth of the transmitted signal can be varied, allowing for flexible bandwidth
assignment.
Furthermore, by shifting the IDFT inputs to which the DFT outputs are mapped, the transmitted signal
can be shifted in the frequency domain
25/38
OFDMA VS SC-FDMA
26/38
Multiple antenna techniques
•Multi antenna systems is the use of multiple receive
and/or transmit antennas
27/38
MIMO technical Background
28/38
MIMO technical Background
29/38
MIMO Benefits
• MIMO has two main benefits either:
3) Beam Forming
30/38
MU-MIMO
The basic implementation of MIMO is generally referred to as SU-MIMO
(Single-User MIMO).
31/38
LTE Transmission Modes
32/38
HARQ Operations
ARQ Operations (Automatic Repeat reQuest)
33/38
HARQ Operations
The use of multiple hybrid ARQ processes means that the receiver decodes data blocks In a different order
from the one in which they were transmitted. In Figure, for example, block 3 is transmitted four times and is
only decoded some time after block 4. To deal with that problem, the receiver includes a re-ordering function
that accepts the decoded blocks and
returns them to their initial order.
34/38
Link Adaption (AMC*)
CQI
in *Adaptive Modulation and Coding
e d d a t a allocated
Modula t
c y ba s e d on CQI
frequen
35/38
Link Adaption (AMC)
CQI has values from 0 to 15 and Indicates the DL channel quality as experienced by
the UE
UE proposes eNB and optimum MCS so BLER is on target CQI not only considers time
domain but also frequency domain. CQI reference resource:
Time: Defined by a single sub-frame
Frequency: Defined by PRB corresponding to the band to which the derived CQI
value related
36/38
Link Adaption (AMC) - DL
Based on CQI Status, Appropriate MCS and TBS index is selected based on SINR value (3GPP Standard measurements)
After MCS and ITBS selection Transport Block - code word Throughput and PRB can be mapped and scheduled in DL
High MCS
corresponds to
high throughput
37/38
Link Adaption (AMC) - UL
The eNB measures the uplink channel quality and orders the UE to use a specific
modulation and coding scheme (MCS) based on this. Other parameters may also be taken
into account, such as UE power headroom, scheduled bandwidth, buffer content and acceptable
delay.
38/38
THANK YOU
OFFICE ADDRESS
UK Office
1A Rothesay Avenue, Wimbledon Chase
London SW20 8AX
+44 7901 572145
Egypt Office
Building-1 St. 210, Victoria Square, Maadi, Cairo
+201111113341
+20111 8003322
+201001150012
EMAIL
[email protected]
[email protected]
facebook.com/DIGIS2
LinkedIn.com/DIGIS2