Transcript Telecom World

WCDMA RAN Protocols and Procedures
Chapter 5
RLC and MAC Protocols
1
Objectives of Chapter 5, RLC and MAC Protocols
After this chapter the participants will be able to:
1.
Explain the RLC functions.
2.
List the different modes of RLC (transparent, unacknowledged and
acknowledged mode) and explain the structure of the Protocol Data Unit
(PDU) involved in these cases.
3.
Explain the MAC functions.
4.
Explain the MAC architecture, its entities and their usage for the mapping of
transport channels.
5.
List the contents of the MAC Protocol Data Unit (PDU).
6.
Explain the Transport Format selection and the relation between
Combinations (TFC) and Sets (TFCS).
7.
Explain Channel Type Switching.
8.
Explain the structure and mapping of physical channels.
2
INTRODUCTION
3
Uu interface protocol architecture (figure 5-1) (1)
Control
UuS boundary
L3/RRC
PDCP
PDCP
control
control
control
control
RRC
RLC
RLC
L2/PDCP
RLC
RLC
RLC
RLC
BMC
L2/BMC
RLC
L2/RLC
RLC
Logical
Channels
MAC
L2/MAC
Transport
Channels
PHY
L1
Physical
Channels
4
Uu interface protocol architecture (figure 5-1) (2)
• The control interfaces between the RRC and all the lower layer protocols are used by the
RRC layer :
* configure characteristics of the lower layer protocol entities, including parameters for
the physical, transport and logical channels.
* to command the lower layers to report measurement results and errors to the RRC.
5
RADIO LINK CONTROL (RLC) PROTOCOL
-- INTRODUCTION--
6
INTRODUCTION
• The RLC work in transparent, unacknowledged and acknowledged mode.
• in the control plane, the service provided by the RLC layer is called Signalling Radio
Bearer (SRB).
• In the user plane, the service provided by the RLC layer is called a Radio Bearer (RB)
7
Protocol Data Unit (PDU) and Service Data Unit (SDU) (1)
(figure 5-2)
PDCP
Uu interface
PDCP PDU
PDCP PDU
RLC PCI
RLC SDU
RLC PDU RLC PCI
payload
RLC SDU
RLC
MAC
RLC PDU RLC PCI
MAC SDU
SDU : Service Data Unit
PDU : Protocol Data Unit
PCI: Protocol Control Information
payload
MAC SDU
Processing done for the SDUs at layer N can be e.g.:
-Add overhead (e.g. sequence number, ch type info)
-Segmentation, etc.
8
Protocol Data Unit (PDU) and Service Data Unit (SDU) (2)
• the Radio Link Control (RLC) layer receives a PDCP PDU.
• In the RLC layer, the data will be known as an RLC SDU
• After the header is added, the data is called an RLC PDU
• In the Medium Access Layer (MAC) this is now a MAC SDU.
• The MAC layer may add a MAC header and send MAC PDUs to the physical layer.
9
RADIO LINK CONTROL (RLC) PROTOCOL
-- RLC FUNCTIONS --
10
RLC Protocol Entity (1)
 RLC Services
RRC
 RLC Functions
–
–
–
–
–
–
–
–
–
–
PDCP
PDCP
control
control
control
L2 connection establishment and release
Transparent data transfer
Unacknowledged data transfer
Acknowledged data transfer
control
–
–
–
–
UuS boundary
L3
Control
RLC
RLC
L2/PDCP
RLC
RLC
RLC
RLC
BMC
L2/BMC
RLC
L2/RLC
RLC
Logical
Channels
Segmentation and re-assembly
Concatenation
Padding
Transfer of user data in transparent,
unacknowledged and acknowledged mode.
Error correction (ARQ)
In-sequence delivery
Duplicate detection
Flow control
Sequence number check
Ciphering
MAC
L2/MAC
Transport
Channels
PHY
11
L1
RLC Protocol Entity (2)
1. Segmentation and reassembly
• Performs segmentation/reassembly of variable length higher layer PDUs into/from
smaller RLC Payload Units (PUs).
2. Concatenation
• If the contents of an RLC SDU do not fill an integral number of RLC PDUs, the first
segment of the next RLC SDU may be put into the RLC PDU in concatenation with the
last segment of the previous RLC SDU
3. Padding
• When concatenation is not applicable and the remaining data to be transmitted does
not fill an entire RLC SDU of given size, the remainder of the data field is filled with
padding bits.
4. Transfer of user data
• RLC supports acknowledged, unacknowledged and transparent data transfer.
Transfer of user data is controlled by QoS setting.
12
RLC Protocol Entity (3)
13
RLC Protocol Entity (4)
14
RADIO LINK CONTROL (RLC) PROTOCOL
-- RLC MODES --
15
16
RLC Layer Architecture (figure 5-3)
TM
Tx
Rx
UM
AM
Rx
Tx
Rx
Tx
Rx
Tx
Tx/Rx
Tx/Rx
• In Transparent and Unacknowledged Mode the RLC entities are unidirectional
• In Acknowledged Mode, it is bi-directional
17
RLC Transparent Mode PDU
(figure 5-4)
 The RLC TM PDU introduces no overhead
 Protocol functions may still be applied e.g. segmentation
Data
 TM is used for voice and circuit switched data where delay should
be as low as possible. It is also used for the SRB for BCCH and
PCCH.
18
RLC Transparent Mode Entities
(figure 5-5)
UE/UTRAN
UTRAN/UE
Radio Interface (Uu)
TM-SAP
TM-SAP
Transmission
buffer
Transmitting
TM- RLC
entity
Receiving
TM- RLC
entity
Reassembly
Reception
buffer
Segmentation
CCCH/DCCH/DTCH/SHCCH – UTRAN
BCCH/PCCH/DCCH/DTCH – UE
CCCH/DCCH/DTCH/SHCCH – UE
BCCH/PCCH/DCCH/DTCH – UTRAN
19
RLC Unacknowledged Mode PDU (figure 5-6)
 Sequence number.
 E: Extension bit. Indicates whether next octet will be a length
indicator and E bit.
 Data shall be a multiple of 8 bits.
 If the transmitted data does not fill an entire PDU the remainder of
