Vous êtes sur la page 1sur 27

Radio Access System Overview

RU10 Release

Nokia Siemens Networks

<LE number and name>

Nokia Siemens Networks Academy


Legal notice Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.

Nokia Siemens Networks

<LE number and name>

Document change history


Date 14.04.2009 Version 1.0 Name Suriansyah Change comment Draft Updated to RU10

Nokia Siemens Networks

<LE number and name>

Content

RAN Architecture and Interfaces RAN Functionalities NSN RAN Roadmaps NSN RAN Solution RAN Operation and Management

Nokia Siemens Networks

<LE number and name>

UMTS Generic Architecture


CN
VLR

GERAN

MSS

Um BT S BSC A

MGW Nb Mc Abis A

Nc

PSTN MGW Mc PSTN PSTN GMSS

VLR

PSTN PSTN

Nc PSTN

BSS UTRAN
Uu IuCS Iur IuCS Gb

MSS F Gs EIR Gf Gr Gn HSS Gc Go Gi GGSN D C

CS-Domain

IMS IMS
PDN/ PDN/ Internet Internet Other Other PLMN PLMN

SIM Iub

IuPS Gp RNC Node B SGSN

UE
Cu USIM

RNS

BG

PS-Domain

Nokia Siemens Networks

<LE number and name>

The general idea in UMTS is to harmonise the CN with GSM/GPRS as much as possible. This can be done since there is no major difference in how subscribers or charging are handled in both systems. Therefore, CN is constituted of a Circuit Switched (CS) domain and a Packet Switched (PS) domain which have the same main elements as is GSM/GPRS beside the CN common elements. The biggest change is in the UMTS Radio Access Network that introduces several new functions and a totally new air interface. The Radio Access Network is controlled by a Radio Network Controller (RNC), unlike the Base Station Controller (BSC) in a GSM network. In the 3GPP specification, the WCDMA BTS is referred to as Node B.

RAN Architecture and Interfaces


NetAct MSS/MGW SGSN A-GPS Server

O&M

Iu-CS

Iu-PS

ADIF*

CBC Iu-BC Iub Node B

RNC Iur

RNC Iu-PC RNS

SAS

Uu * Proprietary interface

UE
6 Nokia Siemens Networks <LE number and name>

WCDMA Radio Access Network (WCDMA RAN) WCDMA RAN consists of one or more Radio Network Subsystem (RNS) where each RNS is constructed by a Radio Network Controller (RNC) and its controlled Node Bs. The main function of WCDMA RAN is handling all radio-related functionalities and managing radio resources in a 3G network. In addition, WCDMA RAN also handles telecommunication management for Circuit-switched and Packet-Switched traffic in a 3G network. The standardised interface between RNCs is called Iur, and interface RNC Node Bs is called Iub. Core Network Core Network (CN) is responsible for routing calls, data connections or other defined services to external network as well as handling user mobility. RAN interface toward Switching Core Network (SCN) is called Iu-CS, and it is implemented by connecting RNC to MSC Server (MSS) for control plane and to Multimedia Gateway (MGW) for user plane. RAN interface toward Packet Core Network (PCN) is called Iu-PS, and it is implemented by connecting RNC to Serving GPRS Support Node (SGSN). RAN interface toward Cell Broadcast Center (CBC), for Cell Broadcast Service (CBS), is called Iu-BC. RAN interface toward Positioning Center (PC), for Location Service (LCS), is called Iu-PC. It is implemented by connecting RNC to Standalone SMLC (SAS). NSN also provides alternative solution for LCS, which is implemented by connecting RNC directly to A-GPS server. For this solution, the position calculation is done by RNC. The proprietary interface toward A-GPS server is called A-GPS Data Interface (ADIF)

RAN Architecture and Interfaces


NetAct MSS/MGW SGSN A-GPS Server

O&M

Iu-CS

Iu-PS

ADIF*

CBC Iu-BC Iub Node B

RNC Iur

RNC Iu-PC RNS

SAS

Uu * Proprietary interface

UE
7 Nokia Siemens Networks <LE number and name>

Operation Support System Operations Support System (OSS) is common for both 2G and 3G networks. The same management system is used for managing both the network and the services provided. In the NSN 3G solution, NetAct Framework is used for this task. The O&M interface toward OSS, called Network Interface for 3rd Generation Network (NWI3), is a CORBA based interface.

RAN Functionalities

8

3GPP TS 25.401

