Professional Documents
Culture Documents
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
A50016-G5000-Z180-3-7618
ND-59083-180(E)-03
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Caution:
This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table
A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful interference to radio communications.
For system installations it is strictly required to choose all installation sites according to national and local requirements concerning construction rules and static load capacities of buildings and roofs.
For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic
field / force (EMF) limits. Otherwise harmful personal interference is possible.
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their own purposes
could violate the rights of their owners.
Issued by:
Siemens AG, Communications, Hofmannstrasse 51, 81359 Mnchen, Germany and
NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo, Japan
Technical modifications possible.
Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.
Siemens AG:
NEC Corporation:
A50016-G5000-Z180-3-7618
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
2.1.3.2
Issue History
Issue
Date of issue
04/2005
08/2005
Number
08/2005
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Contents
1
1.1
1.2
1.3
1.4
Short Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
In General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Customer Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Interworking / Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2
2.1
2.1.1
2.1.2
2.1.3
2.1.3.1
2.1.3.2
2.1.3.3
2.1.3.4
2.1.4
2.1.4.1
2.1.4.2
2.1.4.3
2.1.4.4
2.1.4.5
2.1.4.6
2.1.5
2.1.5.1
2.1.5.2
2.1.5.3
2.1.5.4
2.2
2.3
2.4
13
13
13
14
15
20
21
21
21
22
22
22
22
23
24
24
25
25
25
25
26
26
26
26
3
3.1
3.1.1
3.1.1.1
3.1.1.2
3.1.2
3.1.3
3.1.4
27
31
33
34
34
35
35
3.1.4.1
3.1.4.2
3.1.5
3.1.5.1
3.1.5.2
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
37
37
37
38
38
38
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
3.1.5.3
3.1.5.4
3.1.5.5
3.1.5.6
3.1.6
3.1.6.1
3.1.6.2
3.1.7
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.3
3.3.1
3.3.2
3.3.3
3.4
Transmission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
HARQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Channel Quality Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Measurements and Performance Measurement (PM) Counters . . . . . . . . . 40
Modifications of Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Downlink Signal Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Uplink Signal Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Modifications of Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Functional Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Core Controller (CC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Channel Coding Card (CHC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Repeater (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Transceiver (TRX) or Digital Radio Interface Card (DRIC) . . . . . . . . . . . . . 43
Man-Machine Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Front Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Front Panel Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Manual Intervention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Operating the Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4
4.1
4.1.1
4.1.1.1
4.1.1.2
4.1.1.3
4.1.1.4
4.1.1.5
4.1.1.6
4.1.1.7
4.1.1.8
4.1.1.9
4.1.1.10
4.1.1.11
4.1.1.12
4.1.1.13
4.1.1.14
4.1.1.15
4.1.1.16
4.1.1.17
4.1.1.18
4.1.1.19
4.1.1.20
4.1.1.21
4.1.2
4.1.2.1
4.1.2.2
4.1.2.3
4.1.2.4
HSDPA Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
HSDPA RAB Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
UE Support of HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
RAB Eligibility for HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Radio Bearer Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
RAB Multiplexing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Impacts on the Radio Bearer Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . 49
RRC Connection State Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Traffic Monitoring and Channel-Type Switching . . . . . . . . . . . . . . . . . . . . . 55
Power Control and Measurement Feedback Parameters . . . . . . . . . . . . . . 55
RAB Setup Procedure from DCH to HS-DSCH . . . . . . . . . . . . . . . . . . . . . . 56
RAB Setup Procedure from FACH to HS-DSCH . . . . . . . . . . . . . . . . . . . . . 60
Channel-Type Switching from FACH to HS-DSCH . . . . . . . . . . . . . . . . . . . 63
Channel-Type Switching from HS-DSCH to FACH . . . . . . . . . . . . . . . . . . . 64
RAB Setup Procedure from HS-DSCH to DCH . . . . . . . . . . . . . . . . . . . . . . 66
RAB Release Procedure from HS-DSCH to DCH . . . . . . . . . . . . . . . . . . . . 68
RAB Release Procedure from Multicall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
RRC Connection Reestablishment Procedure. . . . . . . . . . . . . . . . . . . . . . . 71
Radio Bearer Reconfiguration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SRNS Relocation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
RAB Setup Procedure from CCH to DCH and DCH to DCH . . . . . . . . . . . . 72
Pre-emption and Interaction with Admission Control . . . . . . . . . . . . . . . . . . 73
Allocation of H-RNTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
HSDPA Mobility Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Scenarios for Mobility Handling of HS-DSCH . . . . . . . . . . . . . . . . . . . . . . . 76
MAC-hs Reset and Loss of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Measurement Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
HS-DSCH Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.2.5
4.1.2.6
4.1.2.7
4.1.2.8
4.1.2.9
4.1.2.10
4.1.3
4.1.3.1
4.1.3.2
4.1.3.3
4.1.3.4
4.1.3.5
4.1.3.6
4.1.3.7
4.1.4
4.1.4.1
4.1.4.2
4.1.4.3
4.1.4.4
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.4
Inward Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Change of the Serving HS-DSCH Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Outward Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
DRNC Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
UE Differentiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
HSDPA Admission Control and Congestion Control. . . . . . . . . . . . . . . . . 102
Radio Resource Management (RRM) Issues . . . . . . . . . . . . . . . . . . . . . . 102
Load, Power, and Code Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Admission Control in the CRNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Restriction Control in the CRNC for HSDPA. . . . . . . . . . . . . . . . . . . . . . . 107
Admission Control in the Node B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Congestion Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Integration of the Admission Control Algorithm for HSDPA . . . . . . . . . . . 109
HSDPA Code and Power Allocation and Redimensioning . . . . . . . . . . . . 110
State Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Common Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Code and Power Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Modification and Deletion of HSDPA Resources . . . . . . . . . . . . . . . . . . . 120
Functional Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
HSDPA RAB Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
HSDPA Mobility Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
HSDPA Admission Control and Congestion Control. . . . . . . . . . . . . . . . . 121
HSDPA Code and Power Allocation and Redimensioning . . . . . . . . . . . . 121
Man-Machine Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
HSDPA RAB Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
HSDPA Mobility Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
HSDPA Admission Control and Congestion Control. . . . . . . . . . . . . . . . . 124
HSDPA Code and Power Allocation and Redimensioning . . . . . . . . . . . . 125
Operating the Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5
5.1
5.1.1
5.1.1.1
5.1.1.2
5.1.1.3
5.1.1.4
5.1.2
5.1.2.1
5.1.2.2
5.1.2.3
5.1.2.4
5.2
5.3
5.3.1
5.3.2
5.3.2.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
126
126
126
126
128
128
131
132
132
134
134
134
135
136
136
137
137
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
5.3.2.2
5.3.2.3
5.3.2.4
5.3.3
5.3.4
5.3.4.1
5.3.4.2
5.3.4.3
5.3.4.4
5.4
6
6.1
6.1.1
6.1.1.1
6.1.2
6.2
6.3
6.4
7
7.1
7.1.1
7.1.2
7.1.3
7.1.3.1
7.1.3.2
7.1.3.3
7.1.3.4
7.2
7.3
7.4
8
8.1
8.2
8.3
8.4
10
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
1 Short Description
This chapter serves as short introduction to the High Speed Downlink Packet Access
(HSDPA) feature. The chapter is subdivided into the following sections:
In General
Customer Benefits
Interworking / Dependencies
Prerequisites
1.1
In General
Within UMTS, the acceptance of mobile data services strongly relies on high data
throughputs, high user peak rates with minimum delay. HSDPA (High Speed Downlink
Packet Access) is the breakthrough UMTS feature-set which satisfies highest capacity
demands thus providing the prerequisite for broadband services.
HSDPA is specified in the 3GPP Release 5 Standard. On the downlink, the HSDPA
standard implemented in UMR5.0 refers to a shared control channel (HS-SCCH) and a
shared data-bearing channel (HS-DSCH). The data-bearing channel is known as HSDSCH. Key characteristics of HSDPA are:
A downlink only service, the uplink service remains unchanged.
A packet data service. The network allocates resources for transmitting packets over
the air.
Typical achievable throughput rates are in the range of 1 5 Mbit/s.
The HSDPA key principles are:
Scheduling in the time domain (2 ms) and code domain (15 parallel codes) . This
reduces latency and improves the peak rate.
Adaptive Modulation and Coding (QPSK and 16 QAM) which leads to higher data
rates.
Hybrid ARQ which leads to higher efficiency in transmission and error correction.
HARQ (Hybrid Automatic Repeat Request) is an implicit link adaptation technique. In
HARQ, link layer acknowledgements are used for retransmission decisions. For
HSDPA, HARQ is performed by the MAC-hs protocol situated in the Node Bs and UEs,
where the latter deal with the main processing load.
The downlink transport channel for HSDPA is the HS-DSCH that is mapped to up to 15
HS-PDSCHs. The uplink channel is the HS-DPCCH which carries the feedback information from each HSDPA-capable UE in the active set.
HSDPA terminal capabilities extend from 0.9 Mbit/s up to 14 Mbit/s. The HSDPA capability is independent of Rel 99-based capabilities. If the HS-DSCH has been configured
for the terminal, however, the DCH capability in DL is limited to the value provided by
the terminal.
HSDPA Mobility
The High Speed Downlink Shared Channel (HS-DSCH) is a common transport channel
that is shared by several UEs in the same cell. The MAC-hs functionality of the Node B
performs scheduling of UEs on a per cell basis. Therefore, the UE receives the HSDSCH of one cell and can receive DCHs of multiple cells.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
10
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
11
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
combination with unknown traffic volume, the QoS of all traffic on the same AAL type 2
path may decrease.
Air Interface (Uu) modifications
The Node B has implemented the HSDPA MAC-hs protocol, which is responsible for
scheduling between terminals (UEs). Adaptive Modulation and Coding (AMC) and management of data queues for each UE are some of the new air interface functionalities of
the Node B.
1.2
Customer Benefits
With UMR5.0 making use of HSDPA services, the mobile phone subscriber will experience an improvement of QoS compared to Release 99 UMTS services. The improvements become apparent in terms of:
Peak data rate
Average data rate (i.e. packet call throughput)
Lower latency for interactive and background services
Higher availability of high data rate services
Network Operators will benefit from utilizing UMR5.0 with:
Lowest CAPEX for system capacity increase compared to other capacity-improving
technologies such as smart antennas or the installation of new Node Bs. With
UMR5.0, the Operator's costs per bit will be minimized.
Higher system throughput, i.e. more throughput per cell due to a higher Node B capacity. The Node Bs increased capacity leads to more users and, consequently,
more data throughput per square kilometer.
Higher benchmarking of UMR5.0 operators compared to Rel 99 and existing 2.5G
Operators, which already offer data rates up to 384 kbit/s today.
Enabling of new billing categories, such as mobile flat rates combined with high peak
rates in order to compete with fixed network services like DSL.
Competition with WLAN operators via outdoor coverage, security advantage, and
mobility rather than indoor competition.
Higher performance (factor 3) than CDMA2000 systems (especially important for
Asian and US Markets).
1.3
Interworking / Dependencies
The introduction of HSDPA has a design impact on all UTRAN network elements. Network Management systems have to be adapted as well as terminals which have to be
specially designed for HSDPA purpose.
Dynamic allocation of AMR traffic and HSDPA traffic will coexist. Customers will not experience significant degradations of conventional Rel 99 services by introducing
HSDPA. Since Rel 99 users and HSDPA users share the channelization code tree, a
degradation may occur if Rel 99 users run out of codes. The number of AMR users will
not be affected after UMR5.0 implementation.
1.4
Prerequisites
UEs have to be HSDPA-compliant. UE categories will specify the modulation scheme
supported and its throughput more precisely.
12
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Functional Description
The High Speed Downlink Packet Access (HSDPA) feature enables downlink packet
transmission rates up to 14 Mbit/s on the radio interface, which may coexist with the current Rel 99 services. The PRLC and DHT cards of the current RNC HW do not have sufficient capacity to support the peak rate of HSDPA. Therefore, new hardware (HSDST,
HSPRLC) and a new transport channel (HS-DSCH) have been introduced to enable the
throughput of higher peak data rates compared to Rel 99 data rates. The HSDST card
supports the MAC-d entity and HS-DSCH frame protocol (FP), thus providing higher
throughput than the current DHT card (see 2.1.4 "HSDST Functionality" for details). The
HSPRLC card provides PRLC functionality with a higher throughput (see
2.1.5 "HSPRLC Functionality" for details).
2.1.1
PDCP
RLC
RLC
MAC-d
MAC-d
HS-DSCH
FP
MAC-hs
Phy.
Fig. 2.1
AAL2
AAL5
ATM
ATM
ATM
Phy.
Phy.
Phy.
Node B
Uu
IP
HS-DSCH
FP
MAC-hs AAL2
Phy.
UE
UDP
RNC
Iub
Iu
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
13
Support of HSDPA
FD012249 - UMR5.0
2.1.2
Feature Description
Radio Subsystem
Iu
CLP
GMUX
DCCH
M2C
DTCH(PS)
PRLC
HSPRLC
DHT
HSDST
DCCH on
FACH/RACH
MHC
DTCH on
FACH/RACH
DCCH on
DCH
DTCH
on DCH
CMP/
WCMP
DTI/
MDTI
DTCH (DL)
on HS-DSCH
DTCH (UL)
on A-DCH
TINF
for Iub
RNC
E1-IMA
Iub
E1 E1 E1
STM-1/OC-3
E1-IMA
DTCH (DL) on HS-DSCH
DTCH (UL) on A-DCH
DTCH on FACH/RACH (HS-DSCH to FACH)
DCCH on DCH
DCCH on FACH/RACH
DTCH on DCH (HS-DSCH to DCH)
Fig. 2.2
14
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
NOTE
If E1/J1/T1-IMA (8 lines of 2 Mbit/s each) is used for Iub physical lines, the peak rate of
RAB is restricted to less than 12 Mbit/s on the RLC Layer. If the peak rate of 14 Mbit/s
is required, STM-1/OC-3 should be used for Iub physical lines. See chapter 6 "Transport
Network Layer (TNL) Modifications" for details.
In addition to Fig. 2.1, the protocol stack of each card on the HSDPA traffic route within
the RNC is shown in Fig. 2.3.
CMP/WCMP
HSPRLC
GMUX
PDCP GTP-U
GTP-U GTP-U
HSDST
RLC
AAL2 AAL2-d
ATM
ATM
UDP
UDP
IP
IP
IP
AAL5
AAL5
ATM
ATM
Internal
FP
HS-DSCH
(HSDPA)
FP
Internal
FP
(HSDPA)
AAL2-d AAL2-d
AAL2-d AAL5
ATM
ATM
ATM
RNC
Iub
Fig. 2.3
UDP
MAC-d
ATM
Iu
2.1.3
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
15
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Fuse
Fuse
Fuse
PDM
PDM
FAN
FAN
FAN
FAN
FAN
B-SIGM
C-M2CM
C-DHTM
C-DHTM
GTPM
B-LSM
C-DHTM
B-SIGM
C-M2CM
C-LSM
A-PRM (Basic)
FAN
FAN
C-CMPM
A-PRM (Extended)
E-CCPM
D-CCPM
D-CMPM D-CMPM
A-PRM (Extended)
D-CCPM
A-DTIM
B-LSF
C-TRKF
A-PRF
D-LSF
H-TRKF
FAN
E-CCPM
FAN
B-MHM
cRNC/eRNC
WLSC
FAN
C-GTPM
B-PRM
eRNC
CMUX/CMUXE
Modified Firmware
Fig. 2.4
B-MHM
HSDST
HSPRLC
New Hardware
16
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
PDM
PDM
PDM
FAN
FAN
FAN
WCMP
B-MHM
C-DHTM
B-MHM
C-DHTM
SIGM
M2CM
A-HUBM
C-LSM
FAN
FAN
E-CCPM
C-GTPM
FAN
B-PRM
D-CCPM
A-DTIM
D-LSF
H-TRKF
B-PRM
C-PRM
H-TRKF
PDM
PDM
PDM
FAN
FAN
FAN
WCMP
B-MHM
C-DHTM
B-MHM
SIGM
M2CM
A-HUBM
C-DHTM
C-LSM
FAN
FAN
E-CCPM
C-GTPM
FAN
B-PRM
D-CCPM
A-DTIM
D-LSF
H-TRKF
H-TRKF
Fig. 2.5
HSPRLC
Frame layout of RNC (example) with new HW for update and new delivery
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
17
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Fig. 2.6
18
blank #24
blank #25
blank #26
blank #27
WCMP #28
WCMP #29
WCMP #30
WCMP #31
TINF #08
TINF #09
TINF #10
TINF #11
TINF #12
TINF #13
blank #14
blank #15
WCMP #23
TINF #07
CLKD #1
WCMP #22
TINF #06
CLKD #0
#0
CLKD
blank #21
TINF #05
LSW #1
blank #20
TINF #04
WLSC
LSW #0
HSDST #19
blank #03
WLSC #1
HSDST #18
TINF #02
WLSC #0
blank #16
blank #17
TINF #01
HUBIU #1
TINF #00
HUBIU #0
025 035 045 055 065 075 085 095 105 115 125 135 145 155 165 175 185 195 205 215 225 235 245 255
HSDST
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
CMUXE #1
Reinforcing Plate
CMUXE #0
Blank
Blank
Blank
Blank
Blank
Blank
HSPRLC 1
HSPRLC 0
C1HWM #1
C1HWM #0
HUBIU #1
HUBIU #0
Blank
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
A-PRM (Extended)
Blank
Blank
Blank
Blank
Blank
Blank
HSPRLC 1
HSPRLC 0
C1HWM 01
C1HWM 00
C-PRM
B-PRM
CMUX/CMUXE
Fig. 2.7
CMUX #1
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
CMUX #0
Blank
Blank
Blank
Blank
HSPRLC 1
HSPRLC 0
HUBIU 1
HUBIU 0
C1HWM 01
C1HWM 00
CMUX #1
CMUX #0
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
HSPRLC
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
19
Support of HSDPA
FD012249 - UMR5.0
2.1.3.1
Feature Description
Radio Subsystem
Value
Remarks
Throughput
160 Mbit/s/card
Peak rate
14 Mbit/s/ch
RLC Layer
Maximum number of
channels
4000 ch/card
Redundancy
Single(0/1)
Size
294x324 mm (HxW),
1 slot
Target Power
consumption
30 W
Tab. 2.1
RNC SW compatibility
The HSDST card is not backward-compatible, RNC SW release UMR5.0 is mandatory.
Mounting and limitations
HSDST cards are mounted in the B/C-LSM module (see Fig. 2.6).
The following limitations must be considered:
The four leftmost slots in the lower row in B/C-LSM are reserved for TINF cards.
The HSDST cannot be mounted in these slots.
Dual mode operation is not supported for UMR5.0.
20
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
2.1.3.2
Support of HSDPA
FD012249 - UMR5.0
Value
Remark
Throughput
20 Mbit/s/card
Peak rate
14 Mbit/s/ch
RLC Layer
Maximum number of
channels
2016 ch/card
Redundancy
Single
Size
294x324 mm (HxW),
2 slots
50 W
Tab. 2.2
RNC SW compatibility
The HSPRLC card is not backward compatible. RNC SW release UMR5.0 is mandatory.
Mounting and limitations
HSPRLC cards are mounted in the A-PRM, B-PRM, and C-PRM module (see Fig. 2.7).
The following limitations must be considered:
HSPRLC and PRLC can not be colocated in the PRM module.
HSPRLC cards can be mounted in the locations shown in Fig. 2.7, using the PRLC
slots. It is, however, not advisable to fully populate a PRM with HSPRLC cards, as
their combined throughput will exceed the capacity of the CMUX/CMUXE (approximately 120 Mbit/s in RLC Layer).
2.1.3.3
2.1.3.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
21
Support of HSDPA
FD012249 - UMR5.0
2.1.4
Feature Description
Radio Subsystem
HSDST Functionality
The HSDST card only deals with HSDPA traffic. Unlike with the DHT card, Diversity
Handover functionality is not provided as it is not specified in HSDPA. The HSDST card
provides the functions listed below:
U-Plane protocol handling with regard to:
MAC-d
HS-DSCH Frame Protocol
Internal FP (HSDPA)
Traffic monitoring:
Monitoring the number of transmitting MAC-d PDUs
2.1.4.1
MAC-d
The MAC-d protocol provides the following functions:
Data transfer
Mapping between logical channels and transport channels
The MAC-d PDU is generated from the RLC-PDU carried by the Internal FP (HSDPA)
protocol from the HSPRLC card. When MAC-d multiplexing is performed, the C/T field
is then added. However, MAC-d multiplexing (C/T multiplexing) is not supported.
2.1.4.2
2.1.4.3
22
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
IE
Value
Comment
Header CRC
0..127
Frame Type
0 = data frame
CmCH-PI
0..15
MAC-d PDU
Length
13
336, 656
[bits]
NumOfPDU
1..83
16
Spare Bit
Always set to 0.
Padding
Payload CRC
16
0..65535
Tab. 2.3
2.1.4.4
Field
length
[bit]
Field length
[bit]
Value
Spare Bit
Don't care
CmCH-PI
0..15
Maximum MAC-d
PDU Length
13
0..5000
[bits]
HS-DSCH Credits
11
0..2047
HS-DSCH Interval
0..255
[10ms]
Tab. 2.4
Comment
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
23
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
IE
Field length
[bit]
Tab. 2.4
Value
Comment
Don't care
Value
Spare Bit
Don't care
CmCH-PI
0..15
16
0..65535
[octets]
Tab. 2.5
2.1.4.5
Field length
[bit]
Comment
2.1.4.6
Internal FP (HSDPA)
The Internal FP (HSDPA) is the particular frame protocol inside the RNC for HSDPA
which transmits RLC PDUs between the HSDST and the HSPRLC. In this FP, flow control is performed between the HSDST and the HSPRLC, and this FP complies with the
HS-DSCH FP flow control.
24
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
2.1.5
Support of HSDPA
FD012249 - UMR5.0
HSPRLC Functionality
The new HSPRLC card has the same functionality as a PRLC except that it provides a
higher throughput and supports the internal FP for handling HSDPA traffic. This means
that the HSPRLC is basically able to support both Rel 99 traffic and HSDPA traffic
whereas the PRLC cannot support HSDPA traffic.
The HSPRLC has the following functions:
U-Plane protocol handling:
At the Iu interface: IP, UDP, GTP-U
At the Iub interface: PDCP, RLC, Internal FP, Internal FP (HSDPA)
Traffic Monitoring
The information is used for Charging etc.
QoS control
Performs marking of the DSCP (differentiated services code point) to the TOS
(type of service) field of the IP header of the data traffic in UL
2.1.5.1
IP/UDP/GTP-U
Refer to the Iu interface specification 3GPP TS25.414 for the function of the
IP/UDP/GTP-U in conjunction with the Iu interface.
2.1.5.2
2.1.5.3
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
25
Support of HSDPA
FD012249 - UMR5.0
2.1.5.4
Feature Description
Radio Subsystem
2.2
Functional Split
HSDST
Terminates HS-DSCH FP, MAC-d, and Internal FP (HSDPA).
Performs traffic monitoring and flow control between RNC and Node B.
HSPRLC
Terminates IP, UDP, GTP-U on the Iu side and PDCP, RLC, Internal FP, Internal
FP (HSDPA) on the Iub side. Performs traffic monitoring and QoS control.
2.3
Man-Machine Interface
Not applicable (see chapter 5.3).
2.4
26
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
NB-44x
Variant
TRX-LPA
TRX-LPA
Cell
HSDPA
configuration configuration
Power/
cell [W]
1/0/0
1/0/0
20
1/1/0
1/1/0
20
1/1/1
1/1/1
20
1/0/0
1/0/0
20
1/1/0
1/1/0
20
1/1/1
1/1/1
20
2/0/04
1/0/0
20
1/1/0
20
2/2/24
1/1/1
20
1/0/0
1/0/0
20
1/1/0
1/1/0
20
1/1/1
1/1/1
20
1/0/0
1/0/0
40
1/1/0
1/1/0
40
2/2/0
NB-860
DRIC-CAT20
DRIC-CAT40
1/1/1
Tab. 3.1
TRX
LPA
CAT1
RRH2
1/1/1
40
1/0/0
20
2/2/04
1/1/0
20
2/2/24
1/1/1
20
1/0/0
1/0/0
12.5
1/1/0
1/1/0
12.5
1/1/1
1/1/1
12.5
2/0/04
1/0/0
6.25
2/2/04
1/1/0
6.25
2/2/24
1/1/1
6.25
2/0/0
DRIC-RRH
Number of RF modules
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
27
Support of HSDPA
FD012249 - UMR5.0
Node B
type(s)
NB-88x
Variant
DRIC-CAT20
Feature Description
Radio Subsystem
Cell
HSDPA
configuration configuration
Power/
cell [W]
1/0/0
1/0/0
20
1/1/0
1/1/0
20
1/1/1
1/0/0
20
2/2/04
1/1/0
20
1/1/1
20
1/0/0
1/0/0
40
1/1/0
1/1/0
40
RRH2
1/1/1
40
1/0/0
20
2/2/04
1/1/0
20
1/1/1
20
2/0/04
1/0/0
40
1/1/0
40
2/2/24
1/1/1
40
1/0/0
1/0/0
12.5
1/1/0
1/1/0
12.5
1/1/1
1/1/1
12.5
2/0/04
1/0/0
6.25
1/1/0
6.25
2/2/24
1/1/1
6.25
1/1/1/1/0/0
1/1/1/1/0/0
12.5
1/0/0, 1/0/0
20, 12.5
1/1/0, 1/1/0
1/1/0, 1/1/0
20, 12.5
1/1/1, 1/1/1
1/1/1, 1/1/1
20, 12.5
1/0/0, 1/0/0
1/0/0, 1/0/0
40, 12.5
1/1/0, 1/1/0
1/1/0, 1/1/0
40, 12.5
1/1/1, 1/1/1
1/1/1, 1/1/1
40, 12.5
2/0/04, 2/0/04
2/0/0, 2/0/0
20, 6.25
15/26
with Booster
1/0/0
1/0/0
10
without Booster
1/0/0
1/0/0
0.5
2/0/0
2/2/2
2/2/0
DRIC-RRH
2/2/0
28
CAT1
20
1/1/1
Tab. 3.1
LPA
1/1/1
2/2/2
NB-341
TRX
2/0/0
DRIC-CAT40
Number of RF modules
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Node B
type(s)
RS-880
Variant
DRIC-RRH
Support of HSDPA
FD012249 - UMR5.0
Cell
HSDPA
configuration configuration
Power/
cell [W]
1/0/0
1/0/0
12.5
1/1/0
1/1/0
12.5
1/1/1
Tab. 3.1
LPA
CAT1
RRH2
1/1/1
12.5
1/0/0
6.25
2/2/04
1/1/0
6.25
1/1/1
6.25
1/1/1/1/0/0
1/1/1/1/0/0
12.5
1/0/0
1/0/0
12.5
1/1/0
1/1/0
12.5
1/1/1
1/1/1
12.5
2/0/04
1/0/0
6.25
2/2/2
DRIC-RRH
TRX
2/0/0
RS-381
Number of RF modules
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
29
Support of HSDPA
FD012249 - UMR5.0
Node B
type(s)
NB-580
Tab. 3.1
Feature Description
Radio Subsystem
Variant
DRIC-CAT
Cell
HSDPA
configuration configuration
Power/
cell [W]
Number of RF modules
0/0/0 : 1/0/07
0/0/0 : 1/0/07
0 : 407
0 : 18
0/0/0 : 1/1/07
0/0/0 : 1/1/07
0 : 407
0 : 18
0/0/0 : 1/1/17
0/0/0 : 1/1/17
0 : 407
0 : 18
0/0/0 : 2/0/07
0/0/0 : 2/0/07
0 : 207
0 : 18
0/0/0 : 2/2/07
0/0/0 : 2/2/07
0 : 207
0 : 28
0/0/0 : 2/2/27
0/0/0 : 2/2/27
0 : 207
0 : 38
0/0/0 : 2/0/07
0/0/0 : 2/0/07
0 : 407
0 : 28
0/0/0 : 2/2/07
0/0/0 : 2/2/07
0 : 407
0 : 48
0/0/0 : 2/2/27
0/0/0 : 2/2/27
0 : 407
0 : 68
1/0/0 : 0/0/07
1/0/0 : 0/0/07
40 : 07
1 : 08
1/0/0 : 1/0/07
1/0/0 : 1/0/07
40 : 407
1 : 18
1/1/0 : 0/0/07
1/1/0 : 0/0/07
40 : 07
2 : 08
1/1/0 : 1/1/07
1/1/0 : 1/1/07
40 : 407
2 : 28
1/1/1 : 0/0/07
1/1/1 : 0/0/07
40 : 07
3 : 08
1/1/1 : 1/1/17
1/1/1 : 1/1/17
40 : 407
3 : 38
2/0/0 : 0/0/07
2/0/0 : 0/0/07
20 : 07
1 : 08
2/0/0 : 2/0/07
2/0/0 : 2/0/07
20 : 207
1 : 18
2/2/0 : 0/0/07
2/2/0 : 0/0/07
20 : 07
2 : 08
2/2/2 : 0/0/07
2/2/2 : 0/0/07
20 : 07
3 : 08
2/0/0 : 0/0/07
2/0/0 : 0/0/07
40 : 07
2 : 08
2/0/0 : 2/0/07
2/0/0 : 2/0/07
40 : 407
2 : 28
2/2/0 : 0/0/07
2/2/0 : 0/0/07
40 : 07
4 : 08
2/2/2 : 0/0/07
2/2/2 : 0/0/07
40 : 407
6 : 08
TRX
CAT1
LPA
RRH2
30
If the NB-420 and NB-44x are upgraded to DRIC-CAT configuration, the same configurations can be applied as for the NB-860 and NB-88x, respectively.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Only one cell per sector supports HSDPA because UMR5.0 supports HSDPA only on
a single carrier frequency. Chosing the HSDPA cell therefore depends on the choice
in the Node Bs other sectors.
The value in front of the colon (:) applies for cells in the FDD UMTS1900 MHz band
whereas the value behind the colon applies for cells in the FDD UMTS850 MHz band.
The value in front of the colon (:) applies for CAT40 for FDD UMTS1900 MHz whereas the value behind the colon applies for CAT40 for FDD UMTS850 MHz.
The cells which provide HSDPA service are distributed in a round-robin manner on the
available HSDPA-capable CHCs, thus resulting in an even distribution of the cells on the
appropriate CHCs. Tab. 3.2 provides an example of the dependencies between the
Cell configuration of HSDPA cells
Number of available HSDPA-capable CHCs
Cell mode operation of each HSDPA-capable CHC in the Node B, resulting from the
round-robin distribution, where
single
Indicates that the CHC operates in HSDPA single-cell mode, i.e. one HSDPA-capable CHC in HSDPA mode serves exactly one HSDPA cell
multi
Indicates that the CHC operates in HSDPA multi-cell mode, i.e. one HSDPA-capable CHC in HSDPA mode serves two or three HSDPA cells
off
Indicates that the CHC does not operate in HSDPA mode (Rel 99 traffic only)
Cell configuration
1 HSDPA-capable CHC
installed
2 HSDPA-capable CHCs
installed
3 HSDPA-capable CHCs
installed
1/0/0
single
single/off
single/off/off
1/1/1
multi
multi/single
single/single/single
Tab. 3.2
Dependencies between the number of HSDPA-capable CHCs and the cell configuration applied
3.1
Functional Description
With UMR5.0 supporting HSDPA in the Node B, changes have been made to the
Node Bs hardware (HW) and software (SW) architecture. The following functional entities have been extended or newly created in the Node B to support HSDPA:
Flow control
The flow control mechanism dynamically assigns capacity to the HS-DSCH on the
Iub interface. The relevant capacity is allocated in accordance with the available
buffer space for priority queues and the current air interface capacity, for example.
HS-DSCH frame protocol (FP)
The HS-DSCH FP is responsible for
Extracting HS-DSCH capacity requests and forwarding them to the flow control
unit
Signaling flow control credits to the SRNC (serving RNC)
Controlling incoming user traffic. In other words, the Node B can potentially discard incoming user traffic if the RNC exceeds the assigned credit limits.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
31
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Extracting the incoming user data and putting the data into the priority queues
Scheduler
In UMR5.0, the scheduler for HSDPA data traffic is implemented in the Node B rather than in the RNC where the scheduler for Rel 99 traffic is situated. This implementation allows for lower latency.
In general, this functional entity of the Node B is responsible for
Selecting the UEs to be served in a specific time transmission interval (TTI)
Assigning the HS-PDSCH resources to UEs
Selecting the appropriate priority queues which are to be served
Managing the HSDPA air interface resources
Selecting HARQ (hybrid automatic repeat request) processes, redundancy versions, modulation schemes, transport block sizes, and the HSDPA transmit signal
power
Priority queues
The Node Bs priority queues are buffers for the HSDPA user traffic data. By means
of the priority queues, the total amount of pending user data in the priority queues is
visible to the flow control unit and the scheduler.
HS-SCCH symbol level processing unit
This functional entity performs signal processing for the HS-SCCH.
HS-PDSCH symbol level processing unit
This functional entity performs signal processing for the HS-PDSCHs.
HARQ control
On the one hand, the HARQ control entity processes the connected UEs HARQ status indications. On the other hand, this functional unit manages the states of these
UEs HARQ processes.
Transport block assembly
The transport block assembly unit prepares each transport block for further physical
layer processing. Preparing the transport blocks is done upon request of the scheduler. Among other things, this preparation must take into account whether the scheduler demands either initial transmission or retransmission.
Furthermore, the transport block assembly is responsible for managing both the priority queues and the retransmission buffer. This functionality, however, is implementation-dependent.
Another functionality the transport block assembly provides is cleaning up the retransmission buffer. The buffer is cleaned up if the protocol data units (PDUs) are
either successfully transmitted or dropped due to reaching the relevant time-outs.
Channel quality estimation (CQE)
The CQE combines channel quality information (CQI) and downlink (DL) transmit
power commands.
These functional entities impact on the Node Bs core controller (CC), channel coding
card (CHC), and transceiver (TRX) or DUAMCO (duplexer amplifier multicoupler), or
digital radio interface card (DRIC). The majority of the above-mentioned functional units,
however, is located in the CHC. Therefore, a new HSDPA-capable CHC must be installed in the Node B if HSDPA is to be supported. Thus, one of the following two possible alternatives must be chosen for HSDPA support:
Firmware (FW) upgrade of the CHC96 (channel coding card-96)
Installation of the newly developed hs-CHC (high speed channel coding card)
32
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
3.1.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
33
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
In UMR5.0, the HSDPA-capable CHCs support UEs of the classes 1 to 6, 11, and 12.
Additionally, HSDPA calls for UEs of categories 7, 8, 9, and 10 are set up on the HSDSCH with a performance equal to or better than that of UE category 6. For details
about UE classes, please refer to "UE Support of HSDPA" on page 46.
In this context, Tab. 3.3 lists the maximum number of HSDPA users possible with the
HSDPA-capable CHCs when a specific uplink radio access bearer is applied.
UL RAB rate
AMREQ
8 kbit/s
96
32 kbit/s
72
64 kbit/s
36
128 kbit/s
18
384 kbit/s
16
Tab. 3.3
3.1.1.1
CHC96
The existing CHC96 has already been HW-prepared for HSDPA in product releases
prior to UMR5.0. Its SW, however, is updated in order to handle HSDPA traffic in an appropriate way.
The CC OAM SW configures the CHC96 to operate in non-HSDPA mode or in HSDPA
mode. In non-HSDPA mode, no HSDPA-specific channels and functions are supported.
When operating in this mode, the CHC96s maximum performance is equal to
96 channel elements (CEs) and 144 adaptive multi-rate (AMR) equivalents (AMREQs).
These characteristics are the same as in the product release prior to UMR5.0.
When working in HSDPA mode, the CHC96 supports both normal channels (3GPP
Rel 99) and HSDPA-specific channels and functions simultaneously. Compared to the
non-HSDPA mode, no restrictions apply with regard to the maximum number of channel
elements and AMR equivalents.
The applicable baseband (BB) resources are communicated from the CHC to the CC
using the defined BB resource management procedures in each mode of operation.
3.1.1.2
hs-CHC
The newly developed hs-CHC offers the same functionality as a Rel 99-compliant CHC.
Furthermore, functionality for the support of HSDPA is provided.
Unlike the CHC96, the hs-CHC operates in only one mode supporting the processing of
both DCH bearers (Rel 99) and HSDPA. In other words, the hs-CHC simultaneously
supports HSDPA-specific channels and functions as well as normal channels. The
hs-CHCs maximum performance is equal to 96 CEs and an AMREQ of 144.
34
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
3.1.2
Support of HSDPA
FD012249 - UMR5.0
3.1.3
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
35
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
36
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
3.1.4
3.1.4.1
3.1.4.2
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
37
Support of HSDPA
FD012249 - UMR5.0
3.1.5
Feature Description
Radio Subsystem
3.1.5.1
Handling of Parameters
The MAC-hs handles HSDPA-related IEs received from the RNC or sent to the RNC via
NBAP signaling. Furthermore, the MAC-hs supervises the maximum number of HARQ
retransmissions which is a vendor-settable OAM parameter for each radio cell. Adjusting this parameter may become necessary in difficult radio environments. In an indoor
environment, for example, a low value for this parameter is beneficial, whereas in an outdoor scenario a high value is favorable in order to serve UEs at the border of the relevant
macro cell.
Furthermore, the MAC-hs is responsible for OAM with regard to the HSDPA scheduler
type. The operator can select either a Maximum CIR (carrier- to interference-power ratio) or a Proportional Fair scheduler. For more details about the Proportional Fair
scheduler, refer to the FD012251 - Proportional Fair Scheduler for HSDPA. For information about the scheduler-related parameter in the Node Bs software, refer to "Impacts
on the LMT-Node B" on page 143.
3.1.5.2
Flow Control
The Node Bs flow control protects the priority queues from an overflow situation and
supplies the Node B with user traffic data in such a way that the throughput at the Uu
interface is maximized under the given QoS constraints.
Further details about the flow control mechanism are described in the section "Flow
Control" on page 147.
3.1.5.3
Transmission Control
The transmission control function manages the HSDPA Uu interface resources in terms
of transmission time, channelization codes, and transmit power. With regard to the
transmit power for HS-PDSCHs, on the other hand, all HS-PDSCHs of the same UE
have to be transmitted with the same power. When assigning the transmit power to the
HS-PDSCHs, the transmission control functional entity must make sure that it does not
exceed either the maximum HSDPA transmit power configured via NBAP signaling or
the transmit power available for HSDPA. Furthermore, if the scheduler decides to apply
38
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
the 16QAM modulation for at least one UE, it reduces the HS-PDSCH transmit power
by a certain amount.
The transmission control functional entity includes the scheduler functionality where, in
UMR5.0, either a Maximum CIR (carrier- to interference-power ratio) or a Proportional
Fair scheduler is used.
The Maximum CIR scheduler, on the one hand, works according to the following principle: at each time transmission interval (TTI), it selects the UE(s) for transmission in decreasing order of their current CIR. In other words, the UE with the best CIR is served
first, UEs with lower CIRs are currently blocked and served later. Thus, the Maximum
CIR scheduler ensures high peak data rates as well as a maximum Node B cell throughput. Each UE reports its current CIR contained in the channel quality information (CQI)
at every TTI via the HS-DPCCH. Refer to "Channel Quality Estimation" on page 40.
The Proportional Fair scheduler, on the other hand, provides a fairer distribution of transmission bandwidth among the HSDPA users within a radio cell. Thus, the Proportional
Fair scheduler assures that all HSDPA users within this cell will benefit from the availability of HSDPA. For more details about this scheduler, refer to the FD012251 - Proportional Fair Scheduler for HSDPA.
In addition to the above features, the transmission control functional entity is able to set
the following parameters for each scheduled UE:
Channelization code for HS-SCCH
Channelization codes for HS-PDSCH
Transport block size
In the event of a retransmission, the transport block size must be equal to that of the
initial transmission.
Modulation scheme
When selecting the modulation scheme, the transmission control function must take
into account restrictions arising from UE capabilities and those which are implied by
the optional feature handling.
3.1.5.4
HARQ
The hybrid automatic repeat request (HARQ) provides functionality for fast and efficient
retransmission techniques and error detection. Thus, the UE calculates the cyclic redundancy check (CRC) of the incoming packet from the Node B. If this CRC is the same as
the one contained in the packet, an ACK (acknowledged) signal is sent to the Node B.
Otherwise, NACK (not ACK) is sent, thus requesting for a retransmission of the erroneous packet.
The HARQ functionality is based on an N-channel stop and wait automatic repeat request (ARQ). The HARQ supports both chase combining and incremental redundancy.
The number of retransmission attempts is limited to a maximum value given by the corresponding OAM parameter (see subsection Handling of Parameters, above).
Applying stop and wait ARQ, the transmitter persists on the transmission of the current
data block until the UE has successfully received this block. To avoid idle times,
N parallel processes (channels) are set up, thus allowing different processes transmit
in separate TTIs.
The basic idea of chase combining is as follows: upon reception of an erroneous packet,
a NACK signal is sent. The packet, however, is not deleted as is done by normal ARQ
but stored. If the retransmitted packet is erroneous, too, the previous and the current
packet are combined, thus attempting to recover from the errors. Eventually, either the
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
39
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
packet is received without an error, or the UE recovers from the error by means of chase
combining, or the maximum number of retransmissions is exceeded. In the latter case,
error recovery is left to higher-protocol levels.
As regards the incremental redundancy, the transmitter adds previously not transmitted
redundant information to the packet if the receiver detected an error in this packet in advance. Adding further redundant information increases the chances of error-free transmissions or retransmissions with enough errors removed to allow error correction by
means of chase combining with previous packets.
3.1.5.5
3.1.5.6
3.1.6
3.1.6.1
40
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
The scrambling code and the channelization codes for the spreader units are configured
when HSDPA is set up in a UTRAN cell. In other words, their configuration is a direct
consequence of an NBAP: Physical Shared Channel Reconfiguration procedure.
The following list provides information about the channel configuration and thus also
about the signal processing in DL direction:
HS-SCCH
The HS-SCCH is the DL control channel for HSDPA. The information carried on this
channel enables UEs to receive the HS-PDSCH.
In HSDPA mode, the HSDPA-capable CHC processes up to 4 HS-SCCHs per cell,
up to 3 HSDPA cells being supported.
One spreader unit is provided per CHC. The spreading factor (SF) is 128.
HS-DSCH / HS-PDSCH
The HS-PDSCH is the DL data channel carrying the user data.
The HS-DSCHs spreading factor is 16.
The HSDPA-capable CHC supports both HS-PDSCH slot format 0 and slot
format 1, indicating QPSK and 16QAM, respectively.
In HSDPA mode of operation, the HSDPA-capable CHC is able to process one up
to 15 HS-PDSCHs per HSDPA cell. The maximum total number of HS-PDSCH
channelization codes supported is 15. Depending on the number of HSDPA cells
that are set up, this maximum number of codes can be split between these, up to
three, cells. However, these codes must be distributed symmetrically among all
HSDPA cells which the Node B serves. In other words, all HSDPA cells which are
subordinated to the same Node B are assigned the same number of HS-PDSCH
channelization codes.
Furthermore, if the 16QAM modulation scheme is applied, the HSDPA-capable
CHC can process a total of up to 15 HS-PDSCH channelization codes for all HSDPA
cells. Otherwise, if only QPSK modulation is applied, the CHC is capable of processing 30 HSDPA channelization codes in total and up to 15 codes per cell. Tab. 3.4
illustrates this:
Cell mode
16QAM/QPSK modulation
QPSK-only modulation
1-cell mode
15
15
2-cell mode
15
3-cell mode
10
Tab. 3.4
DPCH
The DPCH (dedicated physical channel) is the corresponding physical channel to
the DCH.
In addition to the HSDPA processing specified above, DPCH processing is supported simultaneously. Independent of whether the HSDPA-capable CHC (CHC96 with
SW upgrade or hs-CHC) serves a cell in which HSDPA is enabled or not, the DPCH
symbol rate processing capacity guarantees simultaneous processing of up to
144 AMREQs on the DL.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
41
Support of HSDPA
FD012249 - UMR5.0
3.1.6.2
Feature Description
Radio Subsystem
3.1.7
42
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
3.2
Support of HSDPA
FD012249 - UMR5.0
Functional Split
In UMR5.0, the packet scheduler for HSDPA traffic is implemented in the Node B rather
than in the RNC where the scheduler for Rel 99 traffic is situated. Furthermore, the HSDSCH terminated in Node Bs MAC-hs layer is the only UTRAN transport channel not
terminated in the RNC. Using the HS-DSCH enables several users to be time-multiplexed, thus making the resources available to other users during silent periods.
The modulator on the TRX or DRIC cards takes care of the new modulation scheme.
Additionally, the Node Bs power amplifiers provide a higher linearity for 16QAM.
The main functionalities of HSDPA are concentrated on the Node Bs CHC. One of the
following actions therefore becomes necessary:
SW upgrade of the existing CHC96
Installation of the new hs-CHC
3.2.1
3.2.2
3.2.3
Repeater (REP)
The REP remains unchanged in comparison with the product release prior to UMR5.0.
In other words, the REP module performs data transport between the CHCs and the
TRX or DRIC cards.
3.2.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
43
Support of HSDPA
FD012249 - UMR5.0
3.3
Feature Description
Radio Subsystem
Man-Machine Interface
With regard to operation, administration, and maintenance (OAM) of the Node B, modifications have been applied to the man-machine interface (MMI) for both the new hardware (hs-CHC) and the new software.
As regards the hardware, the front panel of the new hs-CHC serves as a direct manmachine interface for the operator by offering the following:
Front Panel Indicators
Front Panel Connectors
Manual Intervention
For details about changes in the Node Bs software, refer to "Impacts on the LMTNode B" on page 143.
3.3.1
3.3.2
3.3.3
Manual Intervention
A mechanism is provided for resetting and locking the hs-CHC by way of the front panel.
3.4
44
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4 HSDPA Mobility
4.1
Functional Description
The High Speed Downlink Shared Channel (HS-DSCH) is a common transport channel
that is shared by several UEs in the same cell. The MAC-hs functionality of the Node B
performs scheduling of UEs on a per cell basis. Therefore, the UE receives the
HS-DSCH of one cell and can receive DCHs of multiple cells. The cell where the
HS-DSCH is currently established is called the serving HS-DSCH cell. The quality of the
serving HS-DSCH cell constantly varies due to the mobility of the UE. If the quality is
degraded or the serving HS-DSCH cell is deleted, the SRNC needs to move the serving
function to another cell where the quality is good. Furthermore, the UE may enter or
leave the area where HSDPA is supported. In this case, the SRNC performs channeltype switching from DCH to HS-DSCH or from HS-DSCH to DCH.
The following UE mobility scenarios are supported within UMR5.0:
HS-DSCH establishment (when the UE is in Cell_DCH or Cell_FACH state)
Intrafrequency, intra-SRNC, intra-Node B handover
Interfrequency, intra-SRNC, intra-Node B handover (at channel-type-switching
from FACH to HS-DSCH)
Inward mobility (DCH -> HS-DSCH)
Intrafrequency, intra-RNC, inter-Node B handover
Change of the serving HS-DSCH cell
Intrafrequency, intra-RNC, intra-Node B handover
Intrafrequency, intra-RNC, inter-Node B handover
Outward mobility (HS-DSCH -> DCH)
Intrafrequency, intra-SRNC, inter-Node B handover
Intrafrequency, inter-RNC handover
Intrafrequency, inter-RNC (SRNC) relocation
Interfrequency/Intersystem
4.1.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
45
Support of HSDPA
FD012249 - UMR5.0
4.1.1.1
Feature Description
Radio Subsystem
UE Support of HSDPA
The SRNC uses the UE capabilities to determine whether or not the UE supports
HSDPA and if so, which HS-DSCH category it belongs to.
The SRNC determines the UE to be HSDPA capable if the following conditions are both
true:
The UE Radio Access Capability IE indicates that the UE is release 5 and that it
supports HSDPA.
The HSDPA feature is enabled.
Otherwise, the SRNC considers the UE as non-HSDPA capable.
The SRNC determines this information during RRC connection establishment, interRAT handover to UTRAN, or SRNS relocation. It may be necessary to obtain the
information via UE capability enquiry. If the UE is considered capable of HSDPA, the UE
provides the HS-DSCH category to which it belongs.
3GPP TS 25.306 UE Radio Access Capabilities defines 12 HS-DSCH categories.
UMR5.0 supports UE categories 1-6, 11, and 12. Tab. 4.1 shows the information defined for all HS-DSCH categories. Additionally, HSDPA calls for UEs of categories 7, 8,
9, and 10 are set up on the HS-DSCH with a performance equal to or better than that of
UE category 6.
Parameter
Usage
Tab. 4.1
46
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.1.2
Support of HSDPA
FD012249 - UMR5.0
4.1.1.3
Transport channels
supported
Notes
DCH/CCH
DCH
DCCH + PS BE
DCH
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
47
Support of HSDPA
FD012249 - UMR5.0
4.1.1.4
Feature Description
Radio Subsystem
48
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Traffic class
Interactive
Background
Tab. 4.3
4.1.1.5
1 (highest)
15
...
...
15 (lowest)
N/A
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
49
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
M1
RAB
Establishment
RAB
RRC
Connection
Establishment
RB Type
RAB Release
207, 209
212-219
208, 210
RAB
Combination +
UE Capability
Class
AAL2/5
RLC/RB Info
M5
291, 292
Combination
Allowed/
Not Allowed
Max UE Supported
Rate for PS BE
M2
227, 228
DCH Type
205, 206
TFS
M6
New
optional
step for
HSDPA
M3
278, 279
TFSC
DCH
Combination + Rate
M4
220, 221
DPCH Type
Fig. 4.1
202, 203
Physical CH Par
50
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
DL
UL
DCCH
DTCH
DCH
DCH
HS-DSCH
DPCH
Fig. 4.2
DCCH
DTCH
DCH
DCH
DPCH
If HS-DSCH is required, the RAB combination allows HSDPA usage, and a suitable cell
is available, call processing (CP) provides the HS-DSCH Required indicator and the
UE HS-DSCH Physical Layer Category upon request for:
PS BE RAB establishment
Channel-type switching (FACH to DCH + HS-DSCH)
Channel-type switching (DCH to DCH + HS-DSCH)
The SRNC retries the algorithm without the HS-DSCH required indicator if the
UE HS-DSCH Physical Layer category is not part of the radio bearer translation tables.
In this case, the UE connection will be established on DCH instead of HS-DSCH.
The radio bearer translation mechanism calculates the initial, maximum, and minimum
rates for UL and DL DCH during step M2 if HS-DSCH is requested by call processing.
The minimum rate is the rate supported by the RNC which is closest to the UL: 0 kbit/s,
DL: 0 kbit/s rate combination.
Initial rate and maximum rate are selected within step M2 in three steps:
Step 1
The RNC creates a list of permitted rates from the list of RNC supported UL/DL PS
BE DCH rates in the service combination such that all rates are equal to or less than
the maximum rate supported by the UE. A table of permitted UL/DL DCH data rate
combinations exists for each RAB combination which uses HSDPA.
The maximum UE supported rate for the UL is calculated in the same way as for
non-HS-DSCH configurations. The maximum UE-supported rate for the DL,
however, is not taken into account since the maximum DCH rate that is used in the
DL is set to 0 kbit/s. Therefore, the DL Capability with Simultaneous HS-DSCH
Configuration IE from the UE Radio Access Capability IE is ignored.
Step 2
The RNC filters the list of permitted rates from step 1 such that all rates are equal to
or less than the maximum bit rate requested from the core network. If HSDPA is
used, this check is performed for the set of UL rates only. In other words, the UL
DCH rates from step 1 are compared with the UL Maximum Bit Rate value received
in the RAB parameters.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
51
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Step 3
The RNC selects from the list of permitted rates the initial and maximum rates that
can be used during bit rate adaptation with the new service combination:
Initial Rate:
64 kbit/s is the system data value of the initial UL rate if HS-DSCH is used on the
DL. The RNC therefore restricts the permitted rates such that all rates are equal
to or less than 64 kbit/s. The governing procedure fails if no rate is left in the list
of permitted rates. The RNC selects the rate which is closest to the maximum bit
rate requested by the core network if more than one permitted rate remains in the
list.
Maximum rate:
If more than one permitted rate remains in the list after step 2, the RNC selects
the rate which is closest to the maximum bit rate requested by the core network.
The closest rate is defined as the UL/DL permitted rate with the smallest distance:
di =
( x1 xi ) + ( y1 yi )
where (x1, y1) is the coordinate for the maximum bit rate requested by the core network
and (yi, yi) is the coordinate of the permitted rates. The DL rate is set to 0 kbit/s if HSDPA
is used. Therefore, two data rate combinations cannot be equally close to the maximum
bit rate requested by the core network.
Bit rate adaptation uses the pool of rates that were output from step 2 of M2. Only the
UL DCH rate increases or decreases according to traffic activity if HSDPA is used. The
DL DCH rate is fixed at 0 kbit/s.
The new step M6 is introduced to obtain the HS-DSCH parameters. If the radio bearer
translation receives the HS-DSCH Required indicator and the HS-DSCH UE
category, a new table is used to obtain HS-DSCH information from the UE HSDPA
category.
The HS-DSCH-related information consists of the following:
MAC-hs window size
T1
AAL2 parameters (MAC-d flow)
If DCH is used, the RLC Tx/Rx window sizes of AM RLC RABs are based on the radio
bearer type which is determined from the RAB parameters. The radio bearer type is
limited to 384 kbit/s in the DL (largest DCH rate). If the core network signals maximum
bit rates above 384 kbit/s, they are assumed to be equal to 384 kbit/s, which results in
window sizes tuned for 384 kbit/s.
If HSDPA is used, the RLC window sizes are selected according to the available
memory in the UE rather than on the basis of a DL rate parameter supplied by the core
network. The DL rate signaled by the RAB parameters and supported on the air interface
may be much larger than 384 kbit/s. The maximum rate is limited by the UE capability
class. The maximum rate also depends on the RLC window sizes, which in turn depend
on the UEs available memory.
52
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
This method of selecting the window size for an AM RLC RAB is applied if all of the
following conditions are valid:
1. The UE is HSDPA-capable
2. The UE has RAB combinations with only one AM RLC RAB
PS BE
PS BE + CS (any)
PS BE + PS Conversational
The window size is derived from the radio bearer type for all non-HSDPA-capable UEs
and for HSDPA-capable UEs using a RAB combination involving more than one AM
RLC RAB, for example PS BE + PS Streaming.
Tab. 4.4 shows the new system data table for the selection of the RLC window size for
HSDPA-capable UEs with one AM RLC RAB.
UE memory [kbytes]
50
100
150
>150
Tab. 4.4
RLC window sizes for HSDPA-capable UEs with one AM RLC RAB
The UE memory is taken from the Total RLC AM buffer size IE sent in the UE Radio
Access Capabilities in the RRC CONNECTION SETUP COMPLETE message.
Furthermore, the default values of the TX and RX Window Size is changed from 128 to
32 for RLC Type DCCH AM. This reduces UE memory consumption by the SRBs from
12 kbit/s to 3 kbit/s, allowing more memory and hence larger window sizes for the DL
HS-DSCH.
Furthermore, the RNC takes into account the Maximum RLC AM Window Size IE also
sent in the UE Radio Access Capabilities. The RNC assigns the memory size as the
minimum Min (Maximum RLC AM Window Size, RLC Window Size from table).
The UL window also increases with increasing memory with the proposed window sizes
in Tab. 4.4. This is to allow a 384 kbit/s bearer on the UL. If UL bit rate adaptation occurs, the UL window size remains the same. However, a large UL window that is permanently specified reduces the memory available for the DL. If the UE only supplies a small
memory, the DL is prioritized and as a result the UL: 384 kbit/s bearer may not be useful.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
53
Support of HSDPA
FD012249 - UMR5.0
4.1.1.6
Feature Description
Radio Subsystem
DCH_ACTIVE
Cell_DCH
CS RAB setup
or release
Cell_DCH +
HS-DSCH
Mobility in and
out of HSDPA
coverage area
CS RAB setup
CTS triggers
HSDPA cell
unavailable
CTS triggers
HSDPA cell
available
Cell_FACH
CS RAB setup
or release
DCH_INACTIVE
Cell_PCH
Fig. 4.3
54
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.1.7
Support of HSDPA
FD012249 - UMR5.0
4.1.1.8
NBAP/RNSAP name
RRC name
Range
Purpose
Integer (1..4)
Number of repetitions of a
CQI report. Not necessary
when CQI Feedback Cycle
k = 0.
ACK-NACK Repetition
Factor
Integer (1..4)
Number of repetitions of
ACK/NACK reports
Tab. 4.5
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
55
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
NBAP/RNSAP name
RRC name
Range
Purpose
CQI
Integer (0..8)
ACK
Integer (0..8)
NACK
Integer (0..8)
N/A
-32 .. + 31.75 dB
Tab. 4.5
NBAP/RNSAP name
RRC name
Tab. 4.6
Range
-6..13 dB
Purpose
Default Power offset between HSPDSCH and P-CPICH/S-CPICH.
4.1.1.9
The procedures to establish the RAB on DCH are initiated if the condition 1, 2, or 4 is
not true. If condition 3 is not true, see "RAB Setup Procedure from FACH to HS-DSCH"
on page 60.
The first step is the selection of an HS-DSCH RL ID that is the RL ID of the cell where
the HSDPA resources will be established. The cell selection is described in "HSDPA
Mobility Handling" on page 76. Afterward, the radio bearer translation algorithm is
called, see "Impacts on the Radio Bearer Translation" on page 49. This produces the
56
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
MAC-d flow information and the priority queue information for the HS-DSCH
configuration.
The SRNC-based power offset and measurement-related parameters are generated,
see "Power Control and Measurement Feedback Parameters" on page 55. Then the
SRNC initiates the synchronized RL reconfiguration preparation procedure to the
CRNC. This is a local procedure as HS-DSCH via the Iur interface is not supported and
cells in the DRNC are taken into account as non-HSDPA-capable.
The UL part of the PS BE RAB is established on DCH. Therefore, all Node Bs in the
active set are configured with UL DCH information and UL physical channel information.
The DCH Specific Info IE contains a mandatory UL and DL transport format set. When
HS-DSCH is used on the DL, the DL TFS of the DCH associated with the PS BE RAB
is set up and configured to 0 kbit/s using a TFS with one TF. The number of transport
blocks contained is set to zero.
Since the UE is assigned to an HS-DSCH resource belonging to a particular cell within
a particular Node B, only the affected Node B is configured with the HS-DSCH
configuration parameters and the affected cell within that Node B is identified by the
HS-DSCH RL ID.
The admission control is performed in the CRNC, see "HSDPA Admission Control and
Congestion Control" on page 102. If the resources are admitted, the CRNC allocates an
HS-DSCH RNTI such that it is unique for the selected cell, see "Allocation of H-RNTI"
on page 75. Additionally, the CRNC allocates the Measurement Power Offset parameter, see "Power Control and Measurement Feedback Parameters" on page 55. Then
the CRNC initiates the NBAP synchronized RL reconfiguration preparation procedure.
The NBAP: RL RECONFIGURATION PREPARE message contains the following
information:
For all Node Bs:
DCH/DPCH information
For the Node B containing HS-PDSCH RL ID:
MAC-d flow/priority queue configuration
Power offset and measurement feedback information
H-RNTI
HS-PDSCH RL ID
The Node B assigns the codes after receiving the HS-DSCH information. Furthermore,
the Node B configures the MAC-hs entity, HARQ processes, and scheduler with the
received information.
The NBAP: RL RECONFIGURATION READY message contains the following
information:
From all Node Bs:
TNL address info DCH: UL PS DTCH (for ALCAP)
From the Node B containing HS-PDSCH RL ID:
MAC-d flow TNL address info (for ALCAP)
Initial capacity information
The HS-SCCH code information
The HARQ memory partitioning information
The CRNC sends the received information to the colocated SRNC upon reception of the
NBAP RL RECONFIGURATION READY message. The SRNC initiates the ALCAP
transport bearer establishment procedures. The transport bearer for the DCH part
carries the UL DTCH and is established toward all Node Bs/DRNCs in the active set. If
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
57
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
the Transport Bearer Modification Feature flag is set to ON for the DL direction of this
DCH, the link characteristics for connection admission control (CAC) are set to the DCH
rate used, that is 0 kbit/s. Otherwise, they remain configured according to the maximum
rate that this DCH may use. The transport bearer for the MAC-d flow is established
toward the Node B containing the HS-DSCH RL ID.
The NBAP: RL reconfiguration commit procedures are initiated after successful
completion of the transport bearer establishment procedures and the RRC radio bearer
setup procedure is initiated.
The UE is configured with the following information:
H-RNTI (from CRNC)
Within the RB mapping info IE:
Multiplexing options, see "RAB Multiplexing Options" on page 48
Within the Added or Reconfigured DL TrCH Information IE:
HARQ process information (from Node B)
MAC-d flow/priority queue configuration (from SRNC: RBT)
MAC-hs reset indicator set to true
Within the Downlink HS-PDSCH Information IE:
HS-SCCH code set information (from Node B)
Measurement feedback information (from SRNC/CRNC)
Within the Uplink DPCH Power Control Info IE:
ACK/NACK control info (SRNC)
Within the Downlink information for each radio link IE corresponding to selected
HSDPA serving cell:
Serving HS-DSCH radio link indicator
The procedure finishes upon reception of the RRC: RADIO BEARER SETUP
COMPLETE message.
The following failures result in the RAB establishment procedure failing:
NBAP: RL reconfiguration reparation failure with an NBAP cause not equal to
not enough user plane processing resources
ALCAP: TB setup failure
RRC: radio bearer setup failure
In the event of these failures, a RAB ASSIGNMENT RESPONSE message is sent to the
core network indicating that establishment of the RAB failed. Any resources established
for the RAB are released. If an RRC RADIO BEARER SETUP FAILURE message is
received, a radio failure occurs which results in dropping the RRC connection since the
Node B is already committed to the new configuration. The reason is that RRC
connection reestablishment is only supported if a RAB exists.
The following failures result in a retry on DCH:
Admission control failure including an NBAP: RL reconfiguration failure with the
cause not enough user plane processing resources. For more information see
"Pre-emption and Interaction with Admission Control" on page 73.
Fig. 4.4 shows the message sequence chart for RAB setup (DCH to HS-DSCH).
58
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
UE
Support of HSDPA
FD012249 - UMR5.0
Node 1
Node B2
SRNC
Fig. 4.4
New H-RNTI
Downlink HS-PDSCH Iinformation
RB mapping info ->
DL HS-DSCH MAC-d flow id
Added/reconfigured DL TrCH information ->
HS-DSCH
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
59
Support of HSDPA
FD012249 - UMR5.0
4.1.1.10
Feature Description
Radio Subsystem
60
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
61
Support of HSDPA
FD012249 - UMR5.0
UE
Feature Description
Radio Subsystem
Node B
SRNC
Fig. 4.5
62
New H-RNTI
Downlink HS-PDSCH Iinformation
RB mapping info ->
DL HS-DSCH MAC-d flow id
Added/reconfigured DL TrCH information ->
HS-DSCH
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.1.11
Support of HSDPA
FD012249 - UMR5.0
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
63
Support of HSDPA
FD012249 - UMR5.0
UE
Feature Description
Radio Subsystem
Node B
RNC
Cell Selection:
see HSDPA Mobility Handling
Fig. 4.6
New H-RNTI
Downlink HS-PDSCH Iinformation
Added/reconfigured DL TrCH information ->
HS-DSCH
4.1.1.12
64
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Fig. 4.7 shows the message sequence chart for channel-type switching from HS-DSCH
to FACH.
UE
Node B1
Node B2
RNC
Fig. 4.7
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
65
Support of HSDPA
FD012249 - UMR5.0
4.1.1.13
Feature Description
Radio Subsystem
66
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Fig. 4.8 shows the message sequence chart for RAB setup (HS-DSCH to DCH).
UE
Node 1
Node B2
RNC
OPT
Performed if new
RAB uses RLC AM
Deallocate H-RNTI
Fig. 4.8
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
67
Support of HSDPA
FD012249 - UMR5.0
4.1.1.14
Feature Description
Radio Subsystem
68
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
UE
Support of HSDPA
FD012249 - UMR5.0
Node B1
Node B2
RNC
Deallocate H-RNTI
Fig. 4.9
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
69
Support of HSDPA
FD012249 - UMR5.0
4.1.1.15
Feature Description
Radio Subsystem
UE
Node B1
Node B2
RNC
OPT
Fig. 4.10
70
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.1.16
Support of HSDPA
FD012249 - UMR5.0
4.1.1.17
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
71
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
sizes derived from UE available memory if the remaining RAB is eligible for HS-DSCH
usage.
If the UE fails the radio bearer reconfiguration and the cause is configuration
unsupported, the RNC reverts to the local RLC parameters used before the radio
bearer reconfiguration and resumes the governing RAB setup procedure. This RAB setup procedure may fail due to limited UE memory. In the event of other failure causes,
the RNC initiates the Iu release procedure.
Fig. 4.11 shows the message sequence chart for radio bearer reconfiguration.
UE
SRNC
Fig. 4.11
4.1.1.18
4.1.1.19
72
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Fig. 4.12 shows the message sequence chart for RAB setup (CCH to DCH, DCH to
DCH).
GSM
GSM
SRNC
OPT
Fig. 4.12
Message sequence chart for RAB setup (CCH to DCH, DCH to DCH)
4.1.1.20
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
73
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
74
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.1.21
Allocation of H-RNTI
H-RNTI is the unique identifier of an HSDPA user within a cell. It is used to scramble the
control data on the HS-SCCH.
H-RNTI duplication handling for the Node B
Available H-RNTI data in the Node B and RNC become inconsistant if NBAP messages
from the Node B/RNC do not reach their destination RNC/Node B.
Therefore, the Node B checks if a H-RNTI is a unique ID in the cell when it is requested
to setup a radio link. If the Node B detects a H-RNTI ID duplication, it rejects the setup
and sends a RADIO LINK FAILURE message to the RNC that contains all radio links of
the associated DPCH for the duplicated communication context. After that, all resources
for this communication context are removed by a subsequent radio link deletion request
and an ALCAP release from the RNC.
If the Node B does not receive a RADIO LINK DELETION REQUEST message, the
Node B sends an NBAP: RESET REQUEST message to the RNC that contains the
communication context and starts a timer. The Node B releases the call if the RNC
sends an NBAP RESET RESPONSE message or the timer expires.
In the event that no ALCAP is released after Radio Link Deletion or during Reset Procedure, the Node B sends an ALCAP REL message to the RNC. If the ALCAP RLC timer
expired, the Node B releases the ALCAP resource with RES.
Fig. 4.13 shows the the message sequence for a radio link setup. A radio link reconfiguration is handled similar.
Node B
RNC
RadioLinkRequest (H-RNTI=1)
H-RNTI=1 already
exists in the Node B
Fig. 4.13
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
75
Support of HSDPA
FD012249 - UMR5.0
4.1.2
Feature Description
Radio Subsystem
4.1.2.1
76
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
HSDPA cell
UE
Frequency#1
UE
Frequency#1
Node B
Fig. 4.14
The SRNC tries to move the UE to an HSDPA-supporting cell if the UE has an RRC
connection to a cell which does not support HSDPA (Cell_FACH state) and channeltype switching from FACH to HS-DSCH is triggered due to traffic monitoring. This is not
performed if a RAB is established. If such an HSDPA-supporting cell is available, the
SRNC establishes HS-DSCH on that cell. Fig. 4.15 shows the related interfrequency,
intra-SRNC, intra-Node B handover scenario.
UE
Frequency#1
Frequency#2
HSDPA cell
UE
Frequency#1
Frequency#2
Node B
Fig. 4.15
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
77
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
Fig. 4.16
Inward mobility
78
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
UE
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
Node B
Fig. 4.17
UE
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
Node B1
Fig. 4.18
Node B2
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
79
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
Node B1
Fig. 4.19
Node B2
80
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
UE
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
DRNC
SRNC
Fig. 4.20
HSDPA cell
Frequency#1
Active set
UE
Frequency#1
Active set
SRNC
Fig. 4.21
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
81
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
UE
Frequency#1
Frequency#2
HSDPA cell
UE
UE
Frequency#1
Frequency#2
Node B1
Fig. 4.22
4.1.2.2
82
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
If the UE is informed by the SRNC that the MAC-hs is reset, the UE sends the STATUS
PDU to the SRNC. The SRNC can now retransmit the SDUs lost due to the MAC-hs
reset.
4.1.2.3
Measurement Configuration
This section provides an overview of the differences from the measurement
configuration due to the introduction of HSDPA.
With UMR5.0, event 1D is introduced to detect the best cell within the active set, refer
to section "Change of the Serving HS-DSCH Cell" on page 87. Event 1D is a
measurement dedicated to HSDPA and independent of the measurements currently
defined, that is the measurement ID is newly assigned to event 1D.
Event 1D is configured in the event of:
Setup: Upon the successful establishment of HS-DSCH
Release: Upon release of HS-DSCH.
The same Intrafrequency Cell Info List IE is used for event 1D as for the intrafrequency
measurement events 1A, 1B and 1C.
4.1.2.4
HS-DSCH Establishment
The trigger conditions for HS-DSCH establishment are:
1. PS RAB establishment while no other RAB is active
2. Channel-type switching from FACH to HS-DSCH
In UMR5.0, an HS-DSCH is not established if the UE has measurements 2A, 2B, 3A, or
3A active with or without compressed mode. HS-DSCH shall not be established since
simultaneous activation of compressed mode and HS-DSCH is not supported. Therefore, compressed mode is deactivated before the HS-DSCH is established. If the SRNC
receives event 2D/2D/2D, channel-type switching from HS-DSCH to DCH is performed
and compressed mode is activated again.
The system behavior can be improved by the optional feature UE Differentiation. The
purpose of the UE Differentiation feature is to assign power resources to HSDPA UEs
as much as possible. When establishing a PS RAB, the RNC distinguishes Release 99
UEs and Release 5 UEs. For more information see FD012254 UE Differentiation.
PS RAB establishment
In Cell_FACH state, the SRNC establishes a PS RAB on HS-DSCH if no other RAB is
active at this time, the UE has an RRC connection to an HSDPA cell, and the UE supports HSDPA.
In Idle mode and in Cell_DCH state, the load control mechanism is performed that is
known from former releases.
For information on the message sequence charts see "Message sequence chart for
RAB setup (DCH to HS-DSCH)" on page 59 and "Message sequence chart for RAB setup (FACH to HS-DSCH)" on page 62.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
83
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
4.1.2.5
Inward Mobility
Inward mobility is triggered if the UE enters an area where HSDPA is supported and the
quality of the HSDPA cell is the best within the cells reported by measurement event 1A,
1B, 1C, or, if configured, 1A. HS-DSCH is established only if the quality of the reported
HSDPA cell is the best and much better than the reported non-HSDPA cells in order to
avoid frequent channel-type switching between DCH and HS-DSCH. In addition,
channel-type switching from DCH to HS-DSCH is not performed if the UE has measurements 2A, 2B, 3A or 3A active (with or without compressed mode).
The SRNC selects the serving HS-DSCH cell based on the measurement report (1A,
1B, 1C, or if configured 1A). The quality of each cell is derived from the CPICH Ec/N0
IE included in the Cell Measured Results IE. HS-DSCH is only established if the difference of the quality between the best HSDPA cell and the non-HSDPA cells is above a
predefined threshold in order to avoid frequent channel-type switching between DCH
and HS-DSCH. Furthermore, HS-DSCH is not established if the UE has measurements
2A, 2B, 3A or 3A active (with or without compressed mode).
The SRNC establishes HS-DSCH as follows:
1. The SRNC selects the new active set based on the Event results IE.
2. The SRNC checks whether or not the best cell is an HSDPA cell.
If the best cell is a non-HSDPA cell or is under the control of the DRNC, the SRNC
performs an active set update.
If the best cell is an HSDPA cell and is under the control of the SRNC, the difference in quality between the best HSDPA cell and the non-HSDPA cells is
checked. The SRNC performs an active set update if this difference is below the
predefined threshold. If the difference is above the predefined threshold, the
84
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Node B1
SRNC
Node B2
UE
Fig. 4.23
Node B1
Node B2
UE
Inward mobility
The SRNC includes all HSDPA-related parameters in the RADIO LINK RECONFIGURATION PREPARE and the TRANSPORT CHANNEL RECONFIGURATION messages since this is the first establishment of HS-DSCH and the UE and the Node B do not
have these parameters.
Fig. 4.24 shows the message sequence chart for inward mobility. If the trigger for
establishing the HS-DSCH is a measurement report (1B or 1C), the deletion of the radio
link(s) in Node B1/Node B2 might be performed by the active set update procedure. If
the radio link(s) have already been established via Node B2, the RL addition procedure
is used to establish new radio link(s) via Node B2.
Since DL bit rate adaptation is not applicable when HS-DSCH is used, the CRNC
terminates the transmitted code power (radio link quality) measurement by sending a
DEDICATED MEASUREMENT TERMINATION REQUEST message to the related
Node Bs upon the successful configuration of measurement 1D. The rate for the UL
DTCH is changed to 64 kbit/s if the rate is other than 64 kbit/s and the transport bearer
is modified accordingly. For more information on the handling of the transport bearer for
DTCH see "HSDPA RAB Handling" on page 45.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
85
Support of HSDPA
FD012249 - UMR5.0
UE
Feature Description
Radio Subsystem
Node B1
Node B2
SRNC
Decision to perform
CTS (DCH -> HS-DSCH)
RADIO LINK SETUP REQUEST
Allocate H-RNTI
RADIO LINK RECONFIGURATION PREPARE
(Modification of UL DTCH (if necessary), Deletion of DL DTCH)
RADIO LINK RECONFIGURATION PREPARE
(Modification of UL DTCH (if necessary),
Deletion of DL DTCH,
Establishment of HS-DSCH)
RADIO LINK RECONFIGURATION READY
RADIO LINK RECONFIGURATION READY
Fig. 4.24
86
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.2.6
Support of HSDPA
FD012249 - UMR5.0
If this cell is an HSDPA cell and is controlled by the SRNC, the SRNC performs a
change of the serving HS-DSCH cell.
2. If this cell is a non-HSDPA cell or is controlled by the DRNC, the SRNC performs
channel-type switching from HS-DSCH to DCH, see 4.1.2.7"Outward Mobility" on
page 96.
The SRNC ignores the measurement report of event 1D if the reported cell is the same
as the current serving HS-DSCH cell.
Fig. 4.25 shows how the serving HS-DSCH cell is moved from one radio link to another
under the control of the same Node B.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
87
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
SRNC
Node B1
Node B2
UE
Fig. 4.25
SRNC
Node B1
Node B2
UE
88
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
UE
Node B1
SRNC
Deallocate H-RNTI
(for source cell)
Fig. 4.26
Message sequence chart for an intra-Node B change of the serving HS-DSCH cell (event 1D)
Fig. 4.27 shows how the serving HS-DSCH cell is moved from one radio link to another
radio link between two different Node Bs.
SRNC
Node B1
SRNC
Node B2
Node B1
UE
Fig. 4.27
Node B2
UE
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
89
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
parameters since this is the first HS-DSCH establishment for that Node B. The HSDPArelated parameters are the same as the parameters used to configure HS-DSCH. The
TRANSPORT CHANNEL RECONFIGURATION message includes only the cellspecific parameters since the UE already has the HSDPA-related parameters. In
addition, the MAC-hs Reset Indicator is set to true in the TRANSPORT CHANNEL
RECONFIGURATION message.
Fig. 4.28 shows the message sequence chart for inter-Node B serving cell change due
to measurement event 1D. The target cell indicates the cell where HS-DSCH will be
established and the source cell indicates the cell where HS-DSCH was established before the serving HS-DSCH cell was changed.
UE
Node B1
Node B2
SRNC
Allocate H-RNTI
(for target cell)
RADIO LINK RECONFIGURATION PREPARE (Deletion of HS-DSCH)
RADIO LINK RECONFIGURATION PREPARE (Establishment of HS-DSCH)
RADIO LINK RECONFIGURATION READY
RADIO LINK RECONFIGURATION READY
Deallocate H-RNTI
(for source cell)
Fig. 4.28
90
Message sequence chart for inter-Node B serving cell change (event 1D)
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
91
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
SRNC
Node B1
SRNC
Node B2
Node B1
UE
Fig. 4.29
Node B2
UE
92
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
UE
Node B1
Node B2
SRNC
Deallocate H-RNTI
(for source cell)
Fig. 4.30
Message sequence chart for the change of the serving HS-DSCH cell (event 1A)
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
93
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Fig. 4.31 shows a scenario where the radio link on which HS-DSCH was previously
established is deleted after the change of the serving HS-DSCH cell.
SRNC
Node B1
SRNC
Node B2
Node B1
UE
Fig. 4.31
Node B2
UE
94
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
UE
Support of HSDPA
FD012249 - UMR5.0
Node B1
Node B2
SRNC
Deallocate H-RNTI
(for source cell)
ALCAP Iub Transport Bearer Release (HS-DSCH)
Allocate H-RNTI
(for target cell)
HS-DSCH Reestablishment
Fig. 4.32
Message sequence chart for the change of the serving HS-DSCH cell (Event 1C)
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
95
Support of HSDPA
FD012249 - UMR5.0
4.1.2.7
Feature Description
Radio Subsystem
Outward Mobility
Outward mobility occurs if the UE leaves the area where HSDPA is supported. In this
case, the quality of the non-HSDPA cell is much better than the quality of the HSDPA
cell or the HSDPA cell is removed from the active set. Therefore, channel-type switching
from HS-DSCH to DCH is performed.
The trigger conditions for outward mobility are:
1. Measurement report (event 1A, 1B, 1C, 1D, or, if configured, 1A) from the UE and
the quality of the non-HSDPA cell is better than the quality of the HSDPA cells.
Channel-type switching from HS-DSCH to DCH is performed only when the quality
of the current serving HS-DSCH cell is much worse than the quality of the nonHSDPA cells in order to avoid frequent channel-type switching between HS-DSCH
and DCH.
2. Measurement report (event 1B or 1C) from the UE and no HSDPA cell will be
included in the next active set.
3. Measurement report (event 1A, 1B, 1C, 1D, or, if configured, 1A) from the UE and
the quality of the cell under the control of the DRNC is better than the quality of the
HSDPA cells under the control of the SRNC.
4. Measurement report (event 2D/2D/2D) from the UE. Channel-type switching from
HS-DSCH to DCH is performed only when the quality of the current serving
HS-DSCH cell is much worse than the quality of the non-HSDPA cells in order to
avoid frequent channel-type switching between HS-DSCH and DCH.
5. Measurement report (event 1A, 1C, or, if configured, 1A) from the UE and
intrafrequency SRNS relocation without Iur interface is triggered.
Outward mobility is subdivided into an intrafrequency and an interfrequency/intersystem
process.
Detection of outward mobility (intrafrequency process)
Outward mobility is detected during the change of the serving HS-DSCH cell process
due to:
Quality degradation of the HSDPA cells because the UE leaves the area where
HSDPA is supported
Removal of all HSDPA cells from the active set
UE mobility toward the DRNC
Initiation of intrafrequency SRNS relocation without Iur interface
If the SRNC receives a measurement report for the preparation of an SRNS relocation
during channel-type switching from HS-DSCH to DCH, it is treated as a measurement
report that is received within the time period between SRNS relocation is triggered and
the SRNC sends an RANAP: RELOCATION REQUIRED message.
If intrafrequency SRNS relocation with Iur interface is performed, the UE does not use
HS-DSCH because HS-DSCH via Iur interface is not supported.
If, while the UE is using HS-DSCH, measurement report 1A or 1C reports that a cell is
restricted or a RL setup/addition via the DRNC is rejected with the reason cell reserved, channel-type switching from HS-DSCH to DCH is performed before an interfrequency handover is initiated.
Fig. 4.33 shows how a new radio link is established via a new Node B while this Node B
does not support HSDPA.
96
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
SRNC
Node B1
SRNC
Node B2
UE
Fig. 4.33
Node B1
Node B2
UE
Outward mobility
The current serving HS-DSCH cell is deleted if the active set update procedure is
completed. The SRNC stops transmission of the HS-DSCH data frame before channeltype switching from HS-DSCH to DCH in order to minimize the loss of data. If the active
set is not changed, that is the trigger is event 1D or SRNC relocation, only channel-type
switching from HS-DSCH to DCH is performed.
Fig. 4.34 shows the message sequence chart for outward mobility. For more information on the handling of the transport bearer for DTCH see "HSDPA RAB Handling" on
page 45.
Since DL bit rate adaptation is applicable when DCH is used, the CRNC sends a
DEDICATED MEASUREMENT INITIATION REQUEST message to the related
Node Bs to initiate the transmitted code power (radio link quality) measurement if
measurement event 1D is released.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
97
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
UE
Node B1
Node B2
SRNC
Deallocate H-RNTI
ALCAP Iub Transport Bearer Release (DCCH + DTCH)
Fig. 4.34
98
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.2.8
DRNC Behavior
HSDPA is not established via the Iur interface. If the RNC acts as a DRNC, the SRNC
may request the DRNC to establish HS-DSCH. In this case, the DRNC rejects the
request with the case value DL Shared Channel Type not Supported.
4.1.2.9
Error Handling
This section summarizes the handling of failures.
HS-DSCH establishment or release
HS-DSCH establishment or release is subdivided into two phases:
Active set update
Channel-type switching between HS-DSCH and DCH or change of the serving
HS-DSCH cell
For more information on error handling see "HSDPA RAB Handling" on page 45.
When channel-type switching from DCH to HS-DSCH is performed, the active set
update procedure has been successfully completed (event 1A, 1B, 1C, or, if configured,
1A). In the case of event 1D, however, the active set is unchanged.
In the event of an admission control failure or an NBAP failure (RL reconfiguration
prepare failure) or an ALCAP failure, DCH is still available even if HS-DSCH is not available. Therefore, the SRNC keeps the current configuration, that is DCH. Channel-type
switching from DCH to HS-DSCH is triggered by the next active set update procedure.
When channel-type switching from HS-DSCH to DCH is performed, the active set
update procedure has been successfully completed (event 1A, 1B, 1C, or, if configured,
1A). In the case of event 1D or 2D/2D/2D, however, the active set is unchanged.
In the event of an NBAP/RNSAP failure (RL reconfiguration prepare failure with a cause
value other than not enough user plane processing resources) or an ALCAP failure,
HS-DSCH is released and RRC connection reestablishment is performed since
HS-DSCH is not established on the best cell any more. Channel-type switching from
FACH to HS-DSCH is triggered by traffic monitoring.
Upon an admission control failure or an NBAP/RNSAP failure (RL reconfiguration
prepare failure with the cause value not enough user plane processing resources), a
retry at the minimum rate of the DCH is performed.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
99
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
When the serving HS-DSCH cell is changed, the active set update procedure has been
successfully completed (event 1A, 1B, 1C, or, if configured, 1A). In the case of event
1D or 2D/2D/2D, however, the active set is unchanged. Since the associated DCH has
already been established, failures due to admission control in the CRNC never happen.
In the event of an NBAP failure (RL reconfiguration prepare failure with a cause value
other than not enough user plane processing resources) or an ALCAP failure,
HS-DSCH is released and RRC connection reestablishment is performed since
HS-DSCH is not established on the best cell any more. Channel-type switching from
FACH to HS-DSCH is triggered by traffic monitoring.
Upon an admission control failure or an NBAP/RNSAP failure (RL reconfiguration
prepare failure with the cause value not enough user plane processing resources), a
retry at the minimum rate of the DCH is performed.
If an RRC message fails and RRC connection reestablishment is allowed according to
the current system, RRC connection reestablishment is performed. The failure handling
of RRC messages depends on the type of error, for example the cause value.
RL failure of the RL on which the serving HS-DSCH cell is mapped
If the CRNC receives a RADIO LINK FAILURE INDICATION message with the cause
value synchronization failure from the cell where HS-DSCH is currently established
and the radio link concerned is not the last one, the radio link is deleted. The UL
synchronization immediately gets lost and channel-type switching from HS-DSCH to
DCH is performed. This behavior is similar to outward mobility handling where the
serving HS-DSCH cell is deleted by event 1B. If the radio link concerned is the last one,
RRC connection reestablishment is performed.
Reception of measurement report 1D during change of the serving HS-DSCH
cell/outward mobility
If the SRNC receives a measurement report of event 1D during a change of the serving
HS-DSCH cell/outward mobility and the active set update is completed, the SRNC
handles this report in a way similar to other intrafrequency measurement reports during
RAB setup. Measurement reports other than event 1D are handled during inward
mobility/change of the serving HS-DSCH cell/outward mobility similarly to their handling
during RAB setup. If the SRNC receives a measurement report of event 1D during an
active set update, the SRNC handles this report in a way similar to other intrafrequency
measurement reports during an active set update.
Initiation of measurement event 1D
Since event 1D is necessary to detect the best cell within the active set, it results in a
RELEASE CALL message.
100
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.2.10
UE Differentiation
The purpose of the optional UE Differentiation feature is to assign power resources to
HSDPA UEs as much as possible. For more information see FD012254 HSDPA UE Differentiation.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
101
Support of HSDPA
FD012249 - UMR5.0
4.1.3
Feature Description
Radio Subsystem
4.1.3.1
Resource
Allocation
Load Control
Congestion
Control
Node B Measurem.
Control
Power Control
Admission
Control
Interfrequency
Load Control
Congestion
Control
Measurement
Reporting Control
Code Allocation,
Release
Preprocessing
Control
Restriction
Control
Fig. 4.35
Affected by HSDPA
Admission Control
102
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
general, each UE on a PS RAB which is associated to the HSDPA channel requires the
following:
Downlink (DL) direction
One associated DPCH with spreading factor (SF) 256
Uplink (UL) direction
One DPCH in the uplink (UL) direction for the HS-DPCH (for HARQ and CQI) with
SF 256
One associated DPCH (signaling radio bearer SRB) for traffic of varying SF regardless of whether or not waiting data exists
The decision of admission control about whether or not to admit a UE on a channel depends on periodic common measurements. The relevant measurement reports are sent
via NBAP. These reports indicate the ratio of non-HSDPA power in relation with the
maximum configured power in the relevant Node B. Each report is treated by higher-layer-filtering (floating average) over a certain time frame.
Fig. 4.36 illustrates the interactions between admission control and code allocation including the protocols and measurements, call processing, and OAM databases in the
event of allocating or deallocating resources.
CRNC: Congestion Indication
CRNC
Measurement
Database
CRNC
Dynamic
Database
OAM
Database
Resource Allocation
Fig. 4.36
Deallocate Resources
Allocate Resources
Admission
Control
Yes
No
Yes
No
Yes
No
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
103
Support of HSDPA
FD012249 - UMR5.0
4.1.3.2
Feature Description
Radio Subsystem
104
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.1.3.3
Support of HSDPA
FD012249 - UMR5.0
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
105
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Upon RL reconfiguration, the old load of all cells in the active set is removed. This
handling method is the same as that currently applied.
The CRNC allocates the H-RNTI.
Case 3: Outward mobility
On the DL, the new load information for the DCH is available.
On the UL, the new load information for the DCH is available.
In both the DL (SRB) and UL (HS-DPCCH-related PS bearer for the HSDPA radio
link with 64 or 384 kbit/s) directions, the old load information is available.
The CRNC deallocates the H-RNTI.
NOTE
When admission control rejects the setup on the HSDPA channel, a retry on
DCH state with the minimum rate is attempted. RAB pre-emption will then apply, too.
Admission control uses several load thresholds for the different DPCHs which are required for an HSDPA-capable UE to operate. The thresholds are as follows:
For the associated DPCH on the DL, the threshold for the SRB 3.4 kbit/s is applied.
The HS-DPCCH required in the UL direction uses the threshold for this SRB, too.
For the associated DPCH on the UL, the thresholds for the PS interactive/background bearers is applied. Their corresponding UL rate thresholds are based on the
slope function.
Since the HS-DPCCH is only used for control issues, a new load is applied for the
HS-DPCCH which is exclusively applicable to the HSDPA radio link, thus requiring
a new physical channel type attribute for the HS-DPCCH. The gain factors Bc and
Bd, however, will only be system data.
With regard to requirements concerning the signal-to-interference ratio (SIR), the values
of the channels mentioned before are applied.
Since two channels, i.e. the associated DPCH and the HS-DPCCH which is only applicable for the HSDPA radio link, are always used on the UL, HSDPA admission control
has to consider these two pieces of load information.
With respect to call establishment and reestablishment in UMR5.0, admission control
handling is performed as follows, depending on the relevant case:
Case 1: PS RAB setup triggering a DCH to HS-DSCH procedure
Admission control handles this situation in the same way as an inward mobility
handover.
106
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.3.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
107
Support of HSDPA
FD012249 - UMR5.0
4.1.3.5
Feature Description
Radio Subsystem
4.1.3.6
108
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.1.3.7
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
109
Support of HSDPA
FD012249 - UMR5.0
4.1.4
Feature Description
Radio Subsystem
4.1.4.1
State Management
A UTRAN cell is capable of providing HSDPA service as soon as the new High Speed
Downlink Packet Access Channel object is configured. This channel is configured in the
database of the RNCs backend via the hsdpa HMI command. The resource status indication (RSI) and the audit response HSDPA capability information indicate the capabilities of the Node B which is associated to the relevant UTRAN cell. The RNC,
however, does not use this information do decide if the CRNC is to initialize the HSDPA
resources. This scenario is in line with the implementation principle in product releases
prior to UMR5.0, such as power capability values. In the event of a configuration mismatch, i.e. if the Node B is not capable of HSDPA although the configuration data requires HSDPA, NBAP (Node B application part) failure handling is applied. The NBAP:
PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message is thus
used.
Upon the setup of the HSDPA resources, the RSI is used to monitor the HSDPA resources. The current status is indicated by means of the HS-DSCH resource information. Fig. 4.37 provides an overview of the RSI handling.
In general, each status indication of an RSI contains the operational state (OST) and the
availability status (AVS) of the HSDPA channel.
110
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Node B
CRNC
HSDPA-related failure in
the Node B
Resource status indication (RSI)
HS-DSCH resource information
operational state: disabled
Cell operational state: degraded
Non-HSDPA measurements
will be continued (Node B will
use its transmitted carrier
power measurements and
map these onto the nonHSDPA power measurement
report)
Fig. 4.37
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
111
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Otherwise, if further radio links are still active for the specific UE, the RNC initiates
channel-type switching (CTS) from the HS-DSCH to a DCH.
Upon reception of an RSI indicating HS-DSCH resource information: operational
state = enabled, the controlling RNC (CRNC) takes the following measures:
Setting the state attribute of the HSDPA channel to enabled
Informing the OMC about the reactivated status of the HSDPA channel including the
its availability status
Tab. 4.7 provides an overview of the states supported by the HSDPA channel HSDSCH) and the corresponding trigger events.
HS-DSCH state/status
OST
AVS
disabled
offline
disabled
enabled
empty set
disabled
disabled
failed
Tab. 4.7
Furthermore, a dependency exists between the state of the HSDPA channel and the associated UTRAN cell. The state relations between these two objects are shown in
Tab. 4.8.
112
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
OST/AVS
Cell state/status
HS-DSCH
state/status
enabled/
empty set
enabled/
empty set
disabled/
failed
disabled/
dependency
enabled/
degraded
disabled/
failed
enabled/
degraded
enabled/
empty set
The cause which led to the cells degradation does not impact on the HS-DSCHs
state.
disabled/
offline
disabled/
offline
disabled/
not installed
disabled/
not installed
enabled/
empty set
disabled/
offline
Tab. 4.8
4.1.4.2
Common Measurements
The HSDPA feature requires the introduction of new common measurements whose intention is to measure the transmitted carrier power of all codes not used for the transmission of HS-PDSCHs and HS-SCCHs. These measurements are called the NonHSDPA Transmit Power measurement. The Non-HSDPA Transmit Power measurement includes both periodic and event-triggered measurements which are initiated independently. The periodic and event-triggered measurements are used for admission
control and congestion control, respectively.
This new common measurement is set up instead of the Transmitted Carrier Power
measurement which was used in product releases prior to UMR5.0. The Non-HSDPA
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
113
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Transmit Power measurement, however, applies the same characteristics as the previous Transmitted Carrier Power measurement.
4.1.4.3
114
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Transport Channels
Physical Channels
Fig. 4.38
The setup for common channels is not changed with UMR5.0. In other words, none of
them is moved to a secondary scrambling code. Therefore, after the setup of the UTRAN
cell, the following channelization codes are used below one spreading factor of 16:
1 channelization code of SF = 64
1 channelization code of SF = 128 (optional)
4 channelization codes of SF = 256
Fig. 4.39 outlines this information.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
115
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
16
+ 15 * HS-PDSCH
16
....
16
16
32
32
64
128
256
Fig. 4.39
128
256
64
64
256
128
256
256
128
128
256
256
64
256
256
128
256
256
128
256
256
128
256
256
256
NOTE
Before starting the initial code allocation for the HS-PDSCH, the RNC confirms that the
HSDPA feature is enabled. This check is only performed during the setup of the cell. If
the cell has already been active when enabling the HSDPA feature, the change will only
take effect at the next cell setup procedure.
If the HSDPA feature is disabled, no HSDPA capability is provided. Therefore, the same
cell setup procedure as in previous product releases will be applied.
When initially allocating the starting number of HS-PDSCH codes and the codes which
are used for the HS-SCCH, the code with the smallest number is used in both cases.
This handling is in line with the radio resource management of previous releases.
After the setup of the UTRAN cell, the CRNC reserves all specified codes for the HSPDSCH and the HS-SCCH, using the code tree (see Fig. 4.39). Furthermore, the
CRNC marks the descendant and ascendant codes of the specified codes as unavailable. To make sure that none of the code trees codes is assigned to any user, reserving
and marking is done simultaneously with the assignment of the common channel channelization codes in the code tree.
Fig. 4.40 and Fig. 4.41 show the UMR5.0 cell setup sequence. In UMR5.0, the cell setup procedure has been modified in comparison to the product release prior to UMR5.0.
116
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Node B
RNC
- NBAP cell setup
- SysInfoUpdate SIB1,
2, 3, 11
Cell setup
Physical shared channel
reconfiguration request
alt
par
2
As in UMR4.0, including
SIB5 and SIB7
alt
Common measurement
initiation response (cell, nonHSDPA power, periodic)
Common measurement
initiation request (cell, nonHSDPA power, event-triggered)
par
opt
Common measurement
initiation failure (non-HSDPA
power, periodic, cause IE)
4
The RSI can be
received or not
4
Physical shared channel
reconfiguration request
(number of both PDSCH
and SCCH codes = 0)
alt
Fig. 4.40
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
117
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Node B
RNC
par
2
Common transport channel setup
2
Fig. 4.41
118
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
After successful setup of the UTRAN cell, the HSDPA resources are set up by sending
the NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION message to the
Node B. This message provides the HS-PDSCH-FDD-Code-Information and HSSCCH-FDD-Code-Information optional parameters for the HS-PDSCH and HS-SCCH,
respectively. Furthermore, the TPSCR timer is started.
Upon reception of the NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION
message, the Node B parses this message, thus verifying the availability of all necessary resources. If establishing the Node Bs HSDPA resources fails, however, the
Node B sends an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message with a cause corresponding to the failure type which occurred. Tab. 4.9
provides information about the mapping of failure types and cause values.
NOTE
An NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message
impacts neither on the operational state of the UTRAN cell nor on already instantiated
common transport channels.
Failure type
Cause value
CauseRadioNetwork:
Number Of Downlink Codes Not Supported
CauseRadioNetwork:
Node B Resources Unavailable
Tab. 4.9
If the RNC receives neither an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE message nor an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION RESPONSE message before the expiry of the TPSCR, the RNC repeats
the request a predefined number (N) of times. As a consequence, the Node B is capable
of receiving and processing subsequent NBAP: PHYSICAL SHARED CHANNEL
RECONFIGURATION messages of the same configuration. If these N repetitions expire, the cell deletion procedure is triggered.
Upon reception of an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION
FAILURE message, the RNC takes the following measures:
Setting the state attribute of the MOC HSDPA to disabled
Informing the OMC about the failed setup, including the failures cause value. The
NBAP failure will trigger the corresponding alarm as a consequence.
Releasing the configured HSDPA codes in the code tree and making them available
to DCH users.
Setting up the Transmitted Carrier Power common measurements in the way they
were performed in the product release prior to UMR5.0.
Upon reception of an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION
RESPONSE message indicating the successful setup of HSDPA resources, in contrast,
the RNC takes the following measures:
Setting the state attribute of the MOC HSDPA to enabled
Informing the OMC about the successful setup
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
119
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Initiating the Non-HSDPA Transmit Power measurement (see "Common Measurements" on page 113)
If the setup of the periodic Non-HSDPA Transmit Power measurement succeeds, the
HS-DSCH setup procedure ends. Additionally, a failed setup of the event-triggered
Non-HSDPA Transmit Power measurement does not impact on the HSDPA setup in
the relevant UTRAN cell.
Otherwise, if the periodic Non-HSDPA Transmit Power measurement fails, the RNC
takes the following measures:
Informing the OMC about the failed periodic Non-HSDPA Transmit Power measurement. This triggers the corresponding alarm indicating the unsuccessful periodic
Non-HSDPA Transmit Power measurement.
Deleting the configured HSDPA codes by means of the NBAP: PHYSICAL SHARED
CHANNEL RECONFIGURATION message. In this case, the number of codes assigned to PDSCHs or SCCHs is set to zero. Nevertheless, the operational state of
the UTRAN cell is not impacted for DCH users and the cell still operates in non-HSDPA mode. Therefore, a deactivation and a subsequent activation procedure must be
applied to the cell in order to put the UTRAN cell in HSDPA operating mode.
If deleting the configured HSDPA codes fails, however, the RNC deletes the UTRAN
cell.
Setting the HSDPA MOCs operational state to disabled and its availability status to
failed. Furthermore, the RNC informs the OMC about the change of states by
means of an alarm and a notification.
Releasing the configured HSDPA codes in the RNCs code tree. These codes are
made available to DCH users.
Setting up the Transmitted Carrier Power measurement which has been used in
product releases prior to UMR5.0.
4.1.4.4
120
NOTE
In an HSDPA-capable cell, the HSDPA feature may be disabled and then reenabled
again. When disabling HSDPA, all HSDPA-related radio bearers must be released in
advance!
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
4.2
Support of HSDPA
FD012249 - UMR5.0
Functional Split
This chapter describes the functional split of mobility topics with respect to HSDPA. The
following items are covered:
HSDPA RAB Handling
HSDPA Mobility Handling
HSDPA Admission Control and Congestion Control
HSDPA Code and Power Allocation and Redimensioning
4.2.1
4.2.2
4.2.3
4.2.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
121
Support of HSDPA
FD012249 - UMR5.0
4.3
Feature Description
Radio Subsystem
Man-Machine Interface
The introduction of HSDPA in UMR5.0 requires new parameters to configure the systems mobility part with respect to the following:
HSDPA RAB Handling
HSDPA Mobility Handling
HSDPA Admission Control and Congestion Control
HSDPA Code and Power Allocation and Redimensioning
4.3.1
Name
LMT-Name
thsdsch_fach
Tab. 4.10
Range
0 .. 65535 s
Default
Value
30 s
Description/Remarks
Period of uplink and downlink inactivity before
the PS I/B RAB is switched from HS-DSCH to
FACH0 means that inactivity is not monitored
and the connection is not switched to FACH
Name
HS-DSCH Power
Offset
Tab. 4.11
LMT-Name
po_dsch
Range
-6 ..13 dB
step 0.5
Default
Value
3 dB
Description/Remarks
Default Power offset between HS-PDSCH and
P-CPICH/S-CPICH.
Note: This parameter must be set to the same
value for all cells within the same Node B.
New parameter for the High Speed Downlink Packet Access Channel object
Tab. 4.12 shows the parameters related to HSDPA measurement information. Multiple
instances are supported per RNC [0 .. 12].
Name
LMT-Name
Range
Default
Value
Description/Remarks
1 ..64
CQI Feedback
Cycle k
cqi_cyclek
0, 2, 4, 8, 10,
20, 40, 80,
160 ms
4 ms
cqi_rep
1 .. 4
Tab. 4.12
122
Feature Description
Radio Subsystem
Name
Support of HSDPA
FD012249 - UMR5.0
LMT-Name
Range
Default
Value
Description/Remarks
ack_nack_rep 1 .. 4
cqi_po
0 .. 8
Power offset used in the UL between the HSDPCCH slots carrying CQI information and the
associated DPCCH
ack_po
0 .. 8
Power offset used in the UL between the HSDPCCH slot carrying HARQ ACK information
and the associated DPCCH
nack_po
0 .. 8
Power offset used in the UL between the HSDPCCH slot carrying HARQ NACK information
and the associated DPCCH
HS-SCCH Power
Offset
hsscch_po
-32 .. +31.75
dB
0 dB
Tab. 4.12
4.3.2
Name
LMT-Name
Range
Default
Value
Hysteresis
hyst1d
0 .. 7.5 dB
2 dB
by step of 0.5
Time to trigger
tmtrg1d
Tab. 4.13
640 ms
Description/Remarks
Determines the hysteresis value
Indicates the period of time between the timing
of event detection and the timing of sending the
measurement report.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
123
Support of HSDPA
FD012249 - UMR5.0
4.3.3
Feature Description
Radio Subsystem
Name
Reporting period for
transmitted carrier
power
Tab. 4.14
LMT-Name
mmti_tcp
Range
0.01, 0.02 ..
60, 120, 180
.. 3600 s
Default
value
10
Description
Reporting period for admission control
This parameter indicates the interval in which
periodic reports of either the non-HSDPA
transmitted carrier power (if the cell is HSDPAcapable) or the transmitted carrier power (if the
cell does not provide HSDPA service) is issued.
Name
Minimum SF available for PS interactive/background on
DCH in HSDPA cell
LMT-Name
minsf_hsdpa
Range
8, 16, 32
Default
value
8
Description
The minimum SF available in a specific HSDPA cell for the PS interactive/background RAB
if at least the predefined number (X) of UEs
transmit on the HSDPA channel.
NOTE:
A similar parameter (Minimum SF available)
already exists. This parameter is still used because admission control determines the maximum of both parameters if the HSDPA
condition applies. Please refer to "Restriction
Control in the CRNC for HSDPA" on page 107.
Tab. 4.15
124
actrc_hsdpa
0 .. 256 UEs
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
4.3.4
Name
LMT-Name
Range
Default
value
Description
no_pdsch
1 .. 15
NrOfHSSCCHs
no_scch
1 .. 4
Tab. 4.16
MOC HSDPA attributes for code and power allocation and redimensioning
4.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
125
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
5.1
Functional Description
With regard to UTRAN operation and maintenance, the functional descriptions are subsequently provided for
"RNC" on page 126 and
"Node B" on page 132
5.1.1
RNC
With respect to the HSDPA-capable RNC, this section describes the OAM modifications
in terms of:
Equipment Management
Transport Network Layer Management
Radio Network Layer Management
Optional Feature Handling Within the RNC
5.1.1.1
Equipment Management
To support HSDPA, the RNC requires new/modified hardware (HW) to be installed.
However, only model units with either eRNC configuration or mixed cRNC/eRNC configuration are allowed for an upgrade to HSDPA. As a precondition for this upgrade,
model units affected must be equipped with CMP (composite/decomposite) or WCMP
(wideband CMP) cards. In general, all model units intended for HSDPA capability need
a firmware (FW) upgrade of their CMUX cards in the A/B/C-PRM (packet radio module)
and of their WLSC cards in the B/C-LSM (line switch module). RNC model units
equipped with BLSC modules must be exchanged by WLSC modules.
The following new HW cards must be installed for HSDPA support:
Highspeed Downlink Shared Channel Trunk (HSDST) card
The mounting position of the HSDST is the B/C-LSM where C-LSM is the rack type
if eRNC model units are used.
Highspeed Packet Radio Link Controller (HSPRLC) card
The mounting position of the HSPRLC is the A/B/C-PRM where B-PRM and C-PRM
are the rack types if eRNC model units are used.
The two new HW cards operate in single redundancy mode. Both HSDST and HSPRLC
are capable of plug&play operation. With regard to remote inventory management, both
new cards represent ob-RIU objects. Their inventory data is added to the existing inventory data file (IDF).
126
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
RNC-FE state
AST
OST
AVS
PRS
SBS
ins
unlocked
enabled
not applicable
not applicable
not applicable
ous
locked
disabled
not applicable
not applicable
not applicable
flt
unlocked
disabled
failed
not applicable
not applicable
lckft
locked
disabled
failed
not applicable
not applicable
dgt_ous
locked
disabled
in test
not applicable
not applicable
lckdgft
locked
disabled
failed, in test
not applicable
not applicable
dwlod
locked
disabled
not applicable
initializing
not applicable
dlfe
locked
disabled
failed
initializing
not applicable
Tab. 5.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
127
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
As regards the HSPRLCs fault management, the existing alarms 0053268 cmuxbl_fault
and 0053269 cmuxbl_fault_recovery are modified with respect to the new card. The
0053268 cmuxbl_fault and 0053269 cmuxbl_fault_recovery alarms indicate the occurrence of a failure in the equipment subordinated to the CMUX and the failures recovery,
respectively.
In addition to these output messages, the following two existing HMI alarms are enhanced with information about HSPRLCs and HSDSTs. These alarms are applicable for
any trunk card in the RNC:
1348012 trunk_card_congestion_occurred
If the percentage of congestion for one specific card of an equipment group exceeds
the preset threshold value, the RNC-BE will inform the RNC-FE about the congestion.
1348013 trunk_card_congestion_recovered
If the specific cards percentage of congestion falls below the threshold value, this
alarm will be output, indicating that the congestion is over and thus clearing the
1348012 trunk_card_congestion_occurred alarm.
5.1.1.2
5.1.1.3
128
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
The first two items refer to cells. All new attributes are embedded in one new MOC representing the HSDPA channel (HS-DSCH) which is subordinated to the UTRANCell
MOC. The instantiation of the new MOC is optional. This MOC exists only if the cell provides HSDPA service.
Measurement control and radio bearer control are RNC-related attributes. The relevant
data is added to the existing MOCs affected and must be configured even if HSDPA is
not supported by the RNC.
Attributes related to HSDPA measurements with an RNC-wide scope are embedded in
a new MOC called HSDPA Measurement Information. As for the new HSDPA-channel-related MOC, instantiation of this MOC is optional and exists only if the HSDPA feature is supported.
If the operator wants to use HSDPA in a cell, the following steps have to be performed
in the given order:
1.
2.
3.
4.
A detailed guideline description about HSDPA setup in a UTRAN cell is provided in the
section "Operating the Feature" on page 125.
State management
The state management of the HSDPA channel MOC which represents the HS-DSCH is
similar to that of common transport channels.
Upon creation of the MOC in the RNC, the initial combination of OST/AVS is set to disabled/offline. Otherwise, if the HS-DSCH is set up in the Node B by means of the
NBAP: Physical Shared Channel Reconfiguration procedure, the MOCs OST/AVS
combination will be enabled/empty_set. After the HSDPA setup in the Node B, the
Node B issues a resource status indication (RSI) message to the RNC.
Further details are described in the section "State Management" on page 110 in the
chapter HSDPA Code and Power Allocation and Redimensioning.
All HS-DSCH-related state/status values are compliant to ITU-T X.731.
Fault management
Whenever the Node B rejects the NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message during HS-DSCH creation or setup of the non-HSDPA
power measurement is not possible, an alarm is output by the RNC to the LMT/RC.
Therefore, a new message type is defined for the existing RNC back end alarm 1329100
nbap_failure. Furthermore, an alarm of severity major is newly created, indicating that
the HS-DSCH channel has failed in the Node B.
Tab. 5.2 lists the possible state transitions and the generated or cleared alarms at the
RNC front end during normal operation.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
129
Support of HSDPA
FD012249 - UMR5.0
Previous OST/AVS
Feature Description
Radio Subsystem
Current OST/AVS
RNC-FE alarm
MOC
Remark
Alarm content
disabled/offline
Cell
No alarm
disabled/offline
disabled/not installed
Cell
66537 - ranLocalCellNotAvailable
disabled/not installed
disabled/offline
Cell
disabled/offline
disabled/failed
Cell
66536 - ranCellNotOperational
disabled/failed
disabled/offline
Cell
No alarm
disabled/failed
enabled/empty_set
Cell
Cell operable
enabled/empty_set
disabled/offline
Cell
No alarm
enabled/empty_set
disabled/failed
Cell
66536 - ranCellNotOperational
enabled/empty_set
enabled/degraded
Cell
No alarm
disabled/offline
HS-DSCH
No alarm
disabled/offline
disabled/not installed
HS-DSCH
No alarm
The HS-DSCHs state depends on the cells state/status. Therefore, a cell alarm is
sufficient.
disabled/not installed
disabled/offline
HS-DSCH
No alarm
The HS-DSCHs state depends on the cells state/status. Therefore, a cell alarm is
sufficient.
disabled/offline
disabled/failed
HS-DSCH
disabled/failed
disabled/offline
HS-DSCH
No alarm
disabled/failed
enabled/empty_set
HS-DSCH
HS-DSCH operable
enabled/empty_set
disabled/offline
HS-DSCH
No alarm
Tab. 5.2
130
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Previous OST/AVS
Support of HSDPA
FD012249 - UMR5.0
Current OST/AVS
RNC-FE alarm
MOC
Remark
Alarm content
enabled/empty_set
disabled/failed
HS-DSCH
enabled/empty_set
disabled/dependency
HS-DSCH
No alarm
disabled/dependency
disabled/offline
HS-DSCH
No alarm
disabled/dependency
enabled/empty_set
HS-DSCH
No alarm
Tab. 5.2
OST/AVS
RNC-FE alarm
MOC
disabled/offline
Cell
Remark
Alarm content
No alarm
66537 - ranLocalCellNotAvailable
disabled/failed
Cell
enabled/empty_set
Cell
No alarm
disabled/offline
HS-DSCH
No alarm
No alarm
disabled/failed
HS-DSCH
HS-DSCH inoperable
enabled/empty_set
HS-DSCH
No alarm
disabled/dependency HS-DSCH
No alarm
Tab. 5.3
5.1.1.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
131
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
The creation of any item related to HSDPA is rejected as long as the HSDPA flag is
disabled. Configuring HSDPA-related attributes which are added to existing MOCs,
however, will be accepted but ignored.
After having successfully created the HSDPA-related MOCs but disabled the HSDPA
feature later on, the configured states will be kept. The RNC therefore checks the
HSDPA flag with cell activation to confirm whether or not HSDPA service is provided
for the cell. If the flag indicates that HSDPA is not supported, the setup of HSDPA in the
Node B will be skipped. When activating a cell in a Node B, it must be kept in mind that
HSDPA operation is only possible on one carrier frequency per Node B and that only
symmetrical HSDPA configurations in all radio cells on the same carrier frequency are
allowed in UMR5.0.
Furthermore, the download procedure will fail if HSDPA-related MOCs are included in
this procedure.
5.1.2
Node B
With respect to the HSDPA-capable Node B, this section describes the OAM modifications in terms of:
Equipment Management
Transport Network Layer Management
Radio Network Layer Management
Optional Feature Handling Within the Node B
5.1.2.1
Equipment Management
If the Node B is supposed to support HSDPA, an HSDPA-capable channel coding card
(CHC) must be installed. The following two options exist:
Reuse/installation of the CHC96 with a SW load updated for HSDPA
Installation of the new hs-CHC
Although both types of CHCs can coexist within one Node B, it must be mentioned that
HSDPA traffic can be processed by either the CHC96 or the hs-CHC exclusively as soon
as both types are installed. As regards Node Bs remote inventory management, the
new hs-CHC represents an ob-RIU object.
The Node Bs initial trigger to set up HSDPA operation is the configuration of the localCellE managed object instances (MOIs) in the database, thus either enabling or disabling HSDPA for a particular UTRAN cell. At system start-up, the Node B then evaluates
each instances current configuration and triggers the setup of an HSDPA-capable CHC
in HSDPA mode according to the rules listed below. This implementation avoids timeconsuming and complex reconfiguration of CHCs because the Node B already knows
at start-up time how many cells support HSDPA and no HSDPA-related or Rel 99 traffic
must be shifted to other CHCs.
1. The Node B always sets up an hs-CHC in HSDPA mode if such a type of card is installed.
2. If no such hs-CHC is installed but if a HSDPA-capable CHC96 is installed, the
Node B sets up the CHC96 in HSDPA mode.
3. Otherwise, if neither an hs-CHC nor an HSDPA-capable CHC96 is installed, the
Node B will reject any HSDPA setup request by means of an NBAP: PHYSICAL
132
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
SHARED CHANNEL RECONFIGURATION FAILURE message containing the appropriate probable cause information.
NOTE
The number of HSDPA-capable CHCs in HSDPA mode the Node B sets up is equal to
the number of localCellE MOIs with HSDPA support enabled.
Only at start-up time and at the first installation of an HSDPA-capable CHC, the Node B
determines the type of CHC to be used for HSDPA operation. The CHC type selected
for HSDPA processing is then kept until the next restart of the Node B.
Furthermore, the Node B checks whether the number of codes signaled in the NBAP:
PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message is equal to
the number of codes being allocated to cells already configured in HSDPA mode. Here,
the principle of symmetrical distribution of codes to HSDPA cells must be observed.
However, if this condition is not observed, the Node B will reject the HSDPA setup by
means of an NBAP: PHYSICAL SHARED CHANNEL RECONFIGURATION FAILURE
message containing proper probable cause information. The distribution of HSDPA cells
on available HSDPA-capable CHCs is performed in a kind of round-robin manner, thus
resulting in HSDPA cells being evenly distributed on the appropriate CHCs. This functionality is currently implemented for Rel 99 cells, as well. An example is provided in
table 3.2 on page 31.
Due to the new and changed HW for supporting HSDPA, the N2CH MOC representing
all CHCs has been adapted as follows:
The existing attribute chType notifying the type of CHC being used has been extended by a new value which indicates the hs-CHC.
A new attribute has been added to this MOC indicating the cell IDs of those HSDPA
cells served by the HSDPA-capable CHC.
State management
The following applies for an HSDPA-capable CHCs state management with regard to
implementation-specific and logical OAM:
Implementation-specific OAM
In general, the locking or shutting down of an HSDPA-capable CHC currently providing HSDPA service is only possible if no cell(s) will go down or be affected. In other words, no common channel may reside on that CHC. As a consequence, a
request to lock or shut down a CHC operating in HSDPA mode is rejected as long
as any superior cell has not been deleted in advance. Cell deactivation, on the other
hand, requires all common channels to be removed from the relevant CHC in advance.
Upon acceptance of a request to lock or shut down the CHC, Rel 99 traffic running
on the affected HSDPA-capable CHC will be shifted to other CHCs as far as possible according to the current implementation. HSDPA calls, however, will be lost because no call context migration of HSDPA calls exists in UMR5.0.
Logical OAM
In this context, the state management function treats the physical shared channel
which is used by HSDPA traffic in the same way as a dedicated channel for Rel 99
traffic. Although the physical shared channel is considered as a common resource
from 3GPPs point of view, call context migration is not supported.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
133
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Fault management
If a failure occurs in an HSDPA-capable CHC, thus leading to a situation in which no
HSDPA-traffic processing is possible, the Node B issues an NBAP: Resource Status Indication (RSI) to the controlling RNC (CRNC). This RSI indicates the loss of the HSDPA
service for that specific HSDPA cell.
This RSI results in the HS-DSCHs combination of operational state/availability status
(OST/AVS) being set to disabled/failed. The affected cells OST/AVS combination is
set to enabled/degraded. As a consequence, all HSDPA radio links will be dropped and
the RNC sends an NBAP radio link failure indication for each radio link.
5.1.2.2
5.1.2.3
5.1.2.4
134
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
1/1/1 configuration
Each of the three localCellE MOs has to be equipped with exactly one HSDPA data
throughput license. Therefore, the peak data throughput in each cell is 2.4 Mbit/s.
During operation, the Node B confirms that this peak data throughput is not exceeded.
Therefore, the Node B recalculates the possible peak data throughput depending on the
HSDPA configuration at each NBAP: Physical Shared Channel Reconfiguration procedure. The calculation is performed according to the following algorithm:
peakDataThrough
=
putNodeB
numberOf
Codes ( i )
i=1
modulation
0.48 Mbit s
Scheme ( i )
where
A
Indicates the number of configured LocalCellE objects in the Node B
numberOfCodes(i)
Indicates the number codes in cell i which are allocated by the RNC during the
NBAP: Physical Shared Channel Reconfiguration procedure
modulationScheme(i)
Specifies the modulation scheme (HSDPA configuration) applied in cell i. This factors values indicate the following:
0: HSDPA processing in cell i is disabled
1: HSDPA processing in cell i is enabled, using only QPSK
2: HSDPA processing in cell i is enabled, using 16QAM and QPSK
If the calculated possible peak data throughput exceeds the licensed peak data throughput, i.e. if peakDataThroughputNodeB > peakDataThroughputNodeB, the Node B will reject the NBAP: Physical Shared Channel Reconfiguration procedure with the cause set
to Not Enough User Plane Processing Resources.
The update of an HSDPA data throughput license of a CC at runtime becomes effective
without a system restart. In the event of CC redundancy, the higher license value becomes effective after a license update of one of the CCs.
5.2
Functional Split
The functional split for UTRAN OAM is not applicable. With regard to the RNC, the
Node B, HSDPA mobility, the transport network layer, the Uu interface, and the HSDPA
performance measurement counters, the relevant functional splits are described in the
corresponding chapters:
Modifications in the RNC HW/SW Architecture
Modifications in the Node B HW/SW Architecture
HSDPA Mobility
Transport Network Layer (TNL) Modifications
Air Interface (Uu) Modifications
HSDPA Performance Measurement Counters
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
135
Support of HSDPA
FD012249 - UMR5.0
5.3
i
Feature Description
Radio Subsystem
Man-Machine Interface
NOTE
The command lines, GUI windows, and MOC names provided below are only assumptions, as their syntax is subject to change.
Both the RC and the LMTs support the changes in the network elements (NEs) information models and databases, i.e. of the RNC and the Node B. Thus, the new MOCs
including their attributes are displayed at the graphical user interfaces (GUIs); the new
or modified commands and parameters are supported by the command line interfaces
(CLIs).
Furthermore, the OAM tool set (OTS) is affected by the changes of the NEs information
models and databases for HSDPA compliancy.
5.3.1
136
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
The new and modified HSDPA-related performance measurement counters for the
Node B, which are described in the chapter "HSDPA Performance Measurement
Counters" on page 157, are furthermore supported by the RC.
5.3.2
5.3.2.1
hsrrm
hsrc
Tab. 5.4
Operation
Sub-item
Description
cre
del
mod
view
view
st
cre
del
mod
view
cre
del
view
hsdpa
The new CLI hsdpa command has been introduced to set, modify, and control the parameters of the HSDPA channel (HS-DSCH). The HSDPA channel must be configured
for each cell in which the HSDPA feature is to be operated. Tab. 5.5 lists the parameters
of the HSDPA channel which can be controlled by the CLI hsdpa command.
Of course, all parameters are new.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
137
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Parameter name
Default value
Parameter description
cellid
not applicable
Cell identifier
nodebid
not applicable
Node B identifier
no_pdsch
not applicable
no_scch
not applicable
po_dsch
Tab. 5.5
The related UTRAN cell must first be deactivated whenever the data of one channel is
to be changed by means of the cre, del, or mod operation. The view operation does not
only show the settings/data of the specific HSDPA channel but its state.
If a downlink common channel (DLCC; dlcc CLI command or Downlink Common Channel GUI window) with ccho_type=0 or ccho_type=1 exists, the combination of
no_pdsch=15 and no_scch=4 is not allowed for the hsdpa CLI command.
With regard to configuration alignment, the relevant configuration data is included in the
configuration alignment file.
NOTE
The HSDPA channel is subordinated to the associated UTRAN cell. Therefore, if the cell
is deleted, the HS-DSCH will automatically be deleted, too.
hsrrm
The new hsrrm CLI command controls the radio resource data for each UE category. In
UMR5.0, UE categories 1 to 6, 11, and 12 are supported. Additionally, HSDPA calls for
UEs of categories 7, 8, 9, and 10 are set up on the HS-DSCH with a performance equal
to or better than that of UE category 6.
The HSDPA radio resources must be configured whenever HSDPA is to be started. For
this reason, the hsrrm-related parameters as provided in Tab. 5.6 are introduced with
UMR5.0. All parameters are new.
Parameter name
Parameter description
ue_cate
not applicable
cqi_cyclek
cqi_rep
ack_nack_rep
cqi_po
ack_po
nack_po
Tab. 5.6
138
Default value
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Parameter name
hsscch_po
Tab. 5.6
Default value
3
Parameter description
HS-SCCH power offset
With regard to configuration alignment, the relevant configuration data is included in the
configuration alignment file.
hsrc
The new hsrc command controls the RAB combination control data. Tab. 5.7 lists the
hsrc-related parameters, which are all new.
Parameter name
Default value
Parameter description
rab1
psib
ul_rate1
64 kbit/s,
384 kbit/s
Tab. 5.7
With regard to configuration alignment, the relevant configuration data is only included
in the config_file_all file if the all-alignment is performed by means of the view align dk
command.
5.3.2.2
Default value
Parameter description
hyst1d
tmtrg1d
640
Tab. 5.8
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
139
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
With regard to configuration alignment, the relevant configuration data is included in the
configuration alignment file.
rbc
The timer for channel-type switching (CTS) from HS-DSCH to FACH has been added to
the rbc-related parameters. For details, see Tab. 5.9.
Parameter name
thsdsch_fach
Tab. 5.9
Default value
30
Parameter description
Timer for the switch from HS-DSCH to FACH
With regard to configuration alignment, the relevant configuration data is included in the
configuration alignment file.
dlcc
From the code allocation point of view, the dlcc command cannot specify either the
ccho_type=0 or ccho_type=1 when the hsdpa command configures the allocated
number of HS-PDSCH channelization codes and the allocated number of HS-SCCH
channelization codes according to the following pattern:
[Number of HS-PDSCH] = 15
[Number of HS-SCCH] = 4
For this situation, therefore, a new error number has been defined for the dlcc command.
With regard to configuration alignment, this command is not influenced because no parameter is changed. The relevant configuration data is therefore included in the configuration alignment file.
cell adc
Due to the introduction of the HSDPA feature, the existing cell adc command has been
enhanced with parameters to supervise the UTRAN cells admission control for HSDPA
calls. Tab. 5.10 provides the relevant information.
Parameter name
Default value
Parameter description
minsf_hsdpa
actrc_hsdpa
Tab. 5.10
With regard to configuration alignment, the relevant configuration data is included in the
configuration alignment file.
eqp
With regard to the new hardware (HSDST and HSPRLC), new parameters have been
added to the eqp command to configure both cards.
140
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
The following operations of the eqp command have been enhanced with parameters for
HSDST and HSPRLC:
cre eqp (Eqiupment)
del eqp (Equipment)
dgt eqp (Diagnosis)
rst eqp (SP Reset)
dload eqp (Firmware Downlaod)
view eqp (Firmware Download)
ulock eqp (Administrative State Control)
lock eqp (Administrative State Control)
Tab. 5.11 provides the parameters related to the new hardware.
Parameter name
Parameter description
hsdpsijkl
hprlcijklm
Tab. 5.11
bldp d2
With regard to the new hardware (HSDST and HSPRLC), new parameters have been
added to the bldp d2 command to configure both cards physical location data (D2 data).
Tab. 5.12 provides the parameters related to the new hardware.
Parameter name
Parameter description
hsdpsijkl
hprlcijklm
Tab. 5.12
atrk
With regard to the new hardware (HSDST and HSPRLC), new parameters have been
added to the atrk command to handle the traffic the RNC automatically configures on
these cards.
Tab. 5.12 provides the parameters related to the new hardware.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
141
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Parameter name
hsdpsijkl
hprlcijklm
Tab. 5.13
5.3.2.3
Parameter description
5.3.2.4
Affected object
Hsdps
0053268 cmuxbl_fault
0053269 cmuxbl_fault_recovery
Tab. 5.14
142
Hprlc
Hsdpa
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Affected object
Hsdps
Hprlc
1152001 state_of_device_changed
1293001 ast_changed_notifcation
Hsdpa
1329100 nbap_failure
1348004 card_block_complete
1348005 card_unblock_complete
1348006 card_reserved_to_be_blocked
1348012 trunk_card_congestion_occurred
1348013 trunk_card_congestion_recovered
Tab. 5.14
5.3.3
NOTE
The following attribute names are mere proposals but not yet fixed!
Ch
Tab. 5.15 lists the new and modified attributes related to the Ch MOC. The operator
has read-only access to these attributes.
Attribute name
Value range
Attribute description
assignedHsdpaCells
not applicable
chType
[0;2]
Granularity: 1
Tab. 5.15
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
143
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
LocalCellE
Tab. 5.16 lists the new attributes related to the LocalCellE MOC. These attributes can
be configured by the operator.
Attribute name
Attribute description
hsdpaCapable
[0;1]
Granularity: 1
hsdpaModulation
[0;1]
Granularity: 1
hsdpaScheduler
[0;1]
Granularity: 1
Tab. 5.16
5.3.4
Value range
5.3.4.1
144
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
5.3.4.2
Support of HSDPA
FD012249 - UMR5.0
5.3.4.3
Consistency Checks
The OTS is extended by a consistency check confirming that the Node Bs CallProc
MOC uses only those frequency layers for which HSDPA capability is activated. When
using HSDPA, a Node B with a 1/1/1 configuration, for example, is not allowed to use
frequency layer 2.
Another check confirms that the configuration of HSDPA in the RNC and the Node B is
consistent. This consistency check indicates HSDPA channels created in the RNC for
UTRAN cells which do not support HSDPA (hsdpaSupport = 0). On the other hand, it is
permissible to have no HSDPA channels configured in UTRAN cells with HSDPA support (hsdpaSupport = 1).
Third, it is confirmed that the number of channelization codes used per HSDPA channel
is identical throughout the whole Node B. The principle of symmetric distribution of
channelization codes on all cells is thus kept.
5.3.4.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
145
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
interfaces are equivalent to those for the south-bound export operations mentioned
above.
5.4
NOTE
Although the support of HSDPA and the applied modulation scheme have to
be configured in the Node B, this is not modeled at the MCCM interface.
The RNPC interface is extended by a new class representing the HSDPA channel.
This class models the following attributes:
Number-of-HS-PDSCH-codes
MaxNrOfHSSCCHs
146
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Functional Description
HSDPA provides for higher data throughput per UE and per cell. In comparison to Release 99, HSDPA
allows user throughput of more than 384 kbit/s
increases the maximum cell data throughput from 1 Mbit/s to a theoretical maximum
of 13.98 Mbit/s
Such increased data rates require either E1/J1/T1 IMA groups or STM-1/OC-3 lines for
the Iub interface. The maximum throughput is only achievable using STM-1/OC-3 lines.
Using IMA, the cell data throughput is limited to some 12 Mbit/s. On the Iub interface,
HSDPA data is carried through the same AAL2 user plane VCs as is conventional
Rel 99 traffic. On the Iu interface, HSDPA data uses the same AAL5 user plane VCs as
conventional user plane traffic. HSDPA is not supported over Iur.
HSDPA is used for interactive and background traffic classes. This traffic is expected to
exhibit pronounced bursts that might use an Iub interface to full capacity. A flow control
mechanism (see below) in combination with QoS differentiation is introduced to allow for
maximum Iub usage while at the same time providing that HSDPA traffic does not interfere with Rel 99 traffic. In the event of congestion, HSDPA traffic is discarded first.
HSDPA is carried on the same ATM AAL2 VCs as is conventional traffic. Therefore, on
the transport network layer there are no configuration changes for HSDPA in comparison to conventional Release 99 networks. However, because of the increased bandwidth requirements and the limited number range of call identifiers (see below) inside an
AAL2 VC, it is necessary to configure more AAL2 user plane VCs on the Iub interface.
AAL2 user plane VCs can be shared between several calls. To facilitate this, the VC carries several AAL2 links which each are associated with an individual call. AAL2 links are
identified by their CID (call identifier) that is transported as an additional header byte of
an ATM cell.
Each HSDPA user requires 3 CIDs to be allocated, which are used for UL DTCH (ADCH), DCCH, and HS-DSCH. Thus, HSDPA support adds the requirement for 1 additional CID to each call. If there are 64 HSDPA users to a radio cell, and 3 radio cells to
a Node B, the CID requirements add up to 576 CIDs per Node B. Since the CID is an 8
bit number (ranging from 0 to 255; not all values are available for usage), at least 3 AAL2
VCs must be allocated just to provide enough CIDs for a fully equipped HSDPA capable
Node B.
6.1.1
Flow Control
With regard to HSDPA, it is not the RNC but the Node B that controls the transfer rate
on Iub. This transfer rate is adjusted to the transfer rate that is achieved on the air interface, Uu. For each HSDPA UE, the Node B maintains a buffer (priority queue) that
stores the HSDPA user data until it is transmitted over the Uu interface. The Node B requests data from the RNC using the credit-based flow control mechanism of 3GPP
TS25.435, Iub Interface User Plane Protocols for COMMON TRANSPORT CHANNEL
Data Streams. By requesting more or fewer data packets from the RNC, this buffer is
kept at a filling level between an upper and a lower boundary. Among other factors, the
net Uu transfer rate depends on radio interference and the number of retransmissions.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
147
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Refilling the priority queues is subject to the availability of bandwidth on the Iub interface:
if conventional traffic does not leave enough bandwidth, HSDPA buffers may temporarily go empty. This is an intentional behavior since HSDPA data is of the interactive and
background traffic type and conventional traffic always takes precedence over it.
Flow control for a certain queue is activated during the NBAP: RL Setup Procedure, or
if the Node B receives an HS-DSCH Capacity Request control message from RNC.
For each HS-DSCH Capacity Request message the Node B responds with a HS-DSCH
Capacity Allocation message. This message contains information elements (Credits, Interval, Repetition Period) which can be interpreted by the RNC as an offer regarding
data rates or data packets.
After the first capacity allocation, the HS-DSCH MAC-d flow control is mainly driven by
the filling level of the Node B HS-DSCH priority queues. Depending on that filling level,
the Node B sends further adequate HS-DSCH capacity allocation message to the RNC.
6.1.1.1
6.1.2
QoS Mechanism
Within the RNC, QoS differentiation is performed on the AAL2 level. The assigned priorities are:
highest
low
lowest
These assignments make sure that HSDPA traffic has least priority.
148
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
6.2
Support of HSDPA
FD012249 - UMR5.0
Functional Split
The changes on the transport network layer with regard to HSDPA impact on both the
RNC and the Node B. For more information, refer to "Interworking Between RNC and
Node B" on page 37.
6.3
Man-Machine Interface
The RNC atrk HMI command (ATRK Interface GUI window) serves to view, block and
unblock traffic that the RNC itself (rather than the operator) assigns to its hardware resources. This command has been expanded to also offer parameters related to the traffic that is automatically assigned to HSDST and HSPRLC cards.
The new hardware also introduces the following new HMI output messages:
0053299 hsdps_fault
0053300 hsdps_fault_recovery
The existing alarms
0053268 cmuxbl_fault
0053269 cmuxbl_fault_recovery
1348012 trunk_card_congestion_occurred
1348013 trunk_card_congestion_recovered
are modified to also cover faults in the HSPRLC hardware. For details see "Fault management".
6.4
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
149
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
7.1
Functional Description
The UMTS air interface (i.e. Uu interface) is the radio interface between the UMTS terrestrial radio access network (UTRAN) and the user equipment (UE). The Uu interface
comprises the control plane (C-plane) for signaling and the user plane (U-plane) for the
transfer of user data. The Uu interface consists of three protocol layers:
Physical layer (L1/PHY)
Data link layer (L2)
The data link layer is divided into sublayers:
Medium Access Control Protocol (L2/MAC)
Radio Link Control Protocol (L2/RLC)
Broadcast/Multicast Control Protocol (L2/BMC)
Packet Data Convergence Protocol (L2/PDCP)
Network layer (L3)
The radio resource control protocol (L3/RRC) is the only element of the network layer.
Fig. 7.1 provides an overview of the Uu interfaces protocol architecture. Service access
points are marked as ellipses.
150
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
C-plane signaling
U-plane information
GC
Nt
DC
Duplication avoidance
GC
Nt
DC
UuS boundary
control
L3
PDCP
control
control
control
control
RRC
PDCP
L2/PDCP
BMC
RLC
RLC
RLC
RLC
RLC
RLC
RLC
L2/BMC
RLC
L2/RLC
Logical Channels
MAC
L2/MAC
Transport Channels
PHY
Fig. 7.1
L1
The 3GPP Release 5 (Rel 5) RNC is able to interoperate with a UE of Rel 99, Rel 4, and
Rel 5 via the Uu interface.
To support HSDPA, minimum changes are required in the UTRAN for compliancy to the
Rel 5 version of protocols at the Uu interface. These changes impact on Uu layer 1 (L1),
layer 2 (L2), and layer 3 (L3).
7.1.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
151
Support of HSDPA
FD012249 - UMR5.0
7.1.2
Feature Description
Radio Subsystem
7.1.3
7.1.3.1
152
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
(UL) and downlink (DL) messages, whereas critical extensions can only be applied in
DL direction. These two kinds of message extensions are processed as follows:
Non-critical extensions
In general, the receiver processes messages including non-critical extensions which
are not comprehended as if these extensions were absent.
The sending of messages containing non-critical extensions is performed by adding
a non-critical extension container at the end of a release-specific message. Thus,
such messages consist of two parts - the actual message and a non-critical extension. Both parts are release-specific.
Critical extensions
When receiving a message including a critical extension which is not comprehended, the receiver will entirely reject this message and inform the sender about the rejection. A partial rejection of messages is not possible.
To send messages with critical extensions, a new version of the message has to be
defined. The newly defined version is indicated at the beginning of the message.
Here, again, the message structures of the different releases (Rel 99, Rel 4, and
Rel 5) are distinguished.
Due to the introduction of 3GPP Rel 5-compliant critical and non-critical message extensions, enhanced functionalities are required for the RNCs Rel 5 RRC decoder and encoder:
Rel 5 RRC decoder
The Rel 5 decoder is able to comprehend Rel 99, Rel 4, and Rel 5 UL messages including all non-critical extensions introduced up to Rel 5. The decoded messages
will then be sent to the RNC application.
Rel 5 RRC encoder
RNCs Rel 5 RRC encoder must take care of the UEs release in order to use the
appropriate message structure and include only those critical and non-critical extensions supported by the relevant release. Thus, the inclusion of protocol extensions
from releases later than the UEs release is prevented.
In UMR5.0, all HSDPA-related messages are encoded with a Rel 5 structure. The
following messages are affected:
CELL UPDATE CONFIRM
RADIO BEARER SETUP
RADIO BEARER RELEASE
RADIO BEARER RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
MEASUREMENT CONTROL (Rel 4 structure with Rel 5 non-critical extensions)
7.1.3.2
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
153
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
If a UE supports 3GPP Rel 99 or Rel 4, the RNC treats this UE as if it was of Rel 99.
Therefore, Rel 4/5 features and/or message structures including critical extensions are
not used. On the other hand, if a UE supports Rel 5, the RNC applies Rel 5 message
154
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
structures to only those messages containing HSDPA-related IEs. Other messages are
of Rel 99 structure. The following messages may contain HSDPA-related IEs:
CELL UPDATE CONFIRM
SRNC relocation on FACH and re-establishment on FACH
RADIO BEARER SETUP
RAB setup from FACH/DCH to HS-DSCH and from HS-DSCH to DCH
RADIO BEARER RELEASE
RAB release from HS-DSCH to DCH
RADIO BEARER RECONFIGURATION
Setup or release of a second PS BE RAB
TRANSPORT CHANNEL RECONFIGURATION
Channel-type switching (CTS) from FACH to HS-DSCH
MEASUREMENT CONTROL
Setup of event 1D
7.1.3.3
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
155
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
tive RLs in non-diversity cells (individual RL mode NONE) in Rel 99, this change simply
means a clarification of the UEs behavior.
i
7.1.3.4
NOTE
In UMR5.0, Node Bs are not capable of providing Tx diversity for HSDPA cells.
7.2
Functional Split
Not applicable.
7.3
Man-Machine Interface
Not applicable.
7.4
156
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
Functional Description
Tab. 8.1 shows the performance measurement counters that are newly introduced by
support of HSDPA. Modifications to existing scanners are listed in Tab. 8.2 and below
this table.
The mtype values are used to configure performance measurements at the CLI interface of the LMT-RNC.
The Shortname values are used to configure performance measurements at the CLI interface of the Radio Commander.
Measurement
mtype
Shortname
Purpose
hsEstabAtt
101
hsEstabFail
Tab. 8.1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
157
Support of HSDPA
FD012249 - UMR5.0
Measurement
Feature Description
Radio Subsystem
mtype
Shortname
Purpose
72
hsprlcAllocAtt
Number of successful
HSPRLC allocations
73
hsprlcAllocSucc
hsdstAllocAtt
Number of successful
HSDST allocations
75
hsdstAllocSucc
192
hsprlcThrou
ghputRate
This measurement indicates the used channels/bandwidth on HSPRLC and PRLC, given as a percentage of
the maximum performance. Thus, it indicates the RNC
hardware utilization by HSDPA service. Several subcounters are defined for average and maximum values
for UL and DL direction.
193
hsdstThroughputRate
135
hsTranstoFachAtt
hsTranstoFachFail
137
hsTransFromFachAtt
hsTransFromFachFail
RAB assignment
Number of unsuccessful radio bearer reconfigurations
per failure cause
92
158
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Measurement
Support of HSDPA
FD012249 - UMR5.0
mtype
Shortname
Purpose
hsCellThroughput
The HSDPA cell throughput records the number of MAChs PDU bits including MAC-hs header.
The cell throughput is measured every 10 seconds in
kbit/s. At the end of the granularity period, the mean, minimum, and maximum values are provided.
hsNackRatio
This counter serves for monitoring the system performance and validation of HS-PDSCH/HS-SCCH power control mechanism.
The measurements records contain the sum of all not acknowledged data transmissions (including re-transmission). These are compared to the number of all TX
attempts. The HARQ NACK ratio is measured every 10
second. At the end of the granularity period, the mean,
minimum and maximum values are provided.
Tab. 8.1
Shows the mean and maximum base band load for HSDPA resources per cell during the complete granularity period.
This counter informs about HSDPA resources, in addition
to the existing base band (BB) usage ratio counters. The
BB usage ratio reflects the utilized resources per NodeB
with regard to the licensed resources, whereas the BB
usage ratio for HSDPA is related to the UL resources per
HSDPA capable CHC cards not based on the license information. For all cells configured on the same HSDPA
capable CHC card, the same values are provided.
Measurement
mtype
Shortname
99
uuTransmCarrierPwr
Modification
UE quantity measurements
Transmitted carrier power
Tab. 8.2
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
159
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
Measurement
Mean number of bearer services per cell related
Tab. 8.2
mtype
Shortname
Modification
152
8.2
Functional Split
PM counters operate in the network element. They are set up by the OMC or the LMTRNC / LMT-NB. The measurement result files can be uploaded to the LMT or the OMC.
From there, they can be transferred to the OTS for further processing.
8.3
Man-Machine Interface
The new performance counters are configured using the existing commands and GUI
windows on the LMT-RNC or the LMT-NB and the OMC.
8.4
160
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
9 Operating HSDPA
Not yet applicable.
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
161
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
10 Abbreviations
16QAM
3GPP
AAL2
AAL5
AC
ACK
AGC
ALCAP
ALS
AMR
AMREQ
ARQ
AST
ATM
AVS
BB
BE
BLSC
BMC
BRA
CAC
CAPEX
CAT
CC
CCH
CE
CHC
CID
CIR
CLI
CmCH-PI
CMP
CMUX
CN
CQE
CQI
CRC
cRNC
CRNC
CS
CTS
DBMS
DCCH
DCH
DHT
162
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
DL
DLCC
DPCCH
DRIC
DRNC
DSCP
DSL
DSP
DTCH
DUAMCO
E1
eRNC
ETSI
FACH
FP
FW
GMUX
GTP
GPRS
GUI
HARQ
HCS
HMI
HMO
hs-CHC
HSDPA
HS-DPCCH
HS-DSCH
HS-DSCH FP
HSDST
HS-PDSCH
HSPRLC
HS-SCCH
HW
I/B
ID
IDF
IE
IMA
IP
ISO
ITU
Iu
Iub
Iur
J1
L1
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Downlink
Downlink Common Channel
Dedicated Physical Control Channel
Digital Radio Interface Card
Drift Radio Network Controller
Differentiated Services Code Point
Digital Subscriber Line
Digital Signal Processor
Dedicated Traffic Channel
Duplexer Amplifier Multicoupler
European Plesiochronous Digital Hierarchy Signal Level 1
RNC with Enhanced Capacity and Connectivity
European Telecommunications Standards Institute
Forward Access Channel
Frame Protocol
Firmware
GTP Multiplexer
GPRS Tunneling Protocol
General Packet Radio Service
Graphical User Interface
Hybrid Automatic Repeat Request
Hierarchical Cell Structure
Human-Machine Interface
Hardware Managed Object
Highspeed Channel Coding Card
Highspeed Downlink Packet Access
Highspeed Dedicated Physical Control Channel
Highspeed Downlink Shared Channel
Highspeed Downlink Shared Channel Frame Protocol
Highspeed Downlink Shared Channel Trunk
Highspeed Physical Downlink Shared Channel
Highspeed Packet Radio Link Controller
Highspeed Shared Control Channel
Hardware
Interactive/Background (radio access bearer)
Identifier
Inventory Data File
Information Element
Inverse Multiplexing for Asynchronous Transfer Mode
Internet Protocol
International Standard Organization
International Telecommunications Union
Interface between an RNC and the Core Network
Interface between an RNC and a Node B
Interface between two RNCs
Japanese Plesiochronous Digital Hierarchy Signal Level 1
Layer 1
163
Support of HSDPA
FD012249 - UMR5.0
Feature Description
Radio Subsystem
L2
L3
LI
LMT
LPA
LSM
MAC
MAC-d
MAC-hs
MMI
MOI
MOC
NACK
NBAP
OAM
OC-3
OMC
OSI
OST
OTS
P-CPICH
PDCP
PDU
PM
PRLC
PRM
PRS
PS
PSCR
QoS
QPSK
QRS
RAB
RACH
RAT
RB
RC
Rel 4
Rel 5
Rel 99
REP
RF
RL
RLC
RNC
RNC-BE
RNC-FE
164
Layer 2
Layer 3
Length Indicator
Local Maintenance Terminal
Linear Power Amplifier
Line Switch Module
Medium Access Control
Medium Access Control - Dedicated
Medium Access Control - High Speed
Man-Machine Interface
Managed Object Instance
Managed Object Class
Not Acknowledged (message)
Node B Application Part
Operation and Maintenance
Optical Carrier Level 3
Operation and Maintenance Center
Open System Interconnect
Operational State
Operation and Maintenance Tool Set
Primary Common Pilot Channel
Packet Data Convergence Protocol
Protocol Data Unit
Performance Measurement
Packet Radio Link Controller
Packet Radio Link Control Module
Procedural State
Packet-Switched
Physical Shared Channel Reconfiguration
Quality of Service
Quadrature Phase Shift Keying
Quality Requirement Specification
Radio Access Bearer
Random Access Channel
Radio Access Technology
Radio Bearer
Radio Commander
3GPP Release 4
3GPP Release 5
3GPP Release 99
Repeater
Radio Frequency
Radio Link
Radio Link Control
Radio Network Controller
Radio Network Controller - Back End
Radio Network Controller - Front End
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
Feature Description
Radio Subsystem
Support of HSDPA
FD012249 - UMR5.0
RNL
RNS
RNTI
RRC
RRH
RRM
RSI
RTWP
SBS
S-CPICH
SDU
SF
SIR
SN
SRB
SRB2
SRNC
SRNS
STM-1
STTD
SW
T1
TB
TINF
TNL
TOS
TRNC
TRX
TTI
UDP
UE
UL
UM
UMR
UMTS
UTOPIA
UTRAN
Uu
VC
VCI
VP
VPI
WCMP
WLAN
WLSC
Siemens AG:
A50016-G5000-Z180-3-7618
NEC Corporation:
ND-59083-180(E)-03
165