Module 8 - NSN Product Solution For GSM

NSN Product Solution for GSM
NSN Product Solution for

GSM
Contents
1 Objectives...................................................................................................2
2 Nokia Siemens Networks- Implementation of GSM .............................. 3
3 BASE STATION SUBSYSTEM (BSS) ....................................................... 4
3.1 NSN BTS.....................................................................................................4
zoxojaka.und.slo
3.2 NSN Base Station Controller (BSC) Products.......................................... 18

3.3 NSN Transcoder Products........................................................................ 29
4 Network Switching Subsystem (NSS)................................................... 34
4.1 DX 200 MSC/VLR Architecture.................................................................34
4.2 DX 200 HLR/AC/EIR.................................................................................38
5 NSN Release 4 Mobile Switching Centre Server (MSS) ...................... 39
5.1 NSN Media Gateway (MGW)....................................................................43
5.2 D900/D1800NSS - Switching Subsystem................................................. 45
5.3 Data Service Unit DSU ..............................................................................57
5.4 Switching Network SNB ............................................................................ 58
5.5 Signaling System Network Control SSNC ................................................ 63
5.6 Coordination Area ..................................................................................... 67
5.7 Summary D900/D1800NSS...................................................................... 71
6 PACKET SWITCHED CORE NETWORK................................................ 73
6.1 Serving GPRS Support Node (SGSN) ......................................................73
6.2 Gateway GPRS Support Node (GGSN) ................................................... 77
6.3 Operation System Support ........................................................................78
7 Other Products ........................................................................................81
7.1 Location based functions...........................................................................81
7.2 Operation & Maintenance O&M ................................................................ 83
Nokia Siemens Networks 2008 1-1

1 Objectives
After completing this learning element, the student should be able to:
List Product Solution in Base Station Subsystem.
List Product Solution in Circuit Switching Core Network.
List Product Solution in Packet Switching Core Network.
List Product Solution in Operation Support System.
zoxojaka.und.slo
1-2 Nokia Siemens Networks 2008

2 Nokia Siemens Networks-

Implementation of GSM
In the previous sections we have discussed all subsystems and network elements
thoroughly. The picture below shows an overall picture of the GSM network. The
GSM System has been divided into three sub-systems, Base Station Subsystem
(BSS), Network Switching Subsystem (NSS) and Network Management
Subsystem (NMS). All the three subsystems are composed of various network
elements. In this module we shall have a look at the products for various network
elements in these subsystems available from Nokia Siemens Networks.
zoxojaka.und.slo
Fig. 1 GSM network architecture NSN implementation

3 BASE STATION
SUBSYSTEM (BSS)
BSS or Radio access interface is responsible for connecting the wireless mobile
phone to the GSM network. The BSS consists of Base Transceiver Station (BTS),
Base Station Controller (BSC) and Transcoder. There are several NSN products
to serve these NEs.
3.1 NSN BTS

The Base Transceiver Station, BTS, is a part of the Base Station Subsystem,
BSS. The BTS provides radio part for the BSS and is located between the BSC
and the Mobile Stations, MS. The NSN BTS comes in different models and
capacities and the operator can choose the best suited BTS for his network. The
BTS handles signaling as well as traffic in the air interface. It also detects the MS.
Frequency hopping is another function, which is implemented for reducing the
effects of interference. Hopping can be cyclic or pseudo-random as defined in the
GSM specifications. The BSC provides the frequency hopping parameters for the
BTS that operates according to the parameters. Frequency hopping is optional.
The BTS is also responsible for power control in down link direction. LAPD
zoxojaka.und.slo
signaling is used between the BSC and the BTS and LAPDm between the MS
and the BTS.
NSN BTS families

The base stations manufactured by NSN have gone through multiple generations.
Each generation of BTS have come up with new features. The following sections
give a brief overview of different generations of BTSs.
NSN DE21/DF12 BTS

The so-called second generation BTSs came in a wide range of versions. They
had flexible cell extension solutions and an optimised transmission solution. The
features also included remote configuration management, remote fault
management, downloadable SW from the OMC, local MMI for monitoring and
control and non-volatile flash memory for SW storage. The figure below shows
some versions of the second generation BTS.

Fig. 2 NSN 2nd generation BTS (DE21/DF12)
NSN Talk Family BTSs (DE/DF34)

The NSN Talk Family of BTSs has more versions than the second generation
ones. NSN City Talk and Intratalk both have similar features and can be a one
or two cabinet version. With the two-cabinet version, it can have a maximum
sectorised capacity of 4+4+4. When used in omnidirectional mode, up to six
TRXs can be used. With a height of 136 cm, the City Talk is also quite compact.
The Intratalk is slightly bigger with a height of 160 cm.
The Flexitalk is small and compact, and finds most use while being wall mounted
indoors and in shopping malls. It is also quite useful at special sites such as
underground. Its capacity is 1 or 2 TRXs in omnidirectional configuration. With all
zoxojaka.und.slo
its dimensions around 50 cm, it can fit virtually anywhere. The Flexitalk+ is
similar to Flexitalk in capacities and configurations, but is slightly bigger at 1m
height. It is also suitable for rooftop mountings. Figure 3 shows the NSN Talk
Family of BTSs.
Fig. 3 NSN Talk Family of BTSs

3.1.1 NSN MetroSite

The NSN MetroSite is a base station and transmission equipment combined
solution. It is designed for micro-cellular applications.
Fig. 4 NSN MetroSite
A MetroSite base station is small (49 litres) and lightweighted (22 kg with one
zoxojaka.und.slo
TRX and 35 kg with four TRXs installed) with modular mechanics. It supports the
GSM 900, 1800 and 1900 frequency bands. It accommodates up to four TRXs,
and a dual-band configuration with GSM 900 and 1800 frequencies is possible.
The MetroSite can be used for both indoor and outdoor purposes.
It is possible to chain up to three MetroSite cabinets in the same physical site,

which makes it possible to increase the site capacity to 12 TRXs.
Simplicity of installation and integration brings shorter integration times. Having
the possibility of different build-in transmission units, different transmission
solutions can be implemented.

3.1.2 NSN UltraSite

In September 1999, NSN presented the UltraSite base station. It enables a
smooth transition into the 3rd Generation mobile network, as it supports not only
GSM, HSCSD and GPRS, but also EDGE and WCDMA with the addition of
plug-in modules and WCDMA carriers.
zoxojaka.und.slo
Fig. 5 NSN UltraSite

NSN UltraSite BTS Indoor and Outdoor for GSM are offered as 1 - 12 TRX
cabinets, or they can be configured to hold up to 6 TRXs and an optional
Integrated Battery Back-up Unit (IBBU). Up to 40 Ah capacity can be provided,
which means 45 minutes back-up time for those 6 TRXs. Additionally, NSN
UltraSite BTS Midi Indoor/Outdoor, a 1 - 6 TRX BTS for indoor installations, is
available. The BTS can be used in GSM 800, 900, 1800 or 1900 systems or as a
GSM 800/1900 or GSM 900/1800 dual-band BTS.
The NSN UltraSite BTS can support GSM EDGE TRX with minimum hardware
changes. Only the BTS Software, Transceiver Unit, and Transceiver Basestation
Unit have to be upgraded; other units remain the same. GSM and EDGE TRX
can co-exist in the same cabinet with EDGE TRXs occupying the lower half of the
UltraSite cabinet. With the addition of EDGE/EGPRS, the BTS offers a maximum
data rate of over 400 kbit/s with multiple timeslots, as compared to over 100
kbit/s with multiple timeslots for GSM/GPRS.
zoxojaka.und.slo
Fig. 6 NSN UltraSite versions

WCDMA carriers for the 3G system UMTS as well can be added into NSN
UltraSite BTSs. They can operate simultaneously with the basic GSM and EDGE
TRXs. The use of WCDMA equipment reduces the maximum number of basic
GSM and EDGE TRXs to six in one cabinet. The WCDMA configuration can be
either three WCDMA carriers each with output power of 5W or 6 WCDMA carriers
each providing 2 W output power.
Fig. 7 NSN UltraSite flexibility

zoxojaka.und.slo
This makes the NSN UltraSite BTS an efficient solution for building capacity in
mobile networks in the areas of heavy telecommunication traffic. With the BTSs
high output power and receiver sensitivity, large coverage can be achieved in
rural areas when building the network. The output power can be further increased
with an optional booster.
Chaining the NSN UltraSite BTSs can increase capacity. In most configurations,
only the synchronisation cabling is required between the cabinets. Up to 9 NSN
UltraSite BTSs can be chained together. With RF hopping, sectors split between
different cabinets can use common hopping frequencies. BaseBand frequency
hopping is not possible between the chained cabinets (that is, they must have
separate hopping groups). However, BaseBand hopping with TRXs in a
single-cabinet sector is supported.

3.1.3 NSN FlexiEDGE BTS

NSN FlexiEDGE BTS is considered to be a revolutionary BTS with weather-proof
modules. Installation can be done in stacks, on walls, poles, in 19racks or
cabinets. So it gives complete flexibility to the operator to mount the BTS
hardware at his convenience. Same modules are used in FlexiEDGE BTS for
indoors and outdoors, macro- and microcellular sites. Temperature range for
FlexiEDGE can be from -33C to +50 C (temporarily +55 C), so that it can suit
all kinds of climates on different parts of the world.
Site capacity has virtually no limits. One BCF can have 1 to 24 TRX in 1-6
sectors. So FlexiEDGE can support up to 216 TRX per site.
TRX output power is 47 dBm, with sensitivity approximately 115.5 dBm (with
2-way UL div). The best part about FlexiEDGE BTS is that it can support dual
TRX. Dual TRX module (DTRX) is optimal for both capacity and coverage modes.
In Capacity mode (CaM) both TRXs of DTRX are used for traffic. In Double
Power TRX (DPTRX) mode the TRX output power is 49.5 dBm. In Coverage
mode (CoM) 30-50% fewer sites will be required by boosting both down- and
uplink power i.e., DPTRX+IDD+4-way diversity: 53 dBm (200W).
zoxojaka.und.slo
Fig. 8 Flexi EDGE BTS

BTSE-One Family & BTS-Plus Family