the data field is filled with padding bits.
E Oct1
E (Optional)
Ciphering Unit
Sequence Number
Length Indicator
.
.
.
Length Indicator
E
(Optional)
.
.
.
(Optional)
Oct N
Data
PAD
• no retransmission protocol is used and data delivery is not guaranteed. Received erroneous data is
either marked or discarded depending on the configuration.
20
RLC Fields (table 5-1)
Extension bit (E)
Length: 1bit.
This bit indicates if the next octet will be a "Length Indicator" and E bit.
Bit
0
1
Description
The next field is data, piggybacked STATUS
PDU or padding
The next field is Length Indicator and E bit
length indicators
• Length Indicators are also used to define whether Padding is included in the UMD PDU.
• It may be 7 bits (if the largest PDU size is ≤ 125 octets) or 15 bits long (otherwise).
• some length indicator sequences are predefined
21
Predefined length indicators. (table 5-2)
Length: 7 bits
Bit
0000000
1111100
1111101
1111110
1111111
Description
The previous RLC PDU was exactly filled with the last segment of an RLC SDU
and there is no "Length Indicator" that indicates the end of the RLC SDU in the
previous RLC PDU.
UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC
SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this
version of the protocol).
Reserved (PDUs with this coding will be discarded by this version of the
protocol).
AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU.
UMD PDU: Reserved (PDUs with this coding will be discarded by this version
of the protocol).
The rest of the RLC PDU is padding. The padding length can be zero.
Length: 15bits
Bit
000000000000000
111111111111011
111111111111100
111111111111101
111111111111110
111111111111111
Description
The previous RLC PDU was exactly filled with the last segment of an
RLC SDU and there is no "Length Indicator" that indicates the end of
the RLC SDU in the previous RLC PDU.
The last segment of an RLC SDU was one octet short of exactly filling
the previous RLC PDU and there is no "Length Indicator" that indicates
the end of the RLC SDU in the previous RLC PDU. The remaining one
octet in the previous RLC PDU is ignored.
UMD PDU: The first data octet in this RLC PDU is the first octet of an
RLC SDU. AMD PDU: Reserved (PDUs with this coding will be
discarded by this version of the protocol).
Reserved (PDUs with this coding will be discarded by this version of the
protocol).
AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS
PDU. UMD PDU: Reserved (PDUs with this coding will be discarded by
this version of the protocol).
The rest of the RLC PDU is padding. The padding length can be zero.
22
RLC Unacknowledged Mode Entities (figure 5-7)
 Segmentation &
Concatenation
 Padding
 Ciphering
 Sequence number
check
 Transfer of user data
UE/UTRAN
Radio Interface (Uu)
UTRAN/UE
UM -SAP
UM -SAP
Transmission
buffer
Transmittin
g
UM RLC
entity
Segmentation &
Concatenation
Reassembly
Remove RLC
header
Reception
buffer
Add RLC header
Deciphering
Ciphering
DCCH/DTCH
– UE
CCCH/SHCCH/DCCH/DTCH/CTCH
Receiving
UM RLC
enti ty
– UTRAN
DCCH/DTCH
– UTRAN
CCCH/SHCCH/DCCH/DTCH/CTCH
– UE
• Example for UM RLC: The cell broadcast service is an example of a user service that
could utilise UM as well as the RRC Connection Setup/Reject message sent on
CCCH/FACH.
23
RLC Acknowledged Mode PDU (figure 5-8)
 D/C: Data/Control PDU indicator bit
 P: Poll bit. To be used to request for
a Status PDU.
 HE: Header Extension bits. Indicates if the
next octet will be data or a length indicator
and E bit.
 E: Extension bit. Indicates whether next octet
will be a length indicator and E bit.
* for packet-type services such as Internet
browsing and email (DTCH).
* also used for signalling, when it is
important that the signalling is received
Ciphering Unit
• Example for AM RLC:
correctly but delay is not the most
D/C
Sequence Number
Sequence Number
P
HE
Length Indicator
E
Oct1
Oct2
Oct3 (Optional)
.
.
.
Length Indicator
E
(Optional)
Data
PAD or a piggybacked STATUS PDU
OctN
important.
24
RLC fields (table 5-3 and 5-4)
D/C field
Length: 1bit.
The D/C field indicates the type of an AM PDU. It can be either data or control PDU.
Bit
0
1
Description
Control PDU
Data PDU
Sequence Number (SN)
This field indicates the "Sequence Number" of the RLC PDU, encoded in binary.
PDU type
AMD PDU
UMD PDU
Length
12 bits
7 bits
Notes
Used for retransmission and reassembly
Used for reassembly
NOTE: There are some predefined sequence numbers
25
RLC Fields continued (table 5-5 and 5-6)
Polling bit (P)
Length: 1bit.
This field is used to request a status report (one or several STATUS PDUs) from the Receiver.
Bit
0
1
Description
Status report not requested
Request a status report
Header Extension Type (HE)
Length: 2 bits.
This two-bit field indicates if the next octet is data or a "Length Indicator" and E bit.
Value
00
01
10-11
Description
The succeeding octet contains data
The succeeding octet contains a length indicator and E
bit
Reserved (PDUs with this coding will be discarded by
this version of the protocol).
26
RLC fields continued (table 5-7)
PDU Type
Length: 3 bit.
The PDU type field indicates the Control PDU type.
Bit
000
001
010
011-111
PDU Type
STATUS
RESET
RESET ACK
Reserved
(PDUs with this
coding will be
discarded by
this version of
the protocol).
• The Status PDU : is used for retransmission. The receiver transmits status reports to the
sender in order to inform the sender about which AMD PDUs have been received and not
received.
27
RLC PDU Formats- Status PDU (figure 5-9)
D/C PDU type
SUFI 1
Octet 1
SUFI1
Octet 2
SUFIK
Octet N
 D/C: Data/control PDU indicator.
 SUFI: Super Field. This field can be either a list, bitmap, relative bitmap,
Acknowledgment field etc. Which type of field it is is indicated within the SUFI.
28
Super Fields (SUFI)
 Acknowledgement: Gives the SN up to which all PDUs are
received correctly
 List: Lists the SNs of the PDUs which were not received correctly
 Bitmap: Indicates the erroneous PDUs in a bitmap
 Relative List: Optimised method of listing erroneous PDUs
 Move Receive Window: Moves the receiving window when SDU
discard is performed
 No More Data: Indicates the end of a Status Report
 Window Size: This field is for flow control purposes
29
RLC Acknowledged Mode PDU (figure 5-10)
UE/UTRAN
AM-SAP
AM RLC entity
Segmentation/Concatenation
RLC Control Unit
Add RLC header
Piggybacked status
Optional
Retransmission
buffer &
management
Reassembly
Transmission
buffer
Received
acknowledgements
MUX
Remove RLC header & Extract
Piggybacked information
Reception buffer
& Retransmission
management
Acknowledgements
Deciphering
Set fields in PDU Header (e.g. set poll
bits) & piggybacked STATUS PDU
Ciphering(only for AMD PDU)
Demux/Routing
Receiving side
Transmitting side
DCCH/
DTCH**
DCCH/
DTCH*
DCCH/
DTCH**
30
DCCH/
DTCH**
DCCH/
DTCH*
DCCH/
DTCH**
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---INTRODUCTION---
31
• The MAC layer offers services to upper layers in the form of :
* data transfer on logical channels
* reallocation of radio resources
* MAC parameters :
reconfiguration of MAC functions such as change of identity of UE, change of
transport format (combination) sets, change of transport channel type.
* reporting of measurements:
such as traffic volume and quality indication
32
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---MAC FUNCTIONS---
33
UuS boundary
L3
MAC Protocol Entity (1)
Control
PDCP
PDCP
control
control
control
control
RRC
L2/PDCP
 MAC Services
