NN-20500-021 (UMTS RNC 1500 Fundamentals) 04.03 Standard November 2007

NN-20500-021 Wireless Service Provider Solutions
W-CDMA
Product Fundamentals UMTS RNC 1500 Fundamentals
NN-20500-021 04.03/EN Standard November 2007
Wireless Service Provider Solutions
W-CDMA
Product Fundamentals UMTS RNC 1500 Fundamentals
Document number: Document issue: Document status: System release: Date: NN-20500-021 04.03/EN Standard UA05.1 November 2007
Copyright 2005-2007 Alcatel-Lucent, All Rights Reserved ALCATEL-LUCENT CONFIDENTIAL UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies. ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately.
Alcatel-Lucent Confidential
Publication history
PUBLICATION HISTORY
SYSTEM RELEASE UA05.1 November 2007
Issue 04.03/EN Standard Update for DR5
September 2007
Issue 04.02/EN Preliminary Update after internal review
August 2007
Issue 04.01/EN Draft Update for UA05.1
SYSTEM RELEASE UMTS 5.1 June 2007

Issue 03.03/EN Standard Update for UA 5.0 Channel Readiness after editorial review
March 2007
Issue 03.02/EN Preliminary Update after internal review
February 2007
Issue 03.01/EN Draft Update for UA 5.0
SYSTEM RELEASE UMTS 5.0 January 2007

Issue 02.04/EN Standard Post ChR update
Copyright 2005-2007 Alcatel-Lucent
UMTS RNC 1500 Fundamentals
Publication history
ii
April 2006
Issue 02.03/EN Standard Update for Channel Readiness
November 2005
Issue 02.02/EN Preliminary Update for Customer Readiness after internal review
October 2005
Issue 02.01/EN Draft Update for RAN V4.2
SYSTEM RELEASE UMTS 4.1 October 2005

Issue 01.05/EN Standard Update for Channel Readiness
June 2005
Issue 01.04/EN Preliminary Editorial Update.
May 2005
Issue 01.03/EN Preliminary Editorial Update
March 2005
Issue 01.02/EN Preliminary Update for OAM V4.2/RAN V4.1
February 2005
Issue 01.01/EN Draft Update for OAM V4.2/RAN V4.1 Creation
Table of contents
iii
1 About this publication................................................................................................................................................... 1 2 Access Network Roadmap............................................................................................................................................ 3 3 New in this release......................................................................................................................................................... 4 4 RNC regulatory information.......................................................................................................................................... 5 5 UTRAN introduction.......................................................................................................................................................8 6 RNC 1500 basic characteristics.................................................................................................................................. 12 6.1 RNC 1500 introduction............................................................................................................................................ 13 6.2 RNC 1500 features and functionalities.................................................................................................................... 18 6.3 RNC 1500 configurations.........................................................................................................................................21 7 RNC 1500 general architecture................................................................................................................................... 23 8 RNC 1500 services and features.................................................................................................................................27 8.1 RNC 1500 main features......................................................................................................................................... 28 8.2 RNC 1500 main characteristics............................................................................................................................... 29 8.3 RNC 1500 radio resource management.................................................................................................................. 33 8.4 Other RNC 1500 features........................................................................................................................................ 35 9 RNC 1500 interfaces and protocols............................................................................................................................36 9.1 RNC 1500 interfaces............................................................................................................................................... 37 9.2 RNC 1500 protocols................................................................................................................................................ 45 10 RNC 1500 hardware....................................................................................................................................................47 10.1 RNC 1500 hardware presentation.......................................................................................................................... 48 10.2 RNC 1500 hardware modules description.............................................................................................................. 58 10.2.1 Control Processor (CP3) module..................................................................................................................... 59 10.2.2 16p OC-3/STM-1 module................................................................................................................................. 62 10.2.3 Packet Server module hardware...................................................................................................................... 67 10.2.4 Fabric module...................................................................................................................................................70 10.2.5 LED description for Multiservice Switch 15000 module................................................................................... 74 10.3 RNC 1500 cooling system description.................................................................................................................... 77 10.4 RNC 1500 power supply and alarm systems..........................................................................................................86 10.4.1 BIP assembly................................................................................................................................................... 87 10.4.2 PIM modules.................................................................................................................................................... 90 10.4.3 MAC address module.......................................................................................................................................95 10.4.4 Alarm BITS module.......................................................................................................................................... 98 11 Using TML with the RNC 1500.................................................................................................................................102
List of figures
iv
Figure 1 - Alcatel-Lucent UTRAN architecture example....................................................................... ............. ......... 10 Figure 2 - RNC 1500 front view with two RNC 1500 shelves (dual RNC) in the cabinet...................... ............. ......... 15 Figure 3 - RNC 1500 rear view with one RNC 1500 in the upper shelf.............................................................. ......... 16 Figure 4 - RNC 1500 architecture......................................................................................................... ............. ......... 24 Figure 5 - RNC 1500 interfaces.......................................................................................................................... ......... 37 Figure 6 - Iu CS protocol view............................................................................................................... ............. ......... 38 Figure 7 - Iu PS protocol view............................................................................................................... ............. ......... 39 Figure 8 - Iur protocol view................................................................................................................................. ......... 40 Figure 9 - Iub protocol view................................................................................................................... ............. ......... 42 Figure 10 - Iupc protocol view............................................................................................................... ............. ......... 43 Figure 11 - RNC 1500 components layout on the front panel .............................................................. ............. ......... 49 Figure 12 - RNC 1500 components layout on the rear panel............................................................................. ......... 50 Figure 13 - RNC 1500 modules on the front panel............................................................................................. ......... 51 Figure 14 - RNC 1500 modules on the rear panel................................................................................ ............. ......... 52 Figure 15 - Standalone 7k POC modules front view for 120-ohm PCM E1 links.................................. ............. ......... 55 Figure 16 - Standalone 7k POC modules front view for 75-ohm PCM E1 links.................................... ............. ......... 56 Figure 17 - 15k POC modules front view.............................................................................................. ............. ......... 57 Figure 18 - CP3 module: front view.................................................................................................................... ......... 60 Figure 19 - 16p OC-3/STM-1: front view with closed fiber hood........................................................... ............. ......... 63 Figure 20 - 16p OC-3/STM-1 module: front view with open fiber hood................................................. ............. ......... 64 Figure 21 - Packet Server module: hardware overview........................................................................ ............. ......... 68 Figure 22 - RNC cabinet: lower shelf assembly components, rear view............................................... ............. ......... 71 Figure 23 - Fabric module: hardware overview..................................................................................... ............. ......... 72 Figure 24 - Module front panel indicators........................................................................................................... ......... 75 Figure 25 - Upper and lower cooling unit in an RNC 1500 with airflow direction.................................. ............. ......... 78 Figure 26 - Cooling unit: hardware overview...................................................................................................... ......... 81 Figure 27 - Cooling units: front and rear views................................................................................................... ......... 83 Figure 28 - BIP: hardware overview...................................................................................................... ............. ......... 88 Figure 29 - PIM module: hardware overview...................................................................................................... ......... 91 Figure 30 - PIM module: positioning and front panel view.................................................................... ............. ......... 93 Figure 31 - MAC address module: positioning and front panel view..................................................... ............. ......... 96 Figure 32 - MAC Address module: hardware overview...................................................................................... ......... 97 Figure 33 - Alarm BITS: positioning and front panel view..................................................................... ............. ......... 99
List of tables
Table 1 - RNC 1500 SDH/SONET market models............................................................................................. ......... 22 Table 2 - Visual indicator description for all modules............................................................................ ............. ......... 75 Table 3 - Cooling unit LED indications.................................................................................................. ............. ......... 85 Table 4 - Component power consumption............................................................................................ ............. ......... 89 Table 5 - Cooling unit alarm connector................................................................................................. ............. ....... 100 Table 6 - BIP alarm connector............................................................................................................................ ....... 101
About this publication

This publication describes to the Radio Network Controller (RNC) 1500 used in a Universal Mobile Telecommunications System (UMTS). This RNC is called UMTS RNC 1500 (RNC 1500).
Applicability
This publication applies to UA05.1.
Audience
This publication is for operations and maintenance personnel, and other users interested in learning more about the RNC 1500.
Prerequisites
Readers should be familiar with the 3rd Generation Partnership Project (3GPP) Technical Specification release 99 (R99) and the UMTS specification.
Related documents
UMTS RNC 1500 TML Commissioning & Fault Management User Manual (NN-20500-026) Nortel Multiservice Switch 7400 Hardware Description (NN-10600-170) Nortel Multiservice Switch 15000/20000 Hardware Description (NN-10600-120)
How this document is organized

This publication consists of the following parts: The first part provides the Roadmap to UTRAN documentation. The second part provides the RNC regulatory information. The third part gives an UTRAN introduction. The fourth part gives the RNC basic characteristics The fifth part describes the RNC general architecture. The sixth part describes the RNC services and features. The seventh part describes the RNC interfaces and protocols. The eighth part describes the RNC hardware. The last part describes the Local Maintenance Terminal (TML) tool.
Vocabulary conventions
The glossary is presented in the document: UMTS Access Network Terminology (NN-20500-002).
Access Network Roadmap

For collection roadmaps, see UMTS Access Network Documentation Roadmap (NN-20500-050).
New in this release

The following sections detail what's new in the UMTS RNC 1500 Fundamentals NTP for UA05.1.
Features
No new features in this release
Other changes
No other changes for this release.
RNC regulatory information