NSN offers a large variety of BTSE variants for flexible and cost-efficient network
configuration. The BS11, BS20/21/22 (BS2x) and BS60/61 (BS6x) are the
classical BTSE variants, the BS240/241/242 (BS24x), BS82 and BS40/41 (BS4x)
are new variants. All BTSE are compatible on Abis-level.
The BS11 (Micro-BTS) is used for outdoor applications, e.g. for micro-cells (out of
production).
The BS2x and BS6x encompass all standard types with a maximum capacity of
up to 2 or 6 TRXs for both indoor or outdoor applications. The internal
architecture is very similar.
The BS2x family with up to 2 TRX per rack can be supplied in 3 versions:
BS20 for indoor installation
BS21 for outdoor installation
BS22 for indoor & outdoor applications in confined spaces
The BS6x family with up to 6 TRX per rack can be supplied in 2 versions:
The new BS24x offers highest modularity and flexibility, low volume per carrier,
minimized power consumption and costs. The BS24x platform is the basis for the
zoxojaka.und.slo
migration strategy to UMTS (GSM, GPRS, EDGE). The modular HW/SW concept
and mechanical handling is identical. The BS4x family and the BS82 (eMicro) are
derived from the BS24x platform.
The BS24x family with up to 24 TRX is available in the following versions:
BS242 (Pico-BTS) for indoor installation consists of a split BTS architecture
with a core part called Server and up to 24 remote TRXs called Agents.
The BS4x family with up to 4 TRX is available in the following versions:
The BS82 (eMicro) with up to 8 TRX (indoor & outdoor installation) addresses all
kinds of micro cellular applications.

zoxojaka.und.slo
Fig. 9 BTSE Family
3.1.4 BS240: Units & Modules

The new BS24x and BS4x family are based on the same HW platform (same
modules). The fully equipped BS240/241 consists of one Base Rack, 2 Extension
Racks and 2 Service Racks; it is expandable up to 24 TRX (each Base /
Extension Rack with up to 8 TRX). Base & Extension Racks are equipped in the
same way with:
Antenna Combiner (ACOM)
Multi Coppler (MUCO)
Carrier Unit (CU)
Alarm Collector Terminal (ACT)
The Base Rack additionally contains the Core modules:
Core Basis COBA2P8
Core Satellite COSA6P16
The Service Racks contain the AC/DC modules, battery backup and the Line
Equipment LE.

Core Modules: COBA & COSA

COBA & COSA modules are responsible for local control of the BTSE, generation
of system clocks, providing of up to 8 Abis-interfaces (PCM30/24) to BSC or
other BTSEs, routing of the Abis data to up to 24 CUs, providing an interface to
the LMT and handling and processing of O&M messages. For redundancy, the
core modules can be duplicated.
Core Basis COBA2P8

COBA is the central board of the core. The functionality of the advanced clock
generation ACLK and the Base Core Controller BCC of the entire BTSE are
integrated. 2 PCM30/24 Abis interfaces and 8 interfaces to CUs are available on
COBA2P8.
The BCC maintains the SW of all BTSE units in Flash-EPROM, supervises the
SW download and terminates all internal system alarms. Besides the O&M
functions, the BCC handles signaling messages between BSC (Abis) and CUs
(CU-link).
zoxojaka.und.slo
Fig. 10 BS 250: Units and modules

Core Satellite COSA6P16

For interface and feature extension, COBA can be expanded with one COSA.
The COSA6P16 module offers 6 PCM30/24 interfaces for Abis and 16 interfaces
to CUs. The COSA is controlled from the COBA.
Antenna Combiner (ACOM) / Multi Coppler (MUCO)

For the UL & DL transmission of data the Duplexer Amplifier MultiCoupler
DUAMCO can be used. Furthermore, for DL transmission the Filter Combiner
FICOM (DL only) can be used. In this case, for the UL reception the DI Amplifier
Multi Coupler DIAMCO (UL only) can be used.
Duplexer Amplifier Multi Coupler (DUAMCO)

DUAMCO can be used in UL & DL direction. It combines up to 4 TRX to one
antenna. It contains filters in order to combine the transmit path TX and the
receiving path RX to one antenna connector. The RX path consists of a low noise
amplifier (LNA) and a power splitter. The TX path consists of isolators, a hybrid
coupler and an antenna supervision unit (ASU). DUAMCO has 2 different
operation modes: the AMCO mode where no Tower Mounted Amplifier (TMA) is
used, and the (MUCO) mode in case a TMA is used.
zoxojaka.und.slo
Filter Combiner (FICOM)
FICOM can be used in DL direction only. It combines up to 8 TRX of one rack to
one antenna using remote tunable narrowband filters. For the UL direction (RX)
the DIAMCO has to be used to filter and distribute the received signals to the
CUs.
DI(=2) Amplifier MultiCoupler (DIAMCO)

DIAMCO can be used in UL direction only. It contains receive filters, low noise
amplifiers (LNAs) and power splitters. Thus it filters the received signals and
distributes them to the CUs. For DL direction, FICOM has to be used.

zoxojaka.und.slo
Fig. 11 BS 240 Modules
Alarm Collector Terminal (ACT)

ACT contains the interface to the external alarms (Operator / rack / shelter
alarms) and collects internal alarms (door, fans, different operator-defined
rack/shelter internal alarms).
The alarms are delivered to the Core.
Tower Mounted Amplifier (TMA)

TMA connects the antenna with the BTSE in order to amplify the receive signal
and pass through the transmit signal.
Carrier Unit (CU)

CU takes care for all carrier oriented tasks of the BS240, i.e. the conversion of
data between Abis and Um interface. In UL direction, two RF signals (antenna
diversity) are received and finally converted into TRAU frames (16 kbit/s) and
signaling data. In DL direction, TRAU frames and signaling data are received and
converted into a GMSK modulated RF signal, which is amplified to the desired
power level. Up to 8 CU can be placed into one Base / Extension Rack, i.e. up to
8 TRX are supported by one rack.

The CU consists of the subunits: Power Amplifier & Transceiver Unit (PATRX),
Signal Processing Units (SIPRO) and Power Supply Unit (PSU).
PATRX provides the main analogue functions of the CU. In UL direction it
receives the 2 (diversity) RF signals from the antenna combining equipment,
downconverts them and transmits them to SIPRO. In DL direction, it receives the
GMSK modulated signal from SIPRO. The signal is then I/Q modulated,
upconverted, leveled, power amplified and transmitted to the antenna combining
equipment. PATRX supports synthesizer frequency hopping and provides an RF
loop between DL and UL path for the unit test of the CU.
SIPRO contains all digital functions of the CU: UL & DL Signal Processing,
(Encoding, Interleaving, Ciphering, Burst building), Control of RF on PATRX,
Baseband & Synthesizer hopping, Channel Control, Radio Link Control, O&M
parts relevant for CU, Link to Core via CC link. Additionally, some analogue
functions are located on SIPRO: A/D & D/A conversion, Local CU clock.
zoxojaka.und.slo

zoxojaka.und.slo
Fig. 12 Carrier Unit (CU)

3.2 NSN Base Station Controller (BSC)

Products
3.2.1 NSN DX 200 BSC
The NSN DX 200 Base Station Controller (BSC) is also based on the switching
platform DX200, which is also used for MSC and HLR. The group switch used in
the BSC, the GSWB, is capable of switching 1 bit from inside a PCM channel and
switch to any other position in any other channel in any other PCM cable. This
makes it very convenient to switch transcoded speech, which is at the rate of 13
Kbits/s. This also enables switching for half rate speech. GSWB is connected to
both internal and external PCMs. The external PCMs provide connectivity to
various interfaces of the BSC like A-ter, A-bis and Gb. The internal PCMs are
used to connect the computer units BCSU and OMU with GSWB.
zoxojaka.und.slo
Fig. 13 DX 200 BSC (second generation) architecture

3.2.2 Functional units in the DX 200 BSC

The DX 200 BSC consists of a number of functional units, each with its own
processor and back-up facility carrying out a number of tasks. These functional
units have independent tasks, but communicate when and as necessary using a
common message bus. The BSC has marker and the cellular management units
combined to make one MCMU (Marker and Cellular Management Unit) . The
Marker part controls and supervises the GSW. The Cellular Management Unit
part is responsible for the cells and radio channels. It manages the configuration
of radio resources in the cellular network. There is also only one signalling unit. It
is the BCSU (Base Station Controller Signalling Unit) , which handles SS7
signalling between the MSC and the BSC and LAPD signalling between the BSC
and the BTS.
There are several versions of the NSN DX200 BSC, with different capacities.
Furthermore, it is possible to upgrade a certain version of the BSC in order to
increase its capacity.
To exemplify, the maximum capacity of a DX 200 BSCE (large configuration) is
256 Transceivers/248 BTSs. A DX 200 BSC2i can handle up to 512 TRXs /248
BTSs, while the DX200 BSC3i can manage up to 660 TRXs/248 BTSs in S11
software release.
However, the latest BSC3i with S12 software release is equipped with enormous
zoxojaka.und.slo
capacity and can be upgraded upto 1000 TRX in one cabinet and 2000 TRX in
two cabinets.

Fig. 14 Two Cabinet Configuration BSC3i 2000
zoxojaka.und.slo
The new BSC3i S12 release has a boosted capacity within a compact size. Upto
2000 TRXs, 100 ogical PCUs, 16 STM-1/OC-3 interfaces and upto 800 E1/T1
interfaces can be supported.

3.2.3 NSN BSC 120

The NSN BSC 120 is the central component of the BSS. It is responsible for
radio interface control, switching of connections between transcoders and BTSEs,
handling the Radio Resource Management (RRM) and stores the BSS database.
In BR5.5 software release, the BSC has a dynamic capacity of up to 2000 Erlang
and a static port connection capacity of up to 46 PCM30 lines. Due to its compact
design, occupying a volume of only 259 cm3 and due to its low power dissipation
(less than 475 W), the BSC operates without any fans or air conditioning system.
Consequently, the operator has a choice of locating the BSC centrally in
telecommunications rooms or remotely in a shelter or in a confined space. The
BSC can then act as a concentrator for the links between the Abis and Asub
interfaces.
In BR5.5, the BSC supports many additional features / customer benefits, e.g.:
Hierarchical Cellular Structures (HCS) with speed-sensitive Handover HO
algorithms
Emergency calls with priority
Data services (in-call modification, automatic fax,...)
SMS, SMS-Cell Broadcast Service
Easy system upgrade by means of full SW download
Full Rate FR, Half Rate HR, Enhanced Full Rate EFR speech codecs
zoxojaka.und.slo
High Speed Circuit Switched Data (HSCSD) (9.6/14.4 kbit/s; max. 4 TS)
Advanced Speech Call Items ASCI (Voice Broadcast Service VBS, Voice
Group Call Service VGCS)
General Packet Radio Services GPRS (CS1 & CS2; max. 7 TS)