Transfer user data Functions related to overall system access control Radio channel ciphering and deciphering Functions related to mobility Functions related to radio resource management and control Synchronisation Functions related to broadcast/multicast services Tracing Volume reporting RAN information Management Functions related to MBMS
Nokia Siemens Networks <LE number and name>

The following are RAN functionalities defined in 3GPP specification number TS 25.401. RAN may have more functions in newer release. 1. Transfer user data. This function provides user data transfer capability across the UTRAN between the Iu and Uu reference points. 2. Functions related to overall system access control (e.g. admission control, congestion control, system information broadcasting, etc.) 3. Radio channel ciphering and deciphering. This function is a pure computation function whereby the radio transmitted data can be protected against a nonauthorised third-party. 4. Functions related to mobility (e.g. handover, SRNC relocation, positioning, NAS node selection function, shared network access control, etc.) 5. Functions related to radio resource management and control 6. Synchronisation 7. Functions related to broadcast/multicast services 8. Tracing. This function allows tracing of various events related to the UE and its activities. 9. Volume reporting. This function is used to report the volume of unacknowledged data to the CN for accounting purpose. 10. RAN information Management. This function is a generic mechanism that allows the request and transfer of information between two RAN nodes. 11. Functions related to MBMS

Rel.7 Packet Switched Network


Common Service Platforms
BSC LIG

Common Network Management


CG Customer Billing Network Firewall Data Network (internet) GGSN

2G RAN IP backbone DNS BG 3G RAN

Corporate customer network Mobile ISP

RNC

SGSN (combi)

Common Packet Core Infrastructure

Inter-PLMN Network

Nokia Siemens Networks

<LE number and name>

Radio Access Network access the PS Core network through SGSN. With the introduction of Combi SGSN, both 2G and 3G RAN are connected to the same network element in the PS Core Network. The implementation of Iu-PS over IP in RU10 allows the RNC to be directly connected to IP backbone.

Functionalities Split Between Network Elements


Functionality Authentication Interaction with HLR, MSC/VLR Charging and Statistics Interface toward OSS GTP Tunnelling Radio Protocol to IP conversion Ciphering Compression Mobility Management High Capacity Routing IP Telephony Real-time Multimedia
* in case of 2G RAN ** URA concept
10 Nokia Siemens Networks <LE number and name>

SGSN X X X X X X* X* X* X X X X

RNC

BSC

X X X X X X** X X X

Some functionalities in handling packet data traffic are shifted from SGSN to RNC, e.g. Radio Protocol to IP conversion, Ciphering and Compression. Another packet data handling function, i.e. GTP tunnelling is implemented between RNC SGSN, besides SGSN GGSN. The ciphering is done in RLC layer of radio interface protocol, while IP packet compression is handled by PDCP layer. The RAN also has mobility concept which is implemented by UTRAN Registration Area (URA) to support packet data operation.

Radio Resource Management


Cell Capacity Optimization and Tailoring

CRNC functions Admission Control Load Control


Cell Coverage Service Quality

Resource Manager
Node B Iub DRNC

Power Control, packet scheduler

Power Control, packet scheduler


UE

Iur

SRNC functions
Iub Node B SRNC

Packet Scheduler Power Control Handover Control

11

Nokia Siemens Networks

<LE number and name>

The goal of Radio Resource Management (RRM) is to ensure that the radio network capacity is used as efficiently as possible, i.e. radio access network offers high capacity, maintains the planned coverage area and the required quality of service. In WCDMA, the radio resources are defined in terms of transmission power, received wideband power, logical codes, BTS HW, Iub/Iur transport, and RNC HW. To achieve the goal, RRM algorithms are implemented on the RAN Network Elements. They are: Cell-based algorithms, i.e. Admission Control (AC), Packet Scheduler (PS), Load Control (LC) and Resource Manager (RM). Connection-based algorithms, i.e. Power Control (PC) and Handover Control (HC)

In case of HSPA connection, the packet scheduler is shifted to Node B

NSN RAN 3G Roadmap


04/2009 2007
Ready for Contract

Q1/2010 2008
Under Planning

Q1/2011 2009
Study Items

Q1/2012 2010
Research Items

RU10

RU20

RU30

RU40

HSDPA 14 Mbps All-IP Connectivity Flat Architecture Quality of Service LTE- ready Flexi BTS 2.8 Gbps RNC