This section provides regulatory information concerning the RNC.
Regulatory requirement compliance

The equipment described in this document generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the instruction manual, the equipment can cause harmful interference to radio communications. There is no guarantee that interference will not occur in a particular installation. To determine wether this equipment is causing interference, the operator can turn the equipment off and on. The operator is encouraged to correct any interference problems. The Electromagnetic Compatibility (EMC) requirements have been selected to ensure an adequate level of compatibility for apparatus in residential, commercial, and light industrial environments. Compatibility levels, however, do not cover extreme cases that can occur anywhere, but that have a low probability of occurrence. In particular, they may not cover cases where a source of interference that is producing repeated transient or continuous phenomena is permanently present. This could include, for example, a radar or broadcast site in the vicinity. In these cases, the operator can limit the source of interference and/or apply special protection to the impacted equipment. For the integrity of the product, the operator must wear the antistatic wrist strap at all times when working with Alcatel-Lucent systems.
Compliance for American countries (North and South)

The Alcatel-Lucent UMTS RNC does not meet American market requirements as the currently supported frequency bands do not correspond to the allocated UMTS spectrum. Updates will be made to this section as appropriate.
RNC compliance
The UMTS RNC has been demonstrated to comply (either by testing or file submission) with the essential requirements of the following European directives, EMC directive (89/336/EMC) The following standard has been applied to demonstrate compliance with this European Directive, EMC: ETS 300 386 version 1.2.1 In addition, the RNC has been demonstrated to comply with the following standard, Safety: EN 60950, Edition 3, 2000
Other compliances
In addition to the requirements detailed above, and as a voluntary demonstration of compliance, the UMTS RNC and UMTS BTS comply (as appropriate) with the essential requirements of CTR12/CTR13 on E1 PCM lines. These standards cover essential requirements for the physical and electrical characteristics of the terminal equipment interface for unstructured leased lines (U2048S) and structured leased lines (D2048S). Compliance with these requirements does not guarantee end-to-end interoperability.
Compliances for other regions/countries

For countries outside Europe and the Americas, the requirements of European countries usually apply. It is impossible to list all the applicable approvals or compliances as they depend on the markets and products concerned. Contact your local Alcatel-Lucent representative for more information.
Operating conditions
The product compliance standards mentioned above are based on the following conditions: Doors must be closed and (or) covers must be in place. External cables must be of the same type as specified by Alcatel-Lucent. The mechanical and electrical characteristics of the product must not be modified in any way.
Any changes or modifications made to the product without written approval from Alcatel-Lucent releases Alcatel-Lucent from responsibility regarding standards compliance.
Cable specifications
Compliance with these standards was verified using cables as specified by Alcatel-Lucent. The continued compliance of the product relies upon use of the correct cabling scheme as well as use of identical type cables as specified by Alcatel-Lucent. Refer to the installation guides for details on cable specifications.
Product labeling
The label can be located on the inside or the outside of the product, provided that the operation and/or maintenance personnel have the information when working on the product. American countries (North and South). Not applicable. European Union countries. This module gives the regulatory information specific to the European Union countries for the RNC and the BTS.
RNC labeling
To indicate compliance with European directives (EMC and low voltage), the UMTS RNC bears the following label in a visible location:
Manufacturer name Equipment designation Nominal voltage operating range and maximum rated current
Labeling for other regions/countries

Product labels appear for other regions and countries as appropriate and required by the local regulatory framework.
UTRAN introduction
The UTRAN is composed of several Radio Network Subsystems (RNS). An RNS covers a certain geographical area. It is equivalent to the GSM BSS. Each RNS consists of one Radio Network Controller (RNC) and at least one Node B. RNSs are interconnected through the Iur interface of each RNC to form a network.
Alcatel-Lucent UTRAN
The Alcatel-Lucent UTRAN is based on the following components: the UMTS RNC the UMTS BTS the W-NMS for the OAM part
The UTRAN release is RAN 5.1.
UMTS RNC
The UMTS RNC product range consists of the UMTS RNC 1000 and the UMTS RNC 1500. Both are 3GPP-compliant UMTS RNCs developed by Alcatel-Lucent. The UMTS RNC 1000 is based on the Multiservice Switch and C-Node platforms. The UMTS RNC 1500 is based on the Multiservice Switch platform. The RNC supports mobility between UMTS and GSM networks.
Main RNC functions

The main functions of the RNC are to control and manage: the Radio Access Network (RAN) the signaling between Core Network (CN) components and the Radio Network System (RNS) the Node Bs and their corresponding radio resources
RNC interfaces
The RNC provides the following interfaces: Iub interface towards a Node B Iu interface towards the Core Network Iur interface towards another RNC Iupc interface towards a Standalone A-GPS SMLC (SAS)
UMTS BTS
The UMTS BTS is the 3GPP-compliant UMTS Node B developed by Alcatel-Lucent. The generic term BTS designates the Alcatel-Lucent UMTS Internet Base Transceiver Station (UMTS BTS).
Main BTS functions

The BTS supports the following main functions: network interface management radio access call processing configuration and supervision synchronization performance monitoring
BTS interfaces
The BTS provides the following interfaces: Iub interface towards a RNC Uu interface towards a UE
10
Figure 1 Alcatel-Lucent UTRAN architecture example
W-NMS
The Wireless Network Management System (W-NMS) delivers an integrated UMTS management platform through which all Network Elements (NEs) are monitored and controlled. It provides the complete end-to-end management solution for UMTS networks. The W-NMS manages the entire UMTS network which is divided into the UTRAN and core (circuit and packet) areas.
11
The Access Network OAM manages the UTRAN part of the network.
Main Access Network OAM functions

The main functions of the Access Network OAM are the following: fault management configuration management performance management
NSP
The Network Services Platform (NSP) is a graphical user interface to the Access Network, providing a common platform for navigation and control. The NSP interfaces with the NEs through a Common Object Request Broker Architecture (CORBA). This vendor independent architecture links computer applications across different networks.
12
RNC 1500 basic characteristics

This part describes the basic characteristics of the RNC. It contains the following sections: RNC 1500 introduction RNC 1500 features and functionalities RNC 1500 configurations
13
6.1
RNC 1500 introduction

The 3GPP-compliant UMTS RNC developed by Alcatel-Lucent is called the UMTS RNC 1500. The RNC 1500 is based on a multi-service data platform called Nortel Multiservice Switch 15000. This is a single-shelf, single-platform product that occupies the lower part of the cabinet. The RNC 1500 houses four connectivity options: for North American regions: DS3 OC-3 for all regions except North America: E1 STM-1 The E1 option requires the use of a Point Of Concentration (POC). See RNC-SDH with POC, which is based on either the Nortel Multiservice Switch 7480 Multiservice Switch or the 15000 Multiservice Switch. Most RNC interfaces support multi-vendor solutions. The main part of the RNC is built upon the Nortel Multiservice Switch 15000 technology. The main functions of the RNC are to control and manage: the Radio Access Network (RAN) the signaling between the different Core Network (CN) components and the Radio Network System (RNS) the Node Bs and their corresponding radio resources
Multiservice Switch 15000 general description

The RNC 1500 Interface Node is based on the Nortel Multiservice Switch 15000 equipment, which is in turn based on the Nortel Multiservice Switch (Passport) Carrier Release (PCR) 7.2. This provides the connectivity of the user plane with a large array of interfaces. For example: connection of the RNC to the Wireless Gateway (WG) through STM-1 optical fibers connection of the RNC to POC/IMA Terminating Equipment through STM-1/OC-3 optical fibers
The Multiservice Switch 15000 supports : IP/ATM protocols voice services
14
The RNC 1500 is designed for indoor deployment. As it is EMC-compliant, no rack enclosure is necessary. EMC compliance is performed on each shelf assembly.
Product upgrade from RNC 1000

The RNC 1500 is an upgrade of the RNC 1000. It is 50% smaller, simpler to operate, but retains all the functionalities, capacity, performance and reliability of the RNC 1000. The RNC 1500 is based on the same hardware platform as the RNC 1000 Interface Node. The RNC 1500 program consists the removal of the Control Node and associated modules, as well as the porting of Control Node software, mainly to the Packet Server FPs. As a result, all RNC 1000s can be easily upgraded to the RNC 1500 using a seamless migration procedure.
RNC 1500 external interfaces

The RNC 1500 houses the following external interfaces: Iu interface: towards the Core Network Iub interface: towards the Node B Iur interface: towards another RNC Iupc interface: towards the SAS OAM interface: towards the network management platform (W-NMS) or the TML
RNC 1500 Functions

The RNC 1500 has three main functions: Serving RNC (SRNC) refers to a specific mobile. This is the RNC handling the Iu interface for this particular mobile when the Iur interface is used. Drift RNC (DRNC) refers to a specific mobile. This is the RNC controlling the NodeB used by this mobile when the Iur interface is used. Controlling RNC refers to the Node Bs. This RNC is controls all the base stations parented to it.
RNC 1500 general view

These figures for the following views: RNC 1500 front view with two RNC 1500 shelves in the cabinet RNC 1500 rear view with one RNC 1500 in the upper shelf
15
Figure 2 RNC 1500 front view with two RNC 1500 shelves (dual RNC) in the cabinet
16
Figure 3 RNC 1500 rear view with one RNC 1500 in the upper shelf
RNC 1500 general and physical characteristics