zoxojaka.und.slo
Fig. 15 BSC Functions

3.2.3.1 BSC: Link Configuration

The BSC supports various BSC-BTSE configurations:
Star: Each BTSE connected by a link for its own.
Multidrop Chain: Various BTSEs are connected to one BSC using a common
link, which helps to save leased line costs by increasing the usage of 2
Mbit/s links. The allocation and re-allocation of timeslots on the link is freely
configurable.
Loop: A single link passes from the BSC via various BTSEs in one chain and
behind the last one back to the BSC. If the link is interrupted anywhere in the
chain, the system can survive this failure without degradation of service and
without disrupting stable calls, as it automatically detects the fault and
reconfigures the loop without manual interaction from the operator. In normal
operation, the loop configuration works as a multidrop configuration with
communication between BTSEs and BSC only in one direction around the
loop.
Cross-Connection: The basic configuration types like star, multidrop and loop
do not allow hub and spoke configurations which may be only realized with
high leased line costs or with external cross-connect equipment. To save
some of these equipments, a cross connection functionality is integrated in
the BTSE.
The TRAUs are always connected in Star configuration.
zoxojaka.und.slo

3.2.3.2 BSC Capacity

The BSC capacity in BR5.5 is:
max. 2000 Erlang switching & processing capacity
max. 46 PCM30/24 lines, i.e. 20 PCMS (Asub) + 26 PCMB(Abis) with flexible
PCMS lines configuration or
max. 36 PCM30/24 couples configurable on 9 QTLP
max. 20 TRAUs can be connected
max. 100 BTSE (sites)
max. 150 BTS (cells)
zoxojaka.und.slo
Fig. 16 Link Configuration

3.2.3.3 BSC Rack Configuration / HW Architecture

The BSC is equipped with the following elements:
Main Processor Control Card MPCC (Administrative Processor): The
MPCC controls the SN on the basis of TDPC messages; it handles traffic and
performance measurement; it is responsible for status and database
administration, HW configuration, diagnostics and maintenance management,
mass storage control, SW download, O&M interface control and TRAU
control. This unit is having 1+1 redundancy i.e.hot stand-by.
Universal Bus Extender board UBEX : The UBEX interfaces the MPCC to
the network, PLLH, PPCCs & PPLDs, line interface.
Telephony Distribution Processor Circuit TDPC + Memory of the TDPC
MEMT : The TDPC is responsible for message exchange with the other
network entities via PPCC & PPLD; it handles all signaling function above
MTP L2 and all application processes related to Call Control (CC), Radio
Resource management (RR), Mobility Management (MM) and IMSI tracing;
the MEMT is the TDPC memory extension and acts as mailbox for MPCC
TDPC message exchange; (1+1 redundancy; hot stand-by).
Peripheral Processor for CCS7 (PPCC): SS7 pre-processing (MTP L2) for
signaling towards the MSC; 2 PPCC boards; load-sharing redundancy.
Peripheral Processor for LAPD (PPLD): Responsible for handling of LAPD
protocol used for signaling to BTSEs and TRAUs; 14 + 1 PPLD boards; n+1
zoxojaka.und.slo
redundancy.

zoxojaka.und.slo
Fig. 17 BSC Rack
Switching Network SN16 or SN64: The SN16 switches control the MPCC
traffic connections between TRAU & BTSE and signaling between TDPC (via
PPLDs & PPCCs) and external entities; it is able to set up bi-directional
dynamic connections at 8 / 16 kbit/s (e.g. for HR / FR / EFR) and at n x 16
kbit/s. The SN64 (BR3.x or older) is not able to switch 8 kbit/s (e.g. HR). 1+1
redundancy; hot stand-by.
Phase Locked Loop High Performance PLLH: clock unit; 2 PLLH:
master/slave configuration.
Interface to LMT/OMC-B IXLT : allows MPCC to be connected to the
OMC-B via X.25 and to the LMT via proprietary T interface.
Mass Storage DK40: hard disk, containing copies of all BSS SW and all
configuration data to allow fast restart without downloading from the OMC-B;
1 + 1 redundancy.
Quadruple Trunk Line Peripheral board QTLP / Dual Trunk Line
Peripheral board DTLP: the standard QTLP Line Interface board houses 4
dual PCM30/24 line interfaces; connecting Abis / Asub to the SN16; 9 + 2
QTLP redundancy. DTLP for BR3.0 and older: only 2 PCM30/24 line
interfaces.
Power Supply PWRS

For GPRS introduction, the Packet Control Unit (PCU) is co-located with the
BSC. To incorporate the PCU (1 or 2 PCUs) into the BSC, 2 / 4 Peripheral
Packet Control Units (PPCU) are placed instead of 4 / 8 PPLDs.
zoxojaka.und.slo
Fig. 18 BSC Internal Architecture

zoxojaka.und.slo
Fig. 19 eBSC

3.2.3.4 eBSC - Enhanced BSC

The latest BSC product, also known as eBSC can support 2000 TRX or 1000
Cells. It is based on ATCA Platform. EBSC can be connected over STM-1/OC-3
and E1/T1 Interfaces towards TRAU and BTSE.
3.3 NSN Transcoder Products

3.3.1 TCSM Transcoder and Sub-Multiplexer (DX200)
The TCSM has evolved in three generations since 1992. The first product was
TCSME which supported upto 450 speech connections between BSC and MSC.
The second generation TCSM2E/2A, introduced in 1995, had enhanced capacity
of 960 (TCSM2E) and 768 (TCSM2A) speech connections for ETSI and ANSI
environments, respectively. The second generation transcoders also introduced
some advanced features like Acoustic Echo Cancellation, Noise Suppression etc.
The TCSM3i was introduced in 2006 which has enormously high capacity in
terms of traffic handling and supports new circuit pools. It can have upto 11520
ETSI and 9120 ANSI speech connections on A interface.
zoxojaka.und.slo
Fig. 20 Evolution Path of Nokia TCSM Products

TCSM3i has over 12 times more capacity compared to previous TCSM2. High
capacity BSC3i_2000 allows up to 2000 TRX configuration for which 99TCSM
units are needed. If TCSM2E/2A is used then it will require 12 TCSM2 cabinets.
However, for TCSM3i only one cabinet will be needed. Redesigned hardware of
TCSM3i makes it more compact. Instead of several Plug-In Units one transcoder
based on TCSM3i HW technology consists from one Plug-In Unit. TCSM3i
cabinet is based on M98 mechanics. It offers more flexible pool usage in
A-interface. TCSM3i also supports all-in-one circuit pools like pool 28. One
TCSM3i functional unit can handle maximum four TC-PCM on A interface. (120
FR circuits).
3.3.2 TRAU
TRAU is responsible for:
Transcoding, i.e. the compression of speech data from 64 kbit/s (on A
interface) to 13 / 12.2 / 5.6 kbit/s in case of FR/EFR/HR speech coding. All
the 3 speech coding is supported by the TRAU in BR5.5 (Triple Rate
functionality).
Rate Adaptation in case of data (Bearer Services, data Teleservices)
transmission.
Signaling data are transmitted transparent through the TRAU.
The TRAU consists of the following modules:
zoxojaka.und.slo
BSC Interface board BSCI
MSC Interface board MSCI
Transcoding & Rate Adaptation Card TRAC
Power Supply PWRS
3.3.3 Transcoding & Rate Adaptation Card TRAC

TRAC is responsible for central TRAU functions: Transcoding & Rate Adaptation.
It is able to (de-)compress speech using FR, EFR and HR speech coding.
Furthermore, the TRAC performs VAD/DTX function. Each TRAC provides the
processing of up to 24 TCHs (UL & DL).
TRAU is fully equipped with 6 TRACs, using an n+1 (5+1) redundancy.
Therefore, the TRAU is able to process up to 120 TCHs (92 in GSM1900) totally.

zoxojaka.und.slo
Fig. 21 TRAU Functions
BSC Interface board (BSCI)

BSCI board provides the link to BSC via Asub interface (1 PCM30/24),
multiplexing the traffic from/to the TRACs. It houses central TRAU controller, the
BSC clock generator and the link to an LMT via proprietary T interface. The BSCI
is duplicated; the non-active copy operates in hot-standby mode.
MSC Interface board (MSCI)

MSCI board provides the connection to the MSC via A interface (4 PCM30/24),
multiplexing the traffic to/from the TRACs. Furthermore, it is processing the LAPD
protocol of the BSC control link. The MSCI is duplicated; the non-active copy
operates in hot-standby mode.

TRAU Rack
The rack dimensions are 2000 mm (height), 600 mm (width) and 300 mm (depth).
The volume is 360 l, power consumption less than 476 W. Due to the low power
consumption no fans are necessary for cooling. Up to four TRAU modules can be
incorporated into one TRAU rack. Therefore, the maximum processing capacity is
480 TCHs.
zoxojaka.und.slo
Fig. 22 TRAU Rack

zoxojaka.und.slo
Fig. 23 eTRAU
Enhanced TRAU (eTRAU)

The enhanced TRAU (eTRAU) is the high capacity version of transcoder which
we have seen earlier. It supports transcoding functions with 11000 codes and is
based on ATCA platform. Full Rate, Half Rate, Enhanced Full Rate, Adaptive
Multi Rate etc are examples of codecs available on eTRAU. It can support
STM-1/OC3 interface for connecting MSC as well as BSC. Features like Voice
Quality Enhancement (VQE) Acoustic Echo Control, Noise Reduction,
Automatic Level Control etc are also available in eTRAU.

4 Network Switching
Subsystem (NSS)
NSS or Core network part comprises of network elements which perform
switching, subscriber handling, and control signalling functionality of the mobile
networks. Further, the core network has been divided in Circuit core and Packet
core for speech and data traffic respectively. There are various network elements
which are available in NSN product portfolio which can provide NSS network
element functionalities.
4.1 DX 200 MSC/VLR Architecture