HSPA+ Release HSDPA 28 Mbps HSUPA 11.5 Mbps CS-voice over HSPA Adv. FDE Receiver Flexi Multiradio BTS 3.5 Gbps RNC
HSDPA 21 Mbps (64QAM) HSUPA 5.8 Mbps Flexible RLC in DL Continuous Packet Connectivity MBMS Broadcast High Speed Cell_FACH (DL) HSPA Conversational QoS Synchronous Ethernet Concurrent Mode Multiradio BTS

HSPA+ Release HSDPA 84 Mbps HSUPA 23 Mbps <100ms call set-up LTE Interworking Gigabit Flexi BTS 35 Gbps RNC Evolution
HSDPA 42 Mbps (Dual-Cell HSDPA / 64QAM + MIMO) High Speed Cell_FACH (UL) Flexible RLC in UL

HSPA+ Release Higher Bit Rates Multi-carrier HSPA Active Antenna System 2ms TTI UL Range Extension Local Break-Out
Fast Inter-System Handover Multi-Band HSDPA Aggregation Self Optimising Backhaul

HSPA Streaming QoS HSPA Multi NRT RABs Common Iub

I-HSPA Rel.1 Rel.2


CS Enabling Handover BTS Sharing

I-HSPA Rel.4 3G Femto Rel.3

I-HSPA Rel.5 3G Femto Rel.4

3G Femto Rel.1 I-HSPA Rel.3 3G Femto Rel.2

12

Nokia Siemens Networks

<LE number and name>

The key drivers of NSN WCDMA/HSPA evolution are: Best user experience with the leading HSPA capability and evolution e.g. 40% lower latency, real service differentiation (QoS) and extended terminal battery use time Lowest Total Cost of Ownership (TCO). Typically 20-30% less sites and less site cost with Flexi BTS. Flexi BTS SW upgradeable radio, baseband, and transport reduces site visits 50-90%. Most cost efficient RNC and unique Flat Architecture option with I-HSPA data network. Leading WCDMA 900MHz refarming solution with unique 4.2MHz carrier bandwidth and with faster and more accurate planning with NetAct Optimizer. Greenest 3G network with lowest power consumption and typically 70% lower CO2 emissions Shortest time to revenue with Flexi BTS true SW upgradeability.

All-IP Connectivity Solution in RU10


Iur Control Plane RNSAP Iur User Plane FP Layer RTP RTCP UDP IP Ethernet Iu-CS Control Plane RANAP SCCP M3UA SCTP IP Ethernet Iu-CS User Plane Iu User Plane RTP UDP RTCP

Provides 3GPP compliant


IPv4 transport option for all RNC interfaces Allows to use IP and/or Ethernet connectivity from RNC towards to core networks (Iu-CS and Iu-PCS), other RNCs (Iur) and base stations (Iub) New features available are: Gigabit Ethernet Interfaces (optical
and electrical) IP based Iu-PS, IP based Iu-CS IP based Iur

SCCP M3UA SCTP

RNC
Iur/IP Iu-CS/IP

Iur/IP Iu-CS/IP

3G BTS

MGW

Iub/IP

RNC

Iu-PS/IP

3G BTS
Iu-PS Control Plane RANAP Iub Control Plane NBAP SCTP IP Ethernet Ethernet Iu-PS/IP Iub User Plane FP Layer UDP SCCP M3UA SCTP IP

SGSN
Iu-PS User Plane Iu User Plane GTP-U UDP

IP based Iub

Iub/IP

13

Nokia Siemens Networks

<LE number and name>

C-Iub: S-NB Operability in N-RNC


This feature defines the basic
O&M functions in the common NBAP interface
BTS initialization BTS logical resource management BTS and RNC recovery

Iub

NB/RSxxx

RNC

14

Nokia Siemens Networks

<LE number and name>

PS RAB Reconfiguration
PS RAB parameters can be
RNC UE BTS Core network

RAB Assignment Request

RAB Assignment Response

reconfigured. It allows the deployment of single APN and UEs. The usage of network resources is optimized when the QoS parameters in the network are aligned with the QoS requirements of the service.

RAB parameters
Traffic class Maximum bit rate THP ARP Upgraded or downgraded Interactive to background or vice versa

15

Nokia Siemens Networks

<LE number and name>

SGSN or UE can request the RAB reconfiguration procedure if there is a need to modify the characteristics of a RAB service. To the RAN the reconfiguration is triggered by the CN with a RAB Setup message requesting reconfiguration of the existing RAB. The following RAB parameters can be changed for the interactive and background traffic class RABs: Traffic class interactive <-> background Maximum bit rate (UL/DL) Change of Traffic Handling Priority (THP) of an interactive RAB Change of Allocation and Retention Priority (ARP) RNC reconfigures the RNC and BTS with the new RAB/SPI parameters after receiving the RAB reconfiguration request from CN.