Characteristics WxDxH Without cosmetic panels WxDxH With cosmetic panels Unit of measure (mm) (inches) (mm) (inches) RNC 1500 600 x 600 x 2125 23.6 x 23.6 x 83.7 660 x 600 x 2125 25.7 x 23.6 x 83.7
17
Maximum weight Voltage
(kg/lb) (V)
329 / 724 -48(DC) (-57 DC to -43 DC) 1939
Maximum power for maximal con- (W) figuration, consumption depends on the configuration Maximum heat dissipation Normal heat dissipation Normal operating temperature Short-term operating temperature Temperature variation Normal relative operating humidity (non-condensing) (W/m2) (W) (C), (F) (C), (F) (C/h), (F/h) (%)
2580 Not available 5 to 40 , 41 to 104 -5 to 50 , 23 to 122 30 , 86 10 to 90
Short-term relative operating humid- (%) ity (non-condensing) Maximum noise level Earthquake dBA
5 to 90
Less than 60 Up to zone 4
RNC 1500 office layout and footprint

The layout of the RNC 1500 requires: a minimum ceiling clearance of 2.4 m a minimum safety distance for front and rear maintenance activities of 0.9 m
When two RNC are placed side by side, only the first and the last frame in the lineup of the cosmetic panels between the two frames are installed. A junction with the cabinet secures the two adjacent frames to each other. The footprint of the RNC 1500 requires: 600 mm W x 600 mm D = 0.360 m2 without cosmetic panels 660 mm W x 600 mm D = 0.396 m2 with cosmetic panels
18
6.2
RNC 1500 features and functionalities

The RNC 1500 supports all the interfaces defined by 3GPP for UMTS and provides industry-leading capacity and performance for operators. The RNC 1500 is located on a platform that is deployed globally across wireless and high-speed packet networks. The RNC 1500 supports the following features: High Speed Downlink Packet Access (HSDPA) support high capacity distributed architecture a large variety of transmission interfaces differentiated services proven carrier grade scalability simple but powerful OAM
HSDPA support
UMTS RNCs are HSDPA ready. HSDPA is a UMTS packet air interface to enable high speed downlink packet access. There is no need for new boards. A software upgrade may be required.
High capacity
The RNC 1500 supports a high capacity per shelf solution. It is based on off-the-shelf processing technology. In this way, the operator can upgrade the RNC by just upgrading boards as opposed to employing a fork-lift solution. This provides investment protection for the operator.
Wide range of transmission interfaces

A variety of transmission interfaces and traffic grooming functions are integrated for ingress into the RNC 1500 from the Node B. This provides a flexible the transmission architectures. In the RNC 1500 architecture, this translates into decoupling the radio functions from the transmission functions. The radio functions are further decoupled in the Control Plane (CP) and the User Plane (UP). This architecture ensures that the transmission does not limit the radio functions.
Differentiated services
The RNC 1500 is equipped with enhanced Radio Resource Management (RRM) algorithms built on Alcatel-Lucent CDMA and data experience. This enables telecommunication carriers to differentiate customers such as gold, silver, and bronze, and to differentiate services. Telecommunications
19
carriers can optimize the spectrum to match their respective market demographics to meet/exceed their business objectives.
Proven carrier grade

The use of the Multiservice Switch 15000 guarantees high availability based on RQMS specification. RNC 1500 supports the following features: 1+1 hot sparing of critical elements hot insertion of additional processing boards load balancing between processing resources N+P load sharing of traffic processors high component MTBF
Scalability
The RNC supports scalable growth from a minimum configuration at network launch to full capacity configuration through software upgrades and interface board additions. In this way, telecommunication carriers can optimize investment by making capacity upgrades on customer demand only.
Simple but powerful OAM

The Alcatel-Lucent solution is based on providing a simple and intuitive OAM W-NMS that performs efficient cross-checks to guarantee proper provisioning. The interface between RNC and W-NMS is Ethernet TCP/IP in case of Out of band OAM. The Out of band OAM consists in using a separate network for OAM and traffic. For more information about the OAM W-NMS see: W-NMS Engineering Guide (NN-20500-046)
RNC 1500 functions

RNC 1500 functions cover the: Control Plane User Plane
Control Plane
The C-Plane includes all of the functions required to set up, remove, and manage connections between the User Equipment (UE) and the Core Network. Typically, Control Plane functions involve signaling channels and consume RNC resources as a result of external events, such as call origination or handoff between Node Bs. The C-Plane handles:
20
protocol termination for RANAP, RNSAP, NBAP, and ALCAP radio resource management for RRC terminations, RRM strategy, and QoS management logical management of the Node Bs connected to the RNC admission control, communication, maintenance, and release for each user setup, maintenance, and release of transport network resources optimization of the radio spectrum and terrestrial transport network resources to provide a maximum number of simultaneous users according to their service requirements within the UTRAN RNC operations, administration, maintenance, and provisioning (OAM&P) Node B logical OAM&P mobility management
User Plane
The U-Plane is responsible for maintaining the data flow of traffic over three interfaces: It provides the data interface to the U-Plane of the Iu link to the Core Network. It provides the data interface to the Iub links to the Node B and the Iur links to other RNCs it terminates the MAC and RLC radio protocols for the data links between the RNC and UEs.
The U-Plane processing provides radio protocol stacks for radio bearers and associated transport channels and maintains User Plane logical contexts for individual cell contexts and UE calls. The User Plane handles: physical connectivity with the other UMTS nodes based on ATM over PCM trunks or higher speed interfaces (OC-3 or STM-1) User Plane radio protocol termination UTRAN packet switching between the Core Network and the user's terminal
21
6.3
RNC 1500 configurations

This section presents the RNC 1500 configurations.
RNC 1500 configuration

The RNC cabinet can be connected to the UTRAN according to the following configuration types: RNC-SDH/SONET: used in UMTS 2100 and UMTS 1900 respectively, with the RNC SDH-x and RNC SONET configurations. RNC-SDH with POC: used in the UMTS 2100 with the PCM-x configuration
RNC-SDH/SONET
The RNC-SDH/SONET is housed in a single cabinet which contains the Multiservice Switch 15000 in the lower shelf. This configuration allows the operator to directly connect the RNC to the Node Bs through the Iub interface based on a STM-1/OC-3 optical link up to the ATM backbone. In this case, an optical STM-1 connectivity is provided on Iub, Iur, and Iu. For more information about the RNC-SDH/SONET, refer to RNC hardware presentation. With this configuration, it is possible to add a second RNC 1500 in the free upper shelf.
RNC-SDH with POC

This configuration allows the operator to connect the RNC to the Node Bs through the POC. This solution offers E1 connectivity along the Iub interface.
Point of Concentration (POC)

The POC is based either on Nortel MSS7k or Nortel MSS15k. This enables connection of RNC and Node-Bs on the Iub interface in RNC-SDH configurations. Several RNCs can be connected to the same POC. The POC is not an RNC 1500 integrated product, but it can be hosted in the RNC 1500 cabinet. The following configurations are possible: RNC1500 VSS with 7k POC: one RNC1500 shelf assembly and one MSS 7k POC in the same frame, in the upper shelf of the cabinet RNC1500 VSS with 15k POC: one RNC1500 shelf assembly and one MSS 15k POC in the same frame, in the upper shelf of the cabinet Standalone 7k POC: one MSS 7k POC in the lower shelf of the frame. Termination/sparing panels are installed in the same frame, in the upper shelf.
22
RNC 1500 model names

The RNC 1500 model name indicates the number of Packet Servers (PS_FPs) (see Packet Server module hardware). The following table shows the configurations possible and the number of BTSs and cells controlled by the RNC. Table 1 RNC 1500 SDH/SONET market models Market Model 1504 1506 6 PS_FP 1507 7 PS_FP 1510 10 PS_FP 1512 12 PS_FP
RNC 1500 Number 4 PS_FP of PS_FPs Node B Cells 80 360
120 600
140 720
200 1200
200 1200
23
RNC 1500 general architecture

This section describes the RNC 1500 general architecture, and more precisely the Multiservice Switch 15000 architecture. The RNC 1500 cabinet contains the Multiservice Switch 15000 in the lower shelf. The following figure shows the RNC 1500 architecture.
24
Figure 4 RNC 1500 architecture
25
Multiservice Switch 15000 architecture

The Multiservice Switch 15000 houses the main types of processing unit in the following modules: 16p OC-3/STM-1 CP3 Fabric Packet Server
12 Packet Servers (PS) can be hosted in the full RNC 1500 configuration. The Packet Server board contains six PCI Mezzanine Cards (PMC). The PSs work with load sharing redundancy; a portion of each PS load is reserved to take over processing capacity if one PS fails.
Roles of the PMC

This section describes the roles of the PMC.
Master (PMC-M)
There are two PMC-Ms per RNC: manages all other PMCs contains the Resource and Transport Manager PMC-Ms are 1+1 spared: 1 active and 1 standby per RNC and on separate PSs
Protocol Converter (PMC-PC)

There is one PMC-PC per Packet Server and a maximum of 12 per RNC: Segmentation and Reassembly (SAR) functions to do IP/AAL2 to IP/AAL5 conversion and vice versa Load sharing redundancy
Radio Access Bearers (PMC-RAB)

There are up to 40 PMC-RABs per RNC: High touch bearer processing. Radio Protocol Handling (MAC, RLC), Interface bearer, Macro Diversity Handover Load sharing redundancy
Network Interface (PMC-NI)

There are two PMC-NI per RNC: hosts the functionality of the MTP3b and SCCP layers of the SS7 stack PMC-NIs are 1+1 spared: 1 active and 1 standby per RNC and must be on separate PSs
26
Traffic Management units (PMC-TMU)