DX 200 MSC/VLR consists of a number of functional units, each with its own
processor and back-up facility carrying out a number of tasks. These functional
units have independent tasks, but communicate as and when necessary using a
common message bus. The MSC is integrated with the VLR and communication
between the two entities is entirely internal signaling. The MSC also has gateway
functionality; that is, it has interfaces to other networks outside the GSM PLMN.
zoxojaka.und.slo
Fig. 24 Block diagram of the DX 200 MSC/VLR (subrack architecture)

The maximum number of visitor subscribers roaming under a DX 200 MSC is

150000. A DX200 MSCi is capable to handle up to 600000 BHCA (busy hour call
attempts) and its VLR units support up to 600000 subscribers.
DX 200 MSC has full Service Switching Point (SSP) functionality. SSP is part of
an Intelligent Network (IN) solution. Features, such as simplified 800 number
management, can be supported with IN.
4.1.1 Functional units in the MSC/VLR

DX 200 MSC/VLR is the biggest element (with respect to number of functional
units) in the GSM network. It is not the intention of this section to give a complete
explanation of all the units in this section, but only a simple overview of them to
give an understanding. For the purpose of ease of understanding the units have
been classified according to their functions.
Signaling Units
There are six different types of signalling units. These are the CCSU (Common
Channel Signalling Unit) , which handles trunk signalling (SS7) towards the
HLR, other MSCs and PSTN exchanges and is responsible for call control for
trunk originated calls. Another one is the BSU (Base Station Signalling Unit) ,
which takes care of SS7 signalling towards the BSC and call control for mobile
originated calls. The CCMU (Common Channel Signalling Management Unit)
zoxojaka.und.slo
handles centralised functions of the SS7 signalling system. It is only needed in

big exchanges. In smaller exchanges, the CCMU's functions are taken over by
the CM and STU. For MSCs connected to networks which still use R2 signalling
there is CASU (Channel Associated Signalling Unit) , which performs R2
signalling. The PAU (Primary Access Unit) handles DPNSS signalling towards
PABXs and the LSU (Line Signalling Unit) controls the announcement machine
(ANM). One special unit is the IWCU (Inter Working Control Unit) , which
controls Compact Data Services Unit (CDSU), Echo Cancellers (EC) and any
other interworking functional units.

Switching related units

In switching related units of the MSC, the GSW (Group Switch) is the switching
matrix. The basic function of the MSC is the switching of telephone calls. This is
implemented by a group switch where each input is capable of being switched to
any output. The M (Marker) controls and supervises the GSW. There are three
additional units that work together with the GSW. The first of these is the DTMFG
(Dual Tone Multi-Frequency Generator) for generating DTMF signals when
required, such as when the user is trying to transmit DTMF signals to equipment
at the other end. The next one is the TG (Tone Generator), which is responsible
for generating various types of tones, such as dial tone, busy tone, information
tone etc. The TG and DTMFG functions are combined in the TGFP (Tone
Generator Field Programmable) unit in recent MSCs. The third unit is the
CNFC (Conference Circuit) , used for enabling multi-party conference.
Database and statistics related units

One of the most important units in an MSC is the VLRU (Visitor Location
Register Unit) . This is the NSN implementation of the VLR as a functional unit of
the MSC; thus it performs VLR functions. The CMU (Cellular Management Unit)
controls and supervises cellular network and handovers. Exchange specific
statistical data is collected by the STU (Statistical Unit) . For a switch with
relatively low traffic, the STU can also collect charging data, but for switches
zoxojaka.und.slo
which handle high traffic, the CHU (Charging Unit) is needed to collect charging
data.

External interface and data related units

The unit with which a person can do the normal operation and maintenance tasks
is the OMU (Operation and Maintenance Unit) . This is the link between the
user and the MSC. It monitors the exchange continuously and starts recovery
procedures if errors occur. The BDCU (Basic Data Communications Unit)
contains all communication links to the O&M network (terminals for X.25 packet
network and/or for timeslots of the PCM link) and to the Billing Centre. For
subscribers data (data calls, fax etc.) there are Data Service Pools . They
contain modems for data communication services to the PSTN. The ECU (Echo
Canceller Unit) is needed in interworking with the PSTN. It cancels the echo
generated in the 2-wire subscriber cable in the PSTN. The ET (Exchange
Terminal) is the unit that handles the external 2 Mb PCM circuits. There is no
duplication of ETs since their reliability is much greater than that of the actual
link, therefore, in the event of failure; redundancy is taken care of by reorganising
the signalling and traffic.
Other units
The CM (Central Memory) is one of the most important units. It is the RAM of
the exchange, which holds the system software and also keeps a copy of all
exchange specific software data. The CLSU (Clock and Synchronisation Unit)
is responsible for generating synchronisation signals for different units as well as
zoxojaka.und.slo
for other elements such as the BSC and the HLR. The VANG (Verbal
ANnouncement Generator) is used for playing recorded announcements. The
MB (Message Bus) is the parallel, duplicated message bus for sending and
receiving DX messages between different functional units.

4.2 DX 200 HLR/AC/EIR

Once the architecture of the DX 200 MSC/VLR is understood, it becomes a
relatively easy matter to understand all the other DX 200 elements, because of
the same architecture and the presence of similar units in all the elements. The
HLR is no exception. The figure below shows the DX 200 HLR architecture and a
brief explanation of HLR-specific units follows thereafter.
zoxojaka.und.slo
Fig. 25 Block diagram of the DX 200 HLR
The maximum number of created subscribers in a DX 200 HLR is 300000. A DX

200 HLRi supports 1200000 subscriber and its integrated AuC has a capacity of
2.4 million subscribers.
4.2.1 Functional units in the HLR

It can be seen that there is only one signalling related unit in the HLR compared
to the many in MSC. This is because user traffic does not come to the HLR. The
rest of the units and their functions are exactly same as in the MSC. However, we
see that there are three extra units in the HLR that do not exist in the MSC.
These are the database-related units . The HLRU (Home Location Register
Unit) is responsible for subscriber data management and mobility management.
The Authentication Unit (ACU) is responsible for management of authentication
data. It generates authentication triplets and sends them to the VLR and the
EIRU (Equipment Identification Register Unit) handles the equipment identity
and its checking.

5 NSN Release 4 Mobile

Switching Centre Server
(MSS)
NSN's MSC server concept offers common core network for the GSM and UMTS
subscribers. Release 99 introduces the UTRAN network. NSN's 3G-MSC offers
connections both towards the GSM Base Station Subsystem (BSS) and towards
the WCDMA-based UMTS Terrestrial Radio Access Network (UTRAN).
When the network architecture based on UMTS Release 4 is introduced, the user
and control planes are separated in the network. This means that the 3G-MSC
evolves to the direction where the MSC's switching functions are brought to the
Media Gateway (MGW) product, and the MSC evolves to an MSS-like product.
The MSS product provides call control logic for terminals that use circuit switched
logic.
MSS mainly comprises the call control and mobility control parts of a GSM/UMTS
MSC. MSS is responsible for control of mobile originated and mobile terminated
circuit switched calls. It terminates the user-network signalling and translates it
into the relevant network network signalling. The MSS also contains a VLR to
zoxojaka.und.slo
hold mobile subscribers' service data and CAMEL related data. MSS controls the
parts of the call state that pertain to connection control for media channels in a
MGW.
MSC server connects to the Media Gateway using the H.248 protocol
(MEGACO). The physical connection between the MSC server and Media
Gateway (MGW) is Ethernet. The interface between two MGWs performs bearer
control and transport through the ATM backbone by using several ATM
Adaptation Layer protocols (AAL1, AAL2, and AAL5) or the IP backbone.

Fig. 26 Integrated MSS and MGW connections
The interface between two MSC servers (between MSC server and Gateway
MSC server) uses the Bearer Independent Call Control protocol (BICC), Session
Initiation Protocol (SIP), or ISUP if the physical connection is based on E1/T1
(TDM). There is also an interface from the MSC server to the 3G-HLR using the
Mobile Application Part (MAP) protocol over SS7 or IP (SIGTRAN). In this case
the physical connection can be either Ethernet or E1/T1 (TDM).
MSS can be deployed in the operator's 2G-network by integrating MSS
functionality into the regular MSC. MSS can also be deployed as a standalone
zoxojaka.und.slo
network element. Standalone MSS means that only signalling is conveyed to
MSS. Both TDM and packet based user plane is transported via MGW.
The functionality of the MSC server can be divided into two roles: Visited MSS
(VMSS) and Gateway MSS. VMSS contains VLR and controls the MGW that is
connected towards the (BSS and UTRAN) radio networks. Gateway MSS
functionality is to control the MGW that is performing interworking between packet
core network and the external PSTN/ISDN network.
The NSN product that performs the Gateway MSS functionality is called Gateway
Control Server (GCS).

Fig. 27 Network environment of standalone MSS
The standalone MSS is a network element that does not have connections
towards the TDM-based network. The standalone server offers basically the GSM
intelligence and user plane is transported via MGW. The product configuration is
optimised for the packet core network. Naturally, the concept of VMSS and GCS
applies also in stand-alone mode.
zoxojaka.und.slo
Fig. 28 Interfaces from MSS

In the following section, some of the interfaces in the above figure are briefly
described.
The A-interface is used to transmit speech, data and signalling between MSS and
BSS. When the A-interface is connected to the MGW, BSSAP signalling is routed
from MGW to MSS using SIGTRAN. The MGW thus acts as a signalling gateway
between the BSS and the MSS.
The Iu-CS interface is used to carry circuit switched traffic between 3G-RAN and
MGW. This interface is ATM-based and uses AAL2 (ATM Adaptation Layer 2).
MSS handles the control plane traffic of 3G-RAN.
The Iu-CS control plane is routed from the RNC to the MGW, where it is relayed
to MSS using SIGTRAN.
The Nc reference point describes the interface between VMSS and Gateway
MSS. Over the Nc interface network-to-network based call control signalling is
performed. BICC CS-2 is supported in the Nc interface. BICC CS-2 is
Bearer-Independent Call Control signalling, since it will support both ATM and IP
based core networks. Alternatively, SIP is supported in Nc, if core network is
based on IP transport.
The Mc reference point describes the control interface between MSS and MGW.
The used control protocol here is H.248.
Physical connection between MSS and MGW is Ethernet 100. The Ethernet
zoxojaka.und.slo
router/switch can be co-located with each network element (MSS or MGW) in
order to transport signalling information via ATM.
MSS-GCS interface will be based on SIP protocol in order to enable interworking
between the CS domain and the IMS (IP Multimedia Subsystem).
The Nb reference point in the 3GPP model describes the interface between two
MGWs. The NSN gateway utilises several ATM Adaptation Layer (AAL) protocols
for media transport:
AAL1 PVC/SVC (permanent/switched virtual circuits) for circuit switched data
and for PCM coded speech.
AAL2 for compressed speech and for non-real time data transport.
AAL5 PVC/SVC carries user and control data and transports IP traffic.
The ATM forum has specified UNI 4.0 (User Network Interface). This protocol is
used for creating SVC connections from gateway to border ATM backbone
element.
The C reference point describes interface between GMSS to the HSS, while the
D reference point describes interface between the MSS to the HSS. These
interfaces are implemented by using MAP over SS7 and MAP over IP
(SIGTRAN). The physical connection can be either Ethernet or E1/T1/JT1.