– Data Transfer
– Reallocation of resources
– Measurement reporting
RLC
RLC
RLC
RLC
RLC
RLC
BMC
L2/BMC
RLC
L2/RLC
RLC
Logical
Channels
MAC
L2/MAC
Transport
Channels
PHY
 MAC Functions
– Mapping between logical channels and transport channels
– Selection of appropriate Transport Format for each Transport Channel
depending on the instantaneous source rate
– UE identification on common transport channels
– Multiplexing of logical channels (common and dedicated)
– Traffic volume measurement
– Transport Channel Type switching
– Ciphering for transparent mode RLC
34
L1
MAC Protocol Entity (2)
 MAC Functions
– Mapping between logical channels and transport channels
– Selection of appropriate Transport Format for each Transport Channel
depending on the instantaneous source rate
– Priority handling between data flows of one UE
achieved by selecting “high bit rate” and “low bit rate” Transport Formats
for different data flows.
– UE identification on common transport channels
the identification of the UE (Cell Radio Network Temporary Identity (CRNTI) or UTRAN Radio Network Temporary Identity (U-RNTI)) is included in
the MAC header.
35
MAC Protocol Entity (3)
– Multiplexing of logical channels (common and dedicated)
– Traffic volume measurement
* Measure on the amount of data in the RLC transmission buffer
* MAC compares the amount of data corresponding to a transport channel with
the threshold set by RRC. If the amount of data is too high or too low, MAC
sends a measurement report on traffic volume status to RRC.
* use these reports for triggering reconfiguration of Radio Bearers and/or
Transport Channels.
– Transport Channel Type switching
– Ciphering for transparent mode RLC
36
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---ARCHITECTURE---
37
Logical Channels
 Provided by L2/MAC sublayer to higher layers
 Defined by which type of information is transported
 Control Channels
–
–
–
–
Broadcast Control Channel (BCCH, DL)
Paging Control Channel (PCCH, DL)
Common Control Channel (CCCH, DL & UL)
Dedicated Control Channel (DCCH, DL & UL)
 Traffic Channels
– Dedicated Traffic Channel (DTCH, DL & UL)
– Common Traffic Channel (CTCH, DL)
38
Transport Channels
 Services provided by the physical layer (layer 1) to the
MAC layer
 Defined by “how and with what characteristics” the data is
transported
 Common Transport Channels
–
–
–
–
–
–
Broadcast Channel (BCH) (DL)
Paging Channel (PCH) (DL)
Random Access Channel (RACH) (UL)
Forward Access Channel (FACH) (DL)
Downlink Shared Channel (DSCH) (DL)
Common Packet Channel (CPCH) (UL)
Same channel used by several
users
No UE identification provided by
L1, in-band signaling of UE
identity
For exclusive use of one user
UE inherently identified by the
physical channel
 Dedicated Transport Channels
– Dedicated Channel (DCH) (UL & DL)
39
MAC architecture (figure 5-11)
BCCH MAC Control
PCCH BCCH CCCH
CTCH SHCCH MAC Control
TDD only
MAC Control DCCH DTCH DTCH
MAC-d
Serving RNC
per UE
MAC-b
Transparent
RBS, per cell
BCH
MAC-c/sh
Controlling RNC, per cell
PCH FACH FACH
RACH CPCH USCH USCH DSCH DSCH
FDD only
TDD only TDD only
40
Iur or local
DCH
DCH
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---MAC PDU AND FLOW---
41
PDU in MAC
• The MAC PDU : consists of an optional MAC header and a MAC Service Data Unit (MAC
SDU).
• Transport Block: Each RLC PDU (e.g. TMD, UMD or AMD) is mapped onto one and only one
Transport Block.
• Transport Block Set(TBS): In the UE for the uplink, all MAC PDUs delivered to the physical
layer within one Time Transmission Interval (TTI) are defined as Transport Block Set (TBS).
It consists of one or several Transport Blocks, each containing one MAC PDU.
42
MAC DATA PDU
RLC PDU
(figure 5-12)
MAC header
TCTF
UE-Id
type
UE-Id
MAC SDU
C/T
MAC SDU
Ciphering Unit
 Target Channel Type Field (TCTF) identifies the type of logical channel (CCCH,
BCCH, CTCH, DTCH/DCCH) on RACH/FACH.
 UE-Id provides an identifier of the UE on common transport channels.
 UE-Id type is needed to ensure correct coding of the UE-Id field.
 C/T identifies the logical channel number (in case of MAC multiplexing of
several DTCH and DCCH).
43
Target Channel Type Field (TCTF) (table 5-1 and 5-2)
 Provides identification of the logical channel class on FACH or
RACH
TCTF
Designation
00
BCCH
01000000
CCCH
0100000101111111
Reserved
(PDUs with this coding will be discarded
by this version of the protocol)
10000000
CTCH
1000000110111111
Reserved
(PDUs with this coding will be discarded
by this version of the protocol)
11
DCCH or DTCH
over FACH
44
TCTF
Designation
00
CCCH
01
DCCH or DTCH
over RACH
10-11
Reserved
(PDUs with this coding
will be discarded by this
version of the protocol)
C/T Field (table 5-3)
 Provides identification of the logical channel instance when
multiple channels are carried on the same transport channel.
C/T
field
Designation
0000
Logical channel 1
0001
Logical channel 2
...
...
1110
Logical channel 15
1111
Reserved
(PDUs with this coding will be
discarded by this version of
the protocol)
45
UE Id Field (table 5-4)
 Provides an identifier of the UE on common transport channels.
UE Id type
Length of UE Id field
U-RNTI
32 bits
C-RNTI
16 bits
46
UE-Id Type Field (table 5-5)
 Needed to ensure correct coding of the UE-Id field