There are up to 14 PMC-TMUs per RNC: TMU-R FP software is ported to this PMC. Terminates Radio Network interface protocols : RANAP, RNSAP, NBAP. Support RRM, Always-on, QoS Management, Call Admission, iRM scheduling. PMC-TMUs are shared N+P.
OAM Management units (PMC-OMU)

There are two PMC-OMU per RNC: Equivalent to OMU function on RNC 1000. Manages Control Plane functions on the RNC 1500 (equivalent to PMC-M of User Plane for centralized maintenance functions): Performance, Configuration and Fault Management. Call Trace Management. Overload control and load balancing of plane resources. Radio Network Subsystem OAM&P. PMC-OMUs support 1+1 hot redundancy.
27
RNC 1500 services and features

This section describes: RNC 1500 main features RNC 1500 main characteristics RNC 1500 radio resource management other RNC 1500 features
28
8.1
RNC 1500 main features

The RNC 1500 main features are: ability to handle varying traffic loads adaptability to different equipment structures easy operation: all modules have the same visual indicators. network connections are concentrated in a unique and easy access cable transition unit. path finding is used to illuminate a fault module a robust and scalable platform: star architecture This provides accurate and immediate fault detection. fault tolerance scheme This provides fast fault recovery by reconfiguring software activity on the active modules. traffic model independent of the RNC N+P redundancy (the nominal capacity is preserved with P failures) load balancing Load balancing provides the distribution of processing over the modules for optimal use of resources. scalability Possibility to plug a new processing module to increase capacity of the RNC cabinet. plug and play: easy hardware maintenance or extension by extracting or inserting modules hot module insertion or extraction without service interruption
29
8.2
RNC 1500 main characteristics

This section gives a high-level presentation of the RNC 1500 main characteristics: RNC 1500 functions RNC 1500 processing units RNC 1500 capacity and dimensioning RNC 1500 hardware sparing
RNC 1500 functions

The RNC 1500 is fully redundant. It provides the following main functions: Radio Resource Management (RRM) to: process radio accesses process measurements from UEs and Node Bs allocate radio channels (for traffic and signaling) monitor radio channel operating states launch the power control procedures launch the handover procedures Call processing to: set up and release terrestrial and radio links (for traffic and signaling) set up the radio bearer transfer the signaling messages between the UEs and the CNs transfer the speech data channels between the UEs and the CNs Node B management to: set physical channels set the transport channels provide Node B reconfiguration, if needed update system parameters RNC 1500 security to: detect and correct failures and operating anomalies provide robustness by isolating faulty units, to avoid problem spreading provide equipment unit reconfiguration using redundant units. These functions include module switching and restart mechanisms.
30
RNC 1500 processing units

The RNC 1500 software architecture is based on a set of processors called a "core system" that can be tailored to fit into different hardware structures. The core system is divided into logical processing units. A set of modules houses boards and processors and provides each logical unit with the processing power it needs.
Multiservice Switch 15000 processing units

The main types of processing units for the Multiservice Switch 15000 are as follows: CP3 modules to manage: the Preside Wireless Platform access (MDM) and the related function each process in the Multiservice Switch 15000 Packet Server modules to provide: UMTS User Plane services: service communication, AAL2 switching, cells radio bearer processing and UEs radio bearer processing Communication services to the other RNC 1500 interfaces, cell and UE radio bearer allocator and transport bearer allocator RMAN: Resource MANager) Traffic management (TM) Policing Service interworking ILS, PVC and SVC services Operation and maintenance Performance management Billing/accounting Provisioning Scalability Virtual Path Terminology (VPT) Fault/traffic management Sparing 1+1 and N+1 for the PMCs 16p OC-3/STM-1 modules to provide: 16 single-mode ports that support either User-Network Interface (UNI) or ATM Multiservice Switch-Multiservice Switch interface for each OC-3/STM-1 port; The Fabric modules to provide: the centralized resources required to support the Multiservice Switch 15000 applications
31
RNC 1500 capacity and dimensioning

The RNC 1500 was designed to increase operator revenue and decrease costs. Product performance is key to these objectives and is based on: a high-capacity platform, providing reduced footprint and reduced price per Mbit/s scalability, enabling a 'Pay as you grow' approach flexibility, addressing deported and centralized deployments
The main dimensioning factors of the RNC 1500 are: Coverage: number of NodeB and cells supported by the RNC Connectivity: E1 & STM-1 Capacity: real time capacity is a function of the call model and is expressed in terms of users and/or throughput.
The RNC 1500 maximum configuration is as follows (1 shelf with 12 PSs) : 200 Node Bs per Serving RNC 1200 cells per Serving RNC All voice: Service = Speech Bearer = CS 12.2 AMR Simultaneous TRB subscribers (Erlang) = 3900 Referenced subscribers = 220,000 All data: Service = Mobile Office Internet Bearer = PS 64/128 Referenced subscribers = 400,000 Iu Mbps/s application layer = 140
RNC 1500 hardware sparing

Power is 1+1 Fans have a backup capacity in case of failure CP3 is 1+1 hot redundancy PMC-M is 1+1 hot redundancy if the active PMC-M fails, the standby PMC-M becomes active no impact on established cell and UE calls, but no new calls for two seconds ( OMU must recognize the PMC SWACT and update the links) PMC-NI is 1+1 hot redundancy
32
if the active PMC-NI fails, the standby PMC-NI becomes active. no impact on service PMC-OMU is 1+1 hot redundancy: one active and one standby In case of CP switchover, an PMC-OMU SWACT is forced. PMC-TMU is N+P redundancy cells are recreated on the spare PMC-TMU there is no service interruption to cells UE calls are lost PMC-RAB load is shared with remaining PMC-RABs after failure UE calls on faulty PMC-RAB are lost, whereas cells are maintained due to sparing PMC-PC load is shared with remaining PMC-PCs after failure paths on faulty PMC-PC are maintained due to sparing 16pOC-3/STM-1 has 1+1 LAPS switchover to standby 16pOC-3/STM-1 module or port no impact on service, cell or UE calls can lose packets but they are not dropped upgrade with 1 minute predicted HSM outage while all paths are re-boud Switch Fabric has 1+1 load sharing both Fabric modules are working simultaneously no outage if one Fabric fails
33
8.3
RNC 1500 radio resource management

This section describes the RNC 1500 radio resource management functions. Alcatel-Lucent Radio Resource Management (RRM) is an essential part of the RNC 1500 software that controls allocation and maintenance of radio resources during communication. Efficient radio resource allocation and management guarantees QoS and offers high capacity. The main functions related to Alcatel-Lucent's RRM solution are: Admission control Congestion control Power control Radio measurements
Admission control
The admission control function admits or denies new users. Alcatel-Lucent's admission control mechanism consists of two main steps: RAB Matching :This performs the mapping of the requested RAB onto a supported Radio Bearer (RB) configuration. This step includes a RAB to Radio Bearer mapping table which provides the means to admit a RAB at a rate lower than the requested Maximum Bit Rate (MBR) according to the cell load. This function, which is called intelligent RAB Mapping (iRM), only applies to a RAB with an Interactive or Background Traffic Class (TC). Call Admission Control (CAC): This is the function located in the CRNC responsible for deciding whether a request to establish a Radio Access Bearer (RAB) can be admitted in the UTRAN or not based on the available resources. Radio CAC is based on power and OVSF codes in the downlink and on interference in the UL (note that other CAC functions are performed at the transport, NodeB and RNC levels). CAC is applied: On initial admission On RB reconfiguration: such as RB bit rate downgrading/upgrading, CELL_FACH to CELL_DCH transition, etc... On mobility: SHO, inter-frequency HHO and 2G to 3G HHO The Univity RNC component of QoS negotiation includes an RAB matching function that allows the Univity RNC to map the RAB requested by the Core Network to an appropriate provisioned RB. This function ensures proper interoperability on the Iu interface for all requested data rates and maximizes the success rate of the RAB assignment procedure. With intelligent RAB Mapping (iRM), a downsized Radio Bearer can then replace the selected Radio Bearer, depending on cell loading and subscriber priority (OLS). Alcatel-Lucent iRM maximizes the number of subscribers and multimedia services within the
34
available frequency spectrum and minimizes blocking of subscribers at peak times. The operator stimulates traffic outside of peak times thus increasing revenues and customer satisfaction.
Congestion control
This function monitors, detects and handles situations when the system is approaching an overload level with the already connected users. Alcatel-Lucent's congestion control works in two ways: It takes preventive actions to avoid overload using iRM In the event of overload, congestion handling mechanisms bring the system back to normal levels using iRM pre-emption
Power control
This group of functions controls the level of transmitted power to minimize interference and keep the quality of the connections. Alcatel-Lucent supports: DL and UL Outer Loop Power Control DL and UL Inner Loop Power Control and DL power balancing UL Open Loop Power Control
Radio measurements
This function performs measurements on radio channels (located in UE and UTRAN). The UTRAN processes these measurements and uses them for RRM.
Other functions
With the Alcatel-Lucent RRM solution, the operator can make the best use of its radio resources with the following functions: Switch from CELL_DCH to CELL_FACH (and vice versa) based on user activity (Always-On feature) RB bit rate downgrading and upgrading based on radio conditions (iRM scheduling feature)
35
8.4
Other RNC 1500 features
IMA
IMA transports an ATM cell stream over a number of physical links and preserves sequencing and integrity. ICP cells are introduced every 128 cells to frame the payload over the different links. In the Node B, the ATM switching matrix generates a cell stream that is framed with ICP cells and rate adapted with filler cell, then the cells are mapped in round-robin fashion over the E1/T1 span. The original stream is then reassembled at the RNC 1500 or other IMA terminating equipment. The IMA provides for constant physical monitoring including CRC-10 and CDV. When a link does not meet the quality criteria, it goes out of service and falls into a fast, medium, or slow recovery mode all managed by the IMA state machine. To compensate for delays, stuffing events are introduced in the cell stream.
Security features
The security is a major concern for all parties involved in the telecommunication: from subscriber to the service provider, including the wireless access network operator. The RNC 1500 provides two mechanisms to ensure the integrity and confidentiality of message exchange between the UE and the network: integrity protection ciphering of radio interface messages
Integrity protection
Integrity protection of the radio interface is a mandatory requirement for the UMTS. Integrity protection applies to signaling messages but not to user traffic data. This mechanism is supported by the RNC 1500, it ensures that the messages received by one party in the dialogue come from the expected remote party and prevents use of a false BTS.
Ciphering
The Ciphering mechanism ensures confidentiality of signaling message and user traffic data. It makes the content of the messages exchanged unreadable to external parties other than the two sides of the dialogue. Ciphering is performed in the RNC 1500 for the CS domain and for the PS domain.
36
RNC 1500 interfaces and protocols