The interface from the MSS to the SCP (Service Control Point), and the GMSS to
the SCP, is CAMEL, which provides mechanisms to support services of operators
which are not covered by standardised UMTS/GSM services even when roaming
outside the home PLMN. The connection towards SCP is E1/T1/JT1 based.
MSS is integrated in both classic and i-series MSCs. Some of the features of the
MSS are the fast MB (Message Bus) for interconnecting the dedicated processor
units, the GSW (Group Switch) for switching speech/data/signalling circuits, and
finally the ETs (Exchange Terminals) to interface with the transmission
systems/various auxiliary equipment.
5.1 NSN Media Gateway (MGW)

A MGW is needed to interface between the IP mobile core network and the
traditional circuit switched networks like PSTN and GSM. It acts as a gateway for
both media (for user data) and signalling (signalling transport). The higher layers
of the signalling protocol, however, do not end at this element, but go through
transparently. The media gateway control protocol (MGCP) is intended for use on
the interface between a MSS and remote MGWs.
zoxojaka.und.slo
Fig. 29 The role of the Media Gateway
The gateway can be stand-alone or integrated to the MSC, depending on the

network configuration and the amount of traffic. The division between MSC server
and MGW is not one to one. One MSC server may control many MGWs, which
brings scalability into the system.
MGW uses the ATM-based IPA2800 platform. The high-level network element
consists of three parts: network interface functions, switching and multiplexing
functions, and also control functions.

Fig. 30 Block diagram of the MGW
Units is MGW:
A2SU AAL2 Switching Unit
CACU Control and Administrative Computer Unit
CM Central Memory Unit
ISU Interface Signalling Unit
MXU ATM Multiplexer Unit
NEMU Network Element Management Unit
zoxojaka.und.slo
NIS1 Network Interface Unit (STM-1)
NIWU Network Interworking Unit
OMU Operation and Maintenance Unit
SPMU Signal Processing Management Unit
SFU ATM Switching Fabric Unit
DSPU Distributed Signal Processing Units handling, e.g. transcoding (in role
of TCU) and other required tasks
TBU Timing and Hardware Management Unit
NIP1 Network Interface Unit (PDH E1/T1/JT1)
One important difference between future 3G core networks and today's
architecture is that in 3G, the speech (and video) is not transcoded straight from
the Radio Network Controller (RNC). Instead, the information is transferred
through the network in a compressed format and is controlled by the MSC server.
The data is only uncompressed or transcoded once the information has to go out
to the outside world.

5.2 D900/D1800NSS - Switching Subsystem

zoxojaka.und.slo
Fig. 31 Siemens Solution

5.2.1 D900/D1800NSS Architecture

The following network elements determine the system architecture of the
PLMN-NSS: Mobile-services Switching Center (MSC), Visitor Location Register
(VLR), Home Location Register (HLR), Authentication Center (AC) and
Equipment Identification Register EIR (optionally). For the support of ASCI
functions the MSC integrates a Group Call Register (GCR) and for IN/CAMEL
support the Service Switching Function has to be included.
The following description is based on the current NSN solution for the
Circuit-Switched CS branch of the GSM Core Network (CS1.0), with Software
Release SR9.0. The GPRS part of the GSM CN (Packet-Oriented PO 1.0 / GPRS
Release GR 2.0) is not part of this course. It is described in course TM2110
GPRS Introduction.
5.2.2 D900/D1800NSS HW Solution

All the network elements of the PLMN-NSS are realized with D900/D1800NSS
nodes, which are based on experienced EWSD technology. It is fully digital and
modular with respect to software and hardware.
A D900/D1800NSS node consists of a row of racks. There are two types of
racks: the classic rack and the innovation rack .
zoxojaka.und.slo
The racks are available in two height: 7 / 8 foot (2.13 m / 2.45 m). The classic
rack is 770 mm width and 500 mm depth (incl. protective cover), the innovation
rack has 900 mm width and 600 mm depth.
The rack is sub-divided into module frames, carrying special functional units. The
module frames are equipped with modules.

Combination of Network Elements

MSC and VLR are always co-located (associated) in an NSS node, and HLR and
AC are also always co-located in an NSS node. So there are NSS nodes with
MSC/VLR and NSS nodes with HLR/AC functions. Furthermore, NSS nodes can
combine MSC/VLR/HLR/AC functions. EIR are possible as stand-alone NSS
nodes or in combination MSC/VLR/EIR, HLR/AC/EIR or MSC/VLR/HLR/AC/EIR.
zoxojaka.und.slo
Fig. 32 D900/D1800 SSS HW Architecture

D900/D1800NSS: Block Diagram

The D900/D1800NSS are based on a modular HW and SW concept. They
contain the in the current SW version the following HW subsystems which are for
the most part autonomous:
Line/Trunk Groups (LTG)
Data Service Unit (DSU)
Switching Network (SN)
Signaling System Network Control (SSNC) (NSS innovation node) or
Common Channel signaling Network Control CCNC (NSS classic node)
Coordination Area (incl. Coordination Processor CP)
LTGs connect the NSS node to the external world and contain several special
functions necessary for PLMN operation.
DSU is included with interworking functions (IWF) to support data services.
SN is used to switch-through user connections and signaling data. It is the link
between the LTGs, CP and SSNC/CCNC.
Coordination Processor CP is the central element of the Coordination Area. It is
responsible in the NSS network node for common functions such as coordination
of the distributed peripheral microprocessor controls of the other subsystems and
the data transfers between them. Furthermore, it performs common functions like
call processing, operation and safeguarding.
zoxojaka.und.slo

zoxojaka.und.slo
Fig. 33 D900/1800SSS: Block Diagram

5.2.3 Line/Trunk Group LTG

The various LTG control and supervise incoming and outgoing traffic with SS7
signaling to and from:
Base Station System BSS Other public networks, e.g. PSTN/ISDN or other
PLMN
Other D900/D1800 NSS network nodes
Short Message Service Centers SM-SC
Voice Mail System Centers VMSC
IN/CAMEL nodes (Service Control Point SCP / CAMEL Service Environment
CSE)
Remote Access Server RAS for Mobile Internet Access MIA / Wireless
Application Protocol WAP
Furthermore, the LTGs control call traffic for special functions, such as:
Interworking function (IWF) in the DSU (for GSM data services)
Digital Announcement Systems (DAS) in the MSC (for standard
announcements)
Trunk loop function for Mobile-Mobile-Calls (MMC)
Trunk loop function for calls with lawful interception
Conference function (in relation to the Multiparty MTPY services or ASCI
services (VGCS, VBS))
zoxojaka.und.slo

LTGs support all the usual signaling systems (e.g. SS7, MFC:R2) for calls to
fixed networks. Since SS7 is mandatory within the GSM-PLMN, this is the
predominant method.
LTGs furthermore contain a large variety of additional functions, e.g.
Adaptation of Primary Digital Carrier (PDC) to internal SDC
Measurement of call duration and general traffic measurement
Insertion of tones and standard announcements (with OCANEQ digital
announcement equipment or DAS Digital Announcement System)
Duplication / re-assembly of data to / from both SN sides
zoxojaka.und.slo
Fig. 34 LTG Line/Trunk Group

5.2.4 LTG Connections

LTGs can be connected with Primary Digital Carriers (PDC) for a transmission
rate of 2.048 Mbit/s (PCM30: 32 channels, each with 64 kbit/s). Every LTG can
be connected with up to 4 PDC lines to external network nodes.
The connections between the LTG and SN are Secondary Digital Carriers (SDC)
with a transmission rate of 8.192 Mbit/s (128 channels, each at 64 kbit/s). Each
LTG is connected to both sides of the redundant SN. The LTG is responsible for
adaptation between the PDC and SDC carriers and for the duplication /
re-assembly of the data to / from the SN.
LTG Hardware
Two different LTGs are used, depending on the application:
LTGN, for all kinds of LTGs and subscriber lines and for implementation of a
conference LTG (MTPY / ASCI services), standard announcements LTG and
IN/CAMEL user interaction LTG for internal IP.
LTGG as IN/CAMEL user interaction LTG for internal IP.
LTGN is the product of a long evolution to reduce the amount of modules for one
LTG: LTGB (2 frames), LTGG (1/2 frame), LTGM (1/5 frame) and LTGN (1/8
1/16 frame = 1-2 module).
zoxojaka.und.slo

The LTGN has two capacity stages:

Basics functions (1 module) and basics functions plus additional functions (1
module). The basic functions of the LTGN are implemented in Group
Processor N GPN.
Additional functions of the LTGN are accommodated when necessary on a
second module, the functional unit Line/Trunk Unit: Supplementary LTU:S.
The following additional modules are possible:
1.
1. Conference Unit C COUC (for MTPY & ASCI services),
2. Digital Echo Compensator DEC120,
3. Operationally Controlled Equipment for Announcement OCANEQ (can
replace from SR9.0 the DAS for all available announcements in the
MSC) and
4. Voice Processing Unit VPU (for analysis of received speech commands
and conversion into control commands for IN/CAMEL).
Only one additional module can be accommodated in the LTU:S in each case.
zoxojaka.und.slo

zoxojaka.und.slo
Fig. 35 LTG Connections/Hardware

LTGN (GPN) Block Diagram

