Está en la página 1de 43

TA-TC 6270 /Version 01/Chap.

02 Call-
connection analyses
1
HSPA
S.1 General Aspects
S.2 HSDPA
S.3 HSUPA
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
2
S.1 General Aspects
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
3
Nultiplexing options
With the support of HSPA (HSDPA plus HSUPA or E-DCH) there is a great variaty of TrCH
combinations. Up to 7 different TrCH combinations in CELL_DCH state are possible in Rel. 6 of
3GPP but UTRAN will not configure all possible combinations. However, HSUPA capable UEs
must support all of them.
The RBs can be multiplexed with transport channel type
- "DCH for the UL or DL, when the corresponding DCH transport channel are configured.
- "E-DCH" for the UL, when the corresponding E-DCH MAC-d flow(s) is configured.
- "HS-DSCH" for the DL, when the corresponding MAC-d flow(s) is configured.
DCH is needed for CS traffic, which is usually symmetric. PS traffic can be configured to all options,
where limited support (usually as option) for RT PS traffic on HS-DSCH/E-DCH is given. RT PS
traffic needs so the DCH/DCH option. The decision is done in the RNC with knowledge about the
type of traffic and the type of UEs. Switching between the different TrCH options is handled by
Channel Type Switching (CTS) depending on load, capability, mobility.. . Changing the rate for
the Rel 99 traffic channel is provided by BRA (Bit Rate Adaptation).
In Rel 99: only DCH/DCH possible
In Rel 5: only DCH/DCH, HS-DSCH + DCH/DCH possible
All other combinations should be supported starting with Rel 6 UEs!!!
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
+
TrCH combinations and RRC states
RRC idle
CELL_DCH
CELL_PCH
Paging / SRB 0
CELL_FACH
FACH / RACH
URA_PCH
Paging / SRB 0
DCH / DCH
DCH / E-DCH*
HS-DSCH / DCH
HS-DSCH / E-DCH
HS-DSCH + DCH / DCH
HS-DSCH + DCH / E-DCH + DCH HS-DSCH + DCH / E-DCH*
RRC connected
TCH combinations for UL / DL, * not likely to be implemented
3GPP 25.331 (8.5.21)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
S
S.2 HSDPA
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
6
HSDPA analyses
HSDPA Capable cell
HSDPA (high-speed downlink packet access) is a wideband code division multiple access (WCDMA) key
feature, which provides high data rate transmission in a CDMA downlink to support multimedia services.
HSDPA brings high-speed data delivery to 3G terminals, ensuring that users requiring effective multimedia
capabilities benefit from data rates previously unavailable because of limitations in the radio access network
(RAN).
HSDPA Capable UEs
NodeB Rel. 99
NodeB with HSDPA
Rel 5 or later
D
C
H
-
A
D
C
H
-
B
D
C
H
-
C
Fast pipe is shared among UEs Dedicated pipe for every UE
S
c
h
e
d
u
l
i
n
g
A
,
B
,
C
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
7
Rel S !mplemntation
In the Release 5 implementation the radio bearer can only be configured to
-"DCH for the UL and DL, when the corresponding DCH transport channel are configured.
-HSDPA in DL, DCH in UL plus DL (DCH in DL is needed in all cases for the SRB).
-FACH
All other mentionned possibilities require support of Rel 6 UEs.
The Channel Type Switching between these states can be used to handle mobility for example. (Very basic
implementation, switch to FACH, let the UE do ist cell update.
Today normally the Softhandover for the A-DCH is supported, anyway there are situations, which require special
support, for example, the support of compressed mode for the A-DCH may not be given, or HSDPA over Iur may
not be implemented.
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
8
RRC states in 3GPP Rel 5
RRC idle
CELL_DCH
CELL_PCH
Paging / SRB 0
CELL_FACH
FACH / RACH
URA_PCH
Paging / SRB 0
DCH / DCH
HS-DSCH + DCH / DCH
RRC connected
3GPP 25.331 (8.5.21)
Possible transitions
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
9
HSDPA channels
A
s
s
o
c
i
a
t
e
d
D
P
C
H
1
-
1
5
x
H
S
-
P
D
S
C
H
1
-
4
x
H
S
-
S
C
C
H
H
S
-
D
P
C
C
H
Rel99
DCH
Needed for UL data
and the SRB
(SRB can use E-DCH
from Rel 6 on)
Needed for DL data
(eg CS traffic)
and the SRB
(SRB can use HS-PDSCH
from Rel 6 on)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
10
Codes
The HSDPA resources of a UTRAN cell consume Channelization Codes. The channelization codes spreading
factors (SFs) for HS-PDSCHs and HS-SCCHs are 16 and 128, respectively. All HS-PDSCH and HS-SCCH
channelization codes which one single UE can receive are under the primary scrambling code (the associated
DCHs can be under secondary SCs) . The maximum configuration, allows 15 HS-PDSCHs and 4 HS-SCCHs per
cell (the minimum is one HS-PDSCH and one HS-SCCH). In standard implementation the code resources are
permanently configured by O&M. In some vendors case a dynamic allocation between Rel. 99 and HS-PDSCH
codes is available (Flexible code tree management).
In standard implementation there is one code tree available. When 15 codes are configured, There are allmost no
codes left for Rel. 99 users (voice needs Rel 99 DCHs, all HSDPA users need an associated DCH in Rel 5
implementation).
HS-PDSCHs and Rel. 99 Code Shortage
-Alternative 1: Introduce 2nd Frequency F2 beside F1. F1 is for Idle mode & Rel. 99 traffic, F2 is the HSDPA
preferred layer
-Alternative 2: Allow Secondary Scrambling Code on F1. HS-PDSCHs and HS-SCCHs on Secondary Scrambling
Code, Impact on Admission and Congestion Control, Transmitted Carrier Power Utilization
-Alternative 3: Flexible code tree management
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
11
Number of HS-PDSCH codes
SF = 128
SF = 64
SF = 32
SF = 8
SF = 16
SF = 4
SF = 2
SF = 1
Codes for the cell common channels
Code for one
HS-SCCH
Codes for 5
HS-PDSCH's
(Max 15)
SF = 256
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
12
UE in CELL_DCH
HSDPA Radio Link Setup
NODE B
In case no RL has
already been
established (UE
on cell FACH), the
Radio Link Setup
procedure is used
instead of the
Radio Link
Reconfiguration
procedure.
NBAP: RADIO LINK RECONFIGURATION PREPARE
AAL2 Setup
NBAP:RADIO LINK RECONFIGURATION COMMIT
RRC:RADIO BEARER RECONFIGURATION
NBAP: RADIO LINK RECONFIGURATION READY
RRC:RADIO BEARER RECONFIGURATION COMPLETE
HS-DSCH Information, selected HS-DSCH RNTI and the HS-PDSCH RL ID
HS-DSCH Information Response
Common Transport Channel Priority Indicator and User Buffer Size
: Common Transport Channel Priority Indicator, HS-DSCH Credits, HS-DSCH Interval,
HS-DSCH Repetition period, Maximum MAC-d PDU length.
HS-DSCH Frame Protocol: HS-DSCH CAPACITY REQUEST
HS-DSCH Frame Protocol: HS-DSCH CAPACITY ALLOCATION
HS-SCCH
UE listens to HS-DCCH (High Speed Downlink Control Channel)
UE in CELL_DCH
HS-DSCH + DCH / DCH
DCH / DCH
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
13
Number of active users
Number of simultaneous HSDPA users on average (per day, hour)
16 hsdpa users (16 is typically the maximum of HSDPA users per cell, can be more)
.
3
2
1 hsdpa users
No hsdpa users
no user (here 90 %)
2 User (here 9 %)
3 user here 1 %
PS - CS traffic distribution
Hour ,day, month,
amount of HSDPA devices,
HSDPA licences, amount
Of codes per cell, second
Carrier needed?
Max peak number of simultaneous HSDPA users (per day, hour)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
1+
HSDPA Code usage
HSDPA Code usage rate
utilization of the HS-PDSCH codes
The HS-PDSCH code usage ratio considers the accumulated number of HS-PDSCH codes of one TTI
related to the total number of TTI per sampling period and the Max. no of HS-PDSCH codes per cell.
TTIs where HS-PDSCH codes have been transmitted and where no codes i.e. no TTIs have been
transmitted shall be considered. There is no difference if the codes are used as QPSK or 16QAM
codes. The usage ratio of HS-PDSCH code is measured. At the end of GP, the mean, minimum and
maximum values are provided.
Maximum
Minimum
Average
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
1S
HSDPA Throughput

Higher layer data


Higher layer data packets (e.g. IP packets)
Transport block (TB)

RLC PDU
RLC

MAC-d
MAC-hs PDU
Layer1

MAC-hs PDU
MAC-hs
MAC-d PDU
R
N
C
N
o
d
e
-
B
*Headers of the different PDUs are defined in TS25.321 and TS25.322
Iub
21 bits 57 bits
3440 bits
320 bits 320 bits
16 bits
header* data (RLC SDU) header* data (RLC SDU)
header* data (MAC-d SDU) header* data (MAC-d SDU)
data (MAC-hs SDU) header* data (MAC-hs SDU)
10x336=3360 bits
336 bits
336 bits
16 bits
1600 kbps
1680 kbps
1720
kbps
padding
LA defines fixed number of MAC-d
PDUs for one MAC-hs PDU (10)
8 other
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
16
Example of throughput calculation
320 kbps QPSK
Modulation
1.60 / 2.24 Mbps 10 / 14 3440 / 4748 QPSK / 16QAM 5
1.60 / 2.56 Mbps 10 / 16 3440 / 5480 QPSK / 16QAM 5
1.60 / 2.88 Mbps 10 / 18 3440 / 6101 QPSK / 16QAM 5
1.60 / 3.20 Mbps 10 / 20 3440 / 6793 QPSK / 16QAM 5
1.60 / 3.36 Mbps 10 / 21 3440 / 7168 QPSK / 16QAM 5
5
5
5
5
5
5
5
4
3
2
1
HS-DSCH
Codes
160 kbps 1 365 QPSK
480 kbps 3 1036 QPSK
640 kbps 4 1380 QPSK
3440 / 4420
3440
3090
2726
2404
2046
1711
699
Transport Block
Size
1.60 Mbps 10 QPSK
1.60 / 2.08 Mbps 10 / 13 QPSK / 16QAM
9
8
7
6
5
2
Number of
MAC-d PDU per
MAC-HS PDU
1.44 Mbps QPSK
1.28 Mbps QPSK
1.12 Mbps QPSK
960 kbps QPSK
800 kbps QPSK
320 kbps QPSK
RLC Throughput
Modulation
LA in Node B defines (based
on the received Channel Quality
Indication-CQI) about the amount
of data to be sent to the UE.
Example is for max 5 codes.
Besides the 336 bit MAC-d PDU
there Is for Category 10
UE a high transport block size
PDU containing 656 bits
(640 data plus 16 header)
Example is for 336 PDU size
data (MAC-d SDU)
MAC-d
header
data (MAC-d SDU)
656 bits
MAC-d
header
336 bits
high transport block sizes for category 10 UEs:
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
17
Node B measurements
Number of/
Dropped/
discarded
MAC-d
PDUs
Packet Scheduler Flow Control
Link adaptation / Power Control
HS-SCCH power
Discarded
MAC-hs
PDUs
MAC-D flow
Original
transmission
by QSPK/
16QAM
Retrans. by
QPSK/
16QAM
Retrans.
distribution
FP prority
queue
DSP
transmission
buffer
HARQ
process
Iub Uu
CQI
distribution
TRX
Radio
connection
Node B
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
18
HSDPA Throughput
BTS measures the number of incoming PDU in DL direction
Transferred data volume at Iub can be calculated as:
When one MAC-hs PDU is correctly delivered without retransmission or X number of
retransmissions and the ack has been received the respective counter below is incremented by one
HSDPA Retransmission ratio done by MAC-hs can be calculated based on successfully sent
MAC-hs PDUs divided by totally sent MAC-hs PDUs Actually, this is the successfully sent
MAC-hs PDUs divided by all transmitted MAC-hs PDUs including retransmissions
Transmitted Data
Number of MAC-D PDUs received
[ ] Mbit
1000000
656 656)_TOT MAC_D_PDU( 336 336)_TOT MAC_D_PDU( +

The megabit is most commonly used when referring to data transfer rates in network speeds, e.g. a 100 Mbit/s (megabit per second)
connection. In this context, like elsewhere in telecommunications, it always equals 10
6
bits.(not 1020 bits=1 mebibit (Mibit))
Number of HS PDUs transmitted
Once
Twice
3 times
..
Throughput calculations could
consider the traffic class
Background
Interactive
Streaming
(Conversational)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
19
HSDPA Throughput
When one MAC-hs PDU is assembled and transmitted based on Link Adaptation selection, then it
may happen that it is correctly delivered without any retransmission, or some retransmissions are
needed (with same TFRC [Transport Format and Resource Combinations] as the original tx).
-In case the timer expires for certain MAC-d flow then all the non acknowledged MAC-hs PDUs are
cleared.
-In case the max number of retransmissions (Parameter, normally set to 4) is exceeded for certain
HARQ flow the corresponding MAC-hs is cleared.
-MAC-D PDUs can be dropped from BTS buffer due to overflow of the buffer
Number of MAC-HS deleted due to Max number of retransmissions
Number Mac-D dropped due to overflow
Discarded PDUs
Number of MACHS PDUs deleted
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
20
UL Throughput on the A-DCH
HS_DPCCH Channel requires an UL DPCH (return channel) to be allocated.
The return channel is also used for transmission of the TCP acknowledgements, RLC acknowledgements and
other user data. KPI have been defined to monitor the uplink bit rates assigned to HSDPA connections.
Supported bit rate can be usually 64, 128 or 384 kbps
These bit rates will depend upon the USIM QoS profile as well as RNC Parameter settings and load. Bit rate can be
also downgraded due the congestions depending of activated features. Increased uplink bit rates allow greater
throughput performance but have a greater requirement for resources RF coverage, NodeB resources, Iub
transport
HS_DSCH return channel allocations 128kbps
HS_DSCH return channel allocations, 384kbps
UL Bitrate of the A-DCH (rel 99)
HS_DSCH return channel allocations 64kbps
HS_DSCH return channel allocations, xxxx kbps
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
21
HSDPA traffic on Iub
-RLC: PDU size 320 bits payload + 16 bits header = 336 bits, overhead is 16/320 = 5 %.
-MAC-d: No header.
-FP: HS-DSCH data frames FP-header and tail produces 9 bytes overhead and each
MAC-d PDU produces 1 padding byte overhead. There may be 1 to 34 PDUs in the HS-
DSCH frame. Thus, the FP overhead is varying between 3 to19 %. For example, for 10
PDUs in a frame the FP overhead is 9 + 10 = 19 bytes = 152 bits, and 152 / 3360 = 4.5
%. FP data rate = 500*3512 = 1.756 Mbps.
-The AAL2 overhead is 5 / 48 = 10.4 %.
-The ATM overhead is 5 / 53
-MAC-hs: 21 bit header + padding. For 10 * PDU the header + padding = 80 bits, with
payload (10*336) = 3440 bits. Data rate = 500 * 3440 = 1.72 Mbps.
TNL
HS-DSCH-FP
MAC-d
TCP
IP
PDCP
RLC
RLC MAC L1 FP rate (Iub)
Payload + RLC headers + MAC-hs headers
and padding
1.68 Mbps 1.6 Mbps 1.756 Mbps
Payload + RLC
headers + FP
1.72 Mbps
Example with 5 codes and QPSK:
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
22
CQI distribution
H
S
-
D
P
C
C
H
7168
7168
7168
7168
6793
6101
5480
4748
4420
3762
3090
3090
2726
2404
2046
1711
1380
1036
699
699
699
365
TBS
16QAM 5 22
16QAM 5 23
16QAM 5 24
16QAM 5 25
QPSK 4 9
QPSK 2 6
16QAM 5 21
16QAM 5 20
16QAM 5 19
16QAM 5 18
16QAM 5 17
QPSK 5 16
QPSK 5 15
QPSK 5 14
QPSK 5 13
QPSK 5 12
QPSK 5 11
QPSK 5 10
QPSK 3 8
QPSK 2 7
QPSK 2 5
QPSK 1 <5
Mod Codes CQI
UE categories 1...6
The UE reports the CQI
measured assuming a
transmit power PCPICH + +
.
Measurement power offset
signalled to Node B and UE by
NBAP and RRC (example =
PtxMaxHSDPA PCPICH
depends on vendor)
Reference power adjustment
is used to signal how much
quality is better than maximum
TBS supported by UE (given
in UE category specific
tables).
Table to left (from 25.214)
defines CQI for UE categories
1 to 6. Based on 10% BLER.
The Algorithm to calculate CQI
value is not specified by 3GPP
so CQI depends on UE.
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
23
CQI distribution
CQI distribution (very poor environment)
0
100000
200000
300000
400000
500000
600000
700000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
CQI value
N
u
m
b
e
r
o
f
s
a
m
p
l
e
s
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
/ -
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
2+
CQ! distribution
Channel Quality Indicator
one counter for each CQI value
plus one for the failed decoding
CQI distribution gives an idea about the average CIR in that cell, can be so the basis of
dimensioning the Iub interface, optimization of power and other RF characteristica.
Furthermore a broad distribution gives indication about a big variance in the
userdistribution, it may be good to deploy in such cases indoor solutions to seperate
users in buildings from those outdoor.
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
2S
HSDPA power
1-15 x HS-PDSCH (at least) no fast PC
HS-DPCCH (fast power control)
Max power
Node-B Tx power
Power nonHSDPA
Power for Real time traffic
Ptxtotal
Active MAC-D flow (s)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
26
HSDPA traffic on Iub
-RLC: PDU size 320 bits payload + 16 bits header = 336 bits, overhead is 16/320 = 5 %.
-MAC-d: No header.
-FP: HS-DSCH data frames FP-header and tail produces 9 bytes overhead and each
MAC-d PDU produces 1 padding byte overhead. There may be 1 to 34 PDUs in the HS-
DSCH frame. Thus, the FP overhead is varying between 3 to19 %. For example, for 10
PDUs in a frame the FP overhead is 9 + 10 = 19 bytes = 152 bits, and 152 / 3360 = 4.5
%. FP data rate = 500*3512 = 1.756 Mbps.
-The AAL2 overhead is 5 / 48 = 10.4 %.
-The ATM overhead is 5 / 53
-MAC-hs: 21 bit header + padding. For 10 * PDU the header + padding = 80 bits, with
payload (10*336) = 3440 bits. Data rate = 500 * 3440 = 1.72 Mbps.
TNL
HS-DSCH-FP
MAC-d
TCP
IP
PDCP
RLC
RLC MAC L1 FP rate (Iub)
Payload + RLC headers + MAC-hs headers
and padding
1.68 Mbps 1.6 Mbps 1.756 Mbps
Payload + RLC
headers + FP
1.72 Mbps
Example with 5 codes and QPSK:
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
27
HSDPA serving cell change 1
2. Radio Link Setup Request
3. Radio Link Setup Response
5. ALCAP Iub Data Transport Bearer Setup (DCH)
10. Radio Link Reconfiguration Prepare
11. Radio Link Reconfiguration Ready
RNSAP
1. Radio Link
Addition Request
RNSAP
4. Radio Link
Addition Response
NBAP
NBAP
6. ALCAP Iub Data Transport
Bearer Setup (DCH)
7. Radio Link
Reconfiguration Prepare
NBAP
RNSAP
NBAP
NBAP
12. Radio Link
Reconfiguration Ready
RNSAP
13. ALCAP Iub Data Transport Bearer Setup (HS-DSCH)
14. ALCAP Iub Data Transport
Bearer Setup (HS-DSCH)
Source
Target
Drift
Serving
8. Radio Link Reconfiguration Prepare
9. Radio Link Reconfiguration Ready NBAP
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
28
HSDPA serving cell change 2
Source
Target
Drift
Serving
15. Radio Link
Reconfiguration Committ
RNSAP
NBAP
16. Radio Link Reconfiguration Commit
17. Radio Link Reconfiguration Commit
NBAP
RRC
RRC
18. Physical Channel Reconfiguration
19. Physical Channel Reconfiguration Complete
20. ALCAP Iub Data Transport
Bearer Release (HS-DSCH)
21. ALCAP Iub Data Transport
Bearer Release (HS-DSCH)
22. Radio Link Deletion
Request
RNSAP
23. Radio Link Deletion
Request
NBAP
24. Radio Link Deletion
Response
NBAP
25. Radio Link Deletion
Response
RNSAP
26. ALCAP Iub Data Transport
Bearer Release (DCH) 27. ALCAP Iub Data Transport
Bearer Release (DCH)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
29
HSDPA - mobility
Number of initiated HS-DSCH Serving Cell Changes
(SCC)
One counter per cause
-causes depend on the implementation (vendor)
- 1d or 1b events may be usede as trigger, Active set updates as well.
Number of failed HS-DSCH Serving Cell Changes
one counter per cause
Possible causes,
-Node B resources (radio, baseband, UE,..)
-Transport resources
-
Number of successfull HS-DSCH Serving Cell Changes
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
30
Performance of the A-DCH
A
s
s
o
c
i
a
t
e
d
D
P
C
H
1
-
1
5
x
H
S
-
P
D
S
C
H
1
-
4
x
H
S
-
S
C
C
H
H
S
-
D
P
C
C
H
Rel99
DCH
Cell B
Cell A
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
31
Softhandover observations
Number of cells in the active set for HSDPA active UE
Replacements 1c
There is only one and one HSDPA serving cell at any time, anyway the associated DCH (A-DCH) can be
in soft-handover state, depending on the implementation, this can be basis for optimization. In some
vendors case there is an independent set of parameters for HSDPA active UEs. 3GPP defines UE should
support up to 6 cells in the active set, in the usually implementations it is restricted to 3.
Additions 1a
Deletions 1b
Duration (per HSDPA Serving cell)
1 cell in the active set
2 cells in the active set
3 cells in the active set
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
32
S.3 HSUPA
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
33
HSUPA Physical channels
The UE can have:
-1-2 E-DPDCH [4 possible in future (2xSF 2 +2xSF4), but with UL DPDCH max is 2]
-1-3 E-RGCH [max active set size can be 4, 3 implementation]
-1-3 E-HICH [max active set size can be 4, 3 implementation]
-E-AGCH
Serving E-DCH Cell and HS-DSCH serving cell are always identical.
[3GPP 25.309 (6.3.2)]
The E-DCH Dedicated Physical Data Channel (E-DPDCH) and E-DCH Dedicated Physical Control Channel
(E-DPCCH) are called E-DCH Dedicated Physical Channel (E-DPCH).
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
3+
HSUPA Physical channels
E
-
D
P
D
C
H
(
1
.
.
.
2
)
E
-
D
P
C
C
H
E
-
R
G
C
H
(
1
.
.
.
3
)
E
-
A
G
C
H
O
n
e
f
o
r
a
l
l
t
h
e
c
e
l
l
s
t
h
a
t
b
e
l
o
n
g
t
o
t
h
e
E
-
D
C
H
r
a
d
i
o
l
i
n
k
s
e
t
.
O
n
e
i
n
t
h
e
s
e
r
v
i
n
g
E
-
D
C
H
c
e
l
l
E
-
H
I
C
H
(
1

3
)
1
-
1
5
x
H
S
-
P
D
S
C
H
1
-
4
x
H
S
-
S
C
C
H
H
S
-
D
P
C
C
H
Plus
HSDPA
Plus
DCH
(Option)
share one code
F
-
D
P
C
H
or
UL DPDCH: max. 64 kbit/s
(when E-DPCCH configured)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
3S
Definitions
Serving E-DCH cell
Cell from which the UE receives Absolute Grants from the NodeB scheduler. A UE has one Serving E-DCH cell.
Serving E-DCH Radio Link Set
Set of cells which contains at least the Serving E-DCH cell and from which the UE can receive and combine one Relative
Grant. The UE has only one Serving E-DCH RLS. So the serving RLS is determined by the UTRAN if the cells in the
same NodeB being in the E-DCH active set should also transmit the same RG like the E-DCH serving cell.
Non-Serving E-DCH Radio Link(s)
Cells which belong to the E-DCH active set but do not belong to the Serving EDCH RLS and from which the UE can receive
one Relative Grant. The UE can have zero, one or several non-serving E-DCH RL(s). The UTRAN wants to indicate to the
UE, that these non-serving E-DCH cells transmit independent RGs.
DCH Radio Links
Cells which serve the DCH. Not every cell in the DCH active set is necessarily part of the E-DCH active set.
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
36
DL codes for HSPA
HSUPA can only be set up together with HSDPA. For HSUPA, code allocation for E-AGCH, E-RGCH, and E-HICH is
additional necessary.
The channelization codes spreading factors (SFs) are:
16 for HS-PDSCHs
128 for HS-SCCHs
128 for E-RGCH / E-HICH
256 for E-AGCH
The maximum number of HS-SCCH is three for the separate type of common channel. Combined type of
common channel is possible.
The following maximum configurations are currently available:
PCH and FACH are mapped on the same S-CCPCH:
14 HS-PDSCHs
4 HS-SCCHs
1 E-HICH/E-RGCH and 1 E-AGCH
All HS-PDSCH, HS-SCCH, E-AGCH and E-RGCH/E-HICH channelization codes an individual UE can receive
must be subordinated to the same scrambling code tree, that is the primary scrambling code.
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
37
DL HSPA codes
SF = 128
SF = 64
SF = 32
SF = 8
SF = 16
SF = 4
SF = 2
SF = 1
H
S
-
S
C
C
H
Codes for 15
HS-PDSCH's
(
SF = 256
Code Image Example: FACH/PCH Separated, with max. 1 HS-SCCH, 1E-
HICH/E-RGCH/E-AGCH and 15 HS-PDSCH (other allocations possible!)
P
-
C
P
I
C
H
P
-
C
C
P
C
H
A
I
C
H
P
I
C
H
F
A
C
H
P
C
H
E
-
H
I
C
H
/
E
-
E
R
G
C
H
E
-
A
G
C
H
1 code left
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
38
E-DCH physical layer categories
5.76 Mbps 11484 20000 10 & 2 ms 2 4 6
22996
-
5772
-
2798
-
max. # of
E-DCH Bits* / 2
ms TTI
11.52 Mbps 20000 10 & 2 ms 2 4 7*
2.0 Mbps 20000 10 ms only 2 2 5
2.92 Mbps 20000 10 & 2 ms 2 2 4
1.46 Mbps 14484 10 ms only 4 2 3
1.46 Mbps 14484 10 & 2 ms 4 2 2
0.73 Mbps 7110 10 ms only 4 1 1
Reference
combination
Class
max. #. of
E-DCH Bits* / 10
ms TTI
2 & 10 ms TTI
E-DCH
support
min. SF
max.
E-DCH
Codes
E- DCH
Category
Extracted from TS 25.306: UE Radio Access Capabilities
7* category 7 is defined in 3GPP Rel 7 and supports QPSK and 16 QAM in Uplink
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
39
The E-DCH Radio Link Set (E-
RLS)
Serving E-DCH cell
Has to be the HSDPA Serving Cell
Serving E-DCH Radio Link Set
Served by one Node B
E-DCH Radio Link Set
DCH Radio Link Set
(Support of 4 cells in active set usually not given)
Cell A
Cell A
Cell B
Cell A
Cell B
Cell C
Cell A
Cell B
Cell C
Cell D
Cell A
Cell B
Cell C
Cell D
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
+0
E-DCH traffic observations
Number of E-DCH radio link establishments
From RRC FACH substate
Number of successful E-DCH radio link establishments
Per traffic category
Number of failed HSUPA setups
Causes (resources RNC, BTS
or transport, UE)
From RRC DCH substate
Number of simultaneous E-DCH users per cell
Causes (resources RNC, BTS
or transport, UE)
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
+1
Softhandover observations
Number of started E-DCH serving cell changes (in serving cell)
Causes
There is only one and one E-DCH serving cell at any time for one UE using HSUPA. The E-DCH can be
in soft-handover state and the Serving Cell can change. 3GPP defines UE should support up to 6 cells in
the active set, in the usually implementations it is restricted to 3.
Number of successful E-DCH serving cell changes (in source cell)
Intra Node B
Inter Node B
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
+2
HSPA power
Max power
Node-B Tx power
Power nonHSPA
P total
Active MAC-D flow (s)
or MAC-es flow (s)
P
HSPA
= P
HS-PDSCH
+ P
HS-SCCH
+ P
E-AGCH
+ P
E-RGCH
+ P
E-HICH
P
non-HSPA
= P
total
P
HSPA
NBAP: COMMON MEASUREMENT REPORT
Transmitted carrier power (TCP) = P total
Power nonHSPA
TA-TC 6270 /Version 01/Chap. 02 Call-
connection analyses
+3
Power and HSPA
P
HSPA
= P
HS-PDSCH
+ P
HS-SCCH
+ P
E-AGCH
+ P
E-RGCH
+ P
E-HICH
The non-HSPA transmitted carrier power (TCP) refers to the amount of TCP of all codes which are
not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, or E-HICH. The non-HSPA TCP is the
difference between the total TCP on one downlink carrier from one UTRAN access point and the
TCP of all codes which are not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH, or E-HICH, i.e.
the HSPA TCP (P
HSPA
). In other words, P
HSxPA
is calculated as follows:
The resulting P
non-HSPA
is used to calculate the non-HSPA power ratio which will be included in a
NBAP: COMMON MEASUREMENT REPORT message.
P
non-HSPA
= P
total
P
HSPA

También podría gustarte