UE-Id Type field 2
bits
UE-Id Type
00
U-RNTI
01
C-RNTI
10
Reserved
(PDUs with this coding
will be discarded by this
version of the protocol)
11
Reserved
(PDUs with this coding
will be discarded by this
version of the protocol)
47
WCDMA RAN side MAC architecture / MAC-d details (1)
DCCH DTCH DTCH
MAC-Control
UE
Transport Channel Type Switching
C/T MUX
/ Priority
setting
to MAC-c/sh
Flow Control
MAC–c/sh /
MAC-d
Deciphering
C/T
MUX
MAC-d
DL scheduling/
priority handling
Ciphering
DCH
DCH
48
WCDMA RAN side MAC architecture / MAC-d details (2)
• Transport Channel Type Switching : If requested by RRC, MAC switches the mapping
of one designated logical channel between common and dedicated transport channels.
• C/T MUX : a C/T field is added indicating the logical channel instance where the data
originates. This is always needed for common transport channels, such as the FACH, but
for dedicated it is only needed when several logical channels are multiplexed into C/T
MUX.
• Priority setting function : is responsible for priority setting on data received from
DCCH/DTCH.
• flow control function : exists between MAC-c/sh and MAC-d to limit buffering in the
MAC-c/sh entity.
• Ciphering/deciphering : in MAC-d is only performed for transparent mode data.
49
WCDMA RAN side MAC architecture / MAC-c/sh details (1)
PCCH
BCCH
SHCCH
CCCH
MAC – Control
CTCH
(TDD only)
MAC-c/sh
Flow Control
MAC -c/sh / MAC -d
TCTF MUX / UE Id MUX
Scheduling / Priority Hand ling/ Demux
TFC selection
TFC selection
PCH
FACH
FACH
DL: code
allocation
DSCH
DSCH
USCH
USCH
TDD only
TDD only
RACH
50
CPCH
(FDD only )
to MAC –d
WCDMA RAN side MAC architecture / MAC-c/sh details (2)
• UE id MUX: After receiving the data from MAC-d, the MAC-c/sh entity first adds the UE
identification type, which is the actual UE identification (CRNTI or U-RNTI).
• the scheduling/priority handling function : is to decide the exact timing when the PDU is
passed to layer 1 via the FACH transport channel with an indication of what transport
format used.
• The Transport Format Combination (TFC) selection : is done in the downlink for FACH,
PCH and DSCH.
• DL code allocation : is only used to indicate the code if DSCH is used.
51
MAC Model/WCDMA RAN side (figure 5-13 and figure 5-14 connected)
MAC-Control
PCCH BCCH CCCH CTCH
DCCH DTCH DTCH
MAC-c/sh
Transport Channel Type Switching
Flow Control
MAC-c/sh/MAC-d
C/T MUX Deciphering
Priority
setting C/T MUX
TCTF MUX / UE Id MUX
Scheduling / Priority Handling/ Demux
DL scheduling/
priority handling
Ciphering
TFC selection
PCH
FACH
FACH
RACH
DCH DCH
52
MAC-d
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---TRANSPORT FORMAT---
53
• The Transport Format (TF) and Transport Format Set (TFS) : describes the data
transfer format offered by L1 to MAC (and vice versa) and is configured by RRC for a
specific transport channel. Each transport channel is configured with one or more Transport
Formats (TF). This is referred to as the Transport Format Set (TFS)
* The maximum number of TFs per transport channel is 32 (numbered 0-31).
* Each TF corresponds to a certain number of equal size transport blocks, i.e. Transport
Block Set (TBS), which may be transmitted on the transport channel within the same
interval.
* The length of the interval is defined by the Transmission Time Interval (TTI), which is a
fixed periodicity of transport blocks and can have a length of 10, 20, 40 and 80 ms.
54
Transport Format Set (TFS) (figure 5-15)
Only the dynamic attributes differ
between the TFs within the TFS
TF1
Increasing
bit rate
TF2
TF3
55
TFS
Transport format (figure 5-16)
 Describes instantaneous characteristics of a transport channel and
the data transfer format offered by L1.
 Semi-static part
– Transmission Time Interval (TTI)
– Channel-coding scheme
– Reconfiguration by RRC is needed.
 Dynamic part
– Number of transport blocks per TTI
– Number of bits per transport block
Transport Block
N
Transport Block
Transport Block
L bits
Transport Block
Transport Block
Transport Block
TTI
56
Transport Channel Coding (figure 5-17)
Transport Channel
 CRC (Cyclic Redundancy Check)
–
–
Calculated for and added to each transport block
CRC length : 0/8/12/16/24 bits
Add CRC
 FEC (Forward Error Correction)
–
–
Convolution coding (R=1/2, R=1/3)
Turbo coding (R=1/3)
Channel coding
 Channel Interleaving
–
Block interleaving over one TTI
Interleaving
Coded Transport Channel
57
Examples of transport channel structures, simple
variable rate speech and packet data (figure 5-18)
Simple variable-rate speech
 TTI = 20 ms
 Convolutional coding
 One transport block per TTI (one speech frame)
 Variable-length transport blocks
Rate = R
Rate = R/4
Rate = R/2
TTI (typically 20 ms)
Packet data
 Turbo coding
 Fixed-length transport blocks
 Variable number of transport block per TTI
One ”packet”
One ”packet”
One ”packet”
One ”packet”
One ”packet”
One ”packet”
TTI
58
Characterization of Transport Format
59
Multiple transport channels (figure 5-19)
 A connection typically consists of multiple transport channels
in each direction
UTRAN
DL TrCh #1
DL TrCh #M
UL TrCh #1
UL TrCh #N
UE
 One set of transport formats per transport channel
 Transport Format Combination (TFC):
– The instantaneous combination of transport formats for all
transport channels to (from) one UE
– Signaled over L1 as Transport Format Combination Indicator (TFCI)
60
Transport Format Set (TFC) (figure 5-20)
A combination of currently valid Transport Formats at a given point of
time containing one Transport Format for each transport channel.
Transport
channel 1
Transport
channel 2
TF1
TF1
Transport
channel 3
TF1
TFC1
TF2
TF2
TF2
TF3
TF3
TF3
61
Transport Format Set (TFCS) (figure 5-21)
 TFCS is the set of TFCs that has been configured (by RRC)
 MAC selects a TFC out of the TFCS
 Current TFC is indicated by the Transport Format Combination Indicator
(TFCI) in each physical frame every 10 ms
Transport
channel 1
Transport
channel 2
TF1
TF1
Transport
channel 3
TF1
TFC1
TFC2
TF2
TF2
TFCS
TF2
TFC3
TF3
TF3
TF3
62
TFC4
Summary of Data Exchange through transport
channels
 Transport block: the basic unit exchanged between L1 and MAC
 Transport block set: a set of transport blocks which are exchanged between L1 and MAC
at the same time instance on the same TrCH
 The Transmission Time Interval (TTI) and the error protection scheme to apply are semistatic parameters for the TrCH while the number of transport blocks and their size are
dynamic ones
 Transport format: a defined format offered by L1 for the delivery of a Transport Block Set
during a TTI
 Transport format set: a set of Transport Formats associated to a Transport Channel
 Transport Format Combination: a combination of transport formats submitted
simultaneously to L1, containing one Transport Format for each transport channel.
 Transport Format Combination Set: a set of transport format combinations
 The Transport Format Combination Indicator (TFCI): on L1 indicates the currently valid