The basic functions of the LTGN comprise a single functional unit divided up into
task-related parts. The basic functions of the LTGN are implemented in Group
Processor N GPN. The basic functions of the GPN are realized by the:
Group Processor GP- part
Signaling Link Control SILC- part
Code Receiver CR- part
Digital Interface Unit DIU- part
Group Switch GS- / Line Interface Unit LIU- / Tone Generator TOG- part
Group Clock Generator GCG- part and the
Input/Output Processor IOP- part
The GP-part matches the incoming information from the surrounding network
node area to the internal message format of the system and controls all parts
within the GPN. To do this it has interfaces to the IOP part (controls: DIU, CR,
GCG, GS/LIU/TOG and SILC part) and the LTU:S as well as to the controls on
the front panel of the module.
IOP part with SILC part: The IOP part controls DIU, CR, GCG, GS/LIU/TOG and
SILC part. The SILC part functions as Input/Output processor. The SILC part is
used to connect a number of signaling channels via which either the protocol for
DSU or the ISDN D-channel protocol for primary access can be handled. On the
LTG side, the SILC part completes the L2-functions of signaling protocols (GP
zoxojaka.und.slo
part peripheral unit).

GS/LIU/TOG part: The GS interconnects the DIU, TOG, CR and SILC and
connects them to the LIU. The LIU is used to connect the duplicated SN (SN0 &
SN1) to the LTG. The TOG provides programmed tones.
The CR part provides 16 signaling receivers for the LTG call processing.
The DIU part includes connection facilities for 4 PCM30 lines.
The GCG part provides the clock for the speech data and for signaling on the
LTGN.

zoxojaka.und.slo
Fig. 36 LTGN (GPN) Block Diagram

5.3 Data Service Unit DSU

An Interworking Function (IWF) has been implemented for the D900/D1800 NSS
nodes MSC/VLR to support data telecommunication services (bearer services BS
and data teleservices TS). This entails the availability of transparent and
non-transparent network support control functions for data transmission. The
IWF guarantees compatible connections between two users of the corresponding
BS or data TS. The IWF is implemented in the DSU, in the CP and LTG
(GP/GPN).
By introducing a general BS, the facility allows to use all available data rates of
the BS group and not just one. Moreover, the BS20 offers the HSCSD facility
which consists of the following two parts: combination of several Time Slots (TS)
for one call and uses of the new Coding Scheme CS with 14.4 kbit/s.
DSU Hardware
The DSU consists of:
Digital Line Unit System (DLUS)
Interworking Equipment high speed IWE:HS with integrated baby modem
DLUS is responsible for the DSU control and clock generation, handles
information exchange with the IWF:LTG and includes a bus distributor function to
connect DLUS with the peripheral functional units of the IWE:HS.
zoxojaka.und.slo
The IWE:HS determines the DSU application; it is responsible for the data
interworking. One IWE per data connection is looped in for the users of BS and
data TS. Two IWEs are looped into the MSC for an MMC. The IWE:HS supports
HSCSD channel combining and CS with 14.4 kbit/s.

zoxojaka.und.slo
Fig. 37 DSU Data Service Unit
5.4 Switching Network SNB

In a network node, the Switching Network B (SNB) is the link between the
following:
LTGs for speech and data connections
LTGs and Coordination Processor CP for message exchange
LTGs and SSNC/CCNC for SS7 message exchange
A central function of SNB (which is an especially compact version compared to
old SN) is to switch subscriber calls received in one LTG through to the
destination LTG.
SNB sides: SNB0 / SNB1
For security reasons, the SNB is always duplicated, i.e. it consists of two SN
sides SNB0 and SNB1. Each connection is switched redundantly through both
SNB sides. For redundant switching, an LTG has redundant connections to both
SNB sides. It sends identical connection data to both SNB sides and receives
identical connection data from both SNB sides.

zoxojaka.und.slo
Fig. 38 Switching Network B
SNB: Functional Units

SNB consists of two HW functional units:
Time Stage Group B (TSGB)
Space Stage Group B (SSGB)
TSGBs and SSGBs perform switching in the SNB according to the principle Time
Space Time.
In the smallest SNB:63LTG there is a combined Time & Space Stage Group
used.
The larger SNBs consist of TSGBs and SSGBs. An SNB capacity stage can be
equipped on each SN side with 1, 2, 4 or 8 TSGBs and with 0,1,2 or 4 SSGBs.
The number of TSGBs required for the two SNB sides of an SNB capacity stage
depends on the number of LTGs to be connected.
Each group (TSGB or SSGB) in the SNB is controlled by an own Switch Group
Control SGCB. The SGCB accepts setting commands from the CP call
processing programs. (The CP call processing programs use setting commands
to initiate the switching of a connection path.)

SNB: Interfaces
A TSGB has a total of 64 SN-external interfaces comprising the following:
A maximum of 63 SDC:LTGs for the connection of a maximum of 63 LTGs.
Speech and data connections between the LTGBs are carried via SDC:LTG
as well as message transfer between LTG and CP. The no. of SDC:CCNC
decrease the no. of SDC:LTGs.
The SDC:TSG (Time Stage Group) interface for the message transfer
between the CP (via Message Buffer Unit for LTG MBU:LTG) and the LTGs
connected to the TSGB.
The SDC:CCNC for the SS7 message transfer between CCNC and LTG.
Additionally, an SDC:SGC exists for the communication between the CP (via
MBU:SGC) and the Switch Group Controls (SGC).
zoxojaka.und.slo
Fig. 39 SN B Interfaces and Functional Units

SNB: Capacity Stages

Different capacity stages of the SNB are available, depending on the number of
LTGs to be connected:
SNB:504LTG for the connection of up to 504 LTGs
SNB: 252LTG for the connection of up to 252 LTGs
The innovation nodes, using the new Message Buffer D MBD and SSNC, are
equipped with up to 100% of the above listed maximum possible no. of LTGs.
The classic nodes, using the old Message Buffer C MBC and CCNC, can only be
equipped with up to 50% of the above listed maximum possible no. of LTGs. If (1
or 2) SDC:CCNCs are used, the number of LTGs is reduced accordingly.
The NSS nodes can be distinguished in switching nodes (MSC/VLR or
MSC/VLR/HLR/AC/ EIR) and non-switching nodes (HLR/AC or EIR).
The capacity stage SN:63LTG is generally used for non switching nodes.
The capacity stages SNB:126LTG to SNB:504LTG are generally used for
switching nodes.
The SNB needs between one rack (SNB:63LTG) and 10 racks (SNB:504LTG at
max. capacity stage). Or to be more precise: It needs between 2 and 20 frames,
zoxojaka.und.slo
distributed to 1 - 10 partially used racks. The remaining frames of the racks are
filled with LTGs.

zoxojaka.und.slo
Fig. 40 SN B Capacity Stages

5.5 Signaling System Network Control SSNC

Signaling System Network Control (SSNC) / Common
Channel signaling Network Control (CCNC)
SSNC and CCNC are responsible for the control of SS7 signaling traffic in an
NSS network node.
CCNC is part of the NSS classic node. A maximum of 112 signaling links (each
of 64 kbit/s) can be processed by the CCNC.
SSNC is the main part of the NSS innovation node. The maximum system
configuration allows the connection of 1500 signaling links.
In the current SW version, the SSNC or the CCNC can be supported. For that
reason coexistence of SSNC and CCNC operation will be possible within the
same APS (Application Program System). This coexistence is static only. That
means only one of the mentioned SS7 platforms is running at one time. The
choice has to be made during APS installation. If the SSNC is supported, the
Message Buffer D MBD has to be used.
In the following section, the SSNC is described.
zoxojaka.und.slo

SSNC functions
SSNC provides protocol functions of the Message Transfer Part MTP (Level 1
3), the Signaling Connection Control Part (SCCP) and the Operations,
Maintenance & Administration Part (OMAP).
SSNC offers maximum efficiency for SS7 signaling. It can also be used as a
gateway between different networks and network operators. For such applications
the SSNC offers special features for recording and verifying the amount of traffic
with adjacent network nodes and also for protecting the own network against
misuse. It is a future-proof system which also supports connection of SS7
high-speed signaling links HSL.
zoxojaka.und.slo
Fig. 41 SSNC Signalling System Network Control

SSNC Hardware Architecture

SSNC Hardware is based on EWSX ATM technology. It is nearly identical to the
architecture of the NSN SGSN. The SSNC functions are spread over several
functions. This results in a high degree of flexibility. Adaptation to future
requirements regarding message throughput and new features is possible, due to
the scalability of the main processor platform.
The SSNC Hardware comprises the following units:
Line Interface Cards (LIC)
Main Processors (MP)
ATM Switching Network (ASN)
ATM bridge Processor, type C
Line Interface Card (LIC) : Converts incoming message streams from the SS7
network from synchronous transfer mode with 3 Mbit/s to internal ATM cell
streams with 207 Mbit/s and vice versa. LIC is also the interface to high-speed
links HSL. Up to 248 signaling channels, i.e. 8 PCM30 links or 8 HSL can be
connected to a LIC.
Main Processor (MP) : Is the key component of the SSNC. Up to 50 MP exist in

the maximum SSNC configuration:
Up to 47 MPs for Signaling Link Termination MP:SLT (handling MTP, SCCP),
zoxojaka.und.slo
1 MP for Signaling Manager MP:SM (MTP & SCCP management &

maintenance),
1 MP for Statistics MP:STATS and
1 MP for Operation, Administration & Maintenance MP:OAM

ATM Switching Network (ASN) : Interconnects the individual MPs and links the
LICs to the MP:SLTs. An ASN40 with 40 Gbit/s switch capacity is used.
ATM bridge Processor, type C (AMPC) : Is the interface between the ATM
equipment in the SSNC and the Coordination Processor CP in the Coordination
Area. It converts the ATM data from the SSNC to the CP communication mode
and vice versa. For functional purposes, the AMPC belongs to the SSNC, but it is
located in the module frame of the CP.
zoxojaka.und.slo
Fig. 42 SSNC HW Architecture

5.6 Coordination Area