This section presents the RNC 1500 interfaces and protocols.
37
9.1
RNC 1500 interfaces

The external interfaces of the RNC 1500 are as follows: Iu towards the Core Network Iur towards another RNC Iub towards the iBTS Iupc towards the SAS OAM interface towards the network management platform (W-NMS) or the TML
The Interface Node provides the UTRAN interfaces (Iu, Iub, Iur). Iu, Iub, and Iur are all open, multi-vendor, standard interfaces based on ATM layer 2 protocols for UMTS release 99. The following figure shows these interfaces. Figure 5 RNC 1500 interfaces
The SS7 stack on the RNC is currently used on both the Iu link between the Core Network and the RNC, and on the Iur link between neighboring RNC nodes.
38
Iu interface
The Iu interface is an open interface between the Access Network and the Core Network. In the Alcatel-Lucent solution, this is the interface between the RNC and either SGSN (for the packet domain) or MSC (for the circuit domain). On this interface, the SCCP supports transport of RANAP messages used by the Control Plane. The signaling bearers in the Radio Network Control Plane for Iu-CS are MTP3b/SSCF-NNI/SSCOP/AAL5 over ATM. Figure 6 Iu CS protocol view
39
The signaling bearers in the Radio Network Control Plane for Iu-PS are MTP3b/SSCF-NNI/SSCOP/AAL5 over ATM. Figure 7 Iu PS protocol view
Iur interface
The Iur interface supports traffic exchange between RNCs inside the UMTS network. The Iur Interface between the neighboring RNCs is required by 3GPP standards. The Iur interface is an open interface and facilitates the interconnection of RNCs from different vendors.
40
The Iur interface has the following functions: Transport network management Traffic management of transport channels
On this interface, SCCP supports transport of RNSAP messages used by the Control Plane. The signaling bearers in the Radio Network Control Plane for Iur are MTP3b/SSCF-NNI/SSCOP/AAL5 over ATM. Figure 8 Iur protocol view
41
Iub interface
The Iub interface is between the RNCs and the Node B. This interface is equivalent to the GSM Abis O&M and RSL. As opposed to GSM, this interface is partially compliant with the 3GGP standard. The main difference with the Iub interface in the 3GGP standard is use of proprietary extensions over NBAP for the management of the AAL2 connections instead of the use of ALCAP. The NBAP is the control protocol used between Node B and RNC. ALCAP is not supported on the Iub Interface. The signaling bearers in the Radio Network Control Plane for Iub are SSCF-UNI/SSCOP/AAL5 over ATM.
42
Figure 9 Iub protocol view
Iupc interface
Iupc is the interface for Assisted Global Positioning System (A-GPS) location services. The Network A-GPS in UMTS04 locates the geographical position of a mobile with A-GPS positioning technology. To support this technology, the UE is equipped with a GPS receiver and the RNC is connected to a standalone A-GPS Serving Mobile Location Center (SMLC) (SAS).
43
Figure 10 Iupc protocol view
OAM interface
The OAM interface connects the RNC to the OAM access or W-NMS. The OAM interface is also used to connect the TML. This interface uses an Ethernet link. The OAM access or the TML can be connected to the CP3 module.
OC-3/STM-1
The OC-3/STM-1 optical fibers support the Iu, Iur, and Iub interfaces. They consist of two physical SONET/SDH interfaces configured as OC-3/STM-1. Its main function is to perform all physical layer
44
functions in the RNC. This includes SONET/SDH overhead processing and transmission convergence.
IuPC interface
The IuPC interface is the logical interface for the interconnection of the SAS and RNC. The IuPC interface according to the 3GPP standard, enables SRNC and SAS to exchange information related to positioning data. The IuPC interface carries Positioning Calculation Application Part (PCAP) information between the SAS which provides information and processing for assisted position calculation, and the RNC, which communicates between the UE and the Core Network.
45
9.2
RNC 1500 protocols

This section provides a high-level presentation of the two RNC 1500 protocols : User Plane (U-Plane) protocols Control Plane (C-Plane) protocols
User Plane (U-Plane) protocols

The main protocols used for communication on the user plane are respectively: Circuit Switched (CS) domain Packet Switched (PS) domain
The user plane carries all types of user information, such as: user data information user control information
To carry information on the Iu (Iu-CS and Iu-PS), Iub, and Iur interfaces, specific frames are built. These frames are carried in AAL2 frames, except the Iu PS interface where the GTP/UDP/IP/AAL5 protocol is used as a transport layer. This is called Frame Protocol (FP). They consist of a header and a payload. The header contains the following information: a checksum the frame type field information related to the frame type
The payload contains either control or data information. The Iub uses Frame Protocol to carry: dedicated information common information
When dedicated user data information is carried, at the same time a "Quality Estimate" parameter is sent to indicate if the payload is good (or bad) from a radio point of view. Dedicated user control information can be used to transport "outer loop power control" parameters.
Control Plane (C-Plane) protocols

The main protocols used by the Control plane are as follows: Radio Access Network Application Protocol (RANAP) Node B Application Protocol (NBAP)
46
Radio Network Subsystem Application Protocol (RNSAP)
RANAP
The RANAP is used on the Iu, between the RNC and Core Network for the CS domain or the PS domain. This is an evolved GSM BSSMAP protocol. It performs the following main functions: RAB management relocation of an S-RNC transport of NAS signaling messages paging controlling the security mode location reporting
NBAP
The NBAP is used on the Iub, between the RNC and the Node B. It performs the following main functions: cell configuration management radio link management and supervision measurements on common and dedicated resources system information management
RNSAP
The RNSAP is used on the Iur, between the two closest RNCs. One is used as the Server RNC (S-RNC) and the other as a Drift RNC (D-RNC). It performs the following main functions: radio link management physical channel reconfiguration relocation execution measurement on dedicated resources paging
47
10
RNC 1500 hardware

This section describes the RNC 1500 hardware. It contains the following sections: RNC 1500 hardware presentation RNC 1500 hardware modules description RNC 1500 cooling system description RNC 1500 power supply and alarm system
48
10.1
RNC 1500 hardware presentation

This section presents the main RNC 1500 hardware configurations. The RNC 1500 has the following configurations: RNC-SDH/SONET is used in the UMTS 2100 and the UMTS 1900 respectively, with the RNC SDH-x and RNC X SONET configurations. RNC-SDH with POC is used in the UMTS 2100 with the PCM-x configuration
RNC 1500 cabinet

The RNC 1500 cabinet contains the following components: a Multiservice Switch 15000 a cooling system a power-alarm system
See these figures for the following views: RNC 1500 components layout on the front panel RNC 1500 components layout on the rear panel RNC 1500 modules on the front panel RNC 1500 modules on the rear panel
49
Figure 11 RNC 1500 components layout on the front panel
50
Figure 12 RNC 1500 components layout on the rear panel
51
Figure 13 RNC 1500 modules on the front panel
52
Figure 14 RNC 1500 modules on the rear panel
53
Multiservice Switch 15000

The Multiservice Switch 15000 houses the following modules on the front panel: CP3 module 16p OC-3/STM-1 (16-port OC-3/STM-1) 6mPktServ FP (or PS FP) (Packet Server Frame Processor) Filler modules (dedicated to the Multiservice Switch 15000)
The Multiservice Switch 15000 houses the following modules on the rear panel: MAC address Alarm BITS PIM (Power Interface Module) Fabric module
Cooling system
The cooling system is mounted in the center of the frame. For the Multiservice Switch 15000, the cooling system is arranged in a push-pull configuration: cool air is drawn through the bottom shelf and expelled out the back of the frame (the cooling unit acts as a baffle to deflect air horizontally out the back of the frame). The lower cooling unit fans expel air while upper cooling fans draw air in. The cooling unit of the Multiservice Switch 15000 is made up of three field replaceable fans with a controller. If one fan fails, an alarm is generated. If the temperature reaches an unacceptable level, the fan speed increases.
Power supply and alarm systems

Redundant -48 V dc feeds with independent ground return terminate on the Breaker Interface Panel (BIP). The BIP provides low pass filtering reducing conducted emission on the battery feeds and distributes the main battery feeds across five Breaker Interface Modules (BIM). The two BIMs, including four breakers each, power the Multiservice Switch 15000 and the corresponding cooling unit. For each node, one BIM is operational and the second one provides redundancy in case of breaker failure.
POC Hardware Presentation

