Utran Overview

UTRAN overview Siemens/NEC
UTRAN overview
Contents
1 GSM evolution to UMTS 4
2 IMT 2000 6
3 GSM & UMTS Releases 8
4 Harmonization of the RTTs 10
5 TD-SCDMA 12
6 3G frequency spectrum 14
7 The CDMA principle 16
7.1 CDMA types 18
7.2 Advantages of CDMA 20
8 Transmission principles 22
8.1 Duplex transmission: FDD & TDD 24
8.2 Multiplex methods 26
9 UMTS-two different modes 28
9.1 Variation in data rate 30
9.2 Asymmetric allocation of frequency resources 30
9.3 FDD uplink and downlink data rates 32
10 WCDMA 35
10.1 QPSK modulation 38
10.2 Spreading and scrambling 40
10.3 Tasks of the Codes 46
10.4 Structure of channelization codes 48
10.5 Structure of scrambling codes 48
11 UTRAN timing structures 50
12 Logical, transport & physical channels 53
12.1 Channel mapping DL 56
12.2 Channel mapping UL 58
13 UTRAN functional description 61
13.1 Power control 62
13.2 RAKE receiver 70
MN3500EU50MN_0001
1
© 2002 Siemens AG / NEC Corporation
Siemens/NEC UTRAN overview
13.3 Multi User Detection (MUD) 72

13.4 Handover 74
13.5 HSDPA - High Speed Downlink Packet Access 84
14 Functionality of the network entities 87
14.1 User equipment 88
14.2 Node B 92
14.3 RNC 94
14.4 Core network 96
2 MN3500EU50MN_0001
MN3500EU50MN_0001
3
1 GSM evolution to UMTS

In Phases 1 and 2 GSM allows data transfers at rates of only 0.3 to 9.6 kbit/s. Three
different principles are introduced in GSM Phase 2+ for increasing the data rate:
HSCSD, GPRS and EDGE.
HSCSD: High Speed Circuit Switched Data

HSCSD in theory allows up to 8 physical channels of a carrier to be bundled together
(multilinking) to a single subscriber. In practice, however, only up to 4 channels are
bundled together. The maximum transfer rate per physical channel was increased
from 9.6 kbit/s to 14.4 kbit/s with the introduction of a new codec. As a result, up to
57.6 kbit/s can be reached (or theoretically, 115.2 kbit/s). HSCSD, like conventional
GSM, only transfers circuit-switched (CD) data. Only minor modifications to the GSM
network are required to introduce HSCSD.
GPRS: General Packet Radio Services

GPRS also allows bundling (multilinking) of up to 8 physical channels to a subscriber.
Four new coding methods enable transfers at rates of 9.05 /13.4 / 15.6 / 21.4 kbit/s
per physical channel. GPRS introduces packet-switched (PS) data transmission,
which allows efficient use of resources and direct access to packet data networks
(PDN). New network elements and protocols are being introduced that will pave the
way for UMTS. GPRS is therefore of major importance for launching UMTS.
EDGE: Enhanced Data Rate for the GSM Evolution

EDGE introduces a new modulation method over the radio interface –8PSK (8-Phase
Shift Keying). In theory, this allows transfer rates three times faster than those for the
conventional GSM modulation method, GMSK (Gaussian Minimum Shift Keying). In
this way, EDGE increases the performance of GPRS and HSCSD, and transmission
at up to 69.2 kbit/s per physical channel is achievable. A maximum rate of
553.6 kbit/s is possible with 8 channel multilinking.
UTRA(N): UMTS Terrestrial Radio Access (Network)

Fully new transmission methods (WCDMA, ATM) are used in UMTS for the UTRA
radio access and the UMTS Terrestrial Radio Access Network (UTRAN). New
network elements and a new protocol architecture are needed. The maximum
transmission rate via the radio access will approach 1920 kbit/s.
4 MN3500EU50MN_0001
GSM - UMTS Evolution:

Data rates UTRA:
1920 kbit/s
• HSCSD, GPRS & EDGE: Bundling of 1-8 channels
• HSCSD: Circuit-switched
• GPRS: Packet-switched; new infrastructure
• EDGE: 8PSK instead of GMSK EDGE:
max. data rate
• UMTS: UTRA (WCDMA) New

553 kbit/s
transmission
GPRS: principles
171 kbit/s (WCDMA),
New network network
HSCSD: elements &
No new network
elements &
115 kbit/s elements; only
protocol architecture: protocols
prerequisite modifications to
No new network for UMTS ! the modulation
-
elements; method
GSM SW modifications
Phase 1/2:
4 / (8) x 8x 8 x 69.2 kbit/s
9.6 kbit/s 14.4 kbit/s 21.4 kbit/s
9,6 kbit/s
GSM Phase 2+
HSCSD: High Speed Circuit Switched Data 8PSK: Phase Shift Keying
GPRS: General Paket Radio Services GMSK: Gaussian Minimum Shift Keying
EDGE: Enhanced Data rates for the GSM Evolution UTRA: UMTS Terrestrial Radio Access
Fig. 1 From GSM to UMTS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
5
2 IMT 2000
The 1st and 2nd mobile communication generations are characterized by a variety of
different standards for various applications. Each of the standards has specific
technical attributes, advantages and disadvantages, applications, ranges and costs,
and has been optimized for different subscriber groups. Many of these systems exist
(or existed) solely at regional or national level and are incompatible with each other.
In contrast, in the 3rd generation of mobile communications, a family of compatible
standards is to evolve under the umbrella term IMT-2000. These standards are
intended to guarantee global mobile communications for diverse applications.
The general thinking is to provide customers with requested services regardless of
their location and the prevailing infrastructure.
The IMT-2000 concept devised by the ITU includes the following major aspects:
Global, seamless access to mobile communications systems (using terrestrial
systems and mobile satellite systems – MSS)
• Compatibility between all members of the IMT-2000 family
• Downward-compatibility with the major 2G systems (e.g., GSM, IS-95)
• Convergence between mobile and fixed networks
• High data rates for mobile communications
• Circuit- and packet-switched (CS & PS) transfer of data
• Facilitation of multimedia applications
• Inexpensive, flexible telecommunications access also for developing countries
6 MN3500EU50MN_0001
IMT-2000 Concept
• worldwide, seamless access
(terrestrial systems + MSS’s)
• Compatibility within IMT-2000 family
• Downwards-compatible with 2G
• Fixed Mobile Convergence FMC
• High data rates
• Multimedia applications
• Circuit- and packet-oriented
-
• Inexpensive, flexible access
for developing countries
Fig. 2 IMT 2000
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
7
3 GSM & UMTS Releases

The original plans for GSM in the 1980's included all aspects of a 2G standard. In
1988 it became clear that this was not possible in the specified time frame. For this
reason, GSM was released in a preliminary version in 1990/91 as GSM Phase 1.
GSM Phase 1
Phase 1 contains everything required for the operation of GSM networks. Speech
data transfer is the core focus. Data transfer is defined, too (0.3 - 9.6 kbit/s). Only a
few supplementary services are included.
GSM Phase 2
After Phase 1completion, the GSM Standard was fully revised. Phase 2 includes a
wide range of supplementary services comparable with the ISDN standard.
GSM Phase 2+
Phase 2+ enhances in Annual Releases (`96, `97, `98, `99) the GSM standard and
prepares the UMTS introduction. Especially the GSM Core Network CN is enhanced
to be used as UMTS CN at UMTS start. Major Phase 2+ aspects are IN services,
flexible service definition, packet data transfer, high data rate transmission and
improved voice codes. GSM is limited by the narrowband radio access, the radio
resource efficiency and a lack of additionally available frequency bands.
UMTS Release `99 (also: Release 3)

With GSM Rel. `99, a handshake with the first UMTS Release (Rel.. `99 or Rel. 3)
according to many CN and service aspects is performed. UMTS introduces a new,
broadband radio access optimized for packet data transmission up to 2 Mbit/s.
UMTS Release 4
Unlike GSM Phase 2+, the enhancement of UMTS is not performed in annually
steps. Enhancements should be possible in flexible time schedules. Rel. 4 (late 2001)
introduces e.g. important CN modifications (bearer independent signaling flow) and
the Low Chip Rate LCR TDD mode as a third radio access option.
UMTS Release 5, 6, …
For UMTS Rel. 5 major CN modifications, i.e. the IP Multimedia Subsystem IMS, are
planed. New network elements and protocol structures are defined.
For the future modifications of the UTRAN toward an All IP RAN, enhancements of
the radio resource efficiency, new frequency ranges (WRC'2000) and many more
enhancements toward 4G are expected
8 MN3500EU50MN_0001
GSM& UMTS
GSMLimits:
Evolution • narrow-band radio access
UMTS
• resource efficiency
Capabilities • additional frequency bands
required Release
Release 5
Release 4
GSM 3
Phase
2+
Phase •••
Phase 2 Release
1 Release
‘99
Release ‘98
Release ‘97
‘96
Ph1: TeleServicesTS, new SS, flexible new WCDMA new CN solutions Time
BS max. 9.6 Kbit/s Service Concept Radio Interface (R’4: CS domain
Ph2: Supplementary (CAMEL, MExE,..), (large bandwidth, modification
Services SS (= ISDN) higher data rates Flexible data rates; R’5: IMS);
(HSCSD, GPRS, EDGE) optimized for PS); new RTT options
new network elements new RAN (LCR-TDD)
close to original IMS: IP Multimedia Subsystem
3G plans LCR: Low Chip Rate
RTT: Radio Transmission Technology
Fig. 3 Releases of GSM and UMTS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
9
4 Harmonization of the RTTs

Due to the demand for global compatibility of the IMT-2000 systems and as a result
of the improved chances of the individual proposals, many of the RTT solutions
proposed were harmonized. The harmonization reduced – in particular for the
terrestrial, cellular systems – the number of RTTs during the period from the middle
of 1998 until the end of 1999. The ARIB (W-CDMA) and ETSI (UTRA) proposals
were harmonized and further jointly developed as UTRA FDD and TDD components
(as a GSM successor system). The IS-95 successor system, CDMA2000, and the
UTRA FDD/TDD components were also harmonized. This new IMT-2000 RTT
component referred to now as MC-CDMA (instead of CDMA2000) is for the most part
harmonized with the UTRA TDD and FDD (now also known as DS-CDMA)
components with the result that roaming is possible in theory between the system
components. The Chinese TD-SCDMA proposal has also been retained as an IMT-
2000 component.
At the same time, UWC-136 remains as a step toward optimization of D-AMPS in the
direction of high data rates. UWC-136 is equivalent to EDGE for GSM). Therefore,
EDGE has been renamed to Enhanced Data Rates for the Global Evolution,
consisting of an "EDGE Classic" component (for GSM enhancement) and an "EDGE
Compact" component (for D-AMPS enhancement).
So in general four 3G standards are expected to be more or less important on 3G
market: UMTS (FDD mode and TDD mode), MC-CDMA, EDGE and TD-SCDMA.
Now, having finished 3G standardization (ITU TG8/1 closed in 12/99), further plans
are made to enhance 3G (denominated as 3.5G) and first studies are planed for 4G
development (e.g. in the ITU Working Party WP8F).
10 MN3500EU50MN_0001
IMT-2000 Source: ITU

RTT Harmonization
CDMAII, W-CDMA
CDMA2000 UWC-136
NA: W-CDMA TD-SCDMA
CDMA I DECT June `98
UTRA, WIMS
CDMAFDD TDMA/CDMA TDMA

(Hybrid TDD)
UTRA (FDD) UWC-136
WP-CDMA TD-CDMA DECT March `99
CDMA2000 (UTRA TDD)
TD-SCDMA
Paired: Unpaired:
EDGE UTRATDD December `99
UTRAFDD TD-SCDMA
FDD: Frequency Division Duplex
MC-CDMA
TDD: Time Division Duplex (former 12/99 ITU:
DS-CDMA: Direct Sequence CDMA
CDMA2000) TG 8/1 closed &
MC-CDMA: Multicarrier CDMA
TD-SCDMA: Time-Division Synchronous CDMA WP 8F founded: 3.5G / 4G studies
Fig. 4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
11
5 TD-SCDMA
TD-SCDMA Phase 1 - TSM
TD-SCDMA is introduced in two phases. In phase one the existing GSM Phase 2+
core and access networks is used in big parts. The Core NW remains completely
unchanged. The connection of the TSM RAN to the Core NW is done via the A and
Gb interface.
The TSM PLMN as defined in the CWTS release consists of the following:
• Core Network functional units from GSM Phases 1/2 (MSC, VLR, HLR, AC, EIR)
• GPRS functional units (GGSN & SGSN)
• CAMEL functional units: CSE (gsmSSF & gsmSCF)
• The radio component, TD-SCDMA Terrestrial Radio Access Network.
TD-SCDMA Phase 2 - UTRA TDD LCR (UMTS Phase 1)

The UMTS PLMN as defined in UMTS Rel. ’99 consists of the following:
• Core Network functional units from GSM Phases 1/2 (MSC, VLR, HLR, AC, EIR)
• GPRS functional units (GGSN & SGSN)
• CAMEL functional units: CSE (gsmSSF & gsmSCF)
• The radio component, UMTS Terrestrial Radio Access Network (UTRAN).
Three different UTRA modes are specified
• Time Division Duplex - Low Chip Rate TDD-LCR (TD-SCDMA Phase 2),
• Time Division Duplex - High Chip Rate TDD-HCR,
• Frequency Division Duplex FDD.
UMTS-specific extensions / modifications

The Core Network (CN) needs only minor modifications to introduce UMTS. A
number of protocols need to be extended, for example, to enable transfer of the new
UMTS subscriber profiles. In a similar manner, the corresponding registers have to
be extended. Another modification is the relocation of the transcoding TC function
(for speech compression) in the CN. The TC function is needed together with an
interworking function (IWF) for protocol conversion between the A and Iu interfaces.
12 MN3500EU50MN_0001
UMTS Phase 1 =
GSM Phase 1/2 +
GPRS + CAMEL +
UTRAN
A PSTN
GSM MSC /
A GMSC
BSS IWF/ VLR
ISDN
TC
TSM
CSE EIR HLR AC
TD-SCDMA
Gb
TDD-LCR Iu(CS)
IP
SGSN GGSN G
Gn i
TDD-HCR Iu(PS) X.25
FDD
GSM Phase 2+
Core Network
UTRAN
IWF/TC: Interworking Function / Transcoder
Fig. 5 Network with TD-SCDMA
TD-SCDMA
Phase 1 Phase 1
TSM same air interface TDD LCR
CWTS 3GPP
GSM2+ & CN 3G Core
A, Gb Iu
China Wireless Telecommunication Standardization

low Chip Rate
TDSCDMA@GSM
Fig. 6 TD-SCDMA evolution
MN3500EU50MN_0001
13
6 3G frequency spectrum
A significant disadvantage of mobile communications is the limited availability of
frequency resources. The radio interface can be likened to the eye of a needle for
information transfers. The radio interface in most industrial nations has hardly any
unused gaps in the range from kHz to GHz. A variety of diverse applications (e.g.,
radio, TV, radar, mobile communications, radio relay systems, microwave
applications, etc.) for industrial, military and private use are competing for the
available frequency bands. Licenses are granted at national level.
1G mobile communications systems in Europe were mostly positioned in the
450 MHz and 900 MHz frequency bands. 1G and 2G successor systems in America
and Japan occupy the 800 MHz range. Expansions in Japan were implemented for
the 1500 MHz range and in America for the 1900 MHz range. For GSM, frequency
bands around 900 MHz were reserved for GSM900 and GSM-R, and frequencies
around 1800 MHz for GSM1800 in most European countries and in many non-
European countries (outside America). The 1800 MHz band is available for different
2G systems (including GSM1900) in different American states.
The European 2G cordless standard DECT is used globally in many countries in the
range 1880 – 1900 MHz. The Japanese PHS equivalent used in the South Asian
area uses the range 1895 – 1918 MHz.
Frequencies in the range of 1600 MHz are also available to 2G MSS's. Other MSS
bands are located between 2.5 and 30 GHz.
A recommendation for the national authorities for reserving frequencies for 3G
applications was passed on the initiation of the ITU-R at the World Administrative
Radio Conference in February 1992 (WARC-92). The frequency ranges from 1885 –
2025 MHz and from 2110 – 2200 MHz are to be reserved globally for 3G systems.
They include frequency ranges for MSS's: 1980 - 2010 MHz and 2170 - 2200 MHz.
With the WRC-2000 extensions to be reserved in the coming years at national and
regional levels (e.g., throughout the EU) and which could be offered for licensing, the
expected frequency requirement for mobile communications can be covered up until
about 2010.
14 MN3500EU50MN_0001
3G UL
GSM 1900 UL 3G DL
GSM 1900
GSM GSM GSM 1800 GSM 1800 DL
UL DL UL DL
880 915 925 960 MHz 1710 1785 1805 1850 1880 1900 1910 1930 1990 2025 2110 2200
1900 1920 1980 2010 2025 2110 2170 2200
unpaird for MSS paired
Frequency [MHz]
E-GSM 880-915 / 925-960
GSM 1800 1710-1785 / 1805-1880
GSM 1900 1850-1910 / 1930-1990
3G 1900-2025 / 2110-2200
Fig. 7 Frequency Spectrum
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
15
7 The CDMA principle

CDMA is a Spread Spectrum Technology (SST). The origins of SST go back to the
1920's. SST's were used from the 1950's to the 1980's in the military sector – for
example, for satellite navigation. CDMA has been released as an SST for civilian use
since the mid-1980's. The first cellular mobile communications system to use CDMA
for multiplex transmission was IS-95. It began commercial operation at the end of
1995.
In SST's a narrowband signal with high information concentration is transformed to a
broadband signal with low information concentration – this is known as spreading.
The signals are very stable against the influence of narrowband natural or technical
interference (background noise) and interfering transmitters (intentional jamming).
There are different ways of performing the spreading.
For spreading subscriber information for CDMA, a unique (cell-internal) code is
provided for each subscriber. This code is referred to as the spreading code. The
linkage of the high bit rate code with the original subscriber information transforms
the original signal into a broadband signal. This broadband signal is transmitted
together with broadband signals from other subscribers using the same frequency
band over the radio interface. The receiver receives the sum of all of these signals.
By relinking the summation signal with the (synchronized) subscriber code the
original subscriber information is regenerated (a process known as de-spreading).
The remaining information stays in its broadband form and therefore constitutes an
underlying signal. The information remains useful as long as the underlying signal
does not dominate the despread signal. The information for the different subscribers
can be separated because of the orthogonal (or quasi orthogonal) attributes of the
code used.
16 MN3500EU50MN_0001
CDMA User 1
User 2
principle CDMA:
Users 1 & 2
Spread Spectrum Technology
•
Each user has its own code
•
High bit :rate code: spreading / de-spreading
Power P
• -
Frequency f
Frequency f
De-spread Spread signals Radio transmission = after

signals Σ spread signals de-spreading
Fig. 8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
17
7.1 CDMA types

Signals can be spread for CDMA using a number of different methods. The following
three CDMA methods are most commonly used: TH-CDMA, FH-CDMA and
DS-CDMA.
7.1.1 Time hopping CDMA (TH-CDMA)

The information-carrying signal is not continuously transmitted in the TH-CDMA
method. Instead, information is transferred in bursts. The burst transmission time is
specified by the spreading code.
TH-CDMA was developed at the end of the 1940's as the first CDMA method, and
was used for military purposes.
7.1.2 Frequency hopping CDMA (FH-CDMA)

The carrier frequency of the information-carrying signal is changed constantly during
FH-CDMA. Very fast as well as slow changes are possible. The bandwidth at any
particular time is relatively narrow. When considered over a longer period, FH-CDMA
is just as much a broadband method as TH-CDMA and DS-CDMA. The change in
carrier frequency is specified by the spreading code.
An example of the civil use of FH-CDMA is the so-called Bluetooth standard.
Bluetooth allows the transmission of information at high data rates over small
distances in the unlicensed frequency range around 2.4 GHz.
7.1.3 Direct sequence CDMA (DS-CDMA)

In DS-CDMA, subscriber information (digital in 2G and 3G systems) is spread directly
by linking with a sequence of the spreading code. This results in continuous (in
contrast to TH-CDMA) transmission of the broadband signal over the entire
bandwidth (in contrast to FH-CDMA).
DS-CDMA is used for IS-95 and the Globalstart satellite system, for example. In 3G,
UMTS is based on DS-CDMA.
18 MN3500EU50MN_0001
CDMA
types
time t
Time DS-CDMA
Direct Hopping → IS-95
Sequence (TH-CDMA) → Globalstar
(DS-CDMA) → UMTS
Frequency FH-CDMA
Hopping → Bluetooth
(FH-CDMA)
frequency f
Fig. 9 CDMA Types
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
19
7.2 Advantages of CDMA

The CDMA principle is associated with many attributes that can have positive effects
for the transmission of information.
The coded transmission and the low information concentration of the CDMA signals
were particularly important for the military applications. A transmitted signal can only
be despread, and the data regenerated, if the receiver has the correct spreading
code. The low information concentration allows information to be discretely
transmitted – the signals are for all intents and purposes concealed in background
noise.
The high level of stability of the broadband information transmission against the
effects of narrowband background noise is vitally important for military and civil
utilization. Frequency hopping is used in narrowband systems (such as GSM) to
obtain this effect.
Yet another CDMA attribute is extremely important for civil applications in mobile
communications systems. In principle, CDMA allows the re-use of the same
frequency band in all neighboring cells (re-use = 1). In contrast, the same frequency
bands cannot be re-used in neighboring cells in FDMA or TDMA systems. To prevent
interference by subscribers at the same frequencies or in the same timeslots, cells
with identical frequencies must be spatially separated. In FDMA and TDMA systems,
cells are arranged in a careful, complicated frequency planning process. Re-use
schemes of 1/7, 1/9, etc. are typical. As a result, only one part (1/7, 1/9, ...) of the
theoretically available frequency band can be used in the one cell.
CDMA can therefore, in principle, do without complicated frequency planning, and
allows efficient usage of the available (scarce) frequency resources.
The limits to transmission capacities in FDMA and TDMA systems are determined by
a fixed number of physical channels. With CDMA, however, there is a "soft" capacity
limit. The capacity of CDMA systems is mainly restricted by the interference of other
subscribers in a cell (so-called intra-cell interference) and interference from other
cells (inter-cell interference).
Other advantages presented by CDMA, and in particular for transmission in
treacherous terrain, are the use of multiple paths (multipath advantage) and soft
handover. Both effects are described later.
However, CDMA is also accompanied by a number of problems. For example, a fast
power control system is required.
20 MN3500EU50MN_0001
CDMA • Stability → Narrowband noise

advantages • Stability in difficult terrain
(→ Multipath Advantage, Soft HoV)
• Simple frequency planning (re -use: 1)
• Radio resources: efficient usage
• “Soft” capacity limit
• but: fast power control needed
Frequency planning / resource planning

TDMA CDMA
(e.g. GSM with re-use 1/7) (UMTS; re-use: 1)
3/7 1/1
2/7 4/7 1/1 1/1
1/7 1/1
7/7 5/7 1/1 1/1
6/7 1/1
Re-use 2/7
Distance
Fig. 10 CDMA network
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
21
8 Transmission principles
The mobile transfer of information in a cell between base stations and mobile stations
requires coordination of the information transmission. Two different aspects require
coordination. Firstly, during today's typical full duplex transmission, the two
transmission directions (uplink and downlink) must be coordinated between a mobile
station and the base station. Two different principles are applied for duplex
transmissions: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).
Secondly, the transmission between the different mobile stations of a cell and the
base station must be coordinated. Three different multiplex methods are mainly used
for this purpose: Frequency Division Multiple Access (FDMA), Time Division Multiple
Access (TDMA) and Code Division Multiple Access (CDMA).
22 MN3500EU50MN_0001
Transmissionprinciples
FDMA
UL DL
Duplex Multiplex
transmission methods
FDD TDD TDMA CDMA
Fig. 11 Duplex and Multiplex methods
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
23
8.1 Duplex transmission: FDD & TDD

Two duplex methods are used for coordinating the uplink (UL) and downlink (DL)
components of a transmission between a base station and a mobile station, namely
Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
UL and DL are implemented for FDD in different frequency bands. The gap between
the two frequency bands for UL and DL is known as the duplex distance. It is
constant for all mobile stations in a standard. Generally the DL frequency band is
positioned at the higher frequency than the UL band.
In the case of TDD, UL and DL are implemented in the same frequency band. This is
done by dividing the band into timeslots (TS) and frames. A frame contains a specific
number, n, of timeslots, TS. A number, n, of these timeslots is reserved for UL
transmission (half of the timeslots in 2G systems) and the remaining for DL
transmission. The duration of a frame determines the cyclical repetition of the
corresponding UL / DL transmission. The UL and DL transmission occurs almost
simultaneously – i.e., the duration of a frame is generally in the range of a number of
ms.
TDD transmission is mainly used as of the 2nd mobile communications generation (in
digital transmissions). Digital transmission simplifies speech and data compression.
As a result, only a fraction of the time needed for analog transmission is required for
digital transmission of subscriber data.
24 MN3500EU50MN_0001
Duplex transmission
•
FDD & TDD •
•
TDD:
Time t
duplex distance UL UL / DL
separated
Time t
according to
time
DL
UL DL
UL
DL
frequency f
Frame
FDD: UL / DL with n TS
separated according to UL
frequency
FDD: Frequency Division Duplex frequency f
TDD: Time Division Duplex
TS: Time Slot
Fig. 12 FDD and TDD
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
25
8.2 Multiplex methods

Multiplex methods are used to divide the limited frequency resources of a cell
between the different subscribers and mobile stations in the cell. Three different
methods are mainly used today: Frequency Division Multiple Access (FDMA), Time
Division Multiple Access (TDMA) and Code Division Multiple Access (CDMA). Other
multiplex methods are currently being researched or developed (for example, Space
Division Multiple Access – SDMA).
Frequency Division Multiple Access (FDMA)

FDMA divides the available frequency range into channels with a specific bandwidth
(frequency band). One of these frequency bands is made available to a single
subscriber without restriction throughout the entire duration of a connection. Each
subscriber in a cell therefore uses a different frequency band than the other
subscribers. In this way undesirable noise can be avoided (or reduced as much as
possible or as required).
Time Division Multiple Access (TDMA)

Unlike FDMA, a single frequency band is available to a number of different
subscribers with TDMA. The frequency band is divided into TDMA frames for this
purpose. Each frame is divided into n timeslots (TS). Each of the n timeslots of a
frame can be assigned to a different subscriber. In this way, a single frequency band
can carry up to n subscribers. The transmission of a single subscriber comprises
individual timeslots assigned cyclically to the subscriber (generally 1 TS per frame;
longer cycles are also possible). With TDMA, each frequency band is also used only
by a single subscriber at a particular time. This prevents interference occurring
between different subscribers (or prevents noise as much as possible or as required).
Code Division Multiple Access (CDMA)

In contrast to TDMA and FDMA, multiple subscribers can use the same frequency
band at the same time with CDMA. Each subscriber is provided with a unique (in the
cell) code for this purpose. The transmitter links the original information with the
code. The coded information is then transmitted over the radio interface. The original
information is regenerated in the receiver using the same code.
26 MN3500EU50MN_0001
Multiplexmethods
power power
P P
time t
FDMA time t
TDMA
TS 3
TS 2
TS 1
1 2 3
frequency f frequency f
power
P for coordinatinglimited
time t
CDMA frequency resourcesto
different users
Multiple BS & MSwith common

method know-howregarding:
3 FDMA Frequency
2 TDMA Time
1 CDMA PNcode
frequency f
Fig. 13 Multiplex methods
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
27
9 UMTS-two different modes

In UMTS a difference is made between FDD mode and TDD mode.
In FDD mode, multiple access is performed by a combination of CDMA and FDD.
Individual subscriber signals are separated from one another by different spreading
codes. Variable transmission rates can be achieved either by changing the spreading
factor or by multicode transmissions.
The multiple access in TDD mode is performed by a combination of CDMA and
TDMA. A TDMA frame lasts 10 ms and is divided into 15 TS in which each can be
implemented up to 16 CDMA channels. The time slots can be allocated upstream or
downstream independently of one another. This favors optimal division of the radio
resources with strongly unsymmetrical traffic. Variable transmission rates can be
implemented in TDD mode either by multicode, multislot transmissions or by
changing the spreading factor.
UTRA TDD / FDD – common features

UTRA FDD and TDD modes were harmonized in many central areas – for example:
• Bandwidth B = 5 MHz (including guard bands)
• Chip rate Rc = 3.84 Mchip/s
• Modulation method: QPSK
• Re-use = 1 (i.e., same frequency possible in neighboring cells)
• Timing structure (frame & TS duration)
• Spreading codes: based on OVSF (Orthogonal Variable Spreading Factor)
codes
UTRA TDD / FDD – differences

There are also differences in the following central aspects:
FDD uses pure WCDMA (DS-CDMA) for multiplexing. The information is transmitted
continuously spread over the entire bandwidth. The shortest duration of a
transmission is represented by a frame (10ms).
TDD uses a hybrid solution of TDMA and WCDMA (DS-CDMA) as multiplex access.
As is the case with GSM, the subscriber information is sent in the form of single
bursts. A TDMA frame (10ms) contains 15 timeslots (TS) that can contain bursts from
different users (CDMA component).
FDD uses spreading factors of 256 to 4 (UL) or 512 to 4 (DL); TDD uses factors of 16
to 1.
FDD mostly uses soft handover and TDD hard handover (described later).
The 3G TS 25.201 provides an overview of the major common features and
differences along with references to individual aspects.
28 MN3500EU50MN_0001
code
FDD
time t
Mode
Fig. 14 FDD mode
time t
TDD 15
Mode
Frame
2
1
code
TS
Fig. 15 TDD mode
MN3500EU50MN_0001
29
9.1 Variation in data rate

UMTS allows flexible, dynamic variation of the data rate. The data rate can be varied
in different ways in the TDD and FDD modes.
In the FDD mode, the data rate can be varied by SF variation. SF can vary from 256
– 4 (UL) or from 512 – 4 (DL). This gives rise to symbol rates of 15 ksymb/s (UL) or
7.5 ksymb(s) (DL) to 960 ksymb/s. This data rate can include the simultaneous
transmission of data belonging to different applications of the same subscriber. In
other words, multimedia applications are possible.
The data rate can be varied in the TDD mode by SF variation and combination of
timeslots (TS). SF can vary from 16 – 1, therefore yielding symbol rates of
240 ksymb/s to 3.84 Msymb/s. These symbol rates must be regarded while
considering the 15 timeslots, TS (TDMA component of the TDD mode). In this way,
symbol rates of 16 ksymb/s to 256 ksymb/s are available to a subscriber using one
TS by varying the SF from 16 to 1. This transmission rate can be increased by
combining multiple timeslots in a TDMA frame for one user.
The data rate can also be increased in the TDD and FDD modes by allocating
multiple codes to one user (if the UE is capable of doing so). The allocation of
multiple codes is useful for different applications belonging to the same user that are
served simultaneously. A fine level of granularity of the data rate can be obtained in
this way.
9.2 Asymmetric allocation of frequency resources

Strongly asymmetric data streams in the UL and DL directions are expected,
particularly with regard to the mobile use of the Internet in 3G. Both UTRA modes
allow asymmetric transmission of subscriber data. The TDD mode enables network
operators to respond in a flexible manner to the asymmetry and to optimize how they
use their frequency resources. Different numbers of TSs can be used for UL and DL.
However, at least two of the 15 TSs must remain reserved for UL or DL (for different
TDD configuration options, refer to TS 25.221).
30 MN3500EU50MN_0001
V a r ia tio n
in d a ta r a te s
t im e t
FDD
code
V a r ia tio n in d a ta r a te s :
• S F = 4 - 2 5 6 (D L : 5 1 2 )
• A l l o c a t i o n o f m u lt ip le c o d e s
fre q u e n c y f
Fig. 16 FDD data rate
Variation of
data rates in TDD time t
15 Variation in data rates:
• SF = 1 - 16
• TS combination
• Allocation of multiple codes
2
code
frequency f Asymmetric
UL/DL allocation possible
flexible
Switching Point (min. 2/1 TS for DL/UL)
Example: UL DL
Fig. 17 TDD data rates
MN3500EU50MN_0001
31
9.3 FDD uplink and downlink data rates

Data rates in uplink
The maximum user data rate on a single code is derived from the maximum channel
bit rate, which is 960 kbps without channel coding with spreading factor 4. With
channel coding the practical maximum user data rate for the single code case is in
the order of 400-500 kbps. When higher data rates are needed, parallel code
channels are used, e.g. the use of 3 parallel codes with spreading factor 4 lead to a
data rate of 2880 kbps without channel coding.
Data rates in downlink

Modulation causes some differences between the uplink and downlink data rates.
While the uplink DPDCH consists of BPSK symbols (1 symbol represents 1 bit), the
downlink DPDCH consists of QPSK symbols (1 symbol represents 2 bits). The bit
rate that can be accommodated in a single code in the downlink DPDCH is almost
double that in the uplink DPDCH with the same spreading factor.
32 MN3500EU50MN_0001
Spreading factor DPDCH channel DPDCH channel

symbol rate (ksps) bit rate (kbps)
256 15 15
128 30 30
64 60 60
32 120 120
16 240 240
8 480 480
4 960 960
Uplink Dedicated Channel symbol and bit rates
Spreading factor DPDCH channel DPDCH channel

symbol rate (ksps) bit rate (kbps)
512 7.5 15
256 15 30
128 30 60
64 60 120
32 120 240
16 240 480
8 480 960
4 960 1920
Downlink Dedicated Channel symbol and bit rates
MN3500EU50MN_0001
33
34 MN3500EU50MN_0001
10 WCDMA
MN3500EU50MN_0001
35
WCDMA is a wideband Direct Sequence Code Division Multiple Access (DS-CDMA)

system. Digital, binary subscriber information is linked in the transmitter with the
spreading code generated by a code generator – this process is termed spreading.
The spreading code consists of a high bit rate code sequence. The smallest unit of
information in the spreading code is referred to as a chip (quasi-random bits) to
distinguish it from the smallest unit of subscriber information, the bit. The rate of the
spreading code is known as the chip rate. The information obtained by spreading is
modulated to a carrier frequency. The higher the information rate (i.e., the chip rate),
the wider the bandwidth of the resulting signal. In order to support very high bit rates,
the use of variable spreading factor and multicode connections is supported. The
chiprate of 3.84 Mcps (fixed parameter) used leads to a carrier bandwidth of 5 MHz.
The inherently wide carrier bandwidth of WCDMA supports high user data rates and
also has certain performance benefits, such as increased multipath diversity. The
operator can deploy multiple such 5 MHz carriers to increase capacity in form of
hierarchical cell layers.
Originally a chip rate of 4.096 Mcps/s was planned for UMTS. In the course of
harmonization with the American MC-CDMA a chip rate of 3.84Mcps was set. From
this chip rate resulted in the bit rate of 1920 kbit/s (1920kbit/s x 2 = 3840kcps/s)
which is also often described.
The broadband signal is transmitted over the radio interface.
The receiver demodulates the signal and links the resulting information with the same
spreading code used in the transmitter. This process is known as de-spreading. De-
spreading produces the original subscriber information. It is vital for de-spreading that
the code in the receiver be exactly synchronized in time with the code in the
transmitter. A shift by just one chip prevents information from being regenerated.
36 MN3500EU50MN_0001
DS-CDMA: Transmission / reception
Air
Interface
bits chips symbol
RB RB
Wideband De- De-
Spreading Modulation Modulation Spreading
Time
RC fT RC synchronization
Code Carrier Code

Generator Generator Generator
RB: Bit Rate

RC: Chip Rate
fT: Carrier frequency
Fig. 18 Transmission in CDMA
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
37
10.1 QPSK modulation

The spreading process is followed by the modulation of the data. UMTS uses
Quadrature Phase Shift Keying (QPSK) to modulate. Phase Shift Keying (PSK)
means that the information is transmitted in the form of shifts in the phase of the
carrier frequency. Quadrature PSK means that a total of four different phase shifting
options are available. They each allow a 2-bit pair to be represented as a single
information unit: '00', '01', '10' and '11'. The information unit transmitted over the radio
interface is known as a symbol. A symbol therefore has 2 bits in the QPSK
modulation method used in UMTS.
The information in the I-branch is represented as the phase shift of a carrier
frequency generated by an oscillator. The representation of a '1' results in a phase
shift of 270°, the representation of a '0' in a phase shift of 90°. The phase of the
carrier wave is shifted by 90° for the Q-branch. The representation of '1' or '0' results
in a phase shift of 180° or 0° respectively for this branch.
After then adding the I- and Q-branches together, the four possible phase shifts of
45°, 135°, 225° and 315° shown in the phase diagram are obtained. These shifts
represent the symbol information '00', '01', '11' and '10'.
Details on the topics of spreading and modulation can be found in the 3G TS 25.213
and 25.223 (FDD / TDD).
38 MN3500EU50MN_0001
QPSK Modulation
Phase Modulation
“1” ⇒ 270° I-Branch
I- “0” ⇒ 90°
Branch sin(2πfct)
Oscillator: fc
Rc
Σ 90°
Phase Shift
Q- cos(2πfct)
Branch Q-Branch
“1” ⇒ 180°
“0” ⇒ 0°
“01” “00”
135° 45°
Symbol &
Phase Shift
“11” “10”
225° 315°
Fig. 19 QPSK Modulation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
39
10.2 Spreading and scrambling

Physical channels of the same carrier frequency by spreading codes can be
separated by the CDMA procedure. Physical channels of the same transmitter are
separated using so-called OVSF (Orthogonal Variable Spreading Factor) codes.
These codes are also orthogonally suited to one another with different spreading
factors. The individual base and mobile stations are separated among themselves by
scrambling the chip sequence. The orthogonality of the code channels of a station is
not influenced among themselves by this scrambling, the chip sequence of the
individual stations among each other are only semi-orthogonal following scrambling.
The scrambled chip sequence is transmitted with a QPSK modulation.
40 MN3500EU50MN_0001
Spreading and Scrambling
channelization scrambling
code code
Bit Rate Chip Rate Chip Rate
DATA Channel 1
.
.
.
DATA Channel n
Fig. 20 Spreading and Scrambling
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
41
Spreading / de-spreading
In UMTS, the binary, digital subscriber data (1, 0) is converted on the transmission
side to bipolar data (+1, –1) before the spreading process takes place. The spreading
code also consists of bipolar data. The value of a chip can be +1 or –1. The
subscriber data is then multiplied by the high chip rate spreading code. The result is
the coded data, which is then transmitted over the radio interface.
The receiver multiplies the received, code data sequence with the bipolar spreading
code to obtain a bipolar data sequence. The original subscriber data is recovered by
converting this data sequence to binary, digital data.
Spreading Factor (SF)

The spreading factor (SF – also frequently known as the Processing Gain, Gp)
indicates the number of chips that spread a symbol each time (see below). The SF
therefore states the relationship between the chip rate, Rc (chip/s) and the data rate
of the subscriber (symbol/s or bit/s). SF also gives the relationship between the
spread bandwidth B and unspread bandwidth W.
Information units: bits, chips, symbols

The smallest unit of digital information is generally called a bit (an abbreviation
derived from "binary digit"). To distinguish the smallest units in the original subscriber
information, spreading code and data transmitted over the radio interface, different
terms are used, namely: bit, chip and symbol respectively.
A symbol can have different numbers of bits depending on the modulation method
used for transmission over the radio interface. Symbols have one bit each in the
Gaussian Minimum Shift Keying (GMSK) method used in GSM and in the Binary
Phase Shift Keying (BPSK) method. In the Quadrature Phase Shift Keying (QPSK)
method used generally for UMTS, a symbol has two bits, and in the 8 Phase Shift
Keying (8PSK) method used in EDGE even three bits.
42 MN3500EU50MN_0001
Spreading / De-spreading
1 symbol
Binary Data 1 0 1 0
+1
Bipolar
Data -1
SF = Rc / RS
x =B/W
+1
Spreading
Code -1
= +1
Spread Bit / symbol →
Data modulation method
-1 e.g.:
x GMSK: 1 / 1 (bit/symbol)
+1 BPSK: 1 / 1
Spreading
QPSK: 2 / 1
Code -1 8PSK: 3 / 1
= B = Bandwidth, spread
W = Bandwidth, despread
+1
Bipolar RS: Symbol rate [ symb/s]
RB: Bit rate [ bit/s]
Data -1 RC: Chip rate [ chip/s] 3,84 Mcps/s
SF = Spreading Factor
GMSK: Gaussian Minimum Shift Keying
Binary Data 1 0 1 0 BPSK: Binary Phase Shift Keying
QPSK: Quadrature PSK
8PSK: Eight PSK
1 chip
Fig. 21 Spreading and Despreading
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
43
Spreading / de-spreading – an example

The example portrays CDMA transmission for two users. Orthogonal spreading
codes with a spreading factor of 2 are used for both users (1/2).
The original information of the two users (data users 1 and 2) are converted to bipolar
data (1 / 2) and multiplied by the spreading code (1 / 2).
The coded signals interfere with each other during transfer over the radio interface.
The receivers receive the overall signal (of both users). By multiplying the overall
signals with the spreading code (1 / 2) different data sequences (de-spread data
1 / 2) are obtained for users 1 and 2. The sequences are integrated during the
duration of a symbol. The information is interpreted as 1 for positive results and 0 for
negative results. The final result is the original information of the two users 1 / 2.
Integration / capacity restrictions

The integration of the data signals is an important component of the de-spreading
process. If a single coded signal of a user is multiplied by the correct code and then
integrated during the length of a symbol, information is obtained that can be clearly
interpreted. The higher the spreading factor, the clearer ("stronger") the information.
A high spreading factor therefore assures a high level of transmission security (but at
a lower data rate however).
If the coded signal of a user is multiplied by a different code and then integrated, a
zero is obtained for strict orthogonality of the codes – i.e., the result cannot be
interpreted. With the quasi orthogonality used in practice there is little
"misinformation" when compared with the process of multiplying with the correct code
followed by integration. Care must be taken in practical applications to prevent the
sum of the "misinformation" from outweighing the strong (correct) information – i.e.,
the system capacity is limited by the background noise from the transmissions of
other users.
44 MN3500EU50MN_0001
Spreading / Data User 1 1 0 1 Data User 2 0 0 1

De-spreading Bipolar +1 Bipolar +1
Data 1 -1 Data 2 -1
Example: x x
+1 +1
SF = 2; Code 1 Code 2
2 users/channel -1 -1
= +1
= +1
Code 1 Spread Spread
= ( 1 / -1) Data 1 -1 Data 2 -1
Code 2
= ( 1 / 1) Receiver: Σ Spread data here: Σ = 0 -2 -2 0 2 0
Σ Signals +2 Σ Signals +2
(Receiver) 0 (Receiver) 0
-2 -2
x x
+1 +1
Code 1 Code 2
-1 -1
= =
De-spread +2 De-spread +2
0 0
Data 1 -2 Data 2 -2
after +2 after +2
Integration Integration -2
-2
⇒ User Data 1 1 0 1 ⇒ User Data 2 0 0 1
Fig. 22 Integration
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
45
10.3 Tasks of the Codes

Channelization codes
The spreading/channelization codes of UTRA are based on the Orthogonal Variable
Spreading Factor (OVSF) technique.
Channelization codes are used to separate channels from the same source.
For DL this channelization means the separation of different users (or, to take it a
step further, different applications of different users) by the BTS.
For UL the channelization means the separation of different applications used
simultaneously by the same UE. Up to 6 different applications are theoretically
possible from individual UEs.
Scrambling codes
In addition to spreading, part of the process in the transmitter is the scrambling
operation. This is needed to separate terminals or base stations from each other.
Scrambling is used on top of spreading, so it does not change the signal bandwidth
but only makes the signal from different sources separable from each other. With the
scrambling , it would not matter if the actual spreading were done with identical codes
for several transmitters. As the chiprate is already achieved in the spreading by the
channelization codes, the symbol rate is not affected by the scrambling.
Scrambling codes are used to separate different sources.
For DL this means the separation of different BTSs. Each cell has a scrambling code
to allow the UE to distinguish between neighboring cells. The scrambling codes are
not globally unique cell codes.
For UL the scrambling means the separation of different items of UE in a cell. The
scrambling codes are assigned to the UE by UTRAN.
FDD (in up- and downlink) and TDD use different scrambling codes. In FDD so-called
gold codes are used to form scrambling codes (10ms in length = 38400 chips). In
TDD 128 different scrambling codes (sequences of 16 chips) are used.
TS 25.201 provides an overview of channelization and scrambling codes. Details on
the channelization and scrambling codes used for FDD and TDD can be found in TS
25.213 and TS 25.223.
46 MN3500EU50MN_0001
UTRA CC and SC in DL direction

SC 2
SC 1 Node B
CC1
Appl.1
CC2
CC3 Appl.2
CC4
Channelization code: Scrambling code:

Node B Channelisation
separates
source
channels from the same
separates different sources
• DL: separates different BTS

• •DL: channels of the same BTS
e.g. different UE and applications
Fig. 23 Scrambling and Channelization in Downlink
UTRA CC and SC code in UL direction
CC1
CC2
SC 2
CC1
CC2
Scrambling code:
CC3 Scrambling
SC 1 separates different sources
• UL: separates different UE in 1 cell
Channelization code:
•separates channels from the source
Node B • UL: channels of the same UE
e.g. different applications (max. 6 SF variable)
Fig. 24 Scrambling and Channelization in Uplink
MN3500EU50MN_0001
47
10.4 Structure of channelization codes

The channelization codes in the FDD and TDD modes are used for the actual
spreading process. The UTRA channelization codes are based on Orthogonal
Variable Spreading Factor (OVSF) codes of different lengths. A symbol of user
information is spread by a channelization code sequence with a specified length (=
spreading factor, SF) – i.e., number of chips. Different data rates are obtained by
using different spreading factors, SF.
Channelization codes are generated as shown in the next diagram. The (1x1) start
matrix with the value "1" represents the channelization code with SF = 1. All other
matrices are successively constructed by 4-fold insertion of the preceding matrix.
Three of these matrices (top left and right, and bottom left) contain the original values
of the preceding matrix while the fourth (bottom right) contains the inverted matrix
value. The channelization codes of length n (SF = n) are obtained from the columns
of the corresponding matrix (n x n).
A code tree arises in which all codes of a particular length (SF = 1, 2, 4, 8,..., 512)
are orthogonal to each other.
If you take codes that are 256 long, there are 256 different orthogonal codes for 256
different users / applications for FDD DL, for example (ignoring the codes for
signaling), with 15 ksymb/s. In contrast, there are only 4 orthogonal codes of length 4
(SF = 4) with which 960 ksymb/s can be obtained.
As a code is produced in the code tree by multiplying a code of the lower levels,
codes of different levels only then suit each other orthogonally if the shorter is not
found in the longer. This means that two codes of different levels of the code tree are
orthogonally suited to one another provided one of the two codes is not a mother
code of the other. The number of allocable codes is independent of the bit rate and
the spreading factor of one of each physical channel by this limitation.
The definition for the same code tree means that from a single source, from either a
terminal or a base station, one code tree is used with one scrambling code on top of
the tree. This means that different terminals and different base stations may operate
their code trees totally independently of each other; there is no need to coordinate
the code tree resource usage between different base stations or terminals.
10.5 Structure of scrambling codes

In FDD mode, UL of either scrambling codes with long or short periods can be used.
These codes are gained from the mathematical operations from the so-called gold
codes. In DL 38400 long complex codes are used to scramble the spread physical
channels. These are also gained from real gold codes.
In TDD mode there are 128 different real-value scrambling codes of length 16.
48 MN3500EU50MN_0001
Beginning of the channelization code tree
SF = 1 SF = 2 SF = 4 SF = 256
CC256,0
CC256,1
CC4,0 = (1,1,1,1)
CC256,2
CC2,0 = (1,1)
CC1,0 = (1) CC4,1 = (1,1,-1,-1) •

••• • •••
CC4,2 = (1,-1,1,-1) •
CC2,1 = (1,-1)
CC256,255
CC4,3 = (1,-1,-1,1) CC256,256
Channelization Codes (CCn,m) = OVSF Codes
CCn,m Generation: 1 1 CCn/2 CCn/2

CC1 = (1) CC2 = CCn =
from columns in CCn 1 -1 CCn/2 -CCn/2
OVSF =
Orthogonal Variable
branch
Spreading Factor
Fig. 25 Orthogonal Codes
UTRA Scrambling Codes
Scrambling Codes:
• FDD: for BTS / UE “Gold Codes“;
10 ms period (1 frame = 38400 chips)
• TDD: for BTS / UE 16 chips long,
predefined sequences
Fig. 26 Scrambling Codes
MN3500EU50MN_0001
49
11 UTRAN timing structures

Chip
The shortest unit of time used in UTRA corresponds to the duration of a chip. Since a
chip rate of 3.84 Mchip/s is used, the duration of a chip is about 260.4 nano
seconds (ns).
Timeslot (TS)
A UTRA timeslot (TS) is defined as the length of 2560 chips: this corresponds to a
duration of 2/3 ms. A timeslot is the shortest repetitive period in UTRA.
A timeslot for the TDD mode means the time frame allowed by an HF burst.
In the FDD mode specific information is exchanged cyclically between the UE and
network. An example of this is the power control information (Transmit Power Control
– TPC).
Frame
A UTRA frame is defined by the duration of 10 ms. A frame therefore contains 15
timeslots.
In the TDD mode, a frame is identical with the TDMA frame – i.e., the cyclical
repetitive pattern of the TSs.
In the FDD mode, a frame is the shortest possible transmission duration. Short data
packets for setting up a connection, for transmission of SMS messages or packet-
switched data packets are at least one frame in duration.
UTRA is a radio access solution allowing data rates that are not only flexible, but that
can also be dynamically adapted. A frame is likewise (for TDD and FDD) the shortest
period of time for changing the transmission rate.
Superframe
A UTRA superframe is defined as the duration of 72 frames – i.e., 720 ms.
A superframe is the counting period for defining physical channels. Since it is exactly
6 times longer than a traffic channel (TCH) multiframe in GSM (= 120 ms), it enables
adaptation of the timing patterns between UMTS and GSM – as is essential for inter-
system handover between the two systems.
50 MN3500EU50MN_0001
UTRA timing structure
• Shortest information unit in CDMA

(of the spreading code)
Chip 1/3,840,000 s ≈ 0.2604 µs
Timeslot TS 2560 chips • TDD: TS contains 1 burst

• FDD: periodic repetition of
control information (e.g. TPC)
2/3 ms
Frame f TS#0 ••• TS#i • TDD: TDMA frames

••• TS#14 • FDD: shortest transmission duration
• TDD & FDD: shortest pattern
→ data rate adaptation Datenrate
10 ms
• TDD & FDD: counting period for

Superframe f#1 ••• f#i ••• f#72 → Def. physical channels
→ Handover to GSM
(GSM TCH Multiframe = 120 ms)
720 ms
Fig. 27 UTRAN timing structures
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
51
52 MN3500EU50MN_0001
12 Logical, transport & physical channels
Radio Interface:
Transport Concept
Uu
Iub
Node B UE
RNC
Logical, Transport
& Physical Channels
Fig. 28 Logical, Physical and Transport Channels
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
53
UMTS uses a three-layer concept for channel organization: Logical Channels,

Transport Channels and Physical Channels.
Logical channel
Comparable to GSM, a set of logical channels is defined in UMTS for different types
of data transfer services. Each logical channel is defined by “what type of
information” is transferred. The UMTS Logical Channels are described in 3G TS
25.301.
Transport channel
Compared to GSM, in UMTS a new concept, the concept of Transport Channels, has
been defined. Transport Channels are described by “how and with what
characteristics data are transferred over the radio interface”. Different Logical
Channels can be mapped together onto one Transport Channel. The Transport
Channels can be sub-divided into two general classes:
• common transport channels, where there is a need for in-band identification of
the User Equipments UEs when particular UEs are addressed
• dedicated transport channels, where the UEs are identified by the physical
channel. i.e. code & frequency of the FDD mode and code, time slot &
frequency for the TDD mode.
The UMTS Transport Channels are described in 3G TS 25.301. The mapping of
Logical Channels onto Transport Channels is described in 3G TS 25.301, too.
Physical channel
Physical channel describe the physical transmission of the information over the radio
interface. In UMTS physical channels of the UTRA FDD mode are characterized by
the code and frequency (UL & DL) and the physical channels of the TDD mode are
characterized by code, frequency and time slot TS.
The UMTS Physical Channels and the mapping of Transport Channels onto Physical
Channels are described in 3G TS 25.211 for the FDD mode and in 3G TS 25.221 for
the TDD mode. A general overview of the UMTS physical layer is given in 3G TS
25.201. Details of the FDD mode physical layer are given in 3G TS 25.211 – 25.215,
of the TDD mode in 3G TS 25.221 – 25.225.
Due to clarity, not all the UMTS Logical, Transport and Physical Channels are
described in the following. The full set of Logical, Transport and Physical Channels
can be found in 3G TS 25.301, 25.211 and 25.221.
54 MN3500EU50MN_0001
Logical, Transport
& Physical Channels Logical
Logical&&Transport
Transport
Channels:
Channels: TS25.301
TS 25.301
Transport
Transport&&Physical
PhysicalChannels:
Channels:
TS 25.211 & 25.221
TS 25.211 & 25.221
Iub Uu UE
Node
RNC B
Logical Channel ≡type of information transferred

Transport Channel ≡how & with what characteristics
data are transferred
Physical Channel ≡
frequency, code (& TS)
Fig. 29 Channel structure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
55
12.1 Channel mapping DL

In the following, the mapping of Logical to Transport and Physical Channels is
shown. For clarity, only the most important channels of the FDD mode are listed.
Common Physical Channel:

• Common Pilot Channel CPICH. The CPICH is an unmodulated code channel,
carrying the Scrambling Code of the cell.
• Synchronization Channel SCH. The SCH is needed for time synchronization
of the UEs at cell search.
• Primary Common Control Physical Channel P-CCPCH. The P-CCHCH is
carrying the Logical Channel Broadcast Control Channel BCCH, which is
mapped to the Transport Channel Broadcast Channel BCH.
• Secondary Common Control Physical Channel S-CCPCH. The S-CCPCH
carries two different Common Transport Channel: the Paging Channel PCH (for
paging user) and the Forward Access Channel FACH (for either access grants
& acknowledgements or DL small user data packets). They can be multiplexed
together on one single S-CCPCH or use two / several S-CCPCH, depending on
network operators decision.
• Page Indication Channel PICH. The PICH can be used in connection with the
PCH for efficient sleep mode operation of the UE.
• Acquisition Indication Channel AICH. The AICH is used in connection with
the RACH for random access to prevent collisions.
• Physical DL Shared Channel PDSCH. The PDSCH is used to carry the
transport channel DSCH. The PDSCH is used to transmit dedicated data with
high peak rate and low activity cycle on common resources. It is shared by
several users based on code multiplexing. The PDSCH is always associated
with a DPCH.
Dedicated Physical Channel:

Dedicated Physical Channel DPCH. The DPCH is used to carry Dedicated or
Common Traffic Channel DTCH / CTCH data (i.e. payload) and Dedicated Control
Channel DCCH data to maintain the connection. CTCH / DTCH and DCCH
information are time-multiplexed in the DPCH.
56 MN3500EU50MN_0001
TDD:
TDD:
••identical
identicalLogical
Logical&&
FDD Mode (DL) Transport
TransportChannels
••Physical
Channels
Channels:
Physical Channels:
no
noCPICH,
CPICH,AICH
RNC AICH UE
Logical Channels: Control Channels Traffic Channels
BCCH PCCH CCCH DCCH DTCH CTCH
BCH PCH FACH Common DSCH Dedicated DCH

Transport Transport
Channels Channels
P-CCPCH
CPICH Primary
S-CCPCH PICH PDSCH
Common
Pilot SCH
Common
Control
Page
Secondary Indication AICH Physical DL
Shared DPCH
Channel Physical Common Channel Acquisition Channel Dedicated
Synchronisation
Channel Control Indication Physical
Channel Physical Channel Channel
Channel Physical
Channels
BCCH: Broadcast Control Channel DCCH: Dedicated Control Channel FACH: Forward Access Channel
PCCH: Paging Control Channel DTCH: Dedicated Traffic Channel DSCH: DL Shared Channel
CCCH: Common Control Channel CTCH: Common Traffic Channel DCH: Dedicated Channel
Fig. 30 Channel mapping DL
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
57
12.2 Channel mapping UL

Common Physical Channel:
• Physical Random Access Channel PRACH. The PRACH is used to carry the
RACH data, i.e. for initial network access and transmission of small user data
packets on common resources.
• Physical Common Packet Channel PCPCH. The PCPCH is used to carry the
CPCH data, i.e. it is used to transmit small and medium size data packets on
common resources.
Dedicated Physical Channel:

Different to the FDD mode DL transmission, the Dedicated Traffic (DTCH) and
Dedicated Control (DCCH) information of the DCH are not time-multiplexed at UL
transmission. They are code-multiplexed onto different physical cannel:
• Dedicated Physical Control Channel DPCCH. The DPCCH carries the UL
Dedicated Control Channel DCCH physical layer control information to maintain
the connection.
• Dedicated Physical Data Channel DPDCH. The DPDCH carries the UL
Dedicated Traffic Channel DTCH, i.e. user data and higher layer signaling.
In a dedicated connection, the UE may use one DPCCH and one or more DPDCH
(up to 6; TS 25.213) for UL transmission.
58 MN3500EU50MN_0001
FDD Mode (UL)

RNC UE
Logical Channels: Control Channels Traffic Channels
CCCH DCCH DTCH
Common Dedicated
RACH CPCH DCH
Transport Transport
Channels Channels
PRACH DPCCH
Physical PCPCH Dedicated DPDCH
Physical Random
Access
Physical
Common
Physical
Control
Dedicated
Physical
Channels Channel Packet Channel Data
Channel Channel
CPCH: Common Packet Channel

RACH: RandomAccess Channel
DCH: Dedicated Channel
Fig. 31 Channel mapping UL
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
59
60 MN3500EU50MN_0001
13 UTRAN functional description
MN3500EU50MN_0001
61
13.1 Power control

Fast power control is essential in CDMA systems. Since many subscribers transmit in
the same frequency band and as the same frequency can be used in principle in
each cell (re-use = 1), each user can cause interference for the others. The power
control is used to limit interferences. The capacity of the CDMA system is mainly
limited by the level of the (inter- and intra-cell) interferences. As a result, an optimized
power control greatly optimizes the system capacity.
UL power control reduces the interference between different UE, DL power control
and the interference between neighboring base stations, BTS.
The power control is also used to solve the so-called "near-far" problem. For different
UE with identical transmission power, the power received at the BTS of UE located
near the BTS is more powerful than the power of the more remote UE. This may
mean that only the information of the UE near to the BTS can be interpreted. This
must be prevented as much as possible. In ideal cases, the power received at the
BTS is identical for all UE served by the BTS (assuming the transfer rates are
identical). This ideal situation also represents the maximum capacity of the cell.
Genuine fast power control is necessary because of the mobility of the UE. This
mobility causes rapid variation in the attenuation of the power of the UE. Let us
consider an example: the power of UE received at the BTS can increase by several
factors in milliseconds because the UE, for example, has moved away from the "radio
shadow" of a building and has a direct line of sight to the BTS. The interference of the
UE can then disrupt the communication between the BTS and all other UE – the
situation must be governed by a fast power control.
62 MN3500EU50MN_0001
Power control
principle
BTS
UL & DL
Power Control
CDMA: for
all transmit limiting interference
P(UE2)
in the same
frequency band
P(UE1)
⇒
each user can
interfere with UE2
the others
UE1 “near-far”
problem:
BTS P(UE1) ≈ P(UE2)
at Node B receiver
Fig. 32 Power Control
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
63
Three different power control types are used in UTRA for efficient power control:
Open Loop Power Control, Inner Loop Power Control and Outer Loop Power Control.
Open loop PC
Open Loop Power Control is used for UL transmissions to control the initial
transmission power (e.g., for random access) of UE. The attenuation of the
transmission power of the BTS is analyzed by the UE as part of the control. The
original power of the BTS is radiated together with other system parameters as
broadcast information. The UE power is initially controlled on the basis of the
analyzed attenuation.
This initial control can only be coarse because the UL and DL attenuations (for FDD)
can differ.
64 MN3500EU50MN_0001
UTRA Open Loop Power Control
Start Transmission
1. UE measure the
power of the Node B
broadcast information
3. the transmit power

is controlled on this value
UE
RNC
2. Attenuation of the
Node B signal is analyzed
UE:
UE:TS
TS25.101/102
25.101/102(FDD/TDD)
(FDD/TDD)
PC: Power Control BTS:
BTS:TS
TS25.104/105
25.104/105(FDD/TDD)
(FDD/TDD)
TPC: Transmit Power Control PC types: TSTS
25.401
S/N: Signal to Noise PC-Typen: 25.401
Fig. 33 Open loop PC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
65
Inner loop power control

For Inner Loop Power Control the BTS or UE compare the quality of the received
signals with a specified value. This value describes the ratio of the (wanted) received
signal power (the signal) and the (unwanted) interference from other sources (the
noise) called the signal-to-noise ratio (S/N) or (S/N) def.
In the FDD mode, the Inner Loop Power Control is also referred to as a Closed Loop
Power Control because of the different frequencies used for UL and DL.
In closed-loop power control in the uplink, the base station performs frequent
estimates of received Signal- to- Interference Ratio (SIR) and compares it to a target
SIR. If the measured SIR is higher than the target SIR, the base station will command
the mobile station to lower the power; if it is too low it will command the mobile station
to increase its power.
The same closed-loop power control technique is also used on downlink, though here
the motivation is different: on the downlink there is no near-far problem due to the
one-to-many scenario. All the signals within one cell originate from the one base
station to all mobiles. It is, however, desirable to provide a marginal amount of
additional power to mobile stations at the cell edge, as they suffer from increased
other cell interference.
These commands are covered by the term Transmit Power Control (TPC). Values for
TPC are "Up" and "Down".
In the TDD mode, the BTS and UE independently control the power for themselves
according to the completed S/N measurements and specified values (S/N) def
because of the same frequencies used for UL and DL.
Outer loop power control

The specification of the (S/N) def values used in the Inner Power Control is made by
the Serving RNC (SRNC). The SRNC has access to estimates of the actual
transmission quality using measurement reports for Node B's and UE. The quality
can vary due to modified transmission conditions (e.g., UE speed). To assure
transmission quality, the SRNC must be able to vary the (S/N) def values.
66 MN3500EU50MN_0001
UTRA Inner Loop (Closed Loop) Power Control

4. Node B compare
the quality of the
received signal with
the S/Ndef
1. UE and Node B transmit
their measurements in TDD mode the
(measurement reports) UE and the Node B
to the RNC control the power
for themself
2. RNC set up S/N defined
values (vary for QoS, BER) 5. Node B and UE
3. RNC transmit values to command the other
Node B and UE side with TPC to
regulate the power
UE
RNC 4. UE compare the
quality of the
Node B received signal with
the S/Ndef
PC: Power Control UE:

UE:TS
TS25.101/102
25.101/102(FDD/TDD)
(FDD/TDD)
TPC: Transmit Power Control BTS:
S/N: Signal to Noise BTS:TS
TS25.104/105
25.104/105(FDD/TDD)
(FDD/TDD)
PC types: TSTS
PC-Typen: 25.401
25.401
Fig. 34 Closed loop PC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
67
13.1.1 UTRA power control – parameters

The UTRA FDD and TDD modes have different power control cycles and maximum
power stages of the UE.
Power control cycles

The UTRA FDD mode uses 1500 PC cycles/s for the Inner Loop Power Control.
Each timeslot (TS) has a Transmit Power Control (TPC) command.
The UTRA TDD mode flexibly uses 100 to 800 PC cycles/s for the Inner Loop Power.
The minimum number of 100 PC cycles/s is correlated with the duration of a frame
(10 ms). Depending on the frame configuration, up to 800 PC cycles/s may be
required for a subscriber.
Power classes and dynamic performance

The maximum power of the Node B (FDD & TDD) is vendor-specific. Dynamic
performance of 30 dB must be ensured. The power can be provided in PC stages of
1, 2 or 3 dB.
The UE has 4 power classes that differ in the FDD and TDD modes.
In the FDD mode, the maximum power of the UE classes is 2000 mW, 500 mW,
250 mW and 125 mW.
In the TDD mode, the maximum power of the UE classes is 1000 mW, 250 mW,
125 mW and 10 mW. The 10 mW class is used for unlicensed operation.
The minimum UE power should be about 0.04 µW. The power can be provided in PC
stages of 1, 2 or 3 dB.
TIP
3G TS 25.410 provides an overview of the different PC types. Power classes and
dynamic performance are described in TS 25.101 or 25.102 for UE (FDD or TDD), in
TS 25.104 or 25.105 for Node B (FDD or TDD).
68 MN3500EU50MN_0001
UTRA Power Control

••FDD:
FDD:1500
1500PC
PCcycles/s
Zyklen/s
(1(1TPC
TPCper TS)
je TS)
••TDD:
TDD:100
100- -800
800cycles/s
Zyklen/s
(100/s: perjeframe;
(100/s: frame;>100/s:
>100/s:
depends
von frame onKonfiguration
frame config.)abh.)
Fast
Power Control
→ UTRA capacity
Node B limited interference
max. power: → System stability
vendor-specific
PC stages:
1, 2, 3 dB (TDD)
1 (0.5) (FDD)
Dynamic perf.:
30 dB (TDD)
> 18 dB (FDD) UE
max. power (4 classes) :
• FDD: 2000 / 500 / 250 / 125 mW
• TDD: 1000 / 250 / 125 / 10* mW
UE:
UE:TS
TS25.101/102
25.101/102(FDD/TDD)
(FDD/TDD) PC stages: 1, 2, 3 dB
TPC: Transmit Power Control BTS:
BTS: TS 25.104/105(FDD/TDD)
TS 25.104/105 (FDD/TDD) min. power : 0.04 µW
* for unlicensed operation
Fig. 35 PC cycles
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
69
13.2 RAKE receiver

CDMA can benefit from multipath propagation of radio waves with the use of a so-
called RAKE receiver. The information for transmission reaches the receiver in
practice not only by direct "line of sight", but also via echoes from obstacles. Normally
this increases the noise level, a situation that is not desirable. The reflected
information passes over longer paths than the direct line of sight and is therefore
delayed. If the delay is longer than one chip, the receiver usually regards the
reflected information as undesirable noise. The use of RAKE receivers turns this
disadvantage to an advantage.
A RAKE receiver has a number of RAKE fingers. Each of these RAKE fingers
changes (by de-spreading) broadband signals with different delays from the same
source (i.e., with the same spreading code) back into user information by using the
spreading code. This can be done because the different RAKE fingers apply the
spreading code with delays.
The RAKE fingers obtain information from a so-called Matched Filter (MF) for the
synchronization required. The MF compares incoming information with predefined
data sequences. These sequences are shifted in time. If the incoming chip
sequences match the predefined sequences, a power peak is registered. Predefined
information and information in the UL / DL contain so-called pilot sequences or the
mid-ambles of the TDD bursts. The MF returns information on the delays of the
different user signals in this way. It also supplies information on the amplitude of the
different user signals.
The RAKE fingers are responsible for the de-spreading of the user signals received
by multipath propagation. The fingers also correct the information with regard to
phase and adapt the timing of the information.
Depending on the signal strength (MF information), the information components are
summed (Maximum Ratio Combining).
A strong signal consisting of multipath components is therefore obtained in this way
with a RAKE receiver.
70 MN3500EU50MN_0001
Multipath Propagation
Path 3
d3, a3
Path 1
d1, a1
Path 2
d2, a2
d: delay
a: attenuation
Fig. 36 Receive Signals
Matched Filter MF:

measures pilot signals RAKE Receiver
⇒ determines delay
multiple fingers for multipath components

Maximum
De- Ratio
Combining
Spreading
Code (t- d ) „Finger 1“ a 1

1
Σ
De-
Spreading
a 2
Code (t- d 2
) „Finger 2“
a 3
De-
Spreading
RAKE finger:
Code (t- d ) • Despreading(→ MF info.)
3 „Finger 3“
• Phase correction
• Delay correction
Fig. 37 Rake Receiver
MN3500EU50MN_0001
71
13.3 Multi User Detection (MUD)

Multi User Detection (MUD) and Interference Cancellation (IC) can be used for
clearing intra-cell noise. In doing so, the MUD / IC can
1) increase the capacity of the system. Different models indicate that MUD / IC can
theoretically increase the system capacity by a factor of 2.8 and
2) reduce the "near-far" problem.

The broadband information of all UE in a cell generated with the use of different
spreading codes is received by the receiver of a BTS (Node B). The information is
despread in the receiver using the same spreading code. MUD processes the signals
jointly in order to separate undesirable interference due to the other users in the cell
from the signal wanted. In this way, large parts of the intra-cell interference can be
separated from the overall signal and canceled: consequently Interference
Cancellation (IC). The desired signal of a specific user is clearly distinguishable from
the background. MUD therefore provides a much better signal to noise ratio (S/N).
Since the capacity of CDMA systems is mainly limited by interference (there is
however also a restriction regarding the number of available orthogonal codes),
MUD / IC contributes to an increase in capacity.
MUD / IC is a relatively complex method. It is consequently mainly recommended for
applications in the UL direction – i.e., in Node B. However, there are also studies on
the use of MUD / IC in user equipment (UE). The interferences of the most powerful
"disturbers" can be canceled at least.
72 MN3500EU50MN_0001
MultiUser
Detection MUD Node B
Interference Cancellation IC
MultiUser Detection MUD &
De- Data 1
UE 2: Spreading
Code 2 Code 1
De-
Data 2
Spreading
Code 2
De- Data n
UE n: Spreading
Code n Code n
UE 1:
Code 1
Node B MUD:
• mainly for UL (in Node B)
• reduces intra-cell interference
⇒ increases capacity
• alleviates the near-far problem
Fig. 38 Multi User Detection
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
73
13.4 Handover
13.4.1 UTRA handover
The criteria and procedures for performing handover in UMTS are similar to those in
GSM. The UE and Node B determine the quality and strength of a radio transmission.
The UE also determines the signal strength and quality of its own and the local BTSs.
The measurement values are compiled in a measurement report for use by the RNC
as a basis for deciding for or against handover. If handover is decided upon, the new
BTS is activated and included in the so-called active set. The RNC is responsible for
decisions regarding the acceptance or rejection of handovers, while the execution
(initiation of contact with the new Node B) is the responsibility of the UE.
74 MN3500EU50MN_0001
Handover
UE Measurement:
Connection quality and strength
+ strength of own & local Node B
Measurement: Measurement Report

Connection quality and strength
NODE B Processing of measured values

Measured
values
report HOV
decision
UMTS Handover Activation of new NodeB

• Decision-making similar to GSM Update of the active set
• Initiated by RNC RNC
• Performed by UE
Fig. 39 Handover in UMTS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
75
13.4.2 Hard handover

Hard handovers refer to handovers in which a mobile station (MS) transmits its user
information only via one base station at any one time. Up until the time of the
handover command, the MS communicates with the old base station over a specific
physical channel. After the handover command, the MS changes the physical
channel and then communicates with the new base station.
Hard handovers are used in GSM and in the following cases in UMTS:
• During TDD / TDD handovers
• During FDD handovers if the frequency (interfrequency handover) or the Core
Network is changed
• During inter-system handovers – for example, when changing from FDD to TDD
or from UMTS to GSM.
13.4.3 Soft handover

Soft handovers refer to handovers in which a mobile station (MS) transmits its user
information via more than one base station at the same time. Soft handovers can be
used in CDMA systems in order to prevent an increase in power of the MS in
boundary areas between different cells. This reduces the interference level and
therefore increases the capacity of the system. Moreover, the contact with more than
one base station ensures the connection to a moving MS in difficult terrain.
Soft handovers are used in the following cases in UMTS:
• During FDD / FDD handovers (without frequency changes).
76 MN3500EU50MN_0001
Hard Handover
UL
DL
UL
DL
• UTRA TDD
• UTRA FDD for:
• Interfrequency HoV (HCS)
• CN changeover
• Inter-System HoV
• FDD - TDD
• UMTS - GSM
Fig. 40 Hard Handover
Soft Handover
UL
DL
UL
DL
• UTRA FDD
Fig. 41 Soft Handover
MN3500EU50MN_0001
77
13.4.4 Soft handover

UE can communicate with two or three Node B during soft handovers in the UTRA
FDD mode due to the fact that all cells use the same frequency. If the mobile station
enters the boundary area between two or three cells, the RNC can decide that a
connection with two or three Node B is advantageous. The RNC reserves
corresponding codes in the different cells for the UE and commands the UE to
implement handover to the new Node B. As of this time, the information is handled by
the relevant Node B. The identity of the cells involved in the connection is stored in
the RNC as an active set.
The Node B's receive the transmission from the UE, despread it and forward the
information over the Iub interface to the RNC. The RNC combines this information
and forwards it via the Iu interface to the Core Network (CN). This procedure is
implemented frame for frame. The quality of the supplied frames is the basis for
assessment. Only information in frames with top quality is used.
The gain due to reception of additional signals in soft handovers is also known as
macro diversity.
In the opposite direction, the RNC splits the information from the core network and
forwards it to the different Node B's. During soft handover the UE receives the
transmission of the (apart from the TPC command) identical information from the
various Node B's. The transmission information from the Node B's is despread by
different RAKE fingers and combined (Maximum Ratio Combining – MRC).
78 MN3500EU50MN_0001
Soft Handover
Node B
Active Set:
Node B max. 3 cells
Iub
Node B
Iub
Active
Set CN
Combining/
Splitting Iub
RNC Iu
Fig. 42 Soft HO scenario
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
79
13.4.5 Inter-RNC handover

An interesting special case of soft handover is the inter-RNC handover. In this case,
the Node B's involved in the soft handover belong to different RNCs.
The RNC responsible for control of the soft handover is referred to as the Serving
RNC (SRNC). It combines information received from the different Node B's in the
direction of the Core Network (CN) or splits the information transmitted in the
opposite direction. It also stores information regarding the cells involved in the soft
handover (in an active set).
The other RNC responsible only for allocating radio resources is known as the drift
RNC (D-RNC).
Since the handover is to be controlled autonomously in UMTS by the UTRAN as part
of the Radio Resource Management (RRM), an interface is required between both of
the RNCs participating in the soft handover. D-RNC and S-RNC exchange signaling
information and user information via the Iur interface.
The S-RNC has no anchor functionality (comparable to an anchor MSC). The D-RNC
can adopt the function of the S-RNC with an S-RNC relocation procedure if
necessary. The previous S-RNC is then released. The link between both RNCs over
the Iur interface is no longer required. The link is directly handled by the participating
Node B (or Node B's) via the Iub interface using the new S-RNC and sent from there
to the CN via the Iu interface.
80 MN3500EU50MN_0001
Soft Handover
S-RNC: Serving RNC
D-RNC: Drift RNC
Inter-RNC HoV RR: Radio Resources
Node B
Iub
Node B
Node B RNC
Iub
Iub
Iur
Combining / RNC Active
splitting Set
Iu • S-RNC: Combining/splitting + RR allocation
• D-RNC: RR allocation only
• Changeover D-RNC → S-RNC
CN
Fig. 43 Inter RNC HO
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
81
13.4.6 Softer handover

Softer handovers are handovers between sector cells in the same Node B. The
transmission information received via the antennas of the different sector cells is
handled by different RAKE receivers and combined in the Node B itself (Maximum
Ratio Combining – MRC). Softer handovers are internal Node B affairs. Additional
(Iub) transmission capacity to the RNC is not required.
The gain due to reception of additional signals in softer handovers is also known as
micro diversity.
82 MN3500EU50MN_0001
Softer Handover Sector cells
Node B
• between sector cells

• Combining via RAKE
• Node B-internal
RNC
Fig. 44 Softer Handover
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
83
13.5 HSDPA - High Speed Downlink Packet Access

Support of HSDPA
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 2 - 3 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 16QAM) 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.
84 MN3500EU50MN_0001
Fast pipe is shared among

Terminals
Compared to 3G R99…
• Higher efficiency in transmission and error
correction (Hybrid ARQ)
• Higher data rates (Adaptive Modulation and
Coding, 16QAM/QPSK)
• Improved peak rate and reduced latency (15
parallel codes at 2 ms ) C
B,
A,
g
lin
du
che
S
NodeB w/ HSDPA
-A
H
DC -B
H
DC
-C
H
DC No switching of channels
Leads to reduced latency and
therefore to higher user
NodeB Rel. 99 w/o HSDPA acceptance
ARQ = Automatic Retransmission Request

Dedicated pipe for every Terminal
Fig. 45 HSDPA
MN3500EU50MN_0001
85
86 MN3500EU50MN_0001
14 Functionality of the network entities
UE RNS CN
ME
Iu CS
Node B RNC
USIM
Iu
P
S
Iur U-MSC
UE RNS
SC
Iu
ME
Node B
USIM
Iu PS
RNC
UE - User Equipment
Node B RNS - Radio Network Subsystem
RNC - Radio Network Controller
CN - Core Network
Uu Interface Iub Interface Iu Interface
Fig. 46 Network Elements
MN3500EU50MN_0001
87
14.1 User equipment

The User Equipment includes the mobile equipment i.e. the terminal equipment on
the one hand and the USIM or SIM on the other hand.
USIM
The USIM functions to save data and procedures in the terminal equipment. It
supports call handling, contains security parameters, user-specific data, e.g. tele-
phone directory entries, etc. The installed USIM is made available to the customer by
the network operator and can be updated e.g. via SMS or cell broadcasting.
Examples of USIM data and procedures
• Data:
International Mobile Subscriber Identity
Packet Switched Location Information
Security Information for authentication and ciphering for circuit and packet
switched applications
PLMN selector and HPLMN search period
Call meters
Display Languages
Telephone Directory
Forbidden PLMNs
Emergency Call Codes etc.
• Procedures:
Application related procedures
Security related procedures
Subscription related procedures
Mobile Equipment
The Mobile Equipment represents the partner of the Node B and of the RNC. I.e. it is
responsible for serving the radio interface. Some of the tasks of the Mobile
Equipment:
• CDMA coding and encoding
• Modulation demodulation on the carrier
• Power control
• Quality and field strength measurements
• Ciphering and authorization
Mobility management and equipment identification
88 MN3500EU50MN_0001
Data:
Data:
Preferred
PreferredLanguage
Language
International
InternationalMobile
Mobilesubscriber
subscriberidentity
identity
Call
CallMeter
Meter
Authentication
Authenticationand
andciphering
ciphering
Forbidden
ForbiddenPLMNs
PLMNs
Packet
Packetswitched
switchedLocation
LocationInformation
Information
Procedurers:
Procedurers:
Security
Securityrelated
related
Subscripton
SubscriptonRelated
Related
Data
DataDownload
Download
Image
ImageDownload
Download
85 298155
*V0179
59786 8
UMTS Subscriber
identity module
CDMA
CDMAcoding
codingund
undendcoding
endcoding
Modulation Demodulation
Modulation Demodulation
Power
Powercontrol
control
Quality
Quality and StrengthMeasurement
and Strength Measurement
Ciphering
Cipheringand
andAuthorisation
Authorisation
Mobility
MobilityManagement
Management
Equipment
EquipmentIdentification
Identification
Mobile Equipment
Fig. 47 User Equipment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
89
UMTS will be able to offer an extremely large variety of applications. The

conventional GSM services (bearer and teleservices) equivalent to the GSM Rel. '99
will be available. In addition, a large number of new services will become globally
available in the form of flexible bearer services with adaptable, dynamic data rates of
up to 2 Mbit/s thanks to the flexible definition of services allowed by the UMTS VHE
(Virtual Home Environment) concept.
As a result, the proven GSM telecommunication services, such as speech
transmission (with flexible rates – Adaptive Multi rate Speech (AMR)), SMS and fax
transmission along with data transmissions at low data rates will be possible in
UMTS.
In addition to this, UMTS will allow versatile applications, particularly in the area of
data transmission with medium and high data rates (simultaneous speech, image and
data transmission). Examples of the use of UMTS UE include the following:
• Company data transmission (e.g. teleworking, mobile offices, virtual work
groups, etc.)
• Information research (e.g. Internet surfing, online media, etc.)
• Education (e.g. virtual schools, online laboratories, libraries, viewing, etc.)
• Entertainment (e.g. games, music clips, video clip, etc. on demand)
• Public services (e.g. surveys, public voting)
• Telemetric services (e.g. navigation systems, fleet management, etc.)
• Financial services (e.g. mobile banking, online payment, USIM as credit card,
etc.)
• Special services (e.g. security, telemedicine, hotlines, etc.)
Buzz words and catchphrases such as "Internet for everyone", "multimedia services"
and "global, seamless roaming, anytime, anywhere, for everyone" indicate a huge
potential for applications that may not yet even have been conceived.
90 MN3500EU50MN_0001
Information Education
• Internet surfing • Virtual schools
• Intelligent search and • Online laboratories
• Filtering engines • Online libraries
• Online media • Online libraries
• Online translation • Online training
Financial services
• Online payment
• Universal SIM & credit card
• Telebanking Telemetrics
• Location tracking (GPS)
•Traffic information
•Fleet management
•Navigation
••
••
Special services •• Communications
• Security services •• • Video telephony
• Video conferences
• Hotlines
• Speech
• Telemedicine
• Personal localization
• Voice recognition
• Answering machine
• SMS
Public services Company
• Public elections Information Entertainment
• Surveys
• Virtual workgroups • Musik on demand
• Emergency calls • Video conferences • Games on demand
• Mobile offices • Video clips
• Teleworking • Virtual sightseeing
Fig. 48 UE Features
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
91
14.2 Node B
A Node B is a physical unit for implementing a UMTS radio transmission. Depending
on the sectoring of the cells, one (omni) cell or multiple (sector) cells can be serviced
by a Node B. Generally, up to six (60°) cells are serviced by a Node B in UMTS. The
UMTS system is however also open for the use of so-called intelligent antennae that
allow particular UE to be pursued, thereby providing even greater system capacity
(Space Division Multiple Access – SDMA).
A Node B can be used for Frequency Division Duplex (Uplink and Downlink
separated by different frequency bands), Time division Duplex (Uplink and Downlink
in different time slots) or dual mode operation.
A Node B converts user and signaling information received from the RNC for
transport via the radio interface, and in the opposite direction. This activity includes
safeguarding the information against loss in addition to preparing it for CDMA
transmission and Radio Frequency handling.
Node Bs are involved in power control. The Node B also measures the signal noise
ratio of the User Equipment, compares the value with a predefined one and instructs
the User Equipment to control its transmission power.
The Node B also measures the quality and strength of the links and determines the
Frame Error Rate.
92 MN3500EU50MN_0001
Node B
•Uplink
•UplinkDownlink
Downlinkcontrol
controlby:
by:
FDD
FDDororTDDTDD
•Up
•Uptotosix
sixcells
cellsare
areserved
served
•Power control
•Power control
•Signalling
•Signallingconvertion
convertion
•Error
•ErrorCorrection
Correction
•CDMA
•CDMATransmission
Transmission
•Quality
•Qualityand
andStrenght
Strenght
measurement
measurement
FDD Frequency division duplex

TDD Time division duplex
CDMA Code division multiple access
Fig. 49
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
93
14.3 RNC
The RNC is the central control unit in the Radio Network Subsystem for a flexible
number of Node B's. The RNC is linked with the Core Network (CN), the Node Bs or
other RNCs via the Iu, Iub and Iur interfaces.
The RNCs are independently responsible for Radio Resource Management (RRM) –
i.e., independent of the CN. RRM is taken to mean functions required for assigning
resources and maintaining links. The following are examples of RNC functions:
• Power Control
• Handover Control
• Ciphering/deciphering
• Protocol conversion
• Admission Control
94 MN3500EU50MN_0001
Node B RNC
Node B
Core
Radio Network Control Network
(RNC)
Node B
Power
Power Control
Control
Handover
Handover Control
Control
Cipering/deciphering
Cipering/deciphering
Protocol
Protocol conversion
conversion
RNC Admission
Admission Control
Control
Fig. 50 RNC functions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
95
14.4 Core network

The UMTS core network consists of the following components:
MSC - Mobile Services Switching Center
VLR - Visitor Location Register
HLR - Home location Register
AC - Authentication Center
SGSN - Serving GPRS Support Node
GGSN - Gateway GPRS Support Node
EIR - Equipment identification Register
SCP/CSE - Service Control point / Camel Service Environment
• UMSC
For Siemens architecture, the MSC is always combined with a VLR; i.e. for the
SIEMENS solution, no external B- interface exists. For UMTS for Siemens
architecture, the MSC and the SGSN are merged to form the UMSC. The
UMSC consists of one EWSD Switch APS version CS1.0 for the MSC/VLR
parts plus one MainStreetXpress 36190 / SSNC V13 for the SGSN parts and
the Iu CS interface. The Gb interface is covered with the aid of a
MainStreetXpress 36140 with Frame Relay/ATM adaption.
• GGSN
The GGSN is implemented via 1 or 2 MainStreetXpress 36140 combined with a
file server system based on the CompactPCI System Centellis4000.
• HLR Innovation
The HLR corresponds to GSM with integrated AC; i.e. between these two
entities, no external interface is specified. The HLR/AC is provided as
standalone solution or combined with the MSC-VLR. As a standalone solution,
the HLR/AC is implemented via the HLR Innovation, applications on the
Siemens/Fujitsu workstation with SUN operating system.
• EIR
The EIR can be implemented like the MSC /VLR via an EWSD switch APS
version CS1.0, although it has no interoffice trunk or it can be implemented by
an OEM product. The EIR is normally offered with a MSC/VLR or a
MSC/VLR/HLR/AC as an EWSD solution. Therefore the architecture of the EIR
will not be expanded upon any further.
• The SCP/CSE is normally implemented with workstations, such as the Siemens
RM600 or Siemens/FUJITSU GP7000 for instance. The SCP/CSE is not
covered in this course.
96 MN3500EU50MN_0001
Core Network (CN)

MSC/VLR
VLR
B
PSTN
A
Base Station MSC
Subsystem (BSS)
G MSC
Gb
F D HLR/AC
HLR-i
C
H
SCP/CSE EIR HLR AC
S
Iu C
Gf Gr Gc
Radio Network G GSN

Subsystem (RNS) Gn
Iu PS S GSN
Gi
Gp
UMSC
Fig. 51 Core Network
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
97
Exercise 1
Title: Important functions of the UMTS Network Elements
Objectives: Name the major functions of the UMTS NEs
Pre-requisite: none
Task
Answer the following questions
Query
I) Name 5 functions of the RNC.
II) What is the NodeB used for?
III) Which NEs you can find in the Mobile Core Network?
IV) Name 5 functions of the User Equipment.
98 MN3500EU50MN_0001
Solution
Title: Important functions of the UMTS Network Elements
Objectives: Name the major functions of the UMTS NEs
Pre-requisite: none
Query
V) Name 5 functions of the RNC.
Power Control
Handover Control
Ciphering/deciphering
Protocol conversion
Admission Control
VI) What is the NodeB used for?

Node B converts user and signaling information received from the RNC for transport
via the radio interface, and in the opposite direction. This activity includes
safeguarding the information against loss in addition to preparing it for CDMA
transmission and Radio Frequency handling.
VII) Which NEs you can find in the Mobile Core Network?
MSC
SGSN and GGSN
HLR
EIR
AC
MN3500EU50MN_0001
99
VIII) Name 5 functions of the User Equipment.
Power Control
Encoding and Decoding
Signal Quality and Strength measurement
Ciphering / Deciphering
Modulation / Demodulation
100 MN3500EU50MN_0001
Hardware introduction NodeB Platform 2 (PF2) Siemens/NEC
Hardware introduction NodeB Platform 2

(PF2)
Contents
1 Overview 3
1.1 NodeB product range FDD 4
1.2 NodeB Platform 2 (PF 2) modules 5
1.3 NodeB PF 2 common modules short description 6
1.4 Different modules and concepts 8
1.5 Main features NodeB Platform 2 10
1.6 Transport network layer characteristics 12
1.7 NodeB PF 2 racks and shelters 14
2 NodeB modules description 15
2.1 The Core Controller (CC) 16
2.2 Channel Coding Card (CHC) 30
2.3 Digital Radio Interface Card (DRIC) 44
2.4 Combined Amplifier and Transceiver module (CAT) 48
2.5 Macro Remote Radio Head (RRH-m) 52
2.6 Tower Mounted Amplifier (TMA) 58
2.7 Duplex Amplifier Multi-Coupler (DUAMCO) 62
3 The NodeB family 67
3.1 NB-440/441 overview 68
3.2 NodeB NB-880/881/881-HR 70
3.3 Macro Radio Server RS-880 74
3.4 NodeB 860 79
3.5 19“ Micro Radio Server (RSU-380) 84
3.6 Micro Radio Server (RS-381) 86
3.7 NodeB 580 88
3.8 NodeB NB-341 92
3.9 NodeB with SCC - mechanical architecture 95
4 Additional NodeB modules 101
4.1 Connection to the Iub interface 102
4.2 Connection to Ethernet - 4-port Ethernet Hub (EH4) 106
MN3500EU50MN_0001
1
© 2006 Siemens AG
Siemens/NEC Hardware introduction NodeB Platform 2 (PF2)
4.3 Alarm Collection Terminal Modules (ACT) 108

4.4 External Reset - Over-Voltage Protection for External Rest Line
(OERF) 112
4.5 Power supply and battery backup 114
4.6 The service2 shelter for NB-441 and NB-881 116
4.7 System expansion 122
5 Abbreviations 125
2 MN3500EU50MN_0001
© 2006 Siemens AG
1 Overview
MN3500EU50MN_0001
3
© 2006 Siemens AG
1.1 NodeB product range FDD
Overview of the UTRAN Product Range

Siemens/NEC UTRAN products provide a family of macro and micro FDD NodeBs
for area coverage as well as hotspot cells and a corresponding RNC:
NodeB Platform 1
• Macro FDD NodeB (NB-530)
Note: This platform is phased out with UMR5.0
NodeB Platform 2
• Micro FDD NodeB (NB-341)
NodeB 44x family

• Macro FDD NodeB (NB-440/NB-441)
NodeB 88x family

• Macro FDD NodeB (NB-880/NB-881/NB-881 HR)
The Radio Server family

• Macro Radio Server (RS-880)
• 19“ Micro Radio Server (RSU-380)
• Micro Radio Server (RS-381)
• Macro Remote Radio Head (RRH-m)
All types of NodeB incorporate features for the optimum re-use of the existing 2G
infrastructure, such as transmission links, operational procedures, and operation and
maintenance interfaces.
NEC/Siemens provide a complete family of NodeBs comprising FDD macro NodeB
for area coverage, NodeBs for mini and micro cells. All types of NodeB incorporate
features for the optimal re-use of the existing GSM infrastructure (e.g. transmission
links, operational procedures, O&M interface, etc.) in order to enable the smooth
introduction of UMTS in existing networks.
4 MN3500EU50MN_0001
© 2006 Siemens AG
1.2 NodeB Platform 2 (PF 2) modules

The system configuration of the NodeB PF2 contains the following units:
Common units:
Core Controller (CC)
Channel Card (CHC)
Duplex Amplifier Multi-Coupler (DUAMCO)
Over-Voltage Protection and Tracer (OVPT)
Alarm Collection Terminal Modules (ACT)
Cooling System (FAN)
Additional units:
Mains Supply Unit (MSU)
Heater (441/881 only)
AC/DC Rectifiers (441/881 only)
Battery Tray (441/881 only)
Smoke Detector (441/881 only)
Panels
Optional units:
Tower Mounted Amplifier (TMA/DTMA/SDTMA)
Direct Receive Module (DRX) for Smart Cell Configuration (SCC)
Power Splitter (PS) for SCC
Ethernet Hub (EH4)
Over-Voltage Protection for External Rest Line (OERF)
MN3500EU50MN_0001
5
© 2006 Siemens AG
1.3 NodeB PF 2 common modules short description

1.3.1 Core Controller (CC)
The CC handles signal transmission and data controlling of the base rack/shelter and
manages the data exchange with the RNC and the CHC. The CC has E-1 or E-1 and
STM-1 Interfaces. Up to 2 STM-1 lines are directly connected to the CC at the front
panel. Up to 16 E-1 lines are connected to the CC via Iub Connector (IUBCON) or
Overvoltage Protection and Tracer (OVPT) or IUB.
1.3.2 Channel Coding Card (CHC)

The CHC card is a base-band signal processing block mounted on the B-SHF. It per-
forms error correction coding and channel coding of transmission data. The CHC also
performs the de-spreading, chip synchronization, Rake composition, error correction
decoding, and de-multiplexing of received data. The CHC card can simultaneously
perform channel coding and decoding for both the traffic channel and the control
channel in one card. There are two types of CHC: CHC48 with 48 Coding Elements
and CHC96 with 96 Coding Elements.
1.3.3 Duplex Amplifier Multi-Coupler (DUAMCO)

The DUAMCO includes duplexers, low-noise amplifiers (LNA) and multi-couplers.
The duplexer combines the transmit and receive paths with the common antenna
connector. The duplex filter provides receive and transmit band filtering. The receive
path consists of an LNA followed by a power splitter providing four identical outputs
for the TRX units. The power supply and the signaling of the TMA are provided by the
DUAMCO via triplexers at the antenna outputs. The DUAMCORT and the
DUAMCORET are available for the NB-420/440/441 and NB-860/880/881/881-HR.
Both types have the same functionality. In addition, the DUAMCORET supports, in
combination with the DTMARET, DC supply and signaling function for a Remote
Antenna Down tilt unit.
6 MN3500EU50MN_0001
© 2006 Siemens AG
1.3.4 Tower Mounted Amplifier (TMA)

The TMA is installed outside the NodeB cabinet close to the TX/RX antenna. This
amplifier is optional but highly recommended as it compensates cable losses in
uplink and thus ensures lower noise disturbance. The result is an improved link
quality and link availability at cell borders. The TMA feeds the overall NodeB
downlink signal to one TX/RX antenna and filters the overall uplink signal coming
from the same TX/RX antenna. Due to the full duplex architecture of the TMA, only
one feeder cable is required for the TX and RX signal between the TMA outside and
the DUAMCO inside NodeB. The signaling interface between the TMA and the
DUAMCO is provided via the RF interface feeder connector by means of a triplexer.
Status information from the TMA is passed on to the O&M interface via this interface.
In addition to the TMA, a Dual TMA (DTMA) is provided for the NB-420/440/441 and
NB-860/880/881/881-HR. The DTMA includes two TMA units in a single housing and
is very efficient in combination with a cross-polarized antenna. A DTMA including
RET (Remote Electrical Tilt) control is available. Antennas with a remote down tilt
functionality improve the radio and baseband capacity by adapting the cell size to
different load scenarios.
MN3500EU50MN_0001
7
© 2006 Siemens AG
1.4 Different modules and concepts

1.4.1 REP-TRX-LPA concept of NB-420/440/441
This configuration consists of the following modules
• Repeater (REP)
• Transceiver Card (TRX)
• Linear Power Amplifier (LPA)
1.4.2 DRIC-CAT concept of NB-860/880/881/881-HR and RS-

880, RSU-380, RS-381
• Digital Radio Interface Card (DRIC12_12 and DRIC 24_24oe)
• Combined Amplifier and Transceiver Module (CAT20 and CAT40)
• Next Generation CAT (ngCAT)
1.4.3 Remote Radio Head RRH-m

• For NodeBs with DRIC24_24oe/CAT only
8 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 1 REP-TRX-LPA concept
Fig. 2 DRIC-CAT concept
MN3500EU50MN_0001
9
© 2006 Siemens AG
1.5 Main features NodeB Platform 2

The NB-420/440/441 and NB 860/880/881/881-HR have a modular structure and
operates up to 4 carriers in 1 cabinet (NB-88x only).
1.5.1 Configurations
The minimum configuration is one cabinet:
• NB-420/440 and NB-860/880 base rack for indoor installation,
• NB-441 and NB-881/881-HR base shelter for outdoor installation.
The outdoor cabinet consists of a double shelter. It includes a service area to

accommodate AC/DC modules, backup batteries and link equipment. The NB-441
and NB-881 offers a service2 shelter for installing further backup batteries and link
equipment. The NB-881-HR offers a triple shelter: A-Shelf, B-Shelf and AC/DC
modules are mounted in separate shelters.
A maximum of 4 sectors (1/1/1/1 with RS-880 and RRH only) is supported in a NB
single rack/shelter. Different cell configurations up to 2/2/2 are possible without
extension rack in a NB-440/441, in a NB-880/881/881-HR cell configurations up to
4/4/4 are possible without extension rack.
1.5.2 Coding Capacity

The base rack/shelter supports up to 960 channel elements (CE). The capacity is
highly scalable, i.e. it can be increased in steps of 48 CEs with CHC48 and 96 CEs
with CHC96 or hs-CHC.
The NB-420/440/441 is equipped with REP, TRX, and LPA modules (REP-TRX-LPA
concept), the NB-860/880/881/881-HR is equipped with DRIC and CAT modules
(DRIC-CAT concept).
1.5.3 CPRI
The interface between the CAT module and DRIC complies with the publicly
available Common Public Radio Interface (CPRI) specification. Using CPRI offers
the following benefits:
• Varying Radio Base Station architectures for very flexible solutions, e.g.
distributed architectures and remote tower mounted radio concepts
• Additional deployment scenarios
• Efficient network deployment
The CPRI interface specification is available for download from
http://www.cpri.info/spec.html
10 MN3500EU50MN_0001
© 2006 Siemens AG
1.5.4 Radio frequency band

The radio-frequency band for RX and TX signals includes
• 2110 to 2170 MHz for downlink signals
• 1920 to 1980 MHz for uplink signals.
A continuous spectrum within a 15 MHz band is supported. The maximum cell range
is 50 km.
For different markets, e.g. the US, there is a NodeB type named NB-580 to support
radio frequency (RF) bands for
In later releases the UMTS850 band will be supported as well within one NodeB type
NB-580.
1.5.5 Antenna system

Two linear-pole antennas or one cross-pole antenna are supplied for each sector.
The antennas can be complemented by one Dual Tower Mounted Amplifiers
(DTMA) or two Tower Mounted Amplifiers (TMA) per sector as low-noise
amplifiers.
1.5.6 Diversity
• RX diversity is a basic feature.
• TX diversity is optional (hardware-prepared).
1.5.7 RET
The NB-420/440/441 and NB-860/880/881/881-HR offers a remote down tilt
functionality consisting of a RET (Remote Electrical Tilt) module to adjust phase
shifts within the antenna. The result of the superposition is a variable tilt of the
resulting beam. This improves the radio and baseband capacity by adapting the cell
size to different load scenarios without any time delay.
MN3500EU50MN_0001
11
© 2006 Siemens AG
1.6 Transport network layer characteristics

The next table shows the transport network layer characteristics for the NB-
420/440/441 and NB-860/880/881/881-HR. For a detailed description of the UTRAN
Transport Network Management see TED:UTRAN common.
1.6.1 Transport Network

The RNC and the connected NodeBs can be arranged in a star, cascade, hub or loop
configuration (see TED:UTRAN common). The E1/J1 lines can be used with Inverse
Multiplexing for ATM (IMA) in all these configurations. IMA provides for transport of a
high bit rate ATM cell stream on several low bit rate physical links.
The NB-420/440/441 and NB-860/880/881/881-HR supports two forms of

transmission re-use for UMTS – GSM Co-location which are mutually exclusive:
• Circuit Emulation Service (CES)
CES offers a cost-effective way to co-locate NodeBs and GSM base stations
using a common ATM-based transmission network.
• Fractional ATM (FRAC)
Fractional ATM over circuit-switched networks (GSM) provides transport of Iub
timeslots.
For a detailed description see TED:UTRAN common.
12 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 3 Transport network layer characteristics for the NB-420/440/441 and NB-860/880/881/881-HR
MN3500EU50MN_0001
13
© 2006 Siemens AG
1.7 NodeB PF 2 racks and shelters

Following NodeBs are provided with the same type of racks (and shelters):
• NB-420 and NB-860
• NB-440 and NB-880
• NB-441 and NB-881/881-HR
14 MN3500EU50MN_0001
© 2006 Siemens AG
2 NodeB modules description
MN3500EU50MN_0001
15
© 2006 Siemens AG
2.1 The Core Controller (CC)

2.1.1 The Core Controller CC1/CC2
The Core Controller (CC1/CC2)
• supports signal transmission and data controlling of the base rack/shelter
• manages the data exchange with the RNC and the Channel Coding card
(CHC).
The CC consists of three mandatory boards and, one optional board:

• CPU board
• ATM board
• LIU (Line Interface) board for PDH (Plesiochronous Digital Hierarchy) lines
If an STM-1(o) interface is used on the Iub interface, a Core Controller equipped with
an additional
• STM-1 board for optical STM-1 must be used.
The following Iub connectivities are offered:

• 8 x E1/J1: at ports 8...15
• 16 x E1/J1: at ports 0...15
• 16 x E1/J1 and 2 x STM-1: at ports 0...15/ STM-1 ports 0..1
The Core Controller supports Inverse Multiplexing for ATM (IMA).
The RNC and the connected NodeBs can be arranged in a star, cascade, hub and
loop configuration (see TED:UTRAN Common).
A second CC may be inserted for redundancy reasons. Cold redundancy is
supported by most CC types and requires a certain firmware version.
The Clk-In interface can be used to synchronize the CC with an external clock (SMA
connector). The Clk-Out synchronizes the outer device with the CC clock. A standard
10BaseT Ethernet interface connects the CC to the outside world (i.e. the LMT -
Local Maintenance Terminal) via a twisted pair cable (CAT5). The external Ethernet
interface of the CC must have a unique IP address.
16 MN3500EU50MN_0001
© 2006 Siemens AG
Marking Description
first optical STM-1 interface, LC connector with RX0
PORT0
and TX0
second optical STM-1 interface, LC connector with
PORT1
RX1 and TX1
clock input to synchronize the CC to an external
SYNC-IN source; this functionality has to be activated in the
database
SYNC-OUT/ in case the SYNC-IN is activated, the SYNC-IN
TERM signal is forwarded to the SYNC-OUT port
ETHER standard 10Base-T Ethernet interface
electrical monitoring of the incoming TX and
MON
outgoing RX signals
General characteristics CC1/2

Dimensions [mm]
291 x 59 x 295
(length x width x height)
Weight [kg] 1.9
nominal: 45 (25 °C)
Power consumption [W]
max: 80
Duplex LC connectors for
Fiber connector at
small form factor optical
optical transceiver
transceiver
Fig. 4 CC (Example: CC-OMAFV1 (front view)
Details of the Core Controller’s boards are described below.
MN3500EU50MN_0001
17
© 2006 Siemens AG
CPU Board
The CPU board controls the whole NodeB. From the CPU’s point of view, the ATM
board, the LIU board and the STM-1 board are peripheral devices operated by the
operating system Linux. These peripheral devices communicate using either a
message passing principle or memory-mapped access. The main communication bus
inside the CC is the PCI bus. Configuration and data exchange with the LIU during
operation and the ATM processing are performed via the PCI bus. The three CAN
buses are used to send alarm messages, mount and supervise information.
ATM board
The CPU board is able to configure and exchange data with the whole ATM unit over
the PCI bus. A PCI bus bridge converts the PCI protocol to the individual bus
interfaces of the ATM devices.
The ATM board communicates with the LIU board by using 16 full duplex differential
lines. Two different PDH protocols are supported: E1 and J1.
Another major internal bus system between the ATM devices is the UTOPIA bus
interface.
The UTOPIA buses transport the AAL2 and AAL5 traffic between the lub and the
baseband units.
LIU board
The LIU board contains devices for:
• generating the line clocks
• amplifying the line signals
• jitter/wander attenuation
The clock unit selects the best clock source from various line interface units or from
an external clock source and synchronizes the OC-VCXO (Oven controlled - voltage
controlled xtal (crystal) oscillator) clock. All baseband clocks and other timing signals
for the BB are derived from the OC-VCXO reference clock.
The duplex device uses the UTOPIA bus interface for communication between the
ATM board and the BB boards on the B-SHF.
STM-1 board (optional)

The STM-1 board consists of two independent STM-1 interfaces. Just one STM-1
interface is used for the connection to the RNC. The other STM-1 interface can be
used to collect the traffic from other NodeBs, e.g., in a cascade configuration. The
transceiver modules transform optical information to electrical information and vice
versa.
The ATM framer device recovers the transmission clock, attenuates jitter and wander
effects on the line and, frames ATM cells. The ATM framer device communicates
with the ATM processing unit via a UTOPIA-2 bus.
The CPU exchanges data with the STM-1 board via a PCI bus system. A PCI bus is
also used for transporting configuration data and alarm or status messages. A PCI
bus bridge interfaces to the STM-1 framer devices.
18 MN3500EU50MN_0001
© 2006 Siemens AG
2.1.2 The Core Controller CC3

The Core Controller CC3:
• supports signal transmission and data controlling of the NodeB
• manages the data exchange with the RNC and the Channel Coding Card
(CHC).
The CC consists of three mandatory functional blocks:

• CPU functional block
• ATM functional block
• LIU (Line Interface Unit) block for SDH/PDH (Synchronous/Plesiochronous
Digital Hierarchy) lines.
If an STM-1/OC-3 interface is used on the Iub interface, a Core Controller equipped
with an additional STM1(o)/OC-3 board must be used.
The following Iub connectivities are offered:

• 8 x E1/J1/T1
• 16 x E1/J1/T1
• 16 x E1/J1/T1 and 2 x STM1/OC-3
• 2 x STM1
The Core Controller supports Inverse Multiplexing for ATM (IMA). The RNC and the
connected NodeBs can be arranged in a star, cascade, hub and loop configuration
(see TED:UTRAN Common). The loop configuration is only possible with additional
external SDH equipment.
A second CC may be inserted for redundancy reasons (cold redundancy).
The Clk-In interface can be used to synchronize the CC with an external clock
(1.0/2.3 connector). The Clk-Out signal is the same as the Clk-In signal and can be
used e.g. for the second CC. A standard 10/100Base-T Ethernet interface connects
the CC to the outside world (i.e. the LMT - Local Maintenance Terminal) via a twisted
pair cable (CAT5).
The external Ethernet interface of the CC must have a unique IP address. The
default IP address can be customized by using the serial interface (RS-232) during
system start or by data base.
MN3500EU50MN_0001
19
© 2006 Siemens AG
Details of the Core Controller’s four boards:
Mother board
The mother board comprises the CPU, ATM and clock generation functionality. The
Central Processing Unit (CPU) controls the O&M and C-Plane of the NodeB. It
handles basically the NBAP, ALCAP, and the O&M messages within the NodeB and
toward the RNC.
The ATM block

The ATM block is responsible for the complete ATM switching which also includes
the termination and conversation of the ATM adaption layers AAL2 and AAL5. The
master clock part is generating the NodeB internal clocks for the digital cards and RF
modules. It also distributes these clocks via the B-Shelf backplane to the
corresponding cards and modules. The high stable clock signals are realized by an
OC-VCXO [Oven Controlled-Voltage Controlled Xtal (crystal) Oscillator]. The
reference signal is taken from the LIU board(s) or the external clock synchronization
port.
E1/J1/T1 LIU boards

The LIU board contains devices for:
• Generating the line clocks
• Amplifying the line signals
• Jitter/wander attenuation
In addition to the physical line termination including the galvanic isolation and over
voltage protection, the E1/J1/ T1 LIU provides the following functionalities:
• Inverse Multiplexing for ATM (IMA)
• Circuit Emulation Service (CES) Fractional ATM
STM1/OC-3 board
The STM1/OC-3 board consists of two independent interfaces. Just one interface is
used for the connection to the RNC. The other interface can be used to collect the
traffic from other NodeBs, e.g., in a cascade configuration. The transceiver modules
transform optical information to electrical information and vice versa.
An ATM framer device recovers the transmission clock, attenuates jitter and wander
effects on the line and frames ATM cells. The ATM framer device communicates with
the ATM processing unit via a UTOPIA-2 bus.
The CPU exchanges data with the STM1/OC-3 board via a PCI bus system.
20 MN3500EU50MN_0001
© 2006 Siemens AG
Marking Description
first optical STM-1 interface, LC connector with RX0 and
PORT0
TX0
second optical STM-1 interface, LC connector with RX1
PORT1
and TX1
clock input to synchronize the CC to an external source;
SYNC-IN
this functionality has to be activated in the database
SYNC-OUT/ in case the SYNC-IN is activated, the SYNC-IN signal is
TERM forwarded to the SYNC-OUT port
ETHER standard 10/100Base-T Ethernet interface
electrical monitoring of the incoming TX and outgoing
MON
RX signals
standard 9-pin RS232 serial interface connector (for
RS232
debugging only)
TCLK test clock connector (for manufacturing process only)
General characteristics CC3
Dimensions 291 mm x 59 mm x 295 mm

(length x width x height) (11.5” x 2.3” x 11.6”)
Weight 1.5 kg (3.3 lbs.)
Power consumption [W] nominal: 30

at 25 °C (77 °F) nominal max: 40
Fig. 5 Core Controller CC3 (Example CC3E16S2V1 and CC3S2V1 front view)
Fig. 6 Block diagram of Core Controller CC3
MN3500EU50MN_0001
21
© 2006 Siemens AG
2.1.3 Core Controller redundancy

2.1.3.1 In general
The NodeB Core Controller Redundancy feature introduces a comprehensive redun-
dancy concept for the Core Controller (CC) of the NodeB PF2. Switchovers between
the active core controller and the standby core controller can either be initiated on
operator request or as an emergency switchover that is triggered via the Redundancy
Switch Control (RSC) if the active CC fails.
2.1.3.2 Customer benefits

This redundancy feature for the core controller improves NodeB availability
significantly by:
• minimizing service interruption for its own NodeB
• minimizing transmission interruption to associated NodeBs and GSM BTSs
An automated switchover is started as soon as a hardware or software failure has
been detected in an active CC. Maximum out-of-service time in this case is less than
6 minutes due to NodeB reset.
2.1.3.3 Switching between the Core Controllers

Radio Commander (RC) operators are always informed about the modes of both
CCs, to initiate a switchover when necessary. For a switchover, the active CC and
the standby CC have to be reset. Due to the restart of both CCs all connections
belonging to its own NodeBs are lost, as well as the connections to the collocated
NodeBs and GSM BTSs. Thus, a switchover leads to a transmission interruption,
because all information which is stored in the active CC (ATM and CES buffers) will
be lost and, the transmission protocols (CES and physical layer) need additional time
for resynchronization. The redundancy feature automatically aligns the OAM data of
the standby CC via the CC-Link.
The switching behavior depends on the current CC mode and on a certain action,
which can be triggered by either the operator or the CC software. Fig. 7 provides an
overview of a CC mode transition due to a certain action.
The basic concept for the E1/J1 line interface is illustrated in Fig. 8. Only the active
CC module is connected to the external and internal interfaces, while the inactive CC
is disconnected from the external and internal interfaces except for the CC link to the
active CC and the CAN bus.
The basic concept for the STM-1 line interface is illustrated in Fig. 9. Both CCs are
physically connected to the external interfaces via the optical splitter, thus both CCs
are capable of receiving ATM cells. Only the active CC is allowed to communicate
with the external/collocated Nodes. Internal interfaces are only connected to the
active CC.
22 MN3500EU50MN_0001
© 2006 Siemens AG
*) The startup behavior after system reset (push button) and power on is the same. During this startup the CC-
N is preferably the active CC if no error occurs. The CC-N is on the left hand side (of the B-Shelf) and comes
up first after reset, while the CC-E is on the right hand side and comes up second after reset.
Fig. 7 Overview of possible CC mode transitions
Fig. 8 CC redundancy concept for the E1/J1 interface
Fig. 9 CC redundancy concept for STM-1 Interface
MN3500EU50MN_0001
23
© 2006 Siemens AG
2.1.3.4 Redundancy and communication links

The two CC modules with identical functionality are installed in two different slots of
the NodeB’s B-Shelf, where one CC module is active and the other one is inactive i.e.
in standby, faulty or not-installed mode.
Both CCs are connected by the CC Link which is implemented as a twisted pair 100
Mbps Ethernet link that provides a communication interface between the two main
processors. A fail-safe mechanism prevents the active CC board from any
interference to a faulty CC module.
2.1.3.5 Redundancy switching behavior (based on RSC)

The redundancy switch control logic (RSC) on the CCs is responsible for the
switching process. It generates a signal indicating whether the unit is active or in
standby and switches the relays for the Iub interface and the line drivers of the
UTOPIA and clock distribution busses on and off. A switch logic link between the two
CCs controls the switching process. This ensures that only one CC can be active at
any one time which means that only the active CC is in receive/transmit state. The
standby CC is in receive state and its transmit process is suppressed. For this, the
transmitter of the standby CC must be switched off. The switch-off process is
controlled by the RSC.
2.1.4 Operation and maintenance (software-driven)

2.1.4.1 Redundancy concept
The OAM tasks of the NodeB are based on the hardware design. The essential
surrounding in which the switchover behavior is embedded consists of the switching
logic, the CAN Bus interface and the CC link. Only one IP address can be used to
access the CC. Consequently, the active CC can be directly accessed, the standby
CC only indirectly with the help of the active CC and the CC-link. This system
restriction must be considered when a software or database update is made on the
active CC. Due to the cold redundancy approach, the standby CC starts 10 seconds
later than the active CC. The active CC provide the required services and support of
any feature. The standby CC does not provide any service or support of any feature.
2.1.4.2 Reset and switchover behavior of the redundant CCs

The redundant CCs operate in so-called active / standby mode. A reset of one side
affects the other side in a different manner. That means a reset of the active side
causes a switching to the standby CC, whereas the reset of the standby CC does not
affect the active side. The standby CC restarts again in standby mode. A RC switch-
over procedure for the operator allows toggling of the active / standby side in order to
avoid a system wide impact when the active side is reset.
A reset caused by the internal fault management of the CC may lead to an
emergency switchover, see also chapter "Emergency Switchover Procedure".
24 MN3500EU50MN_0001
© 2006 Siemens AG
2.1.5 License Management for NodeB

Following the principles of “pay-as-you-grow” and “design-to-cost”, license
management provides the “rights-to-use” for both SW and highly integrated HW.
Thus, project-specific packaging of features can be offered to the customer.
Different types of licensing have to be distinguished:
2.1.5.1 Node B HW Capacity Activation Licensing (CAL):

• 1 license per 1 capacity unit, that means per 48 CE and per 1 cell
• Implemented as 1 key per RC area for CHC capacity and 1 key per RC area for
a number of cells
• Storage of activated license on ChC96, ngCAT, and DRIC board
Fig. 10 provides an overview of the Node B HW CAL concept.
Cases for HW licensing SAG/NEC Customer

License ordering X
License generation and delivery X

Lincensing application start up X
License import at licensing application host X
Display of available licenses within licensing application X
Display of licensed capacity and maximum capacity at Node B X
License activation at Node B X
Display summary of licensed capacity and maximum X X
capacity for a selected number of Node Bs
bulk license upgrade X
Fig. 10 Overview of the Node B HW CAL concept
MN3500EU50MN_0001
25
© 2006 Siemens AG
Design-to-cost measures result in highly integrated hardware with more capacity and
performance. Node B equipment (platform 2 only) can be contracted by the customer
without activating all its HW capabilities such as number of channels or number of
cells. Later the customer can activate some or all of these HW capabilities by
purchasing licenses from NEC/SAG. CAL provides an easy-to-handle process for the
customer to increase capacity and performance without further HW installation and
service effort.
A central function (Radio Commander) administrates the HW capacity licenses
(CAPLs). The additional license vouchers are provided per RC area and can be
downloaded to the relevant Node Bs. The vouchers can be used for any Node B and
can be purchased in bundles without specifying the Node B at ordering date. That
means, purchased licenses can be imported into the RC which then allows the
operator to activate a certain number of licenses on selected Node Bs without
knowing the existing installation exactly. For this purpose the RC can display
information on how many licenses can be activated on a specific Node B. Imported
license files are checked to fit the RC’s host ID ensuring that used licenses cannot be
imported or used a second time.
The licensing application also provides enhanced functionality for performing bulk
license upgrade. The capacity license upgrade procedure for several Node Bs can be
customized using an XML configuration file. In addition, the Licensing Application
picks the required license vouchers automatically, if more than one are needed, and
performs the upgrade for all selected Node Bs and boards sequentially as a batch
job.
The license information is stored locally on the relevant module where the licensed
capacity is valid. That means the license information is not centrally stored in a
specific Node B CC, which makes it possible to transfer this module to any other
Node B.
2.1.5.2 HSDPA throughput licensing:

• 1 license = peak data throughput of 2.4Mbps per cell (granularity)
• N = number of licenses per Node B (value range 0-60)
• Licensed HSDPA peak data throughput per Node B = N * 2.4Mbps (to be
equally distributed over the Node B cells)
• Maximum HSDPA peak data throughput per cell = 6 * 2.4Mbps = 14.4Mbps
(maximum N = 6 licenses per cell)
• Activation of HSDPA throughput licenses up to the maximum via RC/LMT
Formula to calculate HSDPA licenses and max. cell throughput:

2,4Mbps * factor = 2,4Mbps *3 = 7,2Mbps
26 MN3500EU50MN_0001
© 2006 Siemens AG
hsdpaModulation Number of HS- Throughput

PDSCH codes License
QPSK 5 codes 2.4Mbps * 1
10codes 2.4Mbps * 2
15 codes 2.4Mbps * 3 NodeB Core
16QAM 5 codes 2.4Mbps * 2 Controller
Setting
10codes 2.4Mbps * 4
15 codes 2.4Mbps * 6
Fig. 11 Setting the HSDPA throughput licenses with Radio Commander
HSDPA key file must be stored in LMT

PC root folder, otherwise read/write
license object not available
Fig. 12 Setting the HSDPA throughput licenses with LMT
MN3500EU50MN_0001
27
© 2006 Siemens AG
2.1.5.3 Man-machine interface

The redundant CC is included in the panels of the RC and the LMT. Operators are
informed about the mode of both CCs. RC and LMT both support the new action,
which is switching between the active and the standby CC. An additional alarm
message informs about the failure of a single CC.
28 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 13 Example of the OAM interfaces
MN3500EU50MN_0001
29
© 2006 Siemens AG
2.2 Channel Coding Card (CHC)

The main function of the CHC card is channel coding and decoding. It can
simultaneously perform channel coding and decoding for both the traffic channels
and the control channels (common channels) in one card.
On the uplink path, the CHC card receives and dispreads the uplink data transmitted
from the DRIC on the serial link. The CHC card de-codes the dispread data
depending on its symbol rate and channel type. The decoded data is transmitted to
the CC via the UTOPIA bus.
On the downlink path, the CHC receives and terminates the ATM-formatted data
transmitted from the CC via the UTOPIA bus. The CHC encodes the received data
depending on its symbol rate and channel type. The encoded data is transmitted to
the DRIC.
The CHC card equalizes the multi-path propagation via the rake receiver and
maximum ratio combining.
The B-SHF of the NB-880/NB-881/881-HR supports up to 10 CHCs. The required
number of cards depends on:
• the volume of bearer service capacity (traffic functions)
• the sectorization and cell range (control functions)
Three types of Channel Coding Cards:

• The Channel Coding Card CHC48 offering a processing capacity of 48 channel
elements and 72 AMR equivalent per card
• The higher integrated Channel Coding Card CHC96 offering a processing
capacity of 96 channel elements and 144 AMR equivalent (Adaptive Multi-Rate
equivalent) per card. The CHC96 also supports HSDPA, offering the same
processing capacity as in non-HSPDA mode. It simultaneously processes non-
HSDPA channels and HSDPA channels. In the first release HSDPA is
supported for 1 cell/sector in case of 2/2/2 configuration, only.
• The newly developed hs-CHC. The hs-CHC simultaneously supports HSDPA-
specific channels and functions as well as Rel. 99 channels. The hs-CHC’s
maximum performance is equal to 96 CEs and an AMREQ of 144.
For AMR services, the available CE are limiting the processing capacity, while for
higher data rates the available AMR equivalent are limiting the processing capacity of
the CHC.
The higher integrated CHC is fully hardware- and software-interface compatible to

the CHC48. The NB-880/881/881-HR principally can be equipped with a mixture of
higher CHC96 and CHC48.
30 MN3500EU50MN_0001
© 2006 Siemens AG
RACH resources for the uplink path and FACH/PCH resources for the downlink path
must be assigned to each cell. Generally, the required resources for the uplink path
are dominant.
The number of required RACH resources depends on the size of the cell radius R:
• R ≤ 5 km: 8 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 6 cells per CHC
• 5 km < R ≤ 20 km: 16 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 3 cells per
CHC
• R > 20 km: 48 CE/cell (CHC48) or 6 CE/cell (CHC96), max. 1 cell per CHC
Block diagram of the CHC
Fig. 14 Channel Coding Card CHCFV1 and CHCFV2
MN3500EU50MN_0001
31
© 2006 Siemens AG
Control and UTOPIA interface block

The control block consists of the main processor, peripheral ICs and memory units. It
performs UTOPIA interface control and overall intra-card supervision and control.
The control block exchanges control data with the CC card.
The UTOPIA interface block interfaces with the CC card and terminates the lub user
plane. On the downlink path, it receives transport channel data and control data from
the CC card and transfers it to the coder block. On the uplink path, it receives de-
coded data and control data from the de-coder block and transfers it to the CC card.
CAN block
The CAN block consists of a CAN microprocessor, a transceiver and a memory unit.
It performs supervision and control data communication with the CC card on a CAN
bus.
Coder block
The coder block receives downlink transport channel data from the UTOPIA interface
block and performs coding procedures. It sends the encoded data to the DRIC
interface block.
Searcher block
The searcher block receives uplink data from the DRIC interface block. It performs
channel path estimation, tracking, and RACH preamble detection. The searcher block
provides path information to the finger block.
Finger block
The finger block receives uplink data from the DRIC interface block, and performs
dispreading and rake combining based on the path information provided from the
searcher block. It sends the rake combined data to the de-coder block. The rake
receiver has 8 fingers.
Decoder block
The decoder block receives rake combined data from the finger block, and performs
decoding procedures. It sends the de-coded data to the UTOPIA interface block.
32 MN3500EU50MN_0001
© 2006 Siemens AG
2.2.1 Resource consumption rules

From a hardware point of view the channel card is structured into a number of
independent resource subpools.
The different resource pools are mutually independent. A dedicated channel has to
be completely placed into one of the downlink subpools whereas uplink subpools can
be pooled to support also bearers with 384 kbit/s uplink bit rate. CHC FV1 can
combine 2 uplink resource subpools and CHC FV2 can combine 3 uplink resource
subpools. Furthermore, an appropriate number of uplink subpools can be bundled
together for the support of common channels with larger cell range whereas downlink
common channels can be distributed over the two subpools. Each subpool could
handle common and dedicated channels when the CHC works in combined mode.
Furthermore, the resource requirements of common and dedicated channels is asym-
metrically because the common channels require mainly uplink processing resources
whereas the dedicated channels require mainly downlink processing resources (be-
cause the downlink rate is usually larger than the uplink rate).
This asymmetry of the resource requirements of common and dedicated channels
can be used to improve the resource utilization applying the combined mode. For
example, considering a scenario where 3 large cells have to be supported together
with bearers that have a data rate of 384 kbit/s downlink and 64 kbit/s uplink the
following allocation strategies could be supported:
• Strategy a:
1 CHC-C supporting the common channels of 3 large cells and additionally 2
CHC-T supporting 8 x 384 kbit/s data bearers
• Strategy b:
3 combined CHC-C/T each supporting the common channels of one cell and
additionally 4 x 384 kbit/s data bearers
Therefore, for strategy a 8 x 384 kbit/s can be supported whereas in strategy b 12 x

384 kbit/s can be supported. It can be shown that the distribution of common
channels over channel cards provides a higher total resource utilization than the
concentration of common channels on the minimum number of channel cards as long
as the downlink traffic is larger than the uplink traffic, which is usually the case.
Therefore, the common channels should be distributed over as many channel cards
as possible, i.e., we will only support strategy b. However the common channels
belonging to one cell are never separated, i.e. the different common channels of one
cell are always put together on the same CHC.
MN3500EU50MN_0001
33
© 2006 Siemens AG
2.2.2 Supported combinations

On a single CHC-C/T card the following common channel combinations have to be
supported:
• OTSR with normal cell size
• 1 normal cell
• 1 large cell
• 2 normal cells
• 2 large cells
• 1 normal cell + 1 large cell
• 3 normal cells
• 2 normal cells + 1 large cell
• 1 normal cell + 2 large cells
• 4 normal cells
• 5 normal cells
All other combinations either occupy a whole channel card or can be composed from
these basic configurations by several channel cards.
34 MN3500EU50MN_0001
© 2006 Siemens AG
2.2.3 Channel allocation strategy

2.2.3.1 Allocation of common channels between channel cards
The CC waits a certain time until most of the channel cards have finalized their boot
phase and then the CC decides how the channel cards will be initialized (common
channel allocation). This startup sequence is also beneficial with the CHC96,
because this card has different resource pools for common and dedicated channels
and therefore, the common channels can be allocated on a CHC96. The startup
sequence is illustrated in Fig. 15.
2.2.3.2 Allocation of common channels within a channel card

Besides the global allocation of common channels between channel cards, a channel
card internal resource allocation of common channels onto subpools is required. This
strategy should distribute the common channels over the two subpools to maximize
the number of high bit rate dedicated channels that can be supported.
2.2.3.3 Allocation of dedicated channels between channel cards

The following algorithms may be used for the allocation of DCHs to CHC-C/T channel
cards
• Load Balancing: The load with respect to the no. of occupied uplink channel
elements that are allocated for dedicated channels will be balanced. This
provides the lowest number of call losses when a CHC failure occurs
• Overflow Algorithm: The dedicated channels will be allocated with highest
priority (priority 1) on the first CHC, with priority 2 on CHC 2 and so on.
Minimizes the no. of call losses for new call requests
• More complex algorithms may be used when bearers with higher uplink than
downlink rates may become available
2.2.3.4 Allocation of dedicated channels on one channel card

The allocation of the dedicated channels onto a channel card is optimized by a
defragmentation of the resources. Therefore, no concrete algorithm has to be defined
here.
MN3500EU50MN_0001
35
© 2006 Siemens AG
2.2.4 Reallocation strategy

Since the dedicated channels are allocated in an arbitrary sequence the unoccupied
resources will be distributed over different channel cards and different subpools of
channel cards. Therefore, the resources have to be reallocated using the following
procedures:
• Channel card defragmentation
• Call context migration
These procedures have to be supported for the channel cards that serves dedicated
channels.
36 MN3500EU50MN_0001
© 2006 Siemens AG
Start CHC
setup
CHC resource Time out for

indication startup
Increase CHC Round robin allocation

number by one of common channels
on channel cards (only
allocation and
reservation
but no channel setup
no
CHC number > 0 ?
CHC number :=
CHC number -1
Initialize CHC and inform CHC about End of
allocated common channels (no setup) CHC setup
Fig. 15 Channel card initialization sequence
F a ilu r e
CHC-
CHC- CHC- ... CHC- CHC- ... CHC-
D is -
C /T C /T C /T C /T C /T
a b le d
C om m on D e d ic a te d
C h a n n e ls C h a n n e ls
Fig. 16 Redundancy handling of CHC-C/T (description on following page)
MN3500EU50MN_0001
37
© 2006 Siemens AG
2.2.5 Redundancy handling

The channel coding cards provide redundancy by means of load sharing. When the
combined mode channel card fails the following failure handling procedure shall be
applied (see Fig. 17) I.e., the common and dedicated channels are reallocated on the
remaining boards.
The reallocation shall fulfill the following requirements:
• Common channels shall be reestablished as fast as possible
• The number of common channels that have to be reestablished shall be
minimized
• The number of dedicated channels that have to be reestablished shall be
minimized
• Dedicated channels shall be saved if possible.
A unique procedure for the reestablishment of dedicated channels shall be

implemented irrespectively whether a channel card fails or is rebooted. When a
dedicated channel cannot be reestablished due to a lack of resources the NodeB
should send a radio link failure towards the RNC with the corresponding failure
cause.
In general the redundancy algorithm should minimize the impact on common and
dedicated channels in case of channel card failure.
38 MN3500EU50MN_0001
© 2006 Siemens AG
F a ilu r e
CHC-
CHC- CHC- ... CHC- CHC- ... CHC-
D is -
C /T C /T C /T C /T C /T
a b le d
C om m on D e d ic a te d
C h a n n e ls C h a n n e ls
Fig. 17 Redundancy handling of CHC-C/T
MN3500EU50MN_0001
39
© 2006 Siemens AG
2.2.6 HSDPA support with Channel Coding Cards

HSDPA requires a new type of CHC capable of handling both 3GPP Rel 99 traffic on
DCH and 3GPP Rel 5 HSDPA traffic on HS-DSCH.
This new CHC may either be an existing CHC96 whose FW is updated or a new
hs-CHC.
Both types of HSDPA-capable CHCs are able to handle both HSDPA and non-
HSDPA dedicated and common channels. A HSDPA-capable CHC is able to provide
HSDPA service for up to three cells. If both types of HSDPA-capable CHCs are in-
stalled in the same NodeB, HSDPA operation will only be possible on one CHC-type.
Additionally, HSDPA users of a particular cell for which HSDPA is enabled must not
be distributed on different HSDPA-capable CHCs. The HSDPA-capable CHCs are
furthermore currently operated in a non-redundant configuration. In the event of a
failure of the HSDPA-capable CHC, each SRNC either drops the HSDPA-related call
connections that are affected by the faulty CHC or switches them to DCHs by means
of channel-type switching (CTS). Then, NodeB will try to reconfigure the defective
CHC for HSDPA service. In this case the DL channel elements’ (CE) resources on
TRX/DRIC stay allocated without any change.
General rules
The following general rules must therefore be applied for a NodeB which is to offer
HSDPA service:
• The NB-44x’s and NB-88x’s B-shelf provides 10 slots allowing the installation of
up to 10 CHCs. For HSDPA, at least 1 HSDPA-capable CHC must be installed.
• Any mixed operation of the CHC48, the CHC96, and the hs-CHC is supported
for the NodeB’s non-HSDPA mode.
• When providing HSDPA functionality to a specific radio cell, only one type of
HSDPA-capable CHC, i.e. either the CHC96 or the hs-CHC, is permitted.
Mixed operation of both types of CHCs is not allowed in UMR5.0.
• One single HSDPA-capable CHC is able to handle up to three HSDPA cells.
• For each HSDPA cell, a maximum of 1 HSDPA-capable CHC is permitted.
• The total required number of CHCs depends on the traffic estimation.
40 MN3500EU50MN_0001
© 2006 Siemens AG
2.2.6.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 CHC96’s 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 (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.
2.2.6.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. Thus, the hs-CHC simul-
taneously supports HSDPA-specific channels and functions as well as normal chan-
nels. The hs-CHC’s maximum performance is equal to 96 CEs and an AMREQ of 144.
Manual intervention
There is a Reset and a Lock button to reset or lock the hs-CHC from the front panel.
Front panel indicators

The look and feel of the hs-CHC is the same as that of the pre-HSDPA CHC. The hs-
CHC indicates its state to the user, thus indicating the status of the card in terms of
• Administrative state (AST)
• Operational state (OST)
• Alarm status (ALS)
• Availability status (AVS)
MN3500EU50MN_0001
41
© 2006 Siemens AG
Man-Machine Interface
With regard to operation, administration, and maintenance (OAM) of the NodeB,
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 man machine interface for the operator
by offering the following:
• Front Panel Indicators
• Front Panel Connectors
• Manual Intervention
The hs-CHC visually indicates whether a module is providing HSDPA service.

Furthermore, the hs-CHC physically and logically controls the functionality of HSDPA
upon establishment and release of HSDPA processing resources.
In order to identify the hs-CHC, the card is provided with a new label.
42 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 18 Channel Coding Card hs-CHC
MN3500EU50MN_0001
43
© 2006 Siemens AG
2.3 Digital Radio Interface Card (DRIC)

The Digital Radio Interface Card (DRIC) provides a multiplexing, routing and splitting
function of the baseband signals and the spreading functionality in the downlink
direction.
The DRIC comprises 6 digital radio interfaces which are CPRI-compliant (Common
Public Radio Interface). Alternatively to normal redundancy, there is a HW-
preparation for 50/50 redundancy using the load sharing principle.
The control as well as the operation and maintenance information is received by the
DRIC via the UTOPIA or CAN interface and forwarded via the CPRI interface to the
CATs and/ or RRHs.
The NB-880/NB-881/881-HR can be equipped with the DRIC12_12 as well as with
the DRIC24_24oe. Since the DRIC24_24oe is downwards compatible, mixed
configurations are possible.
The two types of DRIC differ in the following way:
44 MN3500EU50MN_0001
© 2006 Siemens AG
2.3.1 DRIC characteristics
Fig. 19 DRIC12_12 Card (front view)
Fig. 20 Block diagram of the DRIC
MN3500EU50MN_0001
45
© 2006 Siemens AG
2.3.1.1 Characteristics of the CPRI interface

DRIC and CAT are solely linked by the CPRI. There is no extra clock line from DRIC
to CAT.
46 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 21 DRIF characteristics
Fig. 22 DRIC-CAT Interface Diagram and Characteristics of the CPRI
MN3500EU50MN_0001
47
© 2006 Siemens AG
2.4 Combined Amplifier and Transceiver module

(CAT)
The CAT module is a radio-frequency (RF) unit. On the downlink path it receives the
digital I/Q (Inphase/Quadrature) baseband signal from separate input I/Q data
streams via the CPRI from the Digital Radio Interface Card (DRIC). The CAT module
performs channel filtering, upconverts this signal to the required transmitting
frequency. This also amplifies the generated RF signal to a nominal output power
level at the 7/16 antenna connector of the DUAMCO.
On the uplink path, the CAT module receives RF signals from the DUAMCO,
downconverts the signals, and transmits the resulting I/Q data stream via the CPRI.
On the downlink path, the CAT works either as a single-carrier power amplifier or as
a multi-carrier power amplifier. The entire average output power capability is the
same in both cases.
The CAT module applies advanced amplifier concepts such as adaptive Digital
Predistortion (DPD). The CAT amplifies the downlink signal to a nominal level
depending on the type of CAT.
There are two types of CAT modules: CAT40 and CAT20, providing a different
number of TX and RX carrier paths.
The CAT40 offers a higher output power of 40 W and increased carrier capability
enabling additional cell configurations (hardware-prepared for up to 4/4/4 compared
to the CAT20. The CAT40 supports 2 independent RX paths each with dual carrier
capability (suited for dual carrier Rx-diversity).
CAT20 and CAT40 modules can be mixed within one NB-880/881/881-HR.
The NB-440/NB-441 can also be equipped with the next generation CAT ngCAT.
The ngCAT can operate either as CAT40 or as CAT20. It covers the full functionality
of the CAT40 but benefits from a higher efficiency and lower OPEX.
The ngCAT provides:

• at least 4 TX carrier paths
• at least 8 RX carrier paths
• 20 W or 40 W operation, depending on NodeB configuration
The ngCAT is HW-prepared to support future features like:

• higher bandwidth (60 MHz)
• additional antenna carriers per CAT
• additional cells per NodeB
48 MN3500EU50MN_0001
© 2006 Siemens AG
2.4.1 CAT20 / CAT40 characteristics
Fig. 23 CAT20 / CAT40 characteristics
2.4.2 RF interface characteristics of the CAT20/40 module
Fig. 24 RF interface characteristics of the CAT20/40 module
MN3500EU50MN_0001
49
© 2006 Siemens AG
2.4.3 Supported configurations using CAT40
2.4.4 Next Generation CAT ngCAT

The ngCAT is an optimized solution of the CAT40, operating with reduced power
consumption and enhanced RF performance. It provides either 20 W or 40 W at the
antenna port of the NodeB, depending on its configuration.
50 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 25 CAT20 module
Fig. 26 Block diagram of the CAT module
MN3500EU50MN_0001
51
© 2006 Siemens AG
2.5 Macro Remote Radio Head (RRH-m)

The macro Remote Radio Head (RRH-m) is an outdoor unit outside the NodeB/Radio
Server representing a highly integrated future proven solution for RF functionality.
Based on the technology leading Common Public Radio Interface (CPRI), the RRH-m
is fully compatible with the classic NodeB architecture. It can be connected to NB-
880/NB-881/NB-881HR, NB-860, RSU-380, RS-381, and RS-880. The RRH-m
comprises the complete RF functionality of a NodeB in one unit, equal to the three
modules CAT, DUAMCO, and TMARET.
The RRH-m is placed between the NodeB/Radio Server and two antennas. It
provides two CPRI-compliant optical interfaces for connection to the DRIC. This
requires a DRIC of type DRIC24_24OE which supports an optical interface in
addition to the electrical one. The RRH-m is controlled and monitored by the CC via
the CPRI interface.
The RRH-m offers the following features:
• One RRH-m serves one sector
• RET functionality is supported
• External alarms are supported
• TX-diversity using 2 RRH-ms per sector (hardware-prepared)
• CPRI cascading (hardware-prepared)
• Up to 3 RF carriers for operation within a bandwidth of 15 MHz
The RRH-m can be installed outside the NodeB/Radio Server in the following
ways:
• Pole mounting, below or behind antenna
• Wall mounting
• Roof top
For a detailed description please see TED:UTRAN RS-880/RRHs, TED:UTRAN

RSU-380/RRHs, and TED:UTRAN RS-381/RRHs.
52 MN3500EU50MN_0001
© 2006 Siemens AG
Ext. Equipment Service Panel
CPRI PSR RET DC

Antenna
TX Test
Fig. 27 Remote Radio Head, Interfaces and Connectors
Fig. 28 Block diagram of the RRH unit
MN3500EU50MN_0001
53
© 2006 Siemens AG
2.5.1 General characteristics of the RRH-m
54 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 29 Radio server RS-880 with RRH
MN3500EU50MN_0001
55
© 2006 Siemens AG
2.5.2 Cell configurations
Cell configuration NodeB Type variant Power/cell [W]

"1/0/0" 880/881 RRH 12,5
"1/1/0" 880/881 RRH 12,5
"1/1/1" 880/881 RRH 12,5
"2/0/0" 880/881 RRH 6,25
"2/2/0" 880/881 RRH 6,25
"2/2/2" 880/881 RRH 6,25
"1/0/0; 1/0/0" 880/881 CAT-RRH 20 ; 12.5
"1/0/0; 1/0/0" 880/881 CAT-RRH 40 ; 12.5
"1/1/0; 1/1/0" 880/881 CAT-RRH 20 ; 12.5
"1/1/0; 1/1/0" 880/881 CAT-RRH 40 ; 12.5
"1/1/1; 1/1/1" 880/881 CAT-RRH 20 ; 12.5
"1/1/1; 1/1/1" 880/881 CAT-RRH 40 ; 12.5
"2/0/0; 2/0/0" 880/881 CAT-RRH 20 ; 6.25
"2/0/0; 2/0/0" 880/881 CAT-RRH 20 ; 6.25
"1/1/1/1/0/0" 880/881 RRH 12,5
"1/0/0" 860 RRH 12,5
"1/1/0" 860 RRH 12,5
"1/1/1" 860 RRH 12,5
"2/0/0" 860 RRH 6,25
"2/2/0" 860 RRH 6,25
"2/2/2" 860 RRH 6,25
"1/0/0" RS RRH 12,5
"1/1/0" RS RRH 12,5
"1/1/1" RS RRH 12,5
"2/0/0" RS RRH 6,25
"2/2/0" RS RRH 6,25
"1/1/1/1/0/0" RS RRH 12,5
56 MN3500EU50MN_0001
© 2006 Siemens AG
2.5.3 Power Supply for Remote Radio Heads (PSR)
Power Supply for Remote Radio Heads (PSR)
Technical Data: PSR

• Nominal output voltage: –48 V
• Modular design with AC/DC controller and rectifiers
• AC/DC module: 1200W each, n+1 redundancy
AC/DC controller
AC/DC- Panel
AC/DC module
AC/DC module
AC/DC module
• Full lightning protection for AC and DC lines
BAT
• Battery back up time

- 120 minutes for 3 RRH typical operation
- 60 minutes for 6 RRH typical operation
- 40 minutes for 6 RRH worst case operation
• Alarming of PSR itself routed via RRH to O&M
(AC breakdown, battery breakdown, DC voltage out of
EMI Filter EMI Filter
range, high and Over temperature, over voltage on AC AC AC
or DC line, door open, fan
Physical characteristics: MSU

• Dimensions w x d x h = 770 x 500 x 760 mm
• Weight123 kg fully equipped
• Full outdoor capability
- Ingress protection IP55 Connection pannel
• Temperature range: -33 - +50°C
Fig. 30 PSR technical data and physical characteristics
ANT1 ANT0 RET
RRH RRH RRH
-48V, 0V CPRI
IPv4 data
connection
Optional for
redundancy
PSR alarms are -48/0V Data/ 802.3

mapped via RRH
Distribution alarms LMT
on CPRI 10Mbit/s
PSR
Radio Battery
AC/DC Backup
server
AC Input
Fig. 31 RS RRH PSR setup and alarming concept
MN3500EU50MN_0001
57
© 2006 Siemens AG
2.6 Tower Mounted Amplifier (TMA)

The TMA is an optional but highly recommended unit as it compensates cable losses
in the uplink and thus ensures lower noise disturbance. High selectivity filters ensure
high TX/RX isolation enabling the reception of low signal levels in the uplink. It
therefore improves link quality and link availability at the cell borders.
2.6.1 The TMA performs the following functions

• Amplifying the uplink signal received from the TX/RX antenna with a low-noise
figure. The receive path consists of a low-noise amplifier (LNA) and the RX part
of the duplex filters.
• Feeding the overall NodeB downlink signal transmitted to the TX/RX antenna.
The transmit path consists of the TX part of the duplex filters.
The LNA has two parallel gain elements:

• If a single failure occurs, operation continues with reduced gain.
• If both gain elements fail, or the supply of the TMA fails, the LNA is bypassed by
a fail-safe switch.
58 MN3500EU50MN_0001
© 2006 Siemens AG
2.6.2 There are four variants of TMAs

2.6.2.1 TMA
The TMA (see Fig. 32) is always installed outside the NodeB cabinet and close to the
antenna. The TMA thus achieves fixed sensitivity independently of feeder cable
length. With the DUAMCO acting as a combiner inside the cabinet, only one feeder
cable is required for the TX signal and RX signal. In addition, the feeder cable
supplies the TMA with 12 V DC and alarm signals.
2.6.2.2 DTMA
In addition to the TMA, a Dual Tower Mounted Amplifier (DTMA, see Fig. 32) is
provided for the NB-440/441 and NB-880/881/881-HR. The DTMA includes two TMA
units in a single housing and is very efficient in combination with a cross-polarized
antenna. The RET module is only contained in the DTMARET variant.
2.6.2.3 DTMARET
A DTMA including RET control (DTMARET, see Fig. 33) is available to support a
Remote Electrical Tilt (RET) module (2-wire bi-directional bus with 9.6 kbps). The
DTMA provides the interface to the DUAMCO and the RS485 interface to the RET
module. The IF converter in the DTMA evaluates and routes the signals coming from
the DUAMCO to the DTMA itself or to the RET module. The signals are sent via the
HDLC protocol. The RET module sends information and alarms on the RS485
interface via the DTMA to the DUAMCO. The RET capable DUAMCO receives/sends
the RET specific commands from/to the CC. The power supply of the RET module is
integrated within the DTMA. The nominal DC voltage for the DTMA and the RET
module is 12 V. The technical solution consists of an RET module containing a
stepper motor which adjusts a phase shift within the antenna. The stepper motor is
controlled via an RS485 interface connected to the TMA. Signaling and DC power
from the DUAMCO to the RET module via the TMA and vice versa is transported
through the antenna feeder cable. The stepper is located directly under the antenna.
For more information on the whole Remote Antenna Down tilt feature see
TED:UTRAN common.
2.6.2.4 Single Feeder Controlled DTMA (SDTMA)

The SDTMA has the same capabilities as the "Tower Mounted Amplifier (TMA)" plus
the following features:
• Support of DC power supply and SDTMAF signaling via one port for both TMAs.
• SW-preparation to switch automatically from dual feeder controlled to single
feeder controlled DTMA.
• RET functionality can not be used in “single feeder controlled mode”
For more details see Chapter 2.
MN3500EU50MN_0001
59
© 2006 Siemens AG
2.6.2.5 Summary
One TMA unit can handle UMTS downlink signals with a total signal RMS power of
+46 dBm and a signal peak power of +61 dBm.
The DC for the TMA/DTMA is supplied via the inner conductor of the NodeB 7/16
connector. The status monitoring and alarm signals are exchanged via the coaxial
feeder cable. The information is modulated on a carrier in a low MHz range.
60 MN3500EU50MN_0001
© 2006 Siemens AG
Concept of TMA and DTMA Block diagram of the DTMARET
Fig. 32 TMA and DTMA
Fig. 33 DTMA-F Characteristics of TMA/DTMA/DTMARET
MN3500EU50MN_0001
61
© 2006 Siemens AG
2.7 Duplex Amplifier Multi-Coupler (DUAMCO)

On the uplink path, the Duplex Amplifier Multi-Coupler (DUAMCO) amplifies the
receive signal from the antennas and splits it up to the diversity receivers. The
receive path consists of a Low Noise Amplifier (LNA) followed by a power splitter
providing four identical outputs for the TRX input.
On the downlink path, the signal received from the LPA is sent to the antenna. The
transmit path consists of a duplexer, a triplexer and an antenna-monitoring unit for
the TMAs. The triplexer provides the TMA’s DC power and the signaling to the RF
antenna feeder connection.
The duplexer combines the transmit paths and receive paths to the common antenna
connector. The duplex filter provides receive and transmit band filtering.
2.7.1 DUAMCOs for the NB-420/440/441 and NB-

860/880/881/881-HR
2.7.1.1 DUAMCORT
The DUAMCORT module consists of two electrically identical modules (0/1). Each
module has a transmit path and a receive path with a single connector for the
antenna feeder cable, i.e., one antenna connector per module is available.
2.7.1.2 DUAMCORET
The DUAMCORET has the same functionality as the DUAMCORT. In addition, it
supports, in combination with the DTMARET, DC supply and signaling function for a
Remote Antenna Down tilt (RET) module. A triplexer is integrated in one of the
antenna paths to provide these functions. The control and alarm signals of the RET
module are embedded within an HDLC protocol. The DUAMCO de-modulates the
messages and translates them into CAN protocol and vice versa. The gain of each
receive path is adjustable for an amplifier multicoupler (AMCO) configuration or
multicoupler (MUCO) configuration:
• MUCO mode
The MUCO mode is used if TMA units are installed. A built-in attenuator
ensures constant attenuation between the TMA and the DUAMCO
independently of cable losses.
• AMCO mode
The AMCO mode is used if no TMA is mounted. In this mode, the LNA in the
DUAMCO amplifies the uplink signal.
Operation and maintenance information such as alarms, status mode and PID is sup-
ported by a CAN bus. Calibration data is also accessible via a CAN bus allowing
compensation of the DUAMCO’s frequency response in the TRX modules.
RX outputs should be terminated if they are not used. Disconnecting an RX output
termination does not result in a serious loss in the other outputs.
62 MN3500EU50MN_0001
© 2006 Siemens AG
2.7.1.3 DUAMCOF for SCC

The modified DUAMCOF is equal to the Duplexer Amplifier Multi-Coupler
(DUAMCO) except the additional support of a single feeder controlled DTMAF
(SDTMAF) on the RX0 feeder port
In “single feeder control mode” the DUAMCOF does not provide RET control
functionality. Operation and maintenance information such as alarms, status mode
and PID is supported by a CAN bus.
Fig. 34 Duplex Amplifier Multi-Coupler DUAMCORTFV3
MN3500EU50MN_0001
63
© 2006 Siemens AG
2.7.2 Attenuation adjustment

Antenna cable type and length are decisive for the attenuation in the relevant
frequency spectrum.
The next page shows the appropriate formula to calculate the attenuation and the
attenuation adjustment.
The calculation of value is valid for all versions of DUAMCOs
64 MN3500EU50MN_0001
© 2006 Siemens AG
Attenuation part of the table is valid for all DUAMCOs, Attenuation Adjustment:
RET setting is valid for DUAMCOs with RET-option only Antenna cable type and length
are decisive for the attenuation
in the relevant frequency
spectrum.
The calculation of value is valid
for all versions of DUAMCOs
Fig. 35 Block diagram of DUAMCO with RX and TX diversity (DUAMCORT)
MN3500EU50MN_0001
65
© 2006 Siemens AG
66 MN3500EU50MN_0001
© 2006 Siemens AG
3 The NodeB family
MN3500EU50MN_0001
67
© 2006 Siemens AG
3.1 NB-440/441 overview

3.1.1 Features and technical data
Key features of the NB-440/441 include:
• High capacity: 1 rack/shelter (2/2/2)
• High power: up to 40W per carrier with Tx diversity
• RX diversity and TX diversity (hardware-prepared, optional)
The UMTS Terrestrial Radio Access Network (UTRAN) consists of NodeBs and
RNCs, as standardized by 3GPP.
NodeB links up to the RNC via dedicated E1/J1 and/or STM-1 connections. ATM is
used as the transmission protocol. Data traffic is packed into AAL2 cells, whereas
signaling traffic is transferred using the AAL5 protocol.
This chapter gives an overview of the main features, functional units and technical
data of Macro NodeB NB-440/441.
3.1.2 REP-TRX-LPA concept

Repeater card (REP)
The REP card is positioned between CHC cards and TRX cards to provide a
multiplexing function for the base-band signals.
Transceiver card (TRX)

The TRX consists of a Transceiver Baseband Block (TRX BB) and a Radio
Frequency Block (RF). The RF is subdivided into a Transmitter Block (TX) and a
Receiver Block (RX). The TRX BB spreads and scrambles digital signals received
from the REP. The TX uses a quadrature modulator to convert these base-band
spread signals into radio frequency signals. The RX performs coherent detection of
radio frequency signals received from the DUAMCO. The TRX BB converts and
demodulates them into digital signals. The TRX supplies high-precision digital
processing by high-speed sampling as fast as eight times the chip rate. Carrier
leakage in the TX part is prevented by applying a frequency offset to the base-band I
and Q signals to block DC, thus improving the TX ON/OFF ratio and modulation
accuracy. Carrier leakage in the RF part is minimized by the common local oscillation
circuit for the transmitter and receiver.
Linear Power Amplifier (LPA)

The LPA amplifies the transmitter radio frequency signals from the TRX to a specified
level for each sector. Operation and maintenance information such as alarms and
product identification data (PID) is supported by a CAN bus interface. The supplied
Multi Carrier Power Amplifier (MCPA) is designed for operation with one UMTS FDD
signal per carrier with a nominal output power of 20 W or two UMTS FDD signals per
carrier with 20 W as the nominal average output power, i.e. 10 W for each signal.
68 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 36 NodeB NB-440
Fig. 37 NodeB NB-441
MN3500EU50MN_0001
69
© 2006 Siemens AG
3.2 NodeB NB-880/881/881-HR

The modules DRIC (Digital Radio Interface Card) and CAT (Combined Amplifier and
Transceiver) are connected by a digital high-speed interface called the Common
Public Radio Interface (CPRI). The CPRI is already prepared to support Remote
Radio Heads (Tower Mounted Radio Concept).
The NB-880/881/881-HR is the Siemens UMTS FDD Macro NodeB, hence utilizing
W-CDMA technology.
The two versions for indoor usage (NB-880) and outdoor usage (NB-881/NB-881-HR)
grant the operator the flexibility needed for site acquisition.
The NB-880/881/881-HR offers a high upgradeability in terms of frequencies, sectors,
channel elements and features.
The NB-880/881/881-HR can be used for coverage, high mobility and speech-
oriented scenarios, as well as for high data traffic, small-cell and high capacity-
oriented deployments.
Maximum Configuration:
• Upgradeable up to 4/4/4@960VC and 6 sector configurations using Remote
Radio Heads
3.2.1 Applications and services

NB-880 is an UMTS-FDD Macro indoor NodeB.
NB-881 and NB-881-HR are UMTS-FDD Macro outdoor NodeBs.
This implies all applications and service aspects. Some of them are:
• Medium to large cells (0-50km)
• Medium to high capacity
• High mobility
• HSDPA for high downlink data rates (up to 14.4Mbps peak data rate under ideal
conditions)
• High variability due to additional support of Remote Radio Heads and usability
of different power amplifiers 20W and 40W output power.
• Customization of NodeB to the operators need possible
70 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 38 Functional overview for the NB-88x series and NB-880 base rack with DRIC-CAT
Fig. 39 NB-881 and NB-881 Shelter with reduced height (NB-881 HR)
MN3500EU50MN_0001
71
© 2006 Siemens AG
3.2.2 Key features and technical data

• up to 4/4/4 in one rack/shelf
• up to 960 cross VC in one rack/shelf,
• up to 80W per sector-80W per cell with TX-Div possible..
• RX diversity included, TX diversity HW prepared
• High flexibility in terms of line interfaces allow the operator to choose the right
capacity and features for rollout
• Advanced transport capabilities from the beginning to save transmission line
costs:
- Inverse multiplex access (IMA) for up to 2 times 8 E1 lines
- Fractional ATM and Circuit Emulation Service (CES) for co-location with GSM
equipment
- Star, chain and loop configurations including usage of STM-1 technology
• Redundancy for core controller (line interfaces) and DRIC card as well as load
sharing between channel cards minimize the downtime of NodeBs in the field
• Support of the standardized CPRI interface (future proven)
• Channel Card can handle both Traffic and Common Channels, this helps the
operator to utilize the baseband resources much better
• No dedicated reservation of resources for HSDPA required, improves the
flexibility and saves the investment
• Call Context Migration and CHC Defragmentation features increase the
efficiency of baseband resource usage and reduces the required number of
Channel Cards in the NodeB
• Very compact size:
- dimensions of NB-880: 1400x600x450
- dimensions of NB-881: 1499x1270x700
• Low level of TX Spurious emission ensures the isolation is easily reached in
case of GSM BTS collocation scenario
• Support of Remote Electrical Tilt (optional) reduces OPEX costs for the down tilt
adjustment and provides an alternative redundancy concept in operator’s
network. The RET functionality is from the beginning fully AISG compliant. The
standard interface helps to save CAPEX costs by the flexibility in the antenna
choice.
• HSDPA prepared, HSDPA enables high data rate downlink traffic applications
(up to several Mbps peak data rates).
72 MN3500EU50MN_0001
© 2006 Siemens AG
3.2.2.1 NB-880 base rack

Each NB-880 base rack consists of
• one Air Link Shelf (A-SHF)
• one Base Shelf (B-SHF)
Fig. 38 shows the front view of an NB-880 base rack for indoor application with
DRIC-CAT concept and the functional overview for the NB-88x series. The DC panel
is installed in the middle of the rack between the two shelves. For the indoor rack, the
functionality of the EMI panel is provided by the rack ceiling.
3.2.2.2 NB-881 base shelter

The outdoor cabinet NB-441 is a double shelter divided into two separate frames
which provides space for a service area.
Each NB-881 base shelter consists of
• Frame for service equipment
– one Air Link Shelf (A-SHF)
– one Base Shelf (B-SHF)
• Frame for service equipment
– AC/DC sub-rack
– Battery tray
– 6 HU (Height Unit) for link equipment (link equipment is optional)
Fig. 39 shows the front view of an NB-881 base shelter for outdoor application with
DRIC-CAT concept. The DC panel is installed in the middle of the rack between the
two shelves.
3.2.2.3 NB-881 Shelter with reduced height (NB-881 HR)

The NB-881 with reduced height is variant of the NB-881 with a shelter which height
is below 1.150 m. Shelter and base do not exceed 1.500 m. The NB-881 HR is
equipped with DRIC-CAT concept and features a 2 carriers/sector configuration.
Configurations with the RRH-m and RRH-p (HW-prepared) are possible as well as
the use of HSDPA.
The shelter is divided into three separate frames. The whole feature set, functionality
and configurations are offered like in the NB-881 with normal height. The height
reduction is achieved by distributing the boards/modules and panels of the NB-881
onto 3 racks within the shelter.
The height reduced NB-881 does not require neither an Extension Rack nor
additional Service2 Shelters for battery backup and LE.
Fig. 39 shows the front view of an NB-881 shelter with reduced height. The DC panel
is installed in the upper part of the middle rack. The EMI panel is located at the
bottom of the shelter.
MN3500EU50MN_0001
73
© 2006 Siemens AG
3.3 Macro Radio Server RS-880

3.3.1 Features and technical data
The devices feature a shelf design which allows for maximum scalability.
The Radio Server RS-880 provides the full functionality of the NB-880 in conjunction
with Remote Radio Heads. A complete base band shelf with DC-Panel is mounted
into a server rack reducing the acoustic noise emission and the necessary space for
installation. The RF functionality of the NodeB is incorporated in a Remote Radio
Head (RRH). The RS/RRH configuration represents a versatile NodeB architecture
for flexible site planning. RS and RRHs interact via the technology leading Common
Public Radio Interface (CPRI). Now, sites can be flexibly planned with Remote Radio
Heads (RRH).
RS/RRH configurations offer the following benefits:

• RS is centralized in a hotel and RRHs are distributed in the coverage area
• RS can be combined with Macro, Micro and Pico Remote Radio Heads (the
combination with Micro and Pico Radio Head in further releases)
• Flexible number of sectors and antenna sites
• Multi-site configuration (with softer HO)
• Reduced signaling and transmission costs due to softer HO
• Baseband (resource) pooling to reduce CAPEX costs
• Feeder loss in the downlink direction is diminished by the short distance
between RRH antenna connector and RRH. The uplink quality is also improved
superseding a TMA.
• Reduced power consumption and optimizations in operation and maintenance
• Easy site acquisition due to reduced requirements Radio Server locations
(flexible fiber optic cable, long distances between Radio Server and antenna
location possible, low acoustic noise emission for radio server)
Key features of the RS-880 with RRHs include:

• High capacity: 1 rack (1/1/1/1/0/0) or (2/2/2)
• High power: up to 12.5 W per RRH
• RX diversity (strongly recommended) and TX diversity (hardware-prepared,
optional)
NodeBs/Radio Server and RNCs form the UMTS Terrestrial Radio Access Network
(UTRAN), as standardized by 3GPP.
A Radio Server links up to the RNC via dedicated E1/J1 and/or STM-1 connections.
ATM is used as the transmission protocol. Data traffic is packed into AAL2 cells,
where as signaling traffic is transferred using the AAL5 protocol.
74 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 40 RS-880 indoor cabinet
Fig. 41 Block diagram of the RS-880 with RRH
MN3500EU50MN_0001
75
© 2006 Siemens AG
3.3.2 Main features

The RS-880 has a modular structure and operates up to 2 carriers in 1 cabinet in
conjunction with RRHs. The design is prepared for up to 3 carriers. The next Fig.
shows the system concept of Radio Server RS-880 and Remote Radio Head (RRH).
A maximum of 4 sectors is supported in a single rack. Different cell configurations up
to 1/1/1/1/0/0 or 2/2/2 are possible. The system is hardware-prepared to support up
to 12 sectors with 1 carrier by DRIC load-sharing or up to 6 sectors with 2 carriers
and DRIC redundancy.
The radio-frequency band for RX and TX signals includes
A continuous spectrum within a 15 MHz band is supported. The maximum cell range
is 50 km.
The rack supports up to 960 channel elements (CE). The capacity is highly scalable,
i.e., it can be increased in steps of 48 CEs.
The Radio Server Architecture is based on the publicly available CPRI interface
between Radio Server (RS) and Remote Radio Heads (RRH).
The CPRI interface is a unique radio driven interconnect point in radio base stations.
Using CPRI offers the following benefits:

• Varying Radio Base Station architectures for very flexible solutions, e.g.,
distributed architectures and remote tower mounted radio concepts
• Additional deployment scenarios
The DRIC24_24OE (Digital Radio Interface Card) enables the RS-880 to
provide the following features:
• Up to 24 antenna carriers (hardware-prepared) for uplink and downlink
• Support of optical CPRI-compliant interfaces by means of SFP (Small
Formfactor Pluggable) technology
• High spreading capacity of 3072 channel elements
• RX diversity is a basic feature. TX-diversity for every configuration, limited only
by the number of DL Antenna-carriers (hardware-prepared and optional).
• Capability of performing the 16 QAM-modulation scheme in order to support the
HSDPA feature.
The RET (Remote Electrical Tilt) functionality is fully integrated into the RRH.
76 MN3500EU50MN_0001
© 2006 Siemens AG
Iub Interface Configurations

The RNC and the connected Radio Servers can be arranged in a star, cascade, hub
or loop configuration. The E1/J1 lines can be used with Inverse Multiplexing for ATM
(IMA) in all these configurations. IMA provides for transport of a high bit rate ATM cell
stream on several low bit rate physical links.
System reliability
The following cards and modules are redundant to assure maximum system
reliability:
• Semi-hot redundancy for the Digital Radio Interface Card (DRIC)
• Cold redundancy for the Core Controller (CC)
• Load-sharing (pooling of the resources) for the Channel Coding Card (CHC)
The RS-880 supports an emergency configuration in the case of a mains power
supply loss. This mechanism enables the RS-880 to maintain the operation and
service as long as possible.
UMTS – GSM Co-location

The RS-880 supports two forms of transmission re-use for UMTS – GSM Co-location
which are mutually exclusive:
• Circuit Emulation Service (CES)
CES offers a cost-effective way to co-locate Radio Server and GSM base
stations using a common ATM-based transmission network.
• Fractional ATM (FRAC)
Fractional ATM over circuit-switched networks (GSM) provides transport of Iub
timeslots.
3.3.2.1 Technical data
MN3500EU50MN_0001
77
© 2006 Siemens AG
3.3.3 Hardware architecture

The configuration of the RS-880 consists of one rack containing the baseband
modules. The RF modules are located in the Remote Radio Head unit.
The RS-880 is equipped with one or two Digital Radio Interface Cards (DRIC). The
DRIC enables a CPRI-compliant digital radio interface to the Radio Equipment
integrated in the Remote Radio Head. The digital transmission via a fiber cable
reduces feeder and amplifier losses as well as noise.
The modules on the shelf are configured as follows, see Block diagram:
Digital Radio Interface Card (DRIC)

Channel Coding Card (CHC)
The functions and technical data are already described under "Main Features".
The RRHs with the dotted line are hardware-prepared.
The typical power consumption of the RS-880:
78 MN3500EU50MN_0001
© 2006 Siemens AG
3.4 NodeB 860

3.4.1 Main Features
Key features of the NB-860 include:
• High capacity: 1 shelf (2/2/2)
• High power: up to 40 W per carrier, RX diversity
RF features
A maximum of 3 sectors is supported in a single rack. Different cell configurations up
to 2/2/2 are possible.
The antennas can be complemented by one Dual Tower Mounted Amplifier (DTMA)
or two Tower Mounted Amplifiers (TMA) per sector as low-noise amplifiers.
The NB-860 supports up to 384 channel elements (CE) in UL. The capacity is highly
scalable.
The evolution is based on DRIC and CAT introducing the CPRI interface towards
Radio Server (RS) and Remote Radio Heads (RRH) on the same hardware platform.
The CPRI interface specification is available for download from

http://www.cpri.info/spec.html
Using the DRIC-CAT concept, the supplied Combined Amplifier and Transceiver
(CAT) with 40W(CAT40) or 20W(CAT20) output power is designed for operation with
• one UMTS carrier per antenna with a nominal output power of 40/20 W or
• two UMTS carriers per antenna with 40/20 W as the nominal average sum
output power, i.e., each carrier will be radiated with 20/10 W per antenna
(hardware-prepared).
The DRIC24_24OE (Digital Radio Interface Card) enables the NodeB 860 to provide
• 24 antenna carriers (hardware-prepared) for uplink and downlink
• Flexible support of electrical and optical CPRI-compliant interfaces
• Support of Remote Radio Heads in any mixed configuration with CATs
• High spreading capacity of 3072 channel elements in DL
• TX-diversity for every configuration
• Capability of performing the 16 QAM-modulation scheme in order to support the
HSDPA feature.
The RET (Remote Electrical Tilt) functionality is fully integrated into the NB-860.
MN3500EU50MN_0001
79
© 2006 Siemens AG
3.4.2 Hardware Architecture

The Macro NodeB NB-860 features compactness and flexible expandability with
modular shelf configurations. The highly integrated cards/modules/components
(especially CHC96 and the DRIC and CAT modules) noticeably reduce the system
complexity.
The configuration of the Macro NodeB NB-860 consists of one rack. This rack
contains only one shelf for both baseband and RF modules.
The NB-860 is equipped with DRIC and CAT modules (DRIC-CAT concept). The
Combined Amplifier and Transceiver (CAT) module integrates the transmitter and
receiver functions. The Digital Radio Interface Card (DRIC) comprises the spreading
functionality as well as the multiplexing, routing and splitting function of the baseband
signals in the DL.
A NodeB with a DRIC24_24OE can be connected to Remote Radio Heads (RRH) to
reduce feeder and amplifier losses.
In the DRIC-CAT concept, the modules on the shelf are configured as follows,
• Duplexer Amplifier Multi-Coupler (DUAMCO)
• Combined Amplifier and Transceiver Module (CAT)
• Digital Radio Interface Card (DRIC)
• Channel Coding Card (CHC)
• Core Controller (CC)
3.4.3 Rack and Shelf Configuration
80 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 42 NB-860 indoor cabinet (DRIC-CAT concept)
Fig. 43 NB-860 Function blocks
MN3500EU50MN_0001
81
© 2006 Siemens AG
3.4.4 Site Sharing

The Siemens/NEC UTRAN solution provides several kinds of equipment sharing to
deploy the UMTS network very quickly and efficiently. The most common kinds of
equipment sharing are site/mast sharing, NodeB sharing, and Core Network sharing.
Two NB-860 can be combined in a site-sharing configuration. Both NodeBs have
independent access to the -48 V power supplies. Each NB-860 has its own alarm
handling. However, the OMC indicates that the two NodeBs are combined.
The two NB-860 are mechanically connected by a coupling and distance-creating unit
that is not an integral part of the rack.
3.4.5 Co-Location
The Siemens/NEC UTRAN concept of collocation enables the operator to minimize
the number of sites by using UMTS equipment in combination with GSM base
stations.
The NB-860 can be combined with a 6-carrier Siemens BTS to form a collocation
solution for GSM/DCS and UTRAN-FDD equipment. In this configuration, the NB-860
is mounted on top of the BTS rack.
The NB-860 is mechanically connected to the BTS via a mounting device. This
device substitutes the top cover of the BTS and is open at the front and at the back.
The antenna cables of the BTS run from the top of the BTS to the back of the base
stations. Both base stations have independent access to the -48 V power supplies.
Each base station has its own alarm handling. However, the OMC indicates that the
NB-860 and the BTS are combined.
Maximum card configuration
82 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 44 Site-sharing solution of two NB-860
Fig. 45 NB-860 and 6-carrier Siemens BTS co-location solution
MN3500EU50MN_0001
83
© 2006 Siemens AG
3.5 19“ Micro Radio Server (RSU-380)

The Radio Server Unit is a low cost and zero footprint scenario for operators who
want to upgrade their existing GSM equipment to UMTS. The RSU-380 is a 19’’
module with a height of 3 HU which can be mounted into an already existing GSM
service rack by a minimum installation procedure. The RSU-380 is based on the RS-
880 technology, sharing the following modules:
• 1 CC3
• up to 2 CHC96
• 1 DRIC24_24oe
The Radio Server RSU-380 provides medium capacity in conjunction with Remote
Radio Heads (RRHs). The RF functionality of the NodeB is incorporated in a Remote
Radio Head (RRH). The RS/RRH configuration represents a versatile NodeB
architecture for flexible site planning. RS and RRHs interact via the technology
leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned
with Remote Radio Heads (RRH).
Key features of the RSU-380 with RRHs include:

• Max. configuration: up to 192 CES using 2 CHCs
• RSU-380: up to 1/1/1/1/0/0 configuration
• Operation with up to 4 RRH-m, 6 RRH-pi respectively (HW-prepared)
• Low weight (<15 kg)
• RX diversity supported by RRH-m and RRH-pi (HW-prepared)
• HSDPA
For a detailed description please see TED:UTRAN RSU-380/RRHs.
84 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 46 Radio Server Unit RSU-380
Fig. 47 Radio Server Unit RSU-380 block diagram
MN3500EU50MN_0001
85
© 2006 Siemens AG
3.6 Micro Radio Server (RS-381)

The Radio Server RS-381 provides medium capacity in conjunction with Remote
Radio Heads (RRHs). The RF functionality of the NodeB is incorporated in a Remote
Radio Head (RRH). The RS/RRH configuration represents a versatile NodeB
architecture for flexible site planning. RS and RRHs interact via the technology
leading Common Public Radio Interface (CPRI). Now, sites can be flexibly planned
with Remote Radio Heads (RRH).
The outdoor Radio Server RS-381 also contains the baseband part of the NB-88x
product line with same following modules: Core Controller (CC), Channel Coding
Card (CHC) and Digital Radio Interface Card (DRIC). It operates with the macro
Remote Radio Heads (RRH-m) and is hardware-prepared for micro and pico Remote
Radio Heads (RRM-pi).
The RS-381 is a solution for requirements of small to medium capacity and for zero
footprint locations.
Therefore it can be wall or pole mounted. The power supply of the NB-381 can either
be
• an AC-variant, feeding up to one RRH-m (optional battery box available)
or
• a DC-variant, provided by PSR (Power Redundant Supply). The PSR performs
an AC/CD conversion and enables a battery backup time up to 1 h.
Key features of the RS-381 with RRHs include:

• Max. configuration: up to 192 CES using 2 CHCs
• Capacity: 1/0/0 upgradeable to 1/1/1 and 2/0/0 configuration
• Operation with up to 4 RRH-m, 6 RRH-pi respectively (HW-prepared)
• Low weight (< 20 kg)
• RX diversity supported by RRH-m and RRH-pi (HW-prepared)
• HSDPA
For a detailed description please see TED:UTRAN RS-381/RRHs.
86 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 48 Radio Server RS-381
Fig. 49 Radio Server RS-381 block diagram
MN3500EU50MN_0001
87
© 2006 Siemens AG
3.7 NodeB 580

3.7.1 Features and Technical Data
The NodeB 580 covers the configurations for the US market.
In this framework the described NodeB functionality is limited to the frequency
division duplex (FDD) mode, macro cell coverage and UMTS1900 band.
The applied radio frequency (RF) bands are for
• Downlink: 1930 MHz – 1990 MHz (60MHz)
• Uplink: 1850 MHz – 1910 MHz (60MHz)
TX – RX Separation: 80 MHz
Due to the fact that in later releases the UMTS1900 and UMTS850 band will be
supported within one NodeB, a new NodeB type NB-580 is introduced.
The radio communications capability of a NodeB is strongly related with the number
of available sectors /cells.
3.7.2 Main Features

The NB-580 has a modular structure and operates up to 2 carrier frequencies in one
cabinet.
The Main Features are the same as for the NB-860.
Using the DRIC-CAT concept, the supplied Combined Amplifier and Transceiver
(CAT) with 40W(CAT40) or 20W(CAT20) output power is designed for operation with
• one UMTS carrier per antenna with a nominal output power of 40/20 W or
• two UMTS carriers per antenna with 40/20 W as the nominal average sum
output
power, i.e., each carrier will be radiated with 20/10 W per antenna (hardware-
prepared).
The NB-580 supports within the release UMR4.0 US only the 1900 MHz FDD
frequency band. Be aware that the NB-580 is the only NodeB supported within
UMR4.0 US.
88 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 50 NodeB-580 for 1900 MHz
Fig. 51 NodeB-580 for 850 MHz and 1900 MHz with two A-shelves
MN3500EU50MN_0001
89
© 2006 Siemens AG
3.7.3 Hardware Architecture

The B-Shelf of the NB-580 provides the following slots:
• 2 Core Controller slots
• 10 Channel Coding card slot
• 2 DRIC slots
Each A-Shelf of the NB-580 provides slots for:
• 6 CAT modules
• 3 DUAMCO modules
Please note that 850 MHz modules, as well as1900 MHz modules, fit only in their
belonging shelf.
3.7.4 B-Shelf Modules

For UMR4.0 US there are no new B-Shelf modules. Only the number of supported
modules for the NB-580 is reduced.
3.7.4.1 Core Controller Modules (CC)
Only the third generation of Core Controller Modules is supported within UMR4.0 US.
The Core Controller accomplishes the signal transmission and data controlling of the
NodeB NB-580 and manages the data transfer to the Radio Network Controller
(RNC) and the Channel Coding Card (CHC). Within UMR4.0 US the Iub-interface
supports only the T1-interface.
2 Core Controller Modules may be installed for redundancy purposes.
3.7.4.2 Channel Coding Cards (CHC)

The main functions of Channel Coding card (CHC) are:
• the channel coding & decoding procedure defined by 3GPP (Coder and
Decoder)
• the CDMA Rake Receiver function, incl. dispreading and combining of multiple
receive paths (Finger) and searching new propagation paths (Searcher),
receiving the Mobile Station Random Access Channel.
The NodeB NB-580 supports 2 types of Channel Coding cards:
CHC96FVx is able to support simultaneous HSDPA specific channels, as well as
Dedicated Channels (DCHs). The performance for Dedicated Channels (DCHs) is 96
channel elements and AMREQ of 144. HSDPA specific channels are not supported in
UMR4.0 US.
CHC-HS96FVx The High Speed Channel Coding Card supports simultaneous
HSDPA specific channels and functions, as well as normal channels. The
performance for Dedicated Channels (DCHs) is 96 channel elements and AMREQ of
144. HSDPA specific channels are not supported in UMR4.0 US.
90 MN3500EU50MN_0001
© 2006 Siemens AG
3.7.4.3 Digital Radio Interface Cards (DRIC)

The Digital Radio Interface Card combines the functionality of the former REP card
and the digital functionality of several TRX cards. The DRIC has 6 CPRI compliant
Digital Radio Interfaces for 6 CATs.
The B-Shelf of NB-580 provides 2 slots for installation of up to 2 DRIC cards.
• DRIC12-12FVX Provides 12 downlink paths and 12 uplink paths.
• DRIC24-24OEFVx Total capacity of 24 AxC in the DL – as well as in the UL-
direction.
3.7.5 A-Shelf Modules

Within UMR4.0 US two new A-Shelf 1900 MHz modules are introduced due to the
new supported frequency band in the range of 1900 MHz. The new modules are the
‘Combined Amplifier and Transceiver’ with 40W and the ‘Duplexer Amplifier Multi-
Coupler’ with Remote Electrical Tilt functionality.
3.7.5.1 Combined Amplifier and Transceiver

The CAT amplifies the downlink signal to a nominal level dependent of the type of
CAT. The different types of CAT provide a different number of TX and RX carrier
paths. The CAT is connected to the DRIC via the CPRI compliant Digital Radio
Interface (DRIF). The CAT is controlled and monitored via the DRIF interface by the
CC. The A-Shelf 1900 MHz of the NB-580 provides 6 slots for installation of up to 6
CAT modules.
CAT40-3-4UFVx
Combined Amplifier and Transceiver – Multi Carrier for up to 3 TX carrier paths and 2
independent dual carrier paths capable of supporting a dual carrier RX-diversity
scheme for operation within a bandwidth of 15 MHz in the UMTS1900 frequency
band.
The CAT amplifies the downlink signal to a nominal level of equal or less than
+46dBm (40W) measured at the antenna port of the NodeB.
1 CAT module is required at least for each sector.
3.7.5.2 Duplexer Amplifier Multi Coupler (DUAMCO)
The A-Shelf 1900 MHz of the NB-580 provides 3 slots for installation of 1 to 3
DUAMCO modules.
DUAMCORETUFVx
For 2 antennas with RX-Diversity, TX-Diversity and signaling for RET Module. The
DUAMCORETUFVx provides 2 (1 in each antenna branch) Filter RF input ports and
2 (1 in each antenna branch) Filter RF output ports.
TX-Diversity must be administered in the NodeB Data Base.
1 DUAMCORETUFVx is required for each sector
MN3500EU50MN_0001
91
© 2006 Siemens AG
3.8 NodeB NB-341
3.8.1 NB-341 modules

• 1 Power Amplifier (LPA)
• 1 DUAMCO and TX-Amplifier
• 1 Channel Card (CHC)
• 1 TRX
• 1 Core Controller (CC)
• 1 Mains Supply
• 1 Over Voltage Protection (OVP)
• 1 Maintenance Board (MAINT)
3.8.2 NB-341 concept

Identical look and feel for operation and maintenance
• Same Feature Set available for all NodeBs
• Reduces the spare part sizes, Reduces cost, simplifies training of service
people
3.8.3 Supported cell ranges

normal cell size and large cell size
for normal cells: search range of the searcher for RACH: 10km
usual cell range radius: 5km (8 CEs / 8 AMREQs needed for common channels in
UL).
for large cells: search range of the searcher for RACH: 20km
usual cell range radius: <20km (16 CEs / 16 AMREQs needed for common channels
in UL)
3.8.4 Channel capacity

Depending on the installed CHC: 48 or 96 CE
92 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 52 NodeB NB-341 w/o Booster and with Booster
Enclosure
-48 V
RF-Part BB-Part Mains
LNA Supply 48/110/230V
(1)
Duplexer/
TRX LVDS Mainte-
Uu Filter RF Cabling CHC
(1)
CAN 1 nance alarm
(1) (1)
LPA Board
CC
(1) (1) Over
UTOPIA II Bus (ATM)
Iub Voltage Iub
CAN2 Bus (O&M)
Protection
Clock Distribution Bus
Booster
Optional: 48/110/230V
(1)
Fig. 53 NB-341 Modules
MN3500EU50MN_0001
93
© 2006 Siemens AG
3.8.5 Performance
Frequencies :1
Sectors: 1/0/0 or omnicell, RX-Diversity
Output-power: max: 0,5 W w/o Booster, 10 W w/ Booster
Cell Radius: up to 10 km with Booster
Channel Elements: 48 or 96
Iub-Interface: Standard 2x E1/J1, optional 2x E1/J1 and 2xSTM-1, Fractional ATM,
Circuit Emulation Service CES, Configurations: star, loop, cascade, hub
3.8.6 Physical & Environment

Dimensions (H-W-D): 500x425x200mm3
Booster (H-W-D):190x420x200mm3
Weight:: Rack 30 kg, Booster 12 kg
Operation Temperature: -33 °C .. 45 °C
Power Supply: - 48 V DC or 100V/220-240V AC single phase
Power Consumption:
• NB-341 max 250/280 W DC/AC
• Booster max. 210/230 W DC/AC, Heater 340 W
Cooling: Passive Cooling with Heat Exchanger

Number of external Alarm Inputs/Outputs: 8/2
94 MN3500EU50MN_0001
© 2006 Siemens AG
3.9 NodeB with SCC - mechanical architecture

The NodeB with SCC consists of the following modules:
3 SDTMAs
1 CAT
1 DUAMCO
1 Power Splitter
1 DRX
1 DRIC (mandatory)
1 CHC96 (mandatory)
1 CC (mandatory)
Fig. 54 Mechanical architecture of the NodeB with SCC
MN3500EU50MN_0001
95
© 2006 Siemens AG
3.9.1 Single Feeder Controlled DTMA (SDTMA)

The SDTMA has the same capabilities as the "Tower Mounted Amplifier (TMA)" plus
• Support of DC power supply and SDTMAF signaling via one port for both TMAs.
• SW-preparation to switch automatically from dual feeder controlled to single
feeder controlled DTMA.
• RET functionality can not be used in “single feeder controlled mode”
3.9.2 Direct Receive Module (DRX)

The DRX module combines the functionality of the "Combined Amplifier and
Transceiver Module (CAT)" and the "Duplexer Amplifier Multi-Coupler (DUAMCO)"
without the TX-part. The DRX processes the received uplink signals of two sectors.
The DRX module characteristics are:

• RX signal delay equal to the sum of CAT40 and DUAMCOF
• Antenna connection 7/16 female
• Built in attenuators adjustable by 0 dB to 12 dB (1 dB steps), by help of DIP
switches
• Support of one single feeder controlled DTMAF on each RX feeder port
• RET capability (HW prepared for 4 RX)
• Lightening protection
• 8 signaling LEDs at the front panel:
– Power (1)
– Warning (1)
– Alarm int. (1)
– Alarm ext. (1)
– DRIC 0 (1)
– DRIC 2 (1)
– TMA (2), one for each antenna port
• ESD protection
• Power Consumption < 45 W
• Support of CPRI 614.4 Mbit/s electrical
• MTBF > 100000 h at air in take of +25 °C
96 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 55 Block diagram of the DRX module
MN3500EU50MN_0001
97
© 2006 Siemens AG
3.9.3 DUAMCOF for SCC

On the uplink path, the DUAMCO amplifies the receive signal from the antennas and
links it up to the CAT. The receive path consists of a low-noise amplifier (LNA).
On the downlink path, the signal coming from the CAT is sent to the antenna. The
transmit path consists of the TX part of the duplex filters, a VSWR monitoring unit
and a triplexer.
The duplexer combines the transmit and receive paths with the common antenna
connector. The duplex filter also provides receive and transmit band filtering.
The DC power supply and the signaling interface for the TMAs are provided and
applied to the RF antenna feeder connection via the triplexer.
The modified DUAMCOF is equal to the Duplexer Amplifier Multi-Coupler

(DUAMCO) except the additional support of a single feeder controlled DTMAF
(SDTMAF) on the RX0 feeder port
In “single feeder control mode” the DUAMCOF does not provide RET control
functionality.
Operation and maintenance information such as alarms, status mode and PID is
supported by a CAN bus.
3.9.4 Power Splitter

The Power Splitter (PS) is integrated into the A-Shelf.
The 3-way power splitter module PS divides the TX signal power into three equal
signals to support the SCC NodeB.
The Figure below shows the configuration of the PS module. It provides one antenna
port for the TX signal input / combined RX signal output and three antenna ports
(ANT0, ANT1, ANT2) for split TX signal output / RX signal input.
98 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 56 Block diagram of the PS
MN3500EU50MN_0001
99
© 2006 Siemens AG
100 MN3500EU50MN_0001
© 2006 Siemens AG
4 Additional NodeB modules
MN3500EU50MN_0001
101
© 2006 Siemens AG
4.1 Connection to the Iub interface

The NB-440/441 and as well NB-880/881/881-HR is connected to the Iub interface
via the IUBCON. The IUBCON can easily be replaced by the OVPT, an optional unit.
Both modules have almost the same functionality. However, only the OVPT provides
outdoor lightning protection via gas dischargers.
This section describes both modules.
4.1.1 Iub Connector (IUBCON)

The Iub connector module serves as a physical interface between the NodeB’s
internal modules and the Iub cables from the RNC or other external devices, e.g. the
LMT. The IUBCON is plugged in on the EMI panel.
The IUBCON module supports the following features:

• 8 Iub lines for uplink and downlink
• support of 120 Ω and 100 Ω symmetrical connections (twisted pair) or 75 Ω
coaxial connections
• external synchronization clock (coaxial connectors)
• monitoring of the lub lines and external clock synchronization
• lightning protection for the Ethernet interface
• stress relief (clamp blocks) and grounding facility for external cable and
shielding
The type of IUBCON depends on the cable used for the lub interface, either
• symmetrical lines with 100/120 Ω impedance, or
• coaxial lines with 75 Ω impedance
Two IUBCON modules can be installed on the EMI panel of a Base Rack/Shelter to
provide interfaces for 16 Iub lines.
102 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 57 IUBCON; Connector location
MN3500EU50MN_0001
103
© 2006 Siemens AG
4.1.2 Over-Voltage Protection and Tracer (OVPT)

The OVPT module provides the interface of the lub lines between the base cabinet
and the peripheral lub cables. The OVPT also protects the ports from overvoltage.
The module can be used instead of the IUBCON module and is located outside the
EMI shielding.
Two different connection types are possible at the lub interface:

• E1 2048 kbit/s 120 Ω
• J1 1544 kbit/s 100 Ω
The OVPT module supports the following features:

• lightning protection of lub lines and external clock synchronization
• current limiting as part of fine protection
• monitoring of the lub lines and external clock synchronization
• support of 120 Ω and 100 Ω symmetrical connections
• lightning protection for the Ethernet interface
• stress relief (clamp blocks) and grounding facility for external cable and
shielding
The OVPT module consists of two boards:

• one board for coarse protection (surge arrester) of the lub lines, the tracer
connector and protection for the Ethernet interface
• one board for fine protection (current limiting resistors) and the interface to the
EMI panel
The type of OVPT depends on the cable used for the lub interface, either
• symmetrical lines with 100/120 Ω impedance, or
• coaxial lines with 75 Ω impedance
For detailed information about respective connectors refer HWMN: NodeB

Cards/Modules.
104 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 58 left: OVPTE1J1SFV1 / right: OVPTE1CFV1; with Iub and Clock Interface
MN3500EU50MN_0001
105
© 2006 Siemens AG
4.2 Connection to Ethernet - 4-port Ethernet Hub

(EH4)
The 4-port Ethernet Hub (EH4) has the functionality of an Ethernet repeater hub. No
switching function is required.
The Ethernet Hub provides four ports for communication routing between:
Core Controller Redundancy (CC-Red)
Local Maintenance Terminal (LMT)
External Ethernet equipment
If additional devices are connected to the network, a second Ethernet Hub must be
installed. Thus, 6 ports are available for operational service. The Ethernet Hub EH4 is
a 10BaseT Ethernet repeater. The repeater function is contained in an integrated
circuit. The hub supports 4 RJ-45 ports with the same functionality. The ports and the
data input/output pins of the integrated circuit are galvanically isolated by
transformers. An integrated quartz oscillator provides the internal system clock.
Hence no synchronization to any NodeB clock is required.
The maximum power consumption of the EH4 is 5 W.
106 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 59 Example for a Ethernet Hub configuration
MN3500EU50MN_0001
107
© 2006 Siemens AG
4.3 Alarm Collection Terminal Modules (ACT)

The physical function of the ACT is to interface the alarm and command signals
between the CAN BUS and the alarm/command connectors of NodeB. The ACT is
not redundant, but the NodeB subsystem will still work even if the ACT fails.
The ACT functionality is provided by a set of modules:

• a processor board (ACTP)
• an interface board for external signals (ACTA)
• several interface modules for internal signals (ACTCB, ACTCS, ACTCS2)
The interface for operator-specific alarms (site inputs and site outputs) is supported
by the NodeB base rack/shelter. For this purpose, an ACT master module (ACTM)
is installed in each base rack/shelter. The ACTM module consists of an ACTP board
and an ACTA board. If no site inputs/outputs are required, an ACTP suffices.
The ACTCM, a different kind of master module, is required for controlling the alarm
collection in the service area of the NB-441 or NB-881/881-HR base shelter and the
NB-441 or NB-881/881-HR service2 shelter.
108 MN3500EU50MN_0001
© 2006 Siemens AG
ACTMFV1 (side view) ACTPV3 (front view)
ACTMFV1 (top view)
Fig. 60 ACTMFV1 - this module consists of the ACTAFV1 and ACTPV3 and is located at the EMI-Panel
Fig. 61 ACTCBFV1 with connectors
MN3500EU50MN_0001
109
© 2006 Siemens AG
The ACTCM consists of an ACTP board and an ACTCS board.
The ACTP performs the following tasks:

• interfacing the CAN bus
• collecting all alarms for units which have no access to the operation and
maintenance bus or to the CC
• collecting so-called cabinet-specific alarms (for example Door open, Smoke,
FAN)
• supervising the temperature via an external temperature sensor KTY19
• adjusting the rack address
The ACTA performs the following special tasks:

• collecting so-called operator-available alarms (24 site inputs and 8 site outputs).
• indoor lightning protection
The rack address is selected via a switch located at the ACTP board of the single
rack/shelter section.
The optional mounting kit OPEXAL can be used to prevent overvoltage on the
external alarm lines which are routed to the Alarm Collection Terminal Master
(ACTM) of the Base cabinet. The alarm interfaces of ACTM itself support the indoor
lightning protection level. Therefore, OPEXAL is only required for the rack
applications if outdoor lightning protection requirements shall be fulfilled.
For detailed information about respective connectors refer HWMN: NodeB

Cards/Modules.
110 MN3500EU50MN_0001
© 2006 Siemens AG
ACT modules in the NB-441 and NB-881 base shelter.

The same types of ACTM and ACTCB are used for the
NB-440 and NB-880 base rack.
ACT modules in the NB-441 and NB-881

service2 shelters.
The cabinet inputs of the ACTC can be used for
LE alarms, battery breaker alarms etc.
An ACTCM must be built in the first service2
shelter, while an ACTCS2 must be installed in
the other service2 shelters.
Fig. 62 ACT modules of NB-441 and NB-881/881-HR
4.3.1 ACTPV3 switch setting for rack-ID
Fig. 63 ACTPV3 Switch Setting for Rack-ID
MN3500EU50MN_0001
111
© 2006 Siemens AG
4.4 External Reset - Over-Voltage Protection for

External Rest Line (OERF)
If a fatal error occurs within the application software and the NodeB is stuck, a
remote restart of NodeB hardware can be initiated from the operation and
maintenance center via a discrete line.
The Over-Voltage Protection for External Reset Line (OERF) module protects the
modules of the NodeB which are connected to the external reset line against lightning
disturbance.
The OERF module is located in the EMI-Panel.
112 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 64 Over-Voltage Protection for External Rest Line (OERF)
MN3500EU50MN_0001
113
© 2006 Siemens AG
4.5 Power supply and battery backup

This chapter gives an overview of the power supply conditions including input power
and some examples of estimated power consumption.
4.5.1 Power supply

A nominal voltage of -48V DC (-40.5 V to -57.0 V) is required to operate the modules
of the NB-420/440/441 and NB-860/880/881/881-HR.
This DC voltage is delivered by
• an external (customer) power source for the base rack of the NB-420/440 and
NB-860 indoor cabinet
• the service area of the base shelter of the NB-441 and NB-881/881-HR outdoor
cabinet.
Any DC voltage other than the nominal -48 V DC required by specific boards is
generated onboard by a special power supply unit. DC/DC converter alarms are
processed on the modules themselves and forwarded to the CC board.
The DC supply of all service2 shelters that are connected to the same NB-441 and
NB-881/881-HR base shelter is limited to 25 ampere by a breaker. This value
includes all fans, ACTC and link equipment units installed in the service2 shelters.
NodeB is protected against over current/lightning, overvoltage and undervoltage.
4.5.2 Power consumption

For detailed information about power consumption refer TED: UTRAN NB440/441
and TED: UTRAN NB880/881.
4.5.3 Battery backup mode for NB-441 and NB-881/881-HR

At least one battery set must be installed in an NB-441 and NB-881/881-HR base
shelter to avoid distortion of the NodeB subsystem caused by a short interruption of
the AC mains supply. If the backup battery fails, operation continues as long as the
AC/DC converters supply the power.
In the case of AC mains interruption, the NB-441 and NB-881/881-HR base section
can be powered by a battery system consisting of up to 7 battery sets with 92 Ah
capacity each.
These battery sets are installed as follows:

• 1 x 92 Ah @ -48 V in the service area of the base shelter
• 3 x 2 x 92 Ah @ -48 V in three service2 shelters
With a DC power consumption of 3000 W and one battery set with 92 Ah installed in
the service area of the base shelter, a backup time of about 60 minutes can be
achieved.
For detailed information about Battery Backup Mode for NB-441 and NB-881/881-HR
refer TED: UTRAN NB440/441 and TED:UTRAN NB880/881.
114 MN3500EU50MN_0001
© 2006 Siemens AG
MSU:DC80AV3; terminals and connectors MSU:DC150AV1; terminals and connectors
Fig. 65 Power supplies for NB-440 and NB-880
MSU:AC1PHFV1; terminals and connectors MSU:AC3PHV2; terminals and connectors
Fig. 66 Power supplies for NB-441 and NB-881/881-HR
MN3500EU50MN_0001
115
© 2006 Siemens AG
4.6 The service2 shelter for NB-441 and NB-881

Additional battery backup
Additional height units for link equipment
Up to three NB-441 and NB-881Service Shelters can be installed to a NB-441 and
NB-881 Base Shelter.
4.6.1 AC/DC system for the NB-441 and NB-881

The AC/DC system for the NB-441 or NB-881 (outdoor application) consists of:
• 1 to 5 converter modules to achieve a DC power of 1600W up to 8000W.
• 1 additional converter module for redundancy purposes (N+1 redundancy)
• Controller board with battery supervision, rectifier supervision, and alarm
interface.
• Interfaces for AC Input, DC Output and Control Output
The number of AC/DC converters required in each AC/DC subrack depends on the
effective power required for the base shelter.
The AC/DC converter is used as a connection module if NodeB is directly supplied by
the AC mains. The AC/DC rectifier module converts the AC mains voltage (nominal
voltages 230 Vac) to the -48 V DC supply voltage.
The nominal DC output power of 1 AC/DC converter module is 1600W for + 50 °C
ambient temperature.
At least 2 AC/DC converter modules must be installed into the AC/DC subrack of the
NB-441 NB-881 base shelter, while up to 6 converters can be installed.
Each empty AC/DC slot must be closed with an appropriate cover (dummy module).
For the power supply, n+1 redundancy is implemented by N plus one AC/DC
converters that work in load-sharing mode. If one AC/DC converter fails, the
remaining N modules can supply the connected hardware without restrictions.
The maximum DC current is limited to 160 A to

• supply the NodeB equipment including link equipment
• to charge the backup batteries that are connected to the same AC/DC subrack
The charging current for all installed battery sets is limited by the DC battery
controller to 10% of nominal capacity of all installed battery sets with a maximum
value of 30 A.
116 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 67 left: AC/DCAV1; right: AC/DCDV1
Fig. 68 DC and Battery Controller DCBCTRLDV1
MN3500EU50MN_0001
117
© 2006 Siemens AG
The AC power supply for an NB-441 or NB-881 base station consists of:
• 1 base shelter with maximum module configuration and 6 LEs with a total power
consumption of 540 W (battery trickle charge)
• 3 service2 shelters:
– 1 service2 shelter with 2 HU link equipment, two battery sets and one fan
(power consumption: nominal 325 W, max. 370 W (battery: trickle charge))
– 2 service2 shelters with battery only and one fan per shelter
(power consumption: nominal 290 W, max. 380 W (battery: trickle charge))
118 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 69 DCBCTRLAV1
MN3500EU50MN_0001
119
© 2006 Siemens AG
4.6.2 AC/DC and battery system for outdoor application

The base shelter of the NB-441 and NB-881 for outdoor application includes a
service area containing:
• 1 AC/DC subrack
• 1 battery tray
• 1 frame (optional) for 6 HUs for link equipment
The installation of 1 battery set is mandatory. Up to 6 additional battery sets can be

added depending on the DC power consumption and the requested backup time.
The additional NB-441 and NB-881 service2 shelter provides space for
• 2 battery trays and additional HU (Height Unit) for link equipment or
• 1 battery tray and additional HU (Height Unit) for link equipment or
• additional HU (Height Unit) for link equipment
120 MN3500EU50MN_0001
© 2006 Siemens AG
Fig. 70 left: NB-441 and NB-881 Service2 Shelter (no Battery Unit); right: NB-441 and NB-881 Service2 Shelter for 2/2/2
configuration
Fig. 71 left: NB-441 and NB-881 Service2 Shelter (1 Battery Unit); right: NB-441 and NB-881 Service2 Shelter (2 Battery Units)
MN3500EU50MN_0001
121
© 2006 Siemens AG
4.7 System expansion

NodeB can be flexibly expanded to cope with increasing traffic.
The system can be expanded with any of the following expansion types or any
combination of them. The maximum possible expansion differs according to the
expansion type.
• Channel expansion
A maximum of 960 channel elements can be accommodated in an NB-440/441
or NB-880/881 system consisting of a base rack/shelter.
• Carrier expansion
A maximum of 2 carriers per sector can be assigned to an NB-440/441 or NB-
880/881/881-HR system consisting of a base rack/shelter.
• Sector expansion
A maximum of 3 sectors with 2 carriers can be assigned to an NB-440/441 or
NB-880/881/881-HR system consisting of a base rack/shelter.
A system expansion usually requires additional hardware modules. The following
features can be activated by pure software download/licensing from the LMT or OMC
(Operation and Maintenance Center):
• Number of cells supported by the DRIC
• Number of channel elements supported by the NodeB
For some expansion types, software and hardware has to be updated. Both hardware
and software expansions are described in this section.
4.7.1 Hardware expansion

Each type of hardware expansion requires specific units of equipment to be added.
See Fig. 72 for details concerning the DRIC-CAT concept and REP-TRX-LPA
concept.
The procedures for the different types of hardware expansion for the DRIC-CAT
concept are as follows:
Install additional CATs, DUAMCOs and TMA (optional). Connect the CAT with
the DUAMCO ports and add the additional TMA (optional but highly
recommended).
• Channel expansion
An additional CHC96 increases the capacity by 96 CEs: from 96 to 192 CEs or
from 192 to 284 CEs. Install a new CHC96 in a slot. Electrically connect the
card via the back plane.
• Carrier expansion
Install a new CAT in a slot. Install the RF connection via the front of the
rack/shelter and connect the module electrically via the back plane.
122 MN3500EU50MN_0001
© 2006 Siemens AG
After installation, a new card takes approximately 180 seconds before starting
operation.
The procedures for the different types of hardware expansion for the REP-TRX-LPA
concept are as follows:
• Channel / Carrier expansion
Install a card in a slot. Electrically connect the card via the back plane.
Install additional LPAs, TRXs, DUAMCOs and TMA (optional). Connect the
LPAs and/or TRX cards with the DUAMCO ports and add the additional TMA
(optional but highly recommended).
After installation, a new card takes approximately 180 seconds before starting
operation.
Units of expansion (DRIC-CAT concept)
Units of expansion (REP-TRX-LPA concept)

Fig. 72 Units of expansion
MN3500EU50MN_0001
123
© 2006 Siemens AG
124 MN3500EU50MN_0001
© 2006 Siemens AG
5 Abbreviations
MN3500EU50MN_0001
125
© 2006 Siemens AG
A
ALS Alarm Status
AMR Adaptive Multi-Rate
ASIC Application Specific Integrated Circuit
ATM Asynchronous Transfer Mode
AVS Availability Status
B
BTS Base Transceiver Station
C
CAN Controller Area Network
CC Core Controller
CC-BB CC-Base Board
CC-E Core Controller - Emergency
CC-N Core Controller - Normal
CE Channel Element
CES Circuit Emulation Service
CHC Channel Coding Card
CHC-C Channel Coding Card – Control
CHC-C/T Channel Coding Card – Control/Traffic
CHC-T Channel Coding Card Traffic
CMISE Common Management Information Service Element
CP Call Processing
CPICH Common Pilot Channel
CSI Core Shelf Interface
D
DL Downlink
DSP Digital Signal Processor
DTMA Dual Tower Mounted Amplifier
DTMARET Dual Tower Mounted Amplifier supporting Remote Electrical
Tilt
DUAMCO Duplexer Amplifier Multi Coupler
DUAMCORET Duplexer Amplifier Multi Coupler supporting Remote
Electrical Down tilt
126 MN3500EU50MN_0001
© 2006 Siemens AG
E
EEPROM Electrical Erasable Programmable Read Only Memory
EMI Electro Mechanical Interface
F
FACH Forward Access Channel
FRS Feature Request Sheet
G
GSM Global System for Mobile Communication
H
HDLC High-Level Data Link Control
HW Hardware
I
ID Identifier
IDT Inventory Data Table
IP Internet Protocol
ITU-T International Telecommunications Union – Tele-
communications Standardization Sector (formerly CCITT)
J, K
L
LIU Line Interface Unit
LMT Local Maintenance Terminal
LNA Low Noise Amplifier
M
N
NOB Remote Inventory File for equipment without onboard info
element
NodeB PF2 2nd platform NodeB
O
OAM Operation & Maintenance
OB-RIU Onboard Remote Inventory Unit
OEM Original Equipment Manufacturer
OMC Operating and Maintenance Center
OMC Operation and Maintenance Center
OST Operational State
MN3500EU50MN_0001
127
© 2006 Siemens AG
P
PAM Pulse Amplitude Modulation
PCH Paging Channel
PF Platform
PM Performance Management
Q
R
RACH Random Access Channel
RADAR Radio Detection and Ranging
RC Radio Commander
RC Radio Commander
RET Remote Electrical Tilt
RI Remote Inventory
RNC Radio Network Controller
RSC Redundancy Switch Control
Rx Receive
S
SBY Standby
STB Standby Status
STM Synchronous Transfer Mode
SW Software
T
TDM Time Division Multiplex
TMA Tower Mounted Amplifier
Tx Transmit
U
UL Uplink
UMR UMTS Release
UTOPIA Universal Test & Operations Physical Interface for ATM
UTRAN UMTS Terrestrial Radio Access Network
V, W, X, Y, Z
128 MN3500EU50MN_0001
© 2006 Siemens AG
RNC Hardware Siemens/NEC
RNC Hardware
Contents
1 Radio network control introduction 3
1.1 Network parts 4
1.2 RNC general features 6
2 cRNC and eRNC HW platform 7
2.1 RNC functional scheme 10
2.2 Principal modules of the cRNC frames 10
2.3 Principal modules of the eRNC frames 12
3 RNC Frames 14
3.1 Line Switch Frame (LSF) 16
3.2 Trunk Frame (TRKF) 18
3.3 Packet Radio Link Controller Frame (PRF) – (RNCplus-only) 22
4 General Modules of all RNC Frames 25
4.1 Fuse panel and Power Distribution Module (PDM) 26
4.2 Frame Temperature Sensor Unit (FTSU) 30
4.3 Fan Module (FANM) 32
5 RNC Structure 34
6 RNC Modules in LSF 37
6.1 Central processor module (CCPM) 38
6.2 HUB module 42
6.3 Line switch module (LSM) 44
7 RNC Modules in the Trunk Frame (TRKF) 51
7.1 The Composite De-composite Function 55
7.2 Wideband Composite Card (WCMP) 58
7.3 Composite Module (CMPM) for RNCplus only 64
7.4 Features related to E1 connected NodeB 74
7.5 MAC function 78
7.6 MAC Header Handling Module (MHM) 80
7.7 Mobile Layer-2 Control Module (M2CM) 84
7.8 Diversity Hand-over Trunk Module (DHTM) 86
MN3500EU50MN_0001
1
© 2005 Siemens AG
Siemens/NEC RNC Hardware
7.9 Signaling Module (SIGM) 92

7.10 GPRS Tunneling Protocol Module (GTPM) 96
7.11 Packet Radio Link Controller Module (PRM) 100
7.12 RNC Model Unit Overview 104
8 Examples of model units 107
8.1 Configuration of model unit eS 108
8.2 Configuration of model unit eS (STM-1) 112
8.3 Configurations of RNCplus 116
9 Additional information 119
9.1 Function assignment of the trunk modules 120
10 RNCi/RN-880 HW platform 127
10.1 Introduction 128
10.2 General RNCi Architecture 132
10.3 Hardware Architecture 142
10.4 General Hardware Platform 148
10.5 Blades 160
10.6 Features and Technical Data 175
2 MN3500EU50MN_0001
© 2005 Siemens AG
1 Radio network control introduction
MN3500EU50MN_0001
3
© 2005 Siemens AG
1.1 Network parts

One part of UMTS is the access network (Access Network Domain, AND), whose
task it is to enable mobile subscribers to access the UMTS-Core network. The AND
is implemented, in our case, by the UMTS Terrestrial Radio Access Network
(UTRAN). UTRAN provides the functions and protocols which serve voice and data
transfer within the AND and towards the Core Network. This includes the protocols at
the reference point Uu between UE (User Equipment) and the AND and the
protocols at the reference point Iu between AND and the transport network (Core
Network, CN). UTRAN forms the interfaces between the two reference points and
therefore contains the Uu- and the Iu- protocol stack.
The UTRAN consists of a number of radio subsystems (Radio Network Subsystem,
RNS), which are directly connected to the transport network CN via the Iu- interface.
The RNS is composed of a Radio Network Controller (RNC) and several Node Bs.
The Node B is a logical unit which is responsible for the radio transmission and
reception in one or several cells and which communicates with the RNC via the
interface Iub. The Node B realizes only the physical layer of the Uu-protocol stack
(Air Interface) to the subscriber side (User Equipment, UE).
Every connection between the UE and the UTRAN is administered by a RNC in the
Radio Network Subsystem (RNS). This RNC is known as the Serving RNC (S-RNC).
Should a connection use other radio resources from another RNC, e.g. in case of a
soft handover, then the RNC involved is described as the Drift Radio Network
Controller (D-RNC). The classification of an RNC as an S-RNC or an D-RNC
depends on the subscriber’s connection. A logical connection exists between the S-
RNC and the D-RNC at the reference point Iur, which is either an optional physical
line or physically mapped to the Iu-interface passing then transparently the CN. An
end-to-end connection between the UE and the CN exists only via the Iu-interface of
the S-RNC.
RNCs and Node Bs are standardized by 3GPP.
The functions of the RNCs are comparable to those of the BSCs in a GSM network,
and the functions of the Node Bs are comparable to those of the BTSs in GSM.
4 MN3500EU50MN_0001
© 2005 Siemens AG
User Equipment AND, UMTS Terrestrial Radio Access Network Core Network (CN)
RNS 1
RNC
RNC
Cell UMSC
UE IuCS - Interface
Node
NodeBB MSC
Cell
FDD MSC
FDD
UE Cell
UE
Node
NodeBB
TDD
TDD
Iur
Uu - Interface
RNS 2
RNC
RNC
Node
NodeBB
FDD
FDD
SGSN
SGSN
Node
NodeBB
TDD
TDD
IuPS - Interface
RNS...Radio Network Subsystem Iub - Interface
Fig. 1 UMTS network
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
5
© 2005 Siemens AG
1.2 RNC general features

Siemens/NEC’s RNC uses an evolved version of the field proven NEAX61Σ
Asynchronous Transfer Mode (ATM) Switch for its platform. The ATM Switch
platform allows flexible configuration in terms of processing power and of the
number and type of interfaces.
Key features of the NEC/ Siemens RNC solution are:
Most flexible configuration in terms of processing power and number and type of
interfaces;
Fully modular design with a distributed architecture based on a scalable ATM
switching node, a control processor, different interface units and a standardized
management interface;
Highest flexibility in terms of site location with installation directly at the UMSC or
decentralized in the UTRAN area;
High stability and reliability with use of N+1 or 1+1 redundancy. The main hardware
and software components are based on field proven ATM equipment;
Migration to a single RNC platform supporting UMTS, GSM and GPRS.
The functions of the RNC include:
Radio Network Management

Radio link control (radio resource management, outer loop power control, radio
bearer assignment/release, etc.)
Connection of multiple Node-Bs (configuration management, resource management,
radio control signal termination)
Connection to the Core Network (control signal termination)
Configuration management and control for Node-B’s in star or multidrop chain
configuration
Hand-over Control
Wired and wireless resource management and control for diversity hand-over (DHO)
Wired and wireless resource management and control for hard hand-over (including
that between frequencies)
Intra-Node-B hand-over control
Inter-Node-B hand-over control
Inter-RNC hand-over control
Inter-MSC & Inter-SGSN hand-over control
Traffic Statistics Management
Processing for traffic data collection and statistics for wired and wireless sections
Supervision/Control
Local supervision/control with OMC & IMAT (Intelligent Maintenance and
Administration Terminal) and MCSL (Master Console)
Supervision/control of Node B with OMC
6 MN3500EU50MN_0001
© 2005 Siemens AG
2 cRNC and eRNC HW platform
MN3500EU50MN_0001
7
© 2005 Siemens AG
In general a Radio Network Controller is named RNC. Since UMR3.5 there are
different types of RNC 's available. From the functional point of view the RNC types
are identical, but there are differences in hardware and capacity.
The first RNC is called cRNC (classic RNC) and the basic configuration consists of
three frames.
The second RNC is called eRNC (enhanced RNC). The eRNC basic configuration
consists of two frames.
A cRNC can be upgraded with additional hardware (WLSC, WCMP). This kind of
RNC is then called RNCplus.
NOTE
The classic RNC models cRNC are not any more supported in UMR5.0. All RNC
configurations based on the cRNC are upgraded with new hardware and are
called RNCplus.
All descriptions in this document about the cRNC are related to RNCplus
configurations.
8 MN3500EU50MN_0001
© 2005 Siemens AG
Width
700mm
? ? ?
FUSE
Full size
Module
Height Half
1800mm Module
FAN
FAN
Depth
600mm
LSF:Line Switch Frame LSF TRKF PRF

TRKF:Trunk Frame
PRF:Packet Radio Control Frame
Fig. 2 cRNC-Frame structure
Width
700mm
? ??
FUSE
Full size
Module
Height Half
1800mm Module
FAN
FAN
Depth
600mm
D-LSF:Line Switch Frame D-LSF H-TRKF

H-TRKF:Trunk Frame
Fig. 3 eRNC Frame structure
Dim ension Approx. 1,800 m m (Height) x 700 m m(W idth) x 600 mm (Depth)
W eight Less than 300 kg (fully loaded)
Maintenance At least 900 m m of free space at the front and rear of the fram e
Clearance At least 900 m m of free space to the sides of the fram e
Relative Hum idity 65±20 % , no condensation
Am bient Tem perature 5 to 40 °C
Noise 65 dB or below
Fig. 4 Frame technical data
MN3500EU50MN_0001
9
© 2005 Siemens AG
2.1 RNC functional scheme

The functional scheme of the Radio Network Controller (RNC) consists of various
function blocks. In each function block hardware components are configured, i.e.
cards and disks. To ensure hardware reliability, the RNC incorporates different levels
of redundancy for all of its hardware components.
Hardware components of the RNC are installed in frames. Each frame contains 4
shelves, in addition to fuse panels, cooling fan systems and cabling hardware. To
each shelf, one full-size module or two half-size modules are mounted, i.e. up to eight
half-size modules per frame. Cards and disks are plugged into the modules
according to the system configuration.
• The Fuse panel is located on the top stage of the frame. The size and number
of attached fuse panels to be mounted depends on the power consumption of
the modules loaded on the frame.
Cooling for the frame is provided by forced air-cooling fan systems. A standard frame
carries two fan systems, where the mounting position of the fan systems depends on
the heat generation of the modules installed in the frame.
2.2 Principal modules of the cRNC frames

The RNC is a modular system, providing upgrade possibilities from a small
configuration to a large configuration by adding necessary modules. The number and
layout of the frames depends on the system capacity and configuration required by
the customer.
The basic configuration of a cRNC consists of 3 frames:

• Line Switch Frame (D-LSF)
• Trunk Frame (H-TRKF)
• Packet Radio Control Frame (PRF)
10 MN3500EU50MN_0001
© 2005 Siemens AG
LSM
GTPM
From/To 156 M
CN/RNC
From/To 156 M PRM
Node-B
E1 D-CMPM
From/To
Node-B E1
DHTM
C-CMPM
SIGM
MHM
M2CM
CCPM
LSF TRKF PRF
D-CMPM Composite/Decomposite Module Type D

DHTM Diversity Handover Trunk Module
C-CMPM Composite/Decomposite Module Type C
SIGM Signaling Module
MHM Mac Header Handling Module
M2CM Mobile Layer-2 Control Module
LSM Line Switch Module
PRM Packet Radio Link Control Module
GTPM GPRS Tunneling Protocol Module
CCPM Central Control Processor Module
Fig. 5 Principal modules of the cRNC frames
MN3500EU50MN_0001
11
© 2005 Siemens AG
2.3 Principal modules of the eRNC frames

The eRNC is a modular system as well, providing upgrade possibilities from a small
configuration to a large configuration by adding necessary modules. The number and
layout of the frames depends on the system capacity and configuration required by
the customer.
The basic configuration of an eRNC consists of 2 frames:
• Line Switch Frame (D-LSF)
• Trunk Frame (H-TRKF)
12 MN3500EU50MN_0001
© 2005 Siemens AG
LSM
GTPM
From/To 156 M
CN/RNC
From/To 156 M PRM
Node-B
From/To E1/J1 DTIM

Node-B
DHTM SIGM
MHM M2CM
CCPM
D-LSF H-TRKF
DTIM Digital Transmission Interface Module

DHTM Diversity Handover Trunk Module
SIGM Signaling Module
MHM Mac Header Handling Module
M2CM Mobile Layer-2 Control Module
LSM Line Switch Module
PRM Packet Radio Link Control Module
GTPM GPRS Tunneling Protocol Module
CCPM Central Control Processor Module
Fig. 6 Principal modules of the eRNC frames
MN3500EU50MN_0001
13
© 2005 Siemens AG
3 RNC Frames
These basic frames of the cRNC are the Line Switch Frame (LSF), the Trunk Frame
(TRKF) and the Packet Radio Link Controller Frame (PRF), there are different types
of Trunk Frames. The used type depends on the system configuration.
The eRNC consists of at least 2 frames. These basic frames are the Line Switch
Frame (LSF) and the Trunk Frame (TRKF). There are different types of Trunk
Frames. The used type depends on the system configuration.
Each of theses frames has modules with definite functions.
14 MN3500EU50MN_0001
© 2005 Siemens AG
cRNC:
B-LSF C-TRKF A-PRF
PDU PDU PDU

FAN FAN FAN
B-SIGM C-M2CM A-GTPM

B-LSM
C-DHTM C-DHTM A-PRM
FAN FAN FAN
E-CCPM B-MHM C-CMPM A-PRM
D-CCPM D-CMPM D-CMPM A-PRM
RNCplus, cRNC
upgraded with
WCMP, WLSC
eRNC:
D-LSF H-TRKF
PDM PDM
FAN FAN
WCMP B-MHM C-DHTM
C-LSM
B-SIGM C-M2CM
FAN FAN
E-CCPM C-GTPM B-PRM
D-CCPM A-DTIM
Fig. 7 Comparison of Frames in cRNC, eRNC and RNCplus
MN3500EU50MN_0001
15
© 2005 Siemens AG
3.1 Line Switch Frame (LSF)

The LSF supplies power to the equipment in this frame and uses forced air-cooling for
the modules. It also transmits the signals related to the modules in this frame,
collects alarm information from this frame and from other frames via the alarm bus,
and reports such information to the higher-level equipment (CCPM). The LSF
interconnects all modules of the RNC.
The LSF is composed of the following equipment:
• Fuse Panel (FUSE)
Note: The FUSE houses the Alarm Collector Card (ALMC) and Alarm (ALM)
Card
• Frame Temperature Sensor Unit (FTSU)
• Fan Module (FANM)
• Line Switch Module (LSM)
• Central Control Processor Module (D/E-CCPM) with Hub.
The D-LSF of the RNC-E is composed of the following equipment:

• Power Distribution Module (PDM)
Card
• Line Switch Module (C-LSM)
• Central Control Processor Module (D/E-CCPM) with Hub.
16 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE PDM
FTSU FTSU
FANM 0 FANM 0
LSM C-LSM
FANM 1 FANM 1
E-CCPM E-CCPM
D-CCPM D-CCPM
cRNC LSF eRNC D-LSF

Fig. 8 HW modules of the Line Switch Frame
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
17
© 2005 Siemens AG
3.2 Trunk Frame (TRKF)

The cRNC-TRKF supplies power to the equipment in this frame and uses forced air-
cooling for the modules. It also transmits the signals related to the modules in this
frame, collects alarm information from this frame and, via the alarm bus, reports such
information to the higher-level equipment.
The TRKF is composed of the following equipment:
Card
• Signaling Module (SIGM)
• MAC Header Handling Module (MHM)
• Mobile Layer-2 Control Module (M2CM)
• Diversity Handover Trunk Module (DHTM)
• Composite/De-Composite Module (CMPM)
The eRNC TRKF supplies power to the equipment in this frame and uses forced air-
cooling for the modules. It also transmits the signals related to the modules in this
frame, collects alarm information from this frame and, via the alarm bus, reports such
information to the higher-level equipment.
The TRKF is composed of the following equipment:
• Power Distribution Module (PDM)
Card
• Signaling Module (B-SIGM)
• MAC Header Handling Module (B-MHM)
• Mobile Layer-2 Control Module (C-M2CM)
• Diversity Handover Trunk Module (C-DHTM)
• "Digital Transmission Interface Module (A-DTIM) "
• Hub Module (A-HUBM)
• General Packet Radio Service Tunneling Protocol Module (C-GTPM)
• Packet Link Control Module (B-PRM, C-PRM)
18 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE
FTSU
FANM 0
SIGM M2CM
DHTM DHTM
FANM 1
MHM C-CMPM
D-CMPM D-CMPM
Fig. 9 HW modules of the cRNC Trunk Frame (basic)
A la rm L a m p
PDM PDM
FAN M 0 FANM 0
B -M H M C -D H T M B -M H M C -D H T M
B -S IG M C -M 2 C M C -G P T M C -D H T M
FAN M 1 FANM 1
C -G T P M B -P R M B -S IG M C -M 2 C M
A -D T IM B -P R M
E 1 In te rfa c e S T M -1 In te rfa c e
Fig. 10 HW modules of the eRNC Trunk Frame H-TRKF
MN3500EU50MN_0001
19
© 2005 Siemens AG
20 MN3500EU50MN_0001
© 2005 Siemens AG
3.2.1 Example of RNC trunk frames extensions
FUSE FUSE
FTSU FTSU
B-DHTM C-DHTM C-DHTM C-DHTM
FANM0 FANM0
C-CMPM D-CMPM B-SIGM A-HUBM
FANM1 FANM1
C-CMPM D-CMPM B-MHM C-CMPM
D-CMPM D-CMPM D-CMPM D-CMPM
Fig. 11 HW modules of the cRNC Trunk Frame extensions
Alarm Lamp
PDM PDM
FANM 0 FANM 0
B - MHM C - DHTM B - MHM C - DHTM
B - SIGM C - M2CM A - HUBM C - DHTM
FANM 1 FANM 1
C - GTPM B - PRM B - SIGM B - SIGM
B-PRM
A - DTIM B - PRM
H-TRKF(001) -
H-TRKF(005)
Fig. 12 Example of the eRNC Trunk Frame extensions
MN3500EU50MN_0001
21
© 2005 Siemens AG
3.3 Packet Radio Link Controller Frame (PRF) –

(RNCplus-only)
The RNCplus is equipped with a additional Frame for Packet Radio functions which
is called PRF. The PRF supplies power to the equipment in this frame and uses
forced air-cooling for the modules. It also transmits the signals related to the modules
in this frame, collects alarm information from this frame and, via the alarm bus,
reports such information to the higher-level equipment.
The PRF is composed of the following equipment:
Card
• GPRS Tunneling Protocol Module (GTPM)
• Packet Radio Link Control Module (PRM)
22 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE
FTSU
FANM 0
GTPM
PRM (Basic)
FANM 1
PRM (Extended)
PRM (Extended)
Fig. 13 HW modules of the Packet Radio Link Controller Frame in the RNCplus
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
23
© 2005 Siemens AG
24 MN3500EU50MN_0001
© 2005 Siemens AG
4 General Modules of all RNC Frames
MN3500EU50MN_0001
25
© 2005 Siemens AG
4.1 Fuse panel and Power Distribution Module (PDM)

The FUSE panel supplies power to each of the modules mounted in the frame, as
well as collects and reports various alarm information. In RNCplus configurations it
is simply called Fuse panel. In eRNC configurations it is named as PDM. The
function of the Fuse panel and the PDM is the same.
• Power Filter (POW FIL)

Eliminates AC components included in –48 V DC input power and supplies this
power through the Power Bus to each module. The Power Filter has a duplex
configuration for two power lines.
• Alarm (ALM)
Collects alarm information generated in each module to indicate it by lighting up
the alarm lamp on the top of the frame or an aisle pilot lamp. The pushbutton for
resetting power alarms is installed in the front panel of the ALM.
• Alarm Collector (ALMC)
Collects alarm information generated in each module to transfer it via the
doubled Alarm Bus to the MIF (Maintenance Interface) in the D-CCPM.
P P
| |
8 8
POW FIL 0 POW FIL 1 Z X
8 4
3 4
A A
L L
M M
C
Fig.14 Layout of the Fuse Panel
26 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE Panel
–48V/G Power-Bus
POW FIL 0
Power To
Room PTM Each
–48V/G Power-Bus Module
POW FIL 1
Power Alarm –48V Alarm Lamp
ALM on the top of
To Alarm Signals frame or aisle
Each HUBIU pilot lamp
ALM-Bus
D-CCPM (MIF) ALMC
Fig.15 Functional blocks of the Fuse Panel
LSM/CMPM/MHM/GTPM/PRM/SIGM
LSF
D-CCPM
PRU HUB
VALP Visual and Audible
MIF PRU
AALP
E-CCPM
From –48 VDC Input –48 VDC Output To

Power Room FUSE Each Module
AALP : Audible Alarm Panel MIF : Maintenance Interface

CCPM : Central Control Processor Module PRU : Processing Unit
FUSE : Fuse Panel VALP : Visual Alarm Panel
Fig.16 Position of the Fuse Panel in the LSF
ALM-Bus 00
MIF #0 MIF #1
ALM-Bus 10
ALMC ALMC ALMC

Frame 0 Frame 1 Frame 15
ALM-Bus 01
ALM-Bus 11
ALMC ALMC ALMC

Frame 16 Frame 17 Frame 31
ALM-Bus : Alarm Bus MIF : Maintenance Interface

ALMC : Alarm Collector
Fig.17 Doubled Alarm Bus and doubled MIF
MN3500EU50MN_0001
27
© 2005 Siemens AG
4.1.1 Power Supply Redundancy

All cards are individually connected to two separate power supplies. Each card can
only be assigned to one of the two redundancy schemes described below.
Power redundancy scheme 1

This redundancy scheme employs different power supplies for the active unit and the
standby unit of a card. Power supply A is used for normal operation and power
supply B for redundant operation. This scheme applies to the following cards:
BLSC, LSW, PRU, HUBCTL, TINF (HUB), MCLK, CMUX, CMUXE, GMUX
Power redundancy scheme 2

In this redundancy scheme, each card (also redundant ones if existing) is powered by
two separate power supplies simultaneously. This applies to all cards which do not
operate in power redundancy scheme 1.
28 MN3500EU50MN_0001
© 2005 Siemens AG
PDM 0
Fig. 18 Power supply redundancy scheme 1
Fig. 19 Power supply redundancy scheme 2
MN3500EU50MN_0001
29
© 2005 Siemens AG
4.2 Frame Temperature Sensor Unit (FTSU)

The FTSU is mounted in the frame to detect abnormal temperature in it, thus
preventing a fire or minimizing the spread of the fire.
The FTSU provides high temperature sensors at two stages: 70°C and 100°C
(accuracy: ±3°C), five sensors for each stage. In case a sensor detects an abnormal
temperature in the frame, the following procedures take place:
• High temperature or Fire alarm signal sending
When the temperature in the frame exceeds 70°C, the FTSU generates a High
temperature alarm as a Major alarm, or at 100°C a Fire alarm as a Critical
alarm. The FTSU also lights the corresponding alarm (ALM) LED on the front
panel and sends alarm information to the upper level device via the Fuse Panel
(FUSE).
• Blowing the Main Fuse
In case a sensor in the FTSU detects a fire temperature of 100°C in the frame,
an over-current is applied to the FUSE Panel, causing the Main Fuse to be
blown. The over-current is generated by grounding the thyristors via the Power
bus. This cuts off the power supply to all devices in the frame, thus preventing
the spread of the fire.
NOTE
The (ALM) LEDs are only equipped in FTSU of the RNCplus.
30 MN3500EU50MN_0001
© 2005 Siemens AG
Fig.20 Frame Temperature Sensor Unit (FTSU), construction example
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
31
© 2005 Siemens AG
4.3 Fan Module (FANM)

The FANMs, mounted in all the frames of the RNC, are designed to cool down the
shelves and modules.
• Rotation speed:
2,750 rpm
• Rotation alarm detection:
When the rotation speed drops below 1800 ± 200 rpm for more than 3 seconds.
• Abnormal temperature detection:
58°C or higher
The FANM is composed of a maximum of 3 Fan Units (FANUs). Two fans are
provided in each FANU. An Air filter on the top of the FANM keeps dust out of the
modules in the frame.
The fans of the FANM are divided into two groups: the fans mounted on the front side
and those mounted on the rear side. They are using separate power supplies.
When a Blown Fuse Alarm and/or a Fan Stop Alarm (FAN STOP) occur (rotating
speed below the standard value), these alarm signals are reported to the Fuse Panel
(FUSE) of the frame.
The red Fan Alarm LED (FAN ALM) provided on the front panel of the module is
lightened.
32 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE
FTSU
FANM 0
FAN
FANM 1
FANU
Fig.21 Fan Module (FANM)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
33
© 2005 Siemens AG
5 RNC Structure
The RNC HW is structured in different modules. It consists of LSM (Line Switch
Module), the HUB-Module, the Central Control Processor-Module and Trunk-
Modules. With the loaded FW and SW on these modules the logical function
(Logical Processor) is assigned. All modules are units, which carry out different
functions.
In the Central Processor Modules (E-CCPM and D-CCPM) the Processors (O&M,
CLP and RMP) and the HUBM are located. Via the HUBM the communication
between the different modules (internal signaling) is possible.
The LSM is responsible for the internal and external connection of user and signaling
traffic. All modules and also the external interfaces (Iub and Iur) are connected to the
Line Switch Module.
Trunk modules like SIGM, M2CM, DHTM ...are responsible for processing of the
different signaling and user traffic. Depending on the module type the tasks of the
modules are different.
34 MN3500EU50MN_0001
© 2005 Siemens AG
LSM
From/To CLKD
CN/RNC STM1 GTPM

TINF TINF G
M
From/To U
STM1 TINF X HUBIU
Node-B TINF
WCMP PRM
C
From/To
DTIM M PRLC
E1/J1 C TINF U
MDTI M X
Node-B U TINF E HUBIU
X
HUBIU
A
DHTM T SIGM
C M C ANC/
DHT M M MFG
U TINF S TINF U
X W X
DHT E HUBIU
MHM M2CM
C C
MHC M M M2C
U TINF U
X X
HUBIU E M2C
WLSC
HUB
CCPM/HUBM
CLK OMP CLP CLP
SVC COC SCC
MIF
DK
CCPM IMAT DAT
Trunk Module Line Switch Module Processor Module
Fig. 22 RNC HW modules example
MN3500EU50MN_0001
35
© 2005 Siemens AG
36 MN3500EU50MN_0001
© 2005 Siemens AG
6 RNC Modules in LSF
MN3500EU50MN_0001
37
© 2005 Siemens AG
6.1 Central processor module (CCPM)

The CCPM (Central Control Processor Module) consist of D-CCPM and E-CCPM.
The HUBM (HUB-module) is also a part of the E-CCPM. HUBM, an ATM-Bus
system, has interfaces to all CPs, to the LSM and to the Basic Trunk Modules. The
CPs (CP01 and CP02) also located in the E-CCPM are responsible for Call
processing. The HUB and the CPs are working in duplex configuration.
38 MN3500EU50MN_0001
© 2005 Siemens AG
D-CCPM
05 10 15 20 25 30
DK/ DK/ M M C C R B B S S C C H H S S P P
DAT 0 DAT 1 I I L L e L L C C O O U U V V R R
F F K K I A A C C C C B B C C U U
# # # # n N N 0 1 0 1 I I # # # #
0 1 0 1 f K K # # 0 1 1
o 0 1
r
c
I
n
g
P
l
a
t
e
(Front View)
Fig. 23 Layout of D-CCPM
To/From To/From
ALMC HUB
D-CCPM
MPC Bus ALM Bus MH Bus
To/From
SV Bus #1 MCSL
#1 #0 VALP
#0 MIF
SVC AALP
SVC
#1 To/From
#0 LSM
CLK SIGM
#1
#0
HUB Link To/From
#1 HUBI HUB
#0 (E-CCPM)
PRU
Unit 0 Ethernet
To/From CPU COC To/From
Other CCPM IMAT
Unit 1
MM RS-232C
COC
Unit 0 SCSI Bus 0 DK/DAT

SCC
DK DAT
Unit 1 SCSI Bus 1 DK/DAT

SCC
DK DAT
Fig. 24 Architecture of D-CCPM
MN3500EU50MN_0001
39
© 2005 Siemens AG
The D-CCPM consists of the SCSI Controller Unit (SCC) for the communication with
the DK‘s and the DAT-drives, the Communication Controller (COC) for RS232 and
LAN Interfaces. RS232 of COC module is used for Hyper-Terminal connection and
the LAN interface is used to connect the TelNet-session and the Radio Commander
(RC). These cards are in non-duplex configuration. The Clock Card, which generates
the system clock, the Supervision Controller for restart control, the Maintenance
Interface, used for the connection of the Alarm Panels and the Master Console, are in
duplex configuration like the CP00, which is the Operation and Maintenance and
Resource Management Processor. HUBIs are also located in E- and D-CCPM for the
connection to the HUBM.
40 MN3500EU50MN_0001
© 2005 Siemens AG
E-CCPM
05 10 15 20 25 30
B B B H H P P T T H T T H R B B H H P P B
L L L U U R R I I U I I U e L L U U R R L
A A A B B U U N N B N N B I A A B B U U A
N N N I I # # F F C F F C n N N I I # # N
K K K # # 0 1 0 1 T 0 1 T f K K # # 0 1 K
0 1 # # L # # L o 0 1
0 0 # 1 1 # r
0 1 c
I
n
g
P
l
a
t
e
Unit 0 HUB Unit 1

(Front View)
Fig. 25 Layout of E-CCPM
E-CCPM
To/From Unit 0
#1
OMP #0
PRU
#1
#0
CPU
HUBI
MM
MPC Bus
Unit 1
#1
#0
PRU
#1
#0
CPU
To/From
HUBI
Other CCPM
or MM
LSM, Trunk
Module
HUB Unit 0
#1 HUB Link
#1 #0 To/From
Inter HUB #0 OMP
Bus TINF
To/From
HUBM
HUB
CTL Unit 1 To/From
HUB Link CCPM

#1
To/From MH Bus #0
LSM, or
MIF Trunk
TINF Modules
To/From
COC
Fig. 26 Architecture of E-CCPM
MN3500EU50MN_0001
41
© 2005 Siemens AG
6.2 HUB module

The HUB Module is the link between the ATM switch and the processors. The HUB is
also based on ATM. The basic hub provides 8 ports in the 3-rack configuration. Four
of these ports are occupied by the ATM switch and the processor unit. The other four
ports can be used to connect the trunk modules. A single hub connection supports
internal traffic of up to 100 Mbps. There is a bandwidth limitation of 310 Mbit/s in the
link between Basic-HUB and Extension-HUBMs. Maximum 2 Extensions are
possible.
42 MN3500EU50MN_0001
© 2005 Siemens AG
HUB Unit
E-CCPM (Basic) HUBM Extension 1 HUBM Extension 2
#1 #1 #1
#0 #0 #0
HUBCTL HUBCTL HUBCTL
Unit 0 Unit 1 Unit 0 Unit 3 Unit 0 Unit 3

TINF TINF TINF TINF TINF TINF
8 Ports 16 Ports 16 Ports
LSM, Trunk System Modules & CCPM

(Total 40 Ports: 8 Ports/E-CCPM + 16 Ports/HUBM x 2 HUBM)
Fig. 27 Architecture of HUB
MN3500EU50MN_0001
43
© 2005 Siemens AG
6.3 Line switch module (LSM)

The LSM (Line Switch Module) basically is an ATM-switch. The central cards are the
Line Switch Card and the Line Switch Controller. The TINF cards (Trunk Interface
Cards) have the external interfaces (STM1, OC3) towards UMSC, other RNCs, for
NodeBs and also for the internal connection to the trunk modules. For clock
extraction and distribution a Clock Distribution Card is also located in the LSM. HUB
connection is done via HUBIU cards. They are also a part of the LSM. All cards are
working in duplex configuration. The only exception is the TINF card. This card can
be configured in single configuration.
TIP
With the introduction of the WLSC also a new card, the WCMP, can be placed
instead of a TINF card in the LSM. This WCMP cards are like the TINF cards either in
single or duplicated mode depending on the configuration.
Additionally the LSM can be equipped with HSDST cards instead of some TINF cards
to support the HSDPA feature. The HSDST cards are configured in single mode as
hsdps.
44 MN3500EU50MN_0001
© 2005 Siemens AG
© 2005 Siemens AG
025
HUBIU #0 HUBIU #1
card #0 card #16
RNC Hardware
MN3500EU50MN_0001
035
card #1 card #17
Fig. 28 Line Switch Module

card #2 card #18
045
card #3 card #19

card #4 card #20
065
card #5 card #21

card #6 card #22
085
card #7 card #23

WLSC/LSC #0
105
cards can be: TINF, WCMP or HSDST

WLSC/LSC #1
125
LSW #0
145
LSW #1
CLKD #0 CLKD #1
165
card #8 card #24

card #9 card #25
185
card #10 card #26

card #11 card #27
205
card #12 card #28

card #13 card #29
225
card #14 card #30

card #15 card #31
Siemens/NEC
45
6.3.1 HSDST Functionality

The HSDST card only deals with HSDPA traffic and is located in the LSM
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
6.3.1.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.
6.3.1.2 HS-DSCH Frame Protocol

The HS-DSCH frame protocol (FP) has the following functions:
• Data transfer
• Flow control
On the Iub interface, the HSDPA data are transferred by means of HS-DSCH DATA
FRAME. Flow control is performed by means of the CAPACITY ALLOCATION
message (sent from the NodeB to the RNC) and the CAPACITY REQUEST message
(sent from the RNC to the NodeB). The maximum rate, the RNC is allowed to
transmit on the Iub interface, is determined by the CAPACITY given by the
CAPACITY ALLOCATION message.
46 MN3500EU50MN_0001
© 2005 Siemens AG
HSDPS
HSDST-CARD
Fig. 29 HSDST card configured as hsdps
MN3500EU50MN_0001
47
© 2005 Siemens AG
6.3.2 Iu/Iub interface structure

The duplicated ATM link structure is available for the Iu interface. Duplicated and
Non-duplicated ATM link structures are available for the Iub interface.
TIP
Duplicated ATM link and Non-duplicated ATM link are not combined in the same
TINF card.
6.3.3 Duplicated structure

ATM link and TINF card perform duplex operation (ACT/SBY). When fault occurs in
ACT ATM link or TINF card, the RNC switches over the ACT link/card to SBY side.
Duplicated Link
LSM
TINFsys_1 #1
Up ATM Link #1: SBY LSW
To/From
INS
CN Down
(or Node-B) TINFsys_0 #0
Up ATM Link #0: ACT LSW
INS
Down
Duplicated
Fig. 30 Duplicated structure
48 MN3500EU50MN_0001
© 2005 Siemens AG
6.3.4 Non-duplicated structure

In the non-duplicated structure, each TINF cards perform non-duplex operation
receptivity. The RNC does not operate switch over function.
Individual Link
LSM
To/From TINF #1
Node-B Up ATM Link LSW
(B)
Down
To/From TINF #0
Node-B Up ATM Link LSW
(A)
Down
Non-duplicated Duplicated
Fig. 31 Non-duplicated structure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
49
© 2005 Siemens AG
6.3.5 C1HW interface structure

Duplicated C1HW structure is available between TINF card and C1HWM card in the
trunk modules. C1HW and TINF card perform duplex operation (ACT/SBY). When
fault occurs in ACT C1HW or TINF card, LSM switches over the ACT link/card to
SBY side.
Duplicated Link
Trunk System Module LSM
C1HWMsys_1 C1HW #1: SBY TINFsys_1 #1

Up LSW
INS INS
Down
C1HWMsys_0 C1HW #0: ACT TINFsys_0 #0
Up LSW
INS INS
Down
Duplicated
Fig. 32 C1HW interface structure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50 MN3500EU50MN_0001
© 2005 Siemens AG
7 RNC Modules in the Trunk Frame (TRKF)
MN3500EU50MN_0001
51
© 2005 Siemens AG
All trunk modules have in principle the same architecture. The central card is the
CMUX, CMUXE or in the GTPM the GMUX card. Each MUX has its logical controller
running on the card. Not all MUX have a connection to the HUBM for internal
communication because of the limited number of available HUB-interfaces. For this
reason the MUX are grouped in so-called CMUX-groups. Different types of modules
are located inside such cmux groups. One is the so-called basic module (which has
the connection to the HUB-module via the HUBIU interface) and the other modules
are the Extension Modules. One exception is the PRM. This one is a Basic Extension
Module with an HUBIU interface connected to the HUBIU card in the GTPM. Up to 4
MUX (1x basic and 3x extension) can be in a CMUX group.
52 MN3500EU50MN_0001
© 2005 Siemens AG
to HUB SIGM
HUBIU nbsc/assc
HUBIU DHTM
mswc
trunk card trunk card
C1HWY
to TINF
CMUX
C1HWY
CMUX
C1HWY
C1HWY
CMUXE
CMUX
in LSM
to TINF
in LSM
to HUB GTPM
HUBIU gmux M2CM
HUBIU
nbsc
trunk card
trunk card
CMUX
CMUXE
C1HWY
CMUX
C1HWY
GMUX
C1HWY
C1HWY
to TINF
in LSM
trunk card
Fig. 33 General MUX architecture
CMUXG CMUXE
to HUB HUBIU CMUX CMUXE
CMUXE
Fig. 34 CMUXG architecture
MN3500EU50MN_0001
53
© 2005 Siemens AG
CMUXG
GMUX
Primary
to HUB HUBIU GMUX
GMUX
CMUXG
CMUXE
Secondary
HUBIU CMUXE
CMUXE
Fig. 35 CMUXG types for GTPM and PRM
54 MN3500EU50MN_0001
© 2005 Siemens AG
7.1 The Composite De-composite Function

The composite de-composite function is carried either in the CMP cards of a CMPM
Module (CMPM) in case of RNCplus or in WCMP cards for eRNCs.
For upgraded cRNCs which are called RNCplus the composite de-composite function
is spread over CMP and WCMP cards. In this case AAL2 traffic from Iub is handled in
WCMP cards and AAL2 traffic from IuCS/IuR is handled in CMP cards (n1cmp).
The function of the composite de-composite is independent on the hardware (CMP or
WCMP) but there is a difference in capacity.
A WCMP has a throughput of up to 300 Mbit/s, which is equivalent to the capacity
of approximately 8 CMP cards (40 Mbit/s per CMP)
128 AAL2-VC (U-Plane) can be configured per WCMP, which is equivalent to the
capacity of approximately 4 CMP cards (32 VC per CMP).
The VC of the same NodeB should be established on the same WCMP board. There
are no port numbers to be considered.
MN3500EU50MN_0001
55
© 2005 Siemens AG
7.1.1 The Function of CMP/WCMP

The CMP/WCMP is converting all incoming AAL2 (ATM Adaptation Layer 2) cells into
the RNC internal format AAL2d. The AAL2 cells are also called composite cells, and
the converted AAL2d cells are called de-composite or standard cells.
The conversion is necessary because for switching the RNC needs cells in which
each subscriber is separated.
Therefore, every user data in AAL2 cells coming from the MSC or the Node-B should
pass through the CMP/WCMP.
The CMP/WCMP is treating the User Plane CS and PS, and it is also implemented in
the signaling path of the Control Plane.
The following cases can be distinguished:
• The CMP/WCMP receives AAL2 traffic data in the User Plane CS or PS directly
via the DTI or backyard via the TINF, then it executes AAL2/AAL2d conversion.
• The CMP/WCMP receives AAL2 signaling data of the Radio Protocols
(RRC/RLC/MAC) in the Control Plane via the Iub, then it executes AAL2/AAL2d
conversion and forwards the AAL2d cells either to the DHTM (Dedicated
Channels) or to the MHM (Common Channels).
• The CMP/WCMP receives AAL5 signaling data (NBAP or RNSAP) in the
Control Plane, then it forwards these AAL5 cells without conversion to the SIGM
where AAL5 is converted into AAL3/4.
56 MN3500EU50MN_0001
© 2005 Siemens AG
CMP or WCMP card
Composite
Composite
Unit
Unit
PAD A o
Interface
Interface
Interface Unit
Interface Unit
CN L
(via LSM)
A B C m PAD B p S
M
ATM Cell
Unit
Unit
PAD C q
De
De--Composite
Composite ATM Cell
Unit
Unit
Composite Cell Standard Cell

m : Core Network/Node-B Interface Connection Cell Header
o, p, q : Internal Connection Cell Header
A, B, C : User Data
PAD : Blank Part of Cell
Fig. 36 Decomposition / composition of cells
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
57
© 2005 Siemens AG
7.2 Wideband Composite Card (WCMP)

If the WCMP card is used instead of cmp card only backyard connections are
available. The WCMP card offers a total capacity of 300 Mbits/s per card and a
maximum connectivity of 128 VC's. There are no ports to consider.
58 MN3500EU50MN_0001
© 2005 Siemens AG
Backyard
WCMP
maximum
128
VC’s
per card
Fig. 37 Backyard connection WCMP
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
59
© 2005 Siemens AG
7.2.1 Iub interface (WCMP equipped)

Iub interface is the interface between eRNC and Node-B. The Iub interface unit
consists of a line interface unit and an AAL2 multiplexing unit in the eRNC. But the
eRNC doesn’t switch AAL2 cells. Therefore the eRNC should convert AAL2 cell to
AAL2d (AAL2 de-composite). The Node-B interface is designed for following two
types of line accommodation:
Indirect connection The configuration to cover E1 line interface
Backyard connection The configuration to cover STM1 line interface
Indirect connection
The E1 line card (MDTI) is connected to AAL2 disassembly/assembly card (WCMP)
through the ATM SW. The eRNC and Node-B are connected with max 16 E1 links.
Backyard connection
The line is connected to the AAL2 disassembly/assembly card (WCMP), via the ATM
line card (TINF) accommodated in ATM-SW (LSM). Since the ATM line provides
Virtual Path (VP) handler function, the eRNC assumes that VP (Virtual Path)
corresponding to each Node-B is multiplexed within the physical line (TINF).
Therefore, the band within AAL2 disassembly/assembly card is divided into
necessary bands (for each Node-B) and managed with each VP of the ATM line, and
is VP-connected to TINF.
Since the ATM line termination is single, the opposite side TINF is also made single.
Therefore, when user traffic is accommodated with multiplexing to a high degree, 2-
line/Node-B should be provided on Node-B side to diversify risks, and also at least 2-
line/eRNC with VP-multiplexed physical lines (TINF) should be set up on the eRNC
side.
TIP
On Iub interfaces, also the redundant or non redundant mode is possible.
60 MN3500EU50MN_0001
© 2005 Siemens AG
DTIM ATM SW
Max. 16/Node-B AAL2 (Composite Cell)
Node-B E1 Link
MDTI
E1 Link
MDTI
C1HWM
M
TINF
U
X
E1 Link
MDTI
WCMP
AAL2d (Standard Cell)
Fig. 38 Iub Interface (Indirect connection)
Node-B
Node-B Interface Unit
Node-B Interface Unit ATM SW
STM1 (LSW)
TINF
AAL2 (Composite Cell)
WCMP
AAL2d (Standard Cell)

Cell
Composite Function card
Fig. 39 Iub Interface (Backyard connection)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
61
© 2005 Siemens AG
7.2.2 A-DTIM module
The A-DTIM module is composed of up to 3 sets (consisting of 4 MDTI cards) of

MDTI cards. Each A-DTIM module can accommodate up to 12 MDTI cards. Each
MDTI card provides 16 ports for E1/J1 lines (G703). 8 VPs per E1/J1 line are
supported.
In sum the number of E1 lines can be in maximum 192 per A-DTIM which is
double capacity of the RNCplus ( In maximum 3CMPM per TRKF equipped with
DTI ).
62 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 40 Layout of the Card in A-DTIM
A -D T IM
#1
#0
T o/F rom
MDTI 0 N ode-
(1 6 )
B
T o/F rom
LSM MPC
T o/F rom
or Bus MDTI 1 N ode-
(1 6 )
O th e r B
T ru n k
M o d u le T o/F rom
MDTI 2 N ode-
(1 6 )
B
#1 CMUX
T o/F ro
m
#0 (u n it 0 ) MDTI 3
T o/F rom
C 1H W M (1 6 ) N ode-
LSM
B
#1
#0
T o/F rom
H U B IU HUB
#1 #1
#0 #0 T o/F rom
M DTI (1 6 )
N ode-
0 B
CMUX (4 ) CMUX (4 )
(u n it 1 ) (u n it 2 )
T o/F rom
MDTI (1 6 )
N ode-
3 B
Fig. 41 DTIM Functional Block
MN3500EU50MN_0001
63
© 2005 Siemens AG
7.3 Composite Module (CMPM) for RNCplus only

The Iub interface is the interface between RNC and Node-B. Such a interface unit
consists of a line interface unit and the so-called AAL2 multiplexing unit in the RNC.
Because of the fact that the RNC is not able to switch AAL2 cells, all the cells needs
to be converted before the switching takes place.
The C-CMPM (Basic Composite Module) consists of CMUX-cards (Cell Multiplexer),
which are connected via the C1HWM-cards (C1Highway Interface Multimode) with
TINF-cards in the LSM. This configuration is fully redundant. The CMUX are
connected on the other hand with the Trunk cards. In case of C-CMPM and D-CMPM
(which is the extension) those trunk-cards are CMP-cards (and for E1 connection as
well DTI-cards). Every AAL2 cell coming or going from/to MSC or NodeB has to go
trough this CMP-cards. The CMP-cards are responsible for the conversion from/to
AAL2/AAL2d to enable ATM switching. In case of a STM1 interface the connection is
called Backyard connection. DTI cards are necessary in case of NodeB connections
for E1 termination. Each DTI-card has 8 E1 ports. This case is called Frontyard
connection.
In the C-CMPM (the Basic one) the HUBIU is located. Those cards are responsible
for the connection with the HUB in E-CCPM.
The D-CMPM (Extension Composite Module) has no HUBIU cards. The connection
to the HUB is made CMXG-internally via C-CMPM.
• Direct Accommodating: The configuration to cover E1 link

• Backyard: The configuration to cover ATM line (STM1)
7.3.1 Iub interface (CMP equipped)

The Iub interface is the interface between the RNC and the Node-B. The Iub interface
unit consists of a line interface unit and an AAL2 multiplexing unit.
The RNC doesn’t switch AAL2 cells. Therefore the RNC has to convert AAL2 cells
into AAL2d (AAL2 de-composite) cells. The Node B interface is designed for the
following two types of line connections:
Direct Accommodating: The configuration to connect E1 lines.
Backyard: The configuration to connect STM-1 lines (ATM).
64 MN3500EU50MN_0001
© 2005 Siemens AG
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
65
© 2005 Siemens AG
• Direct Accommodating
The line card (DTI) is directly inserted in the AAL2 Disassembly / Assembly unit
(CMPM). This is the normal configuration method for line connections with this unit.
8 E1 / J1 lines
16 E1 / J1 lines
16 E1 / J1 lines and 2 STM-1 lines
• Backyard
The line is not directly connected to the AAL2 Disassembly / Assembly unit (CMPM),
but connected to a TINF card which is inserted in the ATM-Switch (LSM). The ATM-
Switch connects the AAL2 multiplexing card (CMP).
Since the TINF (ATM STM-1 line) provides Virtual Path (VP) handler function, the
RNC assumes that the VP (Virtual Path) corresponding to each Node B is
multiplexed within the physical STM-1 line (TINF). Therefore, the bandwidth within
the AAL2 Disassembly / Assembly card is divided into necessary bandwidths for
each Node-B and managed for each VP of the ATM line, and is VP-connected to the
TINF.
If the ATM line termination is single, the opposite side TINF is also made single.
Therefore, when user traffic is multiplexed to a high degree, 2-lines per Node-B
should be provided at the Node B side to diversify risks, and also at least 2-lines with
VP-multiplexed physical STM-1 lines (TINF) should be set up at the RNC side.
66 MN3500EU50MN_0001
© 2005 Siemens AG

ATM SW
CMPM
(LSW)
Node-B E1 Link
DTI CMP AAL2d (Standard Cell)
E1 Link
DTI CMP
CMUX
C1HWM TINF
E1 Link
DTI CMP
Fig. 42 E1 signal flow for direct connection
Node-B
Node-B
Node-BInterface
InterfaceUnit
Unit ATM SW
STM1 (LSW)
TINF
CMPM
C
M
CMP U TINF
C1HWM
X
Composite Function Unit

AAL2d (decomposite)
Cell
Fig. 43 STM1 signal flow for backyard connection
MN3500EU50MN_0001
67
© 2005 Siemens AG
Basic Composite Module

8/16/16 E1 + 2STM1
to HUB NodeB
HUBIU
HUBIU 880
0
CMP DTI E1
CMP DTI 7
C1HWY
to TINF
CMUX
C1HWY
CMUX
in LSM
CMP
or 0
CMPn NodeB
880
8/16/16 E1 + 2STM1
Fig. 44 Architecture of C-CMPM
C-CMPM
05 10 15 15 10 05
C C C C H H D C D C D C D C D D D D
M M 1 1 U U T M T M T M T M T T T T
U U H H B B I P I P I P I P I I I I
X X WW I I 0 1 1 3 2 5 3 7
# # M M U U / / / / R R R R
0 1 # # # # C C C C E E E E
0 1 0 1 M M M M A A A A
P P P P R R R R
0 2 4 6
(Front View) (Rear View)
Fig. 45 C-CMPM plug in position
68 MN3500EU50MN_0001
© 2005 Siemens AG
Extension Composite Module
8/16/16 E1 + 2STM1
NodeB
880
0
CMP DTI E1
CMP
C1HWY
CMUX
to TINF
C1HWY
in LSM CMUXE 7
or
0
CMPn
NodeB
880
8/16/16 E1 + 2STM1
Fig. 46 Architecture of D-CMPM
D-CMPM
05 10 15 15 10 05
C C C C D C D C D C D C C C D D D D
M M 1 1 T M T M T M T M M M T T T T
U U H H I P I P I P I P P P I I I I
X X W W 0 1 1 3 2 5 3 7 8 9
E E M M / / / / R R R R
# # # # C C C C E E E E
0 1 0 1 M M M M A A A A
P P P P R R R R
0 2 4 6
(Front View) (Rear View)
Fig. 47 D-CMPM plug in position
MN3500EU50MN_0001
69
© 2005 Siemens AG
7.3.2 CMPM for frontyard connection

The so-called Frontyard Connection is used in case of NodeB connections via E1
interfaces. That means that the connection of the NodeB is direct via the DTI card to
the necessary cmp card. All ATM cells have to go through the cmp card independent
from the direction (uplink or downlink).
CMP card allocation
Operators are advised to concentrate the VCs of a Node B on the same CMP card.
Throughput of Frontyard CMP Cards
Frontyard CMPs feature a throughput of 40 Mbit/s. There are 8 ports available,
and each of them can be assigned to one ATM VP. A VP can contain up to 4 AAL2
user plane VCs. The creation of AAL5/AAL2 control plane VCs is subject to
bandwidth considerations only. A front-yard CMP card cannot be simultaneously
used as a backyard CMP.
70 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 12 8/16/16 E1 + 2STM1

CMUX 0 view dclb dclu=120100
NodeB
HUBIU
HUBIU 880
0
to HUB
CMP 120 01 DTI 0 E1
C1HWY CMP 120 03 DTI 2
CMUX
C1HWY
CMUX
ac1d 001 10 00
CMP 120 05 DTI 4 7
0
dclu= NodeB
12 CMUXG 880
0 CMUX
1 CMP
0 DTI
0-7 line CMPC 12 0 8/16/16 E1 + 2STM1
type check
Fig. 48 Frontyard connection
Direct Accomodating
DTI CMP
7 line port 7
6 line port 6
5 line port 5
4 line port 4
3
line port 3
2
line port 2
1
line port 1
0
line port 0
Fig. 49 Connection example DTI - CMP
MN3500EU50MN_0001
71
© 2005 Siemens AG
7.3.3 CMPM for backyard connection

In case of backyard connection e.g. connection of Core Network or NodeB for circuit
switched connection a cmp card connection must be assigned. This connection is
called Backyard connection.
Throughput of Backyard CMP Cards
Backyard CMPs feature a throughput of 40 Mbit/s which is divided into 20 Mbit/s for
ports 0...3 and 20 Mbit/s for ports 4…7. There are 8 CMP ports available per card.
There are no constraints related to the number of VPs per CMP port or CMP,
because the external VPs are terminated in the TINF card. A CMP port can
accommodate up to 4 AAL2 user plane VCs, thus there is a maximum of 32 AAL2
paths per CMP card. A backyard CMP card cannot be simultaneously used as a
front-yard CMP.
72 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 12
CMUX 1
CMP 121 00
T T
CMP 121 01
C1HWY
I ATM- I
CMUX
CN or NodeB
C1HWY
CMUX
via STM1 N Switch N
F F CMP 121 02
lu=0010000
CMP 121 03
ac1d 001 12 02
CMPC 12 1
Fig. 50 Backyard connection
Backyard
CMP
port 7
port 6
port 5
port 4
port 3
port 2
port 1
port 0
Fig. 51 Backyard connection example
MN3500EU50MN_0001
73
© 2005 Siemens AG
7.4 Features related to E1 connected NodeB

7.4.1 Inverse Multiplexing for ATM (IMA)
Inverse Multiplexing for ATM is a mechanism defined by the ATM Forum for the
physical layer of ATM transport networks. IMA provides for transport of a high bit rate
ATM cell stream on several low bit rate physical links. These physical links are
grouped to form a higher bandwidth logical link (IMA group) whose data rate is
approximately the sum of the individual link rates. IMA is supported on the lub
interface for E1. IMA groups can be configured with 2, 4, 6 or 8 E1 links. All links of a
group must be connected to the same DTI/MDTI card. The IMA group pattern applies
to a whole DTI/MDTI card, therefore IMA settings that are not included in the existing
group patterns must be set up using different DTI/MDTI cards. The figures providing
a simple illustration of the IMA technique in one direction. In a real environment, the
same technique is applied in the opposite direction as well.
IMA groups terminate at each end of the IMA virtual link. In the transmit direction, the
ATM cell stream received from the ATM layer is distributed, on a cell-by-cell basis,
across the multiple links within the IMA group. At the remote end, the receiving IMA
unit recombines the cells from each link and thereby recreates the original ATM cell
stream. The aggregate cell stream is then passed to the ATM layer. From a
configuration management point of view an IMA group appears as a new port type,
an IMA virtual port or IMA group. IMA and Fractional ATM cannot be implemented
simultaneously in the same E1 Iub interface. However, individual E1 Iub interfaces
originating from the same RNC can be set up in different ways provided they are
terminated in different interface cards. IMA groups are managed through the imac
command or the IMA Control Window.
IMA Calculation
A realistic calculation of the available bandwidth for Iub traffic can be done by using
the following formula:
maxIMABandwidth = 0.475 x n x 1.92 Mbit/s
where n is the number of lines that are combined into the group.
Fig. 52 IMA Group Pattern
74 MN3500EU50MN_0001
© 2005 Siemens AG
IMA Loop (Principle)
IMA Gro up IMA Gro up

Phys ic al Link #0
PHY PHY
Phys ic al Link #1
PHY PHY
S ing le ATM Ce ll S tre am Orig inal ATM Ce ll

fro m ATM Laye r S tre am to ATM Laye r
Phys ic al Link #2
PHY PHY
IMA Virtual Link
Advantage: Bandwidth of VP/VC (on several E1 links) > 2 Mbit/s

Fig. 53 Inverse multiplexing for ATM
IMA Loop (Principle)
IMA Group Physical Link #0

IMA Group
PHY PHY
Physical Link #1
PHY PHY
Single ATM Cell Stream Original ATM Cell

from ATM Layer Stream to ATM Layer
Physical Link #2
PHY PHY
IMA Virtual Link
Fig. 54 Inverse multiplexing for ATM
MN3500EU50MN_0001
75
© 2005 Siemens AG
7.4.2 Fractional ATM

Fractional ATM is a mechanism, which allows a mobile network operator to transport
both ATM, based UTRAN traffic and TDM based GSM traffic on a single physical line
(E1/J1). It is ideally suited for UMTS/GSM co-location sites with low traffic volume
(less than 2 Mbit/s) where the UTRAN Iub traffic can use the same transmission link
(E1/J1) as the GSM traffic between BTSE and BSC. The principle of Fractional ATM
is that the ATM based UMTS traffic uses only a part of the physical line resources
and the remaining time slots can be assigned to other traffic (e.g. TDM based GSM
traffic). Thus, fractional ATM can be used to realize low bandwidth Iub links by using
the resources of existing E1/J1 lines. Fractional ATM provides a mapping of ATM
cells on a circuit switched connection by supporting transfer rates at integer multiples
of 64 kbit/s up to the maximum rate of the interface because the ATM cells are sent
on a n x 64 kbit/s bearer with the range for n from 1 to 30 in the case of a E1
interface, and 1 to 24 for J1 lines. Timeslots 0 and 16 of an E1 interface are reserved
according to ITU-T standards. The first part of the frame is allocated to ATM traffic
and the second part is dedicated to TDM traffic. For the co-location of a Node B and
GSM BTSE using Fractional ATM, there is a choice between three different
implementations to combine and split the ATM based UMTS traffic and the TDM
based GSM traffic:
• All Platform2 NodeB have the mux/demux functionality integrated:
• BTSE and BSC have the cross-connect functionality integrated. Therefore, the
BTSE extracts/mixes the UMTS traffic to/from the NodeB.
Fractional ATM and IMA cannot be implemented simultaneously in the same E1 Iub
interface. However, individual E1 Iub interfaces originating from the same RNC can
be set up in different ways provided they are terminated in different interface cards.
76 MN3500EU50MN_0001
© 2005 Siemens AG
TDM/ATM
Fractional MUX/DEMUX
ATM
Fractional
ATM
RNC
Function NodeB
Function
RNC E1 NodeB
TDM/ATM E1
TDM
E1
ATM
TDM/ATM
MUX/DEMUX
BTSE
Function
BSC
Function BTSE
BSC unused
TDM Traffic
ATM Traffic
Fig. 55 Node B providing an integrated TDM/ATM Mux/Demux capability
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
77
© 2005 Siemens AG
7.5 MAC function

The multiplexing/demultiplexing of logical channels onto transport channels is the so-
called MAC function. MAC has the following 3 functional blocks.
• MAC-b (Broadcast): Multiplexed/De-multiplexed broadcast channel

• MAC-c/sh (Common/Shared): Multiplexed/De-multiplexed common & shared
channels
• MAC-d (Dedicated): Multiplexed/De-multiplexed dedicated channels
78 MN3500EU50MN_0001
© 2005 Siemens AG
Transport
Logical Channel
Channel
BCH MAC BCCH

-b
PCH PCCH
FACH BCCH
CCCH
RACH
CTCH
CPCH MAC
-c/sh
DSCH
DCCH
DCH MAC
DTCH
-d
MAC: Medium Access Control

RACH: Random Access Channell
FACH: Forward Access Channel
Fig. 56 MAC functional blocks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
79
© 2005 Siemens AG
7.6 MAC Header Handling Module (MHM)

The main function of the MHM is the multiplexing/de-multiplexing of logical channel
onto transport channels (RACH & FACH). For common channel, the MHM terminates
C-plane (RRC) data.
A link (PVC) towards each NodeB for synchronization must be configured in the
database.
The NodeSync links should be evenly distributed over all available MHC cards. MHC
cards are configured in an n+1 redundancy mode, hence seven out of every eight
MHC cards in a module can be used for link configuration and the eighth card must
be left unassigned. Operators may want to achieve an even load (and risk)
distribution and to choose an easy to remember allocation scheme between Node Bs
and ANC/MHC cards. The B-MHM has eight MHC cards.
80 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 10 to HUB HUBIU

CMUX 0 HUBIU
MHC 10 0 00 view mhcijklm

or
MHC 10 0 01 view mhcall
C1HWY
CMUX
C1HWY
CMUX
ac1d 001 08 02
ij=cmux group
k=cmux
lm=logical card no. (00-11)
mswc 10 0
Fig. 57 Architecture of MHM
MHM
05 10 15
C C C C H H M M M M M M M M
M M 1 1 U U H H H H H H H H
U U H H B B C C C C C C C C
X X W W I I 0 1 2 3 4 5 6 7
# # M M U U
0 1 # # # #
0 1 0 1
(Front View)
Fig. 58 Layout of module MHM
MN3500EU50MN_0001
81
© 2005 Siemens AG
7.6.1.1 MAC mapping

The MHC controls MAC (Medium Access Control) mapping of common transport
channel (RACH & FACH). Then, the MHC executes multiplexing/de-multiplexing
common logical channel (CCCH & CTCH), dedicated logical channel (DCCH &
DTCH) and BCCH (Broadcast Control Channel) in the RACH & FACH.
82 MN3500EU50MN_0001
© 2005 Siemens AG
Transport Channel RNC

Logical Channel
Up Link Up Link
MHC
CCCH
RACH
DCCH/DTCH
Down Link Down Link
Node-B
BCCH
UE FACH CCCH
CTCH
DCCH/DTCH
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fig.. 59.MAC
. channel
. . . mapping
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
83
© 2005 Siemens AG
7.7 Mobile Layer-2 Control Module (M2CM)

The termination of the dedicated signaling bearers to the UE is the responsibility of
the M2CM. The M2C terminates C-plane (RRC on dedicated channel) data from/to
Node-B. This C-plane data (RRC) is the control channel data on the radio. The M2C
transports the received data to the processor via SIGM and HUB.
Another function, which the M2CM support is the ciphering, functions for DCCH
(Dedicated Control Channel).
• Terminates RLC-C protocol for dedicated channel (DCCH).

• Terminates the MAC (DCCH), FP, and AAL 2d protocols.
• Provides ciphering function for DCCH.
84 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 11
SIGM CMUX 1
view m2cijklm
M2C 11 1 00 or
view m2call
CMUXE
CMUX
M2C 11 1 00
CMUXE
CMUX
ij=cmux group
k=cmux
nbsc 11 1
Fig. 60 Architecture of M2CM
M2CM
05 10 15
C C M M M M M M M M M M M M
M M 2 2 2 2 2 2 2 2 2 2 2 2
U U C C C C C C C C C C C C
X X 0 1 2 3 4 5 6 7 8 9 10 11
E E
# #
0 1
(Front View)
Fig. 61 Layout of module M2CM
MN3500EU50MN_0001
85
© 2005 Siemens AG
7.8 Diversity Hand-over Trunk Module (DHTM)

DHT (Diversity Handover Trunk) in the DHTM provides the diversity handover
function (macro diversity combining and splitting) in the RNC. The DHT is used for
every communication paths handled in the UMTS. Up to max 3 paths can be used
between the UE and RNC for channel diversity. This function is only applied for
dedicated channels.
When the UE moves and starts handover, the DHT can have 1 additional path to the
UE for the handover duration. This path is released after the handover sequence.
86 MN3500EU50MN_0001
© 2005 Siemens AG
RNC
LSW To/From
Node-B CN
a
DHT
UE Node-B
b
3 paths/call
Node-B
c
Node-B
d
Fig. 62 Macro diversity combining and splitting
RNC
LSW To/From
Node-B CN
a
Start DHT
Handover
Node-B
b
4
UE
paths/call
New path for Handover

Node-B (Temporary)
c
Node-B
d
Fig. 63 Macro diversity combining and splitting in handover
MN3500EU50MN_0001
87
© 2005 Siemens AG
7.8.1 MAC mapping

The DHT controls MAC (Medium Access Control) mapping of dedicated transport
channel (DCH). Then, the DHT executes multiplexing/de-multiplexing dedicated
logical channel (DCCH & DTCH) in the DCH.
88 MN3500EU50MN_0001
© 2005 Siemens AG
Transport ChannelRNC
Logical Channel
Up Link Up Link
DHT
DCH DCCH
DTCH
Down Link Down Link
Node-B DCCH
DCH
UE DTCH
Fig. 64 MAC mapping
CMUXG 10
CMUX 1
DHT 10 1 00 view dhtijklm

or
view dhtall
DHT 10 1 01
C1HWY
CMUX
C1HWY
CMUXE
ac1d 001 08 04
ij=cmux group
k=cmux
mswc 10 1
Fig. 65 Architecture of DHTM
MN3500EU50MN_0001
89
© 2005 Siemens AG
90 MN3500EU50MN_0001
© 2005 Siemens AG
DHTM
05 10 15
C C C C D D D D D D D D D D
M M 1 1 H H H H H H H H H H
U U H H T T T T T T T T T T
X X W W 0 1 2 3 4 3 6 7 8 9
E E M M
# # # #
0 1 0 1
(Front View)
Fig. 66 Layout of module DHTM
MN3500EU50MN_0001
91
© 2005 Siemens AG
7.9 Signaling Module (SIGM)

The SIGM terminates C-plane signals (signaling bearers) from Core Network &
Node-B. For this function, equipment links for RANAP protocols on the IuCS and
IuPO (CCS No.7 towards 3GMSC and SGSN), for NBAP and ALCAP protocols on
the IuB must be created in the database. In case of NodeB 530 another link for
emergency should be installed. This link is used for reset the NodeB in case of
failure. In the NodeB 440 a watch doc takes over this function.
Multi frame signal synchronization is also done in the SIGM. This signal is used for
Frame Number (FN) synchronization on the air interface.
It is possible to mix signaling links from Iub, Iu and Iur on the same ANC card.
However, this is not recommended because all these interfaces would need to be
blocked in case the card needs to be changed. Therefore, ANC cards should be used
for either Iub interfaces or Iu/Iur interfaces. For reasons of reliability, the ALCAP and
NBAP links of a Node B should be established on the same ANC card and overall
ANC resource usage should be distributed evenly over all ANC cards. This way, the
failure of an ANC card has at least effect in terms of dropped calls and the number of
Node Bs affected. If an ’even distribution’ allocation scheme is applied to a 4-rack
RNC configuration (which features an additional Signaling Module with 8 ANC cards),
there is a bandwidth limitation of 310 Mbit/s in the link between HUB and HUBM
which must be taken into consideration. Therefore it is advisable to use the Extension
SIGM for signaling links with lower bandwidth requirements.
The Signaling Module (B-SIGM) has six ANC cards.
Emergency Reset links (only applicable for Node B PF1) should be evenly distributed
over all available SIGMs. There is no need to manually assign ANC resources for ER
links because the command cre emlnk only takes the number of the CMUX of the
SIGM (nbsc xxx) as a parameter and ANC resources for ER links are assigned
internally by the RNC.
Number of ANC Links

ANC cards provide 64 link IDs when used for NNI signaling (Iu/Iur interface), or 128
link IDs when used for UNI signaling (Iub interface). Each Node B requires a VC for
NBAP and another for ALCAP.
92 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 11
CMUX 0
to HUB HUBIU
HUBIU
ANC 11 0 00 view ancijklm / view mfgijklm

ANC 11 0 01 or
view ancall / view mfgall
C1HWY
ANC 11 0 02
CMUX
C1HWY
CMUX
ac1d 001 10 00
ANC 11 0 03 ij=cmux group
k=cmux
MFG 11 0 06
MFG 11 0 07
nbsc 11 0
Fig. 67 Architecture of SIGM
SIGM
05 10 15
C C C C H H A A A A A A M M
M M 1 1 U U N N N N N N F F
U U H H B B C C C C C C G G
X X W W I I 0 1 2 3 4 5 0 1
# # M M U U
0 1 # # # #
0 1 0 1
(Front View)
Fig. 68 Layout of module SIGM
MN3500EU50MN_0001
93
© 2005 Siemens AG
7.9.1 MF interface
The MFG card receives the system clocks from the CLK (Clock) card in the CCPM
(Central Control Processor Module), and generates the MF (Multi-frame) signal for
radio frame synchronization between the DHTM, M2CM and MHM.
The MFG card works in non-duplex configuration, but they are working in
Master/Slave mode by software instruction. The Master MFG card selects the active
system clock from the CLK card, and generates MF signal. The Slave MFG is
synchronized to master MFG.
The Modules DHTM and M2CM receive MF signal through the B-CPI Interface and
the MHM receives the MF signal through MF signal interface.
94 MN3500EU50MN_0001
© 2005 Siemens AG
System Clock CCPM

#1
#0
MF Signal CLK
SIGM MF Signal
#1 MFG 0
#0 Master
Master
(ACT)
(ACT) MHM MHM
CMUX
MFG 1 #1 #1
Slave
Slave #0 #0
(SBY)
(SBY) CMUX CMUX
B-CPI
MHC MHC
#1
#0
CMUXE
DHT/
M2C
DHTM, M2CM
Fig. 69 Clock flow
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
95
© 2005 Siemens AG
7.10 GPRS Tunneling Protocol Module (GTPM)

The termination and load distribution (as well load sharing) of the packet-oriented
throughput is the responsibility of the GTPM.
The GTPM executes load sharing and multiplexing GTP-C/U (GPRS Tunneling
Protocol Controller/User data) by the tunneling protocol.
It receives U-plane data cells from the Iu interface. U-plane data handled in the
GTPM is the traffic channel data for packet.
The GTPM converts the VCI according to TEID (Tunneling Endpoint Identifier) in
GTP-U header. If the GMUX detects undefined IP packets or undefined TEIDs, these
packets are discarded because of the IP filtering function of the GTPM.
The U-plane data is then transported to PRLC modules in the PRM. They are
responsible for further processing of the user signals.
One of traffic flow handled in the GMUX is between the GMUX and the CN. It has
ATM-PVC connection with max 156 M bps bandwidth. Another traffic flow is between
the GMUX and the PRM. This flow has ATM-SVC connection with max 156 M bps
bandwidth.
TIP
An IP address is assigned to GMUX cards for the communication with the
SGSN. The throughput of a GMUX is 100 Mbit/s.
96 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 12
CMUX 0
to HUB
HUBIU
HUBIU
C1HWY
C1HWY
ac1d 001 08 06 view gmux120
12 = cmuxg
GMUX
GMUX
0 = cmux
C1HWY
C1HWY
ac1d 001 11 00
gmux 12 0
Fig. 70 Architecture of GTPM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
97
© 2005 Siemens AG
7.10.1 GTPM hardware layout eRNC
Fig. 71 Layout of the GTPM in eRNC
To/From
Other Trunk
Module
MPC Bus
GTPM
#1
#0
#1 #1
#0 #0 To/From
C1HW HUB
M HUBIU
To/From To/From
LSM PRM
#1 GMUX
#0
C1HW
M
Fig. 72 GTPM Functional Block
98 MN3500EU50MN_0001
© 2005 Siemens AG
7.10.2 GTPM hardware layout RNCplus
GTPM
05 10 15 20 25 30
B G B G C C C C H H B G R G C C C C B G B G C C C C B
L M L M 1 1 1 1 U U L M e M 1 1 1 1 L M L M 1 1 1 1 L
A U A U H H H H B B A U I U H H H H A U A U H H H H A
N X N X W W W W I I N X n X W W W W N X N X W W W W N
K # K # M M M M U U K # f # M M M M K # K # M M M M K
0 1 0 0 1 1 # # 0 o 1 0 0 1 1 0 1 0 0 1 1
# # # # 0 1 r # # # # # # # #
0 1 0 1 c 0 1 0 1 0 1 0 1
I
n
g
P
l
a
t
e
GTPE 0 GTPE 1 GTPE 2

(Front View)
Fig. 73 Layout of module GTPM cRNC
MN3500EU50MN_0001
99
© 2005 Siemens AG
7.11 Packet Radio Link Controller Module (PRM)

The PRM functions are terminating RLC (Radio Link Control) and PDCP (Packet
Data Convergence Protocol) protocol, which is the layer-2 protocol between UE and
RNC. Termination of the IP (Internet Protocol), UDP (User Datagram Protocol) and
GTP (GPRS Tunneling Protocol) between RNC and CN.
U-plane data handled in the PRM is the packet data on the dedicated channel &
common channel.
Traffic Monitoring
It monitors the occupancy of the traffic flows of common and dedicated channel
So it's possible, that the PRM does a dynamically change of the channel assignment
between common channel and dedicated channel according to the traffic volume of
each channel. This function provides efficient transportation of data cell.
Charging
PRLC provides charging for down link according to the traffic volume
Re-transporting
PRM tries to re-transport data cell when he detects cell loss between MS and PRLC.
Ciphering
The ciphering function is available between MS and PRM for security. This function
prevents unauthorized acquisition of data.
One of traffic flow handled in the GMUX is between the GMUX and the CN. It has
ATM-PVC connection with max 156 M bps bandwidth. And another traffic flow is
between the GMUX and the PRM. This flow has ATM-SVC connection with max 156
M bps bandwidth.
7.11.1 Modifications in the RNC HW/SW Architecture

By supporting HSDPA, the RNC must take care of flow control of the PS I/B data
stream between the RNC and the NodeB. This function is performed by the HS-
DSCH Frame Protocol. The higher data rates of PS I/B data traffic (compared to Rel
99 data rates) also require enhanced RNC data cards to cope with the throughput of
high peak data rates. This has resulted in a new design of two additional RNC
components, the HSDST cards located in the LSM and the HSPRLC cards located
in the PRM.:
HSPRLC
HSPRLC cards terminate IP/UDP/GTP-U on the Iu side and RLC/PDCP on the Iub
side. To perform traffic monitoring, charging and ciphering.
100 MN3500EU50MN_0001
© 2005 Siemens AG
CMUXG 14
CMUX 0
to HUB
HUBIU
via GTPM HUBIU
PRLC 140 00 view prlcijklm

PRLC 140 01 or
view prlcall
C1HWY
PRLC 140 02
CMUX
ac1d 001 12 06 C1HWY
CMUX
PRLC 140 03 ij=cmux group
k=cmux
pswc 14 0
Fig. 74 Architecture of PRM equipped with PRLC cards
CMUXG 14
CMUX 0
to HUB
HUBIU
via GTPM HUBIU
view hprlcijklm
HPRLC 140 01 or
view hprlcall
C1HWY
CMUX
C1HWY
ac1d 001 12 06
CMUX
HPRLC 140 03 ij=cmux group

k=cmux
even lm numbers not
used, HPRLC card
pswc 14 0 occupies two slots
Fig. 75 Architecture of PRM equipped with HPRLC cards
NOTE
The throughput of a PRLC card is given with 3Mbit/s. A HSPRLC card has got a
throughput of 20 Mbit/s.
MN3500EU50MN_0001
101
© 2005 Siemens AG
7.11.2 PRM Hardware layout in eRNC
The PRM modules can be equipped with PRLC or HPRLC cards
Fig. 76 Layout of the Card in PRM
7.11.3 PRM Hardware layout in RNCplus
102 MN3500EU50MN_0001
© 2005 Siemens AG
PRM (Basic)
05 10 15 20 25 30
R
B H H C C B P B P B P B P B P C e C B P B P B P B P B P B B B
L U U 1 1 L R L R L R L R L R M I M L R L R L R L R L R L L L
A B B H H A L A L A L A L A L U n U A L A L A L A L A L A A A
N I I W W N C N C N C N C N C X f X N C N C N C N C N C N N N
K U U M M K 0 K 1 K 2 K 3 K 4 E o E K 5 K 6 K 7 K 8 K 9 K K K
# # # # # r #
0 1 0 1 0 c 1
I
n
g
P
l
a
t
e
(Front View)
Fig. 77 Layout of module PRM (basic) RNCplus
PRM (Extension)
05 10 15 20 25 30
B B B C C B P B P B P B P B P C R C B P B P B P B P B P B B B
L L L 1 1 L R L R L R L R L R M e M L R L R L R L R L R L L L
A A A H H A L A L A L A L A L U I U A L A L A L A L A L A A A
N N N W W N C N C N C N C N C X n X N C N C N C N C N C N N N
K K K M M K 0 K 1 K 2 K 3 K 4 E f E K 5 K 6 K 7 K 8 K 9 K K K
# # # o #
0 1 0 r 1
c
I
n
g
P
l
a
t
e
(Front View)
Fig. 78 Layout of module PRM (Extension) RNCplus
MN3500EU50MN_0001
103
© 2005 Siemens AG
7.12 RNC Model Unit Overview
The following table gives an overview of the released RNC Model Units up to
UMR5.0, the number of racks per model unit and the number of supported NodeBs
per model unit.
For UMR5.0 no new Mixed Configuration RNC model unit was released, but new
configurations with 8 CLP were released for mixed RNC model units CMFLplus,
CMXplus and CMX(STM-1)plus.
In the interim release "UMR4.0HS" a few HSDPA versions were released.
Now in UMR5.0 HSDPA versions for all mixed RNC and enhanced RNC models
become available.
For mixed RNC models it is possible to migrate to HSDPA - Upgrade versions by
adding some HSPRLC cards (and eventually an additional B-PRM module or an
additional GMUX in the GTPM module, or both), and - for most model units - to use
the new HSPRLC cards together with some of the elder PRLC cards that were there
before.
WARNING
The classic RNC models cRNC (without the "plus") are not any more supported
in UMR5.0.
104 MN3500EU50MN_0001
© 2005 Siemens AG
RNC Model Units and Parameters since

eRNC Model Units (RNC e...) UMR Release
Number of racks Number of NodeBs
RNC eS 2 64 UMR 3.0

RNC eM 3 1923)/256 UMR 3.0/3.54)
RNC eCMF 3 384 UMR 3.0/3.54)
RNC eS (STM-1) 2 128 UMR 3.0
RNC eCS 2 1923)/256 UMR 3.0
RNC eCLS 3 384 UMR 3.0
RNC eM (STM-1) 2/34) 1923)/256 UMR 3.0/3.54)

RNC eCMF (STM-1) 3 384 UMR 3.0/3.54)
RNC Mplus 4/54) 2882)/352 UMR 3.0/3.54)
RNC CMFplus 5 448 UMR 3.0/3.55)
RNC CLSplus 4 448 UMR 3.0
RNC eCML 4 512 UMR 3.5/4.07)/5.08)
RNC eCMX (revised) 5 512 UMR 3.5/4.07)/5.08)
RNC eL 4 384 UMR 3.5/4.07)/5.08)
RNC eCML (STM-1) 3/46) 7) 8) 512 UMR 3.5/4.07)/5.08)
RNC eCMX (STM-1) 4 512 UMR 3.5/4.07)/5.08)
RNC eL (STM-1) 3/46) 7) 8) 3202)/384 UMR 3.5/4.07)/5.08)
RNC Splus 3 1923)/224 UMR 3.5
RNC CMFLplus 5/67) 8) 512 UMR 3.5/4.07)/5.08)
RNC CMXplus 6 512 UMR 3.5/4.07)/5.08)
RNC CMX (STM-1) plus 6 512 UMR 3.5/4.07)/5.08)
RNC Lplus 5 3682)/480 UMR 4.0
RNC MSplus 4 3682)/480 UMR 4.0
RNC CSXplus 5 3682)/480 UMR 4.0
RNC eXL (revised) 5 4483)/512 UMR 5.0
RNC eXL (STM-1) (revised) 5 4483)/512 UMR 5.0
Fig. 79 RNC model units UMR5.0
MN3500EU50MN_0001
105
© 2005 Siemens AG
• Explanation to table "RNC model units UMR5.0"

1. Higher number valid with trunking option (= 2 * STM-1 / 126 NodeBs per 3
CMPM) as interim solution, but with UMR3.x introduction of WCMP the trunking
option is not any more supported. for a connection bit rate per NodeB of 2 * E1.
2. Valid for a connection bit rate per NodeB of 2 * E1
3. Valid in case of using optional feature “SMS Cell Broadcast”
4. Valid if with 4 CLP Option
6. Valid if with 6 CLP Option or with 7 CLP Option
106 MN3500EU50MN_0001
© 2005 Siemens AG
8 Examples of model units
MN3500EU50MN_0001
107
© 2005 Siemens AG
8.1 Configuration of model unit eS

Model Unit eS provides the connectivity for:
• 64 E1 lines at Iub
• 0 STM-1(o) lines at Iub
(no TINF)
• 1 (redundant) STM-1 (o) at Iu/Iur
(2 TINFs)
• 1500 Erlang (CS voice)
• 24 Mbps PO-throughput
• 1 WCMP for Iub (64 NodeBs with 2 VCs)
• 1 (redundant) WCMP for Iu/Iur
• 64 NodeBs ( 1xE1* per NodeB, 1 VP per NodeB)
• up to 192 cells
number of TINFs
for Iub 0
for Iu/Iur 2
for internal connections 4
Spare 1
Total 7
Number of TINF for Model Unit eS
number of WCMPs
for Iub 1
for Iu/Iur 2
Total 3
Number of WCMPfor Model Unit eS
108 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE FUSE
FAN FAN
B -M H M C -D H T M
100 101
D -L S M
B - S IG M C -M 2 C M
110 111
FAN FAN
C -G T P M B -P R M
E -C C P M
120 130
A - D T IM
D -C C P M
140
D -L S F (0 0 1 ) H -T R K F (0 0 1 )
Fig. 80 Rack layout of Model Unit eS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
109
© 2005 Siemens AG
Configuration of the D-LSF

Slot Occupancy Remarks
16
17
18
19
20
21
22 WCMP #0 WCMP for Iu/Iur (redundant)
24
25
26
27
28
29
30
31 WCMP WCMP for Iub (non redundant)

0 TINF 00 #0 Port 0 for Iu/Iur (and Clock extraction)
1 (TINF 00 #1) (Port 0 for Iu/Iur (and Clock extraction))
2 TINF 02 Port 0 for ATM/Ethernet Converter
3
4
5
6
7
8 TINF 08 #0 B-MHM (00), C-DHTM (02), B-SIGM (04), C-GTPM (06)
9 TINF 08 #1
10 TINF 10 #0 C-GTPM (00), B-PRM (02), A-DTIM (04)
11 TINF 10 #1
12
13
14
15
Fig. 81 D-LSF Configuration for Model Unit eS
TIP
Slot 0 – 1 show the configuration of the Iu/Iur interface in dual mode. However, it
depends on the customer network planning, whether or not the Iu/Iur is operated in
dual mode or single mode.
Slot 2 shows the configuration of the ATM/Ethernet Converter. This is just a
recommendation and depends on the customer network planning.
110 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 82 D-LSF Configuration for Model Unit eS
Trunk Physical Module Name Logical Hub-Node CMXG-Nr CMUX-Nr

Frame Module Number
Name
D-LSF D-CCPM CP00 0
E-CCPM CP01 1
CP02 2
LSM WLSC 3
H-TRKF B-MHM MswcB 8 10 0

(001) C-DHTM MswcE 1
(2nd rack) B-SIGM NbscB 9 11 0
C-M2CM NbscE 1
C-GTPM GmuxB 10 12 0
B-PRM PswcB 74 13 0
A-DTIM DtscB 11 14 0
Fig. 83 Assignment of Hub Node Numbers and HW Addresses for Model Unit eS
MN3500EU50MN_0001
111
© 2005 Siemens AG
8.2 Configuration of model unit eS (STM-1)

Model Unit eS (STM-1) provides the connectivity for:
• 0 E1 lines at Iub
• 2 STM-1(o) lines at Iub (non-redundant)
(1 TINF without line redundancy)
optional: 2 STM-1 (o) lines at Iub (redundant)
(2 TINFs with line redundancy)
• 1 (redundant) STM-1 (o) at Iu/Iur
(2 TINFs)
• 1500 Erlang (CS voice)
• 24 Mbps PO-throughput
• 2 WCMP for Iub (128 NodeBs with 2 VCs)
• 1 (redundant) WCMP for Iu/Iur
• 128 NodeBs (= 2x64)
( 1xE1* per NodeB, 1 VP per NodeB)
• up to 384 cells
number of TINFs
for Iub (non-redundant) 1
Opt.: for Iub (redundant) 2
for Iu/Iur 2
for internal connections 4
Spare 1
Total 8/9 (9 in case of Iub redundant)
Number of TINF for Model Unit eS (STM1)
number of WCMPs
for Iub 2
for Iu/Iur 2
Total 4
Number of WCMPfor Model Unit eS (STM1)
112 MN3500EU50MN_0001
© 2005 Siemens AG
FUSE FUSE
FAN FAN
B-MHM C-DHTM
100 101
B-LSM
C-GTPM
110
FAN FAN
B-SIGM C-M2CM
E-CCPM
120 121
B-PRM
D-CCPM
130
D-LSF (001) H-TRKF (004) (B)
Fig. 84 Rack layout of Model Unit eS (STM1)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
113
© 2005 Siemens AG
Configuration of D-LSF
16
17
18
19
20
21
24
25
26
27
28
29

0 TINF 00 #0 Port 0 for Iu/Iur (and Clock extraction)
1 (TINF 00 #1) (Port 0 for Iu/Iur (and Clock extraction)
2 TINF 02 Port 0 for ATM/Ethernet Converter
3
4 TINF 04 #0 Port 0 and 2 for Iub
5 (TINF 04 #1) (Port 0 and 2 for Iub in case of redundancy)
6
7
8 TINF 08 #0 B-MHM (00), C-DHTM (02), C-GTPM (06)
9 TINF 08 #1
10 TINF 10 #0 C-GTPM (00), B-SIGM (02), B-PRM (04)
11 TINF 10 #1
12
13
14
15
Fig. 85 D-LSF Configuration for Model Unit eS (STM1)
TIP
Slot 0 – 1 show the configuration of the Iu/Iur interface in dual mode. However, it
depends on the customer network planning, whether or not the Iu/Iur is operated in
dual mode or single mode.
Slot 2 shows the configuration of the ATM/Ethernet Converter. This is just a
recommendation and depends on the customer network planning.
Slot 4 – 5 show the configuration of the Iub in dual mode. However, it depends on
the customer network planning, whether or not the Iub is operated in dual mode or
single mode.
114 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 86 -LSF Configuration for Model Unit eS (STM-1
Trunk Physical Module Name Logical Hub-Node CMXG-Nr CMUX-Nr

Frame Module Number
Name
D-LSF D-CCPM CP00 0
E-CCPM CP01 1
CP02 2
LSM WLSC 3
H-TRKF B-MHM MswcB 8 10 0

(004) (B) C-DHTM MswcE 1
(2nd rack) C-GTPM GmuxB 9 11 0
B-SIGM NbscB 10 12 0
C-M2CM NbscE 1
B-PRM PswcB 11 13 0
Fig. 87 Assignment of Hub Node Numbers and HW Addresses for Model Unit eS (STM-1)
MN3500EU50MN_0001
115
© 2005 Siemens AG
8.3 Configurations of RNCplus

8.3.1 Model unit Lplus
The model unit Lplus is a cRNC/eRNC mixed configuration model unit Mplus
expanded with eRNC components for medium traffic volumes using E1 and STM-1
lines on the Iub interface. Up to 480 NodeBs can be connected via 6 (optional: 10)
STM-1 lines and 96 E1 lines, with 1 E1 line per NodeB (E1=1.92 Mbps) and 1 VP per
NodeB (optionally 368 NodeBs with 2 E1 lines per NodeB).
The extended processing capacity and connectivity compared to model unit Mplus is
supplied via additional WCMP cards in the B-LSF frame and additional STM-1 lines
in this five-rack configuration.
See the next table for an overview on performance parameters and interfaces.
116 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 88 Model Unit Lplus
Fig. 89 Performance Parameter model unit Lplus
MN3500EU50MN_0001
117
© 2005 Siemens AG
118 MN3500EU50MN_0001
© 2005 Siemens AG
9 Additional information
MN3500EU50MN_0001
119
© 2005 Siemens AG
9.1 Function assignment of the trunk modules

9.1.1 User Plane CS
In the Circuit Switched User Plane only Dedicated Transport Channels (DCH) are
used. The Inter-working Function of the MSC is inserting the PCM voice samples into
ATM-cells using AAL2.
AAL2 is a container for all kind of protocols for Real Time and Non Real Time Data
with variable Bit rates. Since the Iub and Iu Interfaces can be considered as
dedicated lines between the Node B, RNC and the MSC, the connection oriented
AAL2 is used.
Inside the RNC, for switching purposes the samples in the AAL2 container have to be
separated into single AAL2d (AAL2-decomposite) cells for only one subscriber each.
This function is done in the CMPM. In case of an E1-Interface the CMPM is
additionally equipped with DTI (Digital Transmission Interface).
The figures show a simplified scheme of the Trunk modules.
All connections between the Trunk modules are switched through the LSM (Line
Switch Module) with the corresponding TINF cards. This is not specially indicated.
The input/output units of the Trunk modules to the LSM are C1-Highways, which lead
on the other side to the CMUX/CMUXE inside these Trunk modules.
The DHTM is relaying the Adaptive Multi-rate frames (AMR) from the MSC to the
DCH-frames assigned by RLC/MAC.
120 MN3500EU50MN_0001
© 2005 Siemens AG
CMPM DHTM CMPM
IUB CMP DHT CMP
E1 DTI C1HWM C1HWM C1HWM C1HWM C1HWM
AAL2 – AAL2d RLC/MAC – IuUP AAL2d – AAL2

Transparent Mode
Frame Protocols
T T T T T T
IUCS
I I I I I I
SW SW SW
N N N N N N
MSC
F F F F F F
LSM LSM LSM
Fig. 90 User Plane CS
DTIM DHTM
IUB MDTI DHT
E1 C1HWM C1HWM C1HWM
RLC/MAC – IuUP
Transparent Mode
Frame Protocols
T T
I same TINF I
T N N T
I F F I IUCS
SW SW
N W W N
F F MSC
C C
AAL2 – AAL2d –
M M
AAL2d AAL2
P P
LSM LSM
Fig. 91 User Plane CS eRNC
MN3500EU50MN_0001
121
© 2005 Siemens AG
9.1.2 User Plane PS

User data from the SGSN, in most cases applications over IP, are transferred via the
Iu Interface in an encapsulated form by the GTP-U. The GTPM is multiplexing the
subscriber data streams, converting their TEID into VCI in the GTP-U header and
forwarding them to the PRM.
The PRM relays the Protocol stack GTP/UDP/IP into PDCP/RLC and converts the
incoming AAL5 for switching purposes into the internal AAL2d.
For packet switched traffic either Dedicated transport channels or Common transport
channels can be used depending on the type (QoS) and volume of data. This
decision is done in the PRM.
Further functions of the PRM are Backward Error Correction (BEC), ciphering,
charging in Downlink if requested.
The MAC is handled together with Multiple Diversity (Macro Soft Hand-over) in the
DHTM for Dedicated transport channels.
The MAC is handled in the MHC for Common transport channels.
The CMPM is converting AAL2d into AAL2, which is used on the Iub not only for RT
but also for NRT (PS) data. The AAL5 Routing function for connectionless traffic used
in the PS Core Network is on the Iub no more necessary.
122 MN3500EU50MN_0001
© 2005 Siemens AG
Dedicated Transport Channels

DHTM
MAC: LogCH – Transp.CH
DHT Multiple Diversity
AAL2d
C1HWM C1HWM
RLC/PDCP – GTP/UDP/IP Load Sharing
Dedic.TrCH / Comm.TrCH Multiplexing
BEC, Ciphering TEID to VCI in DL
SW SW Charging DL Multiprotocol packets
CMPM PRM GTPM
ATM- ATM-PVC
CMP PRLC GMUX SVC
IUB AAL2 – AAL2d AAL2d – AAL5 AAL5 T T IUPS
I I
SW
E1 DTI C1HWM C1HWM C1HWM C1HWM C1HWM N N SGSN
F F
LSM
MHM
T T T T T T
I I I I I I
SW C1HWM C1HWM SW SW
N N N N N N
F F AAL2d F F F F
MHC
LSM Common Transp. LSM LSM

Channels
RACH, FACH
Fig. 92 User Plane PS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
123
© 2005 Siemens AG
9.1.3 Control Plane for Interface Protocols

NBAP:
All signaling messages are transferred via the Iub by AAL5. Since signaling channels
are permanently configured (PVC’s) through the LSM and further to the Central
Processor, the CMPM is only passed and does not change the AAL5 cells into
AAL2d.
The next module is the SIGM. The signaling is passing C1HWM – CMUX – ANC- -
CMUX – HUBIU. It converts the AAL5 cells into AAL3/4 to adapt the signaling
primitives to the needs of the CCPM. Hereby, another ATM sublayer, the SSCF
(Service Specific Coordination Function) for support of signaling at the UNI (User-
Network-Interface) is applied.
Finally, the primitives are transferred through the HUB to the Central Processor.
RNSAP:
All signaling messages are transferred via the Iur by AAL5. For all other details see
NBAP.
RANAP:
All signaling messages are transferred via the Iu by AAL5. Since the connection to
the Core Network is based on STM-1 in the physical layer, the connection to the LSM
is direct via a TINF card (no CMPM!).
In the SIGM, the ANC (ATM Adaptation Layer Controller) applies the SSCF for
support of signaling at the NNI (Network-Network-Interface).
Finally, the primitives are transferred through the HUB to the Central Processor.
9.1.4 Control Plane for Radio Protocols

Contrary to the Interface Protocols with AAL5, the Radio Protocols (RRC, RLC, MAC)
use AAL2. Since the User Plane also needs RLC/MAC, the data of C- and U-Plane
are multiplexed together in Dedicated or Common Transport Channels on the Iub.
RLC/MAC is a Layer2 protocol, RRC is the only Layer3 protocol and treated in the
CCPM.
C-Plane data is comparable to U-Plane PS data (data packets). Therefore, the
signaling route is partly using the same modules and the same separation between
Dedicated and Common Transport Channels as User Plane PS.
Since the M2CM has no direct connection neither to the LSM nor to the HUB, the
signaling from DHTM has to pass the SIGM using its C1HWM, CMUX and its
HUBIU. The Primitives are transferred to the HUB link, HUB and CCPM.
Here the RRC (e.g. switching between dedicated and common transport channels) is
performed.
124 MN3500EU50MN_0001
© 2005 Siemens AG
Node B NBAP
(D-RNC) (RNSAP)
C T T C
IUB D 1 1
CMPM I I SIGM SSCF-UNI CCPM
T H
N
SW
N
H
Primitives
HUB
(IUR) I CMP W W ANC CLP
Y F F Y
AAL5 – AAL5 AAL5 – AAL3/4 AAL3/4

passed by PVC C1HWM-CMUX-ANC-CMUX-HUBIU
LSM
MSC/SGSN RANAP
T T C
IU 1
I I SIGM SSCF-NNI CCPM
N
SW
N
H
Primitives
HUB
STM-1 AAL5 W ANC CLP
F F Y
AAL5 – AAL3/4 AAL3/4

C1HWM-CMUX-ANC-CMUX-HUBIU
LSM
Fig. 93 C-Plane Interface Protocols (IUB, IUR, IU)
Dedic.Log.CH – Dedic.Tr.CH
C C C
1 DHTM M
C
M
M2CM
M
H DHT U U SIGM U RLC-C/
W X X
Y
MAC E
X
HUBIU E MPC
AAL2d AAL2d-AAL3/4
Iub L3
Node B
C T T
E1 D 1 Primitives
T CMPM I I CCPM
H
N
SW
N
HUB
I CMP W RRC, CC/ MM
Y F F L2
AAL2-AAL2d AAL3/4
LSM
C H
1
MHM U Primitives
H B
W RLC-C/ MAC I
Y U
AAL2d-AAL3/4
Common Log.CH – Common Tr.CH
Fig. 94 C-Plane Radio Protocols
MN3500EU50MN_0001
125
© 2005 Siemens AG
126 MN3500EU50MN_0001
© 2005 Siemens AG
10 RNCi/RN-880 HW platform
MN3500EU50MN_0001
127
© 2005 Siemens AG
10.1 Introduction
The Radio Network Controller (RNC) is the central network element in the UMTS
Radio Access Network (UTRAN) responsible for mobility management, call
processing, radio resource management, link maintenance and handover control.
The RNCi (RN-880) is a highly innovative and trend setting world market product best
suited for current ATM/SDH based UTRAN infrastructure, and future distributed IP
based Radio Access Networks. It is fully compatible with the existing Siemens/NEC
UTRAN products (Node B, eRNC, RC).
The RNCi is the newly developed powerful successor of the cRNC/eRNC (RN-750).
It is based on a superior state-of-the-art server blade architecture implemented on
the Siemens NgTA platform (Next Generation Telecom Architecture) and provides a
dramatic improvement in terms of both flexibility and processing capacity combined
with optimized footprint. The next figure shows a sample configuration with 1 rack
and 3 shelves.
Usage of the latest technology allows unreached performance values:
• • 1800 Mbps Iub throughput
• • 38.000 Erlang.
• • 512 NodeB
• • 500.000 BHCA
128 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 95 RNCi (sample configuration with 1 rack and 3 shelves)
MN3500EU50MN_0001
129
© 2005 Siemens AG
10.1.1 Innovative Server Blade Architecture

The RNCi provides a very modular, highly scalable, and reliable architecture based
on an innovative server blade architecture which is characterized by the following:
• Based on next generation telecommunication platform using
– Server blades
– ATCA standard
• World leading performance density
• Optimized reliability/availability, best suited for radio applications
• Logical separation of control and user / transport plane
• Completely scalable on blade, shelf, and rack level
• Intra shelf, inter shelf/rack communication via Gigabit Ethernet (GE) switches
• ATM and IP capable
130 MN3500EU50MN_0001
© 2005 Siemens AG
10.1.2 Supported Services and Applications

The RNCi provides future-proof support of services which are attractive for both
operators and end-users. The RNCi is particularly suitable for applications with high
requirements to data transfer volume or Quality of Service such as:
• Video streaming
• Audio streaming
• Real-time gaming
• Multiple sessions (Multiple PDP contexts)
• High Speed Data Package Access (HSDPA)
• Service based handover (Rel. 2)
• Multimedia broadcast/Multicast services (MBMS) (Rel. 2)
• Location service A-GPS (Rel. 2)
MN3500EU50MN_0001
131
© 2005 Siemens AG
10.2 General RNCi Architecture

The RNCi is embedded in the UMTS Radio Access Network (as standardized by 3rd
Generation Partnership Project (3GPP).
This chapter provides a general overview of the RNCi with respect to its functional
(logical) and system (HW/SW) architecture.
132 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 96 The Radio Network Subsystem (RNS)
MN3500EU50MN_0001
133
© 2005 Siemens AG
10.2.1 Logical Architecture

The RNCis functionality is split up into the following logical functional entities, all
within the same network entity:
Control Plane (C-Plane)
The C-Plane terminates the 3GPP control-plane signaling protocols. It also triggers
the U-Plane and T-Plane to allocate and release resources. The communication
between the C-Plane and the U-Plane and the T-Plane is realized over an internal
interface.
User Plane (U-Plane)
The U-plane terminates the 3GPP FDD Uu protocols as well as the FP on the Iub, Iur
and Iu interfaces. The U-plane provides interfaces to C-plane and T-plane for
configuration, measurements data transfer and exchange of bindings. It also forwards
signaling over the radio interface via common or dedicated transport channels.
Furthermore U-plane interfaces with OAM plane via the OAM interfaces.
Transport Plane (T-Plane)
The T-Plane terminates physically the Iub, Iur and Iu interfaces and it handles all the
functionality related with these interfaces.
Operation and Maintenance Plane (OAM-Plane)
The OAM-Plane terminates the external operation and maintenance interfaces of the
RNCi. It interfaces to U-/T-Plane and C-Plane via internal interfaces and controls the
RNCi from operational point of view.
134 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 97 High-level overview of the RNCi functional architecture
MN3500EU50MN_0001
135
© 2005 Siemens AG
10.2.2 System Architecture

The RNCi system architecture consists of the following components:
• Hardware: ATCA compliant
• Operating System: Carrier Grade Linux
• Middleware: basic services for a stable, highly available system
• RNCi C-plane application: C-plane related functions
• RNCi U-plane application: U-plane related functions
• RNCi T-plane application: T-plane related functions
• RNCi OAM: OAM plane related functions
136 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 98 RNCi system architecture overview
MN3500EU50MN_0001
137
© 2005 Siemens AG
C-Plane application
• System Access Control
• Admission/Congestion Control
• Mobility Management, e.g. handover, cell update, positioning
• Radio Resource Management
• External protocol control: RRC, NBAP, RANAP, RNSAP
• Coordination of U-/T-plane resources
• Performance Measurements
• Call Tracing
OAM-Plane application
• Operation and Maintenance: configuration, state, fault, SW, security, test,
performance management of RAN, transport and equipment domain
• Communication with OMC/LMT
T-Plane application
• Management of T-Plane resources
• Handling of the physical transport layer
• Handling of the external transport and signaling bearers
• Control of all internal transport and signaling information
• Performance measurements for T-plane layers
U-Plane application
• Management of U-Plane resources
• Handling of all user plane protocols:
• Iub, Iur frame protocols
• Iu UP layers
• RLC, MAC, PDCP, BMC
• Performance measurements for U-plane layers
• Configuration of U-plane resources
138 MN3500EU50MN_0001
© 2005 Siemens AG
Middleware and OS
• Process and memory management
• Basic System, HW and SW maintenance to ensure high availability services
• Reliable communication services
• Database Management System
• Debug & Trace Management
• Timer Management
• Controlled and reproducible system start-up
• SW and HW error detection and recovery
• HW redundancy support
MN3500EU50MN_0001
139
© 2005 Siemens AG
10.2.3 Interfaces
The RNCi provides full interoperability with existing Siemens/NEC UTRAN products
(Node B, eRNC, RC) and other vendor products (at multi-vendor UTRAN interfaces
Iu, Iur). An overview is given in next figure.
The following interface characteristics apply:

• The Iu and Iub interfaces are connected as STM1.
• Each NodeB requires at least one VP, therefore the maximum number of VPs is
important for the potential network topologies. If IMA is applied (not available for
Node B PF1) several E1 can be combined to one VP, otherwise each E1 carries
at least one dedicated VP.
• If AAL2-Switching is used in CN then both MSC node and adjacent RNCs must
support AAL2 switching.
Using the external interfaces the RNCi provides:

• Configuration of features such as Policing, Traffic Shaping, Overbooking.
• Blocking/Unblocking of VP and VC on Iub, Iu, Iur and State Management for
VPPVC, VC-PVC and Cross Connections or maintenance.
• Configuration of VPs, VCs and VP Cross Connections.
For Fault Management purposes, RNCi at ATM Layer supports:

• Transmission of AIS-cells (Alarm Indication Signal) for reporting defect
indications in the forward direction
• Transmission of RDI-cells for reporting remote defect indication in the backward
direction
• ATM OAM Loop backs (F4/F5 segment and end-to-end, as insertion point and
as loop back point, segment loop backs at intermediate points)
• OAM Continuity Check
140 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 99 External Interfaces
Using the external interfaces the RNCi provides:

• Configuration of features such as Policing, Traffic Shaping, Overbooking.
• Blocking/Unblocking of VP and VC on Iub, Iu, Iur and State Management for
VP-PVC, VC-PVC and Cross Connections or maintenance.
• Configuration of VPs, VCs and VP Cross Connections.
For Fault Management purposes, RNCi at ATM Layer supports:

• Transmission of AIS-cells (Alarm Indication Signal) for reporting defect
indications in the forward direction
• Transmission of RDI-cells for reporting remote defect indication in the backward
direction
• ATM OAM Loop backs (F4/F5 segment and end-to-end, as insertion point and
as loop back point, segment loop backs at intermediate points)
• OAM Continuity Check
MN3500EU50MN_0001
141
© 2005 Siemens AG
10.3 Hardware Architecture

10.3.1 ATCA Based Platform
ATCA (Advanced Telecom Computing Architecture) is an open industrial standard for
new hardware platforms in carrier grade networks. ATCA was published in late 2003
by the PCI Industrial Computer Manufacturers Group (PICMG), a committee of more
than 100 IT and telecom companies. In this standard, PICMG defines the industry's
requirements for the next generation of telecommunication platforms: a modular,
interoperable and scalable hardware platform for communication and data
applications.
ATCA is intended as a common hardware platform for computing and
telecommunications equipment. It provides the high availability necessary for central
office applications. These applications almost always require European
Telecommunication Standard Institute (ETSI) and Network Equipment Building
System (NEBS) compliance.
The ATCA family of standards was designed specifically to meet and exceed the
stringent requirements of telecommunications network elements. Beyond that, ATCA
incorporates extensive experience with its precursor standards consolidated on a
new basis. It defines numerous important properties of the equipment practice.
Key advancements of ATCA include the following:

• A high-capacity (up to 2.5 terabits), packet-based backplane coupled with low
latency enables ATCA systems to process workloads more quickly.
• A highly scalable, switched fabric architecture (initially based on Gigabit
Ethernet and eventually accommodating InfiniBand, StarFabric, and PCI
Express interconnects) overcomes the I/O bottlenecks created by conventional
bus-based architectures.
• Support for up to 200 watts per board and as many as 16 boards per shelf
significantly increases performance density, enabling each blade to have two or
more high-end processors through improved heat dissipation.
• At least two power modules and two power rails to each slot provide hardware
redundancy, reducing single points of failure.
• Support for carrier-grade availability of at least 99.999 percent.
142 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 100 ATCA shelf
MN3500EU50MN_0001
143
© 2005 Siemens AG
10.3.1.1 Mechanical
Blade size of 322 mm by 280 mm, 30 mm pitch allows complex circuits on a single
blade. Blades have hot swap capability, which is a fundamental requirement for high
availability telecommunications products.
10.3.1.2 Connector Zones and Types

The backplane (which is actually a mid-plane) contains the connectors in three
zones:
• Zone 1
provides mandatory and fixed connectivity for shelf management, power
distribution and hardware addressing
• Zone 2
contains redundant Gigabit Ethernet (base fabric) connectors, redundant
extended fabric connectors (optional) and synchronization clocks (optional).
• Zone 3
contains the (optional) connectors between blades and their associated rear
transition modules. These connectors are regarded as blade specific and
beyond the usable space not defined by ATCA. Since these connectors are part
of the blades this zone is normally simply cut out in the backplane.
Nevertheless, for specific solutions, Zone 3 (partial) backplanes can be suitable,
e.g. to provide connectivity between slots for protection switching. Such partial
Zone 3 backplanes are foreseen by ATCA, but out of scope of the
standardization.
144 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 101 ATCA switching blade
Fig. 102 ATCA rear transmission module
MN3500EU50MN_0001
145
© 2005 Siemens AG
146 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 103 ATCA equipment practice
MN3500EU50MN_0001
147
© 2005 Siemens AG
10.4 General Hardware Platform

The RNCi HW platform consists of ATCA compliant shelves with HW management,
Ethernet switches with central clock generator and different application specific
blades.
The RNCi HW architecture is a modular system based on the "Advanced
Telecommunication Computing Architecture" (ATCA). As standardized in PICMG 3.0,
ATCA defines an equipment practice for boards and shelves, a HW management
system and a framework of interconnect technologies.
The equipment practice of ATCA defines different shelf widths with different numbers
of slots. For RNCi ETSI 600mm shelves are used with 14 universal slots for blades
(GPP or NP blades) and 2 slots for the Gigabit Ethernet switch.
The internal connectivity for control as well as for user data traffic is provided by
redundant Gigabit Ethernet switches. To ensure scalability the GE switch of one shelf
provides additional GE interfaces for inter-shelf communication. The next figure
shows a configuration with three fully equipped shelves in one RNCi rack. Each GE
Switch (GES) in the RNCi shelf provides up to 7 GE links per redundant plane for
inter-shelf communication.
148 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 104 Basic architecture of RNCi
Fig. 105 Inter-shelf communication
MN3500EU50MN_0001
149
© 2005 Siemens AG
10.4.1 Rack
The RNCi rack is a physical and logical entity that is specifically designed as a
reinforced Slime-Line Frame. Up to 3 shelves in which the blades are mounted and a
DC-/Breaker Panel are integrated within one rack. In compliance to the ATCA
standard the shelf numbering starts from shelf 1 at the bottom to shelf 3 at the top
position. A connector panel for connecting all necessary cables to the outside is
mounted on top of the rack. Signaling and DC cables can also be connected via
cable duct from the raised floor. For transportation of the rack 4 threads are located
in each corner on top of each rack to screw eye bolts. Each rack has feet with an
adjustable range of about 25 mm to level unevenness of the bottom. Claws to fix the
feet on the ground are part of the RNCi delivery. On top of each rack, lamps (Alarm
Signaling Panel) signalize alarms and warnings, which were generated from the
ACT/Rack Manager (Alarm Collection Terminal) that processes the alarms from the
modules/blades (via maintenance) implemented within this rack.
The RNCi rack consists of the following parts:
• "7ft. rack"
– Frame (EMC incl. earthquake feature)
– Side panel set
– Rear door partly perforated with three air ducts
– Front door partly perforated
– Top cover for cable entry
– Base plate / plinth
– 4 eye bolts on rack roof for lifting
– Grounding Cables
– 4 adjustable feet with an adjustable range of 25 mm
– Earth Bonding Points (EBP) at the front and rear side of the rack
– Cable guides
– EMC gasket
• Intra rack cables
• Optical cables
• Cabling (power supply and rack manager) incl. thermostat and door switches
• Main Supply Unit (MSU) on rack roof providing Terminal Blocks for a nominal
current of 250 A and filters for EMI and lightning protection
• DC-Panel on the upper side of the rack for power distribution, providing circuit
breakers for overload protection
• Lamp Panel on front door providing three Rack Alarm Lamps
• Interface board (ECIB)
• 3 ATCA shelves meeting the dimensions of the ETSI standard
150 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 106 Rack front view with 3 shelves
MN3500EU50MN_0001
151
© 2005 Siemens AG
The main characteristics of the RNCi rack hardware are:

• ETSI-600mm equipment practice shelves with 16 slots.
• Redundant power supply based on nominal voltage of -48VDC.
• Redundant HW Management system:
Redundant Shelf Managers with redundant access to each slot and platform
infrastructure modules (fan tray) as well as access to the shelf FRU data
storage (comprising remote inventory data of the shelf and configuration data of
the shelf)
• Interconnects
– Base Interface: Dual star Gigabit Ethernet transport architecture (Zone 2)
– Fabric Interface: Dual star fabric interface for future extensions (Zone 2)
– HW Management: Dual bus (IPMB) to ATCA slots and infrastructure modules
(Zone 1) (e.g. Shelf Alarm Panel (SAP)) from each ShMgr (Shelf Manager) Dual
Star (I2C) to shelf FRU data storage
– Power distribution: Redundant with isolated power feed return lines (Zone 1)
– Update ports: 10 pairs between adjacent pairs of ATCA blades (Zone 2)
– Telecom clocks: 3 redundant differential clock lines to all slots (Zone 1)
152 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 107 Interconnects (examples)
MN3500EU50MN_0001
153
© 2005 Siemens AG
10.4.1.1 Connector Panel

The Connector Panel is integrated in the top of the RNCi rack.
It supports all interfaces and connections to and from the RNCi, including the
following:
• Connectors for 48 optical STM-1 interfaces (STM-1 and OC-3 SDH/SONET
interfaces make use of the same HW)
• 2 x 2 RJ45 connectors for OMC-R/RC (connected with the two OMM blades)
• Clamps / connectors for external alarm inputs and command outputs
• 4 x RJ45 for external clock interface
• Redundant -48V DC power supply
Beside the connectors, the Connector Panel houses the EMI-filtering on rack level
and the ACT/Rack Manager module.
154 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 108 Connector panel
Fig. 109 Principle design of the connector panel
MN3500EU50MN_0001
155
© 2005 Siemens AG
10.4.1.2 Main Supply Unit

The Main supply Unit (MSU) is located on the rack roof. The MSU provides the main
terminal blocks for the connection of Feed A and B and the EMI filters. The terminal
blocks are designed to accept a cable cross section from 50 mm² to 120 mm².
The main Feeds A and B are routed from the main terminal blocks through the EMI
filters to the power distribution rail of the DC Panel.
156 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 110 Main Supply Unit
MN3500EU50MN_0001
157
© 2005 Siemens AG
10.4.1.3 DC Panel
The DC Panel is located on the front top side of the rack. The DC Panel provides the
power distribution to the shelves and the Rack Manager. The DC Panel splits the
main feeds A and B from the MSU into 24 sub-feeds to the shelves and 2 subfeeds to
the Rack Manager. Each subfeed is separately fused by a circuit breaker.
158 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 111 DC panel
MN3500EU50MN_0001
159
© 2005 Siemens AG
10.5 Blades
The blades used in the RNCi are generally characterized by the following:
• ATCA equipment practice
• Gigabit Ethernet transport
• On-board power supply with redundant power feed lines
• On-board IPMI Controller (remote inventory, hot insertion control, electronic
keying…) with redundant HW management interface (IPMB)
All blades are fully compliant to the ATCA PICMG3.0 specification providing the
following features:
• Power dissipation per blade according to PICMG3.0 <200W
• Mechanical dimensions of 355.6mm(8U) height, 30.48mm width and
approximately 280mm depth
• Faceplate
• Two handles/ejectors to exchange the Blades in the field without any tools
• Lock functionality to take the Blades out of service
• Support of connector
– Zone 1 for redundant power connection, clock, and shelf management
– Zone 2 for data transport interface
– Zone 3 for user defined I/O to RTM (optional)
• Multi-segment discharge strip located on component side 1 along the bottom
edge of the PCB
• Alignment and safety ground pin on both sides of the face plate
• 2 captive retention screws on face plate
The general blade concept of the RNCi is to use:
• General Purpose Processor (GPP) server blades with redundant Gigabit
Ethernet interfaces for all control specific application SW and for signaling
processing.
• Network Processor (NP) blades with redundant Gigabit Ethernet interfaces for
all Tplane and U-plane boards for processing of the user data stream.
• Gigabit Ethernet Switch (GES) blades with redundant Gigabit Ethernet
interfaces for blade connectivity and transport of all types of traffic (user data,
control data and management data).
160 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 112 Basic blade concept
MN3500EU50MN_0001
161
© 2005 Siemens AG
10.5.1 Links and Interfaces

The RNCi provides different interfaces:
• User interface
– Interface to local maintenance terminal and OMC-R/Radio Commander
• Interfaces to other network elements
– Iu
– Iur
– Iub
• External interfaces
– Clock interface
– Debug interface
• Internal interfaces
– Internal transport interface
– Internal clock interfaces
– HW management interfaces
– Inter-Shelf links
162 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 113 RNCi interfaces
MN3500EU50MN_0001
163
© 2005 Siemens AG
10.5.2 HW Management
The RNCi provides an ATCA compliant HW platform management system that
watches over the basic health of the system, reports anomalies and provides
possibilities to take corrective actions when needed (e.g. reset of the board). Thus,
the RNCi HW platform meets the requirements for central office telecom equipment
by providing a maintenance concept, which is capable to monitor, control and assure
proper operation of the shelf, the blades and other devices within the shelf (such as
fans, power entry, …). This includes comprehensive internal alarm handling for rack
and shelves.
ATCA Based HW Management

The RNCi HW management system is based on the interface as defined in
"Intelligent Platform Management Interface Specification" [IPMI_v1.5]. According to
the ATCA standard, basic HW Management functions like resetting and powering up
a blade, monitoring the health of HW components, HW error logging and HW
inventory are available on each blade and work independently from the application
system.
ATCA-compliant HW Management is organized in three distinct levels:

• A “Blade level”
• A “Rack/Shelf level”
• A “System level”
164 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 114 ATCA compliant HW management
MN3500EU50MN_0001
165
© 2005 Siemens AG
10.5.3 Module Description

This chapter provides a functional description of the main modules within the RNCi.
These are:
• Ethernet Switching Module
• General Purpose Processor (GPP) Server Blade
• Network Processor (NP) Blade
10.5.3.1 Ethernet Switching Module

Switched Gigabit Ethernet is used for transport of all types of traffic (user data,
control data and management data) within the system. Therefore, Gigabit Ethernet
switches are located in each shelf of the RNCi. The Ethernet switches are
interconnected with each other using the base interface of ATCA (PICMG 3.0) for
connecting to each slot within the ATCA shelf. The Gigabit Ethernet Switch (GES)
board is connected to a rear transition module providing physical interfaces/ports to
other shelves and boards. As the Ethernet switch module is the central part of each
ATCA shelf, it also carries the central clock generation function.
For reliability reasons the Ethernet switches are redundant and each slot is provided
with redundant Gigabit Ethernet interfaces. Both Ethernet switching planes work
totally independently of each other in active/active configuration. This enables load
sharing over both redundant Ethernet planes (if requested).
The Ethernet switching module contains several functional blocks:
• Gigabit Ethernet Switch (GES): provides connectivity between all blades in the
shelf, and to external shelves, for all types of traffic (control and transport)
• Main Clock Generator (MCG): supports clock synchronization of all units in a
shelf to external reference clock or to derived line clock
• General Purpose Peripheral Processor (PP): controls all functional blocks on
the module (initialization, configuration, maintenance)
• IPMI controller
• Preparation for I/O module for DS1 synchronization located on rear transition
module
166 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 115 Functional blocks of a Gigabit Ethernet switching module
Fig. 116 Gigabit Ethernet switching module and RMT
MN3500EU50MN_0001
167
© 2005 Siemens AG
10.5.3.2 General Purpose Processor (GPP) Server Blade

GPP server blades represent commercially available ATCA based Single Board
Computer (SBC). They are designed and commonly used for server applications
using high performance general-purpose IA32 processors. GPP server blades
provide interfaces for standardized sub-modules, so called mezzanine cards, which
can be used for adding additional support HW or for adding network interfaces. The
next figure shows the functional blocks.
Within the RNCi, GPP server blades are used for T-/U- and mainly C-plane boards
running the RNCi application SW in parallel to the internal communication and
maintenance tasks. For this purpose different versions of the GPP server blade (with
or without hard disk) are provided:
• OMM: GPP blade with HD and mezzanine module for external GE interface
used in OAM-Plane application (Operation and Maintenance Module)
• CCFc: GPP blade without HD used in C-Plane application (Central Control
Function)
• CEBc: GPP blade without HD used in C-Plane application (Cell related Block)
• UEBc: GPP blade without HD used in C-Plane application (UE related Block)
• URMB: GPP blade without HDused in U-Plane application (U-Plane Resource
Management Block)
• TSB: GPP blade without HD used in T-Plane application (Transport Signaling
Block)
• SIGBt: GPP blade without HD used in T-Plane application (Signaling Block T-
Plane)
168 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 117 Functional blocks of the GPP server blade
Fig. 118 GPP server blade
MN3500EU50MN_0001
169
© 2005 Siemens AG
10.5.3.3 Network Processor (NP) Blade

NP blades represent boards with an XSCALE core (32bit RISC compatible ARM
Version 5) integrating 16 “micro engines” on the chip. NP blades use specialized
32bit RISC processors operating in parallel. They are used to realize U-plane and T-
plane functionality. NP blades provide interfaces for standardized sub-modules, so
called mezzanine cards, which can be used for adding additional support HW or for
adding network interfaces.
The NP blade is a modular system consisting of different sub moduls. However, only
a single blade is visible for the operator.
The following components are defined:
• NP Blade: equivalent to an ATCA blade which can be inserted into a slot of an
ATCA shelf.
• NP board (base board): all existing sub-modules must be plugged into this
board type
• NP Sub Module (XP2800): pluggable sub module which will never be
unplugged during lifetime of NP board
• AP Sub Module: pluggable sub module which is needed for all NP boards
• STM1 INTF Sub Module: pluggable sub module which is only needed for the T-
Plane NP board
• GBE INTF Sub Module (Release 2): pluggable sub module which is only
needed for the T-Plane NP board
• U-Plane Sub Module: pluggable sub module which is only needed for the U-
plane NP board
Three (Rel. 2: four) types of NP blades are used the RNCi:

• STM1-INTF: NP blade used in T-Plane application (STM1-line interface board)
is equipped with a sub module providing 4xSTM-1/OC-3 physical layer
processing capability (STM1 INTF Sub Module) and is connected to a Rear
Transition Module (RTM) providing the electrical to optical conversion for optical
IF fiber access.
• GBE-INTF (Release 2): NP blade used in T-Plane application (GbE-line
interface board) is equipped with a sub module providing (GBE-INTF Sub
Module) and is connected to a Rear Transition Module (RTM) providing the
electrical to optical conversion for optical IF fiber access.
• UEBu: NP blade used in U-Plane application (UE related block), equipped with
a sub module to support ciphering function by dedicated HW (U-plane Sub
Module)
• CEBu: NP blade used in U-Plane application (Cell related block) without the U-
plane Sub Module
All NP boards are equipped with an "Adjunct Processor" (AP) as a sub module
providing GPP functionality on the NP Blade.
170 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 119 Overview of the PCB sandwich architecture of the NP blade
MN3500EU50MN_0001
171
© 2005 Siemens AG
Fig. 120 Functional block diagram of the NP blade
172 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 121 NP server blade
MN3500EU50MN_0001
173
© 2005 Siemens AG
10.5.4 Key Features and Customer Benefits

The RNCi allows dramatic OPEX saving thanks to a 75% reduced footprint, reduced
transport costs by support of Gigabit Ethernet and non-real time ATM traffic classes
and IP, minor power dissipation and a simplified operations and maintenance
concept. For seamless integration into existing networks the RNCi will be introduced
in different releases. The RNCi solution also allows a smooth migration to future
network architectures with a high degree of SW and HW reuse and is therefore
prepared for any future RAN evolution including distributed RAN architecture.
10.5.5 Release 1 of RNCi

The first release of the RNCi introduces the powerful successor product of the
cRNC/eRNC (RN-750) offering a comprehensive feature set from the beginning. In
Release 1 the RNCi incorporates the following features:
• HSDPA
• ATM based Iub, Iur and Iu interfaces
• On demand allocation of capacity to voice or data on the same blade
• ATCA® (Advanced Telecommunications Computing Architecture) compliant
hardware
• Powerful 1 rack configurations
• Logical separation of control and user plane
Customer Benefits:
• Increased performance density - 1 RNCi rack replaces 3-4 racks of competitive
products
• Only few basic board types allow for reducing the spare part pool considerably.
• Supports HSDPA.
• Future proof SW defined product, i.e. new features are enabled by a simple SW
upgrade, there is no need to change the HW.
• Reduced footprint and power dissipation.
• Support of asymmetrical configurations (up-, downlink) and CS/PO scalability by
using the same blade for CS and PO services.
174 MN3500EU50MN_0001
© 2005 Siemens AG
10.6 Features and Technical Data

10.6.1 Main Features of RNCi
The RNCi is delivered in a pre-configured rack that allows simple installation and on-
site upgrade by the following:
• 3 shelves each providing slots for 16 blades
• Fully pre-installed power and control cabling
• Pre-installed signal cabling for typical configuration
• Prepared for multi-rack configurations
The RNCi is ATCA compliant and best suited for the Siemens NgTA platform. This
includes the following features:
• Adequate for central office equipment (ETSI, NEBS)
• High availability: “the five nines” >99.999%
• Transport support for ATM and IP (Rel. 2)
• Standardized by PICMG3.0 (PCI industrial computer manufacturer group)
defining ATCA equipment practice with respect to:
– mechanical form factors
– Gigabit Ethernet switching fabric
– regulatory guidelines for safety, EMC and grounding
The RNCi provides outstanding scalability from very small 1-shelf configurations up
to multiple rack configurations with best in class performance.
MN3500EU50MN_0001
175
© 2005 Siemens AG
The RNCi basically uses just 2 processor blade types for simplified logistics and
spare part handling. The functionality of the different blade types is mainly defined by
software.
• The GPP (General Purpose Processor) server blade is based on a Single Board
Computer (SBC) as designed and commonly in use for server applications. The
GPP server blade provides the following features:
– ATCA equipment practice
– Single IA32 CPU
– Dual port GE interface to base interface of ATCA
– Slots for standardized modules
– Hard disk interface for on-board hard disk drive
– V24 and/or USB interface
– IPMI Controller
– On-board power supplies
• The NP (Network Processor) blade is based on a specific processor
architecture, which is designed for mass packet data processing. NP blades are
commonly used in IP router and soft switch products. NP blades offer the
following benefits compared to specialized HW (e.g. ASIC) or GPP blades:
– Higher performance of user plane / transport plane data processing compared to
GPP performance (about factor of 3)
– Flexibility w.r.t. processing of user plane traffic types (UL, DL, realtime CS or NRT
PS) onto single blade
– Flexibility w.r.t. changes in user plane / transport plane functionality (3GPP CR,
new features) by simple SW upgrade
The NP blade provides the following features:

– XSCALE core: 32bit RISC compatible ARM Version 5
– 16 “micro engines” integrated on the chip
– Realization of U-plane and T-plane (STM-1 interfaces) functionality
– “Motherboard” offering connectors for several sub modules, called “mezzanines”
– IPMI Controller
– Dual port GE interface to base interface of ATCA
– V24 and/or USB interface
– On-board power supplies
176 MN3500EU50MN_0001
© 2005 Siemens AG
10.6.2 Electrical and Mechanical Specifications

10.6.2.1 Characteristics RNCi
Physical dimensions
size of a rack
• height 2133mm (7ft)
• width 600mm
• depth 600mm
Weight
rack weight (fully equipped) design goal: <350kg
Environmental
ambient temperature range
• normal operation +5°C ... +40°C (41°F to 104°F)
• transient operation (storage) -25°C ... +55°C (41°F to 131°F)
• transportation -40°C ... +70°C (unventilated)
• humidity +5% ... +85%, no condensation
Power
• input voltage nominal -48V
• input voltage range -40.5V... -57V DC
• max. power dissipation (according to ATCA)
• per rack <10.5kW
• per shelf < 3.5kW
• overcurrent protection circuit breaker
MN3500EU50MN_0001
177
© 2005 Siemens AG
Installation and Operation

• installation of several racks: only side by side
• application indoor/outdoor: only indoor
• ingress protection: at least IP20
• acoustic noise emission: <6.3 B(A) sound power regarding a fully equipped rack
@23°C (ETS 300753 class 3.1)
• cooling method: fans
max. operation height [ASL]

• without any restrictions: 7000ft (2133m)
• with restricted max. ambient temperature: 10000ft (3048m)
• cable access: from the top or via cable duct from the raised floor
• No. of external alarm inputs per rack: 15 + 3 internal alarms
• No. of command outputs per rack: 3 (galv. decoupled; relay output)
178 MN3500EU50MN_0001
© 2005 Siemens AG
RC UMR5.0 Siemens/NEC
RC UMR5.0
Contents
1 RC UTRAN 3
1.1 General description 4
1.2 Network management 6
1.3 Common Handling 8
2 RC Tasks 10
2.1 Configuration management 12
2.2 Fault and test management 14
2.3 Performance management 16
2.4 Log and state management 18
2.5 Software management 20
2.6 Security management 22
2.7 Trace management 24
3 Hardware architecture 26
3.1 Hardware component overview 28
3.2 Additional server equipment 34
3.3 Configuration variants 36
4 Software architecture 38
4.1 Layers, processes and functions 38
5 Exercises 47
6 Solution 51
MN3500EU50MN_0001
1
© 2005 Siemens AG
Siemens/NEC RC UMR5.0
2 MN3500EU50MN_0001
© 2005 Siemens AG
1 RC UTRAN
Fig. 1 Radio commander for UTRAN
MN3500EU50MN_0001
3
© 2005 Siemens AG
1.1 General description

The Radio Commander (RC) is an Operation and Maintenance Center (OMC)
incorporating Element Management functionality for the present and the future Mobile
Radio Networks. Typical tasks of an OMC are e.g. Configuration Management, Fault
and Test Management, Performance Management.
Merging Operation and Maintenance for both 2nd and 3rd generation Mobile Radio
Networks within one common software platform, the Radio Commander introduces
an all-new concept for Mobile Network Element Management.
The Radio Commander supports different Radio technologies as well as the
respective hardware equipment and is prepared for a seamless evolution to 3rd
generation cellular networks. This allows the operator to benefit from reduced training
and operating costs in a highly competitive market.
The Radio Commander is based on the latest object oriented development tools,
methods and technologies as well as on a powerful and reliable hardware and
software platform.
Nearly all the operation and maintenance functionality is accessible via the user-
friendly and customizable Graphical User Interface (GUI), which features a
comprehensive online-help system. Additionally, the Command Line Interface (CLI)
supports single commands and automated command scripting.
This course description deals with the Radio Commander for the 3rd generation
Mobile Radio Network (UTRAN).
Radio Commander UMR5.0 / BR 8.5

The Radio Commander 8.5 (RC 8.5) is a flexible Operation and Maintenance Center
(OMC) incorporating functions for the management of elements in mobile radio
networks. It integrates management tools for elements of both 2nd generation GSM
networks (BR 8.0, 7.0 and 6.2) and 3rd generation UMTS networks (UMR 5.0, 4.0
and 3.5). The radio technologies supported by the Radio Commander include GPRS,
HSCSD and EDGE for GSM networks, UMTS and HSDPA, and access to microwave
transport networks. The common management platform provides a transparent
integration of these technologies, allowing for a seamless evolution from 2nd
generation to 3rd generation cellular networks and thereby reducing training and
operation costs.
The Radio Commander offers functions for equipment management, management of
the transport network (e.g. ATM, PCM24/30) and management of the radio access
network (e.g. cells, channels). These functions are accessible via the configurable
Graphical User Interface (GUI) and the alphanumerical Command Line Interface
(CLI).
4 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 2 Radio commander
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
5
© 2005 Siemens AG
1.2 Network management

The Radio Commander is fully prepared for 3rd generation element management. In
mobile communications, a smooth evolution from 2G GSM to 3G UMTS is desired.
As the number of network elements to be managed steadily increases, networks
diversify, presenting a multi-vendor environment, with decreasing margins for
operators in an even more competitive market.
A key aim of the Radio Commander therefore is the management of UMTS and GSM
as one network relying on the same O&M platform, thus providing a common
management platform for both generations.
This allows the number of network elements managed to be decoupled from
manpower required in operations departments.
Major new characteristics of the Radio Commander architecture for UMTS terrestrial
radio access network (UTRAN) include common O&M management for NodeB and
for RNC functionalities, as well as capabilities to manage the ATM transport network.
In spite of specifics due to inherent technology characteristics, utmost care has been
taken to provide the same functionality for all supported radio network technologies in
a homogeneous representation to the operator.
Common management for GSM and UTRAN equipment consists of the entire range
of management functionalities, such as starting from a similar display and handling of
both GSM-BSS and UTRAN network alarms, and stretching out to a homogeneous
configuration handling, e.g. display and handling of bi-technology network topologies.
Also covered are features such as common logs for all connected network elements
with global search and retrieval, a common state management based on a
comfortable maintenance state approach, as well as common fault and performance
management facilities.
Finally, the Radio Commander also provides the unique entry point for data from both
the GSM-BSS and UTRAN Radio Networks and mediates it to an upper-layer NMC.
The different Radio technologies realized within the GSM and UMTS Network
Elements are connected to the Radio Commander via their respective Q3-interfaces:
• In GSM Network Elements (BSS) the network entities are connected via the Q3-
Interface with regard to the BSS info model.
• In UMTS Network Elements within UTRAN the RNC has a Q3 management
interface. The Qx Interface to NodeB (CORBA-Interface) is splitted with regard
to HW-related and Functionality-related Managed Objects.
6 MN3500EU50MN_0001
© 2005 Siemens AG
Siemens Mobile OSS
Service Management Tools Network Planning Tools
NMC / NOC
Interfaces
Netviewer Radio Switch IP @vantage

Commander Commander Manager Commander
Element
Managers
Message
Coordinator
Microwave
Mobile Data IMS
Mobile Core
Mobile Radio
IP and 3rd party
equipment
Enabling Services
Fig. 3 Siemens network hierarchy
Radio OMC
Commander Control of HW
by tunneling
Q3
(Info Model)
control of
functions
BSC via RNC RNC
BTS GPRS NodeB NodeB

BTS GSM
TDD FDD
Fig. 4 Element management
MN3500EU50MN_0001
7
© 2005 Siemens AG
1.3 Common Handling

The OMC for UTRAN supports the full graphical user interface (GUI). It includes:
• Graphical panel hierarchy containing the managed object instances as icons
• Dynamic update during creation, deletion, alignment
• Dynamic state indication on the icons
• A lot of more lists (e.g. scanner list)
• On each managed object instance a menu can be opened showing all available
commands
• Input and output forms for commands
• Panel navigator
• Network editor
• Common command history for GUI and CLI
• ...
8 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 5 Radio commander network element connections
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
9
© 2005 Siemens AG
2 RC Tasks
The Operation & Maintenance Center (OMC) used in UTRAN is based on the product
used for GSM for the Siemens Base station System (SBS). The OMC is extended to
manage two new network elements NodeB and RNC with different management
interfaces. All features described in the following chapters are common for the
management of both network elements. Exceptions are marked.
The tasks of the Radio Commander can be classified into the following categories:
• Configuration Management
• Fault and Test Management
• Performance Management
• Log and State Management
• Software Management
• Security Management
• Trace Management
10 MN3500EU50MN_0001
© 2005 Siemens AG
Performance
Management
Security
Management
Software
Fault and Test Management
Management
Log and State Configuration

Management Management
RC
UTRAN
Fig. 6 RC Tasks
MN3500EU50MN_0001
11
© 2005 Siemens AG
2.1 Configuration management

The configuration management is related to all changes in the structure of the UMTS-
PLMN and to changes of all parameters relevant for the communication in the radio
cells. Some examples for configuration tasks are
• adding new sites to the UMTS-PLMN (new NodeB)
• adding or removing radio cells to/from a site
• changing codes in the radio cells
Several features in the configuration management are implemented:

• Support all configuration commands modeled in RNC and NodeB information
model
• Upload and Download of RNC and NodeB database
• Support of OMC internal commands
• Execution of all configuration commands via CLI online or using script files
• One common CLI for RNC, NodeB and OMC commands
• Logging of configuration changes is provided. That means, all received Create
Notifications, Delete Notifications and Attribute Values Changes are logged and
can be retrieved by the Operator on graphical lists (see also Log Management).
12 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 7 Configuration management - adding new sites to the UMTS-PLMN
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
13
© 2005 Siemens AG
2.2 Fault and test management

Fault Management includes all the measures required to detect and repair faults in
the mobile communications network. Hardware faults are usually isolated to a
particular module. Operation is normally switched to another redundant module that
takes over the function. The defective unit can be replaced later.
The operator receives information about the standardized probable alarm cause.
Each alarm or state change report is provided with a unique identification and the real
detection time of the failure. Dependent alarm and state change reports show
correlated notification IDs.
In addition, the operator has access to the on-line maintenance documentation,
which provides further information on how to deal with the fault. Fault handling can be
divided into the following main functions:
• Fault detection and recovery
• Alarm logging and reporting
For Fault Management the full feature set is provided in the RC-trial:
• One alarm monitoring list for all connected NEs in a Graphical Layout (see also
figure for Log & State Management)
• Dynamic update (addition of new alarms, removal if the alarm is cleared)
• Active alarms will be aligned. The alignment is started automatically from the
RC: after link interruption, after RC restart, after NE restart. Only the concerned
network elements will be aligned. Alignment can also be triggered by operator
command.
• Acknowledgement and Comments on the alarm by the operator
• List handling like hiding of rows, filters (pre-defined), sorting, etc.. The Filtering
works on following basis: network element, managed object class, managed
object instance, event type, perceived severity, probable cause, trend
indication, specific problems
• Several lists in parallel in one session (e.g. with different filter criteria)
• Alarms will be logged in parallel in an alarm log (for all alarms of all connected
NEs). Retrieval of active alarms on Managed Objects by CLI.
Test Management is closely related to the fault management. The operator is able to
activate remote diagnostic procedures, so-called tests in order to get further
information for maintenance. The full test functionality provided by the NEs is
supported by the Radio Commander. Tests can be started by actions and the test
results on NodeB and on RNC (action response) are displayed on the RC.
14 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 8 Fault management - failure detection
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
15
© 2005 Siemens AG
2.3 Performance management

Performance measurements are essential for the surveillance of a mobile network.
The corresponding information enables the operator to identify failures or quality of
service problem areas within the network, which are not detected by the fault
management, and help to optimize and extend the existing network.
The operator establishes measurements (scanners) with individual parameters. He
can create, schedule, delete, modify, deactivate and display measurements and
administer them interactively.
Measurement results are stored on the NEs as files in standardized ASN.1 BER
(basic encoding rules) binary format and can be uploaded using ftp. For NodeB a
special command is provided embedding the ftp and other necessary operations on
the network entity. The upload can be scheduled by cron.
The measurement files can be stored on the OMC and/or exported to post-
processing tools. By using the Siemens post processing tool SPOTS selected
measurements can be displayed (textual or graphical).
16 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 9 Performance management - usage measurement
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
17
© 2005 Siemens AG
2.4 Log and state management

Log Management: the RC provides a logging of all notifications coming from the
connected NEs or the RC itself. The following logs are supported:
• Alarm reports
• State change reports
• Attribute value change reports
• Configuration change reports (e.g. create/delete notifications)
• others (like software events)
The logs are combined for all incoming notifications from RNC, NodeB and RC. The
log records are stored in a relational database. The operator can retrieve information
from the log-files by CLI. Filtering criteria for retrieval are log instance, time interval
and event-type. The results are written to ASCII files to allow easy further processing
or export. The following features are supported:
• Sorting
• Filtering
• Export to file (ASCII)
State Management:
State management is the basis for an efficient control of the operational condition of
the mobile network. State management in the Radio Network System supports the
standard state and status attributes as defined by ITU-T X.731.
After a computing and a combining process the state and status attributes are
propagated to the superior objects displayed at the RC GUI, thus offering the
operator a detailed overview about the network.
State management provides a powerful function for the operator in order to monitor
and control his network resources according to ITU-T X.731. State and status
attributes are introduced into the managed objects to provide detailed information
about the current condition of network resources, e.g. concerning availability and
operability. Further, it helps the operator to isolate a faulty unit by changing its
administrative state, to run tests for recovery purposes and to perform switches of
redundant boards as well as in many other tasks.
18 MN3500EU50MN_0001
© 2005 Siemens AG
Additional advantages are offered to the operator by the ‘state summarization’, both
in the network elements as well as in the RC. Pre-defined summary panels of the RC
give the operator a quick system overview. User-defined summary panels allow
operators to customize the system overview to their needs. As a result the operator
takes profit by
• enhanced possibility to supervise the network efficiently with a summarized and

easy to understand representation
• essential information is available at a glance, detailed information for each
object in the help view and
• overview of situations where immediate action is required within the network
Fig. 10 E.g. logging of alarm reports
MN3500EU50MN_0001
19
© 2005 Siemens AG
2.5 Software management

From the Radio Commander the complete software of the RNS is administered.
Therefore the RC operator is able to:
• import RNS Software loads and database files coming from software factory
• download the RNS software loads and databases files via ftp to RNC or NodeB.
• For the NodeB a download command (hiding the ftp and triggering some
mechanisms on the NodeB) is provided. The download to NodeB can be
aborted by operator command.
• Database files (system or office data) can be downloaded and uploaded via
special command for NodeB and direct ftp for RNC.
• A manipulation of the mass storage of the network elements (disk on RNC or
flash memory on NodeB) can be also made via ftp.
• Software loads on the NEs can be activated by the operator by using the
modeled actions on the interface.
20 MN3500EU50MN_0001
© 2005 Siemens AG
New RC, RNC, NodeB SW
Fig. 11 SW-management
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
21
© 2005 Siemens AG
2.6 Security management

The Security Management is related to all the functions to prohibit an unauthorized
access to the network. Examples for the Security Management are
• Log-in / log-out of the operator
• Distinction between RC application access and UNIX access
• User administration by the system administrator (modify, delete users)
• Authorization profiles (fixed profiles)
• Password administration (rules, dictionary)
• Password change by the operator
22 MN3500EU50MN_0001
© 2005 Siemens AG
!
Fig. 12 Security management
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
23
© 2005 Siemens AG
2.7 Trace management

Trace management comprises IMSI tracing and RNS Call Alarms.
IMSI Tracing
IMSI Tracing is the collection of data related to one subscriber identified by
International
Mobile Subscriber Identity (IMSI). IMSI Trace is an important feature for operators to
trace:
• subscriber complaints
• problematic network areas with test mobiles etc.
The Radio Commander provides comprehensive functions to manage and monitor
traces.
IMSI data is collected by the network elements currently serving the subscriber. IMSI
data handovers between the mobile switching and mobile radio network elements are
also supported. In the case of handovers the target network elements are informed to
take over the tracing activities.
This includes measurement data for UMTS-UTRAN networks in the RNC:

• Generation of trace records
• Temporary storage of trace records in trace files in the RNC
• Upload of trace files to the Radio Commander
Call Alarms
Statistics based on Call Alarm data is a valuable information for network analysis and
network optimization. Call alarms can contain information about protocol failures,
interface failures, or path and application failures.
24 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 13
Call Alarms
Fig. 14
MN3500EU50MN_0001
25
© 2005 Siemens AG
3 Hardware architecture
The Radio Commander functionality is split into
• the functions of the Operation and Maintenance Processor (OMP), and
• the functions of the Operation and Maintenance Terminals (OMT).
The OMP is the main hardware, where all the tasks for the supervision and control of
a UTRAN are processed. The OMP works as a server and is connected to the OMT
via a Local Area Network (LAN), implemented as an Ethernet. On the other hand, the
OMP is responsible for the connections to the RNS to be controlled.
The OMT are the Workstations with the Command Line Interface, which are used by
the RC staff to enter their commands. Although a bigger number of OMT can be
physically installed in a RC. The maximum number of user sessions at a time
depends on the capacity of the OMP.
The following OMT hardware types can be distinguished:

• the Workstation (WS)
Depending on the hardware used, the Workstations can handle one or two
sessions: one local session and one additional session of an X-Terminal.
• the X-Terminal (XT)
The X-Terminals do not require such a powerful hardware as the Workstations.
However, they cannot run a session alone, but they need a Workstation or a
dedicated X-Terminal-Server to process the user tasks. So the functions of the
X-Terminal are restricted to handle the user input (keyboard and mouse) and to
display the output (monitor).
• a dedicated X-Terminal-Server (OMX)
Unlike the Workstations, which can handle just one additional session, the X-
Terminal-Server can handle many sessions for X-Terminals. One of these
sessions can also run locally, i.e. one session runs at the OMX and all the other
sessions run at the XT.
26 MN3500EU50MN_0001
© 2005 Siemens AG
OMC OMT
OMX 0 OMX 1 OMX k

WS 0 WS 1 WS 2 WS n
......
...
LAN
..........
X-T 0 X-T m
OMX Server
OMC OMP
Fig. 15 General hardware structure of radio commander
Radio Commander
OMT X-T. X-T. OMT X-T.

Server
LAN (Fast Ethernet

Console OMP O&M 10/100 BaseT)
Alarm ToolSet
Disk Array
Printer
ATM-Ethernet
Converter
LMT LMT
LMT LMT RNC LMT
NB-44x NB-53x
BSC RNC
BTS NB44x NB53x
Fig. 16 Radio Commander and Network Elements
MN3500EU50MN_0001
27
© 2005 Siemens AG
3.1 Hardware component overview

The RC runs on UNIX-based systems using commercially available computer
hardware.
The hardware was chosen to have the following characteristics:
• high degree of modularity and flexibility for further extensions in capacity
• provision of a distributable and scalable system
• maximum system reliability
• availability for local maintenance
The RC is designed as a distributed computing system consisting of a set of
components connected via LAN. The architecture is governed by the client/server
principle, which contributes to system flexibility and robustness. The server machine
is the Operation and Maintenance Processor (OMP), whilst the clients are Operation
and Maintenance Terminals (OMTs), typically graphical workstations or X Terminals.
The current server configurations for the RC include Sun Fire E4900 used as the
OMP, Sun Blade 150 used as OMTs and Sun Fire V440 used as OMT servers or
O&M ToolSet servers.
The RC 8.5 still supports previous hardware configurations based on the Sun
Enterprise series, Sun Ultra series and Sun Blade series. Continuous support is also
provided for all the standard hardware presently in field use, as far back as UMTS
release UMR2.0, with recommended upgrading strategies. All details concerning the
delivered hardware components are listed in the “Technical Stock list” that is supplied
to customers with each new software load patch.
All subsequent chapters are describing the minimum hardware requirements for
Servers and Clients. The following picture provides at first an overview about typically
used hardware in RC environments.
28 MN3500EU50MN_0001
© 2005 Siemens AG
OMP OMT
E450x/E400x Sun Fire

F4800 E4900
Ultra 10, SB 100 Sun Blade 150

Sun Fire
E420R V480/V440
OMT Server O&M ToolSet
Sun Blade 1000

Sun Blade 2000 Sun Fire V480/V440
Sun Blade 2000 Sun Fire V480/V440
Sun Ultra 60
Fig. 17 Hardware overview
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
29
© 2005 Siemens AG
The OMTs are connected to the OMP in a LAN (Local Area Network) configuration.
Remote login in pure alphanumeric mode (e.g. via modem) is possible.
The OMP supports communication links to the

• local OMT via LAN through the Fast Ethernet 10/100BaseT (Switch/Hub)
• RNC via WAN / LAN
• NodeB: The connection between RC and NodeB is based on the same logical
connection, but on different physical layers. The direct management of HW-
related objects by the Radio Commander (tunneling) therefore needs a data
conversion (C) between TCP/IP and ATM.
30 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 18 LAN configuration for UTRAN / GERAN
Radio Commander
Ethernet
WAN/LAN
C
ATM ATM
Ethernet
NodeB
RNC ATM
NodeB
Fig. 19 System configuration trial system with O&M links
MN3500EU50MN_0001
31
© 2005 Siemens AG
In a more detailed view the RC-HW-configuration additionally comprises equipment

like
• an OMP-console (Digital VT520-AX) or SUN Standard Color Monitor
• a Tape Unit for OMT and OMP (DAT 72 – 36GB)
• a Spoolprinter black & white (e.g. HP LaserJet 2100M/2200M/2300)
• the IP / ATM Converter ,or Router
The converter and the router are configured by a specific Configuration and
Management Tool. The operator can access the tool via TCP/IP or from a PC
via serial interface.
32 MN3500EU50MN_0001
© 2005 Siemens AG
Laser Printer
DAT 72 Tape Unit
OMT OMT SunBlade150

SunBlade150
Fast Ethernet 10/100BaseT
DAT 72 Tape Unit
Console
SunFire V440
NE
Fig. 20 Configuration OMT-OMP possible for RC UMR5.0
OMTs = ATM-connection
= Ethernet-connection
LAN-Switch/Hub 10/100BaseT
N -card
via LA
C = ATM/Ethernet Converter
RNC1
OMP
SF4900 LMT RNC
NodeB1 NodeBx
LMT NodeB
Fig. 21 Configuration OMP-RNC with LMTs for RC UMR5.0
MN3500EU50MN_0001
33
© 2005 Siemens AG
3.2 Additional server equipment

To increase the reliability, internal redundancy of the OMP-modules is supported.
Since all the modules are hot pluggable, replacement of faulty modules can be
performed without service interruption.
All servers can be delivered additionally with e.g.

• a console which is a video terminal, connected to the OMP via a serial interface.
The installation of the OMP software as well as the control of the OMP can be
performed by this terminal, or from the OMP with an additional graphic card,
working also in the role of an OMT
• a Terminal Server to access the RS232 OMP Connector via LAN/WAN
• an external Tape DAT72, Capacity and Performance : Sustained transfer rate:
3MByte/sec. (MBps) (10.8GB/h) native, 6MBps (21.6GB/h) with hardware data
compression (2:1) Max. native capacity : 36 GB native, 72 GB with hardware
data compression on a DAT 72 data cartridge
• Sun StorEdge 3310 SCSI Array, up to 12 disks, each with up to 300GB
• Dot Matrix Printer Epson LQ-2180
• Print Server HP JetDirect 500x to enable the usage of LAN-Printers as Spool,
and/or Alarm printers
• L8 Jukebox - External Tapes for Backup and Restore. 1.6 TB capacity and 30
MB/sec. throughput, Eight-slot autoloader
34 MN3500EU50MN_0001
© 2005 Siemens AG
SE3310 Disk Array L8 Autoloader

DAT72 Tape Drive
Epson LQ-2180 HP JetDirect 500x Terminal Server

MicroAnnexXL
Fig. 22 Additional server equipment examples
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
35
© 2005 Siemens AG
3.3 Configuration variants

For the OMP, the Radio Commander uses the Sun server line. The product line
ranges from low-budget Workgroup Servers V440 for small systems up to high-end
Sun Fire 4900 Servers for large systems.
36 MN3500EU50MN_0001
© 2005 Siemens AG
Spoolprinter(b&w)
...
OMT-Server
Tape
Unit X-Terminal X-Terminal
X-Terminal
LAN
OMP
Console
DiskArray
Disk Array SE3310

Character
Printer
RNC
Fig. 23 OMX - server
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
37
© 2005 Siemens AG
4 Software architecture
4.1 Layers, processes and functions
The software architecture of the Radio Commander is governed by the client-server
principle and strictly follows the object-oriented approach. It complies with common
application software standards such as Q3, GDMO/ASN.1, SNMP, CORBA and
standard C++. The whole system is modular and distributed, which increases its
flexibility, scalability and robustness.
The RC-Software consists of various logical layers, which are built one on top of the
other:
• The operating system used on both platforms, OMT and OMP, is version 8 of
SUN SOLARIS. It is based on the standard UNIX System V Release 5.0
(SVR5.0) and offers multi-user / multitasking capability, a high portability level
and a very high communication capacity between all processes.
• The Solstice Enterprise Manager is the state-of-the-art, standard-compliant,
commercial TMN platform for the Radio Commander and stands for improved
functionality, flexibility and scalability. It maintains consistent information relying
on
a) GDMO/ASN.1 model for the description of interfaces to BSS / RNS and NMC
b) Management Information Tree (MIT)
c) GUI data
d) Integrated logging manager
The Management Information Server (MIS) is the “heart” of the TMN platform.
Other important features are the Management Protocol Adapters (MPA), which
support different protocols (CMIP, SNMP, RPC), and the Portable Management
Interface (PMI), which ensures location and protocol transparency for the
applications.
• CORBA, the Common Object Request Broker Architecture, uses an object-
oriented approach for creating software objects that can be reused and shared
between applications. Each object encapsulates the details of its inner workings
and presents a well-defined interface, which reduces application complexity.
CORBA is an international standard defined by the Object Management Group
(OMG). With its simple and future-safe Interface Description Language (IDL) it
provides operating system and programming language independent interfaces
to all the services and objects available on a network. CORBA thus reduces
client-server inter-dependence, laying the basis for improved scalability.
• DBMS: The Radio Commander relies on a reliable state-of-the-art commercial
Relational Data-base Management System (RDBMS) from ORACLE. In addition
to the storing of the RNS database copy it contains the OMC-Database as well
as a database for measurement data, alarm log tables, active alarms and user
administration data.
38 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 24 RC software layers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
39
© 2005 Siemens AG
• Application Base Services: these services, which form the first sublayer of the
special Radio Commander applications, provide universally required functions
accessible by all applications, such as Logging, file handling or safeguarding.
This layer shows clearly how the Radio Commander software itself is modular
and distributed, making for more flexibility and robustness.
• The System Management Function (SMF) make up the Radio Commander’s

typical operation and maintenance functionality, covering various specific
functions such as Fault and State Management, Configuration, Performance
and Security Management. The uniformity of the SMF modularity on every
system level is one of the main design principles, ensuring reliability and
flexibility.
In later versions, the Radio Commander offers a standard Q3 Interface to the
superior Network Management Center (NMC). Thus, System Management
tasks issued at NMC level are mediated by the Radio Commander to be applied
to the Siemens Network Elements.
• The highly configurable and user-friendly Man-Machine Interface of the new
Radio Commander features a Graphical User Interface (GUI), a Command Line
Interface (CLI) and an Online Help System: Graphical applications of the Radio
Commander are based on the X-Window system and OSF-Motif. The OMT
application runs on the Common Desktop Environment (CDE).
40 MN3500EU50MN_0001
© 2005 Siemens AG
Fig. 25 SMFs: Logical function split according to the TMN model
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
41
© 2005 Siemens AG
Due to the distributed SW-Architecture there is no one big process for the operated
Network but every NE has its agent as a separate process within the OMP.
Additionally the Radio Commander runs a process for its own operation and
maintenance tasks. Other processes are reserved for new agents of 3rd party-SW-
providers.
42 MN3500EU50MN_0001
© 2005 Siemens AG
Radio Commander
OMT
MMI
OMP
BUS
new
CORBA GSM ... GSM OMC agent
NodeB1 ... NodeBn RNC1 ... RNCn e.g.
Processes BSS1 BSSn local
3rd party
Data Solstice Enterprise Manager

Base TMN Platform
Fig. 26 Radio commander distributed SW-structure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
43
© 2005 Siemens AG
For to avoid internal blocking situations the Radio Commander separates the event
path from the command and response path. In consequence two types of processes
exist within the OMP: object processes per NE for events and SLS-processes for
commands / responses per management function (such as Fault Management,
Configuration Management, etc.).
• An event, which happened in a RNS, is received by the related object process
from the EFD for a specific NE. Via the internal Event Dispatcher the message
is handed over to the SMF, which fits to the event. At least the event message
is sent to an actual session at the OMT for to show the event to the operator
e.g. an alarm in the alarm list at the GUI.
• A command input by the user first is checked e.g. on syntax in the Service
Request Executor (SRE) at the OMT. Next the SRE sends the command to the
Second Level Server (SLS, what is a SW-process) at the OMP, which fits to the
management function related to the command. At least the command is sent to
the NE via MIS.
• After receiving the response MIS hands it over to the same SLS, which
processed the command. The command execution ends with the transfer of the
response from the SLS to the operator at the OMT.
• An exception happens if a received event leads to an automatic command
execution e.g. after a connection interruption of a RNS the first event there from
initiates automatically an alignment procedure.
In the event path the Event Forwarding Discriminators (EFD) realize a user
definable information flow on the O-link to RNS. Easy adaptation for special
purposes, e.g. Blocking of notifications for particular events is possible:
• EFDs allow the operator to select for each RNS which notifications and alarms
are propagated to the OMC
• Discrimination of event reports on the O-interface is provided for all event
reports generated by the RNS. Event reports are e.g. alarm reports,
performance measurement reports, state change event reports, attribute value
change event report.
44 MN3500EU50MN_0001
© 2005 Siemens AG
Command
e.g. CLI
Path
MMI OMT Event Path
event Service Request acting as 1st Level

Executor (SRE) Server in the client
command OMP
Object Process response
MMI Session Distributor

Second Level Servers
SMF
SMF
SMF
SMF
SMF
SLS SLS SLS SLS

auto Serving a dedi -
command cated SMF
Event Dispatcher
response
event
Topo
EFD MIS DB Tree
Fig. 27 Separating event path from command / response path
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MN3500EU50MN_0001
45
© 2005 Siemens AG
46 MN3500EU50MN_0001
© 2005 Siemens AG
5 Exercises
MN3500EU50MN_0001
47
© 2005 Siemens AG
48 MN3500EU50MN_0001
© 2005 Siemens AG
Exercise
Title: RC Introduction
Objectives: The students are in able to name and fill out basic Radio
Commander knowledge
Pre-requisite: none
Task
Please answer the following questions:
1) What is a Radio Commander ?
2) Which mobile network technologies can be handled with the Radio Commander ?
a)
3) Which network elements can be handled in particular from the Radio Commander
?
a)
b)
c)
d)
e)
4) Please name an example for every of the following RC tasks:

CM
FM
TRM
Security Management
Log- and State Management
MN3500EU50MN_0001
49
© 2005 Siemens AG
5) Please fill out the empty blocks, corresponding with the correct names:
X-Terminal server
OMT
Alarm printer
NODEB
CISCO
LMT-RNC
LMT NodeB
Radio Commander
X-T. X-T. X-T.
LAN (Fast Ethernet

OMP O&M 10/100 BaseT)
ToolSet
LMT
LMT LMT
Fig. 28 RC Environment
50 MN3500EU50MN_0001
© 2005 Siemens AG
6 Solution
MN3500EU50MN_0001
51
© 2005 Siemens AG
52 MN3500EU50MN_0001
© 2005 Siemens AG
Solution
Title: RC Introduction
Objectives: The students are in able to name and fill out basic Radio
Commander knowledge
Pre-requisite: none
Task
Please answer the following questions
1) What is a Radio Commander?

It is an Operation and Maintenance Center for the GSM and/or UMTS Radio
Network
2) Which mobile network technologies can be handled with the Radio Commander?
a) GSM
b) UMTS
3) Which network elements can be handled in particular from the Radio Commander?
a) BSC
b) TRAU
c) BTS
d) RNC
e) NodeB
4) Please name an example for every of the following RC tasks:

; CM: Adding a new Cell
; FM: Working on an equipment alarm
; TRM: Starting of an IMSI Trace
; Security Management: Creation of a new User
; Log- and State Management: Checking the state change of a TRX from enabled
to disabled
MN3500EU50MN_0001
53
© 2005 Siemens AG
5) Please fill out the empty blocks, corresponding with the correct names:
X-Terminal server
OMT
Alarm printer
NODEB
CISCO
LMT-RNC
LMT NodeB
Radio Commander
OMT X-T. X-T. OMT X-T.

Server
LAN (Fast Ethernet

Console OMP O&M 10/100 BaseT)
Alarm ToolSet
Disk Array
Printer
Cisco Router
LMT
LMT RNC LMT
NB-44x NB-53x
RNC
NB44x NB53x
Fig. 29 RC Environment
54 MN3500EU50MN_0001
© 2005 Siemens AG

Utran Overview

Uploaded by

Copyright:

Available Formats

Utran Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Utran Overview

Uploaded by

Copyright:

Available Formats

UTRAN overview Siemens/NEC

13.3 Multi User Detection (MUD) 72

1 GSM evolution to UMTS

HSCSD: High Speed Circuit Switched Data

GPRS: General Packet Radio Services

EDGE: Enhanced Data Rate for the GSM Evolution

UTRA(N): UMTS Terrestrial Radio Access (Network)

GSM - UMTS Evolution:

• UMTS: UTRA (WCDMA) New

Fig. 1 From GSM to UMTS

Fig. 2 IMT 2000

3 GSM & UMTS Releases

UMTS Release `99 (also: Release 3)

Fig. 3 Releases of GSM and UMTS

4 Harmonization of the RTTs

IMT-2000 Source: ITU

CDMAFDD TDMA/CDMA TDMA

TD-SCDMA Phase 2 - UTRA TDD LCR (UMTS Phase 1)

UMTS-specific extensions / modifications

Fig. 5 Network with TD-SCDMA

TSM same air interface TDD LCR

GSM2+ & CN 3G Core

China Wireless Telecommunication Standardization

Fig. 6 TD-SCDMA evolution

1900 1920 1980 2010 2025 2110 2170 2200

unpaird for MSS paired

Fig. 7 Frequency Spectrum

7 The CDMA principle

De-spread Spread signals Radio transmission = after

7.1 CDMA types

7.1.1 Time hopping CDMA (TH-CDMA)

7.1.2 Frequency hopping CDMA (FH-CDMA)

7.1.3 Direct sequence CDMA (DS-CDMA)

Fig. 9 CDMA Types

7.2 Advantages of CDMA

CDMA • Stability → Narrowband noise

Frequency planning / resource planning

2/7 4/7 1/1 1/1

7/7 5/7 1/1 1/1

Fig. 10 CDMA network

FDD TDD TDMA CDMA

Fig. 11 Duplex and Multiplex methods

8.1 Duplex transmission: FDD & TDD

Fig. 12 FDD and TDD

8.2 Multiplex methods

Frequency Division Multiple Access (FDMA)

Time Division Multiple Access (TDMA)

Code Division Multiple Access (CDMA)

Multiple BS & MSwith common

Fig. 13 Multiplex methods

9 UMTS-two different modes

UTRA TDD / FDD – common features

UTRA TDD / FDD – differences

Fig. 14 FDD mode

Fig. 15 TDD mode

9.1 Variation in data rate

9.2 Asymmetric allocation of frequency resources

Fig. 16 FDD data rate

Fig. 17 TDD data rates

9.3 FDD uplink and downlink data rates