HSPA Solution
HSDPA 64 users / cell HSUPA 60 users / bts

64 users

64 users

64 users

64 users

60 users

16

Nokia Siemens Networks

<LE number and name>

I-HSPA Architecture and Interface



3GPP open air interface
Uu

I-HSPA is a simplified flat architecture network Standard 3GPP packet core RNC HSPA functionality integrated to Node B Standard 3GPP HSPA terminal

3GPP open network interface


Iu-ps C Direct Tunnel SGSN C-plane Iur C
C ps Iu-

Gn U

U-plane Gn C GGSN

Gn U

3GPP Rel5 or later HSPA terminal

17

Nokia Siemens Networks

<LE number and name>

I-HSPA is part of 3GPP R7 HSPA Evolution Work Item. It specifies Flat PaCo: Direct Tunnel defined in SA WG2, for removing SGSN from the U-plane Flat RAN: HSPA Evolution TR25.999 defines BTS collapsed RNC RNC ID extension from 4096 to a higher value to allow large I-HSPA network

NSN Radio Access Solution


NSN provides Radio Access solution: Radio Network Controller (RNC) Base Station Transmission and Transport Solution RAN Operation and Management

18

Nokia Siemens Networks

<LE number and name>

19
1 1 1 1
NIP1 2

NIP1 0 SFU 1

SFU 0

2 2 2

NIP1 3

NIP1 1

3 3 3

ICSU

ICSU

NIS1P 5 NIS1P 4

4 4 4

ICSU NIS1P 7

ICSU
NIS1P 6

5 5 5
ICSU
NISx 1 NISx 0

ICSU

6 6 6
DMCU Optional ESA24 A2SU

CPD80-B 0

DMCU

7 7 7
DMCU
ICSU ICSU RRMU 1 RRMU 0

RNC196 CS1-5

DMCU

8 8 8
DMCU RSMU 1 MXU 1 PD20 FDU (O MU) EHU ESA24 / ESA24 ESA12 NEMU
HDD 0 (NEMU)

RRMU removed. Release plug-in unit configured as ICSU.


DMCU RSMU 0 MXU 0 PD20 MXU 4
PD20

NSN Radio Network Controller

Feature upgrade configuration steps in RN4.0 are:

Basic new delivery configuration steps in RN4.0 are:

MXU 2 PD20 MXU 3 DMCU DMCU DMCU


HDD 1 (NEMU)

MXU 5 DMCU DMCU DMCU


A2SU ICSU GTPU NISx 3 NISx 2 GT PU -

CPD80-B 1
A2SU OMU 1 WDU 1 ( OMU) WDU 0 (O MU) OMU 0

9 10 11 12 13 14 15 16 17 18 19 9 10 11 12 13 14 15 16 17 18 19 9 10 11 12 13 14 15 16 17 18 19 9 10 11 12 13 14 15 16 17 18 19

RNC196

38 38 38
TBUF TBUF TSS3

38

TBUF

TBUF

TBUF T BUF

TSS3

4
1 1 1 1

NIP1 10 NIP1 8 NIP1 4 NIP1 6

2 2 2 2

NIP1 11 NIP1 5

NIP1 9

NIP1 7

3 3 3 3
ICSU ICSU

ICSU ICSU

4 4 4 4
ICSU ICSU

ICSU ICSU

5 5 5 5
ICSU ICSU ICSU

ICSU

6 6 6 6
DMCU DMCU DMCU

CPD80-B 0

DMCU

7 7 7 7
DMCU DMCU DMCU

DMCU

8 8 8 8
DMCU DMCU MXU 6 PD20 MXU 7 DMCU DMCU DMCU A2SU GT PU DMCU DMCU MXU 8 PD20 MXU 9 DMCU DMCU DMCU A2SU GTPU DMCU DMCU DMCU MXU 10 PD20 MXU 11 DMCU DMCU DMCU A2SU GT PU DMCU DMCU

DMCU MXU 12 PD20 MXU 13 DMCU DMCU DMCU A2SU GTPU DMCU DMCU

CPD80-B 1

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

38 38 38 38
TBUF T BUF TBUF T BUF TBUF TBUF TBUF TBUF