The POC platform is built upon either Nortel Multiservice Switch 7480 technology (7k POC) or Nortel Multiservice Switch 15000 technology (15k POC). The 7k POC shelf assembly houses the following components: 2pOC-3 STM-1 modules MSA32 modules (only single-slot modules are used)
54
CP2 modules (Control Processor) power supply assemblies cooling unit assembly
The 15k POC has the same architecture as the RNC 1500 shelf with the exception of the Packet Server. Therefore, it has the following components: CP3 module 16p OC-3/STM-1 (16-port OC-3/STM-1) 4p DS3 (4-port DS3)
Only the 7kPOC can be used alone in a single frame. In this case, it is called Standalone 7kPOC. In this configuration, the 7kPOC is located in the lower part of the cabinet. The upper part houses the following components: for the 120-ohm or 75-ohm E1 PCM links, 154 E1s are supported with Inverse multiplexing on ATM (IMA) mode for the E1 PCM links, 224 E1s are supported without IMA mode
See these figures for the following views: Standalone 7k POC modules front view for 120-ohm PCM E1 links Standalone 7k POC modules front view for 75-ohm PCM E1 links 15k POC modules front view
55
Figure 15 Standalone 7k POC modules front view for 120-ohm PCM E1 links
56
Figure 16 Standalone 7k POC modules front view for 75-ohm PCM E1 links
57
Figure 17 15k POC modules front view
58
10.2
RNC 1500 hardware modules description

This section describes the hardware modules that are housed into the RNC Interface Node. It contains the following sections: Control Processor (CP3) module 16p OC-3/STM-1 module Packet Server FP (PS FP) module Fabric module LED description for Interface Node module
59
10.2.1
Control Processor (CP3) module
This section describes the hardware of the Multiservice Switch 15000 CP3 module. It contains the following subsections: CP3 module presentation and functions CP3 module external interfaces CP3 module electrical interfaces
CP3 module presentation and functions

The Control Processor (CP3) performs the following functions: manages all Multiservice Switch resources interfaces with the MDM/MDP management system contains a local disk for loads and logs
The CP3 processor is a Motorola PowerPC 755 at 400MHz with 256MB of RAM. The CP3 is provisioned in a 1+1 redundancy scheme and uses a proprietary operating system built on VxWorks. The hard disk in the CP3 module is 20G. The CP3 module is responsible for the following functions: Control of base Interface Node functions such as loading, fault detection and sparing Control over ATM PVC connections on the external interfaces Disk management Ethernet access to MDM/MDP via TCP/IP IP routing function for OMC-B/Node B links
CP3 module external interfaces

This section provides a high-level presentation of the CP3 module interfaces: on the front panel on the backplane
Front panel
The CP3 module front panel is composed of the following components and connectors: two visual indicators (LEDs) one RJ45 connector that provides 10BaseT Ethernet access through TCP/IP to the TML or 100BaseT Ethernet access through TCP/IP to W-NMS. The CP3 module can be connected directly or through one or two optional HUBs.
60
The following figure shows the CP3 module front view: Figure 18 CP3 module: front view
61
Backplane
The backplane of an CP3 module is composed of the following components: packet link redundancy redundant - 48 V dc links one Slot ID
CP3 module electrical interfaces

This module is powered by the -48 V dc, which comes from the operator boxes through the BIP frame assembly and PIM modules. It houses the following components: a dc/dc converter, which provides power to each component a common ground for each board a fixed fuse to protect each component
62
10.2.2
16p OC-3/STM-1 module
This section describes the hardware of the Multiservice Switch 15000 16p OC-3/STM-1. It is divided into the following sections: 16p OC-3/STM-1 module presentation and functions 16p OC-3/STM-1 module external interfaces 16p OC-3/STM-1 module electrical interfaces
The following figures show the 16p OC-3/STM-1 module with a closed fiber hood and an open fiber hood.
63
Figure 19 16p OC-3/STM-1: front view with closed fiber hood
64
Figure 20 16p OC-3/STM-1 module: front view with open fiber hood
65
OC-3/STM-1 module presentation and functions

The OC-3/STM-1 FP has 16 ports and is available in single mode only. This FP contains 16 OC-3/STM-1 duplex HP MTRJ or LC fiber optic transceivers and supports either one User Network Interface (UNI) or one ATM Multiservice Switch interface for each port. The FP can operate from either side of the user/network boundary. Each OC-3/STM-1 ATM port supports a line rate of 155.52Mbit/s that operates in B-ISDN mode. The OC-3 FP runs on Motorola Power PC 750 processors at 233MHz and with 128MB of RAM. It is provisioned in a 1+1 redundancy scheme and supports Automatic Protection Switching and can recover from board failure within 50 ms. Two 16p OC-3/STM-1 are available with different PEC codes. For more information, see UMTS RNC 1500 Troubleshooting Maintenance Guide (NN-20500-023). The two types of 16p OC-3 STM-1 FP modules are: 16p OC-3 STM-1 PQC based 16p OC-3 STM-1 MS3 based
The 16p OC-3 MS3 supports a line rate of up to 2.5 Gbps IP forwarding Vs 310 Mbps for the PQC based modules. The 16pOC-3 MS3 can optionally replace the existing 16pOC-3/STM-1 (PQC based). 16pOC-3 PQC and MS3 mixing and matching are not supported.
OC-3/STM-1 module external interfaces

This section gives a high-level presentation of the 16p OC-3/STM-1 module interfaces on the front panel and backplane.
Front panel
The single front panel of an 16p OC-3/STM-1 module is composed of the following components and connectors: two visual indicators (LEDs) 16 connectors for the single-mode OC-3/STM-1 optical fibers. In non RoHS modules, each connector houses the following connectors for transmission/reception: MT-RJ for 16pSTM-1 (used for UMTS 2100) LC connector for 16pOC-3 (used for UMTS 1900) The 16pOC-3 optical connection changes with RoHS. Only LC connectors are supported on the RoHS version of this module.
66
An MTRJ to LC patch cable adaptor is available to convert MTRJ cables to LC. This allows RoHS modules to be deployed with the existing MTRJ cable infrastructure. The 16p OC-3 MS3 FP has small form pluggable (SFP) optics. Each port on the FP can be individually fitted with an optical module for short-reach, intermediate-reach, or long-reach laser technology.
Backplane
The backplane of an 16p OC-3/STM-1 module is composed of the following components: packet link redundancy redundant - 48 V dc links slot ID
OC-3/STM-1 module electrical interfaces

This section presents the electrical interfaces of the 16p OC-3/STM-1. This module is powered by the -48 V dc that comes from the operator boxes through the: BIP assembly PIM modules
It houses the following components: a dc/dc converter, which provides power to each component a common ground for each board a fixed fuse to protect each component
67
10.2.3
Packet Server module hardware
This section describes the hardware of the Multiservice Switch 15000 Packet Server module. It is composed into the following sections Packet Server module presentation and functions Packet Server module external interfaces Packet Server module electrical interfaces
The Packet Server module, also called PS FP or 6-module Packet Server Frame Processor (6mPktServSP FP), is a server FP that provides services for the other interfaces in the Multiservice Switch 15000.
Packet Server module presentation and functions

The Packet Server processor is based on an internal open architecture PCI Mezzanine Card (PMC) interfaces for the daughter boards for rapid hardware upgrades and product development. Each Packet Server FP board hosts 6 PMCs. Two of these PMCs (called PMC-M, 1 active, 1 standby on a different card) are reserved for the management of all other PMCs. The Alcatel-Lucent RNC uses PMCs from two vendors, each with PowerPC 7410 (G4) processors operating at 450 MHz with 256 MB of SDRAM. The Packet Server is provisioned in a load sharing redundancy scheme. The load is shared between the PMCs with an engineering margin, whereas PMC-Ms are provisioned in a 1+1 redundancy. The Packet Server module is responsible for the following functions: High-touch Bearer processing Radio protocol handling (MAC, RLC and PDCP) Interface bearer protocols Macro-Diversity Handover (frame selection, buffering, synchronization, combining/splitting) AAL2 Segmentation And Reassembly (SAR) Translation between AAL2 and IP All C-Node functions
Packet Server module external interfaces

This section gives a high-level presentation of the Packet Server module interfaces that are located on the front panel and on the backplane.
68
Front panel
The front panel of an Packet Server module is composed of two visual indicators (LEDs). The following figure shows a hardware overview of the Packet Server module. Figure 21 Packet Server module: hardware overview
69
Backplane
The backplane of an Packet Server module is composed of the following components: packet link redundancy - 48 V dc link redundancy Slot ID
Packet Server module electrical interfaces

This module is powered by the -48 V dc which comes from the operator boxes through the BIM assembly and PIM modules. It houses the following components: a dc/dc converter, which provides power to each component a common ground for each board a fixed fuse to protect each component
70
10.2.4
Fabric module
This section describes the Fabric module. It contains the following sections: Fabric module presentation and functions Fabric module redundant backplane Fabric module control buses
Fabric module presentation and functions