Coordination Processor CP113C/CR: Is a central element of NSS network
node. It is responsible in the NSS network node for common functions such as
coordination of the distributed microprocessor controls and the data transfer
between them. The CP performs the following functions: Call Processing,
Operation and Safeguarding. Normal NSS nodes use a CP113C; CP113CR is
used for rural/container NSS (MiniSwitch).
Message Buffer MB : The MBB is used in the NSS classic nodes (with CCNC);
the MBD in the NSS innovation nodes (with SSNC). With usage of the new MBD,
there are no LTG mounting restrictions of SNB. The MBD controls the message
exchange between the individual subsystems, i.e. between CP113C and the
LTGs, CP113C and the SN, LTGs, LTGs and SSNC.
Central Clock Generator (CCG) : The CCGB (type B) is used (with CCNC &
MBB) in the NSS classic nodes, the CCGE (type E) is used (with SSNC & MBD)
in the NSS innovation nodes. The CCG supplies NSS network node with a highly
accurate, stable clock. It locks onto an external reference (e.g. a cesium
frequency standard). The clock is available even if all reference signals fail.
Craft Terminal CT : PCs (Craft Terminals CT) are used for local O&M of the NSS
nodes. They are equipped with Windows NT and CD-ROM drives.
External Memory EM : EM are Mass Storage Media. It used for e.g. for programs
zoxojaka.und.slo
& data that do not always have to be resident in the CP, as mirror image of all
resident programs & data for automatic recovery and call charge and traffic
measurement data. It consists of two Magnetic Disc Devices (MDD), a Magnetic
Tape Device (MTD) or Magneto-Optical Disk (MOD) for input & output.
Authentication Centers: Authentication Centers are connected to the CP only
when the NSS node includes AC functionality.

zoxojaka.und.slo
Fig. 43 Coordination Area
Coordination Processor CP113C/CR

CP113C/CR consists of a modular multiprocessor system. It performs the
following functions:
Call Processing (digit translation, routing, zoning, path selection through the
switching network, charge registration, traffic data administration, network
management),
Operation (input/output to/from EM, communication with CT, communication
with the Switch Commander SC) and
Safeguarding (self-supervision, error detection, error treatment).

The CP consists of the following functional units:

Base Processors (BAP) : 1 BAP operates as Master BAPM, 1 as Spare
BAPS. The BAPM processes O&M tasks plus some of the call-processing
tasks; BAPS handles only call-processing.
Call Processors (CAP) : CAPs (between 0 and 10) handle call-processing
tasks only. They form a pool (n+1) redundancy.
Input/Output Controls (IOC): The IOCs form the interfaces between the
BCMY and the IOPs. 1 / 2 pair are used.
Input/Output Processors (IOP): Various types of IOPs connect the
CP113C/CR with the other HW subsystems and functional units of the NSS
node. IOP types usage in the CP113C/CR are: IOP:MB (IOP for MB, used for
the connection to MB, SYP, CCG, CCNC), IOP:TA (IOP for Time & Alarms),
IOP:UNI (UNIversal IOP for O&M devices), IOP:SCDP (IOP for Serial data
Communication Devices with BX.25/X.25 Protocol; i.e. for connection to the
Switch Commander and Operation System OS) and IOP:AUC (IOP for
Authentication Center).
ATM bridge Processor (AMPC) : The AMPC links the CP113C/CR to the
SSNC and converts the ATM data (SSNC) to CP format and vice versa.
Common Memory (CMY) : The components of CMY include the database
shared by all processors and the input & output lists used by the IOPs for MP
(IOP:MB) and the communication areas used by the IOPs linked to the O&M
periphery.
zoxojaka.und.slo
Bus for Common Memory (BCMY) : The BCMYs interlink all processors
(BAP, CAP, AMPC) including IOCs and links them with the CMY.

zoxojaka.und.slo
Fig. 44 Coordination Processor

5.7 Summary D900/D1800NSS

The D900/D1800NSS contains the following HW subsystems:
Line/Trunk Groups LTG
Data Service Unit DSU
Switching Network SN
Signaling System Network Control SSNC (NSS innovation node) or Common
Channel signaling Network Control CCNC (NSS classic node) consists of:
Coordination Processor CP113C/CR
Message Buffer MB (MBD / MBC)
Central Clock Generator CCG (CCGE / CCGB)
External Memory EM
Craft Terminal CT
Authentication boxes (optionally)
In the NSS classic node, the CCNC is used together with the CCGB and the
MBB.
In the NSS innovation node, the SSNC is used together with the CCGE and the
MBD.
zoxojaka.und.slo

zoxojaka.und.slo
Fig. 45 Summary D900/1800SSS

6 PACKET SWITCHED CORE

NETWORK
6.1 Serving GPRS Support Node (SGSN)
SGSN is the most important element of the GPRS network. The SGSN of the
GPRS network is equivalent to the MSC of the GSM network. There must at least
one SGSN in a GPRS network. There is a coverage area associated with a
SGSN. As the network expands and the number of subscribers increases, there
may be more than one SGSN in a network. The SGSN has the following
functions:
Protocol conversion (for example IP to FR)
Ciphering of GPRS data between the MS and SGSN
Data compression is used to minimise the size of transmitted data units
Authentication of GPRS users
Mobility management as the subscriber moves from one area to another, and
possibly one SGSN to another.
Routing of data to the relevant GGSN when a connection to an external
network is required.
zoxojaka.und.slo
Interaction with the NSS (that is, MSC/VLR, HLR, EIR) via the SS7 network
in order to retrieve subscription information.
Collection of charging data pertaining to the use of GPRS users.
Traffic statistics collections for network management purposes.

Nokia Siemens Networks SGSN is based on modular software (SW) and

hardware (HW) architecture. All interfaces between system modules are
specified. This makes it possible to add new functions easily without changing the
overall system architecture. Thus, the Nokia Siemens Networks SGSN can have
a long operational life span and still always support functionality according to the
latest requirements.
The architectural solution of the Nokia Siemens Networks SGSN provides high
capacity with dedicated processing power for various 2G and 3G GPRS tasks
combined with carrier-class availability. The system element enables the
distribution of processing capacity to several computer units with dedicated tasks,
called functional units.
zoxojaka.und.slo
Fig. 46 DX200 SGSN layout

Each functional unit has its own, separate hardware and software, equipped with
a dedicated Pentium M processor and they use Compact PCI technology as
internal bus. These units are referred to as computer units and they are
interconnected by an Ethernet-based message bus (EMB). The EMB is used only
for exchanging signalling between units.
The Nokia Siemens Networks SGSN supports balanced packet processing and
subscriber/PDP context capacity with flexible connectivity options and capacity.
Both packet processing and subscriber capacity can be enhanced with future
upgrades. With modular software and hardware architecture it is possible to add
new functions easily without changing the overall system architecture. Thus, the
Nokia Siemens Networks SGSN can have a long operational life span and still
support the functionality according to the latest requirements.
DX200 Computing Platform has been renewed continuously in order to keep up
with the new capacity demands that have been set for it. This in practice means
that DX200 has evolved into a completely new platform when comparing to older
versions. In SG6 the nature of DX200 changes so that it becomes more a server
than a traditional switch. The internal message bus used for signalling and data
interchange between the computer units is based on fast Ethernet connections. In
addition, more powerful processors have been continuously taken into use. Older
HW versions are not required to have the message bus Ethernet-based in order
to support combined 2G/3G traffic in Nokia Siemens Networks SGSN SG6.
LAN switches were already integrated as a part of DX200 in SG5 release to
zoxojaka.und.slo
simplify connectivity towards external Ethernet switches. Even hardware releases

earlier than SG5 can be used in combined 2G/3G mode with smaller capacities.
Its modular software and hardware architecture enables integrating the 3G
functionality to complement the existing 2G functionality.
Nokia Siemens Networks SGSN is implemented as a stand-alone node. This
enables the location to always be selected most optimum from Transmission and
NMS needs and site requirements point of view. Often, especially in early stages
of GPRS implementation, SGSN can be co-located with the MSC.

Nokia Siemens Networks SGSN is implemented according to specifications thus

enabling operation in a multivendor environment. It is available for both ETSI and
ANSI environments. Functionality of ETSI and ANSI specific products is the
same; the differences are with the transmission interfaces and signalling
protocols.
Natural step towards optimisation of network transport is to use IP and Ethernet
in the Iu and Gb interfaces. IP and Ethernet are essential when taking for
example Multipoint Iu/Gb features in use in order to reduce the connectivity cost
and simplify management of the network. In Gb interface Ethernet technology is
needed to achieve full end-to-end QoS inside the GPRS network. The Nokia
Siemens Networks SGSN, which supports both 3G and 2G, is based on IP
interfaces i.e. Iu over IP and Gb over IP. Frame relay can exist for 2G
concurrently with IP and ATM for Iu.
6.1.1 Cabinet configuration

SG6 release offers two cabinet solutions: the existing one, with 2 cabinets, and
the new one-cabinet solution. The options are shown in Figure 18. Operators can
choose the one-cabinet solution (basic cabinet), and later upgrade the SGSN
adding another cabinet (extension cabinet).
zoxojaka.und.slo
Fig. 47 Rack layout of DX200 SGSN

6.2 Gateway GPRS Support Node (GGSN)

GGSN is the gateway to external networks. Every connection to a fixed external
data network has to go through a GGSN. The GGSN acts as the anchor point in
a GPRS data connection even when the subscriber moves to another SGSN
during roaming. The GGSN may accept connection request from SGSN that is in
another PLMN. Hence, the concept of coverage area does not apply to GGSN.
There are usually two or more GGSNs in a network for redundancy purposes,
and they back up each other in case of failure. The functions of a GGSN are
given below:
Routing mobile-destined packets coming from external networks to the
relevant SGSN
Routing packets originating from a mobile to the correct external network
Interfaces to external IP networks and deals with security issues
Collects charging data and traffic statistics
Allocates dynamic or static IP addresses to mobiles either by itself or with the
help of a DHCP or a RADIUS server
Involved in the establishment of tunnels with the SGSN and with other
external networks and VPN.
From the external network's point of view, the GGSN is simply a router to an IP
sub-network. This is shown below. When the GGSN receives data addressed to a
specific user in the mobile network, it first checks if the address is active. If it is,
zoxojaka.und.slo
the GGSN forwards the data to the SGSN serving the mobile. If the address is
inactive, the data is discarded. The GGSN also routes mobile originated packets
to the correct external network.

Fig. 48 GPRS network as seen by another data network
6.3 Operation System Support

6.3.1 NetAct
In the preceding section we have already discussed the main functions of the
Network Management Subsystem. Here we see the actual implementation of it.
The raw data from the GSM network is transferred to the NetAct via a router and
a Data Communications Network (DCN).
zoxojaka.und.slo
Fig. 49 NSN NetAct architecture

Functional units in the NetAct