Nokia Siemens Networks


2 1 4
1 1 1 1
O ptional NIP1 0

SFU 1 SFU 0

2 2 2 2
DMCU 34

DMCU 42

3 3 3 3
NPGEP 0

ICSU ICSU NPG EP 1

NISx 5 DMCU NIS1P 5 26


DMCU 4 NIS1P NISx 4 18

4 4 4 4
DMCU 6 NIS1P NISx 6 19 NPGEP 2

ICSU ICSU DMCU NISx 7 7 27 NIS1P NPG EP 3

5 5 5 5
NISx 0 7 A2SU NPS1P 2 NISx 1 8 A2SU NPS1P 3 ICSU

ICSU

6 6 6 6
DMCU

CPD80-B 0

DMCU

Optional ESA24
A2SU

7 7 7 7
ICSU ICSU RRMU 0 DMCU RRMU 1

RNC196 CS1-5 CS6-7

DMCU

8 8 8 8
DMCU MXU 2 PD20 MXU 3 DMCU DMCU EHU B: HDD 1 (NEMU) HDD 1 (NEMU) A: WDU 1 (OMU) A: W DU 0 ( OMU) B: HDD 0 (NEMU) HDD 0 ( NEMU) DMCU A2SU NIS1P 0 GTPU NISx 2 ICSU 21 NPGEP 4 ICSU 19 ICSU GTPU 6 ESA24 ESA12 / ESA24 MXU (15 FDU OMU) MXU EHU 1 14 MXU 1

DMCU MXU 4 PD20 MXU 5 DMCU DMCU DMCU A2SU NIS1P 1 GTPU NISx 3 NPG EP 5 ICSU

RSMU 1 RSMU 0

MXU 0
PD20

PD20

RRMU removed. Release plug-in unit configured as ICSU.

CPD80-B 1

NEMU

OMU 1 OMU 0 WDU 6 ( OMU) ICSU 0 WDU 1 (OMU) ICSU 20

38

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

RNC196/300

38 38 38
TBUF TBUF T SS3
TBUF TBUF TBUF TBUF TSS3

4
1 1 1 1
-

2 2 2 2
DMCU 25 DMCU 35

DMCU 43

3 3 3 3

ICSU

ICSU

ICSU

ICSU

4 4 4 4

ICSU ICSU ICSU ICSU

5 5 5 5
ICSU ICSU

ICSU ICSU

6 6 6 6
DMCU DMCU

CPD80-B 0

DMCU DMCU

7 7 7 7
DMCU DMCU DMCU

DMCU

8 8 8 8
DMCU DMCU MXU 6 PD20 MXU 7 DMCU DMCU DMCU A2SU G TPU NIS1P 4 NIS1P 6 ICSU MXU 8 PD20 MXU 9 DMCU DMCU GTPU 7 A2SU GTPU NIS1P 5 NIS1P 7 ICSU DMCU MXU 10 PD20 MXU 11 DMCU DMCU DMCU A2SU GTPU NIS1P 8 NIS1P 10 ICSU

DMCU MXU 12 PD20 MXU 13 DMCU DMCU DMCU A2SU GTPU NIS1P 9 NIS1P 11 ICSU

CPD80-B 1

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

38 38 38 38
TBUF TBUF TBUF TBUF TBUF TBUF TBUF TBUF

<LE number and name>


2 1 4
1 1 1
O ptional NIP1 0 SFU 1 SFU 0

2 2 2
DMCU 34

DMCU 42

3 3 3

ICSU ICSU NIS1P 5 26 NISx 5 DMCU NPG EP 1

NIS1P NISx 4 18 DMCU 4 NIS1P NISx 6 19 DMCU 6 A2SU NISx 0 7 A2SU RRMU 0 RSMU 0 MXU 0 PD20 EHU 1 MXU

NPGEP 0 NPGEP 2 NPS1P 2

4 4 4

ICSU ICSU NIS1P NISx 7 7 27 DMCU NPG EP 3

5 5 5
A2SU1 8 NISx NPS1P 3

ICSU ICSU

6 6 6
Optional ESA24

CPD80-B 0

DMCU DMCU

7 7 7
ICSU

RNC196 CS1-5 CS6-7

DMCU DMCU

RRMU 1

ICSU

8 8