The Fabric module provides the centralized resources required to support the Multiservice Switch 15000 applications. The Multiservice Switch 15000 has two 56.3 Gbit/s redundant switching fabric cards. It is connected with high speed serial bidirectional 3.2 Gbit/s links to the switching the elements that reside on each fabric module. The Fabric module operates in redundant mode. For this mode, two Fabric modules are used. Both Fabric modules contain identical information and are connected to each other by redundant links. While one Fabric module operates as the active module, the second module operates in warm standby mode to provide instant availability. The following figures show respectively: Fabric modules on the rear panel of a RNC 1500 cabinet a hardware overview of a Fabric module
71
Figure 22 RNC cabinet: lower shelf assembly components, rear view
72
Figure 23 Fabric module: hardware overview
73
Fabric module redundant backplane

Within an interface node, two Fabric modules provide backplane redundancy. They are referred to as the X Fabric and Y Fabric modules. The X Fabric module and the Y Fabric module are used in a load-sharing mode. If one Fabric module fails, all traffic is carried by the other Fabric module. Physically there is only one type of Fabric card. The designation of X vs Y Fabric module is determined by the location of the Fabric module. The Fabric module must read X or Y designation from backplane pins. The Fabric modules provide redundant backplane communication in the interface node between 16 modules. The Fabric modules are not included in these 16 modules. Therefore, the interface node can still have: two CP3 modules up to twelve Packet Server modules two 16p OC-3/STM-1 modules on the front panel: two visual indicators (LEDs)
74
10.2.5
LED description for Multiservice Switch 15000 module
This section describes the LEDs on the Multiservice Switch 15000 modules.
LED description
Each module inside the Multiservice Switch 15000 houses three LEDs on the upper part of the front panel to facilitate on-site maintenance and reduce the risk of human error. These LEDs are represented as: amber with a circular shape red with a triangular shape green with a rectangular shape
The red and green LEDs indicate the module status. The amber LED indicates that the module is not operational. The following figure shows the position of each LED for each module (except the Filler module).
75
Figure 24 Module front panel indicators
LED display
The Multiservice Switch 15000 has only one LED active at any given time; combinations of green, red and amber LEDs are not supported. The following table gives the description, combinations and states of the red LED, the green LED and the amber LED for each module inside the interface node of the RNC 1500 cabinet. Table 2 Visual indicator description for all modules LED display LED off Solid red Slow flashing red Slow flashing green Module status No power is reaching the module. The module is disabled. The module has performed auto-tests but has not yet fully loaded its software. The software of the module is fully loaded but not yet activated. For the interface node, the module
76
LED display Fast flashing green Solid green Solid amber
Module status may also be locked. The module is running as standby. The module in active service. The module is not configured on this slot.
77
10.3
RNC 1500 cooling system description

This section gives a high-level presentation of the cooling system. The cooling system components are as follows: RNC 1500 environmental control equipment air filters temperature sensors cooling units
If the upper shelf is empty, one cooling unit is placed on the rear for the lower shelf. If the cabinet is full, two cooling units are placed in the middle of the frame. The following figure shows the relationship between the upper cooling unit and the upper shelf and between the lower cooling unit and the lower shelf in an RNC 1500 cabinet. Each cooling unit consists of three fan modules and a cooling unit backplane located in a common shelf. Each cooling unit is controlled by remote temperature sensors located in the shelf assembly. If one fan fails, an alarm is generated. If the temperature reaches an unacceptable level, the fan speed increases. The upper cooling unit expels air from the fans under the modules to the top of the upper shelf assembly. The upper cooling unit is only installed if the upper shelf is installed. The lower cooling unit draws air from the bottom of the frame to the rear of the lower shelf assembly.
The RNC 1500 must always be operated with the cooling units on to avoid damage to the cabinet modules.
78
Figure 25 Upper and lower cooling unit in an RNC 1500 with airflow direction
79
RNC 1500 environmental control equipment

The RNC 1500 environmental control equipment consists of two cooling units located in the middle of the frame, between the upper and lower shelf assemblies. The upper cooling unit expels air from the fan under the modules in the upper shelf assembly out through the exhaust plenum under the BIP. The lower cooling unit draws air in from the bottom of the frame, over the modules in the lower shelf assembly and out through the fan assembly. Each cooling unit consists of three fan modules and a cooling unit backplane located in a common shelf. Each cooling unit is controlled by remote temperature sensors located in the shelf assembly. Under normal operating conditions and with 2200 W dissipated power, the cooling unit provides sufficient air flow (1 to 1.2 m/s), if the air conditioner fails, to maintain an overall air temperature increase across the shelf of less than 15C (59F). At temperatures above 55C (131F), the fans switch to high (full) speed to increase air flow and cooling of the shelf. The fans return to normal speed when the temperature falls below 46C (115F).
Air filters
The RNC 1500 frame is equipped with air filters to prevent dust and other airborne contaminants from being drawn into the shelf assemblies by the cooling units. The filters also assist air flow by acting as airflow diffusers. The air filter for the lower cooling unit is located at the bottom of the frame. The air filter for the upper cooling unit is located in the middle of the frame, between the upper cooling unit and the upper shelf. The air filters must be installed in the frame assembly to ensure proper air flow across the shelf assembly. The RNC 1500 must not be operated when the air filters are removed, except during filter replacement.
Temperature sensors
A temperature sensor (one per fan controller) is placed in the air flow above the shelf assembly in the exhaust air stream. Each temperature sensor is mounted on a Printed Circuit board (PCB). The temperature sensors are not linked directly to a specific fan and can monitor the air flow generated by multiple fans simultaneously. The temperature sensors are linked to a temperature interface block, which provides bias to the sensors, monitors faults in the sensor circuit, and processes temperature information. If temperatures greater than 72C (162F) are detected, a HighTemp alarm is sent to the Alarm/BITS module where the alarm is indicated. When temperatures less than 55C (131F) are detected, the fans operate at normal speed. If temperatures between 55C and 72C (131F and 162F) are detected, the fans switch to high-speed mode. The RNC environmental control equipment consists of two cooling units located in the middle of the frame, between the upper and lower shelf assemblies. The upper cooling unit expels air from the fan
80
under the modules in the upper shelf assembly and out through the exhaust plenum under the BIP. The lower cooling unit draws air in from the bottom of the frame, over the modules in the lower shelf assembly and out through the fan assembly.
81
Figure 26 Cooling unit: hardware overview
82
Cooling unit
The following figure shows the front view and the rear view of the cooling units on the RNC 1500. Each cooling unit houses the following components: cooling unit description fan controller module cooling unit LED indications
83
Figure 27 Cooling units: front and rear views
84
Cooling unit description

The cooling unit maintains an ambient temperature inside the shelf assembly. Each cooling unit has the following characteristics: The dimensions for the upper and lower cooling unit are approximately 200mm high, 480 mm deep and 534 mm wide. Three individually replaceable fans. Three replaceable fan controllers. Fans run at 2900 RPM in normal operating conditions to minimize wear and tear, and fan noise; fans run at full speed (3600RPM) at fan-fail and over-temperature conditions. Each fan is controlled by a fan controller board. Fully redundant power (A and B feeds to cooling unit). Fan-fail and over-temperature lights the front LED and sends an alarm signal to the shelf. The cooling unit is based on Rotarian Maltese fan units (150mm L x 55mm W x 171mm H). Fan output CFM: 150@2900RPM and 300@3600RPM. Both front and rear cooling units are cabled from the rear. The front cooling unit (upper), if needed, is a push-type forced convection system; air flow direction is from the bottom to the rear. The rear cooling unit (lower) is a pull type forced convection system: air flow direction is from the bottom to the rear. LEDs are viewable from the front of both cooling units to confirm failure. An air filter is provided at the shelf level. The maximum dissipation of the RNC 1500 cabinet is 2600W.
Fan controller module

The fan controller module performs the following functions: controls the fan power supply monitors fan speed and operation monitors the status of the remote temperature sensors
In case of failure, the controller sends an alarm signal to the alarm/BITS module and sends a status signal to the other fans, forcing them to switch to a higher speed.
Cooling unit LED indications

Each cooling unit is equipped with LEDs to indicate the status of the unit. The table below gives the description, combinations and states of the red and green LEDs for the modules in the RNC cabinet.
85
Table 3 Cooling unit LED indications Red LED (triangular) LED off LED off LED on Green LED (rectangular) LED off LED on LED off Status The module is not powered The module is on, no fault detected Missing fan or temperature sensor detected. A FANFAIL signal is sent to the alarm/ BITS module, and the remaining fan modules are switched to the high speed setting.
86
10.4
RNC 1500 power supply and alarm systems

The power supply and alarm systems of the RNC 1500 cabinet are composed of the following components: the Breaker Interface Panel (BIP) is used for all power and alarm cabling used inside the RNC. four PIM modules, for the Multiservice Switch 15000. They are used to transfer the -48 V dc each alarm to/from each Multiservice Switch 15000 module and the BIP. a MAC address module, containing the range of MAC addresses available for assignment (based on the base address value). an Alarm/BITS module, terminating alarm and BITS signals.
87
10.4.1
BIP assembly
The BIP assembly is located in a frame power distribution tray and is mounted on the top of the RNC 1500 frame. It provides a central location where redundant dc power feeds (nominal -48 V dc) connect to the switch and route up to four Breaker Interface Modules (BIM) with two BIMs per RNC 1500 shelf. Power is distributed from the BIMs to the shelves and the cooling units. The BIP also contains an alarm module that monitors system components, generates alarms, and controls LED status indicators. The BIP assembly contains a front cover, which provides the main following functions: It protects the components and connections on the front of the power breakers and alarm module. It directs exhaust air venting from the upper cooling unit. It provides tool-only access through captive screws (for security and convenience).
The front cover can be opened to access the retaining screws holding the BIM and alarm module in place. The following figure shows the location of the individual components in the BIP assembly and the location of the power connectors. The BIP houses the following components: BIM alarm module
88
Figure 28 BIP: hardware overview
89
Table 4 Component power consumption Component Quantity Typical Watts Typical Watts total 74 260 1200 13 80 100 0 1 0 Maximum Watts total 55 x 2 150 x 2 100 x 12 21 x 1 187 x 1 60 x 2 0 1x1 0
CP3 16pOC-3/STM-1 PS BIP Lower cooling unit Fabric PIM Alarm/BITS MAC address module Total
2 2 12 1 1 2 4 1 1
37 130 100 13 80 50 0 1 0
1728
1939
90
10.4.2
PIM modules
The PIM modules are the dc power conditioner. The shelf assembly houses four modules. The dc part of the PIM module houses the following connectors: a connector dedicated to alarms a connector dedicated to fan unit alarms a connector dedicated to the -48 V dc a power block
The PIM module also provides the alarm interface between the central distribution boxes and the Multiservice Switch 15000. The following figure shows a hardware overview of the PIM module.
91
Figure 29 PIM module: hardware overview
92
PIM modules: location and physical description

