Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
-Balamourougan V
Proprietary &
Confidential. Aricent
Group 2013
BASIC TERMINOLOGIES
Service Data Unit (SDU) and Protocol Data Unit (PDU) An SDU
is the basic unit of
data passed between layers and sub layers of the protocol stack. In the
transmit direction, each layer operates on an SDU received from the
layer above, transforming it into a PDU through segmentation,
concatenation, and by adding a header, as needed. That PDU then
becomes the SDU passed to the next layer below.
Proprietary & Confidential.
Aricent Group 2011
LTE DL CHANNELS
LTE UL CHANNELS
Types of RAP:
Contention based RAP
Non-contention based RAP
Contention based versus Contention free
10
12
Scenario:
Multiple UE's attempt to access the network:
1. So, the UEs initiates RACH with same Preamble
sequence, RA-RNTI
2. Therefore, the UEs willreceivethe same T-C-RNTI and
resource allocation from eNB
3. All UEs would send msg 3 (RRCconnectionRequest)
message through the same resource allocation to the
Network
4. Once, when msg3 is transmitted, two Timers are started:
a. T300 : Transmission ofRRCconnectionRequest
b. Contention Resolution Timer:broadcastedin SIB2. If
the UE doesn't receive msg4 (Contention Resolution
message) within this timer, then it go back to Step 1 i.e.
transmitting RAP. If there is a HARQ NACK for msg3
Proprietary
& Confidential.
(RRCconnectionRequest)
and
it has to be re-transmitted
13
Aricent Group 2011
then thisContention Resolution Timer will be re-started.
Timing Diagram
14
15
16
17
Further Reading
3GPP standards, http://www.3gpp.org/ftp/specs/latest
3GPP TS 36.321 version 9.6.0 Release 9
Thank you
19
Contd
MAC Layer
Provisioning for Traffic
Handling
-Mohamed zeeshan
Proprietary & Confidential.
Aricent Group 2011
20
Agenda
21
22
Proprietary &
Confidential. Aricent
Group 2013
23
MAC Sub-Headers
A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but
for the last subheader for fixed sized MAC control elements.
The last subheader in the MAC PDU and subheaders for fixed sized MAC
control elements consist solely of the four header fields R/R/E/LCID
A MAC PDU subheader corresponding to padding consists of the four
header fields R/R/E/LCID.
A maximum of one MAC PDU can be transmitted per TB per UE.
Padding occurs at the end of the MAC PDU, except when single-byte or
two-byte padding is required. Padding may have any value and the UE
shall ignore it. When padding is performed at the end of the MAC PDU,
zero or more padding bytes are allowed.
Proprietary &
Confidential. Aricent
Group 2013
24
MAC Sub-Headers
Proprietary &
Confidential. Aricent
Group 2013
25
-The E field is set to "1" to indicate another set of at least R/R/E/LCID fields.
-The E field is set to "0" to indicate that either a MAC SDU, a MAC control
element or padding starts at the next byte
LCID : The Logical Channel ID field identifies the logical channel instance of the
corresponding MAC SDU or the type of the corresponding MAC control element
or padding.
F : F means 'Format'. This defines the length of 'L' field. If F is '0', the length of
L field is 7 bit and if F is '1', the length of L field is 15 bit.
L : L means 'Length'. It shows the length of the MAC SDU..
Proprietary &
Confidential. Aricent
Group 2013
26
27
Proprietary &
Confidential. Aricent
Group 2013
28
Proprietary &
Confidential. Aricent
Group 2013
29
Timing Alignment (8bits): Sent to provide initial and periodic time synchronization
to the
UE for UL
Proprietary &
Confidential. Aricent
Group 2013
30
DRX operation
In normal operation, UE has to be awake all the time and
monitor PDCCH for every subframe meaning that it has to be
awake all the time since it doesn't know exactly when the
network will transmit the data for it.
DRX is a mechanism in which UE gets into sleep mode for a
certain period of time and wake up for another period of time.
The UE and network timings need to be synchronized.
If these two timing does not match, there can be a worst case
where UE is awake but Network does not transmit anything or
Network transmit something for the UE but UE is in sleep mode.
One solution would be that Network decide when to let UE
sleep and when to wake it up and inform the timing to the UE
using a RRC message.
We can also have implicit transition based on timers.
Proprietary &
Confidential. Aricent
Group 2013
31
DRX operation
During DRX, UE maintains a DRX cycle that is defined as a
number of subframes.
UE monitors PDCCH for on-duration subframes (1~200
subframes) and may turn off its receiver for rest of the DRX
cycle
eNB does not schedule transmissions during off-period of the
DRX cycle
Two DRX cycles: Short and Long
Proprietary &
Confidential. Aricent
Group 2013
32
4 step process
UE is supposed to give CQI(Channel Quality Indicator) to the eNB on a
periodic basis. UE measures the channel quality and reports the CQI
using PUCCH.
Scheduler at eNB dynamically allocated DL resources to the UE
(PDCCH)
When the DL scheduler makes resource allocation decisions the eNB
will use these resources to transmit traffic to those UEs. But all the
UEs reported CQI values and so all of them are expecting traffic from
the network. The eNB needs to ensure that the selected UEs
understand their allocation of resources and receive data. This is
done by sending the allocation info by eNB during the initial symbols
followed by the user traffic. Allocation info is sent on PDCCH.
The eNB transmits traffic to the selected UEs on the PDSCH( FEC,
Modulation , Mapping)
ACK/NACK: When a UE receives its transmission it will verify the
checksum of the packet and sends ACK/NACK on the PUCCH
Proprietary &
Confidential. Aricent
Group 2013
33
Proprietary &
Confidential. Aricent
Group 2013
34
35
Proprietary &
Confidential. Aricent
Group 2013
36
HARQ
Proprietary &
Confidential. Aricent
Group 2013
37
HARQ
LTE utilizes Incremental Redundancy HARQ with a
1/3 turbo encoder used for forward error correction.
The receiver only receives different punctured
versions of the same turbo-encoded data
The maximum number of retransmissions is limited
to 3 in DL and in UL the value is set by RRC in UE.
For FDD there shall be a max of 8 HARQ processes.
There is one entity at the UE which maintains a
number of parallel HARQ processes
Each HARQ process is associated with a HARQ ID.
HARQ process is stopped when
ACK is received
Proprietary
& number of re-transmissionhas reached
Max
Confidential. Aricent
38
Group 2013
HARQ - Downlink
The HARQ entity directs HARQ info and associated TBs received
on DL-SCH to the corresponding HARQ process in D/L.
UE does not know anything about HARQ process information for
DL data before it gets it. So Network send these information
(Process ID, Redundancy Version - RV) in PDCCH
It can use the 8 HARQ processes in any order (Asynchronous
Process).
AsynchronousHARQ increases signalling overhead because it
includes the HARQ process Identity
The frequency location and possibly the more detailed
transmission
format can be changed b/w transmissions
Proprietary &
Confidential. Aricent
Group 2013
39
HARQ - Uplink
It has to use the specific process in a specific
subframe (Synchronous Process). UE has to use the
same HARQ process number every 8 subframes.
Since UE have to use specific HARQ process ID at
specific subframe, the receiver (eNode B) knows
exactly which HARQ process comes when. And
eNodeB can also knows about RV because UL Grant
from eNodeB can specify RV using MCS field.
It can use the 8 HARQ processes synchronous order.
Proprietary &
Confidential. Aricent
Group 2013
40
HARQ - Timing
Timing relation b/w downlink data in
subframe n and uplink HARQ
acknowledgement in subframe n+4 for
FDD is as in the figure below
Upon reception of HARQ
acknowledgement, eNB can, if needed,
retransmit the downlink data in
subframe n+8.
Proprietary &
Confidential. Aricent
Group 2013
41
References
Proprietary &
Confidential. Aricent
Group 2013
42
Thank You.
-Janardhan R
-Subhashini R
44
AGENDA
45
46
LOGICAL CHANNEL
PRIORITIZATION
UE performs Logical Channel Prioritization
The
procedure which is applied when a new transmission
is performed
RRC controls the scheduling of uplink data for each
logical channel by
47
Contd..
For each TTI (Transmission Time Interval), Bj is
incremented by PBR * TTI value
Bj value can never exceed Bucket Size and
If Bj value > Bucket Size of the logical channel
j,
then Bj = Bucket Size
Bucket Size = PBR * BSD, where PBR and BSD
are configured by upper layers
UE allocates resources to the logical channel as
follows :
48
49
50
51
52
SCHEDULING
The Scheduling Request (SR) is used for
requesting
UL-SCH
resources
for
new
transmission
When an SR is triggered, it shall be considered
as pending until it is cancelled
If an SR is triggered and there is no other SR
pending, the UE shall set the SR_COUNTER to 0
53
Downlink Scheduling
The PDCCH carries the Cell Radio Network
Temporary Identifier (C-RNTI), which is the dynamic
UE identifier
The CRNTI indicates that an upcoming downlink
resource has been de-multiplexed by the MAC and
passed on to higher layers and is now scheduled
for this UE
Semi-persistent
scheduling
periodicity
is
configured by RRC. Whether scheduling is dynamic
or semi-persistent is indicated by using different
scrambling codes for the C-RNTI on PDCCH
Proprietary & Confidential.
Aricent Group 2013
54
55
56
Uplink Scheduling
57
58
59
60
Contd..
LCG ID : The Logical Channel Group ID field
identifies the group of logical channels for
which buffer status is being reported. Length
2 bits
Buffer Size : This field identifies the total
amount of data (in bytes) available across all
logical channels of a LCG after the MAC PDU has
been built. Length - 6 bits
The BSR formats are identified by MAC PDU sub
headers with LCID 11100(Truncated BSR),
11101(Short BSR) & 11110(Long BSR)
Proprietary & Confidential.
Aricent Group 2013
61
62
63
64
65
66
67
68
69
BSR types
Regular BSR
Periodic BSR
Padding BSR
Proprietary & Confidential.
Aricent Group 2013
70
Contd..
Triggers for BSR transmission
UE has UL data to transmit : When UE has some data
to transmit in RLC or PDCP entity for a certain LCG
UE got the UL Grant and the padding data is larger
than the size of BSR CE and the subheader
retxBSR-Timer is expired and UE has some data to
transmit
periodicBSR-Timer is expired
71
72
73
References
3GPP standards, http://www.3gpp.org/ftp/specs/latest
3GPP TS 36.321 version 9.6.0 Release 9
74
75