TFC.
63
MEDIUM ACCESS CONTROL (MAC) PROTOCOL
---CHANNEL SWITCHING---
64
• The purpose of Channel Switching : is to optimize the use of the radio
resources, by dynamically changing the resources allocated to the best-effort users. When
there are plenty of resources available, the best-effort user receives high bit rates but when
the system is heavily loaded and there are not many resources left,
65
5. SHO can
initiate a
switch if it
fails to add a
RL
Soft
Congestion
Channel Switching
Cell_DCH 64/384
1. CELL_FACH to CELL_DCH: Bufferbased
Cell_DCH 64/128
4. Coverage
triggered downswitch
3. Upswitch
2. CELL_DCH to CELL_FACH: Throughput
based on
bandwidth
Cell_DCH 64/64
3. Upswitch: Bandwidth
Cell_FACH
4. Downswitch: DL Code Power Based
5. Downswitch: Handover Based
6. Downswitch: CELL_FACH to Idle due to inactivity
2. Dedicated
1. Common
to common
based on
throughput
6. No
to Dedicated
based on
buffer size
activity
Idle Mode
7. Multi-RAB Upswitch: Bufferbased
8. Multi-RAB Downswitch: Throughput based
Cell_DCH
Speech + PS 64/64
8. UL & DL
throughput =
0 for a
certain time
Cell_DCH
Speech + PS 0/0
Copyright © Ericsson Education. All rights reserved
66
7. UL or
DL buffer
size above
a threshold
1. Switch from Cell_FACH to Cell_DCH state
• based on the buffer load.
• Downlink buffer load measurements in the S-RNC , uplink buffer load
measurement by the UE in the MAC layer.
• in the Idle State or Cell_FACH the UE will read the System Information and
configure its measurements.
• For the DCH state, measurements are configured by a “Measurement
Control” message.
• In the UL case the UE sends a “Measurement Report” to the RNC when the
buffer size is reached. In the DL case, the RNC handles the switch internally.
67
2. switch from Cell_DCH to Cell_FACH
• Throughput based
• triggers the MAC layer to report to RRC and send a “Measurement Report” to the
RNC for low throughput in UE.
• If both the throughput in the UL and the DL is below the set values, a switch from
Cell_DCH to Cell_FACH will be performed via Radio Bearer Reconfiguration
procedure.
3. Up Switch between the Radio Bearers for the Cell_DCH state
• based on bandwidth need.
• The supported bit rates are 64/64, 64/128 and 64/384 kbps.
• When the throughput becomes close to the maximum user bandwidth (64 or 128
kbps) the procedure is triggered.
• In the UL case, the UE sends a “Measurement Report” and in the DL case it is
handled in the RNC internally.
68
4. Down Switch between the Radio Bearers for the Cell_DCH state
• performed due to coverage, i.e. due to DL power.
• In this case the congestion control triggers it based on measurements via NBAP
(from RBS to RNC).
5. Other channel switching type is not indicated here !!!!
69
Channel switching (UL) (figure 5-22)
User 1
User 2
Random-Access
Request
Random-Access
Request
Random-Access Channel
Switch to
dedicated
TTime-out
Packet
Packet
Switch to
common
Packet
Dedicated Channel
Release dedicated
channel
70
Channel Switching from dedicated to common (DCCH
and DTCH) before switching (figure 5-24)
 No MAC header is needed for the
DTCH.
 Multiplexing of logical channels
(DCCHs used for SRBs, C/T MUX)
 Mapped on DCH transport
channels
DCCHs
DTCH
MAC-d
Channel switching
C/T MUX
Ciphering
DCCHs
MAC header
C/T
DTCH
TFC Selection
RLC PDU
RLC PDU
MAC SDU
MAC SDU
MAC SDU
MAC SDU
DCH
DCH
Physical layer L1
Ciphering Unit
Ciphering Unit
71
Channel Switching from dedicated to common (DCCH
and DTCH) after switching (figure 5-25)
Switching is transparent for the logical channels
DTCH and DCCH mapped to RACH/FACH
MAC header fields to distinguish logical channels and UEs
DCCH
CCCH CTCH BCCH
MAC-c
UE ID
DTCH
MAC-d
Channel switching
C/T MUX
RLC PDU
TCTF MUX
MAC header
FACH
TCTF UE-Id UE-Id C/T
type
RACH
MAC SDU
MAC SDU
Physical layer, L1
Ciphering Unit
72
CIPHERING
73
• The protection of the user data and some of the signaling information is done by both
integrity protection, executed by RRC layer and ciphering, performed either in RLC or in
the MAC layer according to the following rules:
* If a radio bearer is using a non-transparent RLC mode (AM or UM), ciphering is
performed in the RLC sub layer.
* If a radio bearer is using the transparent RLC mode, ciphering is performed in the
MAC sub layer (MAC-d entity).
>> If ciphering is used it is between S-RNC and UE <<
74
Ciphering of user and signaling data transmitted over
the radio access link (figure 5-26) (1)
/
SRNC
DIRECTION
COUNT-C
BEARER
CK
DIRECTION
COUNT-C
BEARER
LENGTH
f8
CK
KEYSTREAM
PLAIN TEXT
BLOCK
/
SRNC
LENGTH
f8
KEYSTREAM
PLAIN TEXT
BLOCK
CIPHERTEXT
BLOCK
Sender
UE or SRNC
Receiver
SRNC or UE
75
Ciphering of user and signaling data transmitted over
the radio access link (figure 5-26) (2)
• Procedure for ciphering:
* The input parameters to the algorithm : the ciphering key, CK, a time-dependent input,
COUNT-C, the bearer identity, BEARER, the direction of transmission, DIRECTION,
and the length of the key stream required, LENGTH.
* Based on these input parameters the algorithm generates the output keystream block,
KEYSTREAM, that is used to encrypt the input plaintext block, PLAINTEXT, to
produce the output ciphertext block, CIPHERTEXT.
76
Input Parameters to the Cipher Algorithm (1)
• COUNT-C : ciphering sequence number
• CK, Ciphering Key: The CK is established during the Authentication procedure
using cipher key derivation function f3 available in the USIM and in the HLR/AUC
• BEARER : There is one BEARER parameter per radio bearer associated with the same
user . The radiobearer identifier is input to avoid that for different keystream an identical
set of input parameter value is used.
• DIRECTION : The value of the DIRECTION is 0 for UL messages and 1 for DL.
77
Input Parameters to the Cipher Algorithm(2)
• LENGTH : The parameter determines the length of the required keystream block .
• Ciphering key selection: There is one CK for CS radio bearer, CKCS, connections
and one CK for PS radio bearer, CKPS, connections.
78
PHYSICAL CHANNELS
79
Physical channels
 The final Layer 1 bit stream to be carried over the air
– Multiple multiplexed coded transport channels (CCTrCH)
– Layer 1 control information
 Pilot bits
 Transmit Power Control (TPC) commands and other
Feedback Information (FBI)
 Transport Format Combination Indicator (TFCI)
 Mapped to combination of
