3g Ran Nsn Hsdpa Rrm & Parameters
-
Upload
markuskrasus -
Category
Documents
-
view
444 -
download
105
description
Transcript of 3g Ran Nsn Hsdpa Rrm & Parameters
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 1 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 1
HSDPA RRM & parameters
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 4 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 4
HSDPA RRM & parameters: Module Objectives
At the end of the module you will be able to:
• Explain the physical layer basics of HSDPA technology
• List the key changes brought by HSDPA and their impact on the network and on the protocol model
• Explain HSDPA RRM and the related parameters in detail, including packet scheduling, resource allocation, mobility and channel type selection
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 5 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 5
HSDPA RRM: Contents
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 6 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 6
HSDPA Principles
High Speed Downlink Packet Access (HSDPA) based on:
• Node B decisions
• Multi-code operation
• Fast Link Adaptation • Adaptive Modulation & Coding AMC
• Fast Packet Scheduling
• Fast H-ARQ
• Fast 2 ms TTI*
• Downwards Compatibility with R99
• (shared or dedicated carrier)
* TTI = 1 Subframe = 3 Slots = 2 ms
H-ARQ: Hybrid Automatic Repeat Request
Motivation:
- enhanced spectrum efficiency
- higher peak rates >> 2 Mbps
- higher cell throughput
- reduced delay for ACK transmission
3GPP Rel. 5; TS 25.308:
“HSDPA Overall Description”
HSDPAenabled WCEL; 0 = disabled; 1 = enabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 7 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 7
Principles of DC HSDPA
SSHSC
Primary serving cell
• Dual-Cell HSDPA of 3GPP Rel8 uses two adjacent WCDMA carriers (same bandwidth) to transmit data for a single
UE
• Can be used with MIMO 2x2 and/or 64QAM
• DC HSDPA UEs are assigned HS-PDSCHs in the primary serving cell & Secondary Serving High Speed Cell (SSHSC)
• UL (CQI, ACK/NACK) for DC HSDPA UEs via primary serving cell (no UL in SSHSC)
• Besides HS-DSCH the primary serving cell is carrying
– The full set of control & common control channels
– UL transport channels E-DCH HS-DPDCH + optional DC HS-DPCCH (HSUPA UEs)
• SSHSC is left clean from control signaling (max. HS-DSCH capacity)
– Among common channels only CPICH is used in SSHSC
– E-AGCH, E-RGCH, E-HICH in SSHSC existent but not used by DC HSDPA
f1
f2
DCellHSDPAEnabled WCEL; 0 = disabled; 1 = enabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 8 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 8
Adaptive Modulation & Coding (1/2)
I
Q 0000
0010
0011
0001
1000
1010
1011
1001
1100
1110
1111
1101
0100
0110
0111
0101
16QAM
4-Bit Keying QPSK
2-Bit Keying
Q
I
(1,1) (0,1)
(1,0) (0,0)
HSDPA uses
• QPSK
• 16QAM
• 64QAM* dynamically based on
quality of the radio link
* defined in 3GPP Rel. 7 / implemented with NSN RU20
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 9 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 9
Adaptive Modulation & Coding (2/2)
Rate
Matching
Puncturing /
Repetition
Turbo Coding
1/3
Effective
Code Rate:
1/4 - 3/4
HSDPA Adaptive Coding
• based on the R’99 1/3 Turbo Coding
• Rate Matching: Puncturing or Repetition
code rate: 1/6 – 4/4
• dynamically based on
quality of the radio link
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 10 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 10
C1,0 = [1]
C2,1 = [1-1]
C2,0 = [11]
C4,0 = [1111]
C4,1 = [11-1-1]
C4,2 = [1-11-1]
C4,3 = [1-1-11]
C8,0 = [11111111]
C8,1 = [1111-1-1-1-1]
C8,2 = [11-1-111-1-1]
C8,3 = [11-1-1-1-111]
C8,4 = [1-11-11-11-1]
C8,5 = [1-11-1-11-11]
C8,6 = [1-1-111-1-11]
C8,7 = [1-1-11-111-1]
C16,0 = [.........]
C16,1 = [.........]
C16,15 = [........]
C16,14 = [........]
C16,13 = [........]
C16,12 = [........]
C16,11 = [........]
C16,10 = [........]
C16,9 = [.........]
C16,8 = [.........]
C16,7= [.........]
C16,6 = [.........]
C16,5 = [.........]
C16,4 = [.........]
C16,3 = [.........]
C16,2 = [.........]
SF = 1 2 4 8 SF = 16 256 512 ...
SF = 16
240 ksymb/s
Multi-Code operation:
1..15 codes
0.24 .. 3.6 Msymb/s
Multi Code Operation (1/3)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 11 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 11
Multi Code Operation (2/3)
RU20 includes
3GPP Rel. 7 features:
• 64QAM (RAN1643)
Modulation
QPSK
Coding rate
1/4
2/4
3/4
5 codes 10 codes 15 codes
600 kbps 1.2 Mbps 1.8 Mbps
1.2 Mbps 2.4 Mbps 3.6 Mbps
1.8 Mbps 3.6 Mbps 5.4 Mbps
16QAM
2/4
3/4
4/4
2.4 Mbps 4.8 Mbps 7.2 Mbps
3.6 Mbps 7.2 Mbps 10.8 Mbps
4.8 Mbps 9.6 Mbps 14.4 Mbps
64QAM
3/4
5/6
4/4
5.4 Mbps 10.8 Mbps 16.2 Mbps
6.0 Mbps 12.0 Mbps 18.0 Mbps
7.2 Mbps 14.4 Mbps 21.6 Mbps
HSDPA64QAMAllowed
WCEL; 0 (Disabled), 1 (Enabled)
64QAM
6 bits/symbol
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 12 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 12
Multi Code Operation (3/3): HSDPA UE capability classes
HS- DSCH
category
max. No. of
HS-DSCH
Codes
min. *
Inter-TTI
interval
Modulation
Dual-
Stream
MIMO
supported
Peak
Rate
1 5 3 (6 ms) QPSK/16QAM No 1.2 Mbps
2 5 3 QPSK/16QAM No 1.2 Mbps
3 5 2 (4 ms) QPSK/16QAM No 1.8 Mbps
4 5 2 QPSK/16QAM No 1.8 Mbps
5 5 1 (2 ms) QPSK/16QAM No 3.6 Mbps
6 5 1 QPSK/16QAM No 3.6 Mbps
7 10 1 QPSK/16QAM No 7 Mbps
8 10 1 QPSK/16QAM No 7 Mbps
9 15 1 QPSK/16QAM No 10 Mbps
10 15 1 QPSK/16QAM No 14 Mbps
11 5 2 QPSK only No 1 Mbps
12 5 1 QPSK only No 1.8 Mbps
13 15 1 QPSK/16QAM/ 64QAM
No 17.4 Mbps
14 15 1 QPSK/16QAM/ 64QAM
No 21.1 Mbps
15 15 1 QPSK/16QAM Yes 23.4 Mbps
16 15 1 QPSK/16QAM Yes 28 Mbps
17 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
17.4 or 23.4 Mbps
18 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
21.1 or 28 Mbps * TTI: Transmission Time Interval
RU20/30 include
3GPP Rel. 7/8 features:
• 64QAM (cat 13, 14, 17, 18)
• 2x2 MIMO (Dual-Stream MIMO) (cat 15, 16, 17,
18)
MIMO w/- 64QAM (cat 19, 20)
• DC-HSDPA (cat 21, 22)
• DC–HSDPA w/- 64QAM (cat 23, 24)
RU40 include 3GPP Rel.9 features:
• DC–HSDPA w/-MIMO w/o 64QAM (cat 25, 26)
• DC–HSDPA & MIMO & 64QAM (cat 27, 28)
MIMOEnabled WCEL; 0 (Disabled), 1 (Enabled)
HSDPA64QAMAllowed
WCEL; 0 (Disabled), 1 (Enabled)
Further details on HS-DSCH categories &
other parameters HSPA+ RRM
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 13 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 13
UE Iub
Uu
Red
uced
retra
nsm
issio
n
RNC: functionalities
shifted to
Node B
„more intelligence“
new functionalities
new UEs
HSDPA Capability
Classes
Network Modifications for HSDPA
UTRAN & UE:
• modified PHY layer
• modified MAC
• modified transport and physical channels
• modified coding
• modified modulation
new Node B functionalities:
• Acknowledged transmission: Fast H-ARQ
faster retransmission / reduced delays !
less Iub retransmission traffic !
higher spectrum efficiency !
• Fast Packet Scheduling
fast & efficient resource allocation !
• Fast Link Adaptation
Adaptive Modulation & Coding !
compensation of fast fading (without fast PC)
higher peak rates & spectrum efficiency !
Node B
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 14 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 14
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 15 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 15
TNL
MAC-d
DCH FP
DCH FP
MAC-d
TNL
Node B Iub RNC
RLC RLC
PHY PHY TNL
MAC-d
MAC-hs
MAC-ehs HS-DSCH FP
MAC-d
TNL
UE Uu Node B Iub RNC
RLC RLC MAC-d flow
HS-DSCH
PHY PHY
UE Uu
DCH
DPCH
HS-PDSCH
R99
HSDPA (R5)
(e)hs: (enhanced) high speed
TNL : Transport Network Layer
HSDPA Protocol Model
MAC-hs
MAC-ehs HS-DSCH FP
HSDPA (R7)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 16 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 16
MAC: Medium Access Control MAC TS 25.321 • Mapping of logical channels onto transport channels
• Multiplexing of multiple logical channels onto a single transport channel, e.g. of 4 signalling radio bearers (SRB) onto single DCH
• Complete MAC multiplexing for user plane data currently not supported
• Multiplexing requires the addition of a MAC header
• MAC entities on network side distributed between RNC and Node B
MAC-hs
• supports HSDPA with 3GPP Rel. 5
• Tasks of MAC-hs within the Node B
• Flow control (see section packet scheduling)
• Packet scheduling (see section packet scheduling)
• H-ARQ (see section layer 1 re-transmission)
• Transport format selection (see section link adaptation)
• Tasks of MAC-hs within the UE
• HARQ (see section layer 1 re-transmission)
• Disassembly of transport blocks
• Re-ordering
• Header & payload
• Payload: Concatenating of one or more MAC-d PDU into single MAC-hs PDU
• Header: 21 bits assuming single MAC-d PDU size
MAC-ehs
• supports enhanced HS-DSCH functions of 3GPP Rel. 7 - 9
• must be configured to support features such as: 64QAM (RAN1643), MIMO (RAN 1642), flexible RLC (RAN1638), Dual-Cell HSDPA
(RAN1906)
Concepts of MAC Layer, MAC-hs & MAC-ehs
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 17 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 17
Physical Channel Overview
HS-PDSCH High-Speed Physical DL Shared Channel
HS-SCCH High Speed Shared Control Channel
associated DCH Dedicated Channel (Rel. 99)
HS-DPCCH High Speed Dedicated Physical Control Channel
Node B
MAC-hs
F-DPCH Fractional Dedicated Physical Channel (Rel. 6/7)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 18 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 18
HS-PDSCH
• HS-PDSCH: High-Speed Physical Downlink Shared Channel
• Transfer of actual HSDPA data
• 5 - 15 code channels
• QPSK or 16QAM modulation
• Divided into 2 ms TTIs
• Fixed SF16
HSPDSCHCodeSet HS-PDSCH code set; WCEL; (-) (-) (5 codes)
Examples
00000 00000 100000 = always 5 codes reserved (default)
11010 10100 100000 = number of reserved codes adjustable (5, 8, 10, 12, 14 or 15 codes, recommended)
0-4 codes always disabled 11-15
codes
6-10
codes
• HS-PDSCH code set parameter
• Specifies whether number of
codes channels reserved for HSDPA is fixed* or dynamically adjustable
• Minimum 5 code channels / Maximum 15 codes channels
• Possible numbers of code channels enabled / disabled bit wise
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 19 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 19
HS-SCCH (1/2)
• HS-SCCH: High-Speed Shared Control Channel • L1 Control Data for UE; informs the UE how to decode the next HS-PDSCH frame
e.g. UE Identity, Channelization Code Set, Modulation Scheme, TBS, H-ARQ process information
• Fixed SF128
• transmitted 2 slots in advance to HS-PDSCHs
• NSN implementation with slow power control: shares DL power with the HS-PDSCH
• more than 1 HS-SCCH required when code multiplexing is used
TBS: Transport Block Size
• Code multiplexing
• HSDPA service for several users simultaneously
• For each user individual HS-SCCH required
• available only, if > 5 codes can be reserved for HS-PDSCH
SF16
HS-PDSCH
Time
User 1 User 2 User 3 User 4
Subframe
2 ms
5
10
15
MaxNbrOfHSSCCHCodes
Maximum number of HS-SCCH codes
WCEL; RU10 & earlier: 1..3; 1; 1; RU20: 1..4
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 20 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 20
HS-SCCH (2/2)
128 128 128
Available CC Allocated CC Blocked CC
SF16
SF32 32
SF64 64 64 64
SF256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256
128 128 128 128 128 128 128 SF128
+15 x SF16
HS-PDSCH
CPICH
S-CCPCH1
S-CCPCH2 HS-SCCH HS-SCCH HS-SCCH
FACH-s: for Service Area Broadcast (CTCH)
P-CCPCH
AICH
PICH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 21 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 21
HS-DPCCH
• UL HS-DPCCH: High-Speed Dedicated Physical Control Channel
• MAC-hs Ack/Nack information (send when data received)
• Channel Quality Information (CQI reports send every 4ms, hardcoded period)
• Fixed SF 256
HARQ-ACK
(10 bit)
1 Slot = 2560 chip 2 Slots = 5120 chip
Subframe # 0 Subframe # i Subframe # N
1 HS-DPCCH Subframe = 2ms
CQI (20 bit)
Channel Quality Indication
TS 25.21: CQI values = 0 (N/A), 1 .. 30; steps: 1;
1 indicating lowest, 30 highest air interface quality
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 22 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 22
HS-DPCCH & CQI
UE observes
P-CPICH (Ec/Io)
CQI*
1 137 1 QPSK 0
2 173 1 QPSK 0
3 233 1 QPSK 0
4 317 1 QPSK 0
5 377 1 QPSK 0
6 461 1 QPSK 0
7 650 2 QPSK 0
8 792 2 QPSK 0
9 931 2 QPSK 0
10 1262 3 QPSK 0
11 1483 3 QPSK 0
12 1742 3 QPSK 0
13 2279 4 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3565 5 16-QAM 0
17 4189 5 16-QAM 0
18 4664 5 16-QAM 0
19 5287 5 16-QAM 0
20 5887 5 16-QAM 0
21 6554 5 16-QAM 0
22 7168 5 16-QAM 0
23 9719 7 16-QAM 0
24 11418 8 16-QAM 0
25 14411 10 16-QAM 0
26 14411 10 16-QAM -1
27 14411 10 16-QAM -2
28 14411 10 16-QAM -3
29 14411 10 16-QAM -4
30 14411 10 16-QAM -5
* UE internal (proprietary) process
TB Size [bit]
CQI value 0: N/A (Out of range)
= Reference Power Adjustment (Power Offset) [dB]
CQI used for:
• Link Adaptation decision
• Packet Scheduling decision
ACK/NACK used for:
• H-ARQ process • Link Adaptation decision
• HS-SCCH power adaptation
CQI TB Size # codes Modulation
CQI Table (Example) TS 25.214: Annex Table 7b
Cat 8 UE
P-CPICH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 23 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 23
CQI Tables 1 136 1 QPSK 0
2 176 1 QPSK 0
3 232 1 QPSK 0
4 320 1 QPSK 0
5 376 1 QPSK 0
6 464 1 QPSK 0
7 648 2 QPSK 0
8 792 2 QPSK 0
9 928 2 QPSK 0
10 1264 3 QPSK 0
11 1488 3 QPSK 0
12 1744 3 QPSK 0
13 2288 4 QPSK 0
14 2592 4 QPSK 0
15 3328 5 QPSK 0
16 3576 5 16-QAM 0
17 4200 5 16-QAM 0
18 4672 5 16-QAM 0
19 5296 5 16-QAM 0
20 5896 5 16-QAM 0
21 6568 5 16-QAM 0
22 7184 5 16-QAM 0
23 9736 7 16-QAM 0
24 11432 8 16-QAM 0
25 14424 10 16-QAM 0
26 15776 10 64-QAM 0
27 21768 12 64-QAM 0
28 26504 13 64-QAM 0
29 32264 14 64-QAM 0
30 32264 14 64-QAM -2
CQI TB Size # codes Modulation
1 137 1 QPSK 0
2 173 1 QPSK 0
3 233 1 QPSK 0
4 317 1 QPSK 0
5 377 1 QPSK 0
6 461 1 QPSK 0
7 650 2 QPSK 0
8 792 2 QPSK 0
9 931 2 QPSK 0
10 1262 3 QPSK 0
11 1483 3 QPSK 0
12 1742 3 QPSK 0
13 2279 4 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3565 5 16-QAM 0
17 4189 5 16-QAM 0
18 4664 5 16-QAM 0
19 5287 5 16-QAM 0
20 5887 5 16-QAM 0
21 6554 5 16-QAM 0
22 7168 5 16-QAM 0
23 9719 7 16-QAM 0
24 11418 8 16-QAM 0
25 14411 10 16-QAM 0
26 17237 12 16-QAM 0
27 21754 15 16-QAM 0
28 23370 15 16-QAM 0
29 24222 15 16-QAM 0
30 25558 15 16-QAM 0
CQI TB Size # codes Modulation
TS 25.214:
Annex Table 7d
Cat 10 UE
TS 25.214:
Annex Table 7f
Cat 27 UE
TS 25.214 Annex Table 7g
Cat 14 UE:
CQI29: 14 Codes; 32257 bit
CQI30: 15 Codes; 38582 bit
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 24 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 24
Associated DCH (DL & UL)
• DL DPCH: Associated Dedicated Physical Channel
• L3 signalling messages
• Speech - AMR
• Power control commands for associated UL DPCH
• UL DPCH: (DPDCH & DPCCH)
• L3 signalling messages
• Transfer of UL data 16 / 64 / 128 / 384 kbps, e.g. TCP acknowledgements
• Speech - AMR
DPDCH / DPCCH (time multiplexed)
DPDCH: L3 signalling; AMR
DPCCH: TPC for UL DPCH power control
DPDCH: L3 signalling, AMR; TCP ACKs;
16 / 64 / 128 / 348 kbps
DPCCH: TPC, Pilot, TFCI
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 25 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 25
Fractional DPCH: F-DPCH (DL)
The Fractional DPCH (F-DPCH):
• introduced in 3GPP Rel. 6 (enhanced in Rel. 7; NSN RU20 implementation based on Rel. 7)
• replaces the DL DPCCH
• includes Transmit Power Control (TPC) bits but excludes TFCI & Pilot bits & SRB – TFCI bits - no longer required as there is no DPDCH
– Pilot bits - no longer required as TPC bits are used for SIR measurements
– SRB mapped to E-DCH & HS-DSCH
• increases efficiency by allowing up to 10 UE to share the same DL SF256 channelization code
- time multiplexed one after another
• RU20 feature RAN1201; – requires Rel. 7 or newer UE
– HSDPA & HSUPA must be enabled
– Feature is licensed using an RNC ON/OFF license
– License CPC exists and its state is ON
Tx Off TPC
Slot #i
1 time slot 2560 chips
Tx Off
256
chips
FDPCHEnabled WCEL; 0 (Disabled), 1 (Enabled)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 26 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 26
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 27 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 27
Summary
DB: Dual Band
Characteristic RU10 RU20 RU30 RU40/RU50
HSDPA users per cell ≤ 64 ≤ 72 (RAN1668) ≤ 72 ≤ 128 (RAN2124)
Modulation QPSK/16QAM QPSK/16QAM & 64QAM
(RAN1643) QPSK/16QAM/64QAM QPSK/16QAM/64QAM
MIMO No Yes (2x2) (RAN1642) Yes Yes
Dual-Cell HSDPA No Yes (RAN1906) DC-HSDPA DC-HSDPA
DB DC HSDPA (RAN2179)
Data rate per UE up to 14 Mbps up to 42 Mbps up to 42 Mbps 84 Mbps
(RAN 1907) up to 84 Mbps (RAN1907)
Traffic Classes Interactive + Background +
Streaming
+ CS Voice over HSPA
(RAN1689) all traffic classes
all traffic classes
Packet Scheduler Proportional Fair (PF)
+ QoS Aware HSPA
Scheduling
PF + QoS aware scheduling PF + QoS aware
scheduling
PF + QoS aware
scheduling
HSDPA Multi-RAB multiple RAB HSDPA +
AMR multiple RAB HSDPA + AMR
multiple RAB HSDPA +
AMR, +CS64 Conv.
multiple RAB HSDPA +
AMR, +CS64 Conv.
Code Multiplexing (Scheduled users per TTI)
Yes (up to 3) Yes (up to 4) Yes (up to 4) Yes (up to 4)
UL associated DCH 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps 16, 64, 128, 384 Kbps
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 28 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 28
• Most enhanced features must be licensed individually and are activated by setting individual off / on parameter
• Some features can be activated on cell level, others on WBTS or even RNC level only
Feature Activation
HSDPAenabled WCEL; 0 = disabled; 1 = enabled
HSDPA48UsersEnabled RNFC; 0 = disabled; 1 = enabled
HSDPA64UsersEnabled WCEL; 0 = disabled; 1 = enabled
HSDPA14MbpsPerUser WBTS; 0 = disabled; 1 = enabled
HSDPAMobility Serving HS-DSCH cell change & SHO on/off switch
RNFC ; 0 = disabled; 1 = enabled
HspaMultiNrtRabSupport HSPA multi RAB NRT support
WCEL; 0 = disabled; 1 = enabled
HSDPADynamicResourceAllocation HSDPA Dynamic Resource Allocation
RNFC; 0 = disabled; 1 = enabled
HSDPA16KBPSReturnChannel HSDPA 16 Kbps UL DCH return channel on/off
RNFC; 0 = disabled; 1 = enabled
HSPA72UsersPerCell WCEL; 0 = disabled; 1 = enabled
if enabled, max. 72 HSDPA/HSUPA users can be supported
per cell.
HSPA128UsersPerCell WCEL; 0 = disabled; 1 = enabled
if enabled, max. 128 HSDPA/HSUPA users can be supported
per cell.
RU20/
30
HSDPA64QAMAllowed; MIMOEnabled; DCellHSDPAEnabled;
MIMOWith64QAMUsage
WCEL; 0 (Disabled), 1 (Enabled)
DCellAndMIMOUsage
WCEL; 0=DC-HSDPA and MIMO disabled; 1=DC-HSDPA and MIMO w/o
64QAM enabled; 2=DC-HSDPA and MIMO with 64QAM enabled
FDPCHEnabled; CPCEnabled
WCEL; 0 (Disabled), 1 (Enabled)
HSPAQoSEnabled WCEL; 0..4; 1; 0 = disabled
0 = QoS prioritization is not in use for HS transport
1 = QoS prioritization is used for HS NRT channels
2 = HSPA streaming is in use
3 = HSPA CS voice is in use
4 = HSPA streaming & CS voice are in use
RU40
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 29 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 29
Cell Group Definition
• SCHs under the same Node B should not overlap with each other
• define for each sector offset relative to BTS frame number with parameter Tcell
• Cells with offsets within certain range form one cell group
– Group 1 offset = 0-512 chips
– Group 2 offset = 768-1280 chips
– Group 3 offset = 1536-2048 chips
– Group 4 offset = 2304 chips
0 chips
256 chips
512 chips
BTS reference
SCH
BTS reference
SCH
BTS reference
SCH
Tcell Frame timing offset of a cell
WCEL; 0..2304 chips;
256 chips; no default
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 30 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 30
HSPA 72 / 128 Users per Cell (1/3)
72/128 users
72/128 users
72/128 users
Hardware requirements:
• Flexi Node B must have Rel2 or Rel3 system module
HSPA72UsersPerCell
WCEL; 0 = not enabled; 1 = enabled
• HSPA 72 users/cell: RAN1686 (RU20); HSPA 128 users/cell: RAN2124 (RU40); optional
• RNC License Key required (On-Off)
• increases the number of simultaneous HSPA users to 72 / 128 per cell
• both with dedicated & shared scheduler
• HSDPA, HSUPA, Dynamic Resource Allocation must be enabled, Continuous Packet Connectivity & F-DPCH are
recommended for both RAN1686 & RAN2124, HSUPA DL Physical Channel Power Control recommended for
RAN2124
• max. 15 codes allocated (HS-PDSCH code set = 11010 10100 10000)
• Code multiplexing (max. no. of HS-SCCH codes MaxNbrOfHSSCCHCodes = 4)
• HSDPA 16 Kbps UL DCH should be enabled to avoid UL overload
Other parameters may restrict max. number of
HSPA users, e.g.:
-WCEL: MaxNumberEDCHCell
- WBTS: MaxNumberEDCHLCG
- WCEL: MaxNumberHSDSCHMACdFlows
- WCEL: MaxNumberHSDPAUsers
- WCEL: MaxNumbHSDPAUsersS
- WCEL: MaxNumbHSDSCHMACdFS
HSPA128UsersPerCell
WCEL; 0 = not enabled; 1 = enabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 31 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 31
DL Code allocation in a cell depends on activated features and traffic
– if HSPA 72 Users Per Cell or HSPA 128 Users Per Cell is enabled, RNC allocates DL codes according to Maximum number of scheduled HSDPA user per TTI (Code Multiplexing)
MaxNbrOfHSSCCHCodes; WCEL; 1..4; 1; 1 (4 is recommended in both cases)
– 1 E-RGCH & E-HICH codes is reserved in cell setup; max number of E-RGCH/E-HICH codes is 4 or not limited
reserved number of E-RGCH/E-HICH codes depend on number of HSUPA users, TTI (2ms or 10ms), whether the cell is serving or non-serving E-DCH cell to the UE, and scheduled or non-scheduled transmission
– if Paging 24 kbps feature is enabled, more DL codes are needed to separate FACH and PCH traffic
PCH24kbpsEnabled; WCEL; on/off & NbrOfSCCPCHs; WCEL; 1..3; 1; 1
S-CCPCH
depending on
FACH / PCH
configuration
HS-SCCH
E-RGCH
E-HICH
HSPA 72 / 128 Users Per Cell (2/3) DL Code allocation
SF 16,0
SF 32
SF 64
SF 128
SF 256
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 32 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 32
• No. of HS-SCCH channels increased to 4 to schedule & control increased
number of HSPA users in a cell
• DL code space limited dynamic DL control channel allocation mechanism
introduced to maximize available codes for HS-PDSCHs
HSUPA RRM (E-RGCH & E-HICH management / dynamic code allocation)
• if code tree resources allocated like on previous slide, following traffic is supported: – 15 codes @ SF16 for HSDPA
– single user per 2 ms TTI (no code multiplexing)
– MIMO enabled
– F-DPCH enabled
• most likely RNC will allocate another SF16 branch to increase control channel traffic reducing HSDPA
SF16 codes further
Traffic analysis
HSPA 72 / 128 Users Per Cell (3/3) MaxNbrOf
HSSCCHCodes
WCEL; RU10 & earlier: 1..3;
1; 1; RU20: 1..4
Code allocation in
case of 4 HS-SCCH:
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 33 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 33
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 34 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 34
Link adaptation algorithm
1) Generation of CQImeasured : – UE monitors EC/I0
– UE reads PHS-PDSCH SIG (L3/RRC signalling)
2) UE reports CQImeasured every 4 ms (NSN solution) – can be increased with Mass Event Eandler
3) CQI Correction in Node B Node B corrects reported CQImeasured to CQIcompensated based on:
– actual HS-PDSCH power PHS-PDSCH TRUE
– Number of ACK & NACK
4) Link Adaptation decision: Node B decides about TB size for next sub-frame: – Modulation
– Coding rate
– Number of codes
CQI Reporting & Link Adaptation
P-CPICH
CQI used for:
• Link Adaptation decision • Packet Scheduling decision
ACK/NACK used for:
• H-ARQ process • Link Adaptation decision
• HS-SCCH power adaptation
Remember:
* UE internal (proprietary) process
PHS-PDSCH: HS-PDSCH transmission power
TB: Transport Block
UE observes
P-CPICH (Ec/Io)
CQImeasured*
CQImeasured*
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 35 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 35
CQI Compensation (1/3)
CQImeasured
UE generates CQImeasured assuming Tx power PHS-PDSCH SIG = PCPICH + +
– calculated by RNC: = f x Min(PtxMaxHSDPA, PtxMax – PtxNonHSDPA) – PCPICH
PHS-PDSCH SIG = (f x Min(PtxMaxHSDPA, Ptxmax – PtxNonHSDPA)) [dBm] +
= Reference Power Adjustment (Power Offset) [dB] CQI tables
PtxMax = max. cell power
PtxNonHSDPA = total power allocated to R99 & DL control channels (latest report is taken)
PtxMaxHSDPA = max. allowed HSDPA power
signalled to UE in case of
HS-DSCH setup
Serving cell change
f = 0.7 for static HS-PDSCH power allocation
f = 0.5 for dynamic HS-PDSCH power
CQI Compensation in Node B
• Node B compensates CQI from differences between assumed HS-PDSCH Tx power
& actual HS-PDSCH Tx power PHS-PDSCH TRUE
– Part of HSDPA power used for HS-SCCH
– HS-PDSCH power can vary because of dynamic power allocation
• Offset X used to convert reported CQImeasured into compensated CQIcompensated
CQIcompensated = CQImeasured + X [dB]
X = PHS-PDSCH TRUE – (PCPICH + + ) – A [dB]
correction A estimated by outer loop link adaptation algorithm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 36 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 36
Outer loop link adaptation algorithm correction A
• If ACK received for first transmission of a packet – Correction A decreased by 0.005 dB
– But not below -4 dB (maximum CQI improvement towards higher TBS)
• If NACK received for first transmission of a packet – Correction A increased by 0.05 dB
– But not above 4 dB (maximum CQI downgrade towards lower TBS)
ACK for 1st transmission
NACK for 1st transmission
time
P0
CQI Compensation (2/3)
increase CQI
lower CQI
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 37 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 37
CQIMEASURED = 3
233 bits per TB (167 K)
e.g. PHS-PDSCH SIG = 37 dBm
e.g. PHS-PDSCH TRUE = 40 dBm
X = (40 – 37) dB = 3 dB
CQICOMPENSATED = 3 + 3 = 6
461 bits per TB (230 K)
X = 3 dB
• CQI compensation makes it difficult to map reported CQI from UE log files into expected HSDPA transport block size TBS
CQI Compensation (3/3)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 38 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 38
Spectral Efficient Link Adaptation
• Good radio conditions CQICOMPENSATED, but less data to be sent
• Node B determines CQINEEDED required for actual service
• Node B reduces HSDPA transmission power by CQICOMPENSATED - CQINEEDED
Example:
CQICOMPENSATED = 10
Actual service 384 K
Requires 768 bits per TB
CQINEEDED = 8
Power reduction = (10 – 8) dB = 2 dB
RAN1244: Spectral Efficient Link Adaptation
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 39 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 39
0
5
10
15
20
25
30
-15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5
CPICH Ec/Io (dB)
Co
mp
en
sa
ted
Ch
an
ne
l Qu
alit
y In
dic
ato
r (C
QI)
PtxMaxHSDPA = 30 dBm
PtxMaxHSDPA = 35 dBm
PtxMaxHSDPA = 40 dBm
Compensated
Reported
CQI as a function of CPICH Ec/Io
Measurement Examples (1/2)
• CQI improves both with increasing:
– EC/I0
– HSDPA power
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 40 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 40
• CQI estimation differs from one type of UE to the next one
Prediction of different values in spite of identical channel conditions
• CQI compensation capable to remove most of these differences
Almost same service experienced in spite of proprietary CQI estimation
0
5
10
15
20
25
30
-15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3
CPICH Ec/Io (dB)
Ch
an
ne
l Qu
alit
y In
dic
ato
r (C
QI)
Samsung zx20
Novatel U740
Common Channel
Loaded
Unloaded
0
5
10
15
20
25
30
-15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3
CPICH Ec/Io (dB)C
om
pe
ns
ate
d C
ha
nn
el Q
ua
lity
Ind
ica
tor
(CQ
I)
Samsung zx20
Novatel U740
Common Channel
Loaded
Unloaded
Prior to compensation After compensation
Measurement Examples (2/2)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 41 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 41
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 42 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 42
R99 & HSDPA Retransmission
Terminal
BTS
R99 DCH R5 HS-DSCH
Packet
Re-transmission
RLC ACK/NACK
Re-transmission
L1 ACK/NACK
Packet
Terminal
BTS
RNC RNC
Da
tafl
ow
DL control moved to BTS
H-ARQ: Hybrid Automatic
Repeat reQuest
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 43 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 43
Hybrid Automatic Repeat Request H-ARQ
• H-ARQ Objective: – ensures reliable data transfer between UE and Node B
– short Round Trip Time between UE and network
• HSDPA connection re-transmission can originate from: – MAC-hs layer between UE and Node B (HARQ)
– RLC layer between UE and RNC
– TCP layer between UE and application server
• Re-transmission time out – after 3rd L1 re-transmission HSDPA packet discarded (hardcoded threshold)
• HARQ algorithms:
– Chase combining CC
– Incremental Redundancy IR
Algorithm selected by operator on BTS level
HARQRVConfiguration
WBTS; 0 = Chase Combining,
1 = Incremental Redundancy
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 44 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 44
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
– Scheduling Types: Round Robin & Proportional Fair
– Scheduling & Code Multiplexing
– Basics of QoS Aware Scheduling and Application Aware RAN
– In-bearer Application Optimization
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 45 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 45
Basic Scheduler Types
• Supports packet schedulers
– Round Robin RR
– Proportional Fair PF (requires individual license)
– Type of scheduler set by HSDPA.BB.Resource.Allocation commissioning parameter
Round Robin Scheduler
• assigns sub-frames in rotation
– User at cell edge served as frequently as user at cell centre
• does not account for channel conditions experienced by UE
– Low total throughput in cell
• if no data have to be transferred from Node B to certain UE then the sub-frame is assigned to the next one
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 46 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 46
Proportional Fair PF Scheduler
TTI 1 TTI 2 TTI 3 TTI 4
USER 1 Es/N0 USER 2 Es/N0
Scheduled user
• Takes into account multipath fading conditions experienced by UE
– Improved total throughput in cell in comparison to round robin
• Sub-frames assigned according scheduling metric
– Ratio instantaneous data rate / average data rate experienced in the past
– User at cell edge served less frequently as user at cell centre
Estimate of instantaneously supported user
throughput
Based on compensated CQI
Calculated average user throughput in the past
Throughput measured every 10 ms with 100 ms
sliding window
ave
inst
TP
TP
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 47 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 47
Scheduling / HSDPA Code Multiplexing
UE1 UE2 UE3
Amount of
data in buffer
UE1 UE2 UE3
Full buffer Different data amounts
7
8
7
8
RU10 & later
15 codes 2
10
5
8
3
10
Codes & power are divided
optimally between users
depending on data amount.
MaxNbrOfHSSCCHCodes Max. number of HS-SCCH codes
WCEL; 1..4*; 1; 1
(no Code Multiplexing)
HSDPA Code Multiplexing: enables simultaneous transmission of up to 4* HSDPA UEs during 1 TTI
– each simultan. served HSDPA UEs must have separate HS-SCCH
– ≥ 5 codes must be allocated to HS-PDSCH
– MAC-hs entity selects (3) best users (based on PF or QoS aware metric)
for transmission in the next TTI
– HS-PDSCH codes & power resources shared, taking into account: how much data user has in its buffer
Channel conditions of user
* 3 before RU20
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 48 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 48
Basics of QoS Aware Scheduling
• Shortcomings of standard PF
– PF metric does not distinguish between traffic classes
– No bit rate guarantee, i.e. no streaming services supported
– Interactive service not prioritised against background one
• Idea of QoS aware HSPA scheduling (RAN1262)
– QoS aware HSPA scheduling enabled with parameter HSPAQoSEnabled
– HSDPA dynamic resource allocation must be enabled
– Streaming services
Guaranteed bit rate set by RNC
– Interactive IA & Background BG services
Operator can set nominal bit rate (target minimum bit rate)
If not defined, service treated as best effort one
Operator can set service priorities, so that IA services are scheduled more often than BG ones
Services belonging to same traffic class again scheduled according PF
HSPAQoSEnabled WCEL; 0..4;1; 0 = disabled
0 = QoS prioritization is not in use for HS transport
1 = QoS prioritization is used for HS NRT channels
2 = HSPA streaming is in use (RAN1004)
3 = HSPA CS voice is in use (RAN1689)
4 = HSPA streaming and CS voice are in use
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 49 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 49
Basics of QoS Aware Scheduling
• Guaranteed Bit Rate GBR
– Set by RNC for streaming services on basis of the RAB profile
• Nominal bit rate NBR = target minimum bit rate
The nominal bit rate NBR is set as the target minimum bit rate in the RNC for NRT HS-DSCHs.
– Can be specified by operator for NRT services
Individually for each SPI 0..12 and Individually for UL and DL
If Application Aware RAN is enabled SPI is dynamically modified by the RNC PDCP layer but the new NBR value
corresponding to the new SPI is not communicated to the BTS and BTS continues using the old NBR value. RNC
ensures that the SPI promotion/demotion for NBR users is performed within the SPI range defined for NBR users
NBR: Nominal Bit Rate
NBRForPri0..12UL UL NBR for Priority value 0..12 (structured parameter)
RNHSPA; 0..2000 K; 8 K; 0 K for all priority values
NBRForPri0..12DL DL NBR for Priority value 0..12
RNHSPA; 0..2000 K; 8 K; 0 K for all priority values
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 50 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 50
Application Aware RAN – Principle
Application Aware RAN
• Equips operators with QoS tools for typical terminals carrying multiple
applications within one bearer with HSDPA allocated
• Enables prioritization of the latency sensitive data by increasing
the scheduling priority at the air interface and/or demotion of
non-priority P2P traffic (priority drop = P2P traffic share down),
and introduces dynamic demotion of UL bulk traffic by the BTS in a single RAB case
• Applications requiring the same treatment at RAN are grouped
by the operator into Application Groups (up to 6) characterized
with AARConfigTable (consisted of AppGrpId, DSCPCode1..5
(up to 5 applications per group), Precedence, TargetSPIforSPI0..11)
• Precedence value determines what SPI should be chosen when packets
belonging to multiple application groups are detected by the RNC
(promote/demote/do nothing)
Shortcomings of available 3GPP QoS model:
• 3GPP bearer-based QoS differentiation model is not widely supported by typical terminals connecting with
single PDP context carrying all applications within one bearer.
• Subscriber level QoS does not separate different applications within single bearer; although each
application has different requirements when utilizing a bearer.
AppAwareRANEnabled WCEL; Disabled (0), Enabled (1); 0
Precedence RNHSPA; 1..6; 1; 255 = not defined
AppGrpId RNHSPA; 1..6; 1; 255 = not defined
DSCPCode1..5 RNHSPA; 0..62; 1; 255 = not defined
TargetSPIforSPI0..11 RNHSPA; 0..11; 1; 255 = not defined
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 51 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 51
Application Aware RAN – NSN implementation
Application Aware RAN solution is implemented in 2 network elements GGSN and RNC
1. In GGSN: Core network based DPI (Deep Packet Inspection) provides application detection and inner (user) IP packet
marking with DSCP (Differential Service Code Point - a field in the IPv4 and IPv6 header)
DSCP of user packet is marked
based on PCC rule action
2. In RNC: Initial Scheduling Priority Indicator of the radio bearer is demoted or promoted in the RNC PDCP layer
according to Deep Packet Inspection marking (DSCP marking).
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 52 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 52
QoS Aware Scheduling and Application Aware RAN (1/2)
• Scheduling weights
– For each combination of RAB QoS parameters operator can define service priority Traffic class
Traffic handling priority THP
Allocation & retention priority ARP
– Service priorities & Scheduling Priority Indicators SPI Defined by multiple parameter QoSPriorityMapping
For services on DCH service priorities just define values entering queuing and priority based scheduling (see R99
PS)
For services on HS-DSCH/E-DCH or HS-DSCH/DCH services priorities define directly SPI
• It is initial SPI value if AppAwareRANEnabled = 1 (dynamic SPI based on the application type and initial SPI value
is set and communicated to BTS using CmCH-PI field in Frame Protocol)
If HSPAQoSEnabled is disabled but AppAwareRANEnabled = 1 then initial SPI for services with HSDPA can be
configured by the operator with is defined by InitialSPINRT; RNHSPA; SPI 5 (5), SPI 6 (6); SPI 5 (5)
– SPI mapped onto scheduling weights: define how often service of certain QoS parameter set scheduled in comparison to another one with another
QoS parameter set
PF scheduling extended by required
activity detection RAD with delay sensitivity DS
Priority for Streaming traffic class with ARP1/2/3:
PriForStreamARP1/2/3 (RNPS) (0..15) ( = 1) (13/13/13)
Priority for Interactive TC with THP 1 & ARP 1/2/3:
PriForIntTHP1ARP1/2/3 (RNPS) (0..11) ( = 1) (11/11/11)
Priority for Interactive TC with THP 2 & ARP 1/2/3:
PriForIntTHP2ARP1/2/3 (RNPS) (0..11) ( = 1) (8/8/8)
Priority for Interactive TC with THP 3 & ARP 1/2/3:
PriForIntTHP3ARP1/2/3 (RNPS) (0..11) ( = 1) (5/5/5)
Priority for Background TC with ARP 1/2/3:
PriForBackARP1/2/3 (RNPS) (0..11) ( = 1) (0/0/0)
ARP: Allocation & retention priority
SPI: Scheduling priority indicators
THP: Traffic handling priority
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 53 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 53
QoS Aware Scheduling and Application Aware RAN (2/2) • Mapping QoS parameter for DCH
QoS parameter
RAB profile
Service
priority
Mapping defined
by QoSPriorityMapping
RNC PS
Queuing
Priority Based Scheduling
• Mapping QoS parameter to scheduling weights for HS-DSCH/E-DCH or HS-DSCH/DCH
QoS parameter
RAB profile Service priority
Mapping defined
by QoSPriorityMapping
Node B PS:
Scheduling weight
modifying PF
SPI: Scheduling Priority Indicators
Mapping defined by
SchedulingWeightList
SchedulingWeightList • is BTS commissioning parameter
• defining Mapping QoSPriorityMapping to
SchedulingWeight
If AppAwareRANEnabled = 1 then dynamic SPI setting
based on the application type and initial SPI
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 54 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 54
In-bearer Application Optimization
In-bearer Application Optimization introduces service prioritization within one downlink radio access bearer.
User traffic marked as latency sensitive is scheduled differently and is prioritized ahead of non-latency sensitive traffic inside RNC.
GTP-U Payload
User IP payload User IP header DSCP
GT
P-U
Hea
de
r
UD
P
Hea
de
r
IP
Header
DSCP of user packet is marked
according to DPI rules
In Core network:
Mobile
Network The Internet
HTTP
P2P
Priority packets (e.g. HTTP) get
more bandwidth within RAB
Promoted traffic
Demoted traffic
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 55 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 55
In-bearer Application Optimization
Background download
RAB Bandwidth
Time
Web page
Background
download
RAB Bandwidth
Time
Web
page
T1
T2
More instantaneous bandwidth granted for prioritized applications’ packets leads to minimized download time in comparison to download time without RAN2510
Without RAN2510
With RAN2510
(T2 < T1) Improved download time BETTER QUALITY OF EXPERIENCE
Without RAN2510 only generic 3GPP QoS differentiation is possible on RAB level. No content detection with prioritization is
possible.
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 56 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 56
In-bearer Application Optimization
PDCP
RNC
RNC
PDCP HQ
LQ
S
RLC
MAC
Phy
NodeB
New entities in PDCP: HQ, LQ, S.
In Radio network:
Application marking
Weighted Fair Queueing High priority queue (marked blue), served with
bigger weight, resulting in lower delay time and
higher bandwith for the higher priority packets than
for lower priority packets
TPU DPI
Core Network
Internet
In-bearer Application Optimization can be enabled with InBearerAppPrioEnabled Parameter.
InBearerAppPrioEnabled. WCEL; Disabled (0), Enabled (1);
IBAOHighQueueWeight RNHSPA; 50...100 %, step 10 %, 50%
IBAODSCPHighPrioQPart1
RNHSPA; Bit 0: DSCP0,
Bit 1: DSCP1,
Bit 2: DSCP2,
......
Bit 31: DSCP31
The parameter IBAOHighQueueWeight defines the weight for the high PDCP Priority Queue.
The DSCP code values for PDCP priority high queue are defined by the IBAODSCPHighPrioQPart1 (DSCPs 0 to 31) and IBAODSCPHighPrioQPart2 (DSCPs 32 to 63)
IBAODSCPHighPrioQPart2
RNHSPA; Bit 0: DSCP32,
Bit 1: DSCP33,
Bit 2: DSCP34,
......
Bit 31: DSCP63
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 57 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 57
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
– HS-SCCH & HS-DPCCH Power Control – Static & Dynamic HS-PDSCH Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 58 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 58
Overview HS-PDSCH High-Speed Physical DL Shared Channel
HS-SCCH Shared Control Channel for HS-DSCH
associated DCH* Dedicated Channel
HS-DPCCH Dedicated Physical Control Channel (UL) for HS-DSCH
Static power allocation
Tx power „fixed“
Slowly adjusted in dependence on HS-SCCH Tx power
Dynamic power allocation
All power not needed for R99 services available for HSDPA
Slowly adjusted in dependence on R99 & HSDPA traffic
Fast power control in dependence on:
- CQI
- Feedback of UE
Fast power control parallel to DPCCH with offset for CQI
ACK/NACK
Inner loop PC basing DL TPC and CQI
WBTS UE
F-DPCH* Fractional Dedicated Physical Channel
* F-DPCH can be allocated in
DL only if SRB can be
mapped to HSPA channels
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 59 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 59
Example:
PCPICH + Γ = 6 W (37.8 dBm)
P0 = 0
CQI TBS Throughput CQI PHS-SCCH
4 317 159 K -7.7 dB (37.8 - 7.7) dBm = 30.1 dBm (1.0 W)
13 2279 1140 K -16.6 dB (37.8 - 16.6) dBm = 21.2 dBm (0.13 W)
HS-SCCH inner loop power control algorithm
• Node B estimates HS-SCCH Tx power according to: PHS-SCCH = PCPICH + Γ + CQI + P0
HS-SCCH Power Control (1/3)
– PCPICH: CPICH power
– Γ measurement power offset
(see section link adaptation)
– CQI: power offset taken from CQICOMPENSATED by
look up table (next slide)
– P0: correction estimated by HS-SCCH outer
loop power control algorithm
• HS-SCCH Tx power – Estimated for each HSDPA connection
individually
– Updated with each CQI report
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 60 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 60
HS-SCCH Power Control (2/3)
HS-SCCH outer loop power control algorithm
• With each feedback (ACK or NACK) from UE
– Correction P0 decreased by 0.005 dB
– But not below -2 dB (maximum power decrease by factor 1.6)
• If there is no feedback from UE
– Correction P0 increased by 0.5 dB
– But not above 4 dB (maximum power increase by factor 2.5)
ACK or NACK
No feedback
time
P0
0.005 dB
0.5 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 61 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 61
HS-SCCH Power Control (3/3)
0
2000
4000
6000
8000
10000
12000
14000
16000
18000
0 100 200 300 400 500 600 700 800 900 1000
HS-SCCH Tx Power (mW)
Oc
cu
ran
ce
s
PtxMaxHSDPA = 30 dBm
PtxMaxHSDPA = 35 dBm
PtxMaxHSDPA = 40 dBm
0
5000
10000
15000
20000
25000
30000
0 100 200 300 400 500 600 700 800 900 1000
HS-SCCH Tx Power (mW)
Oc
cu
ran
ce
s
PtxMaxHSDPA = 30 dBm
PtxMaxHSDPA = 35 dBm
PtxMaxHSDPA = 40 dBm
Variance of HS-SCCH Tx power in relatively poor channel conditions
Variance of HS-SCCH Tx power in relatively good channel conditions
• HS-SCCH Tx power increases
– in poor channel conditions
– with higher HS-PDSCH Tx power
• Link budgets typically assume 0.5 W HS-SCCH Tx power at cell edge
Static Power Allocation
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 62 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 62
• Power offsets
– HS-DPCCH Tx power goes parallel to that of DPCCH
– for ACK / NACK & CQI fields hardcoded power offsets in dependence on DPDCH data rate (16 / 64 / 128 / 384 K)
– for UL link budgets ACK / NACK offset more important than CQI one
HS-DPCCH Power Control
DPCCH
DPDCH
Factor
2.7 dB for 16 K DPDCH
9.5 dB for 384 K DPDCH CQI ACK/NACK
HS-DPCCH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 63 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 63
HS-PDSCH Power Allocation
Static Power Allocation Dynamic Power Allocation
• PHSDPA ≤ PtxMaxHSDPA PHSDPA ≤ min(PtxMaxHSDPA, PtxCellMax)- power
allocated to R99 DCH & DL control channels
• Fixed load target PtxTargetHSDPA Dynamically adjusted load target PtxTargetPS
• Fixed overload threshold for R99 Overload threshold for R99 goes parallel to load target:
PtxTargetHSDPA + PtxOffsetHSDPA PtxTargetPS + PtxOffset
• In case of overload HSDPA might be In case of overload HSDPA power might be reduced,
released immediately but usually service not released immediately
• Priorities distinguish between R99 & Priorities distinguish between interactive & background
• HSDPA users only users as well
PtxMaxHSDPA Maximum allowed HSDPA power
WCEL; 0..50 dBm; 0.1 dB; 43 dBm
PtxTargetHSDPA Target for transmitted non-HSDPA power
WCEL; -10..50 dBm; 0.1 dB; 38.5 dBm
PtxOffsetHSDPA Offset for transmitted non-HSDPA power
WCEL; 0..6 dB; = 0.1 dB; 0.8 dB
HSDPADynamicResourceAllocation HSDPA Dynamic Resource Allocation
RNFC; 0 = disabled; 1 = enabled
PtxCellMax Cell maximum transmission power
WCEL; 0 .. 50 dBm; 0.1 dB; 43 dBm
PtxOffset Offset for transmitted power
WCEL; 0 .. 6 dB; 0.1 dB; 1 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 64 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 64
• BTS may allocate all unused DL power up to maximum cell power
• all power available after DCH traffic, HSUPA control & common channels can be used for HSDPA
PtxNC
PtxNRT
PtxHSDPA
PtxMax = min (PtxCellMax, MaxDLPowerCapability)
PtxNonHSDPA
Dynamic HS-PDSCH Power Allocation
PtxCellMax
Cell maximum transmission power
0..50 dBm; 0.1 dB; 43 dBm
MaxDLPowerCapability: 0..50 dBm; 0.1 dB; -
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 65 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 65
Dynamic HS-PDSCH Power Allocation
No active HSDPA users
• NRT DCH scheduling to – PtxTarget + PtxOffset if HS-RACH isn’t set up in the cell
– PtxTargetPS if HS-RACH is set up in the cell
• RT DCH admission to PtxTarget
Active HSDPA users
• NRT DCH scheduling to PtxTargetPS
• RT DCH admission to – PtxTarget no RT HS-SDCH
– PtxTargetTot at least 1 RT HS-DSCH
HSDPA active No HSDPA users No HSDPA users
PtxTarget + PtxOffset
PtxMax
PtxTargetPS
PtxNC
PtxNRT
PtxHSDPA
1
2
3
PtxNonHSDPA
PtxTotal
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 66
Dynamic HS-PDSCH Power Allocation
• Adjustable load target PtxTargetPS
– PtxTargetPSMin (minimum value)
– PtxTargetPSMax (maximum value, also initial value, HS-RACH is set up in the cell)
– PtxTargetPSMaxtHSRACH (maximum value used if HS-RACH is set up in the cell)
PtxTargetPSMin Min DCH PS target for dynamic HSDPA pwr allocation
WCEL; -10..50 dBm; 0.1 dB; 36 dBm
PtxTargetPSMax Max DCH PS target for dynamic HSDPA pwr allocation
WCEL; -10..50 dBm; 0.1 dB; 40 dBm
PtxTargetPSMaxtHSRACH Max DCH target power level with HS-RACH for dynamic HSDPA pwr allocation
WCEL; 0..40 dBm; 0.1 dB; 32767 dBm (Value set by the PtxTargetPSMax parameter used when the HS-RACH has been setup in
the cell)
PtxNC
PtxNRT
PtxHSDPA
PtxMax
PtxNonHSDPA
PtxTargetPSMin (36 dBm)
PtxTargetPSMax (40 dBm)
PtxTargetPS
PtxTargetPSMin -10..50 dBm; 0.1 dB; 36 dBm
PtxTargetPSMax -10..50 dBm; 0.1 dB; 40 dBm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 67
Dynamic Load Target
Ideal load target: Ideal_PtxTargetPS
• Dynamic load target adjusted if
– High DCH load or total load AND
– Current load target deviates from ideal load target
• Ideal load target estimated by RNC in dependence on
– Non controllable traffic PtxNC = total non-controllable transmitted DCH power - power used by all HSDPA streaming users of the cell - non-controllable HSDPA power
– NRT DCH traffic (sum over all weights of R99 services WeightDL_DCH)
– NRT HS-DSCH traffic (sum over all weights of HSDPA services WeightHS-DSCH)
Target
Target
WeightWeight
Weight
MinTarget_ DL_DCHDSCH-HS
DL_DCH
PSMinPtx
PSMaxPtx
PtxNCPtxMaxPtxNC
MaxPSPtxIdeal
PtxTargetPSMaxtHSRACH
if HS-RACH is set up in the cell
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 68 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 68
Dynamic Load Target
Weights of individual services
• Can be set individually for each release
– R99 (structured parameter WeightDCH)
– HSPA (structured parameter WeightHSPA)
• Can be set individually for each traffic class
– Interactive THP1, THP2, THP3
– Background
• In case of multi-RAB the average weight of the individual RABs is taken for that user
Structured parameter WeightDCH
Weight of NRT DCH UE BG RAB
WeightDCHBG (RNHSPA) (0..100) ( = 1) (15)
Weight of NRT DCH UE THP1/2/3 RAB
WeightDCHTHP1/2/3 (RNHSPA) (0..100) ( = 1) (90/65/40)
Structured parameter WeightHSPA Weight of HSPA UE BG RAB
WeightHSPABG (RNHSPA) (1..100) ( = 1) (25)
Weight of HSPA UE THP1/2/3 RAB
WeightHSPATHP1/2/3 (RNHSPA) (0.100) ( = 1) (100/75/50)
15 25 Background
40 50 Interactive THP3
65 75 Interactive THP2
90 100 Interactive THP1
DCH weight value 0…100
HSDPA weight value 0…100
Traffic Class
Ideal Load Target - Example
• 2 HS-DSCH users interactive THP1 + background
WeightHS-DSCH = 100 + 25 = 125
• 3 DCH users background
WeightDL_DCH = 3 * 15 = 45
• PtxMax = 43 dBm
• PrxNC = 37 dBm
Ideal_PrxTargetPS = 37 dBm + (45 / (125 + 45)) * (43 dBm
- 37 dBm) = 38.6 dBm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 69 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 69
Load Target Adjustment
• Required information
– Total power PtxTotal measured by Node B
– Non HSDPA power PtxNonHSDPA measured by Node B
– Both averaged according PSAveragingWindowSize (same parameter as for R99)
• Need for adjustment checked periodically according PtxTargetPSAdjustPeriod
• If adjustment needed
– Increase by PtxTargetPSStepUp in case of DCH congestion
– Decrease by PtxTargetPSStepDown in case of HSDPA congestion
PSAveragingWindowSize
Load measurement averaging window size for PS WBTS; 1..20; 1; 4 scheduling periods
PtxTargetPSAdjustPeriod DCH PS target adjust period for dyn HSDPA power
alloc; WBTS; 1..255; 1; 5 RRI periods
PtxTargetPSStepUp DCH PS target step up for dynamic HSDPA pwr alloc.
WCEL; 0..5; 0.1; 1 dB
PtxTargetPSStepDown DCH PS target step down for dynamic HSDPA pwr alloc.
WCEL (0..5 dB) ( = 0.1 dB) (1 dB)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 70 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 70
Actions in Case of Congestion
DCH congestion only
• Increase PtxTargetPS by PtxTargetPSStepUp, if currently below ideal load target (but not
above PtxTargetPSMax)
HSDPA congestion only
• Decrease PtxTargetPS by PtxTargetPSStepDown, if currently above ideal load target (but
not below PtxTargetPSMin)
Both DCH & HSDPA congestion
• Increase PtxTargetPS, if currently below ideal load target
• Decrease PtxTargetPS, if currently above ideal load target
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 71 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 71
PtxMax 43 dBm
PtxTargetPS
PtxNC
PtxNRT
PtxTotal
PtxTargetPS_ideal
Example: HSDPA congestion
1) HSDPA power congestion, if
Ptxtotal ≥ PtxHighHSDPAPwr
High threshold of PtxTotal for dynamic HSDPA pwr alloc:
PtxHighHSDPAPwr (WCEL) (-10..50 dBm) ( = 0.1 dB) (41 dBm)
PtxTargetPSMin -10..50; 0.1; 36 dBm
PtxTargetPSMax -10..50; 0.1; 40 dBm
PtxHighHSDPAPwr -10..50; 0.1; 41 dBm
Decrease by PtxTargetPSStepDown
in case of HSDPA congestion
PtxTargetPSStepDown 0..5; 0.1; 1 dB
PtxHSDPA
1
2
PtxNonHSDPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 72 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 72
2) NRT DCH power congestion, if
PtxNonHSDPA ≥ PtxTargetPS - 1dB (hardcoded margin)
PtxMax 43 dBm
PtxTargetPS
PtxNC
PtxNRT
PtxTotal
PtxTargetPS_ideal
Example: DCH Congestion
PtxTargetPSMin -10..50; 0.1; 36 dBm
PtxTargetPSMax -10..50; 0.1; 40 dBm
PtxTargetPSStepUp 0..5; 0.1; 1 dB
Increase by PtxTargetPSStepUp
in case of DCH congestion
PtxHighHSDPAPwr -10..50; 0.1; 41 dBm
PtxHSDPA
1
2
PtxNonHSDPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 73 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 73
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection and Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 74 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 74
Static & Dynamic Allocation (1/3)
HSPDSCHCodeSet
11010 10100 100000
HSPDSCHCodeSet
00000 10100 100000
HSPDSCHCodeSet
00000 00000 100000
Additionally required
HSDPADynamicResourceAllocation = enabled
Number of HS-
PDSCH codes (full
set)
HSDPA
15
Codes
HSDPA
10
Codes
Static
code
allocation
5 X X X
6 - - -
7 - - -
8 X X -
9 - - -
10 X X -
11 - - -
12 X - -
13 - - -
14 X - -
15 X - -
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 75 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 75
Static & Dynamic Allocation (2/3)
Dynamic code allocation applied if:
• HSDPA dynamic resource allocation enabled (HSDPADynamicResourceAllocation)
• Maximum number of codes > minimum number (HSPDSCHCodeSet)
• BTS capable of 10/15 codes
• HSDPA service starts with minimum number of codes defined by HSPDSCHCodeSet
• Cell-specific scheduler reserves HS-SCCH codes from the spreading code tree according to MaxNbrOfHSSCCHCodes
If HSDPA dynamic resource allocation disabled, 5 codes are available only
SF=8
SF=4
SF=2
SF=1
SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
HS - PDSCH
………. ……….
SF=8
SF=4
SF=2
SF=1
SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
HS - PDSCH Rel - 99 channels (& HS - SCCH)
Rel - 99 code area (& HS - SCCH)
Shared code area
Dedicated HS - PDSCH
SF=8
SF=4
SF=2
SF=1
SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
HS - PDSCH
………. ……….
SF=8
SF=4
SF=2
SF=1
SF=16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
HS - PDSCH Rel - 99 channels (& HS - SCCH)
Rel - 99 code area (& HS - SCCH)
Shared code area
Dedicated HS - PDSCH code area
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 76 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 76
Static & Dynamic Allocation (3/3)
128 128 128
Available CC Allocated CC Blocked CC
SF16
SF32 32
SF64 64 64 64
SF256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256
128 128 128 128 128 128 128 SF128
+14 x SF16
HS-PDSCH
CPICH AICH
S-CCPCH1
S-CCPCH2 HS-SCCH HS-SCCH HS-SCCH
32
64 64
256 256 256 256 256 256 256 256
128 128 128 128
SF16
E-RGCH E-HICH
E-AGCH
Maximum of 14 HS-PDSCH codes possible with 3 HS-SCCH & HSUPA
P-CCPCH PICH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 77 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 77
Dynamic Allocation Procedure (1/2)
Periodic upgrade
• HSDPA service starts with minimum number of codes
• RNC attempts periodic upgrade according the timer HSPDSCHAdjustPeriod if
• Number of currently allocated HS-PDSCH codes < maximum allowed number supported
by BTS capability
• Free SF 16 codes adjacent to currently allocated ones available
• After upgrade enough SF 128 codes available according HSPDSCHMarginSF128
• If all conditions are fulfilled, the next greater value from HS-PDSCH code set
is taken
Periodic downgrade
• RNC attempts periodic downgrade according the timer HSPDSCHAdjustPeriod if
• Number of currently allocated HS-PDSCH codes > minimum allowed number
• Not enough SF 128 codes available according HSPDSCHMarginSF128
• If all condition fulfilled, the next lower value from HS-PDSCH code set is taken
HSPDSCHMargin
SF128 WCEL; 0..128; 1; 8
# SF128 codes to be available
after Code upgrade
HSPDSCHAdjustPeriod RNHSPA; 1..60; 1; 10s
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 78 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 78
Dynamic Allocation Procedure (2/2) N
um
ber
of
allo
cate
d S
F16 c
od
es
DPCHOverHSPDSCHThreshold
set relative to max. number of codes
6
7
8
9
10
11
12
13 14
15 Maximum code set
5
• Code congestion events
– RT request congested due to lack of code HS-PDSCH downgrade in any case
– NRT request congested due to lack of code HS-PDSCH downgrade only, if actually for HSDPA too much SF 16 codes in use according DPCHOverHSPDSCHThreshold
• Limitations of congestion triggered downgrade
– Not below minimum allowed number of HS-PDSCH codes
– Highest still possible number of codes according HSPDSCHCodeSet is taken
Minimum code set
HSPDSCH
CodeSet WCEL; 5..15; 1; 5
DPCHOver
HSPDSCHThreshold WCEL; 0..10; 1; 5
Code tree optimization
• Code tree optimization procedure tries to re-arrange DPCH codes to
make room for HS-PDSCH code upgrade • DPCHs having SRB DCH only are not allowed to be re-arranged
CodeTreeOptimisation WCEL; 0 = disabled; 1 = enabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 79 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 79
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• HSDPA Power Allocation
• HSDPA Code Allocation (Basics)
• HSDPA Mobility – Serving Cell Change
– HSPA+ over Iur
– Inter-RNC Mobility
– Inter-frequency Mobility
– Directed RRC Connection Setup
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 80 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 80
Parameter Templates
FMCS/I/GId identifies parameter set for intra-, inter-frequency & inter-system
measurements
FMCS/G/I; 1..100; 1; no default
HSDPAFMCS/I/GIdentifier Identifies FMCS/I/G parameter set to be applied for a HSDPA service
within a certain serving cell
WCEL; 1..100; 1; no default
RTwithHSDPAFMCS/I/GIdentifier HSDPA FMCS/I/G identifier for AMR multi-service
WCEL; 1..100; 1; no default
Identifies FMCS/I/G parameter set to be applied for a HSDPA + AMR
multi-RAB service within a certain serving cell
S:Intra- Frequency
I:Inter- Frequency
G:Inter- System
WCELL
ADJG / L
ADJI
ADJS
WBTS
RNC
FMCS
FMCI
FMCG
100
100
100
HOPS 100
HOP I 100
HOPG 100
32
48
32
ADJD
HOPS 100
32
HOPSId HOPS identifier: identifies parameter set for intra-frequency mobility
HOPS; 1..100; 1; no default
HSDPAHOPSIdentifier ADJS; 1..100; 1; no default
identifies parameter set to be applied for a HSDPA service to move to a
certain adjacent cell
RTwithHSDPAHOPSIdentifier HSDPA HOPS identifier for AMR multi-service
ADJS; 1..100; 1; no default
RNFC
RNMOBI
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 81 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 81
HSDPA Mobility
Serving Cell Change SCC (1/5): Candidate
Initial cell selection
• 1 cell active only: just attempt to establish service
• More than 1 cell active
– Initial selection of Serving Cell based on latest reported Ec/I0
– To be candidate, HSDPA capable cell must fulfil following condition:
– Serving cell is chosen in order of EC/I0
– If allocation of HS-DSCH fails due to any reason, next best candidate cell is attempted
EC/I0 (active cell*) ≥ EC/I0 (best cell) – HSDPAServCellWindow
HSDPAServCellWindow CPICH Ec/Io window for serving HS-DSCH
cell selection
RNMOBI; 0..6; 0.5; 2 dB
* Serving Cell
Max. allowed difference between the best cell in the Active Set & the Serving HSDSCH cell.
If Serving HS-DSCH cell out of this window Serving HS-DSCH cell change procedure initiated.
Methods to handle HSDPA mobility
• Serving HS-DSCH cell change
• Cell reselection
with HS-DSCH - FACH channel type switching ( Appendix)
HSDPAMobility Serving HS-DSCH cell change & SHO on/off switch
RNFC; 0 = HSDPA cell reselection
1 = Serving HS-DSCH cell change
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 82 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 82
Serving Cell Change: Ec/Io based • Periodical Intra-frequency EC/I0 measurements started when:
– HS-DSCH MAC-d flow active AND Active set size > 1 (event 1a)
– Measurements stopped if either of the above criteria not true
• CPICH EC/I0 measurement reporting by UE:
– Higher layer filtering for measurement results before reporting by
EcNoFilterCoefficient
– Periodical reporting with reporting interval defined by
HSDPACPICHReportPeriod
– RNC averages reports over HSDPACPICHAveWindow
• EC/I0 based Serving Cell change triggered if:
– Ec/I0 (server) < EC/I0 (best cell) – HSDPAServCellWindow AND
– EC/I0 (server) < HSDPACPICHEcNoThreshold
EcNoFilterCoefficient FMCS; k = 0..6; 1; k = 3
HSDPACPICHReportPeriod RNMOBI; 0.25, 0.5, 1, 2, 3, 4, 6, 8,
12; 0.5 s
HSDPACPICHAveWindow RNMOBI; 1..10; 1; 3
Addition
window
CPICH 1
CPICH 2
EC/I0
time New cell
detected
Periodic
reports
Serving cell change
EC/I0 threshold
Serving cell change
triggered
periodic reports as long
process is running
HSDPAServCellWindow Serving Cell change window
RNMOBI; 0..6; 0.5; 2 dB
HSDPACPICH
EcNoThreshold RNHSPA; -20..0; 0.5;-5 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 83 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 83
Serving cell change
triggered
Serving Cell Change: SIR error based
• SIR error based Serving Cell change triggered if:
SIRerror (Server) < HSDPASIRErrorServCell
SIRerror
time
Periodic reports as long
HSDPA service running
Serving cell change
SIRerror threshold
HSDPA service
established
HSDPASIRErrorServCell RNMOBI; -10..0; 0.5; -3 dB
• for Inter Node B & intra Node B inter-LCG cell change only (not applicable for intra Node B intra-LCG )
• Periodical SIR error measurements started when
– HS-DSCH MAC-d flow active
– difference between actual SIR & SIRtarget: SIRerror = SIR – SIRtarget
• Measurement reporting by Node B
– Higher layer filtering for measurement results before reporting by
HSDPASIRErrorFilterCoefficient
– Periodical reporting with reporting interval defined by
HSDPASIRErrorReportPeriod (if set to 0 SIR measurement
is not used as criteria for SCC)
– RNC averages reports over HSDPASIRErrorAveWindow
HSDPASIRErrorFilterCoefficient RNMOBI; k = 0..10; 1; 5
HSDPASIRErrorReportPeriod RNMOBI; 0..10; 0.5; 0.5 s
HSDPASIRErrorAveWindow RNMOBI; 1..10; 1; 3
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 84 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 84
Method Trigger
AS update
Event 1B
Event 1C
Event 6F/6G
HO to D-RNC AS update for Serving Cell to D-RNC
Serving Cell Change: other trigger
on Serving Cell
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 85 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 85
Serving Cell Change
Target cell selection criteria
• Dynamic Resource Allocation disabled – Cell having HSDPA power allocated already chosen as serving cell
– Otherwise serving cell chosen in order of EC/I0
• Dynamic Resource Allocation enabled – Serving Cell is chosen in order of EC/I0
• If serving cell change triggered by Ec/I0 or SIRerror
– need SIRerror (target) ≥ HSDPASIRErrorTargetCell
• If triggered by other event:
– need SIRerror (target) ≥ HSDPASIRErrorServCell
HSDPASIRErrorTargetCell RNMOBI; -10..0; 0.5; -2 dB
Timing Constraints
• min. time interval between consecutive Serving HS-DSCH Cell changes
based on Ec/I0: HSDPACellChangeMinInterval
• max. number of repetitive Serving HS-DSCH Cell changes
HSDPAMaxCellChangeRepetition during predefined time period
HSDPACellChangeRepetitionTime
• if exceeded, HS-DSCH released & switched to DCH0/0 or DCH with initial bit
rate
HSDPACellChangeMinIn
terval RNMOBI; k = 0..10; 1; 3 s
HSDPACellChange
RepetitionTime RNHSPA; 0..60; 1; 10 s
HSDPAMaxCell
ChangeRepetition RNHSPA; 1..16; 1; 4
HSDPASIRErrorServCell RNMOBI; -10..0; 0.5; -3 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 86 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 86
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• HSDPA Power Allocation
• HSDPA Code Allocation (Basics)
• HSDPA Mobility – Serving Cell Change
– HSPA+ over Iur
– Inter-RNC Mobility
– Inter-frequency Mobility
– Directed RRC Connection Setup
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 87 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 87
UE
DRNC
SRNC
one PS NRT RAB
HSPA+ over Iur Introduction
• After the serving-cell change, HSDPA and HSUPA data is transmitted over the Iur.
• HSPA throughput over Iur restricted to 10Mbps in DL and 2Mbps in UL
• HSPAOverIur enables HSPA over Iur.
• The DRNC does not read the parameter HSPAOverIur but the license only.
• HSPA over Iur feature improves the end-user performance by maintaining the continuous high data rate HSPA service during the inter-RNC mobility.
• The possibility of setting up HSDPA/HSUPA MAC-d flows over Iur interface is introduced by the feature RAN1231 in RU20.
• Prior, HSDPA channel type switch to DCH is performed. (only DCH services are allowed over Iur).
HSPAOverIur IUR; 0 (HSPA over Iur disabled), 1 (HSPA over Iur enabled)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 88 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 88
HSPA+ over Iur Extension
• Extension of HSPA over Iur feature introduces additionally:
- the CS AMR on DCH + 1 PS NRT on HS(D)PA multi-RAB combination over Iur,
• and it can be enabled with HSPAOverIurExt (in RU40).
HSPAOverIurExt IUR; 0 (Disabled), 1 (Enabled)
SCC during anchoring (DRNC cell to DRNC cell)
allowed due to RAN2270
DRNC
SRNC
SGSN
HSDPA+
allowed
over Iur
• It allows:
- HS-DSCH and E-DCH Mac-d flow setup and release over Iur for single PS NRT RAB.
- The SRNC to set up the HS-DSCH and/or E-DCH RL over Iur during anchoring.
- The SRNC to perform SCC from DRNC cell to DRNC cell during anchoring.
- The SRNC can set up a single HS-DSCH and /or E-DCH Mac-d flow with CS AMR on DCH over Iur.
- The SRNC allows for the PS NRT RAB reconfiguration for HS-DSCH and E-DCH Mac-d flow over Iur.
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 89 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 89
HSPA+ over Iur RU50 New improvements (RAN2221)
• Introduces the following functionalities to the Iur interface:
- Flexible RLC in DL (FRLCOverIurEnabled)
- Dual-Cell HSDPA (DCHSDPAOverIurEnabled)
- HSDPA 64QAM (HSDPA64QAMOverIurEnabled)
• New HSDPA configurations supported over Iur:
- Single cell HSDPA with Flexible RLC DL (14Mbps)
- Single cell HSDPA (64QAM) with Flexible RLC DL (21Mbps)
- Dual cell HSDPA with Flexible RLC DL (28Mbps)
- Dual cell HSDPA (64QAM) with Flexible RLC DL (42Mbps)
- For RAN1231 HSPA over Iur throughput in DL was limited to 10Mbps.
DRNC
SRNC
SGSN
Up to
42 Mbps DL
2 Mbps UL
FRLCOverIurEnabled IUR; 0 (Disabled), 1 (Enabled)
DCHSDPAOverIurEnabled IUR; 0 (Disabled), 1 (Enabled)
HSDPA64QAMOverIurEnabled IUR; 0 (Disabled), 1 (Enabled)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 90 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 90
HSPA+ over Iur RU50 New improvements (RAN2221)
• Configurations are supported only with SRB on DCH.
• In case of SRB on HSPA reconfiguration to SRB on DCH is done before SCC.
• Configurations are supported only with one NRT PS RAB.
• HSUPACCIurEnabled enables the HSUPA Congestion Control for Iur E-DCH MAC-d flows in the SRNC, covering also DRNC's Iub part.
• Maximum Bit rate limitations are configured with:
- MaxIurNRTHSDSCHBitRate (DL),
- MaxTotalUplinkSymbolRate (UL)
DRNC
SRNC
SGSN
SRB on DCH
HSUPACCIurEnabled IUR; 0 (Disabled), 1 (Enabled)
MaxIurNRTHSDSCHBitRate IUR; 128...41984 kbps,
step 128 kbps; 75 kbps
MaxTotalUplinkSymbolRate WCEL; 960 kbps, SF4 (0),
1920 kbps, 2*SF4 (1),
3840 kbps, 2*SF2 (2),
5760 kbps, 2*SF2 + 2*SF4 (3)
960 kbps, SF4
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 91 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 91
HSPA+ over Iur RU50 New improvements (RAN2221)
• Anchoring:
• When HSPAOverIurExt is enabled the SRNC is allowed to:
- Setup HS-DSCH with Flexible RLC in DL, DC-HSDPA, and/or HSDPA64QAM over Iur
- perform Serving Cell Change from DRNC cell to DRNC cell with:
• Flexible RLC in DL, DC-HSDPA, and/or HSDPA64QAM without radio links in serving RNC.
- If there is an attempt to establish AMR call with the existing HSPA+ over Iur RAB:
• DC-HSDPA is reconfigured to SC-HSDPA for enabling AMR+HSPA over Iur.
- When there is an attempt to establish another PS RAB with the existing HSPA+ over Iur RAB,
• DRNC rejects the request by the failure code Requested Configuration not Supported.
DRNC
SRNC
SGSN
SRB on DCH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 92 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 92
HSPA+ over Iur Nokia and non-Nokia DRNC operation
DC-HSDPA SCC from SRNC to Nokia DRNC
Cell Capability Containers of the neighboring cells of the target cell, and for the target cell are send by DRNC
If Flexible RLC and DC-HSDPA (or HSDPA 64QAM) are supported, those will be used on the DRNC cell as well.
UE makes SCC to DRNC cell, with Flexible RLC DL and DC-HSDPA or HSDPA 64QAM (if supported).
DC-HSDPA SCC from SRNC to non-Nokia DRNC
Cell Capability Containers of the neighboring cells of the target cell are send by DRNC
If SRNC does not receive the HS-DSCH Support Indicator assumes that HS-DSCH is supported
If SRNC does not receive the E-DCH Support Indicator assumes that E-DCH is supported
If Cell Capability Container of the target cell is not received from DRNC, intra-frequency SCC over Iur shall be tried with existing RLC. But if new HSDPA is established, then fixed RLC is used.
UE makes SCC to DRNC cell, with SC-HSDPA.
• Neighboring RNC settings (Nokia to non-Nokia RNC) are configured with InterfaceMode and the Neighboring RNC settings for Nokia need to be NRncVersion = Rel 9 or higher.
InterfaceMode IUR; 3GPP, Nokia (0), Mode 1 (1),
Mode 2 (2), Mode 3 (3), Mode 4 (4),
Mode 5 (5), Mode 6 (6), Mode 7 (7)
NRncVersion IUR; R99 (1), Rel4 (2), Rel5 (3), Rel6 (4), Rel7 (5),
Rel8 (6), Rel9 (7), Rel10 (8), Rel11 (9), Rel12 (10)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 93 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 93
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• HSDPA Power Allocation
• HSDPA Code Allocation (Basics)
• HSDPA Mobility – Serving Cell Change
– HSPA+ over Iur
– Inter-RNC Mobility
– Inter-frequency Mobility
– Directed RRC Connection Setup
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 94 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 94
HSPA Inter-RNC Cell Change
• The HSPA Inter-RNC cell change is applied to Flexi Direct RNC when:
- 1. The Iur interface between the Adapters does not exist (is not configured).
- 2. S-Flexi Direct RNC has one or more radio links (RL) with the RNC.
- 3. When SHO over Iur is not enabled, that is the RNP parameter EnableInterRNCsho is disabled.
- 4. Iur interface is enabled and SHO over Iur fails (PS RABS only).
Situation prior to HSPA inter-RNC cell change
• improves the end user performance by:
- maintaining a high data rate HSPA service
during intra-frequency inter-RNC mobility.
• Capacity gain is achieved at the cells
border area:
- HSPA instead of DCH can be used.
• uses SRNS relocation with UE involvement
SGSN/GGSN
RNC
Iu/Gn
Iur
Iub
RNC
Serving HSPA RL
UL DCH
E-DCH non-serving RL / UL DCH
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 95 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 95
HSPA Inter-RNC Cell Change
• HSPA intra-frequency inter-RNC cell can be enabled with HSPAInterRNCMobility
parameter:
- need to be set to Enabled or Enabled without E-DCH trigger.
• With HSPAInterRNCMobility =“Disabled”: - HSPA Inter-RNC cell change is not supported but SRNC applies a switch from HSPA to DCH at the
RNC border.
• HSPA Inter-RNC cell change from source RNC to target RNC is performed by means of
the “UE involved” SRNS relocation procedure.
Situation after successful HSPA inter-RNC cell change
• HSDPAMobility has to be set to “Enabled”.
• A new serving cell cannot be selected under
the DRNC, - if the feature HSPA over Iur is not in use
- or the DRNC does not support CS voice over HSPA (virtual cell parameter HSPAQoSEnabled).
SGSN/GGSN
RNC Iu/Gn
Iur
Iub
RNC
DRNC SRNC
Serving HSPA RL
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 96 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 96
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• HSDPA Power Allocation
• HSDPA Code Allocation (Basics)
• HSDPA Mobility – Serving Cell Change
– HSPA+ over Iur
– Inter-RNC Mobility
– Inter-frequency Mobility
– Directed RRC Connection Setup
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 97 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 97
Inter-frequency Mobility (Optional feature)
• Trigger for IFHO / ISHO process in case of active HSDPA service
– Event 1F (too low Ec/I0 or RSCP for all active cells)
– Event 6A (too high UE Tx power)
– Too high DL RL power
– UL quality deterioration
– IMSI based HO
– Capability based HO
• General rule for HHO process
– Channel type switch HS-DSCH to DCH for ISHO
– No channel type switch for IFHO
• Allowed transitions for IFHO process
– DCH/DCH to
DCH/HSDPA
HSUPA/HSDPA
– DCH/HSDPA to
DCH/DCH
DCH/HSDPA
HSUPA/HSDPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 98 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 98
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• HSDPA Power Allocation
• HSDPA Code Allocation (Basics)
• HSDPA Mobility – Serving Cell Change
– HSPA+ over Iur
– Inter-RNC Mobility
– Inter-frequency Mobility
– Directed RRC Connection Setup
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 99 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 99
Directed RRC Connection Setup
Enhanced functionality
• More than 2 layers supported
• Can be restricted to certain types of
services
• Load balancing applied
• R99 directed RRC connection setup
simultaneously supported
• Layering in Cell_FACH supported
(same rules as for RRC con. setup)
HSDPALayering
CommonChEnabled HSDPA layering for UEs in common
channels enabled
WCEL; 0 = disabled;
1 = enabled
Basic functionality
• Only for 2 layers
• Service (cause for RRC connection
setup) not considered
• Load of target layer not considered
• Cannot be used simultaneously with
R99 directed RRC connection setup
• Layering in Cell_FACH supported
(same rules as for RRC con. setup)
Basic feature
• Target
– R5 or newer UEs directed from non-HSDPA supporting carrier to HSDPA supporting one
– R99 or R4 UEs directed from HSDPA supporting carrier to non-HSDPA supporting one
– Feature works within same sector defined by SectorID
• Required parameter settings
– DirectedRRCForHSDPALayerEnabled = enabled
– DirectedRRCForHSDPALayerEnhanc = disabled
DirectedRRC
ForHSDPALayerEnabled WCEL; 0 = disabled; 1 = enabled
DirectedRRC
ForHSDPALayerEnhanc RNMOBI; 0 = disabled; 1 = enabled
SectorID WCEL; 0..12; 1; 0 = cell not
belonging to any sector
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 100 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 100
Enhanced feature
• Non-HSDPA UEs
– Directed away from HSDPA capable cell if
Load of the target cell not too big (i.e. R99 load balancing back to source cell not triggered)
• HSDPA UEs
– Directed away from non-HSDPA capable cell if
Establishment cause indicated by UE allowed in HSDPA layer
Not too much HS-DSCH users in target cell
– Directed to other HSDPA capable cell if
Load balancing required
Establishment cause indicated by UE allowed in HSDPA layer
• HSUPA UEs
– Same rules as for HSDPA UEs, but additionally
Directed to HSUPA capable cell if possible
Not directed away from HSUPA capable cell
Directed RRC Connection Setup
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 101 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 101
Directed RRC Connection Setup: Example
Decision algorithm for UEs
camping on non HSDPA layer
UE HSPA capability = cell HSPA capability
A Yes current layer (f1)
B & C No f2 & f3
Establishment cause allowed in HSDPA target layer
B & C No current layer (f1)
B & C Yes f2 & f3
UE HSPA capability = target cell HSPA capability
B f2 or f3 (where more HSDPA throughput)
C f3
f1, R´99
f2, HSDPA
f3, HSDPA&HSUPA
A
B
UE reporting Rel5 or
Rel-6, HSDPA capability
Any other UE
UE reporting Rel-6
HSDPA & HSUPA capability
C
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 102 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 102
Decision algorithm for UEs
camping on HSDPA layer
UE HSPA capability = cell HSPA capability
A No f1
B & C Yes f2 & f3
Establishment cause allowed in HSDPA target layer
B & C No current layer (f2)
B & C Yes f2 & f3
UE HSPA capability = target cell HSPA capability
B f2 or f3 (where more HSDPA throughput)
C f3
f1, R´99
f2, HSDPA
f3, HSDPA&HSUPA
A
B
C
Directed RRC Connection Setup: Example
UE reporting Rel5 or
Rel-6, HSDPA capability
Any other UE
UE reporting Rel-6
HSDPA & HSUPA capability
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 103 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 103
Load Balancing
• Load of serving and target cell (both in same sector) is checked only if
DirectedRRCForHSDPALayerEnhanc parameter is ON
• Applied if there are 2 or more layers supporting HSDPA
• Target layer selection depends on number of active HSDPA UEs, which is checked against
HSDPALayerLoadShareThreshold
– if number of UEs > HSDPALayerLoadShareThreshold in one cell of sector
HSDPA UEs directed to HSDPA layer offering highest HSDPA power per user
– Otherwise
HSDPA UEs directed to HSDPA layer with highest value of CellWeightForHSDPALayering
Directed RRC Connection Setup: Load Balancing
HSDPALayerLoadShareThreshold
HSDPA layers load sharing threshold
RNMOBI; 0..48; 1; 3
CellWeightForHSDPALayering
Cell weight for HSDPA layering
WCEL; 0.01..1; 0.01; 1
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 104 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 104
Select cell which has
• Highest cell weight
(CellWeightForHSDPALayering)
• Highest number of HS-DSCH users
Cell
f1
Number of HS-DSCH users <
HSDPALayerLoadShareThreshold for all layers
Max
0 Cell
f2
Cell
f3
Directed RRC Connection Setup: Load Balancing
HSDPALayer
LoadShare
Threshold
RNMOBI; 0..48; 1; 3
Number of HS-DSCH users >
HSDPALayerLoadShareThreshold for one layer
Max
0
Cell
f1
Cell
f2
Cell
f3
Select cell which offers highest HSDPA power per
user
CellWeightFor
HSDPALayering
WCEL; 0.01..1; 0.01;
1
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 105 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 105
Directed RRC Connection Setup: Load Balancing
HSDPA power per user
• If not disabled with DisablePowerInHSDPALayeringDecision, select cell with highest HSDPA Power per user:
• Otherwise select cell with highest HSDPA Cell Weight of:
1
*
DPAUsersNumberOfHS
yeringForHSDPALaCellWeightPtxNonHSPAPtxMaxPerUserHSDPAPower
HSPA
power
Non
HSPA
power
PtxNonHSPA
PtxMax
0
Number of HS-DSCH users >
HSDPALayerLoadShareThreshold for one layer
1
DPAUsersNumberOfHS
yeringForHSDPALaCellWeightereightPerUsHSDPACellW
DisablePowerInHSDPA
LayeringDecision Disable power in decision making for
HSDPA layering
RNMOBI; 0..1; 0 = not disabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 106 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 106
Interworking with R99 directed RRC connection setup
• Both parameters DirectedRRCEnabled and DirectedRRCForHSDPALayerEnabled enabled and DirectedRRCForHSDPALayerEnhanc enabled
• Decision of directed RRC connection setup for HSDPA layer done first
– Decision = change layer directed RRC connection setup for HSDPA layer is done
– Decision = do not change layer decision of directed RRC connection setup is done
• If several target candidates exist for R99 directed RRC connection setup
– UE kept in most suitable layer from capability point of view, if possible
– Non HSDPA capable UE non-HSDPA capable cell
– HSDPA capable UE HSDPA or HSDPA and HSUPA capable cell
– HSDPA and HSUPA capable UE HSDPA & HSUPA capable cell preferred, then HSDPA capable cell
– F-DPCH capable UE F-DPCH capable cell preferred otherwise HSDPA&HSUPA capable and HSDPA capable cells
– DC HSDPA capable UE HSPA/DC HSDPA capable cell preferred otherwise HSDPA&HSUPA capable and HSDPA capable cells
• HSDPA/HSUPA capable UE in R99 directed RRC connection setup
– not transferred away from HSDPA/HSUPA layer if requesting interactive or background service
– can be transferred away from HSDPA/HSUPA layer if requesting other kind of service
Directed RRC Connection Setup
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 107 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 107
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching CTS – Channel Type Selection
– Switching from DCH to HS-DSCH
– Switching from HS-DSCH to DCH
– Switching from HS-DSCH to FACH
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 108 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 108
HS-DSCH selected in case of Capacity Request if all of the following conditions are met:
1) Traffic class & THP allowed on HS-DSCH: configurable with HSDSCHQoSClasses
2) UE supports HS-DSCH
2) Cell supports HSDPA & HS-DSCH is enabled
3) Multi-RAB combination of UE supported with HS-DSCH
HSDPA + AMR to be enabled with AMRWithHSDSCH
HSDPA + R99 NRT + AMR / R99 streaming enabled with
HspaMultiNrtRabSupport
5) No. of simultaneous HS-DSCH allocations in BTS/cell below max. no.
supported by base band configuration
6) HsdschGuardTimerHO & HsdschGuardTimerLowThroughput guard timers not running for UE
7) UE not performing inter-frequency or inter-system measurements
8) Active set size = 1 if HSDPAMobility = disabled
9) If HSDPA dynamic resource allocation disabled and no existing MAC-d flow in the cell
PtxNC ≤ PtxtargetHSDPA for HSDPAPriority = 1
PtxnonHSDPA ≤ PtxtargetHSDPA for HSDPA Priority = 2
10) UE does not have DCHs scheduled with bit rates higher than zero
11) HS-DSCH physical layer category is supported
12) HS-DSCH can be admitted if PS streaming and CS voice RB resource are utilized
13) HSDPA prevention function of the RAN2879: Mass Event Handler feature does not prevent from HS-DSCH allocation
HSDPA prevention is started if RNC starts using the prioritized DL power AC for AMR CS DCH speech call
Channel Type Selection CTS
HSDSCHQoSClasses HS-DSCH QoS classes
RNHSPA; 11111 = background /
interactive with THP 1/2/3 / streaming
allowed
AMRWithHSDSCH Usage of AMR service with HS-DSCH
RNFC; 0 = disabled; 1 = enabled
HspaMultiNrtRabSupport HSPA multi RAB NRT support
WCEL; 0 = disabled; 1 = enabled
THP: Traffic Handling Priority
HsdschGuardTimerHO HS-DSCH guard time after switching to DCH due to
HO
RNHSPA; 0..30 s; 1 s; 5 s
HSDSCHGuardTimerLowThroughput HS-DSCH guard timer due to low throughput
RNHSPA; 0..240 s; 1 s; 30 s
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 109 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 109
CTS: DCH to HS-DSCH
Trigger
1) First HSDPA capable cell added to the Active Set (UE enters HSDPA coverage)
Example: SHO of HSDPA capable UE
2) RAB combination of UE is changed so that it supports HS-DSCH
Example: Release of video call (multi RAB NRT support disabled)
3) Initial HS-DSCH reservation not successful for temporary reason (DCH allocated although HS-DSCH
supported)
Example: No dynamic power allocation, initially too high non controllable load
4) HS-DSCH to DCH switch done for IFHO/ISHO measurement, but IFHO/ISHO not performed due to
unsatisfied measurement results
Example: No suitable adjacent IF/IS cell found
HSDPA non-HSDPA
SWITCH
f1
f2
CTS: Channel Type Switching
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 110 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 110
CTS: DCH to HS-DSCH
General Conditions
1) UE has RAB combination supporting HSDPA
• Not more than three NRT RABs (if multi RAB NRT support enabled)
• No R99 streaming or NRT RAB (if multi RAB NRT support disabled)
2) UE and at least 1 active cell HSDPA capable
• If HSDPAMobility = disabled, active set size must be 1
3) No inactivity or low utilization detected on DCH (DL/UL)
4) No guard timers running to prevent HS-DSCH selection
• HsdschGuardTimerHO
• HSDSCHGuardTimerLowThroughput
• HSDSCHCTSwitchGuardTimer
5) RAB attribute “Maximum bit rate” does not prevent use of HSDPA
HSDSCHCTSwitchGuardTimer
HS-DSCH channel type switch guard timer
RNHSPA; 0..30 s; 1 s; 5 s
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 111 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 111
Ec/Io condition for HS-DSCH candidate:
Periodic Ec/Io measurements
• Filtering based on EcNoFilterCoefficient as for any mobility functionality
• Reporting period defined by specific parameter HSDPACPICHCTSRepPer
• RNC averaging over HSDPACPICHAveWindow reports*
• RNC needs as least 1 report to initiated channel type switch
CTS: DCH to HS-DSCH
Addition
window
CPICH 1 R99
CPICH 2 HSDPA
EC/I0
time HSDPA cell
detected
Periodic
reports
Channel type
switch
Addition
Time
Ec/Io (candidate) >
Ec/Io (best cell) – HSDPAChaTypeSwitchWindow
HSDPAChaTypeSwitchWindow RNHSPA; 0..4; 0.5; 0 dB
HSDPACPICHCTSRepPer RNHSPA; 0.5; 1; 2; 3; 4; 6 s; 2 s
HSDPACPICHAveWindow RNMOBI; 1 .. 10; 1; 3
* as for any HSDPA mobility functionality
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 112 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 112
CTS: HS-DSCH to DCH
• Trigger
– Last HSDPA capable cell dropped
– Event 1F (too low Ec/I0 or RSCP for all active cells)
– Event 6A (too high UE Tx power)
– Too high DL RL power
– UL quality deterioration
• DCH allocation
– attempted in next scheduling period with initial bit rates defined by InitialBitRateUL & InitialBitRateDL
– If initial bit rates can not be allocated, DCH 0/0 is offered only
Only if ISHO process
triggered
In case of IFHO process
switch not required
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 113 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 113
CTS: HS-DSCH to FACH
• HS-DSCH released & channel type switching to Cell_FACH in following cases:
– Low utilization
– Low throughput
– In case of Multi-RAB with AMR no channel type switching to Cell_FACH, but to Cell_DCH with
AMR + NRT DCH 0/0
• Throughput calculated by counting all transmitted bits during configurable sliding
measurement window MACdflowthroughputAveWin
– Parameter = 0 throughput measurements switched off
– Otherwise throughput measurements averaged over sliding window
– Sliding measurement window moved every HS-DSCH MAC-d scheduling interval
MACdflowThroughputAveWin WAC; 0..10 s; 0.5 s; 3 s
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 114 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 114
• Low Utilisation indicated when
– MAC-d flow throughput below MACdflowutilRelThr
– AND RLC does not have any data to send
– AND there are no more data in the BTS buffer (normal release)
Time
MACdflowutilRelThr
Timer
started Timer
started
Throughput
MAC-d PDU in buffer
Timer
reset
Switching from HS-DSCH to FACH: Low Utilisation
MACdflowutilRelThr Low utilisation threshold of the MAC-d flow
WAC; 0..64000 bps; 256 bps; 256 bps
MACdflowutilTimetoTrigger Low utilization time to trigger of the MAC-d flow
WAC; 0..300 s; 0.2 s; 0 s
• HS-DSCH released & CTS to Cell_FACH in following cases:
– Low utilization
– Low throughput
– In case of Multi-RAB with AMR no CTS to Cell_FACH, but to Cell_DCH with AMR + NRT DCH 0/0
MACdflowThroughputAveWin WAC; 0..10 s; 0.5 s; 3 s
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 115 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 115
Time
MACdflowutilRelThr
MACdflowthroughputRelThr
HsdschGuardTimerLowThroughput
Timer
started
Timer
started
Throughput
MAC-d PDU in buffer
Timer
started Timer
reset
Timer started
• Low Throughput indicated when
– MAC-d flow throughput below MACdflowthroughputRelThr
– AND there is still data in the BTS buffer (abnormal release)
– After MAC-d flow release HS-DSCH not allowed until guard timer HsdschGuardTimerLowThroughput expires
MACdflowthroughputRelThr Low throughput threshold of the MAC-d flow
WAC ; 0..64000 bps; 256 bps; 0 bps
MACdflowthroughputTimetoTrigger Low throughput time to trigger of the MAC-d flow
WAC ; 0..300 s; 0.2 s; 5 s
HsdschGuardTimerLowThroughput RNHSPA; 0..240 s; 1 s; 30 s
Switching from HS-DSCH to FACH: Low Throughput
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 116 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 116
HSDPA RRM
• HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
– Bit Rates – Packet Scheduling
• HSDPA Improvements
• Other Features
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 117 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 117
UL Return channel - Bit Rates
RB mapped onto HS-DSCH in DL DCH (or E-DCH) allocated as UL return channel
• data rates for UL DCH return channel:
– 16, 64, 128 &384 kbit/s independent on R99 settings
– 16, 64, 128 kbit/s if PS streaming is mapped on HS-DSCH
– 16 kbps UL DCH return channel*: HSDPA16KBPSReturnChannel
– HSDPAminAllowedBitrateUL: min. allowed bit rate -> this parameter is also used to limit UL DCH date
rate if RAN2879 Mass Event Handler is used
PS: HS-DSCH (DL)
PS: DCH (UL)
PS: HS-DSCH (DL)
PS: DCH (UL)
HSDPA16KBPSReturnChannel RNFC; 0 = disabled; 1 = enabled
* optional feature RB: Radio Bearer
HSDPAminAllowedBitrateUL Min. bit rate for HSDPA a-DCH
WAC; 16 K, 64 K, 128 K, 384 K
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 118 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 118
Packet Scheduling: HSDPA with UL associated DCH • HS-DSCH allocation triggered by UL:
– high traffic volume indicated RNC tries to allocate return channel with highest possible bit rate
– low traffic volume indicated RNC tries to allocate return channel with initial bit rate
• HS-DSCH allocation DL triggered:
RNC tries to allocate HSDPAinitialBitrateUL
• Direct DCH to HS-DSCH switch UL a-DCH bit rate can be same
as existing DCH UL bit rate
• initial bit rate cannot allocated HS-DSCH not possible UL/DL DCH
HSDPAinitialBitrateUL
Initial bit rate for HSDPA a-DCH WAC; 16 K, 64 K, 128 K, 384 K
Capacity Request
(TVMHigh)
64
kbps
384
128
t
0
Capacity Request
(TVM Low)
Initial bitrate
64 kbps
Decrease of the retried
NRT DCH bitrate
PBS
RT-over-NRT
t 1 t 2 t 3 t 5
16
t 4
Example
Initial bit rate = 64 K
Minimum bit rate = 16 K
Capacity Request
(TVMHigh)
Min. bitrate
16 kbps
• UL a-DCH functionalities:
– PBS & overload control
– Decrease of retried NRT DCH bit rate
– RT over NRT
– Throughput based optimisation
– Upgrade of NRT DCH data rate
(normal or flexible)
DynUsageHSDPAReturnChannel
Dynamic usage of UL NRT a-DCH
HSDPA return channel
RNFC; 0 or 1; 0 = disabled
enabled by
TVM: Traffic Volume Measurement
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 119 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 119
HSDPA RRM
• HSDPA Principles • HSDPA Protocols & Physical Channels • RU50 Capabilities & Baseband Configuration • HSDPA Link Adaptation • HSDPA H-ARQ • HSDPA Packet Scheduling • Basics of HSDPA Power Allocation • Basics of HSDPA Code Allocation • Basics of HSDPA Mobility • HSDPA Channel Type Selection & Switching • Associated UL DCH • HSDPA Improvements
– 64QAM (RAN1643) – MIMO (RAN1642) – MIMO 42Mbps (RAN1912) – Dual-Cell HSDPA (RAN1906) – DC-HSDPA with MIMO 84Mbps (RAN1907) – Flexible RLC in DL (RAN1638) – Dual Band HSDPA (RAN2179) (RU50)
• Other Features • Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 120 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 120
Multicarrier HSPA Evolution in Release 9/10 & beyond
1 x 5 MHz
Uplink Downlink
1 x 5 MHz
2 x 5 MHz
Uplink Downlink
8 x 5 MHz
• 3GPP Rel. 7 UE can receive and transmit only on 1 frequency even if the operator has total 3-4 frequencies
• Rel. 8 brought DC-HSDPA, Rel. 9 defined DC-HSUPA
• Further Releases bring multicarrier HSDPA which allows UE to take full
benefit of the operator’s spectrum
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 121 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 121
HSPA Data Rate Evolution
14 Mbps
21-28 Mbps
3GPP R5 3GPP R6
3GPP R7
42 Mbps 84 Mbps
3GPP R8 3GPP R9
168 Mbps
3GPP R10
14 Mbps
0.4 Mbps 5.8 Mbps
11 Mbps 11 Mbps
23 Mbps
DC-HSDPA,
+ 64QAM
MIMO
(2x2)
DC-HSDPA + 64QAM + MIMO
(2x2)
4-carrier HSDPA
+ 64QAM + MIMO
(2x2)
DC-HSUPA + 16QAM 16QAM
64QAM or
16QAM
+ MIMO
(2x2)
RU20 / RU30 / RU40 / RU50 3GPP R11
336 Mbps
8-carrier HSDPA
+ 64QAM + MIMO (2x2)
or 4-carrier HSDPA
+ 64QAM + MIMO (4x4)
23 Mbps
DC-HSUPA + 16QAM 16QAM
70 Mbps
DC-HSUPA + 64QAM
+ MIMO (2x2)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 122 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 122
64QAM: RAN1643 Modulation
QPSK
Coding rate
1/4
2/4
3/4
15 codes
1.8 Mbps
3.6 Mbps
5.4 Mbps
16QAM
2/4
3/4
4/4
7.2 Mbps
10.8 Mbps
14.4 Mbps
64QAM
3/4
5/6
4/4
16.2 Mbps
18.0 Mbps
21.6 Mbps
64QAM
6 bits/symbol
HSDPA64QAMAllowed
WCEL; 0 (Disabled), 1 (Enabled)
HS-
DSCH
category
max. HS-
DSCH
Codes
min. *
Inter-TTI
interval
Modulation MIMO
support
Peak
Rate
13 15 1 QPSK/16QAM/ 64QAM
No 17.4 Mbps
14 15 1 QPSK/16QAM/ 64QAM
No 21.1 Mbps
17 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
17.4 or 23.4 Mbps
18 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
21.1 or 28 Mbps
• optional Feature;
RNC License Key required (ON-OFF)
• HSDPA peak rate up to 21.1 Mbps
• UE categories 13,14,17 & 18 supported
• optional feature for UE
Prerequisites:
• Flexible RLC, HSDPA 14.4 Mbps,
Dynamic Resource Allocation, HSUPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 123 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 123
21 Mbps
64QAM: Channel Quality Requirements
• good channel conditions required to apply / take benefit of 64QAM CQI 26 ! – 64QAM requires 6 dB higher SNR than 16QAM
– average CQI typically 20 in the commercial networks
0 Mbps 10 Mbps 14 Mbps
no gain from 64QAM some gain from
64QAM
only available with
64QAM
64QAM QPSK 16QAM
1/4 2/4 2/4
1/6 2/4 3/4 3/4 3/4 5/6 4/4
CQI > 15 CQI > 25
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 124 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 124
64QAM: CQI Tables 1 136 1 QPSK 0
2 176 1 QPSK 0
3 232 1 QPSK 0
4 320 1 QPSK 0
5 376 1 QPSK 0
6 464 1 QPSK 0
7 648 2 QPSK 0
8 792 2 QPSK 0
9 928 2 QPSK 0
10 1264 3 QPSK 0
11 1488 3 QPSK 0
12 1744 3 QPSK 0
13 2288 4 QPSK 0
14 2592 4 QPSK 0
15 3328 5 QPSK 0
16 3576 5 16-QAM 0
17 4200 5 16-QAM 0
18 4672 5 16-QAM 0
19 5296 5 16-QAM 0
20 5896 5 16-QAM 0
21 6568 5 16-QAM 0
22 7184 5 16-QAM 0
23 9736 7 16-QAM 0
24 11432 8 16-QAM 0
25 14424 10 16-QAM 0
26 15776 10 64-QAM 0
27 21768 12 64-QAM 0
28 26504 13 64-QAM 0
29 32264 14 64-QAM 0
30 32264 14 64-QAM -2
CQI TB Size # codes Modulation
1 137 1 QPSK 0
2 173 1 QPSK 0
3 233 1 QPSK 0
4 317 1 QPSK 0
5 377 1 QPSK 0
6 461 1 QPSK 0
7 650 2 QPSK 0
8 792 2 QPSK 0
9 931 2 QPSK 0
10 1262 3 QPSK 0
11 1483 3 QPSK 0
12 1742 3 QPSK 0
13 2279 4 QPSK 0
14 2583 4 QPSK 0
15 3319 5 QPSK 0
16 3565 5 16-QAM 0
17 4189 5 16-QAM 0
18 4664 5 16-QAM 0
19 5287 5 16-QAM 0
20 5887 5 16-QAM 0
21 6554 5 16-QAM 0
22 7168 5 16-QAM 0
23 9719 7 16-QAM 0
24 11418 8 16-QAM 0
25 14411 10 16-QAM 0
26 17237 12 16-QAM 0
27 21754 15 16-QAM 0
28 23370 15 16-QAM 0
29 24222 15 16-QAM 0
30 25558 15 16-QAM 0
CQI TB Size # codes Modulation
TS 25.214:
Annex Table 7d
Cat 10 UE
TS 25.214:
Annex Table 7f
Cat 13 UE
TS 25.214 Annex Table 7g
Cat 14 UE:
CQI29: 14 Codes; 32257 bit
CQI30: 15 Codes; 38582 bit
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 125 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 125
64QAM: Link Simulations
• UE peak data rate increased to 21.1 Mbps (L1 - theoretical)
• Max application level throughput ~17.9 Mbps (ideal channel)
• 64QAM is applicable for better radio conditions
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 126 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 126
64QAM Parameter – Bitrate control
MaxBitRateNRTMACDFlow
can be used to restrict the maximum bit rate of NRT MAC-d flow.
The bit rate used in the reservation of the resources for the MAC-d flow is
the minimum value of 1) max. bit rate based on UE capability, 2) max. bit
rate of the RAB, 3) activated HSDPA bit rate features and 4) the value of
this parameter.
This parameter does not limit the maximum instantaneous bit rate on air
interface.
The value of the parameter is compared to the user bitrate of the NRT
MAC-d flow excluding MAC-hs header, RLC header and padding.
RNHSPA; 128..83968; 128; 65535*
42112 kbps DC HSDPA
27904 kbps MIMO
21120 kbps 10 / 15 codes & 64 QAM
13440 kbps 10 / 15 codes & 14Mbps per user
9600 kbps 10 / 15 codes & 10Mbps per user
6784 kbps 10 / 15 codes
3456 kbps No license for HSDPA 15 codes
Suggested Parameter Setting Features enabled
42112 kbps
27904 kbps MIMO
21120 kbps 10 / 15 codes & 64 QAM
13440 kbps 10 / 15 codes & 14Mbps per user
9600 kbps 10 / 15 codes & 10Mbps per user
6784 kbps 10 / 15 codes
3456 kbps No license for HSDPA 15 codes
Suggested Parameter Setting Features enabled
84224 kbps DC HSDPA & MIMO
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 127 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 127
MIMO Principle
Tm
T2
T1
Rn
R2
R1
• • •
• • •
Input
M x N MIMO
system
Output
• MIMO: Multiple-Input Multiple Output
• M transmit antennas, N receive antennas form MxN MIMO system
• huge data stream (input) distributed toward m spatial distributed antennas; m parallel bit streams
(Input 1..m)
• Spatial Multiplexing generate parallel “virtual data pipes”
• using Multipath effects instead of mitigating them
Signal from jth Tx antenna
Sj
MIMO
Processor
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 128 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 128
MIMO Principle
Tm
T2
T1
Rn
R2
R1
MIMO
P r o c e s s o r
• • •
• • •
Input
M x N MIMO
Output
h1,1
h2,1 hn,1
hn,2
hn,m
h2,2
h2,m
h1,m h1,2
• Receiver learns Channel Matrix H
• inverted Matrix H-1 used for recalculation
of original input data streams 1..m
m
j
ijjii nshy1
,
Signal at ith Rx antenna
Yi
Signal from jth Tx antenna
Sj
ni: Noise at receiver
H =
h1,1
h2,1
hn,1
h1,2
h2,2
hn,2
h1,m
h2,m
hn,m
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 129 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 129
MIMO: RAN1642
HS-
DSCH
category
max. HS-
DSCH
Codes
min. *
Inter-TTI
interval
Modulation MIMO
support
Peak
Rate
15 15 1 QPSK/16QAM Yes 23.4 Mbps
16 15 1 QPSK/16QAM Yes 28 Mbps
17 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
17.4 or 23.4 Mbps
18 15 1 QPSK/16QAM/ 64QAM or Dual-Stream MIMO
21.1 or 28 Mbps
MIMOEnabled WCEL; 0 (Disabled), 1 (Enabled) • RU20 (3GPP Rel. 7) introduces 2x2 MIMO with 2-Tx/2-Rx
– Double Transmit on BTS side (D-TxAA), 2 receive antennas on UE side
– System can operate in dual stream (2x2 MIMO) or single stream (Tx diversity) mode
• MIMO 2x2 enables 28 Mbps peak data rate in HSDPA – 28 Mbps peak rate in combination with 16QAM
– 64QAM: no simultaneous support of 64QAM & MIMO (not yet)
– Dual-Cell HSDPA: not possible to enable MIMO & DC-HSDPA in a cell in parallel
• Benefits: MIMO increases single user peak data rate,
overall cell capacity, average cell throughput & coverage
• UE categories for MIMO support: Cat. 15, 16, 17 & 18
UE: 2 Rx-
antennas
WBTS: 2 Tx-
antennas
• optional Feature (ASW)
• RNC License Key required (ON-OFF)
Prerequisites:
• double Power Amplifier units & antenna lines per cell;
• must be enabled: HSDPAEnabled, HSUPAEnabled, HSDPA14MbpsPerUser, HSDPADynamicResourceAllocation, FDPCHEnabled,
HSDPAMobility, FDPCHEnabled, FRLCEnabled; must not be enabled: DCellHSDPAEnabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 130 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 130
• MIMO enabled cell: S-CPICH is broadcast for DL channel estimation in UE
– S-CPICH transmission power is controlled with existing parameter
• UE must be able to estimate each of the 2 signals separately
– P-CPICH is broadcast along with data stream 1
– S-CPICH (new with RU20) is broadcast along with data stream 2
– SF 256 spreading code must be allocated in DL to support S-CPICH transmission
MIMO
S-CPICH Power & Code allocation
SF 16
SF 32
SF 64
SF 128
SF 256
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
S-CCPCH
depending on
FACH / PCH
configuration
HS-SCCH
E-RGCH
E-HICH
,0
S-CPICH tx power =
PtxPrimaryCPICH -10..50; 0.1; 33 dBm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 131 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 131
Allocation of MIMO for a UE
MIMO 2x2 / 28 Mbps
MIMO Parameter Enabled
Start
BTS is MIMO capable
RAB configuration for UE allows MIMO
Streaming RAB state changes to inactive
SRB* can be mapped to HSPA (F-DPCH)
MAC-ehs can be allocated (Flexible RLC)
UE is MIMO capable
yes
yes
yes
yes
yes
yes
yes – allocate MIMO
no
no
no
no
no
no
no
no – do not allocate MIMO
optional
feature for
UE
RNC checks following conditions, before MIMO allocation to a UE:
(if at least one of the conditions is false during active MIMO allocation, MIMO will be deactivated)
MIMOEnabled WCEL; 0 (Disabled), 1
(Enabled)
FDPCHEnabled
WCEL; 0 (Disabled),
1 (Enabled)
FRLCEnabled
WCEL; 0 (Disabled),
1 (Enabled) yes
* i.e. SRB must be mapped to HSPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 132 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 132
Layering:
• RU20 MIMO supports following site configurations:
– 1 / 1 / 1
– 2 / 2 / 2
– 3 / 3 / 3
• more than one MIMO layer not possible in RU20.
MIMO
Layer
MIMO: Layering & Mobility
Mobility
• Once allocated to a UE, MIMO will be kept also during mobility procedures
– Service Cell Change can be used to allocate / de-allocated MIMO for a UE
– If target cell is not supporting MIMO or MIMO can not be enabled, RNC deactivates MIMO for the UE
• Compressed Mode is started for a UE having MIMO allocated
• MIMO Mobility over Iur interface NOT supported in RU20
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 133 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 133
Performance
MIMO 2x2 / 28 Mbps
CLM: Closed Loop Mode; Single-Stream with Rx- & Tx-Diversity
mean cell throughput vs.
various scheduling schemes
UE throughput at the Cell Edge,
middle of the cell & cell center
Single-stream Dual-stream Single-stream Dual-stream
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 134 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 134
MIMO 42Mbps (RAN1912)
64QAM
6 bits/symbol WBTS: 2 Tx-
antennas
Basics:
• optional Feature; RNC License Key required (ON-OFF)
• RU20 enables either 2x2 MIMO (RAN1642) or 64QAM (RAN1643)
• RU30 enables simultaneous 2x2 MIMO and 64QAM operation (RAN1912)
• Peak Rates: up to 2 x 21 Mbps = 42 Mbps
• 3GPP Rel. 8
• new UE Categories: 19, 20
Requirements
• Flexible RLC, F-DPCH, MIMO 28 Mbps, HSDPA 64QAM
2x2 MIMO
MIMOWith64QAMUsage
WCEL; 0 (Disabled), 1 (Enabled)
HS-
DSCH
category
max. HS-
DSCH
Codes
Modulation MIMO
support
Peak
Rate
19 15 QPSK/16QAM/ 64QAM
Yes 35.3 Mbps
20 15 QPSK/16QAM/ 64QAM
Yes 42.2 Mbps
2x2 MIMO & 64QAM
up to 42 Mbps
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 135 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 135
Allocating MIMO 42Mbps
• 64QAM is allocated with MIMO whenever possible
• Switching can occur when conditions change, i.e. when it becomes possible to
support MIMO with 64QAM, or when it is no longer possible to support MIMO with
64QAM
• The conditions required to support MIMO 42Mbps are:
– it must be possible to support MIMO
– it must be possible to support HSDPA 64QAM
– The WCEL MIMOWith64QAMUsage parameter must be set to enabled
– The BTS and UE must support simultaneous use of MIMO and 64QAM
• If MIMO with 64QAM is not possible but MIMO without 64QAM, or 64QAM without
MIMO is possible, MIMO shall be preferred
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 136 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 136
DC-HSDPA Principles
• prior to 3GPP Release 8, HSDPA channel bandwidths limited to 5 MHz
• Dual-Cell HSDPA: 3GPP Rel. 8 allows 2 adjacent channels to be combined
effective HSDPA channel bandwidth of 10 MHz (RU20 feature)
• 3GPP Rel. 8: Dual Cell HSDPA can be combined with 64QAM but not with MIMO (Release 9 allows combination with both, 64QAM & MIMO)
42 Mbps HSDPA peak rate
5 MHz 5 MHz
F1 F2
MIMO (28 Mbps), or
64QAM (21 Mbps)
10 MHz
DC-HSDPA & 64QAM (42
Mbps)
2 UE, each using 5 MHz RF Channel
Peak Connection Throughput = 28 Mbps
1 UE, using 2 × 5 MHz RF Channels
Peak Connection Throughput = 42 Mbps
F1 F2
Dual Cell Approach Basic Approach
DCellHSDPAEnabled
WCEL; 0 (Disabled), 1 (Enabled)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 137 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 137
DC-HSDPA Principles
• DC-HSDPA provides greater flexibility to the HSDPA Scheduler, i.e. the scheduler can allocated
resources in the frequency domain as well as in the code and time domains
F1 F2 F1 F2 F1 F2
Channel conditions good on
both RF carriers
Channel conditions good on
RF carrier 1
Channel conditions good on
RF carrier 2
UEx UEx UE1 UE1 UE1
Gains of DC-HSDPA:
1) Improved Load Balancing
2) Frequency Selectivity
3) Reduction of Latency
4) Higher Peak Data Rates
5) Improved Cell Edge
“User Experience”
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 138 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 138
DC-HSDPA: UE Cat & Requirements
• RU20 (3GPP Rel. 8) introduces DC-HSDPA (RAN1906)
• DC-HSDPA & 64QAM enable DL 42 Mbps peak rates
• UE categories for DC-HSDPA support: Cat. 21, 22, 23 & 24
• optional feature; requires long term
RNC license for specific number of cells
• following features must be enabled:
• HSDPA (HSDPAEnabled)
• HSUPA (HSUPAEnabled)*
• HSDPA 15 codes (HS-PDSCHcodeset)
• HSDPA 14 Mbps per User (HSDPA14MbpsPerUser)
• HSDPA Serving Cell Change (HSDPAMobility)
• Fractional DPCH (FDPCHEnabled)
• DL Flexible RLC (FRLCEnabled)
• Shared Scheduler for Baseband Efficiency
• HSPAQoSEnabled must be configured with the same value
in both DC-HSDPA cells
• MaxBitRateNRTMACDFlow (def. 65535 = not restricted)
should be configured to allow the peak throughput
• RU20: MIMO + DC-HSPDA must not be enabled for all cells belonging to the Node B (MIMOEnabled); ;
• RU40: MIMO + DC-HSDPA possible DC-HSDPA + MIMO possible in RU40
HS-
DSCH
category
max. HS-
DSCH
Codes
Modulation MIMO
support
Peak
Rate
21 15 QPSK/16QAM No 23.4 Mbps
22 15 QPSK/16QAM No 28 Mbps
23 15 QPSK/16QAM/6
4QAM No
35.3 Mbps
24 15 QPSK/16QAM/6
4QAM No
42.2 Mbps
* at least 1 of the RF carriers
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 139 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 139
DC-HSDPA: Requirements
• DC HSDPA cells require:
• adjacent RF carriers UARFCN
• same sector SectorID
• same Tcell value
SectorID = 1
RF Carrier 2 SectorID = 2
SectorID = 3
SectorID = 1
SectorID = 2
SectorID = 3
RF Carrier 1
Tcell: defines start of SCH, CPICH, Primary CCPCH & DL Scrambling Code(s) in a cell relative to BFN
• 2+2+2 Node B with DC-HSDPA requires:
• each cell belonging to the same sector must
have the same Tcell value
• Tcell values belonging to different sectors
must belong to different Tcell groups
• Configuration requires 3 HSDPA Efficient
Baseband Schedulers
• RF carriers 1 & 2 must be adjacent
Tcell = 0
RF Carrier 2
Tcell = 3
Tcell = 6
Tcell = 0
Tcell = 3
Tcell = 6
RF Carrier 1
DC-HSDPA: Tcell Configuration (I)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 140 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 140
DC-HSDPA: Tcell Configuration (II)
• 3+3+3 Node B with DC-HSDPA
requires:
• each DC-HSDPA cell belonging to same
sector to have same Tcell value
• DC-HSDPA Tcell values belonging to
different sectors must belong to different
Tcell groups
• Configuration requires 4 HSDPA Efficient
Baseband Schedulers
• RF carriers 1 & 2 must be adjacent
• Cells belonging to RF carriers 1 & 2 must
be within the same LCG
• Cells belonging to RF carrier 3 must be
within a further LCG
Tcell = 3
RF Carrier 2 Tcell = 9
Tcell = 6
Tcell = 3
Tcell = 9
Tcell = 6
RF Carrier 1
Tcell = 0
Tcell = 2
Tcell = 1
RF Carrier 3
LCG: Local Cell Group
Tcell Groups
• Group 1: Tcell values 0, 1, 2
• Group 2: Tcell values 3, 4, 5
• Group 3: Tcell values 6, 7, 8
• Group 4: Tcell value 9
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 141 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 141
DC-HSDPA: HSDPA Scheduler
• A single HSDPA shared scheduler for baseband efficiency is required per DC-HSDPA cell pair
• 3 HSDPA shared schedulers are required for a 2+2+2 Node B configuration with DC-HSDPA
• Each scheduler is able to serve both HSDPA & DC-HSDPA UE on both RF carriers
• Link Adaptation is completed in parallel for each RF carrier
Shared Scheduler
per DC-HSDPA cell
pair
HSDPA UE on f2
HSDPA UE on f1
DC-HSDPA UE with serving cell on f2
DC-HSDPA UE with serving cell on f1
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 142 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 142
DC-HSDPA with MIMO 84Mbps
64QAM 6 bits/symbol
WBTS: 2 Tx-
antennas
2x2 MIMO
Dual-Cell (DC-)
HSDPA Benefits:
• higher Peak Rate: up to 2 x 2 x 21 Mbps = 84 Mbps
• better Coverage due to DC-HSDPA & MIMO
• More robust transmission due to MIMO & DC HSDPA usage
Basics:
• enables simultaneously: DC HSDPA, MIMO & 64QAM • MIMO uses Single Stream or Double Stream transmission
• DC-HSDPA uses 2 cells (in 1 sector) at same BTS;
same frequency band & adjacent carriers to a UE
• 64QAM 6 bits/symbol
DC-HSDPA,
2x2 MIMO & 64QAM
up to 84 Mbps
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 143 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 143
DC-HSDPA with MIMO 84Mbps
Feature Enabling:
• DC-HSDPA with MIMO 84 Mbps: optional feature;
but: w/o own license; required licenses:
RAN1642 MIMO (28 Mbps)
RAN1643 HSDPA 64QAM
RAN1906 DC-HSDPA 42 Mbps
• DC-HSDPA + MIMO can be enabled w/o 64QAM
Peak Rate up to 56 Mbps
• to enable Peak Rate = 84 Mbps
DCellAndMIMOUsage must be enabled &
MIMOWith64QAMUsage = 2
DCellAndMIMOUsage
WCEL; 0 (DC-HSDPA & MIMO disabled),
1 (DC-HSDPA & MIMO w/o 64QAM enabled),
2 (DC-HSDPA & MIMO with 64QAM enabled)
MIMO + 64QAM RAN1912 / 3GPP Rel. 7
DB-DC-HSDPA + 64QAM RAN2179 / 3GPP Rel. 9
DC-HSDPA + MIMO 3GPP Rel. 9
42 Mbps 42 Mbps 56 Mbps
DC-HSDPA + MIMO + 64QAM 3GPP Rel. 9
84 Mbps both supported by
RAN1907
max. Peak Rate
in RU40
MIMOWith64QAMUsage
WCEL; 0 (Disabled), 1 (Enabled)
w/o
64QAM
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 144 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 144
DC-HSDPA: UE Categories & Requirements
HS-
DSCH
category
max. HS-
DSCH
Codes
Modulation MIMO
support
DC-
HSDPA
support
Peak
Rate
19 15 QPSK/16QAM/
64QAM Yes No
35.3 Mbps
20 15 QPSK/16QAM/
64QAM Yes No
42.2 Mbps
21 15 QPSK/16QAM No Yes 23.4 Mbps
22 15 QPSK/16QAM No Yes 28 Mbps
23 15 QPSK/16QAM/
64QAM No Yes 35.3 Mbps
24 15 QPSK/16QAM/
64QAM No Yes 42.2 Mbps
25 15 QPSK/16QAM Yes Yes 46.7 Mbps
26 15 QPSK/16QAM Yes Yes 56 Mbps
27 15 QPSK/16QAM/
64QAM Yes Yes 70.6 Mbps
28 15 QPSK/16QAM/
64QAM Yes Yes 84.4 Mbps
Requirements
• RAN1642 MIMO 28 Mbps
• RAN1638 Flexible RLC
• RAN1906 DC HSDPA
• RAN1643 64QAM
• RAN1912 MIMO 42Mbps
DC-HSDPA with MIMO 84Mbps
DC-HSDPA with MIMO
(w/o 64QAM)
DC-HSDPA with 64QAM
(w/o MIMO)
DC-HSDPA
(w/o MIMO, 64QAM)
64QAM with MIMO
(w/o DC-HSDPA)
UE Categories (3GPP Rel. 9; TS 25.306)
MaxBitRateNRTMACDFlow* can be used to restrict max. bit rate of NRT MAC-d
flow
RNHSPA; 128... 83968 ; 128; 0 value 0 / 65535 (before): HSDPA peak rate not
limited by the RNC
* parameter value range has been updated
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 145 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 145
DC-HSDPA: Mobility
Hard
Handover HHO
• DC-HSDPA with MIMO can be maintained, activated or de-activated during mobility
• Availability of DC-HSDPA with MIMO checked in target cell when SCC or HHO initiated
• If DC-HSDPA with MIMO cannot be used in the target cell mobility proceeds without it: – DC-HSDPA or MIMO is used if possible, according to the parameter DCellVsMIMOPreference
• If HSUPA IFHO can be used DC-HSDPA & MIMO is not be deactivated but is maintained during Inter-Frequency measurements
• If HSUPA IFHO cannot be used, E-DCH to DCH switch is completed before inter-frequency measurements; DC-HSDPA with MIMO is deactivated at the same time
• DC-HSDPA with MIMO is not supported across the Iur
• S-RNC does not configure DC-HSDPA with MIMO if there are radio links over the Iur in the active set
SCC: Serving Cell Change
DCellVsMIMOPreference
RNHSPA; DC-HSDPA preferred (0), MIMO
preferred (1)
defines whether RNC primarily activates DC-HSDPA or
MIMO for a UE, which supports both DC-HSDPA & MIMO in
case simultaneous usage of DC-HSDPA & MIMO is not
possible.
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 146 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 146
DC-HSDPA: Gain in Throughput & Coverage
Gain of DC-HSDPA &
MIMO compared to SC-
HSDPA:
• Throughput: + 220%
• Coverage: + 57%
Furthermore:
Some 29% more subscriber
can be served
SC-HSDPA: Single Carrier HSDPA
DC-HSDPA: Dual-Carrier HSDPA
TP: Throughput
more Coverage
Mo
re
Th
rou
gh
pu
t
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 147 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 147
Flexible RLC (DL): RAN1638
FRLCEnabled
RNFC; 0 (Disabled), 1 (Enabled)
• included in RU20 basic software package – no license needed
• HW Prerequisites: Flexi Rel2, UltraSite with EUBB
• Flexible RLC used, if:
– Cell Flexible RLC capable & enabled
– UE supports Flexible RLC
– AM RLC is used
– HS-DSCH & E-DCH selected as transport channels
– Dynamic Resource Allocation enabled
AM: Acknowledged Mode
prior Rel. 7
RLC
PDCP IP packet (max. 1500 byte)
Rel. 7 Flexible RLC
segmentation
RLC PDU: 336 bit or 656 bit
16 bit RLC Header 4.8% or 2.4% Overhead
MAC-hs
IP packet (max. 1500 byte)
• • •
concatenation
TBS (depending on scheduling)
IP packet (max. 1500 byte)
adapts RLC-PDU size to
actual size of higher layer data unit
no segmentation
segmentation
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 148 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 148
DL Flexible RLC
• Prior to Rel. 7: RLC layer segments high layer data units (IP packets) in RLC PDU
sizes of 336 and 656
– 336 is 320 net bit plus 16 bit RLC OH
– 656 is 640 net bit plus 16 bit RLC OH
• On MAC-d layer did not increase Overhead
– Data was passed directly to MAC-hs layer (MAC-d)
• Several MAC-d PDUs were concatenated to form a MAC-hs data block
• BTS selects proper MAC-hs data block size based on
– available user date in BTS buffer and
– radio conditions for that UE
• With DL Flexible RLC the RNC adapts the RLC-PDU size to the actual size of the higher layer
data unit (IP)
– maximum size of 1500 Byte is supported (IP packet length in Ethernet)
Background
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 149 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 149
DL Flexible RLC
• Major improvements with DL Flexible RLC – less processing in RNC & UE
– higher end user application throughput
– lower latency for packet access
– Significantly lower Overhead
– Much less padding bits
– Lower risk for RLC stalling because of too small transmission windows
Advantages
0%
5%
10%
15%
20%
25%
30%
35%
40%
45%
50%
0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500
Rel. 6 with RLC PDU Size of 336 bits
Rel. 6 with RLC PDU Size of 656 bits
Rel. 7 Flexible RLC
Ove
rhe
ad
IP packet size [byte]
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 150 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 150
Dual Band HSDPA: With and Without the Feature (RU50)
2 x 5 MHz
U2100
f1 f2
Without DB-HSDPA feature there is no possibility to establish
data connection with to different band at the same time
2 x 5 MHz
U900
f1 f2
f1
U2100
5 MHz
f1
U900
5 MHz
DC-HSDPA DL transmission options
SC-HSDPA DL transmission options
2 x 5 MHz
f1 f2
DB-HSDPA DL transmission options
With DB-HSDPA feature there is possibility to establish
data connection with to different band at the same time
U2100 U900
*Pre
sente
d f
requency
bands a
re o
nly
exem
pla
ry d
eta
iled c
onfigura
tions o
ptions p
resente
d l
ate
r on
• This feature introduces for a single UE the possibility of using simultaneously two carriers in DL
that are situated on two different WCDMA frequency bands
• Feature enables achieving 42 Mbps peak rate for user in DL (assuming 64QAM and 15 codes
usage on both frequencies)
DBandHSDPAEnabled
WCEL; (0) Disabled, (1) Enabled
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 151 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 151
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features – Continuous Packet Connectivity CPC (RAN1644)
– CS Voice over HSPA (RAN1689)
– Fast Dormancy (RAN2136)
– Fast Dormancy Profiling (RAN2451)
– High Speed Cell_FACH (DL) (RAN1637)
• Appendix
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 152 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 152
• Discontinuous UL DPCCH Transmission & Reception during UE UL traffic inactivity
(UL DPCCH gating + DRX at BTS)
– CQI reporting reduction (switched from periodical to synchronized with DPCCH burst)
– Stopping E-DPCCH detection at NodeB during DPCCH inactivity
• Discontinuous DL Reception (DRX at UE)
– Stop receiving HS-SCCH, E-AGCH & E-RGCH when not needed
• Faster response times
– Increased number of low activity packet users in CELL_DCH state
Motivation / Benefits:
• Increased capacity for low data rate applications
• Longer battery life
• Network:
– optional feature; ON-OFF RNC License
• Prerequisites:
– UE must support CPC
– F-DPCH enabled
CPC: Continuous Packet Connectivity Introduction
CPCEnabled
WCEL; 0 (Disabled),
1 (Enabled)
CPC “Sub-features”:
• UL DPCCH Gating (UL DTX)
• CQI Reporting reduction
• Discontinuous UL Reception (MAC DTX)
• Discontinuous DL Reception (DL DRX)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 153 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 153
CPC: UL Gating (UL DTX)
UL Gating (UL DTX): reduces UL control channel (DPCCH) overhead
• no data to sent on E-DPDCH or HS-DPCCH UE switchs off UL DPCCH
• DPCCH Gating is precondition for other 3 sub-features
DPDCH
DPCCH
E-DPDCH
DPCCH
E-DPDCH
DPCCH
Rel99 Service
Voice (20ms)
Rel6 Voice 2ms
(Rel6 VoIP)
Rel7 Voice 2ms
(Rel7 VoIP)
UL DPCCH Gating
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 154 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 154
CPC: UL Gating
• UE specific Packet Scheduler provides CPC parameters
• These are service & UL TTI specific & part of parameter groups
– Voice 2ms, 10ms; RNHSPA: CPCVoice10msTTI, CPCVoice2msTTI
– Streaming 2ms, 10ms; RNHSPA: CPCStreaming10msTTI, CPCStreaming2msTTI
– Interactive, Background 2ms, 10ms; RNHSPA: CPCNRT10msTTI, CPCNRT2msTTI
UL DPCCH Gating (UL DTX)
Following parameters are parameters from CPCNRT2msTTI group (per sub-feature):
DPCCH Gating (UL DTX):
• N2msInacThrUEDTXCycl2: number of consecutive E-DCH TTIs without an E-DCH transmission, after which
the UE should immediately move from UE DTX Cycle 1 to UE DTX Cycle 2. RNHSPA; Range:1 (0), 4 (1), 8 (2), 16
(3), 32 (4), 64 (5), 128(6), 256 (7); default: 64 (5) TTIs
• N2msUEDPCCHburst1: UL DPCCH burst length in subframes when UE DTX Cycle 1 is applied. RNHSPA;
Range:1 (0), 2 (1), 5 (2); default: 1 (0) subframes
• N2msUEDPCCHburst2: UL DPCCH burst length in subframes when UE DTX Cycle 2 is applied. RNHSPA;
Range:1 (0), 2 (1), 5 (2); default: 1 (0) subframes
• N2msUEDTXCycle1: UL DPCCH burst pattern length in subframes for UE DTX Cycle 1. RNHSPA; Range: 1 (0),
4 (1), 5 (2), 8 (3), 10 (4), 16 (5), 20 (6); default: 8 (3) subframes
• N2msUEDTXCycle2: UL DPCCH burst pattern length in subframes for UE DTX Cycle 2. RNHSPA; Range: 4 (0),
5 (1), 8 (2), 10 (3), 16 (4), 20 (5), 32 (6), 40 (7), 64 (8), 80 (9), 128 (10), 160 (11); default: 16 (4) subframes
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 155 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 155
UL Gating, E-DCH 2ms TTI example: CPCNRT2msTTI
CPC: UL Gating / DPCCH Gating
10ms Radio Frame 10ms Radio Frame
2ms subframe
CFN
UE_DTX_Cycle_1
UE_DTX_Cycle_2
Inactivity Threshold for UE cycle 2
10ms Radio Frame
UE_DTX_Cycle_2
switch to UE cycle 2 UE_DTX_DRX_offset is UE specific offset granted from BTS
cycle 1 cycle 2
E-DPDCH
Tx, 2ms TTI
DPCCH
pattern
DPCCH with
E-DCH, 2ms TTI
synch reference
CFN: Connection Frame Number; used for any synchronized procedure in UTRAN
Pre/Postambles not shown here
no data on E-DPDCH
N2msUEDPCCHburst1 RNHSPA; 1, 2, 5; 1 subframe(s)
N2msUEDTXCycle1 RNHSPA; 1, 4, 5, 8, 10, 16, 20; 8 subframes
N2msInacThrUEDTXCycl2 RNHSPA; 1, 4, 8, 16, 32, 64, 128, 256; 64 TTIs
N2msUEDPCCHburst2 RNHSPA; 1, 2, 5; 1 subframe(s)
N2msUEDTXCycle2 RNHSPA; 4, 5, 8, 10, 16, 20, 32, 40,
64, 80, 128, 160; 16 subframes
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 156 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 156
CPC: Reduced CQI Reporting
CQI Reporting reduction:
• CQI Reporting Reduction reduce the Tx power of the UE by reducing the CQI reporting; this means
to reduce the interference from HS-DPCCH in UL when no data is transmitted on HS-PDSCH in DL
• Reduced CQI reporting takes place only if the CQI reporting pattern defined by the last HS-DSCH
transmission and CQI cycle overlaps the UL DPCCH burst of the UE DTX pattern
• N2msCQIDTXTimer: defines the number of subframes after an HS-DSCH reception, during which the CQI reports
have higher priority than the DTX pattern. RNHSPA; 0 (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256
(9), 512 (10), Infinity (11); 64 (7) subframes
• N2msCQIFeedbackCPC: defines the CQI feedback cycle for HSDPA when the CQI reporting is not reduced
because of DTX. RNHSPA; 0 (0), 2 (1), 4 (2), 8 (3), 10 (4), 20 (5), 40 (6), 80 (7), 160 (8); default: 8 (3) ms; Note:
Bigger CQI reporting cycles 10ms are not recommended.
ACK/NACK transmission
CQI transmission
CQI period 2ms
CQI period 4ms
CQI period 8ms
CQI transmission time defined by
CQI period, but not overlapping with DPCCH transmission no CQI transmission
CQI Transmission
DPCCH pattern
UE_DTX_cycle_1 UE_DTX_cycle_1
UE_DTX_cycle_2 UE_DTX_cycle_2
7.5
slots
HS-DSCH reception CQI_DTX_TIMER
UE_DTX_cycle_2
CQI_DTX_Priority set to 1
CQI_DTX_Priority set to 0
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 157 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 157
CPC: Discontinuous UL & DL Reception (MAC DTX & DL DRX)
During E-DCH inactivity, E-DPCCH detection happens at the BTS only every MAC_DTX_Cycle subframes. It is stopped at
Node B after MAC_inactivity_threshold subframes of E-DCH inactivity. As a consequence, the UE experiences a delay
regarding the transmission start time. The UE-specific offset parameter UE_DTX_DRX_Offset allows to stagger the processing
of several UEs in time to save the BTS resources.
Discontinuous UL Reception (MAC DTX):
• N2msMACDTXCycle: length of MAC DTX Cycle in subframes. This is a pattern of time instances where
the start of the UL E-DCH transmission after inactivity is allowed. RNSHPA; Range: 1 (0), 4 (1), 5 (2), 8 (3), 10 (4),
16 (5), 20 (6); default: 8 (3) subframes
• N2msMACInacThr: E-DCH inactivity time in TTIs after which the UE can start E-DCH transmission only at
given times. RNHSPA; Infinity (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256 (9), 512 (10) TTIs;
default: Infinity (0)
Discontinuous DL Reception (DL DRX):
• N2msInacThrUEDRXCycle: number of subframes after an HS-SCCH reception or after the first slot of an
HS-PDSCH reception, during which the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set
continuously. RNHSPA; Range: 0 (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256 (9), 512 (10);
default: 64 (7) subframes
• N2msUEDRXCycle: HS-SCCH reception pattern (UE DRX Cycle) length in subframes. This parameter is a
multiple or a divisor of the parameter UE DTX Cycle 1. If the value is not allowed, the parameter value minus 1 is
used to calculate a new value, and so on. RNHSPA; Range: 0.5 (0), 1 (1), 2 (2), 3 (3), 4 (4); default: 2 (2) subframes
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 158 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 158
CPC: Discontinuous UL Reception
Discontinuous UL Reception (MAC-DTX) – NSN implemented parameters
UE can transmit E-DPDCH data only
at predefined time instances.
N2msMACInacThr RNHSPA; Infinity, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512; Infinity subframes
N2msMACDTXCycle length of MAC DTX Cycle
RNHSPA; Infinity, 1, 4, 5, 8, 10,
16, 20; 8 subframes
DTX
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 159 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 159
CPC: Discontinuous DL Reception Discontinuous DL Reception (DL DRX)
• N2msInacThrUEDRXCycle: number of subframes after an HS-SCCH reception or after the 1st slot of an HS-PDSCH reception,
during which the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set continuously; UE DRX Inactivity threshold; RNHSPA; 0, 1, 2,
4, 8, 16, 32, 64, 128, 256, 512; 64 subframes
• N2msInacThrUEDRXCycle: HS-SCCH reception pattern (UE DRX Cycle) length in subframes; RNHSPA; 0.5, 1, 2, 3, 4; 2 subframes
N2msUEDRXCycle length of UE DRX Cycle
RNHSPA; 0.5, 1, 2, 3, 4; 2 subframes
N2msInacThrUEDRXCycle UE DRX Inactivity threshold
RNHSPA; 0, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512; 64 subframes
DRX
• When the UE DRX is enabled, the UE may turn off the receiver when there is no need to receive anything in DL
• The DL DRX can be enabled only in conjunction with UL DTX
DL DRX
only with UL DTX !
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 160 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 160
• New parameter introduced to control step size for DL Inner Loop PC
Power Control
CPC & Power Control
DownlinkInnerLoop
PCStepSize
RNAC: 0.5..2; 0.5; 1 dB
DLInLoopPCStepSizeCPC
RNSPA: 0.5..2; 0.5; 1.5 dB
DLInLoopPCStepSizeCPC:
used by the WCDMA BTS to calculate the power increase/decrease step size when receiving TPC commands. It is
applied when CPC (UE DTX, etc.) is activated for the UE.
Note: If CPC is not used for a UE, BTS applies DownlinkInnerLoopPCStepSize
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 161 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 161
CPC: Extra-inactivity timer for Transition from CELL_DCH to CELL_FACH
RNC UE CELL_ DCH Node B
PDU Transport on the DCH/DPCH
All data sent & RLC-U buffer empty
Inactivity detected Start
InactivityTimerDownlinkDCH InactivityTimerUplinkDCH
Radio Bearer Reconfiguration
Radio Bearer Reconfiguration Complete
Expiry
CELL_ FACH
InactivityTimerDownlinkDCH
InactivityTimerUplinkDCH Range: 0 .. 20 s; Step: 1 s; default:
• for 8, 16 & 32 kbps: 5 s
• for 64 kbps: 3 s
• for 128, 256, 320 & 384 kbps: 2 s
as soon as L2 in RNC indicated RB inactivity, RNC allocates “extra -
inactivity timer” to keep the UE in Cell_DCH
This depends on:
– CPC is allocated for a UE or not (CPC or NonCPC)
– UE Device Type – RNC knows from UE capabilities
UE benefits / does not benefit from Power Consumption Optimization (BatOpt /
NoBatOpt)
InactCPCNoBatOptT: 180 s
InactCPCBatOptT: 0 s
InactNonCPCNoBatOptT: 0 s
InactNonCPCBatOptT: 0 s
all parameters: RNHSPA; 0s..48h
& infinity; several steps;
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 162 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 162
Network: • optional RU20 feature; ON-OFF RNC License
UE: • must support CSvoiceOverHSPA
• optional feature in Rel. 7/8
required Network Features: • HSDPA Dynamic Resource Allocation
• QoS Aware HSPA Scheduling
• CPC
• F-DPCH
• HSPA with simultan. AMR Voice
• SRB must be mapped to HSPA
• supported RAB combinations: • Speech CS RAB
• Speech CS RAB + PS streaming PS RAB
• Speech CS RAB + 1...3 IA/BG PS RABs
• Speech CS RAB + PS Streaming PS RAB + 1...3
IA/BG PS RABs
• Load based AMR selection algorithm not used while
CS Voice is mapped on HSPA
Requirements
CS Voice Over HSPA (RAN1689)
BG: Background
IA: Interactive
Codecs supported for CS Voice Over HSPA: • AMR (12.2, 7.95, 5.9, 4.75), (5.9, 4.75) & (12.2)
• AMR-WB (12.65, 8.85, 6.6)
for Voice, SRB
& other services
HSPAQoSEnabled WCEL; 0..4*; 1; 0 = disabled
0 = QoS prioritization is not in use for HS transport
1 = QoS prioritization is used for HS NRT channels
2 = HSPA streaming is in use
3 = HSPA CS voice is in use
4 = HSPA streaming & CS voice are in use
* if HSPA streaming or CS voice is activated, then QoS
prioritization for NRT HSPA connections is in use, too
QoSPriorityMapping RNPS; 0..15; 1; 14 for CS Voice over HSPA
• Priority must be lower than SRB (15)
• Priority must be higher than Streaming 13)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 163 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 163
• CS voice over HSPA license exists & state is 'On‘
• HSDPA with Simultaneous AMR Voice Call license exists & state is 'On'
• HSUPA with Simultaneous AMR Voice Call license exists & state is 'On'
• AMRWithHSDSCH & AMRWithEDCH: HSPA with Simultaneous AMR Voice Call enabled
• HSDPAenabled & HSUPAenabled : HSPA enabled in all Active Set cells
• HSDPA Dynamic Resource Allocation license exists & state is 'On‘
• HSDPADynamicResourceAllocation is enabled
• QoS Aware HSPA Scheduling license exists & state is 'On‘
• HSPAQoSEnabled is set to “HSPA CS voice” in all Active Set cells
• CPC & Fractional DPCH licenses exists & state is 'On‘
• CPCEnabled in all Active Set cells
• FDPCHEnabled: Fractional DPCH enabled in all Active Set cells
Enabling the feature: CS Voice Over HSPA
Pre-conditions
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 164 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 164
CS Voice Over HSPA
Efficiency
• Two different voice transmission scenarios are being considered with IP:
– VoIP – UE connects with network as in standard Packed Data transmission and by using “web communicators” a connection can be established (hard to establish appropriate charging schemes)
– CS voice over IP – voice is being carried by HSPA transport channels transparent for the user
[REF. WCDMA for UMTS – HSPA Evolution and LTE, HH AT]
Assumed IP Header
Compression
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 165 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 165
CS Voice Over HSPA
Concept / Protocol Stack
• In UL there is a so called Dejitter buffer implemented in RNC PDCP
• used to align the UL data stream before routing to MSC or MSS system
• In DL MAC-ehs is used to support flexible RLC PDU sizes
• supporting different AMR rates
DCH
CS Core
TM RLC
RAN
CS Voice over DCH
Dejitter buffer
UM RLC
PDCP
HSPA
CS Core RAN
CS Voice over HSPA
• Inter system mobility between 2G & 3G is as today, the CS Voice Over HSPA is just RAN internal mapping and it
is not visible outside of the RAN. Handover signaling is not affected and RAN provides the measurement periods
for UE using compressed mode as today
• AMR rate adaptation can be used to provide even higher capacity gains by lowering the AMR coding rate
• Voice related RRM algorithms like pre-emption are expanded to cover also the Voice Over HSPA
• Air interface capacity gain of the feature depends on parameterisation of HSUPA including CPC parameters,
allowed noise rise and voice activity
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 166 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 166
CS Voice Over HSPA
NCT Tx power target
for DCH + HSPA
NCT Tx power target
for DCH
PtxTargetTot is calculated always when
NCT* load services
are admitted Common Channels
DCH RT + SRBs (excluding PS streaming)
DCH PS streaming
DCH NRT
HSDPA voice + SRBs
HSDPA NRT
HSDPA PS streaming
PtxNCTDCH
PtxNCTHSDPA
PtxTargetTotMax
PtxTargetTotMin
PtxCellMax
PtxTargetTot
PtxTargetTotMax max. target pwr for NCT* load
WCEL; -10..50; 0.1; 32767 dBm
Special value: Use of dynamic DL
target power is disabled
PtxTargetTotMin min. target pwr for NCT* load
WCEL; -10..50; 0.1; 32767 dBm
Special value: Use of dynamic DL target
power is disabled
* Non-Controllable Traffic NCT: CS services & PS conversational services
PtxTarget
PtxNCTHSDPA: power used by HSDPA conversational services
PtxNCTDCH: power used by DCH services associated as NCT load
Admission Control: CS Voice over HSPA connection
admitted if:
PtxNCTDCH + PtxNCTHSDPA + Pnew < PtxTargetTot
&& PtxNCTHSDPA + Pnew < PtxMaxHSDPA
PtxMaxHSDPA max. allowed
HSDPA power
WCEL; 0..50 dBm;
0.1 dB; 43 dBm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 167 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 167
PtxNCTDCH: power used by DCH services associated as NCT load
Dynamic target power for NCT load
The min. & max. value for dynamic target power for
NCT load (CS services & PS conversational
services) can be set :
PtxTargetTotMin WCEL; -10..50 dBm; 0.1 dBm; 32767 dBm
PtxTargetTotMax WCEL; -10..50 dBm; 0.1 dBm; 32767 dBm
PtxTargetTot = PtxTargetTotMax - PtxNCTDCH
PtxTargetTotMax
PtxTarget -1 ( )
PtxTargetTot is calculated whenever a NCT connection is admitted
NCT: Non-Controllable Traffic
Dynamic target power is used when in cell there are SRBs or conversational services (NCT load) mapped to HS-DSCH
transport channel. Dynamic target power varies between PtxTargetTotMin & PtxTargetTotMax depending on the mix of
services mapped to DCH & HS-DSCH transport channels.
However, NCT load caused by services mapped to DCH transport channels must still stay below PtxTarget.
Power margin between PtxCellMax & PtxTargetTotMax is needed to protect the already admitted services mapped to HS-
transport channels by giving time for the overload control to adjust PS DCH load before high priority HS-DSCH load is
affected.
Rules:
PtxTargetTotMin PtxTargetTot
PtxTargetTotMax
PtxTargetTotMin PtxTargetTotMax
PtxTarget PtxTargetTotMin
PtxTargetTotMax PtxCellMax
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 168 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 168
PtxTargetPS Target Calculation
• The introduction of CS Voice over HSPA impacts the calculation of the target for PtxTargetPS
• The original calculation in RAS06 was:
PtxTargetPSTarget = Ptx_nc + [(Pmax - Ptx_nc- Ptx_hsdpa_stream) x WeightRatio]
PtxTargetPSTarget = Ptx_nc + [(Pmax - Ptx_nc) x WeightRatio]
PtxTargetPSTarget = Ptx_nc + [(Pmax - Ptx_nc- Ptx_hsdpa_stream- Pnc_hsdpa) x WeightRatio]
• This calculation shares the power left over from non-controllable load between HSDPA & NRT DCH
connections
• The calculation was updated in RU10 to account for HSDPA streaming:
• The updated calculation reduces the quantity of power to be shared by effectively including HSDPA
streaming power as non-controllable power
• The calculation is further updated when CS Voice over HSPA is enabled
CS Voice over HSPA transmit power
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 169 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 169
UL Power Allocation: dynamic threshold PrxTargetAMR PrxTargetMax
max. UL target power for CS
speech service allocation
WCEL; 0..30; 0.1; 465535 dB
NST: Non-Scheduled Transmission
SCT: Semi-controllable traffic
other interference,
Noise power
DCH CS data
DCH PS streaming
DCH PS NRT
HS/DCH CS AMR
HSUPA NRT
HSUPA PS streaming
PrxTargetAMR
PrxTargetPS
PrxTargetMax
PrxTarget
PrxDataDCHNST
Non-Controllable Load
Semi-Controllable Load Controllable Load
• PrxTargetAMR is used for the admission of UL DCH
& E-DCH, SRB & CS AMR connections
• PrxTargetAMR shall be applied always, w/o
considering the activation of the feature CS voice over
HSPA.
• PrxTargetAMR varies between PrxTarget &
PrxTargetMax depending upon the UL load of data
services
• PrxTargetAMR is calculated by cell specific AC
inside RNC
• NCT can always use power up to PrxTarget
• Standalone SRB & CS AMR can be admitted even if
the NC interference power exceeds PrxTarget as long
as the RSSI is below PrxTargetAMR
• SCT load of the HSUPA & UL DCH streaming services
can take all power left from the NCT load up to
PrxTarget
• DCH PS NRT services can use power up to dynamic
UL DCH target PrxTargetPS
• HSUPA PS NRT services can take all power left from
all other services
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 170 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 170
HSUPA Non-Scheduled Transmission NST
• NST is used for the UL of CS Voice over HSPA
• HSUPA TTI = 2 ms 1 HARQ process is allocated for the E-DCH MAC-d flow
• EDCHMuxVoiceTTI2 & EDCHMuxVoiceTTI10 define whether or not other E-DCH MAC-d flow data can be
multiplexed within the same MAC-e PDU as CS Voice
• The max. Number of Bits per MAC-e PDU for NST indicates the number of bits allowed to be included in a
MAC-e PDU per E-DCH MAC-d flow configured for non-scheduled transmissions
• Generally the MAC-d flow of the SRB has higher SPI value, being prioritized over the CS voice in the E-
TFC selection
• The max. SRB bit rate will be limited so that the at least 1 CS voice frame can always transmitted
together with the signaling when the max. puncturing is applied, for minimizing the CS voice delay
• 2 ms TTI is selected whenever possible, otherwise 10 ms TTI is used
The maximum target value for the RTWP in UL for CS speech service allocation:
PrxTargetMax
defines the max. target value for the RTWP in the UL resource allocation for the CS speech services. A dynamic target of RTWP
is applied in the resource allocation for the CS speech services and for the establishment of the link. Dynamic target is the
closer to the value of this parameter, the less there is PS NRT R99 data traffic and RT data R99 and HSPA traffic in the cell.
Establishment of the stand alone signaling link or a single service CS speech can be admitted in UL even the received non-
controllable interference exceeds the value of the parameter "Target for received power" so long as the RTWP keeps below the
dynamic target value defined with this parameter.
WCEL: 0..30 dB; 0.1 dB; 465535 dB NST: Non-Scheduled Transmission
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 171 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 171
Fast Dormancy: Background
URA_PCH
CELL_DCH CELL_FACH
CELL_PCH
UTRA RRC Connected Mode
Idle Mode
Smart phones with many applications, requiring frequent
transmission of small amount of data# (always-on)
To save battery power, 3GPP defines transition from states
with high power consumption (Cell_DCH, Cell_FACH) to those
with low consumption (Cell_PCH, URA_PCH)
approx. battery consumption in different RRC states:
•Idle = 1 (relative units)
•Cell_PCH < 2*1
•URA_PCH ≤ Cell_PCH*2
•Cell_FACH = 40 x Idle
•Cell_DCH = 100 x Idle
*1 depends on DRX ratio with Idle & mobility
*2 < in mobility scenarios, = in static scenarios # e.g. sending frequent ‘polls’ or ‘keep-alives’
0
50
100
150
200
250
300
URA_PCH /
Cell_PCH / Idle
Cell_FACH Cell_DCH
Pow
er c
on
sum
pti
on
[m
A]
Typical terminal power consumption
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 172 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 172
Fast Dormancy: Background
URA_PCH
CELL_DCH CELL_FACH
CELL_PCH
UTRA RRC Connected Mode
Idle Mode
Problem for UE:
many networks with rel. long inactivity timers for Cell_DCH &
Cell_FACH and/or PCH states not activated
UE vendors introduced proprietary Fast Dormancy:
•UE completes data transfer
•UE sends Signaling Connection Release Indication SCRI (simulating a failure in the signaling connection)
•RNC releases RRC connection UE to RRC Idle mode
Disadvantages:
•increasing signaling load due to frequent packet connection
setup (PS RAB),
•large number of “signaling connection failures”
•increased latencies
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 173 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 173
Fast Dormancy: Principle
URA_PCH
CELL_DCH CELL_FACH
CELL_PCH
UTRA RRC Connected Mode
Idle Mode
3GPP Rel. 8: Fast Dormancy
•modifying SCRI message; new cause value indicating packet
data session end
•RNC can keep UE in RRC connected mode, moving it into
CELL_PCH/URA_PCH
UE battery life remains prolonged because power
consumption in CELL_PCH/ URA_PCH is low
Network again in charge of RRC state; clarification of
“signaling connection failures”
Reduction of signaling load & latency times Cause value of
‘UE Requested PS
Data Session End’
defined
3GPP TS 25.331
10.3.3.37a Signalling Connection Release Indication Cause
„This IE is used to indicate to the UTRAN that there is no more PS data for a prolonged period.“
SRCI: Signalling Connection Release Indication
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 174 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 174
Fast Dormancy
SIB1: T323
SCRI: „UE Requested PS Data Session End”
„Physical Channel Reconfig.” move to CELL_PCH
UE RNC
BTS FastDormancyEnabled
RNFC; 0 (Disabled), 1 (Enabled)
RAN2136: Fast Dormancy (FD) • Basic SW; no activation required; enabled by default
• MSActivitySupervision to be configured with value > 0 to enable PCH states
• Enabling FD results in T323 being broadcast within SIB1
T323:
• Inclusion of T323 within SIB1 allows UE to detect that network supports FD
• Setting a min. delay between 2 SRCI messages for FD; prevents, that UE is sending a flow of SCRI messages, if
network is temporarily unable to move UE to a battery-saving state
MSActivitySupervision RNC; 0..1440; 1; 29 min
SRCI: Signalling Connection Release Indication
T323 RNC; 0..7; 1; 0 s
(hardcoded)
Fast Dormancy - RNC Actions:
After receiving SCRI message with cause value ‘UE Requested PS Data Session End’:
•FD functionality overrides inactivity timers
•RNC instructs UE to make state change to CELL_PCH/URA_PCH
If RNC receives an SCRI message without a cause value then the existing legacy functionality is
applied & the UE is moved to RRC Idle mode
MSActivitySupervision
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 175 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 175
• Included in RU40 application software package – license is required
Brief description:
• Identifies legacy Fast Dormancy phones which cause unnecessary signaling load
• Provides with better network resources utilization due to shorter inactivity timers
• Less signaling load because LFD (Legacy Fast Dormancy) Phones are being forced to stay in Cell_PCH
Benefits:
• Signaling load reduction on Iub, UU and Iu interfaces
• Signaling load reduction in the RNC
• Longer UE battery life
Overview:
SIB1 contains info about T323
• RAN supports Fast dormancy
• Application has no more data to transfer
• UE wants go to more battery efficient RRC state
SCRI
RNC: Data session ended
RNC: UE move to more battery efficient state
Go to URA/Cell_PCH
Fast Dormancy Profiling: RAN2451
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 176 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 176
Legacy Fast Dormancy phone detection:
• The UE is detected as Legacy Fast Dormancy phone (LFDphone) when network receives RRC:Signaling Connection Release Indication without any cause
• If the Fast Dormancy Profiling feature is activated then RRC state transition is performed according to Fast Dormancy functionality
Handling the PS Connection Establishment:
• The LFD Phone after sending SCRI without any cause may still silently goes to Idle
• After receiving RRC: Initial Direct Transfer, RNC checks if Iu-PS connection already exists
• If yes, then all existing PS RAB resources locally and the old Iu connection are released
• New Iu connection is established for pushing RRC: Initial Direct Transfer to SGSN
SCRI - without any cause RNC checks if the
license is ON
If the license is available - Go to Cell_PCH
RRC: Initial Direct Transfer
RNC checks
if Iu-PS
connection
for this UE
already
exists
Iu
Fast Dormancy Profiling: Background
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 177 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 177
Shorter Inactivity Timers for LFD Phone and Smartphones:
• Shorter inactivity timers should be used for moving smartphones and LFD Phones to Cell_PCH state - saving UE battery
• It gives possibility to avoid unnecessary movement to IDLE_mode – less signaling load
Higher Traffic Volume Thresholds for LFD Phone and Smartphones:
• Higher traffic volume thresholds should be used for moving smartphones and LFD Phones to Cell_DCH state
• It gives possibility to avoid unnecessary movement to Cell_DCH – only for sending keep-alive message
• Stored IMSI gives possibility to faster usage of higher traffic volume thresholds
Fast Dormancy Profiling: Principle
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 178 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 178
• Included in RU30 application software package – license required
• HW prerequisites: Flexi rel.2
• Can be used if: Flexible RLC Downlink is active
Brief Description:
• This feature enables Fast Cell_PCH to Cell_FACH switching (transition <200ms)
• Feature reduces signaling load on Iub and Iur interfaces
• Reduces code tree occupation
• Saves BTS baseband resources
• Increases number of supported smartphones
• Increases possible throughputs on common channels to 1.80Mbps in DL
DL channel mapping:
HSFACHVolThrDL
WCEL; Infinity, (8, 16, 32, 64, 128,
256, 512, 1024, 2048, 3072, 4096,
8192, 16384, 24576, 49152) bytes
PCCH CCCH DCCH DTCH
3GPP Rel7
BCCH
FACH FACH FACH BCH PCH FACH
S-CCPCH P-CCPCH
HS-DSCH
HS-PDSCH S-CCPCH S-CCPCH
Logical channels
Transport channels
Physical channels
High Speed Cell_FACH (DL): RAN1637
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 179 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 179
Dedicated channels
Common channels
Dedicated channels
Common channels
HSDPA only on
dedicated channels HSDPA also on
common channels
Data transmission
• Cell_PCH to Cell_FACH state change
• Cell Update not needed
• <200 ms
• Cell_PCH to Cell_DCH state change
• Cell Update required
• 600 ms
Channel type switch
Transmission/reception in Cell_FACH
Data appears in buffer
t [ms] Transmission/reception in Cell_DCH Cell
update
Data appears in buffer
t [ms] Channel type switch
Significant setup time reduction
RAN1637 Activated
RAN1637 Not activated
High Speed Cell_FACH (DL): With and Without the Feature
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 180 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 180
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix: – Static HS-PDSCH Power Allocation
– Cell Reselection
– Iub Flow
– Congestion Control
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 181 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 181
Static HS-PDSCH Power Allocation (1/2)
• Required parameter settings – Dynamic HS-PDSCH power allocation disabled
– “Fixed” HS-PDSCH power defined with PtxMaxHSDPA
• Rules for HSDPAPriority = 1 (higher priority for HSDPA) – A: 1st HSDPA users enters cell
Non-controllable traffic PtxNC ≤ PtxTargetHSDPA HSDPA allowed
Otherwise R99 only
– HSDPA already active R99 scheduled up to PtxTargetHSDPA
– B: Overload for total R99 traffic PtxnonHSDPA > modified overload threshold Standard R99 overload actions
– C: Overload for PtxNC > modified overload threshold HSDPA released
Max power Node B Tx power
A
PtxOffsetHSDPA PtxnonHSDPA
PtxNC
PtxTargetHSDPA
B
Ptxtotal
PtxTarget
C
HSDPAPriority 1,2; 1 = HSDPA priority
PtxTargetHSDPA Target for transmitted non-HSDPA power
-10..50 dBm; 0.1 dB; 38.5 dBm
PtxOffsetHSDPA Offset for transmitted non-HSDPA power
0..6 dB; 0.1 dB; 0.8 dB
PtxMaxHSDPA Maximum allowed HSDPA power
WCEL; 0..50 dBm; 0.1 dB; 43 dBm
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 182 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 182
Static HS-PDSCH Power Allocation (2/2)
• Rules for HSDPAPriority = 2 (higher priority for R99)
– A: 1st HSDPA users enters cell Total R99 traffic PtxnonHSDPA ≤ PtxTargetHSDPA Can have HSDPA
Otherwise can have R99 only
– HSDPA already active R99 scheduled up to PtxTargetHSDPA
– B: Overload for total R99 traffic PtxnonHSDPA > modified overload threshold HSDPA released
– C: Standard overload for total R99 traffic PtxnonHSDPA > standard overload threshold Standard R99 overload actions
Max power
Node-B Tx power
PtxOffsetHSDPA
PtxnonHSDPA
PtxNC
PtxTargetHSDPA
Ptxtotal
PtxTarget
PtxOffset
A B C
HSDPAPriority 1,2; 1 = HSDPA priority
PtxTargetHSDPA Target for transmitted non-HSDPA power
-10..50 dBm; 0.1 dB; 38.5 dBm
PtxOffsetHSDPA Offset for transmitted non-HSDPA power
0..6 dB; 0.1 dB; 0.8 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 183 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 183
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix: – Static HS-PDSCH Power Allocation
– Cell Reselection
– Iub Flow
– Congestion Control
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 184 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 184
Cell Re-selection (1/3)
• HSDPAMobility set to disabled
• IF- mobility handled by HSDPA Cell Reselection, not by serving cell change
• IF- / IS- mobility handled by same events as for serving cell change
• HSDPA cell reselection
• Transition to CELL_FACH based on event 1a
• Handling depends on setting of EnableRRCRelease
if disabled 1a triggers transition to Cell_FACH immediately
if enabled 1a triggers IF- measurements only; transition to cell_FACH triggered by release margins
EnableRRCRelease
Enable RRC connection release
HOPS; 0 = disabled; 1 = enabled
HSDPARRCdiversity
SHO of the HSDPA capable UE
RNHSPA; 0 = disabled; 1 = enabled
• HSDPARRCdiversity
• can disable SHO for stand alone SRB of HSDPA capable UE (e.g. according addition window)
• reduces capacity consumption due to stand alone RRC connections (more capacity available for HSDPA)
• if conditions for HSDPA mobility fulfilled, SHO for stand alone SRB is allowed in any case (e.g. triggered by release margins)
HSDPAMobility Serving HS-DSCH cell change & SHO on/off switch
RNFC; 0 = HSDPA cell reselection;
1 = Serving HS-DSCH cell change
IF: Interfrequency
IS: Intersystem
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 185 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 185
Cell Re-selection (2/3)
Measurement Reports
EnableRRCRelease = disabled
Risk of ping-pong
But UE connected mostly to optimum cell
AdditionWindow
FMCS; 0..14.5 dB; 0.5 dB; 4 dB
Recommended 0 dB
time
Ec/Io
CPICH 2
Addition
Time
Addition Window
CPICH 1
HSDPA CELL_FACH HSDPA
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 186 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 186
time
Ec/Io
CPICH 2
Measurement Reports
CPICH 1
HSDPA CELL_FACH
ReleaseMarginAverageEcNo ReleaseMarginPeakEcNo One margin need to be exceeded only
HSDPA
Cell Re-selection (3/3) EnableRRCRelease = enabled
No ping-pong
But UE often connected to non optimum cell
Addition
Time
Addition Window
ReleaseMarginAverageEcNo Release margin for average Ec/Io
HOPS; -6..6; 0.1; 2.5 dB
ReleaseMarginPeakEcNo Release margin for peak Ec/Io
HOPS; -6..6; 0.5 dB; 3.5 dB
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 187 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 187
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix: – Static HS-PDSCH Power Allocation
– Cell Reselection
– Iub Flow
– Congestion Control
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 188 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 188
Iub Flow Control (1/4)
• Objective
– Node B has to offer sufficient data for HSDPA
– to avoid overflow of its buffer
– to be performed per HSDPA connection on Iub
• Node B informs RNC about
– Max. number of MAC-d PDUs (credits) allowed to be sent by RNC for unlimited 10ms periods.
That means that the RNC can send data according to latest capacity allocation as long as new
capacity allocation is received
• Number of assigned credits are recalculated by BTS each 10ms and signaled to the RNC (if
differs enough from the previously signaled). Calculated capacity allocation depends on
– Air interface throughput estimation (the higher, the more credits)
– Buffer occupancy (the higher, the less credits)
• BTS prevents packet loss due to buffer overflow by reducing the capacity allocation in case of air
interface congestion and ensures that the HSDPA capacity can be reached by having enough
data to fill the reserved power allocation
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 189 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 189
Iub Flow Control (2/4)
Node B RNC
CAPACITY REQUEST
Priority
User buffer size in RNC
CAPACITY ALLOCATION
Priority
User buffer size in Node B
Credits (number of MAC-d PDUs)
Repetition period (number of time intervals)
Credit validity interval (duration of time interval)
DATA
Priority
User buffer size in RNC
Length of MAC-d PDU
MAC-d PDUs
Example:
Credits = 4
Repetition period = 3
Credit validity interval = 10 ms
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 190 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 190
Iub Flow Control (3/4)
• Number of credits allocated per user decreases and the HSDPA connection throughput decreases as the number of connections increases
• Number of PDU transferred drops frequently when 1 HSDPA connection is active only
0
10
20
30
40
50
60
0 20 40 60 80 100 120 140 160 180 200 220 240 260 280
Time (seconds)
Nu
mb
er
of
MA
C-d
PD
U (
33
6 b
its
)
MAC-d PDU sent to Node B
Credits allocated by Node B
2 active UE
3 active UE 4 active UE
1 active UE
0
10
20
30
40
50
60
0 20 40 60 80 100 120 140 160 180 200 220 240 260 280
Time (seconds)
Nu
mb
er
of
MA
C-d
PD
U
MAC-d PDU sent to Node B
Credits allocated by Node B
Raw data Averaged data
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 191 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 191
Iub Flow Control (4/4)
0
100
200
300
400
500
600
0 25 50 75 100 125 150 175 200 225 250 275 300
Time (s)
No
de
B B
uff
er
Oc
cu
pa
nc
y (
MA
C-d
PD
U) Connection 1
Connection 2
Connection 3
Connection 4
2 active UE
3 active UE
4 active UE
1 active UE
0
100
200
300
400
500
600
0 25 50 75 100 125 150 175 200 225 250 275 300
Time (s)
No
de
B B
uff
er
Oc
cu
pa
nc
y (
MA
C-d
PD
U) Connection 1
Connection 2
Connection 3
Connection 4
Raw data Averaged data
• Node B buffer occupancy can be evaluated as follows
number of acknowledged MAC-d PDU - number of MAC-d PDU transferred from the RNC
• Comparison with previous slide shows, that number of credits decreases also because of high buffer occupancy
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 192 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 192
HSDPA RRM • HSDPA Principles
• HSDPA Protocols & Physical Channels
• RU50 Capabilities & Baseband Configuration
• HSDPA Link Adaptation
• HSDPA H-ARQ
• HSDPA Packet Scheduling
• Basics of HSDPA Power Allocation
• Basics of HSDPA Code Allocation
• Basics of HSDPA Mobility
• HSDPA Channel Type Selection & Switching
• Associated UL DCH
• HSDPA Improvements
• Other Features
• Appendix: – Static HS-PDSCH Power Allocation
– Cell Reselection
– Iub Flow
– Congestion Control
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 193 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 193
Iub Congestion Control CC (1/2)
• Objective: – RNC can not see Iub congestion towards Node B after hub node – Iub congestion must be detected by Node B
• RNC informs Node B by DL Frame Protocol about: – Build up delay – Sequence number
• Node B thus can detect: – Too strong delay of frames – Loss of frames
• Delay thresholds: – 3 thresholds (BTS commissioning parameter) – Minimum threshold Thmin: 0..5000 ms; 50 ms – Intermediate threshold Thmid: 0..5000 ms; 250 150 ms
– Maximum threshold Thmax: 0..5000 ms; 1000 250 ms
• Actions: – Delay < Thmin no action – Thmin ≤ delay ≤ Thmid Node B reduces credits for RNC with low probability (depending
linearly on delay with low slope) – Thmid ≤ delay ≤ Thmax Node B reduces credits for RNC with high probability (depending
linearly on delay with high slope) – Delay > Thmax or frame loss Node B reduces credits for RNC in any case
• If QoS aware scheduling applied: – for high priority service Node B reduces credits for RNC with lower probability than for low priority
service
HSDPACCEnabled
WBTS; 0 (disabled);
1 (enabled)
18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 194 18/08/2015 © Nokia 2014 - RN3167AEN50GLA1 194
Iub Congestion Control (2/2)
Delay [ms]
1
Thmax
Probability for less credits P(delay)
Pmax
Thmid Thmin
Less credits in any case
Less credits with rapidly
increasing P(t)
Less credits with slowly
increasing P(t)