The standard NSN NetAct consists of servers and operator positions that can be
either application workstations or X terminals. These components are connected
to a Local Area Network (LAN). Servers are also provided and consist of a
communications server, a database server and a standby server or combinations
of these. A router is provided to allow communication to the various elements in
the GSM network, which is connected to a Data Communication network (DCN).
zoxojaka.und.slo
Fig. 50 NetAct connections to GSM network elements

Evolution of NSNs Network Management System the NSN

NetAct Solution
The NSN solution for supporting the operation of a network evolves with the
introduction of the NSN NetAct Solution. The structure of the solution is not built
round the technology but the functions and processes that an operator must
perform to ensure the operation of the business.
NSN has launched NSN NetAct Framework in order to support the transition from
2G to 3G. It also extends the multivendor integration capability of the Network
Management System (NMS).
NetAct provides a full-scale management capability for both packet data and
traditional voice traffic, independent of technology. Thanks to this, it is possible to
deploy new technologies with the same system that manages the current
infrastructure.
The next figure illustrates the different functions that NetAct supports. All the
functions are brought together in a common framework and are connected to the
physical network elements through a UMA (Unified Mediation and Adaptation)
object, which allows NetAct to talk to NSN elements and 3rd party systems.
zoxojaka.und.slo
Fig. 51 NSN NetAct Framework

7 Other Products
7.1 Location based functions
Location-based applications are the next major class of value-added services that
mobile network operators can offer their subscribers. The NSN intelligent
Gateway Mobile Location Center (iGMLC) is designed to provide the positioning
functions necessary for these services. This kind of functionality is sometimes
called interrogations server since the system interrogates the network and MS to
determine a users location. This server .. provides the location information to
higher layer applications which are the actual location based services.
GSM Location Based Services provide personalised services to the subscriber
based on their current position.
7.1.1 Basic positioning

Basic positioning methods are based on the knowledge of the cell the subscriber
is using (cell ID). This can be used alone, or together with other information
available in the network such as timing advance (TA) and network measurement
reports (NMR). This information is available for all handsets used in GSM/GRPS.
zoxojaka.und.slo
Advanced techniques will be available in new handsets such as Enhanced

Observed Time Difference (E-OTD) and Assisted GPS (A-GPS) which uses the
GSM network to help the reception of the freely available GPS system.
The division of position technologies above is based on accuracy of the
positioning method. Other factors, also very important are for example complexity
of the system, availability of the positioning technology in the network (e.g.
A-GPS may not be available everywhere) and the investment needed on the
network side and in handsets.

7.1.2 Enhanced Observed Time Difference

Enhanced Observed Time Difference is based on measuring the time difference
of downlink synchronisation burst arrival. An MS is constantly aware of multiple
surrounding base-stations and the run time difference to these base stations can
be measured. Mobile Stations are by default aware of surrounding cells but the
E-OTD is an extension of the normal synchronisation function. To make the
E-OTD fully functional an additional, Location Measurement Unit is used to further
enhance the accuracy. The LMU has a known position and can thus serve as
reference. The process requires considerable computing power, however, this
can be located in network server. The accuracy of E-OTD is 50-125 meters and
the response time is approximately 5 seconds.
7.1.3 Assisted GPS

Assisted GPS is a system where outside sources, such as an assistance server
and reference network, help a GPS receiver to perform the tasks required to
make range measurements and position solutions. The assistance server has the
ability to access information from the reference network and also has more
computing power than the GPS receiver. The assistance server communicates
with the GPS receiver via a wireless link. With assistance from the network, the
receiver can operate more quickly and efficiently than it would unassisted, since a
set of tasks that would normally be handled by the handset are shared with the
zoxojaka.und.slo
assistance server. The resulting AGPS system, consisting of the integrated GPS
receiver and network components, creates performance beyond that of the same
receiver in a stand-alone mode.

7.2 Operation & Maintenance O&M

O&M of the BSS and NSS network elements can be done locally, i.e. at the site
of the particular node, and centralized.
7.2.1 Local O&M

For local O&M in the BSS Local Maintenance Terminals LMT (portable PCs) are
used. LMTs can be connected via proprietary T-Interface to BSC, BTSE and
TRAU. For local O&M in the NSS Craft Terminals CT (commercial Windows NT
PCs) are used.
7.2.2 Centralized O&M: OMS

Remote, centralized O&M is done in the Operation & Maintenance Subsystem
OMS. The OMS is split up into OMC-B (Operation & Maintenance Center for the
BSS), OMC-S (OMC for the NSS) OMC-S for the NSS classical nodes (including
the CCNC) and SC (Switch Commander) for the NSS innovation nodes (including
the SSNC).
SC and OMC-B are used for GPRS network elements / enhancements, too.
OMC-S and OMC-B are connected via PSDN (X.25) to the NSS / BSS network
elements.
zoxojaka.und.slo
The OMC-B is always linked to the BSCs of the BSS. The link between BSC and
OMC-B is realized either via dedicated X.25 (64 kbit/s) lines or via MSC PCM30
links (nailed-up connections NUC).
The SC is connected either via PSDN (X.25) or via LAN (Q3) with TCP/IP
protocol to the NSS nodes.

7.2.3 SC / OMC-B: Network Components

Central components of the SC are Craft Terminals CT and the SC Servers.
Central components of the OMC-B are the O&M Terminals OMT and O&N
Processor OMP Server.
CTs / OMTs and the SC Servers / OMP Servers are connected to LANs in the
OMC.
The CTs and SC Servers are commercial computers (Windows NT PCs /
Windows NT Servers). The SC is a highly scalable system and can be configured
from a single workplace system to 40 communication servers and 300 clients
using a 100 Mbit/s LAN.
The OMP Servers are commercially computer (SUN Sparc/Enterprise), the OMTs
SUN graphical workstations WS or X-Terminals X-Ts (SUN Sparc classic X). Up
to 8 WS or X-Ts with an X-T Server are connected in an OMC-B to the OMP
Server (optionally duplicated) via LAN.
zoxojaka.und.slo
Fig. 52 Network Components

7.2.4 Central Functions

The OMC-B includes the following central functions required for centralized O&M
of the BSS network elements and the OMC-B itself:
Configuration Management CM: The task of configuration management is
administration of network resources, i.e. administration of network changes,
support of installation and recovery action, provision and display of status
information.
Software Management SWM: Software can be downloaded from the OMC-B
to the BSS network entities (First SW installation, Patch handling, SW
changes & upgrades).
Test Management TM: Operator-controlled tests are available to verify proper
working of managed objects. Diagnostics are very important for the process
of fault treatment and restoration of repaired units.
Fault Management FM: FM includes all measures required to detect and
repair faults (down to a single module) in the PLMN.
Performance Management PM: Monitoring the traffic load and network
performance. Short- & long-term traffic, performance and quality-of-service
measurements are recorded and made available.
Security Management SM: Access protection mechanism.
zoxojaka.und.slo

The Switch Commander software includes basic system and application

software functions.
The basic system includes the following parts: installation, recovery, central
functions, which allow general access to utilities, LAN & WAN communication, file
transfer functions to the network elements of the NSS.
The application software includes basic applications and NSS applications. Basic
applications are security management SM, user interface, computer & database
structure, facilities for interworking the CT to the SC.
NSS applications include configuration management CM, fault & maintenance
management, performance management PM, accounting management and
automated patch supply (autopatch).
zoxojaka.und.slo
Fig. 53 OMC-B

Module 8 - NSN Product Solution For GSM

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Module 8 - NSN Product Solution For GSM

Hochgeladen von

Copyright:

Verfügbare Formate

NSN Product Solution for GSM

NSN Product Solution for

3.2 NSN Base Station Controller (BSC) Products.......................................... 18

Nokia Siemens Networks 2008 1-1

1-2 Nokia Siemens Networks 2008

2 Nokia Siemens Networks-

Fig. 1 GSM network architecture NSN implementation

Nokia Siemens Networks 2008 1-3

3.1 NSN BTS

NSN BTS families

NSN DE21/DF12 BTS

1-4 Nokia Siemens Networks 2008

Fig. 2 NSN 2nd generation BTS (DE21/DF12)

NSN Talk Family BTSs (DE/DF34)

Fig. 3 NSN Talk Family of BTSs

Nokia Siemens Networks 2008 1-5

3.1.1 NSN MetroSite

Fig. 4 NSN MetroSite

It is possible to chain up to three MetroSite cabinets in the same physical site,

1-6 Nokia Siemens Networks 2008

3.1.2 NSN UltraSite

Fig. 5 NSN UltraSite

Nokia Siemens Networks 2008 1-7

1-8 Nokia Siemens Networks 2008

Fig. 7 NSN UltraSite flexibility

Nokia Siemens Networks 2008 1-9

3.1.3 NSN FlexiEDGE BTS

Fig. 8 Flexi EDGE BTS

1-10 Nokia Siemens Networks 2008

BTSE-One Family & BTS-Plus Family

Nokia Siemens Networks 2008 1-11

3.1.4 BS240: Units & Modules

1-12 Nokia Siemens Networks 2008

Core Modules: COBA & COSA

Core Basis COBA2P8

Fig. 10 BS 250: Units and modules

Nokia Siemens Networks 2008 1-13

Core Satellite COSA6P16

Antenna Combiner (ACOM) / Multi Coppler (MUCO)

Duplexer Amplifier Multi Coupler (DUAMCO)

DI(=2) Amplifier MultiCoupler (DIAMCO)

1-14 Nokia Siemens Networks 2008

Fig. 11 BS 240 Modules

Alarm Collector Terminal (ACT)

Tower Mounted Amplifier (TMA)

Carrier Unit (CU)

Nokia Siemens Networks 2008 1-15

1-16 Nokia Siemens Networks 2008

Fig. 12 Carrier Unit (CU)

Nokia Siemens Networks 2008 1-17

3.2 NSN Base Station Controller (BSC)

Fig. 13 DX 200 BSC (second generation) architecture

1-18 Nokia Siemens Networks 2008

3.2.2 Functional units in the DX 200 BSC

Nokia Siemens Networks 2008 1-19

Fig. 14 Two Cabinet Configuration BSC3i 2000

1-20 Nokia Siemens Networks 2008

3.2.3 NSN BSC 120

Nokia Siemens Networks 2008 1-21

1-22 Nokia Siemens Networks 2008

3.2.3.1 BSC: Link Configuration

Nokia Siemens Networks 2008 1-23

3.2.3.2 BSC Capacity