As shown in the following figure, the four PIM modules are located along the left side of the rear of the shelf assembly. Each PIM module provides a point at which power and alarm cables from the BIP are connected. The shelf assembly houses four PIMs: two for the A power feed two for the B power feed
The input power feeds from the BIP are routed to the Multiservice Switch 15000. The BIP backplane power connections are the terminations for input power feeds up to 100 A, and for output power cables from the BIP to the shelves and the cooling units. A four-BIM model BIP supports four input feeds (a battery and battery-return wire per BIM). A backplane safety cover overlays the backplane to prevent inadvertent shorts from metallic contact with the connectors. Each power input connection is covered by an insulating boot. Each PIM module provides the following functions: separate power filtering for the portions of the shelf it supports termination for the shelf clocks and for the secondary control bus
The PIM module is a replaceable unit. You must first, however, power down the Multiservice Switch 15000 from the appropriate BIP circuit breakers and unplug the PIM module power cables before you remove the module.
93
Figure 30 PIM module: positioning and front panel view
94
PIM modules: front panel

The power cables from the BIP are connected to the front panel of a PIM module. The front panel is designed so that you cannot remove the PIM module unless the power cable is removed first. This protects the backplane pins from arcing if the PIM module is pulled out with the power left on.
95
10.4.3
MAC address module
The Media Access Control (MAC) address module is located at the left side of the rear of the shelf assembly, between the two fabric modules and between the PIM modules of the upper and lower cage. The MAC address module is a replaceable module that provides the shelf with MAC addresses for the control and function processors. The module also communicates the shelf type to the control processors. The MAC address module contains the range of MAC addresses available for assignment (based on the base address value). During the RNC 1500 boot sequence, the control processor takes the range stored in the MAC address module, divides this value by the number of functional processors, and distributes a base value and a range to each functional processor. The following figure shows the front panel and the hardware overview of the MAC address module.
96
Figure 31 MAC address module: positioning and front panel view
97
Figure 32 MAC Address module: hardware overview
98
10.4.4
Alarm BITS module
As shown in the following figure, the alarm BITS module is located at the right side of the rear of the shelf assembly, between the upper and lower fabric modules. The alarm BITS module is a replaceable module that performs the following functions: terminates cables carrying: alarm signals (from the cooling unit and BIP) BITS signals passes the information over shelf backplane to the control processors and expansion slots
The alarm/BITS module supports connection to DS1 balanced cable (CP3 T1 module) and E1 balanced cable (CP3 E1 module). For connection to the E1 unbalanced cable (CP3 E1 module) use an adapter cable. The alarm BITS module contains the following connectors: BITS ports Sync A-J4 cooling unit alarm connector alarm BITS module cable assembly BIP alarm connector
99
Figure 33 Alarm BITS: positioning and front panel view
100
BITS ports Sync A-J4

The alarm BITS module provides two ports for connecting the interface node to a Built-in Integrated Timing Supply (BITS) interface. These ports support connection to E1 balanced cables (120-ohm twisted pair D-sub). For connection to E1 unbalanced cables (75-ohm coax D-sub) use an adapter cable. The ports are labeled Sync A-J4. These ports are paired with the control processors that contain the active BITS circuits. The pin assignments and the functional specifications for the transmit and receive circuits for the BITS connectors are listed in Nortel Multiservice Switch 15000/20000 Hardware Installation, Maintenance and Upgrades (NN-10600-130).
Alarm BITS module: cooling unit alarm connector

The cooling unit alarm connector is a 9-pin D connector that receives alarm signals from the interface node cooling unit and transmits them to the switch backplane through the alarm BITS module. Table 5 Cooling unit alarm connector Pin number 1 2 3 4 5 6 7 8 9 No connection FANTEMP No connection GND No connection No connection GND FANFAIL No connection Signal
Alarm BITS module: cable assembly

The cable assembly for the alarm BITS module is part of the BIP alarm cable assembly. The assembly includes the wires and connectors for connecting to the J1 and J2 outlets on either a lower or an upper switch. Connecting the DB9 connectors onto the BITS wires is described in Nortel Multiservice Switch 15000/20000 Hardware Installation, Maintenance and Upgrades (NN-10600-130).
Alarm BITS module: BIP alarm connector

The BIP alarm connector is the bottom connector in the alarm/BITS E1 module. This module performs the following functions:
101
BIP alarm termination This provides proper over-voltage protection for all BIP alarms and provides an interface between the BIP and the CP3 modules through the backplane.
shelf ID termination This provides proper over-voltage protection and a backplane interface for shelf ID and the BIP signals to the CP3 module slots.
audiovisual alarm termination This provides a connection between the backplane audio visual alarm signals and the BIP interface to the CP3 modules slots.
Table 6 BIP alarm connector Pin Number 1 2 3 4 5 6 7 8 9 10 11 12 13 Signal MINAUDN MAJAUDN CRITAUDN SHID4 GND MINVISN ALMFAILN No connection No connection MINVISN MAJVISN CRITVISN SHID3 14 15 16 17 18 19 20 21 22 23 24 25 26 Pin Number Signal No connection No connection BKRFAILBN EXTPWRN ACON SHID0 SHID1 SHID2 SHID5 BKRTRIPAN BKRFAILAN BKRTIPBN No connection
102
11
Using TML with the RNC 1500

The RNC 1500 has a number of tools, including the Local Maintenance Terminal (TML). The TML hardware consists of a laptop. It runs with windows and behaves like a Java browser. This section describes the TML functions and TML connection to the RNC 1500.
TML functions
The TML tool performs the following functions: graphically displays the current RNC 1500 hardware configuration performs tests after equipment installation audits system before major operations upgrades software or hardware downloads new software diagnoses and localizes link failures between the RNC 1500 boards customizes the RNC 1500 nodes installs software tests RNC 1500 modules operates corrective maintenance
TML connection to the RNC 1500

The TML is connected to the RNC through Ethernet connections to the CP3 module inside the Multiservice Switch 15000. The operator can plug into the active or passive modules, provided that the LED status is correct. The TML can also be plugged into a hub that is hosted in the cabling area interface of the RNC. The TML is also used for RNC installation and the test and maintenance activities. The TML is used for the following types of connections: Direct connections: On the Multiservice Switch 15000 the TML hardware can be plugged on the CP3-0 module with a RJ45 crossed cable. Remote connections: In this connection, the TML is connected to LAN/WAN network. The connection can be checked with a ping [IP address]. For more information, see UMTS RNC 1500 TML Commissioning & Fault Management User Manual (NN-20500-026).
103
Wireless Service Provider Solutions W-CDMA Product Fundamentals UMTS RNC 1500 Fundamentals
Copyright 2005-2007 Alcatel-Lucent, All Rights Reserved ALCATEL-LUCENT CONFIDENTIAL UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies. ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately. Document number: Document issue: Document status: System Release: Date: NN-20500-021 04.03/EN Standard UA05.1 November 2007

NN-20500-021 (UMTS RNC 1500 Fundamentals) 04.03 Standard November 2007

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NN-20500-021 (UMTS RNC 1500 Fundamentals) 04.03 Standard November 2007

Încărcat de

Drepturi de autor:

Formate disponibile

NN-20500-021 Wireless Service Provider Solutions

Wireless Service Provider Solutions

SYSTEM RELEASE UMTS 5.1 June 2007

SYSTEM RELEASE UMTS 5.0 January 2007

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

SYSTEM RELEASE UMTS 4.1 October 2005

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

About this publication

How this document is organized

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Access Network Roadmap

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

New in this release

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

RNC regulatory information

Regulatory requirement compliance

Compliance for American countries (North and South)

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

Compliances for other regions/countries

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Labeling for other regions/countries

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

The UTRAN release is RAN 5.1.

Main RNC functions

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Main BTS functions

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

Figure 1 Alcatel-Lucent UTRAN architecture example

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

Main Access Network OAM functions

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

RNC 1500 basic characteristics

NN-20500-021 04.03/EN Standard November 2007

Copyright 2005-2007 Alcatel-Lucent

RNC 1500 introduction

Multiservice Switch 15000 general description

The Multiservice Switch 15000 supports : IP/ATM protocols voice services

Copyright 2005-2007 Alcatel-Lucent

UMTS RNC 1500 Fundamentals

Product upgrade from RNC 1000

RNC 1500 external interfaces

RNC 1500 Functions

RNC 1500 general view