DMCU DMCU MXU 2 PD20 MXU 3 DMCU DMCU DMCU A2SU NIS1P 0 GTPU NISx 2 NPGEP 4 ICSU A: WDU OMU 1 ICSU 20 (OMU) WDU 1 ICSU 21 EHU 1 (NEMU) B: HDD1 (NEMU) HDD 1 (OMU) GTPU 6 MXU (15 FDU OMU) PD20 1 MXU 14 MXU 4 PD20 MXU 5 DMCU DMCU DMCU A2SU NIS1P 1 GTPU NISx 3 NPG EP 5 ICSU

RSMU 1

ESA24 ESA12 / ESA24 NEMU B: HDD NEMU) HDD 0 ( 0 (NEMU) A: W DU 0 ( OMU) OMU 0 WDU 0 ICSU 6 ( OMU) ICSU 19

RRMU removed. Release plug-in unit configured as ICSU. 9 10 11 12 13 14 15 16 17 18 19 9 10 11 12 13 14 15 16 17 18 19 9 10 11 12 13 14 15 16 17 18 19 38 38 38


TBUF TBUF TBUF TBUF

CPD80-B 1

9 10 11 12 13 14 15 16 17 18 19

38

TSS3

TBUF

TBUF

T SS3

4
1
DMCU 35 ICSU ICSU ICSU DMCU DMCU DMCU MXU 10 PD20 MXU 11 DMCU DMCU DMCU A2SU GTPU NIS1P 8 NIS1P 10 ICSU

3
1
-

2
1
-

1
1

DMCU 43

DMCU 25

ICSU

ICSU

ICSU

ICSU

ICSU

ICSU

ICSU

ICSU

ICSU

CPD80-B 0

DMCU

DMCU

DMCU

DMCU

DMCU

DMCU

DMCU MXU 12 PD20 MXU 13 DMCU DMCU DMCU A2SU GTPU ICSU NIS1P 9 NIS1P 11

DMCU MXU 8 PD20 MXU 9 DMCU DMCU GTPU 7 A2SU GTPU NIS1P 5 NIS1P 7 ICSU

DMCU MXU 6 PD20 MXU 7 DMCU DMCU DMCU A2SU G TPU NIS1P 4 NIS1P 6 ICSU

RNC196/450
CPD80-B 1

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

9 10 11 12 13 14 15 16 17 18 19

38
TBUF

38

38

38

RNC2600/900, configuration for capacity step 1


TBUF TBUF TBUF TBUF TBUF TBUF TBUF

RNC2600/1450 ,configuration for capacity step 2


1 1 1 1

RNC2600/2000, configuration for capacity step 3


DMCU DMCU ICSU ICSU ICSU DMCU DMCU DMCU MXU 6 PD30 MXU 7 A2SU DMCU DMCU NIS1P / NIS1 5 GTPU NIS1P / NIS1 1 NIS1P / NIS1 3
38

DMCU
2 3 4 5 6 7 8 9

SFU 1
2

SFU 0
2

DMCU ICSU ICSU ICSU DMCU DMCU DMCU MXU 4 PD30 MXU 5 A2SU DMCU DMCU
NIS1P / NIS1 4 / (Opt. NIP1)

3 4 5 6 7 8 9

DMCU DMCU Optional ESA24 GTPU RRMU 1 RSMU 1 MXU 2 PD30 MXU 3 A2SU A: WDU 1 OMU B: HDD 1 NEMU EHU
16 16

DMCU
4 5 6 7

DMCU ESA24 OMS ICSU RRMU 0


8 9

5 6 7

ICSU RSMU 0 MXU 0 PD30 MXU 1 A2SU A2SU A: W DU 0 OMU B: HDD 0 NEMU
16 10 11 12 13 14 15 10 11 12 13 14 15 10 11 12 13 14 15

RNAC

8 9

RRMU removed. Release plug-in unit configured as ICSU.

10 11 12 13 14 15 16

G TPU NIS1P / NIS1 0 NIS1P / NIS1 2


38

OMU 1 ICSU ICSU


38

OMU 0 ICSU ICSU


38 17 18 19 17 18 19 17 18 19

RNC196/196 configuration for RNC196 capacity step 1-5

RNC450/450 configuration for RNC450 capacity step 3


17 18 19

RNC450/300 configuration for RNC450 capacity step 2


TBUF TBUF T BUF TBUF TSS3 TBUF TBUF TSS3

RNC450/150 configuration for RNC450 capacity step 1


4 3 2 1
1 1 1 1

RNC196/450 configuration for RNC196 capacity step 7


DMCU ICSU ICSU ICSU DMCU DMCU DMCU MXU 14 PD30 MXU 15 A2SU DMCU DMCU DMCU GTPU NIS1P 9 NIS1P 11
38

RNC196/300 configuration for RNC196 capacity step 6


2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

DMCU ICSU ICSU ICSU DMCU DMCU DMCU MXU 12 PD30 MXU 13 A2SU DMCU DMCU DMCU G TPU NIS1P / NIS1 8 NIS1P / NIS1 TBUF TBUF T BUF 10 TBUF

DMCU
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

DMCU
3

ICSU ICSU ICSU DMCU DMCU MXU 10 PD30 MXU 11 A2SU DMCU DMCU GT PU G TPU NIS1P 5 NIS1P 7 T BUF TBUF

ICSU
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

ICSU ICSU DMCU DMCU DMCU MXU 8 PD30 MXU 9 A2SU DMCU DMCU DMCU GT PU NIS1P / NIS1 NIS1P / NIS1 TBUF 4 6 TBUF

RNC450

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNBC

4
1

3
1

2
1

1
1

ICSU 8 ICSU 9 ICSU 10 ICSU 11 ICSU 12 D MCU 13 D MCU 14 D MCU 15 MXU 6 PD30 MXU 7 D MCU 16 D MCU 17 ICSU 13 N PS1(P)/ NPGE(P) 3 N PS1(P) / NPGE(P) 5
38 38

ICSU 3
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

SFU 1
2

SFU 0
2

ICSU 4 ICSU 5 ICSU 6 EHU DMCU 8 DMCU 9 DMCU 10 MXU 4 PD30 MXU 5 DMCU 11 DMCU 12 ICSU 7 NPS1( P)/ NPGE(P) 2 NPS1( P)/ NPGE(P) 4

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

ICSU 1 RSMU 1 SWU 1 ICSU 2 DMCU 4 DMCU 5 MXU 2 PD30 MXU 3 DMCU 6 DMCU 7 A: WDU 1 (OMU) B: HDD 1 (OMS) OMU 1 NPS1(P)/ NPGE(P) 1

ICSU 0
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

RSMU 0 SWU 0 OMS DMCU 0 DMCU 1 MXU 0 PD30 MXU 1 DMCU 2 DMCU 3 A: WDU 0 (OMU) B: HDD 0 (OMS) OMU 0 NPS1(P)/ NPGE(P) 0

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNAC

TBUF

TBUF

TBUF

TBUF

T SS3 TSS3

TBUF

TBUF

TSS3

4
1

3
1

2
1

1
1

ICSU 32 ICSU 33 ICSU 34 ICSU 35 ICSU 36 D MCU 33 D MCU 34 D MCU 35 MXU 14 PD30 MXU 15 D MCU 36 D MCU 37 ICSU 37 N PS1(P)/ NPGE(P) 11 N PS1(P) / NPGE(P) 13 TBUF TBUF

ICSU 26
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

ICSU 20
2

ICSU 14
2

ICSU 27 ICSU 28 ICSU 29 ICSU 30 DMCU 28 DMCU 29 DMCU 30 MXU 12 PD30 MXU 13 DMCU 31 DMCU 32 ICSU 31 NPS1( P)/ NPGE(P) 10 NPS1( P)/ NPGE(P) 12 TBUF TBUF

ICSU 21
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

ICSU 15
3

ICSU 22 ICSU 23 ICSU 24 DMCU 23 DMCU 24 DMCU 25 MXU 10 PD30 MXU 11 DMCU 26 DMCU 27 ICSU 25 NPS1(P)/ NPGE(P) 7 NPS1(P) / NPGE(P) 9 TBUF TBUF

ICSU 16
4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38

ICSU 17 ICSU 18 DMCU 18 DMCU 19 DMCU 20 MXU 8 PD30 MXU 9 DMCU 21 DMCU 22 ICSU 19 NPS1(P)/ NPGE(P) 6 NPS1(P) / NPGE(P) 8 TBUF TBUF

RNC2600

New delivery in RU10/RN4.0 release

5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

RNBC

RNC2600

With full configuration: Total Iub throughput 2839 (DL+UL) 2800 carriers or Node Bs connectivity 20000 Erl Iu capacity Full load sharing, regardless cabinet or subrack Scalability through hardware configuration and capacity licensing Upgrade path is available for RNC450 Upgradeable to support RU20

20

Nokia Siemens Networks

<LE number and name>

Nokia Siemens Networks WCDMA Base Station


MetroSite
MetroSite50

UltraSite

3G MetroSite

Optima Indoor

Optima Compact Outdoor

Supreme Indoor

Supreme Outdoor

Triple Mode

@vantage Node B FlexiBTS

Flexi WCDMA BTS


21 Nokia Siemens Networks <LE number and name>

NB880 (indoor)

Flexi WCDMA BTS Rel.2 HW


Flexi BTS multimode system module
is also prepared for LTE evolution with a SW upgrade. High capacity system module FSMC with 180 CEs FSMD with 396 CEs Can be used as capacity extension for Rel.1 HW (FSMB)

Transmission sub module FTIB to


support All-IP transport and Timing over Packet (TOPA) FRGF, triple RF Modules, support configuration: 2+2+2@30W or 20W 1+1+1@40W or 60W.

22

Nokia Siemens Networks

<LE number and name>

RAN Transmission and Transport

SGSN WBTS CoCo WBTS OAM SDH/ PDH OSS

ATM IP ATM IP Ethernet RNC

WBTS MGW

23

Nokia Siemens Networks

<LE number and name>

RAN supports different transport solution, i.e. ATM and IP. Both types are possible to be used independently for signalling or user plane, even used toward the same network element in RAN (called hybrid transport)

Transmission and Transport Solution


Standalone AXC (S-AXC) is ATM
transmission node. One subrack (on the figure) supports 2 x 1.2 Gbps of switching capacity. Various interface unit are available
Standalone AXC

Short to long hop length Various frequency band: 6, 7, 8, 13,


24 Nokia Siemens Networks <LE number and name>

PowerHopper

FlexiHopper

15, 18, 23, 26, 28, 32, 38 and 58 GHz PDH radio SDH radio (PowerHopper) Various indoor unit type: FIU19, IFUE or FXC-RRI Flexbus interface

NetAct Framework
Workflow Manager Planner Configurator & Provisioning Reporter

Administrator

Monitor Service Quality Manager Unified Mediation and Adaptation

3rd party tools

Rating & Charging

Network
Fixed NW 1G 2G GPRS EDGE 3G 4G

25

Nokia Siemens Networks

<LE number and name>

The new NSN OSS product architecture provides a lot of benefits to the service provider. The separation of the element management from network and service management allows for fast adaptation to new network technologies and new releases of network elements. This kind of architecture is capable of supporting any combination of network technologies. The main principle is that current and new systems and applications can co-exits smoothly in the same network. Highlights of the NetAct Framework: 1. 3rd party tools: Building blocks allow the use of 3rd party products as an integrated part of OSS. 2. Common Network Topology: Access to OSS data is available through open interfaces. This enables the integration to other OSS/IT systems. 3. The use of a CORBA (Common Object Request Broker Architecture) based message bus allows peer-to-peer communication within the OSS. 4. Common WEB-GUI (Graphical User Interface): user access via Web interface application location transparent to the users all user interface applications work on network level 5. Management applications are developed separately as system components which are based on operator processes.

Top Level User Interface

26

Nokia Siemens Networks

<LE number and name>

Presents a graphical, hierarchical view of the network or part of the network General alarm situation of managed objects can be viewed. Uses pop-up menus for a variety of applications Activates also other Nokia NetAct applications. The users can easily create and tailor the view hierarchy as well as the contents of the views.

RAN Configuration Management


Radio network planning
Radio network planning tool Nokia NetAct Planner 3rd party planning tool

Plan management in NetAct


OSS Database CM Editor: CM Editor: Edit Plans Edit Plans

intranet

CM Plan Manager: Import & Export Plans

CM Provisioner: Activate & Download Plans

NetAct provides a web site for RNW plans: Storage Edit Download, activate and rollback Upload actual configuration

RNW plan in XML format

WBTS WBTS WBTS RNC MGW

Radio Access Network

27

Nokia Siemens Networks

<LE number and name>

The NetAct solution supports the capability to plan the RAN with NetAct Planner or a 3rd party planning tool. The plan is transferred to NetAct electronically and the planned parameters, settings and software are downloaded to the actual network equipment. Storing the plan for later use is also possible. The main advantages of the NSN tools for RAN network development are: Faster planning and implementation of network coverage provides for an early launch of service. Less manual work and site visits are required to put parameters into network elements. This results in fewer errors and an improved effectiveness. Optimised infrastructure investments and improved network quality can be achieved by analysing the network behaviour, performance and usage.