[3g] rnc2600 hardware.ppt
TRANSCRIPT
Slide 1For internal use
Insert footnotes as appropriate.
Nokia Siemens Networks has four information confidentiality classes: Public, For internal use, Confidential, Secret
"Public" - May be distributed to anyone. Usually public information shall be available for everyone.
"For internal use" - May be distributed to anyone employed or having a business relationship with the company under a valid non-disclosure agreement. The disclosure of small amounts of this information to the public will not cause meaningful damages to the company. ‘’For internal use’’ is the default class for Nokia Siemens Networks information, this should be included e.g. in all MS Office (master) templates.
(Previously Nokia: Company Confidential, Siemens: Internal use)
"Confidential" - May be distributed only to people who have a valid business need. The validity of the business need can be judged by anyone who is authorised to possess the information. Unintentional disclosure of this information to the public will cause significant damages to the company. ‘’Confidential’’ is the default class for any customer information.
(Previously Nokia and Siemens: Confidential)
"Secret" - May be distributed only to people who are specifically authorised by the owner of the information. Disclosure of this information to the public will cause serious damages to the company.
(Previously Nokia: Secret, Siemens: Strictly confidential)
All documents in Nokia Siemens Networks shall be labelled according to this confidentiality schema.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Interfaces
For internal use
UMTS network architecture
For internal use
For internal use
Main RNC tasks
The main function of the RNC is to control and manage the Radio Access Network (RAN) and the radio channels. The RNC is designed for efficient use of radio resources and easy operation and maintenance.
Radio Resource Management
Operation and maintenance
For internal use
all based on IPA platform,
all using same plug in units
RNC196
Uses 1.8m tall cabinet,
Capacity expansions available still today
RNC450
Uses 2.1m tall cabinet,
RNC2600
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC196, Original Design
Step1,
Step1, 48 Mbps
For internal use
For internal use
high capacity,
high coverage,
remote and indoor solutions
Max Iub capacity of 2.8Gbit/s in RU10 and 3.5Gbit/s in RU20 with two cabinets
Optimized for mobile broadband and flat fee tariffing
High number of HSPA users
Capacity licensing
NSN RNC2600
For internal use
RNC2600 with RU20
Same cabinet solution as with RNC450
Same max 2 cabinet solution
Same max 4 subracks per cabinet
Three target capacity steps
1540 Mbit/s DL+UL
2520 Mbit/s DL+UL
3500 Mbit/s DL+UL
Transport interfaces per unit
For internal use
For internal use
For internal use
The platform allows
Offers a wide range of cellular and fixed network operations
The operating system is used as a platform for other system level software and all the application software
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 Software
The software level for use with the RNC2600 is RN4.0 for release RU10 and RN5.0 for release RU20.
Common system software used for all the control computers
This provides a standard easy to use operating environment for the application software
Facilitates easy development and maintenance of the application software
Helps the user to understand the software operation
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 Architecture
The NSN RNC2600 has a modular software and Hardware architecture
This allows:-
Flexibility of the number and types of interfaces
New functionality to be added without changing the system architecture
A long operational life span while still being able to support new and up to date features
The RNC2600 is able to provide more than adequate computing power that will be necessary to support the complex services envisioned for the future.
The computing environment is fault tolerant (redundancy)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 Architecture
For internal use
A2SU units – functionality is included in the STM-1 interface unit
GTPU units – functionality is included in the Ethernet or STM-1 interface units NP8S1-B or NP2GE-B
RRMU units – functionality is included in ICSU and RSMU/OMU units
NIP1 – E1/T1/JT1 interfaces are not supported by the RNC2600
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Multiprocessor based system
The data processing capacity is divided amongst several computer unit
Appropriate redundancy is configured according to the application needs
2N - Hot standby
N+1 - 1 or more spare units designated to a group of functional units
SN+ - No spare unit is allocated due to the units being part of a resource pool. Extra capacity is already built in to the pool
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Management and control computer units
- OMU, ICSU, RSMU, DMCU and OMS
Switching and multiplexing units
Units in the timing, power supply, and hardware management subsystems
- TBU, Power supply
For internal use
Certain SW modules are loaded to each functional unit type
Each functional unit has its own redundancy scheme
Functional unit has certain operations state (WO, SP, TE)
Example: SFU
Physical HW unit
One plug-in-unit type can be used for one or more functional unit types
In most of the operations the plug-in-unit type is not relevant for the operator (e.g. state handling of the units is done for functional units)
Most of SW does not see the different plug-in-unit types – only functional units
Example: SF20H
For internal use
OMU - Operations and Maintenance Unit
Serves as an interface between the RNC and Operations and Maintenance Server (OMS)
Responsible for basic system maintenance functions
Connects to and controls duplicated system hard disks containing the operating software and fallback software
Stores the Radio Network database, ATM/IP configuration database, Equipment database, Alarm History database
Responsible for Cellular Maintenance functions for recovering and configuring the radio network
monitors the status of the network and blocks the faulty units if necessary
2N redundant plug in unit
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
ICSU - Interface Control and Signalling Unit
Performs RNC functions that are highly dependant upon signalling to other network elements
Handles distributed RRM functions related to the RNC
The ICSU is responsible for the following tasks
Layer 3 signalling protocols - RANAP, NBAP, RNSAP, RRC, SABP
transport network level signalling protocol ALCAP
Handover control
Power control
Load control
For internal use
RSMU - Resource and Switch Management Unit
Performs the central resource management tasks
The RSMU is responsible for the following tasks
Allocation of DSP and resource management for different tasks - macro diversity combining, data traffic
Supervision and management of DMCUs
Software loading of DMCUs
ATM connection control
ATM resource management
For internal use
Performs the User Plane and Control Plane related RNC functions
Processors used are
State of the art Digital Signal Processors
Signalling processing is configured and altered dynamically for each DSP
The DMCU is responsible for the following tasks
UE and L2 protocols
SN+ redundant
For internal use
OMS - Operations and Maintenance Server
Provides an interface to
Local user interface functions (via Application Launcher)
The OMS is implemented using an Intel based standard PC core and supports
SCSI Interfaces to its own mass memory devices (2 - Raid1)
A USB keyboard and mouse
A standard VGA display
A Serial port
For internal use
NSN RNC2600 Architecture - Element Management Unit - OMS
Primarily responsible for the RNC Element Management functions and performs the following tasks
Support of Graphical User Interfaces - GUIs
Support for MML/MMI sessions
Provides the NetAct interface to the RNC and Network Elements
Supports O&M functions in the RNC
Post processing support for Measurements and Statistics
Support for the duplicated SCSI interfaces for its mass memory devices (hard disks)
Operating system is Linux supporting the Linux based NSN Flexi platform.
The Flexi platform provides high availability and security
The OMS has no redundancy - does not affect traffic switching capabilities of the RNC
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Based on ATM technology
The ATM technology provides required capacity and flexibility to support the various traffic types within the network.
Support capacity and traffic switching within the RNC
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
SFU - Switching fabric Unit
Provides part of the ATM cell switching functionality
Supports Point to Point and Point to Multi Point connection topologies
Differentiated handling of the various ATM service categories
Connects to the Network Interface Units (NIUs) and Multiplexer units (MXUs)
2N redundant
For internal use
MXU - Multiplexer Unit
The RNC has several pairs of MXUs depending on the RNC configuration
The MXU
Multiplexes traffic from the various tributary units to the ATM SFU
Allows for the efficient usage of switching resources for the low bit rate NIUs
Allows for the efficient usage of computer units with small to moderate bandwidth requirements (RSMU/ICSU/DMCU)
Responsible for part of the ATM layer processing functions
Policing
Statistics
Buffer management and scheduling
For internal use
NSN RNC2600 Architecture - Switching and Multiplexing Units - MXU
The ICSU, DMCU, RSMU all connect to the SFU via the MXU
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 Architecture - Timing and Hardware Management Bus Unit - TBU
TBU - Timing Bus Unit
Two plug in units in each sub rack
Serial bus that spans all the plug in units in the RNC
Responsible for
RNC synchronisation
For internal use
NPS1/NPS1P
Provides 8 x STM-1/OC-3 optical interfaces or 2 x STM-4 optical interfaces on the unit’s front panel
Executes the physical layer and ATM layer functions
Maps ATM cells to and from the SDH/Sonet frame structure
Header translation
Usage Parameter Control (UPC) - UNI / Network Parameter Control (NPC) - NNI
OAM functions
Traffic management
Performance monitoring
Optional reference clock for timing and synchronisation
The NPS1P supports transport protection (MSP 1+1 / APS 1+1)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NPGE/NPGEP
Executes physical layer and IP layer functionality
Maps IP packets to and from the Ethernet transmission frame structure
Header translation
Traffic management
Performance monitoring
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
EHU - External Hardware Unit
Receives alarms from external sources and forwards them via the HMS to the OMU located external alarm handler
Drives an external lamp panel (EXAU), the cabinet integrated lamp and any other external notification equipment
The EXAU unit is an option
External device connections handled via a cabling panel at the rear of the RNC cabinet
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
ESA24 - 24 port Ethernet Switch
2 Ethernet ports in the Front panel
Provides the Ethernet switch functionality required for the OMS
2N redundant
For internal use
Winchester disk unit for the OMU
2N redundant
Plug in unit type HDS-B
Hard disk devices for the OMS
Collocated with OMU disks on HDS-B PIUs
Configured Raid1
For internal use
For internal use
For internal use
MXU
MX1G6-A
OMU
CCP18-A
NPS1P/NPS1 0
NPS1P/NPS1 0
TBU/TBUF
TSS3
For internal use
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Radio Resource Management
For internal use
Radio Resource Management (RRM)
Manages channel allocations - traffic and signalling that can simultaneously be used in the RAN
Divided into Network based functions and connection based functions
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Network based functions can be divided into two categories
Event Based - as and when required
Admission Control - used to maintain stability and achieve the required traffic capacity of the RAN. Executed when the RAB is set up or modified. Also interacts with Handover Control
Packet Scheduling - takes care of scheduling the radio resources for NRT radio bearers
Continuous
Load Control - ensures that the system does not become overloaded. If an overload situation does occur it needs to make sure that the system is returned to the normal load state as defined by radio network planning in a quick and controlled manner
Connection Based functions are activated when a radio link is allocated to a connection
Power Control - takes care of the power requirements for the transmitting entities and tries to ensure that all the SIR targets are kept ensuring minimum interference and sufficient quality of the connection
Handover Control - provides support for soft/softer handovers. Primarily RNC controlled but can be UE initiated as well
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Provides basic functionality and End User related features
User Plane (UP) processing towards the Circuit Switched (CS) and Packet Switched (PS) core networks - management of RABs
Radio Network Layer Control Plane processing
Security - Integrity Checking and Ciphering
Location Services
For internal use
Operations and Maintenance (O&M)
Provides the means for operations personnel to maintain the RNC and Radio Network in optimal condition
Easy to use Graphical User Interfaces (GIUs) for
Configuration
Fault Management
Performance Management
Accessible via Local Management System (LMS) or Network Management System (NMS)
Configuration
Support for remote software upgrades to the RNC and WBTS
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Fault Management
Continuous checking of the network to detect any irregularities in the operation of the Network Elements
Identification of faulty units in the RNC and notifying the NMS and recovery system of the problem
Isolates the faulty unit/s from the system and places spare units into operation if they exist
Fault diagnosis system pinpoints the exact nature of the problem and verifies the status of the faulty unit and the system as a whole
Maintains an alarm and events history
Performance Management
Continually monitors and collects performance statistics from the network and network elements
Provides the ability to set triggers in order to identify possible problem areas in the network before they become a real problem
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 - Interfaces
For internal use
NSN RNC2600 - Interfaces
RNC2600 Interfaces
The RNC2600 provides various interfaces between the Network Elements situated in the Core Network and the RAN
Iub Interface
3GPP compliant
Iur Interface
Connects between two RNCs
Manages soft handovers by transferring all the necessary information and data between the Serving RNC (SRNC) and Drift RNC (DRNC)
The Iur is a standardised open interface
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 - Interfaces
3GPP compliant
The interfaces between the RNC and Core Network are split into two separate functional paths
Iu-CS supports Circuit Switched traffic
Iu-CS normally terminates in the MSC via the MGW
Iu-PS supports Packet Switched traffic
Iu-PS normally terminates in the SGSN
Iu-BC Interface
The interface between the RNC and the Cell Broadcast Centre (CBC)
3GPP compliant
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 - Interfaces
Iu-PC Interface
The interface between the Stand Alone Serving Mobile Location Centre (S-SMLC)
Uses PCAP protocol
Provides GPS assistance data to the RNC for UE positioning
May also perform the position calculations for different postioning methods
Network Management Interface
The interface used to connect the RNC to the Operations Support System (OSS/NetAct)
Provides the O&M connections between the Radio Network and the OSS
Uses TCP/IP
RNC/NetAct application level communication uses CORBA
O&M traffic secured by IPSec protocol between the RNC and NetAct
Supports MML via telnet
For internal use
For internal use
STM-1 / OC-3
The NPS1 or NPS1P functional unit offers ATM over SDH/Sonet interfaces
The NPS1P offers MSP 1+1 and APS 1+1 protection
Plug in unit type is NP8S1-B for both NPS1 and NPS1P
Each plug in unit contains 8 x SDH STM-1/Sonet OC-3 optical interfaces
Gigabit Ethernet
The NPGE or NPGEP functional unit offers IP over Ethernet interfaces
The NPGEP supports 2N redundancy
Plug in unit type is NP2GE for both NPGE and NPGEP
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
RNC2600/1278
RNC2600/2840
Iub throughput:
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC2600/1540
RNC2600/3500
RNC2600/2520
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 (RU20) - Hardware Capacity
The RNC2600 can be equipped for three different hardware configuration steps
RNC2600/1540 (Step 1)
This consists of 1 cabinet with all the sub racks fully equipped
RNC2600/2520 (Step 2)
This consists of 2 cabinets - cabinet 1 with all sub racks fully equipped and cabinet 2 with the first two sub racks fully equipped
RNC2600/3500 (Step 3)
This consists of 2 cabinets - cabinet 1 with all sub racks fully equipped and cabinet 2 with all the sub racks fully equipped
The RNC2600 supports capacity licensing which defines the actual allowed capacity of the RNC2600
The software only defines the maximum RNC2600 capacity from the hardware perspective
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Capacity steps for RNC2600 at RN4.0 level
Config. steps
Number of interfaces
For internal use
Capacity steps for RNC2600 at RN5.0 level
Config. steps
Number of interfaces
For internal use
For internal use
NSN RNC2600 - Capacity licensing
The RNC2600 capacity licensing allows for capacity configurations based upon the actual RNC2600 traffic
This allows for cost efficient usage of the RNC2600 resources in different networks
Capacity is licensed using three capacity parameters
Iub PS data throughput in Mbps
AMR capacity in Erlang
Number of required carriers
The license keys are required to be installed in the RNC2600
The initial RNC2600 capacity is defined when ordering the RNC2600
The corresponding license file will be delivered with the RNC2600
RNC2600 capacity upgrades can be performed by ordering new capacity license files and activating them via
NetAct
For internal use
RNC2600 enables capacity licensing
RNC Capacity can be freely configured with SW license key for:
Data
Voice
capacity step 1
capacity step 2
capacity step 3
0….23800 Erl
0….1440 Cells
0….47600 Erl
0….2100 Cells
0….70000 Erl
0….2800 Cells
For internal use
For internal use
one spare unit designated for one active unit
software in the unit pair is kept synchronized (hot-standby) -> fast switchover
Replacement (N+1)
one or more units designated to be spare units for a group
allocating resources to a unit defines it as active, not allocating resources defines to be spare
spare unit can replace any active unit in the group -> slower switchover, requires warming (cold-standby)
users responsibility to change the working state of the unit to reflect the resource allocation situation and to leave at least one spare unit
Load sharing (SN+)
no spare units, group acts as a resource pool
number of units selected so that there is overcapacity
if a few units are disabled, the whole group can still perform its functions
No redundancy
no special requirements for reliability
SN+ redundancy has been used in A2SPs, DMCUs and GTPUs for example. System should still function if there exists one faulty A2SP unit.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
2N - Hot standby
N+1 - 1 or more spare units designated to a group of functional units
SN+ - No spare unit is allocated due to the units being part of a resource pool. Extra capacity is already built in to the pool
Functional Unit
Redundancy Principle
NPGEP
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC architecture and load sharing
In RNC2600 all the plug in units of the network element are in the same resource pool regardless of the cabinet or the subrack they are physically located.
All User plane and all Control Plane resources are shared between all BTSs connected to RNC2600.
In NSN RNC there are no dedicated resources for certain BTSs or Iub, Iu CS or Iu PS.
This allows the most optimal RNC capacity utilization. The load can be shared over all the units. This is efficient as the traffic is not evenly shared between BTSs and traffic changes over the time.
Any RAN interface (Iub, Iu-cs, Iu-ps, ..) can be configured to any physical interface unit or to any physical interface of RNC2600.
The same ATM/IP interface unit and even the physical interface can have several logical interfaces. This allows efficient utilization of the physical interfaces in RNC.
NSN RNC
One resource
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Insert footnotes as appropriate.
Nokia Siemens Networks has four information confidentiality classes: Public, For internal use, Confidential, Secret
"Public" - May be distributed to anyone. Usually public information shall be available for everyone.
"For internal use" - May be distributed to anyone employed or having a business relationship with the company under a valid non-disclosure agreement. The disclosure of small amounts of this information to the public will not cause meaningful damages to the company. ‘’For internal use’’ is the default class for Nokia Siemens Networks information, this should be included e.g. in all MS Office (master) templates.
(Previously Nokia: Company Confidential, Siemens: Internal use)
"Confidential" - May be distributed only to people who have a valid business need. The validity of the business need can be judged by anyone who is authorised to possess the information. Unintentional disclosure of this information to the public will cause significant damages to the company. ‘’Confidential’’ is the default class for any customer information.
(Previously Nokia and Siemens: Confidential)
"Secret" - May be distributed only to people who are specifically authorised by the owner of the information. Disclosure of this information to the public will cause serious damages to the company.
(Previously Nokia: Secret, Siemens: Strictly confidential)
All documents in Nokia Siemens Networks shall be labelled according to this confidentiality schema.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Interfaces
For internal use
UMTS network architecture
For internal use
For internal use
Main RNC tasks
The main function of the RNC is to control and manage the Radio Access Network (RAN) and the radio channels. The RNC is designed for efficient use of radio resources and easy operation and maintenance.
Radio Resource Management
Operation and maintenance
For internal use
all based on IPA platform,
all using same plug in units
RNC196
Uses 1.8m tall cabinet,
Capacity expansions available still today
RNC450
Uses 2.1m tall cabinet,
RNC2600
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC196, Original Design
Step1,
Step1, 48 Mbps
For internal use
For internal use
high capacity,
high coverage,
remote and indoor solutions
Max Iub capacity of 2.8Gbit/s in RU10 and 3.5Gbit/s in RU20 with two cabinets
Optimized for mobile broadband and flat fee tariffing
High number of HSPA users
Capacity licensing
NSN RNC2600
For internal use
RNC2600 with RU20
Same cabinet solution as with RNC450
Same max 2 cabinet solution
Same max 4 subracks per cabinet
Three target capacity steps
1540 Mbit/s DL+UL
2520 Mbit/s DL+UL
3500 Mbit/s DL+UL
Transport interfaces per unit
For internal use
For internal use
For internal use
The platform allows
Offers a wide range of cellular and fixed network operations
The operating system is used as a platform for other system level software and all the application software
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 Software
The software level for use with the RNC2600 is RN4.0 for release RU10 and RN5.0 for release RU20.
Common system software used for all the control computers
This provides a standard easy to use operating environment for the application software
Facilitates easy development and maintenance of the application software
Helps the user to understand the software operation
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 Architecture
The NSN RNC2600 has a modular software and Hardware architecture
This allows:-
Flexibility of the number and types of interfaces
New functionality to be added without changing the system architecture
A long operational life span while still being able to support new and up to date features
The RNC2600 is able to provide more than adequate computing power that will be necessary to support the complex services envisioned for the future.
The computing environment is fault tolerant (redundancy)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 Architecture
For internal use
A2SU units – functionality is included in the STM-1 interface unit
GTPU units – functionality is included in the Ethernet or STM-1 interface units NP8S1-B or NP2GE-B
RRMU units – functionality is included in ICSU and RSMU/OMU units
NIP1 – E1/T1/JT1 interfaces are not supported by the RNC2600
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Multiprocessor based system
The data processing capacity is divided amongst several computer unit
Appropriate redundancy is configured according to the application needs
2N - Hot standby
N+1 - 1 or more spare units designated to a group of functional units
SN+ - No spare unit is allocated due to the units being part of a resource pool. Extra capacity is already built in to the pool
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Management and control computer units
- OMU, ICSU, RSMU, DMCU and OMS
Switching and multiplexing units
Units in the timing, power supply, and hardware management subsystems
- TBU, Power supply
For internal use
Certain SW modules are loaded to each functional unit type
Each functional unit has its own redundancy scheme
Functional unit has certain operations state (WO, SP, TE)
Example: SFU
Physical HW unit
One plug-in-unit type can be used for one or more functional unit types
In most of the operations the plug-in-unit type is not relevant for the operator (e.g. state handling of the units is done for functional units)
Most of SW does not see the different plug-in-unit types – only functional units
Example: SF20H
For internal use
OMU - Operations and Maintenance Unit
Serves as an interface between the RNC and Operations and Maintenance Server (OMS)
Responsible for basic system maintenance functions
Connects to and controls duplicated system hard disks containing the operating software and fallback software
Stores the Radio Network database, ATM/IP configuration database, Equipment database, Alarm History database
Responsible for Cellular Maintenance functions for recovering and configuring the radio network
monitors the status of the network and blocks the faulty units if necessary
2N redundant plug in unit
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
ICSU - Interface Control and Signalling Unit
Performs RNC functions that are highly dependant upon signalling to other network elements
Handles distributed RRM functions related to the RNC
The ICSU is responsible for the following tasks
Layer 3 signalling protocols - RANAP, NBAP, RNSAP, RRC, SABP
transport network level signalling protocol ALCAP
Handover control
Power control
Load control
For internal use
RSMU - Resource and Switch Management Unit
Performs the central resource management tasks
The RSMU is responsible for the following tasks
Allocation of DSP and resource management for different tasks - macro diversity combining, data traffic
Supervision and management of DMCUs
Software loading of DMCUs
ATM connection control
ATM resource management
For internal use
Performs the User Plane and Control Plane related RNC functions
Processors used are
State of the art Digital Signal Processors
Signalling processing is configured and altered dynamically for each DSP
The DMCU is responsible for the following tasks
UE and L2 protocols
SN+ redundant
For internal use
OMS - Operations and Maintenance Server
Provides an interface to
Local user interface functions (via Application Launcher)
The OMS is implemented using an Intel based standard PC core and supports
SCSI Interfaces to its own mass memory devices (2 - Raid1)
A USB keyboard and mouse
A standard VGA display
A Serial port
For internal use
NSN RNC2600 Architecture - Element Management Unit - OMS
Primarily responsible for the RNC Element Management functions and performs the following tasks
Support of Graphical User Interfaces - GUIs
Support for MML/MMI sessions
Provides the NetAct interface to the RNC and Network Elements
Supports O&M functions in the RNC
Post processing support for Measurements and Statistics
Support for the duplicated SCSI interfaces for its mass memory devices (hard disks)
Operating system is Linux supporting the Linux based NSN Flexi platform.
The Flexi platform provides high availability and security
The OMS has no redundancy - does not affect traffic switching capabilities of the RNC
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Based on ATM technology
The ATM technology provides required capacity and flexibility to support the various traffic types within the network.
Support capacity and traffic switching within the RNC
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
SFU - Switching fabric Unit
Provides part of the ATM cell switching functionality
Supports Point to Point and Point to Multi Point connection topologies
Differentiated handling of the various ATM service categories
Connects to the Network Interface Units (NIUs) and Multiplexer units (MXUs)
2N redundant
For internal use
MXU - Multiplexer Unit
The RNC has several pairs of MXUs depending on the RNC configuration
The MXU
Multiplexes traffic from the various tributary units to the ATM SFU
Allows for the efficient usage of switching resources for the low bit rate NIUs
Allows for the efficient usage of computer units with small to moderate bandwidth requirements (RSMU/ICSU/DMCU)
Responsible for part of the ATM layer processing functions
Policing
Statistics
Buffer management and scheduling
For internal use
NSN RNC2600 Architecture - Switching and Multiplexing Units - MXU
The ICSU, DMCU, RSMU all connect to the SFU via the MXU
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 Architecture - Timing and Hardware Management Bus Unit - TBU
TBU - Timing Bus Unit
Two plug in units in each sub rack
Serial bus that spans all the plug in units in the RNC
Responsible for
RNC synchronisation
For internal use
NPS1/NPS1P
Provides 8 x STM-1/OC-3 optical interfaces or 2 x STM-4 optical interfaces on the unit’s front panel
Executes the physical layer and ATM layer functions
Maps ATM cells to and from the SDH/Sonet frame structure
Header translation
Usage Parameter Control (UPC) - UNI / Network Parameter Control (NPC) - NNI
OAM functions
Traffic management
Performance monitoring
Optional reference clock for timing and synchronisation
The NPS1P supports transport protection (MSP 1+1 / APS 1+1)
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NPGE/NPGEP
Executes physical layer and IP layer functionality
Maps IP packets to and from the Ethernet transmission frame structure
Header translation
Traffic management
Performance monitoring
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
EHU - External Hardware Unit
Receives alarms from external sources and forwards them via the HMS to the OMU located external alarm handler
Drives an external lamp panel (EXAU), the cabinet integrated lamp and any other external notification equipment
The EXAU unit is an option
External device connections handled via a cabling panel at the rear of the RNC cabinet
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
ESA24 - 24 port Ethernet Switch
2 Ethernet ports in the Front panel
Provides the Ethernet switch functionality required for the OMS
2N redundant
For internal use
Winchester disk unit for the OMU
2N redundant
Plug in unit type HDS-B
Hard disk devices for the OMS
Collocated with OMU disks on HDS-B PIUs
Configured Raid1
For internal use
For internal use
For internal use
MXU
MX1G6-A
OMU
CCP18-A
NPS1P/NPS1 0
NPS1P/NPS1 0
TBU/TBUF
TSS3
For internal use
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Radio Resource Management
For internal use
Radio Resource Management (RRM)
Manages channel allocations - traffic and signalling that can simultaneously be used in the RAN
Divided into Network based functions and connection based functions
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Network based functions can be divided into two categories
Event Based - as and when required
Admission Control - used to maintain stability and achieve the required traffic capacity of the RAN. Executed when the RAB is set up or modified. Also interacts with Handover Control
Packet Scheduling - takes care of scheduling the radio resources for NRT radio bearers
Continuous
Load Control - ensures that the system does not become overloaded. If an overload situation does occur it needs to make sure that the system is returned to the normal load state as defined by radio network planning in a quick and controlled manner
Connection Based functions are activated when a radio link is allocated to a connection
Power Control - takes care of the power requirements for the transmitting entities and tries to ensure that all the SIR targets are kept ensuring minimum interference and sufficient quality of the connection
Handover Control - provides support for soft/softer handovers. Primarily RNC controlled but can be UE initiated as well
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Provides basic functionality and End User related features
User Plane (UP) processing towards the Circuit Switched (CS) and Packet Switched (PS) core networks - management of RABs
Radio Network Layer Control Plane processing
Security - Integrity Checking and Ciphering
Location Services
For internal use
Operations and Maintenance (O&M)
Provides the means for operations personnel to maintain the RNC and Radio Network in optimal condition
Easy to use Graphical User Interfaces (GIUs) for
Configuration
Fault Management
Performance Management
Accessible via Local Management System (LMS) or Network Management System (NMS)
Configuration
Support for remote software upgrades to the RNC and WBTS
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Fault Management
Continuous checking of the network to detect any irregularities in the operation of the Network Elements
Identification of faulty units in the RNC and notifying the NMS and recovery system of the problem
Isolates the faulty unit/s from the system and places spare units into operation if they exist
Fault diagnosis system pinpoints the exact nature of the problem and verifies the status of the faulty unit and the system as a whole
Maintains an alarm and events history
Performance Management
Continually monitors and collects performance statistics from the network and network elements
Provides the ability to set triggers in order to identify possible problem areas in the network before they become a real problem
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
NSN RNC2600 - Interfaces
For internal use
NSN RNC2600 - Interfaces
RNC2600 Interfaces
The RNC2600 provides various interfaces between the Network Elements situated in the Core Network and the RAN
Iub Interface
3GPP compliant
Iur Interface
Connects between two RNCs
Manages soft handovers by transferring all the necessary information and data between the Serving RNC (SRNC) and Drift RNC (DRNC)
The Iur is a standardised open interface
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 - Interfaces
3GPP compliant
The interfaces between the RNC and Core Network are split into two separate functional paths
Iu-CS supports Circuit Switched traffic
Iu-CS normally terminates in the MSC via the MGW
Iu-PS supports Packet Switched traffic
Iu-PS normally terminates in the SGSN
Iu-BC Interface
The interface between the RNC and the Cell Broadcast Centre (CBC)
3GPP compliant
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 - Interfaces
Iu-PC Interface
The interface between the Stand Alone Serving Mobile Location Centre (S-SMLC)
Uses PCAP protocol
Provides GPS assistance data to the RNC for UE positioning
May also perform the position calculations for different postioning methods
Network Management Interface
The interface used to connect the RNC to the Operations Support System (OSS/NetAct)
Provides the O&M connections between the Radio Network and the OSS
Uses TCP/IP
RNC/NetAct application level communication uses CORBA
O&M traffic secured by IPSec protocol between the RNC and NetAct
Supports MML via telnet
For internal use
For internal use
STM-1 / OC-3
The NPS1 or NPS1P functional unit offers ATM over SDH/Sonet interfaces
The NPS1P offers MSP 1+1 and APS 1+1 protection
Plug in unit type is NP8S1-B for both NPS1 and NPS1P
Each plug in unit contains 8 x SDH STM-1/Sonet OC-3 optical interfaces
Gigabit Ethernet
The NPGE or NPGEP functional unit offers IP over Ethernet interfaces
The NPGEP supports 2N redundancy
Plug in unit type is NP2GE for both NPGE and NPGEP
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
For internal use
RNC2600/1278
RNC2600/2840
Iub throughput:
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC2600/1540
RNC2600/3500
RNC2600/2520
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
NSN RNC2600 (RU20) - Hardware Capacity
The RNC2600 can be equipped for three different hardware configuration steps
RNC2600/1540 (Step 1)
This consists of 1 cabinet with all the sub racks fully equipped
RNC2600/2520 (Step 2)
This consists of 2 cabinets - cabinet 1 with all sub racks fully equipped and cabinet 2 with the first two sub racks fully equipped
RNC2600/3500 (Step 3)
This consists of 2 cabinets - cabinet 1 with all sub racks fully equipped and cabinet 2 with all the sub racks fully equipped
The RNC2600 supports capacity licensing which defines the actual allowed capacity of the RNC2600
The software only defines the maximum RNC2600 capacity from the hardware perspective
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Capacity steps for RNC2600 at RN4.0 level
Config. steps
Number of interfaces
For internal use
Capacity steps for RNC2600 at RN5.0 level
Config. steps
Number of interfaces
For internal use
For internal use
NSN RNC2600 - Capacity licensing
The RNC2600 capacity licensing allows for capacity configurations based upon the actual RNC2600 traffic
This allows for cost efficient usage of the RNC2600 resources in different networks
Capacity is licensed using three capacity parameters
Iub PS data throughput in Mbps
AMR capacity in Erlang
Number of required carriers
The license keys are required to be installed in the RNC2600
The initial RNC2600 capacity is defined when ordering the RNC2600
The corresponding license file will be delivered with the RNC2600
RNC2600 capacity upgrades can be performed by ordering new capacity license files and activating them via
NetAct
For internal use
RNC2600 enables capacity licensing
RNC Capacity can be freely configured with SW license key for:
Data
Voice
capacity step 1
capacity step 2
capacity step 3
0….23800 Erl
0….1440 Cells
0….47600 Erl
0….2100 Cells
0….70000 Erl
0….2800 Cells
For internal use
For internal use
one spare unit designated for one active unit
software in the unit pair is kept synchronized (hot-standby) -> fast switchover
Replacement (N+1)
one or more units designated to be spare units for a group
allocating resources to a unit defines it as active, not allocating resources defines to be spare
spare unit can replace any active unit in the group -> slower switchover, requires warming (cold-standby)
users responsibility to change the working state of the unit to reflect the resource allocation situation and to leave at least one spare unit
Load sharing (SN+)
no spare units, group acts as a resource pool
number of units selected so that there is overcapacity
if a few units are disabled, the whole group can still perform its functions
No redundancy
no special requirements for reliability
SN+ redundancy has been used in A2SPs, DMCUs and GTPUs for example. System should still function if there exists one faulty A2SP unit.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
2N - Hot standby
N+1 - 1 or more spare units designated to a group of functional units
SN+ - No spare unit is allocated due to the units being part of a resource pool. Extra capacity is already built in to the pool
Functional Unit
Redundancy Principle
NPGEP
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
RNC architecture and load sharing
In RNC2600 all the plug in units of the network element are in the same resource pool regardless of the cabinet or the subrack they are physically located.
All User plane and all Control Plane resources are shared between all BTSs connected to RNC2600.
In NSN RNC there are no dedicated resources for certain BTSs or Iub, Iu CS or Iu PS.
This allows the most optimal RNC capacity utilization. The load can be shared over all the units. This is efficient as the traffic is not evenly shared between BTSs and traffic changes over the time.
Any RAN interface (Iub, Iu-cs, Iu-ps, ..) can be configured to any physical interface unit or to any physical interface of RNC2600.
The same ATM/IP interface unit and even the physical interface can have several logical interfaces. This allows efficient utilization of the physical interfaces in RNC.
NSN RNC
One resource
* © Nokia Siemens Networks Presentation / Author / Date
For internal use