– Carrier frequency
– Code (channelization/scrambling code pair)
– Relative phase (UL only): On either the I branch or the Q branch of a QPSK
signal (uplink only).
80
Physical-layer overview (figure 5-27)
Transport channels
Channel
coding
Channel
coding
Multiplexing
Transport-channel
processing
Mapping to physical channels
Physical channels
Spreading
Spreading
3.84 Mcps
Modulation
Modulation
5 MHz
81
Physical-layer
procedures
and
measurements
RRC Connection Establishment (figure 5-28)
WCDMA RAN
Idle
Mode
”RRC Connection Request” CCCH/RACH
”RRC Connection Setup” CCCH/FACH
WCDMA RAN
Connected
Mode
”RRC Connection Setup Complete” DCCH/DCH
82
Physical Random Access Channel (figure 5-29)
RACH Message Data Slot (0.666 mSec)
Random Access Message (10, 20, 40, or 80 bits per slot)
I
RACH Message Control Slot (0.666 mSec)
Pilot (8 bits)
1
2
3
4
5
6
7
TFCI (2 bits)
8
9
10 11 12 13 14 15
1 Frame = 15 slots = 10 mSec
83
Q
RACH carrying RRC Connection request (figure 5-30)
166
8.4 Kbps => 166 bits in 20msec
166
Transparent Mode => no RLC header
2 bit MAC header
166
MAC layer
CRC 16
168
8 tail bits
184
192
Rate 1/2 CC
384
1st Interleaving
Rate Matching
300
2nd Interleaving
Slot segmentation
20
20
RACH Message part 30ksps SF 128
PILOT
TFCI
Control part
8
84
2
I
branch
Q
Secondary Common Control Physical Channel (figure 5-31)
Carries the Forward Access Channel (FACH) and Paging Channel (PCH)
Spreading Factor = 256 to 4
1 Slot = 0.666 mSec = 2560 chips = 20 * 2k data bits; k = [0..6]
0, 2, or 8 bits
20 to 1256 bits
TFCI or DTX
1
2
Data
3
4
5
6
7
8
Pilot
9
10 11 12 13 14 15
1 Frame = 15 slots = 10 mSec
85
0, 8, or 16 bits
FACH carrying RRC Connection setup (figure 5-32)
152
152
152
152
160
Max rate 3040 bps => 10msec = 304 bits = 2X152
Unacknowledged Mode (UM) => 8 bit RLC
160
8 bit MAC
168
CRC 16
MAC layer
168
184
8 tail bits
184
376
Rate 1/2 CC
752
1st Interleaving
Rate Matching
1080
2nd Interleaving
72
8
Slot segmentation
L1 (8 bit TFCI)
S-CCPCH 60ksps => SF = 64
86
72
8
Uplink DPDCH/DPCCH
(figure 5-33)
Dedicated Physical Data Channel (DPDCH) Slot (0.666 mSec)
Coded Data, 10 x 2k bits, k=0…6
I
(10 to 640 bits)
Dedicated Physical Control Channel (DPCCH) Slot (0.666 mSec)
Pilot
1
2
3
4
5
6
TFC
I
7
8
9
FBI
TPC
Q
10 11 12 13 14 15
1 Frame = 15 slots = 10 mSec
DPCCH: 15 kb/sec data rate, 10 total bits per DPCCH slot
PILOT: Fixed patterns (3, 4, 5, 6, 7, or 8 bits per DPCCH slot)
TFCI:
Transmit Format Combination Indicator (0, 2, 3, or 4 bits)
FBI:
Feedback Information (0, 1, or 2 bits)
TPC:
Transmit Power Control bits (1 or 2 bits); power adjustment in steps of
1, 2, or 3 dB
87
Uplink Signaling Radio Bearer on DPDCH/DPCCH
RRC AM or NAS DT normal or high priority
RRC UM
136
136
144
(figure 5-34)
128
128
144
8 bit RLC
4 bit MAC
MAC Layer
CRC 16
148
8 tail bits
164
16 bit RLC
4 bit MAC
136 bits in 10 msec => 13.6 kbps
128bits in 10 msec => 12.8 kbps
172
Rate 1/3 CC
516
1st Interleaving
Rate Matching
600
2nd Interleaving
Slot segmentation
40
40
DPDCH 60ksps => SF = 64
PILOT
TFCI
TPC
DPCCH 15ksps
88
6
2
2
I
branch
Q
Downlink DPDCH/DPCCH (figure 5-35)
1 Slot = 0.666 mSec = 2560 chips = 10 x 2k bits, k = [0...7]
SF = 512/2k = [512, 256, 128, 64, 32, 16, 8, 4]
Data 1
0
1
DPDCH
DPCCH
DPDCH
TPC
2
3
TFCI
4
5
6
DPCCH
Data 2
7
8
9
10
11
Pilot
12
13
14
1 Frame = 15 slots = 10 mSec
The DPDCH carries user traffic, layer 2 overhead bits, and layer 3
signaling data.
The DPCCH carries layer 1 control bits: Pilot, TPC, and TFCI
Downlink Closed-Loop Power Control steps of 1 dB dB
89
Downlink Signaling Radio Bearer on DPDCH/DPCCH
(figure 5-36)
RRC AM or NAS DT normal or high priority
RRC UM
136
136
144
8 bit RLC
4 bit MAC
MAC Layer
CRC 16
148
8 tail bits
164
128
128
144
16 bit RLC
4 bit MAC
136 bits in 10 msec => 13.6 kbps
128bits in 10 msec => 12.8 kbps
172
Rate 1/3 CC
516
1st Interleaving
Rate Matching
510
2nd Interleaving
4
34
Slot segmentation
34
2
2 TPC & 4 PILOT
2
DPDCH/DPCCH = 30ksps => SF = 128
90
4
Uplink Speech RAB mapping (figure 5-37)
20 msec of each subflow
103
81
CRC 12
81
103
93
1/3
1/3
303+1
333+1
304
334
152
152
152
167
167
2nd interleaving
40
167
1st Interleaving
68
68
152
140
600
40
DPDCH 60kbps => SF=64
PILOT TFCI TPC
RRC AM or NAS DT normal priority
40 msec
128
60
8 bit RLC
16 bit RLC
128
4 bit MAC
144
4 bit MAC
MAC Layer
8 tail bits
60
CRC 16
148
8 tail bits
164
Convolutional coding
1/2
Radio frame equalization
136
516 Rate 1/3 CC
136
68
Rate match 360
RRC UM
136
136
144
Frame segmentation
167
68
Rate match 360
2nd interleaving
Rate matching 2nd speech block
140
600
DPDCH 60kbps => SF=64
DPCCH 15kbps
152
6 Q 2
91
2
167
68
#1 110
152
600
40
40
1st interleaving
129 129 129 129
140 140 140 140
I
Branch
Q
600 bits (600 symbols)
68
#2 110
600
40
40
167
40
40
600 bits (600 symbols)
Uplink Speech RAB mapping (during SID frame) (figure 5-38)
• After every eight frames the UE sends a Silence Descriptor (SID) frame, which is used
during the discontinuous speech periods.
92
Downlink Speech RAB mapping (figure 5-39)
RRC UM
136
136
144
20 msec of each subflow
81
81
93
60
103
303 (1/3)
294
294
147
147
60
333 (1/3)
316
316
158
158
40 msec
128
128
144
8 bit RLC
4 bit MAC
MAC Layer
CRC 12
103
RRC AM or NAS DT normal priority
CRC 16
148
164
8 tail bits
136 (1/2) Convolutional coding
172
Rate matching
1st interleaving
172
Frame segmentation
86
86
16 bit RLC
4 bit MAC
8 tail bits
516 Rate 1/3 CC
476
1st interleaving
119 119 119 119
2nd speech block
147
158
86
2nd interleaving
119
510
34
34
147
158
86
2nd interleaving
119
510
34
34
2 TPC 4 Pilot
2 TPC 4 Pilot
DPDCH 60ksps => SF=128
DPDCH 60kbps => SF=128
93
152
167
68
#1 110
152
600
600
68
#2 110
600
40
40
167
40
40
600
Uplink CS 64 RAB mapping (figure 5-40)
64 kbps = 1280 in 20 msec
=>2X640 bit Transport Blocks
640
640
640
640
Turbo Coding 3936
RRC UM
136
136
144
RRC AM or NAS DT normal priority
40 msec
128
16 bit RLC
8 bit RLC
128
4 bit MAC
4 bit MAC
144
CRC 16
MAC Layer
CRC 16
148
12 Trellis termination bits
8 tail bits
164
516 Rate 1/3 CC
1st Interleaving
1974
Frame segmentation
1974
2243
Rate matching
2243
1st interleaving
129 129 129 129
157 157 157 157
2nd speech block
2243
2nd interleaving
160
2400
160
DPDCH 240kbps => SF=16
PILOT TFCI TPC
2243
157
2nd interleaving
157
2400
DPDCH 240kbps => SF=16
DPCCH 15kbps
6 Q 2
94
2
I
Branch
Q
600
40
40
600 bits (600 symbols)
#2 110
152
600
160
160
#2 110
152
40
40
600 bits (600 symbols)
Downlink CS 64 RAB mapping (figure 5-41)
RRC UM
64 kbps = 1280 in 20 msec
=>2X640 bit Transport Blocks
640
640
640
640
136
136
144
CRC 16
Turbo Coding 3936
3926
3926
1963
1963
RRC AM or NAS DT normal priority
40 msec
128
16 bit RLC
8 bit RLC
128
4 bit MAC
4 bit MAC
144
MAC Layer
CRC 16
148
8 tail bits
164
516 Rate 1/3 CC
12 Trellis termination bits
Rate matching
548
1st interleaving
1st interleaving
Frame segmentation 137 137 137 137
2nd speech block
1963
2nd interleaving
137
2100
140
140
4/8/8
DPDCH 120ksps => SF=32
1963
2nd interleaving
140
137
2100
140
TPC/TFCI/PILOT
DPDCH 120ksps => SF=32
95
600
600
Uplink Streaming 57.6 kbps RAB mapping (figure 5-42)
Up to 4X576 TBs in 40 msec
=> max data rate = 57.6 kbps
1
2
3
4
576
16
576
16
576
16
576
Turbo Coding 7104
RRC UM
16
RRC AM or NAS DT normal priority
40 msec
136
128
136
128
8 bit RLC
16 bit RLC
4 bit MAC
144
144
4 bit MAC
CRC 16
MAC Layer
CRC 16
148
12 Trellis termination bits
8 tail bits
164
1st Interleaving 7116
1779
2218
1779
2218
1779
2218
1779
2218
Frame segmentation
Rate matching
516 Rate 1/3 CC
1st interleaving
129 129 129 129
182 182 182 182
2nd speech block
2218
2nd interleaving
160
2400
160
DPDCH 240kbps => SF=16
PILOT TFCI TPC
2218
182
2nd interleaving
182
2400
DPDCH 240kbps => SF=16
6 Q 2
96
2
167
68
#1 110
152
600
160
160
DPCCH 15kbps
152
I
Branch
Q
600 bits (600 symbols)
68
#2 110
600
40
40
167
40
40
600 bits (600 symbols)
Downlink Streaming 57.6 kbps RAB mapping (figure 5-43)
RRC UM
Up to 4X576 TBs in 40 msec
=> max data rate = 57.6 kbps
1
2
576
576
16
3
16
4
576
576
16
Turbo Coding 7104
7764
7764
1941
1941
136
136
144
1941
16
CRC 16
RRC AM or NAS DT normal priority
40 msec
128
16 bit RLC
8 bit RLC
128
4 bit MAC
4 bit MAC
144
MAC Layer
CRC 16
148
8 tail bits
164
12 Trellis termination bits
516 Rate 1/3 CC
Rate matching
636
1st interleaving
1st interleaving
Frame segmentation 159 159 159 159
1941
2nd speech block
1941
2nd interleaving
2100
140
140
1941
159
4/8/8
DPDCH 120ksps => SF=32
2nd interleaving
140
159
2100
140
TPC/TFCI/PILOT
DPDCH 120kbss => SF=32
97
600
600
Uplink PS DATA CELL_FACH (DCCH on RACH)
RRC UM
(figure 5-44)
RRC AM, NAS DT normal or low priority
136
128
8 bit RLC
136
144
24 bit MAC
MAC layer
168
184
16 bit RLC
128
144
24 bit MAC
136 bits in 10 msec => 13.6 kbps
16 CRC 16
8 tail bits
128 bits in 10 msec => 12.8 kbps
Rate 1/2 Convolutional Coding 384
1st Interleaving
Rate Matching 300
2nd Interleaving
Slot segmentation
20
20
RACH message part 30ksps => SF = 128
PILOT
TFCI
8
98
2
I
Branch
Q
Uplink PS DATA CELL_FACH (DTCH on RACH) (figure 5-45)
Max user plane 320 bits in 20 msec => 16 kbps
320
AM => 16 bit RLC
320
24 bit MAC
336
MAC layer
16 CRC 16
360
8 tail bits
376
Rate 1/2 Convolutional Coding 768
1st Interleaving
Frame segmentation 384
Frame segmentation 384
Rate Matching 300
Rate Matching 300
2nd Interleaving
2nd Interleaving
20
20
20
RACH message 30ksps => SF = 128
PILOT TFCI
8
2
20
RACH message 30ksps => SF = 128
PILOT TFCI
99
8
2
Downlink PS DATA CELL_FACH (DCCH on FACH) (figure 5-46)
RRC UM
136
136
144
168
RRC AM or NAS DT normal priority
40 msec
128
8 bit RLC
24 bit MAC
MAC layer
168
184
16 bit RLC
128
184
24 bit MAC
144
136 bits in 10 msec => 13.6 kbps
CRC 16
128 bits in 10 msec => 12.8 kbps
8 tail bits
376
Rate 1/2 Convolutional Coding 752
1st Interleaving
Rate Matching 1080
2nd Interleaving
72
8
Slot segmentation
TFCI bits
S-CCPCH = 60ksps => SF = 64
100
72
8
Downlink PS DATA CELL_FACH (DTCH on FACH) (figure 5-47)
320
320
336
360
Max user plane = 320 bits in 10msec => 32 kbps
AM => 16 bit RLC header
24 bit MAC header
CRC 16
376
Turbo Coding
12 trellis termination bits
1128
1st interleaving
Rate Matching 1080
2nd Interleaving
72
8
Slot segmentation
TFCI bits
72
8
S-CCPCH = 60ksps => SF = 64
101
Uplink PS 64 RAB mapping (figure 5-48)
Up to 4X320 TBs in 20 msec
=> max data rate = 64 kbps
1
2
3
4
320
336
16
RRC AM or NAS DT normal priority
40 msec
136
128
136
128
8 bit RLC
16 bit RLC
16 bit RLC
4 bit MAC
144
144
4 bit MAC
CRC 16
336
336
336
MAC Layer
CRC 16
148
Turbo Coding 4224
12 Trellis termination bits
8 tail bits
164
320
16
RRC UM
16
320
16
16
320
16
16
16
1st Interleaving 4236
2118
Frame segmentation
2118
2246
2246
Rate matching
516 Rate 1/3 CC
1st interleaving
129 129 129 129
154 154 154 154
2nd speech block
2246
2nd interleaving
160
2400
160
DPDCH 240kbps => SF=16
PILOT TFCI TPC
2246
154
2nd interleaving
154
2400
DPDCH 240kbps => SF=16
6 Q 2
102
2
167
68
#1 110
152
600
160
160
DPCCH 15kbps
152
I
Branch
Q
600 bits (600 symbols)
68
#2 110
600
40
40
167
40
40
600 bits (600 symbols)
Downlink PS 64 RAB mapping (figure 5-49)
RRC UM
Up to 4X320 TBs in 20 msec
=> max data rate = 64 kbps
1
320
336
2
16
320
16
336
3
16
4
320
16
136
136
144
16
336
320
16
336
16
16 bit RLC
16
CRC 16
Turbo Coding 4224
3932
3932
1966
1966
RRC AM or NAS DT normal priority
40 msec
128
16 bit RLC
8 bit RLC
128
4 bit MAC
4 bit MAC
144
MAC Layer
CRC 16
148
8 tail bits
164
12 Trellis termination bits
516 Rate 1/3 CC
Rate matching
536
1st interleaving
1st interleaving
Frame segmentation 134 134 134 134
2nd speech block
1966
2nd interleaving
2100
160
160
1966
134
4/8/8
DPDCH 120ksps => SF=32
2nd interleaving
160
134
2100
160
TPC/TFCI/PILOT
DPDCH 120kbss => SF=32
103
600
600
Downlink PS 128 RAB mapping (figure 5-50)
Up to 8X320 TBs in 20 msec
=> max data rate = 128 kbps
320
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16 bit RLC
16
16
RRC UM
16
CRC 16
Turbo Coding 8448
8376
8376
4188
136
136
144
4188
RRC AM or NAS DT normal priority
40 msec
128
16 bit RLC
8 bit RLC
128
4 bit MAC
4 bit MAC
144
MAC Layer
CRC 16
148
8 tail bits
164
12 Trellis termination bits
516 Rate 1/3 CC
Rate matching
528
1st interleaving
1st interleaving
Frame segmentation 132 132 132 132
2nd speech block
4188
2nd interleaving
4320
288
288
4188
132
8 / 8 / 16
DPDCH 240ksps => SF=16
2nd interleaving
288
132
4320
288
TPC/TFCI/PILOT
DPDCH 240ksps => SF=16
104
600
600
Downlink PS 384 RAB mapping (figure 5-51)
RRC UM
Up to 12X320 TBs in 10 msec
=> max data rate = 384 kbps
320
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
320
16
16
Turbo Coding 12672
9025
1st interleaving
320
16
16
16
RRC AM or NAS DT normal priority
40 msec
136
128
16 bit RLC
8 bit RLC
136
128
4 bit MAC
4 bit MAC
144
144
MAC Layer
CRC 16
148
12 Trellis
8 tail bits
164
termination
516 Rate 1/3 CC
bits
380
Rate matching
1st interleaving
95 95 95 95
Next 3 blocks
9025
2nd interleaving
95
9120
608
608
8 TCI 8 TPC 18 Pilot
DPDCH 480ksps => SF=8
600
105
600
600
Uplink MultiRAB, Speech RAB + PS 64/64 RAB mapping
(figure 5-52)
RRC UM
20 msec of each subflow
60
103
81
CRC 12
81
2
3
4
320
320
320
320
336
103
93
1
336
336
16 bit RLC
336
CRC 16
136
136
144
8 tail bits
60
1/3
1/2
303+1
333+1
136
304
334
136
148
158
158
88
2nd interleaving
158
1881
88
1st Interleaving 4236
2118
125
148
1881
88
2nd interleaving
160
125
2400
160
160
DPDCH 60kbps => SF=16
DPDCH 60kbps => SF=16
PILOT TFCI TPC
CRC 16
DPCCH 15kbps
6
106
8 tail bits
1st interleaving
1881
158
16 bit RLC
4 bit MAC
516 Rate 1/3 CC
2118
1881
88
2400
160
128
144
164
1/3
148
8 bit RLC
4 bit MAC
148
Turbo Coding 4224
148
RRC AM or NAS DT normal priority
40 msec
128
2
2
I
Branch
Q
129
129 129 129
125
125 125 125
Downlink MultiRAB, Speech RAB + PS 64/64 RAB mapping
(figure 5-53)
RRC UM
Up to 4X320 TBs in 20 msec
max data rate = 64 kbps
20 msec of each subflow
81
60
103
CRC 12
81
93
103
303 (1/3)
333 (1/3)
RM 258
RM 276
1st Int. 258
1st Int. 276
129
129
138
129
138
77
8 tail bits
60
138
2nd interleaving
2
3
4
320
320
320
320
336
336
336
1st Int. 154
77
8 bit RLC
4 bit MAC
16 bit RLC
CRC 16
128
16 bit RLC
144
4 bit MAC
148
CRC 16
8 tail bits
164
12 Trellis termination bits
516 Rate 1/3 CC
RM 3294
436
1st Int. 3294
1st interleaving
1647
1647
109
2100
160
160
336
144
Turbo Coding 4224
RM 154
1647
136
136
1
136 (1/2) CC
77
=>
RRC AM or NAS DT normal
priority
40
msec
128
4 TPC 8 Pilot 8 TFCI
DPDCH 120 ksps => SF=32
107
109 109 109 109