01_RN33111EN20GLA1_RNC Architecture and Functionalities

March 23, 2018 | Author: Gaurav Varshney | Category: High Speed Packet Access, Asynchronous Transfer Mode, Computer Network, Network Switch, Technology
Share
Report this link


Comments



Description

RN33111EN20GLA0RNC Architecture and Functionalities 1 1 © Nokia Siemens Networks RN33111EN20GLA1 RU20 RNC Architecture and Interfaces RN33111EN20GLA0 RNC Architecture and Functionalities 2 2 © Nokia Siemens Networks RN33111EN20GLA1 Nokia Siemens Networks Academy Legal notice Intellectual Property Rights All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks. RN33111EN20GLA0 RNC Architecture and Functionalities 4 4 © Nokia Siemens Networks RN33111EN20GLA1 Objectives After this training module, the student should be able to: • Explain RNC architectures: cabinet, Plug In Unit (PIU) connection, cabling, Functional Units (FUs), redundancy types and Hardware Management System (HMS) of RNC196, RNC450 and RNC2600 • Explain RU20 RNC configuration and capacity steps for RNC196, RNC450 and RNC2600 • Understand new changes in RU20 (RN5.0) for RNC196, RNC450 and RNC2600 • Understand signalling and data flow in RU20 for RNC196, RN450 and RNC2600 • Explain changes in RU20 for hardware, software, alarms, MML, measurement RN33111EN20GLA0 RNC Architecture and Functionalities 5 5 © Nokia Siemens Networks RN33111EN20GLA1 CN BSS UE UTRAN PS-Domain CS-Domain RNS EI R HS S VL R PDN/ Internet PDN/ Internet VLR PSTN PSTN Um Uu Abis A A IuCS Gb Gs F D C PSTN Gf Gc Gn Gp Nc Mc Mc Nb PSTN Nc E G IuPS Iur USIM IuCS Gr Gi PSTN PSTN SIM Cu GERAN BSC BTS Node B RNC SGSN GGSN MG W MSS MS S MGW GMSS Iub IMS IMS Go Other PLMN Other PLMN BG UMTS Basic Network Architecture (Rel 7) The picture shows an overview of mobile network supporting both 2G and 3G. The core network (CN) is divided into Circuit Switched and Packet Switched domains. The 3G radio access network, or UTRAN (UMTS Terrestrial Radio Access Network), consists of Node B's and RNC's. One RNC together with all Node B controlled forms an RNS (Radio Network Subsystem). RN33111EN20GLA0 RNC Architecture and Functionalities 6 6 © Nokia Siemens Networks RN33111EN20GLA1 UTRAN Iu-CS Uu User Equipment (UE) Iur Iub DRNC WBTS WBTS WBTS WBTS SRNC Core Network (CN) 3G- SGSN 3G- MSC Iu-PS CBC Iu-BC SAS or A-GPS Server Iu-pc or ADIF UTRAN Interfaces Picture shows UTRAN interfaces. In addition to the MSC and SGSN, interfaces to optional core network nodes are shown:  CBC (Cell Broadcast Centre) supports cell broadcast traffic to all mobiles within a service area.  SAS (Standalone SMLC, Standalone Serving Mobile Location Centre) or Assisted GPS (A- GPS) server supports location services (LCS). For location services the following methods are supported by RNC: Cell Coverage Based with Geographical Coordinates In the Cell Coverage Based positioning method, the location of the UE is estimated on the basis of its serving cell. Information about the serving cell is obtained, for example, by paging, location area update, cell update, URA update or routing area update. Assisted GPS Since RAS05.1 / RAS05.1 ED, in addition to Cell Coverage Based positioning, A-GPS (Assisted GPS) is supported. The objective of this method is to forward to the UE the GPS Navigation Message in a specified Assistance Measurement Control message. Hence, the satellite acquisition time can be significantly reduced and the availability of the positioning service can be enhanced to urban canyons and light indoor environments. Moreover, the A-GPS positioning accuracy can be improved if rough location of the UE can be included in the Assistance Measurement Control message. Rough position of the UE can be estimated based on, e.g., introduced Cell Coverage Based location technique. RN33111EN20GLA0 RNC Architecture and Functionalities 7 7 © Nokia Siemens Networks RN33111EN20GLA1 OMU lower traffic capacity higher traffic capacity TDM E1/T1/JT1 1.5-2 Mbit/s NIWU FDU WDU Generic Functional Architecture of IPA2800 ATM E1/T1/JT1 1.5-2 Mbit/s NIP1 DMCU /TCU MXU MXU TBU Ethernet 10/100 Mbit/s ATM STM-1 155 Mbit/s NIS1 NPS1 OMS Interface Functions Switching Functions Control Functions Signal Processing System Functions TDM STM-1 155 Mbit/s IWS1E IWS1T IPGO/GE NPGE IPFE Ethernet 1G (optical/ electric) Ethernet 100M ISU /ICSU Signaling RSMU /CACU … Resource mangement A2SU SFU SWU The general functional architecture of the IPA2800 Packet Platform based network elements is shown above. At the high level network element consists of switching functions, interface functions, control functions, signal processing functions, and system functions (such as timing and power feed). Functionality is distributed to a set of functional units capable of accomplishing a special purpose. These are entities of hardware and software or only hardware. Operation and Maintenance Unit (OMU) for performing centralized parts of system maintenance functions; peripherals such as Winchester Disk Drive (WDU) and Floppy Disk Drive (FDU) (i.e. magneto-optical disk in the ATM Platform) connected via SCSI interface; Distributed Control Computers (signaling and resource management computers) which consist of common hardware and system software supplemented with function specific software for control, protocol processing, management, and maintenance tasks; Network Interface Units (NIU) for connecting the network element to various types of transmission systems (e.g. E1 or STM-1); (Please note that actual names of functional units are different, e.g. NIS1 and NIP1 instead of NIU) Network Interworking Units (NIWU, IWS1) for connecting the network element to non-ATM transmission systems (e.g. TDM E1); ATM Multiplexer (MXU) and ATM Switching Fabric Unit (SFU) for switching both circuit and packet switched data channels, for connecting signalling channels, as well as for system internal communications; AAL2 switching unit (A2SU) performs switching of AAL type 2 packets; Timing and Hardware Management Bus Unit (TBU) for timing, synchronization and system maintenance purposes; and Distributed Signal Processing units (DMCU/TCU) which provide support for e.g. transcoding, macro diversity combining, data compression, and ciphering. Units are connected to the SFU either directly (in the case of units with high traffic capacity) or via the MXU (in the case of units with lower traffic capacity). The order of magnitude of the interconnection capacity for both cases is shown in the figure. RN33111EN20GLA0 RNC Architecture and Functionalities 8 8 © Nokia Siemens Networks RN33111EN20GLA1 Generic Block Diagram of IPA2800 MXU MXU TBU OMU WDU E1/T1/JT1 ATM STM-1/VC-4 STM-1/VC-3 ATM Ethernet 100Base-TX CU* NIS1 NIP1 NIWU MXU OMS A2SU CU* SPU* FDU E1/T1/JT 1 TDM IPFE Ethernet 1G IPGO/GE IWS1E/T STM-1 TDM Ethernet 100M STM-1/VC-4 STM-1/VC-3 ATM NPS1 NPGE Ethernet 1G SFU SWU Ethernet 100Base-TX CU* CU* More formal way to view the generic functional architecture is by the generic block diagram. Note that the naming of functional units is different in actual network elements based on the platform. Here more generic terms are used to describe the concepts (for example, NIU, SPU and CU). Such generic terms are marked with an asterisk (*). To achieve higher reliability, many functional units are redundant: there is a spare unit designated for one or more active units. There are several ways to manage these spare units. All the centralized functions of the system are protected in order to guarantee high availability of the system. To guarantee high availability, the ATM Switching Fabric and ATM Multiplexer as core functions of the system are redundant. Power feed, hardware management bus, and timing supply are also duplicated functions. Hot standby protected units and units that have management or mass memory interfaces are always duplicated. Hard discs and buses connecting them to control units are always duplicated. Computing platform provides support for the redundancy. Hardware and software of the system are constantly supervised. When a defect is detected in an active functional unit, a spare unit is set active by an automatic recovery function. The number of spare units and the method of synchronization vary, but redundancy always operates on software level. If the spare unit is designated for only one active unit the software in the unit pair is kept synchronized so that taking the spare in use in fault situations (switchover) is very fast. This is called 2N redundancy principle or duplication. For less strict reliability requirements, the spare unit may also be designated to a group of functional units. The spare unit can replace any unit in the group. In this case the switchover is a bit slower to execute, because the spare unit synchronization (warming) is performed as a part of the switchover procedure. This redundancy principle is called replaceable N+1. A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of unit in the pool is selected so that there is some extra capacity available. If a few units of the pool are disabled because of faults, the rest of the group can still perform its designated functions. This redundancy principle is called complementary N+1 or load sharing. RN33111EN20GLA0 RNC Architecture and Functionalities 9 9 © Nokia Siemens Networks RN33111EN20GLA1 IPA2800 Conceptual Model Application Software (RNC, MGW) Application Software (RNC, MGW) Applications Signal Processing Platform SW Adjunct Platform (NEMU) Adjunct Platform (NEMU) Switching Platform SW Fault Tolerant Computing Platform Software Modular and Scalable Hardware (Processing, switching and interface capacity required) Modular and Scalable Hardware (Processing, switching and interface capacity required) IPA2800 Platform API API API API The IPA2800 Packet Platform consists of the Switching Platform Software, the Fault Tolerant Computing Platform Software, Signal Processing Platform Software, and the Hardware Platform. In addition, adjunct platforms can be used if needed in an application. The Switching Platform Software provides common telecom functions (for example, statistics, routing, and address analysis) as well as generic packet switching/routing functionality common for several application areas (for example, connection control, traffic management, ATM network operations and maintenance, and resource management). The Fault Tolerant Computing Platform Software provides a distributed and fault tolerant computing environment for the upper platform levels and the applications. It is ideal for use in implementing flexible, efficient and fault tolerant computing systems. The Computing Platform Software includes basic computer services as well as system maintenance services, and provides DX Light and POSIX application interfaces. The Computing Platform Software is based upon general purpose computer units with inter- processor communications implemented using ATM virtual connections. The number of computer units can be scaled according to application and network element specific processing capacity requirements. The Hardware Platform based on standard mechanics provides cost-efficiency through the use of modular, optimized and standardized solutions that are largely based on commercially available chipsets. The Signal Processing Platform Software provides generic services for all signal processing applications. Digital signal processing (DSP) is needed in providing computation intensive end-user services, such as speech transcoding, echo cancellation, or macrodiversity combining. The Adjunct Platform (NEMU) provides a generic platform for O&M application services and different NE management applications and tools. Concept platform and it's layer structure should in this context be seen as a modular set of closely related building blocks which provide well defined services. Structure must not be seen as static and monolithic, as the subset of services needed for an application (specific network element) can be selected. RN33111EN20GLA0 RNC Architecture and Functionalities 10 10 © Nokia Siemens Networks RN33111EN20GLA1 Mechanics (M2000) Cabinet mechanics for indoor use Cabinet contains 4 subracks, 4 fan trays, and power distribution equipment EMC shielding at subrack level rather than at cabinet level Front and back cabling Based on metric dimensioning (IEC/ETSI) Old hardware mechanics (prior to A5): IC186-B Indoor Cabinet, 1800*600*600 mm SRA1 Subrack, ATM, type 1 SRA2 Subrack, ATM, type 2 FTRA Fan Tray New hardware mechanics (A5HW): EC216 Equipment Cabinet, 2100*600*600 mm SRA3 Subrack, ATM, type 3 FTRA-B Fan Tray 1200W The IPA2800 platform introduces a new mechanics concept, with new cabinet, new subrack (EMC shielded), and new plug-in unit dimensions. Fan units are needed inside the cabinet for forced cooling. The M2000 mechanics comprises the basic mechanics concept based on ETSI 300 119-4 standard and IEC 917 series standards for metric dimensioning of electronic equipment. The concept supports the platform architecture which allows modular scalability of configurations varying from modest to very large capacity. It also allows the performance to be configured using only few hardware component types. The mechanics consists of following equipment: cabinet mechanics 19-slot subrack, it's backplane and front plate mechanics connector and cabling system cooling equipment. Dimensions of the cabinet are: width 600 mm, depth 600 mm, and height 1800/2100 mm (based on standard ETS 300 119-2 and IEC 917-2). Subrack has a height of 300 mm, a depth of 300 mm, and a width of 500 mm. The nominal plug-in unit slot in the subrack is 25 mm which results in 19 slots per one subrack. The basic construction allows dividing a part of a subrack vertically into two slots with optional guiding mechanics for the use of half-height plug-in units. The backplane and cabling system provides reliable interconnections between plug- in units. In addition to this, the backplane provides EMC shield to the rear side of the subrack. Common signals are delivered via the backplane and all other interconnection signals are connected via cabling. This allows backplane modularity and flexibility in different configurations. Because of flexible cabling and redundancy it is possible to scale the system to a larger capacity in an active system without shutting down the whole system. Cabinet power distribution equipment and four subracks with cooling equipment can be installed in one cabinet. Openings in the sides of the cabinet behind the subrack backplanes allow direct horizontal cabling between cabinets. RN33111EN20GLA0 RNC Architecture and Functionalities 11 11 © Nokia Siemens Networks RN33111EN20GLA1 Similarities and Differences of DX200 and IPA2800 (Optional) RN33111EN20GLA0 RNC Architecture and Functionalities 12 12 © Nokia Siemens Networks RN33111EN20GLA1 Comparison of IPA2800 & DX200 Platforms Similarities and Differences: Hardware Platform All plug-in units are different in IPA2800 platform and DX 200 platform. However, plug-in units may contain common hardware blocks in some cases. System internal communication: ATM vs. Message Bus and LAPD channels Hardware Management System (HMS) replaces Wired Alarms, and provides new functionality. Similarities and Differences: Computing Platform Major improvements visible to application level will be: POSIX, I/O architecture, System Maintenance, Chorus Computing Platform Similarities and Differences: Switching Platform Switching based on ATM: a lot of ATM-specific additional functionality Similarities and Differences: Hardware Basic switching technology different: TDM versus ATM A variety of new interface types, also network interworking is supported. New mechanics concept and new dimensioning, but common technical solutions in M98 and M2000 mechanics when possible. All plug-in units are different in IPA2800 platform and DX 200 platform. However, plug-in units may contain common hardware blocks in some cases. System internal communication: ATM vs. Message Bus and LAPD channels Hardware management system replaces wired alarms, and provides new functionality Increased functional integration Compact network elements Forced cooling with fans RN33111EN20GLA0 RNC Architecture and Functionalities 13 13 © Nokia Siemens Networks RN33111EN20GLA1 DX 200 / IPA 2800 Platform Both Platform support the common features: • Distributed Processing Architecture • Modularity • Common Hardware • Modular Software • Fault Tolerance RN33111EN20GLA0 RNC Architecture and Functionalities 14 14 © Nokia Siemens Networks RN33111EN20GLA1 IPA2800 Redundancy Principles RN33111EN20GLA0 RNC Architecture and Functionalities 15 15 © Nokia Siemens Networks RN33111EN20GLA1 2N Redundancy 2N Redundancy (duplication) • one spare unit designated for one active unit • Software in the unit pair is kept synchronized (hot-standby) -> fast switchover Active Hot stand-by 2N redundancy principle 2N Redundancy (duplication) is used when two units are dedicated to a task for which one is enough at any given time. One of the units is always active, that is in the working state. The other unit is kept in the hot stand–by state, the spare state. For example: 2N in RNC: OMU, SFU, MXU, RSMU 2N in BSC: OMU, GSW, MCMU When a unit is detected faulty, it is taken into the testing state, and the fault location and testing programs are activated. On the basis of the diagnosis, the unit is taken to the separated state, if a fault is detected, or into use automatically, if no fault is detected. If the spare unit is designated for only one active unit. the software in the spare unit is kept synchronised so that taking it in use in fault situations switchover· is very fast The spare unit can be said to be in hot standby This redundancy principle is called duplication. abbreviated :N RN33111EN20GLA0 RNC Architecture and Functionalities 16 16 © Nokia Siemens Networks RN33111EN20GLA1 Replaceable N+1 Redundancy • Replacement (N+1) or (N+m) • one or more units designated to be spare units for a group • allocating resources to a unit defines it as active, not allocating resources defines to be spare • spare unit can replace any active unit in the group -> slower switchover, requires warming (cold-standby) • users responsibility to change the working state of the unit to reflect the resource allocation situation and to leave at least one spare unit Active Active Stand-by N+1 redundancy principle Replaceable N+1 / N+m Redundancy are used when there is just one or a few spare units for a set of N units of a given type. The spare unit is not used by the applications and is not permanently bound to one of the N active units, but can take over the load of any one of them. When a command–initiated changeover for a replaceable N+1 unit is performed, a pair is made up, the spare unit is warmed up to the hot stand–by state, and changeover takes place without major interruptions. When a unit is detected faulty, it is automatically replaced without interruptions to other parts of the system. For example: N+1 in RNC: ICSU N+1 in BSC: BCSU RN33111EN20GLA0 RNC Architecture and Functionalities 17 17 © Nokia Siemens Networks RN33111EN20GLA1 SN+ Redundancy (Load Sharing) SN+ (Load Sharing) • no spare units, group acts as a resource pool • number of units selected so that there is overcapacity • if a few units are disabled, the whole group can still perform its functions Active Active Active SN+ redundancy principle Active Active Fail Load 33% 33% 33% Load 50% 50% 0% Load sharing (SN+) or Complementary N+1 Redundancy A unit group can be allocated no spare unit at all if the group acts as a resource pool. The number of units in the pool is selected so that there is a certain amount of extra capacity. If a few units of the pool are disabled because of faults, the whole group can still perform its designated functions. This redundancy principle is called load sharing and abbreviated as 'SN+ For example: SN+ in RNC: GTPU, A2SU, DMCU SN+ in BSC: - RN33111EN20GLA0 RNC Architecture and Functionalities 18 18 © Nokia Siemens Networks RN33111EN20GLA1 Functional Unit Redundancy Principles No redundancy • no special requirements for reliability No Redundancy is needed in cases where the redundancy of a unit would not noticeably increase the overall availability performance of the unit type. For example: RNC: OMS BSC: ET The 2–Mbit/s exchange terminal (ET), where the probability of failure of the 2– Mbit/s line is expected to be much greater than that of the exchange terminal hardware. For example: RNC: OMS BSC: ET RN33111EN20GLA0 RNC Architecture and Functionalities 19 19 © Nokia Siemens Networks RN33111EN20GLA1 Multiplex Section Protection (MSP 1+1) Physical Layer Protection (MSP 1+1) MSP is the SDH name for the Multiplex Section Protection scheme. as defined in ITUT recommendation G:s In SONET. the equivalent term APS Automatic Protection Switching· is used instead Throughout the rest of the document the term MSP is used for both SDH and SONET In the basic MSP functionality. the service line is protected using another line which is called the protection line if an error occurs. for instance a loss of signal LOS·. the protection mechanism switches over to the protection line RN33111EN20GLA0 RNC Architecture and Functionalities 20 20 © Nokia Siemens Networks RN33111EN20GLA1 Exercise 1. List 2 Network Elements use IPA2800 Platform ____________________________________ 2. Fill in redundancy type to match description Redundancy Type Description If a few units are disabled, the whole group can still perform its functions Spare unit can replace any active unit in the group slower switchover Software in the unit pair is kept synchronized Fast switchover RN33111EN20GLA0 RNC Architecture and Functionalities 21 21 © Nokia Siemens Networks RN33111EN20GLA1 RNC Mechanical Design RNC450 and RNC2600 CPD120A Cabinet (H=2100mm) RNC196 CPD80B Cabinet (H=1800mm) Subracks The subrack mechanics consist of a subrack frame, backplane, and front plate forming electromagnetic shielding for electronics to fulfil EMC requirements. The basic construction allows dividing a part of a subrack vertically into two slots with optional guiding mechanics for the use of half-height plug-in units. Plug-in unit The RNC is constructed by using a total of approximately 11 plug-in unit types. The basic mechanical elements of the plug-in units are PCB, connectors and front plate mechanics. Front plate mechanics include insertion/extraction levers, fixing screws and EMC gasket. RN33111EN20GLA0 RNC Architecture and Functionalities 22 22 © Nokia Siemens Networks RN33111EN20GLA1 Connector panels External PDH lines are connected to the RNC cabinet using a back interface plug-in unit which allows modular backplane connections. One back interface plug-in unit supports one E1 plug-in unit. The back interface plug-in unit is installed in the same row as the plug-in unit, but at the rear of the cabinet. There are two kinds of connector panels available: connector panel with RJ45 connectors for balanced E1/T1 line connection to/from the cabinet connector panel with SMB connectors for coaxial E1 line connection to/from the cabinet External timing requires a specific connector panel. PANEL 1 in the RNAC cabinet provides the physical interface connectors Picture on top: Cabling cabinet IC183 installed next to IC186. Notice the balanced cabling between rear transition cards and cabling cabinet patch panels. Topmost patch panel in IC186 is CPSAL. Picture on buttom: BIE1C (SMB connectors) and BIE1T (RJ45 connectors) rear transition cards installed to SRBI in rearside of cabinet. RN33111EN20GLA0 RNC Architecture and Functionalities 23 23 © Nokia Siemens Networks RN33111EN20GLA1 Fan Tray (FTRA-B) Forced cooling for subracks (max power dissipation per subrack 1,2kW) FTRA-B is used with 2000mm cabinet Fans are controlled and supervised by HMS via fan control and supervision HWB located in PD30 M0 M1 Control and alarm Interface (rear cable) M2 M3 M4 M5 M6 M7 PD30 Plug-in unit 2 x –48vdc 2 x CAN Acoustic noise emitted by one IPA2800 fully equipped cabinet is 67 dBA (Power level) 61 dBA (pressure level) in normal conditions (4 FTR1 fantarys containing 32 fans). Acoustic noise increases by 3 dB per new cabinet. FTR1 meet the ETS 300- 753 requirements. Expected lifetime L10(time when 10% of fans failed) ~8years (@+40 degree Celsius). Fantray replacement is possible in live system. Without the fantray live system will overheat approx. in 5 minutes. Faulty FTRA fantary replacement procedure: -Remove front cable conduit if present (move cables carefully away) -Unscrew the fantay from mounting flanges -Unplug the control cable first from subrack side and secondly from fantray side. -Extract the faulty fantary from cabinet and insert the spare fantray unit -Plug the control cable first in fanray and secondly to the subrack side -Screw the fantray to the cabinet flanges -Install cable conduit and cables (if present) -Faulty FTRA-A and FTRA-B replacement procedure: -Remove fantray front grill and extract air filter -Unplug the control cable from fantray side (rear side of cabinet) -Open two thumb-screws behind the grill -Lower and extract the fan assembly by openening the locking latches (drawer assembly and cable conduit is still mounted to cabinet) -Insert spare fan assembly and secure latches and thumb-screws -Plug the control cable -Insert new air filter and close the fantray front grill. RN33111EN20GLA0 RNC Architecture and Functionalities 24 24 © Nokia Siemens Networks RN33111EN20GLA1 RNC196 and RNC450 Architecture The network element consists of the following parts: •Network interface functions •Switching and multiplexing functions •Control plane functions •User plane functions O&M functions The functions are distributed to a set of functional units capable of accomplishing a special purpose. These are entities of hardware and software. The main functional units of the RNC are listed below: The control computers (ICSU and RSMU) consist of common hardware and system software supplemented with function-specific software. The AAL2 switching units (A2SU) perform AAL2 switching. The Data and Macro Diversity Unit (DMCU) performs RNC-related user and control plane L1 and L2 functions. The Operation and Maintenance Unit (OMU) performs basic system maintenance functions. The O&M Server (OMS) is responsible for RNC element management tasks. The OMS has hard disk units for program code and data. The Magneto-Optical Disk Drive (FDU) is used for loading software locally to the RNC. The Winchester Disk Unit (WDU) serves as a non-volatile memory for program code and data for the OMU. The Timing and Hardware Management Bus Unit (TBU) takes care of timing, synchronisation and system maintenance functions. The Network Interface Unit (NIU) STM-1/OC-3 (NIS1/NIS1P) provides STM-1 external interfaces and the means to execute physical layer and ATM layer functionality. Network interface and processing unit 2x1000Base-T/LX provides Ethernet external interfaces and the means to execute physical layer and IP layer functionality. The NIU PDH (NIP1) provides 2 Mbit/s / 1,5 Mbit/s (E1/T1) PDH external interfaces and the means to execute physical layer and ATM layer functionality. The GPRS Tunnelling Protocol Unit (GTPU) performs RNC-related Iu user plane functions towards the SGSN. The External Hardware Alarm Unit (EHU) receives external alarms and sends indications of them as messages to the OMU-located external alarm handler through HMS. Its second function is to drive the Lamp Panel (EXAU), the cabinet-integrated lamp and other possible external equipment. The Multiplexer Unit (MXU) and the Switching Fabric Unit (SFU) are required for switching both circuit- and packet-switched data channels, for connecting signalling channels and for the system's internal communication. RN33111EN20GLA0 RNC Architecture and Functionalities 25 25 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Architecture Some units from earlier releases areno longer exist, because – The functionalities are embedded to other units, or – The unit is no longer supported The units are: – GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P) – A2SU, functionalities are embedded to NPS1(P) – RRMU, functionalities are distributed to ICSU and OMU/RSMU – NIS1(P), replaced with NPS1(P) – NIP1, no more PDH interface are supported The functions are distributed to a set of functional units capable of accomplishing a special purpose. These are entities of hardware and software. The main functional units of the RNC are listed below. The control computers (ICSU and RSMU) consist of common hardware and system software supplemented with function-specific software. The Data and Macro Diversity Unit (DMCU) performs RNC-related user and control plane L1 and L2 functions. The Operation and Maintenance Unit (OMU) performs basic system maintenance functions. The Operation and Maintenance Server (OMS) is responsible for RNC element management tasks. The OMS has hard disk units for program code and data. From RU20/RN5.0, standalone OMS is recommended for new RNC2600 deliveries. Both standalone and integrated OMS are supported in RU20/RN5.0 release. The Winchester Disk Unit (WDU) serves as a non-volatile memory for program code and data. The Timing and hardware management Bus Unit (TBU) takes care of timing, synchronisation and system maintenance functions. The Network interface and processing unit 8xSTM-1/OC-3 (NPS1/NPS1P) provides STM-1 external interfaces and the means to execute physical layer and ATM/AAL2 layer functionality. It also terminates the GTP protocol layer in Iu-ps interface. Network interface and processing unit 2x1000Base-T/LX (NPGE/NPGEP) provides Ethernet external interfaces and the means to execute physical layer and IP layer functionality. The External Hardware alarm Unit (EHU) receives external alarms and sends indications of them as messages to the OMU located external alarm handler via HMS. Its second function is to drive the lamp panel (EXAU), the cabinet-integrated lamp and possible other external equipment. The MultipleXer Unit (MXU) and the Switching Fabric Unit (SFU) are required for switching both circuit and packet-switched data channels, for connecting signalling channels and for the system's internal communication. RN33111EN20GLA0 RNC Architecture and Functionalities 26 26 © Nokia Siemens Networks RN33111EN20GLA1 RNC Functional Units in RU20 SFU MXU HDD WDU EHU TBU ICSU DMCU OMU OMS SWU DMCU ICSU NIU - NIS1(P)* A2SU* GTPU* MXU NIU - NIP1* PDU NIU - NPGE(P) NIU - NPS1(P) * Only unit in RNC196 / RNC450 RSMU RRMU Availability performance calculations describe the system from the availability point of view presenting availability Availability performance values are calculated for the complete system, that is, redundancy principles are taken into account In reference to ITU-T Recommendation Q.541, intrinsic unavailability is the unavailability of an exchange (or part of it) due to exchange (or unit) failure itself, excluding the logistic delay time (for example, travel times, unavailability of spare units, and so on) and planned outages The results of the availability performance calculations for the complete system are presented in the Predicted availability performance values. Some units from earlier releases are no longer exist, because The functionalities are embedded to other units, or The unit is no longer supported The units are: GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P) A2SU, functionalities are embedded to NPS1(P) RRMU, functionalities are distributed to ICSU and OMU/RSMU NIS1(P), replaced with NPS1(P) NIP1, no more PDH interface are supported RN33111EN20GLA0 RNC Architecture and Functionalities 27 27 © Nokia Siemens Networks RN33111EN20GLA1 New Plug-in Units in RNC2600 SF20H MX1G6-A CDSP-DH NP8S1-B NP2GE-B The main function of the SF20H plug-in unit is to switch cells from input to output ports. It has protocol-independent switching core of 80 Gbit/s, half of which is reserved for routing and framing overhead (link speed-up). There are 32 ports of 3.9 Mcells/s ATM cell rate (corresponds to a user data rate of 1.65 Gbit/s). The MX1G6-A is 1.6 Gbit/s ATM multiplexer plug-in unit. It multiplexes and demultiplexes ATM cells and perform ATM layer and traffic management functions. This enables connecting low speed units to the switching fabric and improve the use of switching fabric port capacity by multiplexing traffic from up to twenty tributary units to a single fabric port. The NP8S1-B provides multiprotocol packet processing at wire speed and network connectivity with eight optical synchronous digital hierarchy (SDH) STM-1 or synchronous optical network (SONET) OC-3 interfaces. The high processing power of the network processor and the unit computer enable the NP8S1-B plug-in unit to process protocol and data at the line interface unit (LIU) instead of the dedicated processing units. Similarly, the NP2GE-B provides multiprotocol packet processing at wire speed and also offer the possibility of using both electrical (copper) and optical (fibre) based Ethernet. It has two 1000Base-LX/T (optical or electrical) Gigabit interfaces. interfaces in compliant with the IEEE802.3 specifications. The configurable dynamic signal processing platform CDSP-DH plug-in unit function as CDSP pool. Each CDSP-DH has 8 DSPs. The DSP cores are used in applications that need digital signal processing including the outer loop power control and the PDCP, RLC, MAC, MDC, FP and RTP/RTCP (on IP-based Iu-CS) protocols. RN33111EN20GLA0 RNC Architecture and Functionalities 28 28 © Nokia Siemens Networks RN33111EN20GLA1 Block Diagram and Plug-in Unit Variants for RNC2600 FU/Product PIU Variant ICSU CCP18-A RSMU CCP18-A OMU CCP18-A DMCU CDSP-DH SFU SF20H MXU MX1G6-A SWU ESA24 WDU HDS-B 73G OMS (integrated) MCP18-B TBUF TBUF TSS3 TSS3 PDU PD30 NPS1 NP8S1-B NPGE NP2GE-A Standalone or Integrated Functional units (FU) and their functionalities: ICSU (Interface Control and Signalling Unit) Ssignalling to other network elements and distributed radio resource management related tasks of the RNC. RSMU (Resource and Switch Management Unit) RNC's central resource management tasks such as connection control, internal ATM/IP resource scheduling, DSP related resource management tasks, call connection related functions. OMU (Operation and Maintenance Unit) Maintaining the radio network configuration and recovery, basic system maintenance functions, interface to the OMS unit. DMCU (Data and Macro Diversity Combining Unit) RNC-related user and control plane functions in Frame Protocol (FP), Radio Link Control (RLC), Medium Access Control (MAC) SFU (Switching Fabric Unit) ATM cell switching function supporting point-to-point and point-to-multipoint connection topologies, as well as differentiated handling of various ATM service categories. RN33111EN20GLA0 RNC Architecture and Functionalities 29 MXU (Multiplexer Unit) Multiplex traffic from tributary units to the ATM switching fabric, ATM layer processing functions such as policing, statistics, OAM, buffer management and scheduling SWU (Switching Unit) – Ethernet switch WDU (Winchester Disk Unit) – system disk units for OMU OMS (Operation and Maintenance Server) – RNC element TBU (Timing and Hardware Management Bus Unit) synchronisation, timing signal distribution and message transfer in the Hardware Management System of a network element. The TBU functional unit consists of 2 different plug-in units: TBUF (Timing Buffer) Receive the system clock from the TSS3's, buffer and transmit to the backplane, basic hardware management functions such as alarm supervision and the configuration of the plug-in unit. TSS3 (Timing and Synchronization, SDH, Stratum 3) Snchronize and deliver the timing signals to TBUF units, basic hardware management functions such as alarm supervision and the configuration of the plug-in unit. PDU (Power Distribution Unit) Power distribution and control the cooling equipment of its own subrack NIU (Network Interface Unit) can be either NPS1 or NPGE: NPS1 (Network Processor Interface Unit STM-1) 8x STM-1/OC-3 external interfacesATM layer functions such as header translation, AAL2 mini-packet switching, UPC/NPC parameter control, OAM functions, traffic management, performance monitoring, and performance data collection, and part of the GTP protocol termination for IuPS NPGE (Network Processor Interface Unit Gigabit Ethernet) 2x1000Base-T/LX Gigabit Ethernet external interfaces, IP layer functions such as header translation, traffic management, performance monitoring, and performance data collection, and part of the GTP protocol termination for IuPS EHU (External Hardware alarm Unit) Rreceive external alarms, drive the external lamp panel (EXAU), the cabinet integrated lamp, and any other external equipment RN33111EN20GLA0 RNC Architecture and Functionalities 30 30 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Functional Unit Removed from Non-exist units Non-exist units • Some units from earlier releases are no longer exist, because – The functionalities are embedded to other units, or – The unit is no longer supported • The units are: – GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P) – A2SU, functionalities are embedded to NPS1(P) – RRMU, functionalities are distributed to ICSU and OMU/RSMU – NIS1(P), replaced with NPS1(P) – NIP1, no more PDH interface are supported RN33111EN20GLA0 RNC Architecture and Functionalities 31 31 © Nokia Siemens Networks RN33111EN20GLA1 Change in RU20 (RN5.0) for RNC196/RNC450 and RNC2600 • Change of RNC196 in RU20 (RN5.0) • Change of RNC450 in RU20 (RN5.0) • Change of RNC2600 in RU20 (RN5.0) The RNC2600 has many improvements in RU20 which keep in line with current network challenges but also maintain CAPEX and OPEX at minimum and increase the RNC data throughput. Flexi Multiradio RF module introduces industry leading RF integration level and the smallest power consumption combined with flexible GSM-WCDMA-LTE site evolution. RN33111EN20GLA0 RNC Architecture and Functionalities 32 32 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC196 in RU20 (RN5.0) RN33111EN20GLA0 RNC Architecture and Functionalities 33 33 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC196 in RU20 (RN5.0) • Common Iub interface has been removed from RNC functionality • Broadband interfaces has been updated - Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. - NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450 • Connectivity rule has been updated - CBR AAL2 Path VCC: PCR - UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR ) Broadband interfaces STM-1 Functional units, NIS1 or NIS1P offer ATM over SDH network interface. NIS1 has MSP 1+1 protection possibility within one plug-in unit and NIS1P between plug-in units. Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit contains four SDH STM-1 (optical) interfaces. OC-3 Functional units, NIS1 or NIS1P offer ATM network interface OC-3. APS 1+1 protection can be used with OC-3 interfaces. Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit contains four OC-3 IR-1 (optical) interfaces. Gigabit Ethernet (GE) Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450. For detailed information, see the feature description. NPGEP supports 2N redundancy. Single plug-in unit type NP2GE-B is utilised by NPGE and NPGEP functional units. A plug-in unit contains two GE (optical or electrical) interfaces. Connectivity The AAL2UP connectivity corresponds to the sum of AAL2 path sizes in Iub, Iur, and Iu-CS connections. The limiting factor for the AAL2UP connectivity in steps 1...5 is the A2SU capacity. For steps 6 and 7, the limiting factor is the physical interface capacity, and the AAL2UP connectivity value is derived from the sum of STM-1 interface capacities. The AAL2UP connectivity is consumed as follows: CBR AAL2 Path VCC: PCR UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR ) RN33111EN20GLA0 RNC Architecture and Functionalities 34 34 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC196 in RU20 (RN5.0) • HSUPA and HSDPA peak rate information has been updated in CDSP-DH upgrade for HSDPA peak rate per user The RNC196 HSPA capacity HSDPA traffic does not include soft handovers. HSUPA includes 40% soft handover overhead in Iub. *) On top of GTP-U layer. HSPA traffic uses shared channel where the peak rate throughput is shared by all users in the same cell. When the number of user's transmitting data simultaneously increases, the average throughput per user decreases. RN33111EN20GLA0 RNC Architecture and Functionalities 35 35 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC196 in RU20 (RN5.0) • Table Capacity and reference call mix model has been updated • NPS1/NPS1P interfaces has been added toRNC196 architecture • RNC196 capacity step 8 information has been added toRNC 196 capacity • New figure RNC configuration and plug-in locations in capacity step 8 has been added. The actual number of subscribers in one RNC varies depending on how many of the subscribers are in Soft Handover (SHO) state. The operator can affect this with radio network planning, as well as handover and power control parameters. The actual number of base stations controlled by one RNC varies depending on how the Iub is configured. The RNC capacity and the number of BTSs has to be calculated together with Radio Network Planning. Transmission planning needs to be made according to match the anticipated traffic mixes used in RNW planning. RN33111EN20GLA0 RNC Architecture and Functionalities 36 36 © Nokia Siemens Networks RN33111EN20GLA1 RNC196 Capacity Steps RNC196, 8 steps Capacity steps: 1.RNC196/48 2.RNC196/85 3.RNC196/122 4.RNC196/159 5.RNC196/196 6.RNC196/300 (RAS05.1) 7.RNC196/450 (RAS05.1) 8.RNC196/1000 (RU20) • Step 6 is achieved by: – Removing NIP1 and FDU. – Replace HDS-A with HDS-B. – Add more ICSU, GTPU, MXU and A2SU. – Add more NIS1(P). • Step 7 is achieved by upgrade computer units at step 6 to latest version. RNC196/48M The smallest capacity step, RNC196/48M includes the first cabinet and the plug-in- units NIS1 and NIS1P share same unit locations and are mutually exclusive. If redundancy is to be used, RNC196 can be configured to use NIS1 or NIS1P in case of STM1 ATM transport, and to NPGE or NPGEP in case of IP transport. RNC196/85M to 196M In capacity steps 2 to 5, the capacity is expanded by taking additional subracks 1 to 4 into use from the second cabinet. RNC196/300M The capacity of RNC196/196M is increased to 300Mbit/s (Iub) by removing some units and replacing them with other functional units. • NIP1 and FDU are removed. Optionally, one NIP1 can be left to the configuration. • The FDU or the magneto-optical disk drive functionality is replaced by an external USB memory stick supported with OMU. The external USB memory stick can be used for transferring data to or from the RNC. The OMU unit must be upgraded with another hardware variant (CCP18-A) that supports the USB interface. • There are additional units for A2SU, ICSU, MXU, and GTPU. • The number of NIS1/NIS1P units can be increased. • The HDS-A plug-in-unit is replaced by another variant (HDS-B) that supports two hard disk units in one card. RN33111EN20GLA0 RNC Architecture and Functionalities 37 37 © Nokia Siemens Networks RN33111EN20GLA1 RNC 196/1000M in RU20 (RN5.0) The capacity of RNC196/450M is increased to 1000 Mbit/s (Iub) by removing some units and replacing them with other functional unit: • SF10 is removed and replaced with SF10E. • NIS1, A2SU are removed and replaced with NPS1. • GTPU is removed and re-configured as ICSU. • Eight more CDSP-DH units are configured. The table below defines the minimum hardware requirements that must be fulfilled in the RNC196/196M before upgrading to RNC196/300M. Separate unit upgrade packages are available if the requirements are not met. RNC196/450M The RNC196/450M includes the same number of units as the RNC196/300, but the minimum hardware requirements for the units are different. The following table defines the minimum hardware requirements for RNC196/450M. Separate unit upgrade packages are available if the requirements are not met. RN33111EN20GLA0 RNC Architecture and Functionalities 38 38 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Traffic Flow GTP termination in NIU • NIU, NPGE(P) or NPS1(P), covers GTPU functionalities in RNC2600, that is termination of UDP/IP protocol in Iu-PS interface. ATM IP GTP’ GTP UDP ATM GTP’ ATM ATM IP GTP UDP 3G-SGSN NPS1 DMPG SNAP LLC AAL5 AAL5 SNAP LLC GTP appl. AAL5 AAL5 GE IP GTP’ GTP UDP ATM GTP’ ATM GE IP GTP UDP 3G-SGSN NPGE DMPG GTP appl. AAL5 AAL5 RN33111EN20GLA0 RNC Architecture and Functionalities 39 39 © Nokia Siemens Networks RN33111EN20GLA1 RNC196 Capacity Figure RNC196 196/48 196/85 196/122 196/159 196/196 196/300 196/ 450 196 /1000 Number of subscribers 59000 122000 181000 240000 300000 300000 360000 1000000 BHCA 52000 108000 160000 216000 272000 272000 320000 1000000 Erlangs 1300 2700 4000 5400 6800 6800 8000 20000 Iub throughput Mbit/s 48 85 122 159 196 300 450 1000 Number of carriers 384 576 768 960 1152 1152 1152 1800 Number of BTSs 170 256 340 420 512 512 512 600 AAL2UP connectivity Mbit/s (AL2S-D) 950 1450 1950 2400 2800 3594 3594 - AAL2UP connectivity Mbit/s (NP8S1B) - - - - - - - 5100 RRC connected mode users 20000 30000 40000 50000 60000 70000 100000 100000 HSDPA on IuPS Mbit/s 43 94 109 140 176 270 405 900 HSUPA on IuPS Mbit/s 13 23 32 42 53 81 122 270 Number of HSDPA carriers 384 576 768 960 1152 1152 1152 1800 Number of HSDPA BTSs 170 256 340 420 512 512 512 900 Note: Capacity and reference call mix model In case RAN1754: HSPA optimized configuration is used, the maximum possible R99 data capacity is 67% from the maximum throughput of the configuration defined in Table Capacity and reference call mix model. RN33111EN20GLA0 RNC Architecture and Functionalities 40 40 © Nokia Siemens Networks RN33111EN20GLA1 RNC196 Interface Capacity RNC196/ STM-1 / OC-3 E1 / T1 Gigabit Ethernet Unprotected Protected Unprotected Unprotected Protected 48 24 16 + 16 64 8 4 + 4 85 24 16 + 16 96 10 5 + 5 122 24 16 + 16 128 12 6 + 6 156 24 16 + 16 160 14 7 + 7 196 24 16 + 16 192 16 8 + 8 300 24 24 + 24 16 16 8 + 8 450 24 24 + 24 16 16 8 + 8 1000 24 24 + 24 16 16 8 + 8 Mixing STM-1/OC-3, E1/T1, and Gigabit Ethernet interfaces is possible, but the number of cards and interfaces are reduced due to limited number of available slots in the subracks. RN33111EN20GLA0 RNC Architecture and Functionalities 41 41 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC450 in RU20 (RN5.0) RN33111EN20GLA0 RNC Architecture and Functionalities 42 42 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC450 in RU20 (RN5.0) •Common Iub interface has been removed from RNC functionality • Broadband interfaces has been updated - Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. - NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450 • Connectivity rule has been updated - CBR AAL2 Path VCC: PCR - UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR ) Broadband interfaces STM-1 Functional units, NIS1 or NIS1P offer ATM over SDH network interface. NIS1 has MSP 1+1 protection possibility within one plug-in unit and NIS1P between plug-in units. Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit contains four SDH STM-1 (optical) interfaces. OC-3 Functional units, NIS1 or NIS1P offer ATM network interface OC-3. APS 1+1 protection can be used with OC-3 interfaces. Single plug-in unit type NI4S1-B is used by NIS1 and NIS1P. A plug-in unit contains four OC-3 IR-1 (optical) interfaces. Gigabit Ethernet (GE) Functional unit NPGE or NPGEP offers IP over Ethernet interfaces. NPGE or NPGEP is introduced with RAN1225: IP Interface Upgrade for RNC196 and RNC450. For detailed information, see the feature description. NPGEP supports 2N redundancy. Single plug-in unit type NP2GE-B is utilised by NPGE and NPGEP functional units. A plug-in unit contains two GE (optical or electrical) interfaces. Connectivity The AAL2UP connectivity corresponds to the sum of AAL2 path sizes in Iub, Iur, and Iu-CS connections. The limiting factor for the AAL2UP connectivity in steps 1...5 is the A2SU capacity. For steps 6 and 7, the limiting factor is the physical interface capacity, and the AAL2UP connectivity value is derived from the sum of STM-1 interface capacities. The AAL2UP connectivity is consumed as follows: CBR AAL2 Path VCC: PCR UBR+ AAL2 Path VCC: max( 0.1 * PCR, MDCR ) RN33111EN20GLA0 RNC Architecture and Functionalities 43 43 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC450 in RU20 (RN5.0) • HSUPA and HSDPA peak rate information has been updated in CDSP-DH upgrade for HSDPA peak rate per user The RNC450 HSPA capacity *) 10M is for CDSP-C, 21 for CDSP-DH, CDSP-DH upgrade is an optional upgrade HSDPA traffic does not include soft handovers. HSUPA includes 40% soft handover overhead in Iub. 1) On top of GTPU layer HSPA traffic uses shared channel where the peak rate throughput is shared by all users in the same cell When the number of users transmitting data simultaneously increases. the average throughput per user decreases RN33111EN20GLA0 RNC Architecture and Functionalities 44 44 © Nokia Siemens Networks RN33111EN20GLA1 RNC450 Configuration Steps Configuration steps: 1.RNC450/150 2.RNC450/300 3.RNC450/450 • 3 basic capacity option and 6 carrier-optimised option. 1 2 3 RNC450/150 The smallest capacity step, RNC150 includes the first cabinet and the plug-in-units RNC450/300 Expanded capacity to 300 Mbits/s, the RNC can be obtained by adding another cabinet and the necessary plug-in units and connecting internal cabling between the cabinets. RNC450/450 Expanded capacity to 450 Mbits/s, the RNC can be obtained by adding the necessary plug-in units into two subracks. Note: NIS1 and NIS1P share same unit locations and are mutually exclusive. If redundancy is to be used, RNC196 can be configured to use NIS1 or NIS1P in case of STM1 ATM transport, and to NPGE or NPGEP in case of IP transport. Reference: DN0628405 : RNC capacity extensions and upgrade RN33111EN20GLA0 RNC Architecture and Functionalities 45 45 © Nokia Siemens Networks RN33111EN20GLA1 RNC450 Capacity Basic Option RNC450/150 RNC450/300 RNC450/450 Number of subscriber 181000 284000 360000 BHCA 240000 375000 576000 Erlangs 4000 6250 8000 Iub throughput Mbps 150 300 450 Number of carriers 600 900 1152 Number of BTS 200 300 512 AAL2UP connectivity Mbit/s 1950 2800 3594 RRC connected mode users 35000 70000 100000 HSDPA on IuPS Mbps 135 270 405 HSUPA on IuPS Mbps 41 81 122 Number of HSDPA carries 600 900 1152 Number of HSDPA BTS 200 300 512 Note: Capacities with NSN traffic mix model The capacities of carrier-optimized configurations is given in RNC450 carrier- optimized configurations. The actual number of the subscribers in one RNC varies depending on how many of the subscribers are in Soft Handover (SHO) state. You can affect this with radio network planning, as well as handover and power control parameters. The actual number of base stations controlled by one RNC varies depending on how the Iub is configured. The RNC capacity and the number of BTSs should be calculated together with radio network planning. Transmission planning needs to be made accordingly to match the anticipated traffic mixes used in RNW planning. HSPA capacity figures RN33111EN20GLA0 RNC Architecture and Functionalities 46 46 © Nokia Siemens Networks RN33111EN20GLA1 RNC450 Capacity Figure Carrier Optimised RNC450/150 Carrier opt1 RNC450/150 Carrier opt2 RNC450/150 Carrier opt3 RNC450/150 Carrier opt4 RNC450/300 Carrier opt RNC450/450 Carrier opt Number of subscriber 181000 181000 181000 181000 309000 454000 Busy Hour Call Attempt 240000 240000 240000 240000 408000 720000 Erlangs 4000 4000 4000 4000 6800 10000 Iub throughput Mbps 135 105 80 50 180 250 Number of carriers 660 720 780 840 1200 1800 Number of BTS 220 240 260 280 400 600 AAL2UP connectivity Mbit/s 1950 1950 1950 1950 2800 3594 RRC connected mode users 35000 35000 35000 35000 75000 100000 HSDPA on IuPS Mbps 122 95 72 45 163 227 HSUPA on IuPS Mbps 36 28 21 13 49 67 Number of HSDPA carries 660 720 780 840 1200 1800 Number of HSDPA BTSs 220 240 260 280 400 600 Note: Capacities with NSN traffic mix model RNC450 carrier-optimized configurations RNC450 supports the carrier connectivity optimization functionality that can be used to increase the number of carriers by decreasing the Iub throughput at the same time. Also the AMR capacity is increased in some of the carrier-optimized configurations. The carrier-optimized configuration is activated by altering the HSDPA configuration values. For detailed information, see Activating Basic HSDPA with QPSK and 5 codes. RAN1754: HSPA optimized configuration is not supported in carrier optimized configurations. RN33111EN20GLA0 RNC Architecture and Functionalities 47 47 © Nokia Siemens Networks RN33111EN20GLA1 RNC450 Interface Capacity RNC450 STM-1 / OC-3 E1 / T1 Gigabit Ethernet Unprotected Protected Unprotected Unprotected Protected 150 16 8 + 8 or 12 + 12 (if no E1/T1) 16 8 4 + 4 300 24 16 + 16 or 20 + 20 (if no E1/T1) 16 12 6 + 6 450 24 24 + 24 16 16 8 + 8 Mixing STM-1/OC-3 and Gigabit Ethernet interfaces is possible, but the number of cards and interfaces are reduced due to limited number of available slots in the subracks. RN33111EN20GLA0 RNC Architecture and Functionalities 48 48 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC2600 in RU20 (RN5.0) RN33111EN20GLA0 RNC Architecture and Functionalities 49 49 © Nokia Siemens Networks RN33111EN20GLA1 Change of RNC2600 in RU20 (RN5.0) • New standalone OMS in RNC2600 architecture • Number of recommended BTSs has been updated to 1600 BTSs • Values in BHCA calculation have been updated BHCA = AMR Erl· / MHT * 3600 MHT used in the formula is 90s according to NSN traffic profile • Capacity related updates throughout RNC2600 capacity Recommended up to 1600 BTSs The actual number of subscribers in one RNC varies depending on how many of the subscribers are in Soft Handover (SHO) state. The operator can affect this with radio network planning as well as handover and power control parameters. The actual number of base stations controlled by one RNC varies depending on how the Iub is configured. The RNC capacity and the number of BTSs should be calculated together with Radio Network Planning. Transmission planning needs to be made accordingly to match the anticipated traffic mixes used in Radio Network (RNW) planning. RN33111EN20GLA0 RNC Architecture and Functionalities 50 50 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Configuration Steps Configuration steps: 1. RNC2600/step1 2. RNC2600/step2 3. RNC2600/step3 Capacity is licensed • Iub PS data throughput Mbits· • AMR capacity Erl· • Number of carriers 1 2 3 configuration step. RNC2600/step 1 The smallest configuration step RNC2600/step 1 includes the first cabinet and the plug- in-units. Note that NPS1 and NPS1P / NPGE and NPGEP are mutually exclusive. RNC2600/step 2 Configuration extension to RNC2600/step 2 can be obtained by adding the new cabinet, necessary plug-in units. There are more reserved slots for NPGE(P) and NPS1 units than can be installed at the same time - the combined maximum is 14. RNC2600/step 3 Configuration extension to RNC2600/step 3 can be obtained by adding the necessary plug-in units into two sub-racks There is a restriction on a number of NPS1 and NPGE. There is a total of 28 slots and 16 SFU ports available: 1 NPS1 occupies 2 slots and 1 SFU port 1 NPGE occupies 1 slot and 1 SFU port As a result, you cannot exceed either of the available slots or SFU ports. For PIU detail please check DN70474741 : RNC Capacity extension and upgrade RN33111EN20GLA0 RNC Architecture and Functionalities 51 51 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Capacity RNC2600 step 1 RNC2600 step 2 RNC2600 step 3 Number of subscribers 680 000 1 360 000 2 000 000 BHCA (CS) 680 000 1 360 000 2 000 000 CS Erlangs 17 000 34 000 50 000 CS Erlangs (including softhandover) 23 800 47 600 70 000 BHCA (PS) 800 000 1 400 000 2 000 000 DL Iub throughput Mbit/s 1 100 1 800 2 500 DL + UL Iub throughput Mbit/s 1540 2520 3500 Number of carriers 1 440 2 100 2 800 Number of BTSs 1 440 2 100 2 800 RRC connected mode subscribers 100 000 152 000 200 000 Iu-PS HSDPA net bit rate [Mbit/s] 990 1 980 2 250 Iu-PS HSUPA net bit rate [Mbit/s] 297 594 675 HSDPA carriers 1 440 2 100 2 800 HSDPA BTSs 1 440 2 100 2 800 Note: Capacities and reference call mix model Recommended up to 1600 BTSs Iub throughput is the traffic in downlink direction defined in FP level. Additionally, 30% PS traffic in the uplink direction is supported. For Rel99, throughput is calculated in the Iub interface and the Soft Handover (SHO) (40%) are included. For High-Speed Uplink Packet Access (HSUPA), throughput is calculated in the Iu-PS interface from the effective High-Speed Downlink Packet Access (HSDPA) throughput where the SHO is excluded. This means that in the case of HSUPA, if the SHO is added on top of the 30%, and the actual HSUPA throughput in the Iub including the SHO is more than 30% (= 30% * (1+ 40%)). Maximum number of simultaneous HSDPA users in Cell_DCH state RN33111EN20GLA0 RNC Architecture and Functionalities 52 52 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Traffic Flow DSP pool configuration • RNC2600 use CDSP-DH only – Two powerful DSPs on each DMPG • CCH DSPs process CCH for cells • non-CCH DSPs process R99 DCH and HSPA DMCU DMPG PPC DMPG PPC DMPG PPC DMPG PPC CCH non- CCH non- CCH non- CCH CCH non- CCH non- CCH non- CCH RN33111EN20GLA0 RNC Architecture and Functionalities 53 53 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Traffic Flow AAL2 switching in NPS1(P) NIS1(P) or NIP1 A2SU DMPG A2SU NPS1(P) DMPG 1CID AAL2 VCC AAL2 VCC AAL2 VCC NCID 1CID 1CID NCID AAL2 VCC NPS1(P) 1CID NIS1(P) Iub - ATM Iub - ATM Iu-CS/Iur -ATM Iu-CS/Iur -ATM Old NE RNC2600 RN33111EN20GLA0 RNC Architecture and Functionalities 54 54 © Nokia Siemens Networks RN33111EN20GLA1 RNC2600 Interface Capacity RNC2600 STM-1 / OC-3 Gigabit Ethernet Unprotected Protected Unprotected Protected Step 1 48 24 + 24 16 8 + 8 Step 2 80 40 + 40 24 12 + 12 Step 3 112 56 + 56 32 16 + 16 This table shows the maximum number of STM-1/OC-3 and Gigabit Ethernet interfaces possible in the RNC. Both protected and non-protected numbers are shown. Note that mixing STM-1/OC-3 and Gigabit Ethernet interfaces is possible, but the number of cards, and hence the number of interfaces are reduced due to limited number of available slots in the subracks. RN33111EN20GLA0 RNC Architecture and Functionalities 55 55 © Nokia Siemens Networks RN33111EN20GLA1 General Protocol Model Application Protocol Data Stream(s) ALCAP(s) Physical Layer Signalling Bearer(s) Control Plane User Plane Radio Network Layer Signalling Bearer(s) Data Bearer(s) Transport Network Layer Transport Network User Plane Transport Network User Plane Transport Network Control Plane The picture shows general model for protocols in the UTRAN interfaces Iub, Iur, Iu- CS and Iu-PS. In each interface there are two options of transport technology: ATM, and IP over Ethernet. Additionally, an option to use IP over ATM is supported for signalling in Iu-CS and Iu-PS. Protocols can be divided into two layers: Radio Network Layer –protocols handling UTRAN functionalities. The protocols used in an interface are the same regardless of the choice of transport technology used: ATM or IP. Transport Network Layer – protocols handling the actual transmission of data or signalling over the interface. The detail of protocols is specific to a particular transport technology used. Protocols can be divided into three planes according to the type of information: Control Plane – for signalling purpose between network elements. User Plane – for user data. Transport Network Control Plane – this plane only exists when the ATM option is used and user data is carried in AAL2. It is used to dynamically configure AAL2 channels for user plane traffic. The control plane and the user plane, in turn, rely the transport network user plane inside the transport network layer as their bearers. RN33111EN20GLA0 RNC Architecture and Functionalities 56 56 © Nokia Siemens Networks RN33111EN20GLA1 WCDMA L1 RLC MAC FP RNC WBTS UE MGW I ub I u U u RLC MAC PHY ATM AAL2 FP WCDMA L1 CS application PHY ATM AAL2 Iu-UP protocol PHY ATM AAL2 CS application Ethernet-Phy Ethernet-MAC IPv4 UDP Ethernet-Phy Ethernet-MAC IPv4 UDP RTP Iu-UP protocol PHY ATM AAL2 Ethernet-Phy Ethernet-MAC IPv4 UDP Ethernet-Phy Ethernet-MAC IPv4 UDP RTP Protocols in the CS User Plane ATM-based option The figure illustrates protocols used in carrying user plane circuit switched traffic. Both ATM and IP options are shown for Iub and Iu interfaces. 3GPP Release 5 introduces IP transport option as an alternative to ATM transport. Due to the layered structure of the UMTS protocol architecture, the impact on the Radio Network Layer is minimal. However, there is a deep change in the architecture of the transport, in terms of protocols, functionality and network configuration. Since RN4.0, IP based Iu-CS is an option to ATM based transport, and both can be supported simultaneously in RNC. For Iub, there are two features supported: IP based Iub and Dual Iub. Dual Iub feature is different from IP Based Iub in a sense that there are transport bearers over the ATM and IP towards one BTS. IP based Iu-CS is implemented by Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP), which are carried on top of UDP (User Datagram Protocol) and IP. RTP/RTCP protocol provides end-to-end delivery services for data with real-time characteristics, e.g. interactive audio. RTP/RTCP was developed by IETF to overcome the shortcomings of IP network, such as packet loss, reordering and delay. RTP itself does not provide any mechanisms to ensure timely delivery or other Quality-of-Service (QoS) guarantees, but relies on lower layer services to do that. In Iub, the frame protocol (FP) user data is carried over UDP over IP on top of Ethernet. Abbreviations WCDMA – Wideband Code Division Multiple Access AAL2 – ATM (Asynchronous Transport Mode) Adaptation Layer 2 RLC – Radio Link Control MAC – Medium Access Control PHY – Physical layer FP – Frame Protocol RTP – Real-Time transport Protocol UDP – User Datagram Protocol RN33111EN20GLA0 RNC Architecture and Functionalities 57 57 © Nokia Siemens Networks RN33111EN20GLA1 WCDMA L1 RLC MAC FP RNC WBTS UE 3G- SGSN I ub I u U u RLC MAC PHY ATM AAL2 FP WCDM A L1 PS application PHY ATM AAL5 PDCP PDCP IP GTP-U UDP IP GTP-U UDP PHY Link Layer IP GTP- U UDP G n IP GGSN PHY IP GTP- U UDP PHY Link Layer IP Ethernet-Phy Ethernet-MAC IPv4 UDP PHY ATM AAL2 Ethernet-Phy Ethernet-MAC IPv4 UDP Ethernet -MAC PHY ATM AAL5 Ethernet -MAC Ethernet -Phy Ethernet -Phy Protocols in the PS User Plane CN IP-based option ATM-based option The figure illustrates protocols used in carrying user plane packet switched traffic. Both ATM and IP options are shown for Iub and Iu interfaces. The feature IP Based Iu-PS enables the use of cost-efficient IP-over-Ethernet transport at the Iu-PS interface in accordance with the 3GPP release 5 and later specifications. The RNC supports both Ethernet and ATM-based protocol stacks at the Iu-PS interface. In other words, the connection to a certain serving GPRS support node (SGSN) can be based on either Ethernet or ATM transport. For Iub, it is the same as CS user plane figure. In the picture, Release 99 PS data is shown. For HSDPA and HSUPA, additional MAC layers in RNC, WBTS and UE exist. Abbreviations PDCP – Packet Data Convergence Protocol GTP-U – GPRS (General Packet Radio System) Tunnelling Protocol for the user plane UDP – User Datagram Protocol IP – Internet Protocol AAL5 – ATM Adaptation Layer 5 RN33111EN20GLA0 RNC Architecture and Functionalities 58 58 © Nokia Siemens Networks RN33111EN20GLA1 Protocols in the UE Control Plane RNC WBTS UE CN WCDM A L1 I ub I u U u RLC MAC PHY ATM AAL2 FP WCDM A L1 RLC MAC PHY ATM AAL5 SSCOP RANAP MTP3b SCCP PHY ATM AAL5 SSCF-NNI RANAP MTP3b SCCP SSCOP NAS NAS M3UA SSCF-NNI SCTP IP RRC RRC Ethernet-Phy Ethernet-MAC IPv4 UDP PHY ATM AAL2 FP Ethernet-Phy Ethernet-MAC IPv4 UDP PHY ATM AAL5 Ethernet -MAC Ethernet -Phy IP-based option ATM-based option M3UA SCTP IP PHY ATM AAL5 Ethernet -MAC Ethernet -Phy The figure illustrates protocols used in carrying signalling between UE and the network mobile. Signalling between UE and RNC is handled by RRC protocol while signalling between UE and CN is handled by various NAS protocols such as Connection Management (CM), Supplementary Service (SS), etc. Signalling between RNC and CN is handled by RANAP protocol. IP-based control plane at the Iu-PS, Iu-CS, and Iur (to be shown in the next figure) supports the evolution of the mobile core network towards an all-IP network. This feature is introduced as an option to the current ATM-based control plane transport architecture. The message-oriented and reliable SCTP (Stream Control Transmission Protocol) is a new alternative to the unreliable UDP and the reliable but slow TCP protocol. SCTP is described in IETF RFC 3286. M3UA (MTP3 User Adaptation) protocol supports transport of SCCP messages over IP using the services of SCTP. M3UA is described in IETF RFC 3286. Abbreviations NAS – Non Access Stratum RANAP – Radio Access Network Application Protocol RRC – Radio Resource Control SCCP – Signalling Control Connection Part MTP3b – Message Transfer Part Layer 3 broadband SSCF-NNI – Service Specific Coordination Function – Network-to-Network Interface SSCOP – Service Specific Connection Oriented Protocol RN33111EN20GLA0 RNC Architecture and Functionalities 59 59 © Nokia Siemens Networks RN33111EN20GLA1 PHY ATM AAL5 SSCOP SSCF-UNI NBAP WBTS D-RNC PHY ATM AAL5 SSCOP SSCF-NNI RNSAP MTP3b SCCP S-RNC I ub I ur Ethernet-Phy Ethernet -MAC IPv4 SCTP PHY ATM AAL5 SSCOP SSCF-UNI NBAP Ethernet -Phy Ethernet -MAC IPv4 SCTP M3UA SCTP IPv4 Ethernet -Phy Ethernet -MAC PHY ATM AAL5 SSCOP SSCF-NNI RNSAP MTP3b SCCP M3UA SCTP IPv4 Ethernet -Phy Ethernet -MAC Protocols in the Iub and Iur Control Plane IP-based option ATM-based option The figure illustrates protocols used in the control plane of Iub and Iur protocol. Abbreviations RNSAP – Radio Network Subsystem Application Part NBAP – NodeB Application Part SCCF-UNI – Service Specific Coordination Function – User-to-Network Interface RN33111EN20GLA0 RNC Architecture and Functionalities 60 60 © Nokia Siemens Networks RN33111EN20GLA1 User Data and Signalling Flow in RNC RN33111EN20GLA0 RNC Architecture and Functionalities 61 61 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) Permanent Signalling Links Traffic Flow ATM Iub/Iu/Iur IP Iub/Iu/Iur Standalone or Integrated The picture shows traffic flow for permanent signalling links on different type of Iub interface, ATM based and IP based. Permanent signalling links external VCCs to/from ATM based Iub are originated/terminated in NPS1(P). Permanent signalling links IP connections to/from IP based Iub are originated/terminated in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 62 62 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) Common Control Channel Traffic Flow ATM Iub IP Iub The picture shows traffic flow for common control channel on different type of Iub interface, ATM based and IP based. RACH (Random Access Channel) and FACH (Forward Access Channel) are the transport channels used to carry common control channel in uplink and downlink direction, respectively. Common control channel external VCCs to/from ATM based Iub are originated/terminated in NPS1(P). AAL2 switching this type of traffic is also done in NPS1(P). Common control channel IP connections to/from IP based Iub are originated/terminated in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 63 63 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) Dedicated Control Channel Traffic Flow ATM Iub IP Iub The picture shows traffic flow for dedicated control channel on different type of Iub interface, ATM based and IP based. It is carried by the transport channel DCH (Dedicated Channel). Dedicated control channel external VCCs to/from ATM based Iub are originated/terminated in NPS1(P). AAL2 switching this type of traffic is also done in NPS1(P). Dedicated control channel IP connections to/from IP based Iub are originated/terminated in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 64 64 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) CS User Data Traffic Flow ATM Iub IP Iu-CS The picture shows CS user data flow involving ATM based Iub and IP based Iu-CS. DCH is used and AAL2 switching of traffic is done in NPS1(P). RN33111EN20GLA0 RNC Architecture and Functionalities 65 65 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) PS User Data over DCH ATM Iub IP Iu-CS The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS. DCH is used to carry user data. The GTP termination for Iu-PS connection is performed in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 66 66 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) PS User Data over FACH/RACH ATM Iub IP Iu-CS The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS. FACH and RACH are used to carry user data for uplink and downlink, respectively. The GTP termination for Iu-PS connection is performed in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 67 67 © Nokia Siemens Networks RN33111EN20GLA1 SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) HSPA User Data ATM Iub IP Iu-CS The picture shows PS user data flow involving ATM based Iub and IP based Iu-PS. HS-DSCH (high-speed downlink shared channel) and E-DCH (enhanced dedicated channel) are the transport channels used to carry traffic in downlink and uplink, respectively. The GTP termination for Iu-PS connection is performed in NPGE(P). RN33111EN20GLA0 RNC Architecture and Functionalities 68 68 © Nokia Siemens Networks RN33111EN20GLA1 Review of RNC Architecture and Interfaces • UMTS Networks and NSN RNC Overview • RNC2600 • RNC196 and RNC450 • RNC Protocol and Transport Options • Traffic Flow Examples • Review Questions RN33111EN20GLA0 RNC Architecture and Functionalities 69 69 © Nokia Siemens Networks RN33111EN20GLA1 Review Questions 1. Describe the role of functional units: ▪ RSMU ▪ ICSU ▪ DMCU ▪ OMU ▪ MXU ▪ SFU 2. Explain the difference between NIS1 and NPS1. 3. List all the configuration steps of RNC2600 and the number of cabinets and subracks equipped with plug-in units. RN33111EN20GLA0 RNC Architecture and Functionalities 70 70 © Nokia Siemens Networks RN33111EN20GLA1 WCDMA L1 RNC WBTS UE MGW I ub I u U u MAC PHY ATM FP WCDM A L1 CS applicatio n PHY ATM PHY ATM AAL2 CS application Ethernet-Phy Ethernet-MAC IPv4 Ethernet-Phy Ethernet-MAC IPv4 UDP Iu-UP protocol PHY ATM Ethernet-Phy Ethernet-MAC IPv4 UDP Ethernet-Phy Ethernet-MAC IPv4 UDP IP-based option ATM-based option Review Questions 4. Fill in the missing protocol names in CS domain. RN33111EN20GLA0 RNC Architecture and Functionalities 71 71 © Nokia Siemens Networks RN33111EN20GLA1 Review Questions 5. Draw the flow of PS data over HSPA through the RNC. Assume that both IP-based Iub and Iu-PS are used. SFU MXU RSMU HDD WDU ICSU DMCU OMU OMS SWU DMCU ICSU MXU NIU - NPGE(P) MXU NIU - NPS1(P) RN33111EN20GLA0 RNC Architecture and Functionalities 72 72 © Nokia Siemens Networks RN33111EN20GLA1 RNC Functional Units This is optional module In case participant has not attend RNC Architecture e-learning or IPA2800 platform following slides should be cover training RN33111EN20GLA0 RNC Architecture and Functionalities 73 73 © Nokia Siemens Networks RN33111EN20GLA1 RNC Functional Units in RU20 SFU MXU HDD WDU EHU TBU ICSU DMCU OMU OMS SWU DMCU ICSU NIU - NIS1(P)* A2SU* GTPU* MXU NIU - NIP1* PDU NIU - NPGE(P) NIU - NPS1(P) * Only unit in RNC196 / RNC450 RSMU RRMU Availability performance calculations describe the system from the availability point of view presenting availability Availability performance values are calculated for the complete system, that is, redundancy principles are taken into account In reference to ITU-T Recommendation Q.541, intrinsic unavailability is the unavailability of an exchange (or part of it) due to exchange (or unit) failure itself, excluding the logistic delay time (for example, travel times, unavailability of spare units, and so on) and planned outages The results of the availability performance calculations for the complete system are presented in the Predicted availability performance values. Some units from earlier releases are no longer exist, because The functionalities are embedded to other units, or The unit is no longer supported The units are: GTPU, functionalities are embedded to NPS1(P) and/or NPGE(P) A2SU, functionalities are embedded to NPS1(P) RRMU, functionalities are distributed to ICSU and OMU/RSMU NIS1(P), replaced with NPS1(P) NIP1, no more PDH interface are supported RN33111EN20GLA0 RNC Architecture and Functionalities 74 74 © Nokia Siemens Networks RN33111EN20GLA1 RNC Units Redundancy Type Functional Unit Redundancy principle DMCU SN+ EHU None ICSU N+1 MXU 2N OMS None OMU 2N RSMU 2N SFU 2N TBU 2N WDU 2N OMS HDD 2N NPS1 None NPGE None NPS1P 2N (MSP 1+1 / APS 1+1) NPGEP 2N Duplication (2N) If the spare unit is designated for only one active unit, the software in the spare unit is kept synchronised so that taking it in use in fault situations (switchover) is very fast. The spare unit can be said to be in hot stand-by. This redundancy principle is called duplication, abbreviated "2N". Replacement (N+1) For less strict reliability requirements, one or more spare units may also be designated to a group of functional units. One spare unit can replace any unit in the group. In this case, the execution of the switchover is a bit slower, because of the spare unit synchronisation (warming) is performed as a part of the switchover procedure. The spare unit is in cold stand-by. This redundancy principle is called replacement, abbreviated "N+1". Load sharing (SN+) A unit group may be allocated no spare unit at all, if the group acts as a resource pool. The number of units in the pool is selected so that there is a certain amount of extra capacity. If a few units of the pool are disabled because of faults, the whole group can still perform its designated functions. This redundancy principle is called load sharing, abbreviated "SN+". None Some functional units have no redundancy at all. This is because a failure in them does not prevent the function or cause any drop in the capacity. RN33111EN20GLA0 RNC Architecture and Functionalities 75 75 © Nokia Siemens Networks RN33111EN20GLA1 SFU: Switching Fabric Unit (1/2) Functions: • Serves as the main switch fabric of the exchange. • Provides redundant, fully accessible and non-blocking connection at ATM level. • Supports both point-to-point and point-to-multipoint connection topologies. • Handles various ATM service categories. Type: Switching Fabric Redundancy: 2N Plug-in unit: SF10, SF10E and SF20H Interfaces: Network Interfaces Low bit-rate network interface and control computer (via MXU) OMU from the unit computer of SFU via MXU Switching Fabric Unit (SFU) The Switching Fabric Unit (SFU) provides a part of the ATM cell switching function. It provides redundancy, full accessibility and is non-blocking at ATM connection level (that is, if input and output capacity is available, the connection can be established). SFU supports point-to-point and point-to-multipoint connection topologies, as well as differentiated handling of various ATM service categories. High capacity network interface units and multiplexer units are connected to the 2N redundant SFU. RN33111EN20GLA0 RNC Architecture and Functionalities 76 76 © Nokia Siemens Networks RN33111EN20GLA1 SFU: Switching Fabric Unit (2/2) SF10 SF10E SF20H SF10 The main function of the SF10 plug-in unit is to switch ATM cells from 16 input ports to 16 output ports. The cell switching uses self-routing where the cell is forwarded by hardware to the target output port based on the given output port address. The correct cell sequence at the output port is guaranteed. The switching fabric supports spatial multicasting. The total switching capacity of SF10 is 10 Gbit/s with 16x16 switching fabric port interfaces capacity of each is 622 Mbit/s. Port interfaces are duplicated for redundant multiplexer units and redundant network interface units. The active input is selected inside the SF10 SF10E The main function of the SF10E (C110899) plug-in unit is to switch cells from input to output ports. Within the SF10E switching is protocol independent, meaning that before the cells are sent to the fabric they are encapsulated inside a special fabric frame. In the case of APC based legacy port cards, the cells are always ATM cells, but network processor based units (such as MX1G6) are able to process any protocol. SF20H The main function of the SF20H plug-in unit is to switch cells from input to output ports. Within the SF20H, switching is protocol independent. This means that before the cells are sent to the fabric, they are encapsulated inside a special fabric frame. With a total of 32 ports, the SF20H provides a 2.5 Gbit/s serial switching fabric interface (SFPIF2G5). Several SFPIF2G5 ports can be combined for higher capacity ports RN33111EN20GLA0 RNC Architecture and Functionalities 77 77 © Nokia Siemens Networks RN33111EN20GLA1 MXU: Multiplexer Unit (1/2) Functions: • Enable connection of the low-to-medium bit-rate signal processing units and computer units, as well as low-bit-rate network interface units, to the ATM switch fabric • Multiplexes/de-multiplexes traffic from tributary units to the ATM switching fabric vice versa. • ATM layer functions such as header translation, UPC/NPC parameter control, OAM functions, traffic management. Type : Multiplexer Unit Redundancy : 2N Plug-in unit : MX622-B, MX622-C, MX622-D, MX1G6, MX1G6-A Multiplexer Unit (MXU) The MultipleXer Unit (MXU) multiplexes traffic from tributary units to the ATM switching fabric. Therefore, it allows the efficient use of switching resources for low bit rate network interface units and computer units with small to moderate bandwidth requirements. The MXU also includes part of the ATM layer processing functions, such as policing, statistics, OAM, buffer management and scheduling. Control computers, signal processing units, and low bit rate network interface units are connected to the switching fabric via the MXU, which is a 2N redundant unit. The RNC has several pairs of MXUs, depending on the configured capacity. For more information, see RNC2600 capacity. RN33111EN20GLA0 RNC Architecture and Functionalities 78 78 © Nokia Siemens Networks RN33111EN20GLA1 MXU: Multiplexer Unit (2/2) MX622-B/C/D MX1G6-/A MX622 The ATM Multiplexer Plug-in Unit 622 Mbit/s MX622 multiplexes and demultiplexes ATM cells and performs ATM Layer functions and Traffic Management functions. MX1G6 and MX1G6-A The MX1G6 and MX1G6-A are 1.6 Gbit/s ATM multiplexer plug-in units. They multiplex and demultiplex ATM cells and perform ATM layer and traffic management functions. The MX1G6 and MX1G6-A enable connecting low speed units to the switching fabric and improve the use of switching fabric port capacity by multiplexing traffic from up to twenty tributary units to a single fabric port. RN33111EN20GLA0 RNC Architecture and Functionalities 79 79 © Nokia Siemens Networks RN33111EN20GLA1 A2SU: AAL Type 2 Switching Unit (1/2) Functions: • Performs minipacket switching of AAL2 CPS. • Collects AAL2 layer statistics This unit is no longer needed when network interface unit NIP1 and/or NIS1(P) are not used in RNC. Type : Signal Processing Unit Redundancy : SN+ Plug-in unit : AL2S-B/D A2SU AAL2 Switching Unit (A2SU) performs switching of AAL Type 2 CPS packets between external interfaces and signal processing units. A2SU operates in the load- sharing redundancy configuration (SN+). The AAL Type 2 guarantees bandwidth-efficient transport of information with limited transfer delay in the RAN transmission network. If Iub, Iu-CS, and Iur have been IP upgraded, A2SU units are not used. RN33111EN20GLA0 RNC Architecture and Functionalities 80 80 © Nokia Siemens Networks RN33111EN20GLA1 A2SU: AAL Type 2 Switching Unit (2/2) AL2S-D AL2S-B AL2S, AL2S-A, AL2S-B The AAL2 Switching unit (AL2S, AL2S-A or AL2S-B plug-in unit) serves to demultiplex AAL2 channel from AAL2-VC, maps the AAL2 payload to AAL5 or AAL0, terminates VC containing AAL2, AAL5 or AAL0 and performs traffic and performance management and statistics collection for AAL2. AL2S-D The AAL2 Switching unit (AL2S-D plug-in unit) serves to demultiplex AAL2 channel from AAL2-VC, maps the AAL2 payload to AAL5 or AAL0, terminates VC containing AAL2, AAL5 or AAL0 and performs traffic and performance management and statistics collection for AAL2 RN33111EN20GLA0 RNC Architecture and Functionalities 81 81 © Nokia Siemens Networks RN33111EN20GLA1 OMU: Operational and Management Unit (1/2) Functions: • Cellular management – Handles all RNC's crucial upper-level system maintenance functions – Serves as an interface between OMS and the other units of the network element – Maintains radio network configuration and recovery – Houses radio network database and ATM/IP configuration database – Has dedicated storage devices • Basic maintenance – Hardware configuration management – HMS supervision – Centralised recovery functions Type: Computer unit with a dedicated storage device unit as a sub-unit Redundancy: 2N Plug-in unit: CCP10, CCP18-A Operation and Maintenance Unit (OMU) The RNC always includes a duplicated (2N) OMU to provide high availability and minimized interruptions in usage (see ¨Redundancy principles). Duplicated system disk units are connected to and controlled by the OMU. The system disk units contain the operative software and the fallback software of the RNC. The cellular management functions of the OMU are responsible for maintaining the radio network configuration and recovery. The OMU monitors the status of the network and blocks the faulty units if necessary. The OMU contains the radio network database, ATM/IP configuration database, RNC equipment database and alarm history database. The OMU unit further contains basic system maintenance functions and serves as an interface between the RNC and the OMS unit. In the event of a fault, the unit automatically activates appropriate recovery and diagnostics procedures within the RNC. The unit has the following interfaces: a duplicated SCSI interface that connects mass memory devices an Ethernet interface; an auto-sensing 10 base-T/100 base-TX interface, which can be used, for example, as a management interface of the network element a service terminal interface which provides support for debugger terminals a multiplexer interface that allows termination of ATM virtual connections to the computer unit, thus supporting both inter-processor communication and termination of external connections in the network element (used, for example, for signalling or network management purposes). a duplicated hardware management system interface (see RNC hardware management and supervision) a USB 1.1 port and drivers for loading software or making backups locally to the RNC RN33111EN20GLA0 RNC Architecture and Functionalities 82 82 © Nokia Siemens Networks RN33111EN20GLA1 OMU: Operational and Management Unit (2/2) CCP18-A CCP 10 CCP10 The Control Computer with 800 MHz Pentium III-M processor (CCP10) acts as the central processing resource in the IPA2800 system computer units. The CCP10 incorporates an Intel Mobile Pentium III-M Microprocessor with 133MHz SDRAM memory on DIMM modules. CCP10 has ATM connections to other plug-in units. This is done by an interface to ATM multiplexer (MX622-B /-C). CCP10 has an interface to the Hardware Management System (HMS) which is implemented in CCP10 as two Hardware Management Nodes (HMN): the HMS Master Node (HMSM) and HMS Slave Node (HMSS). CCP10 has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16 devices into the SCSI bus (including CCP10). CCP10 has two SCSI interfaces because the mass memory system is 2N redundant. Current Ultra2 SCSI is also supported. The timing and synchronization of CCP10 is provided by Timing and Synchronization plug-in unit (TSS3). TSS3 provides 19.44 MHz clock signal for real time clock and UX ASIC. There are two V.24/V.28 based serial interfaces for service terminals to provide an interface for controlling and monitoring CCP10. CCP10 has two 10 Base-T /100 Base-TX /1000 Base-T Ethernet interfaces to connect to LAN. In addition to the interfaces discribed above CCP10 gets the - 48 V DC supply and HMN’s power feed through back plane connectors. CCP10 is assembled into subrack SRA1 and SRA2. There can be more than two CCP10 units in the subrack RN33111EN20GLA0 RNC Architecture and Functionalities 83 83 © Nokia Siemens Networks RN33111EN20GLA1 OMU's Storage Device • New plug-in unit HDS-B, consist of two Hard Disk Drive (HDD): One for OMU and another for OMS • 73 GB formatted storage capacity/disk • Redundancy type : 2N • External devices: USB memory stick, one for each OMU (for CCP18-A only) OMU has two dedicated hard disk units, which serve as a redundant storage for the entire system software, the event buffer for intermediate storing of alarms, and the radio network configuration files. Backup copies are made onto a USB memory stick that is connected to the CCP18- A front plate. Only memory sticks can be used. FDU is the functional unit when using the USB memory stick. No separate configuration in the HW database is needed, because the USB memory stick is an external device. When removing the USB memory stick, set the state to blocked, because the system does not do it automatically. In previous deliveries, the MDS-(A/B) magneto optical drive with a SCSI interface is used. FDU is the functional unit. No separate configuration is needed. RN33111EN20GLA0 RNC Architecture and Functionalities 84 84 © Nokia Siemens Networks RN33111EN20GLA1 Configuration and redundancy principle of OMU's storage devices • The two mutually redundant WDUs are connected simultaneously to both OMUs by means of separate SCSI buses. • SCSI connection is shown on the figure beside. (CCP18-A and HDS- B) The USB stick is an optional external device that is not automatically delivered. The operator can choose to use the USB memory stick for backup purposes in RN2.2 new deliveries. When USB memory stick is used (the functional unit is FDU), it is plugged in one CPU card. There is no direct connection to the other CPUs. Only the USB memory stick that is connected to the active OMU can be used. For OMU switchover, two USB memory sticks are needed: one for each OMU. In previous deliveries, the MDS-A plug-in unit is used (the functional unit is FDU). When MDS-A is used, FDU connects to the SCSI 0 bus. It has been left without backup since it is primarily used for facilitating temporary service operations. RN33111EN20GLA0 RNC Architecture and Functionalities 85 85 © Nokia Siemens Networks RN33111EN20GLA1 ICSU: Interface Control and Signalling Unit (1/2) Functions: • Handles signalling transaction and RRM functions: – Signalling protocols to Iu, Iub, Iur and Iu-BC interfaces for ▪ NBAP, RNSAP, RANAP, SABP signalling ▪ ALCAP (Q.2630.1) signalling ,RRC signalling – Termination of the UNI-SAAL, NNI-SAAL/MTP-3 and SCTP/M3UA signalling associations – Monitoring and recovery of the signalling links – Distributed RRM functions ▪ Admission control (AC), Handover control (HC) ▪ Load control (LC) , Packet scheduling (PS) – Location calculations for location-based services Type : Computer Unit with no sub units Redundancy : N+1 Plug-in unit : CCP10, CCP18-A, CCP18-C Interface Control and Signalling Unit (ICSU) The Interface Control and Signalling Unit (ICSU) performs those RNC functions that are highly dependent on the signalling to other network elements. The unit also handles distributed radio resource management related tasks of the RNC. The unit is responsible for the following tasks: • Layer 3 signalling protocols RANAP, NBAP, RNSAP, RRC, and SABP • Transport network level signalling protocol ALCAP • Handover control • Admission control • Load control • Power control • Packet scheduler control • Location calculations for location based services According to the N+1 redundancy principle (for more information, see Redundancy principles).there is one extra ICSU in addition to the number set by the dimensioning rules. The additional unit is used only if one of the active units fails. RN33111EN20GLA0 RNC Architecture and Functionalities 86 86 © Nokia Siemens Networks RN33111EN20GLA1 ICSU: Interface Control and Signalling Unit (2/2) CCP18-A CCP18-C CCP10 CCP18-A, CCP18-C The Control Computer with Pentium M 745 processor (CCP18-A and CCP18-C) acts as the central processing resource in the IPA2800 system computer units. The CCP18-A/-C incorporate an Intel Pentium M 745 Microprocessor with DDR200 SDRAM memory on board The CCP18-A and CCP18-C have ATM connections to other plug-in units. This is done by an interface to the ATM multiplexer (MXU). The CCP18-A and CCP18-C have an interface to the Hardware Management System (HMS). CCP18-A has two Hardware Management Nodes (HMN): the HMS Master Node (HMSM) and HMS Slave Node (HMSS-B). CCP18-C has only the HMS Slave Node (HMSS-B). The CCP18-A has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16 devices into the SCSI bus (including CCP18-A). The CCP18-A has two SCSI interfaces because the mass memory system is 2N redundant. Current Ultra2 SCSI is also supported. CCP18-C does not have a SCSI bus. The timing and synchronisation of the CCP18-A and CCP18-C is provided by the Timing and Synchronisation plug-in unit (TSS3). TSS3 provides 19.44 MHz clock signal for real time clock and UX2 FPGA. There are two V.24/V.28 based serial interfaces for service terminals to provide an interface for controlling and monitoring the CCP18-A and the CCP18-C. The CCP18-A and CCP18-C have two 10 Base-T /100 Base-TX /1000 Base-T Ethernet interfaces to connect to LAN. In addition to the interfaces described above, CCP18-A and CCP18-C get the - 48 V DC supply and HMN’s power feed through back plane connectors RN33111EN20GLA0 RNC Architecture and Functionalities 87 87 © Nokia Siemens Networks RN33111EN20GLA1 Resource and Switch Management Unit (1/2) Functions: • Controls the switch fabrics in RNC • Establishes connections for calls according to requests from the signalling computer units (ICSUs). • Handles DSP resource management. – Allocation of the DSPs and associated computer resources to different tasks, such as macrodiversity combining and data traffic functions. – supervision and management of the DMCU units, including the necessary software upload procedures – management of the ATM connections within DMCU • ATM switching management functions: – Establishment of both internal and external connections via the SFU – Management and control of the SFU, A2SU and MXU. – Transmission resource management. Type : Computer Unit Redundancy : 2N Plug-in unit : CCP10, CCP18-A, CCP18-C RSMU, Resource and Switch Management Unit RSMU controls the switch fabrics in RNC and establishes connections for calls according to requests from the signalling computer units (ICSUs). It also handles DSP resource management. ATM switching management functions comprise: Establishment of both internal and external connections via SFU, including ATM circuit hunting Management and control of SFU, A2SU and MXU Transmission resource management. DSP resource management tasks comprise: Supervision and management of the DMCU units, including the necessary software upload procedures Allocation of the DSPs and associated computer resources to different tasks, such as microdiversity combining and data traffic Management of the ATM connections within DMCU RN33111EN20GLA0 RNC Architecture and Functionalities 88 88 © Nokia Siemens Networks RN33111EN20GLA1 Resource and Switch Management Unit (2/2) CCP18-A CCP18-C CCP10 Redundancy2N TypeComputer unit Plugin unitCCP18-C / CCP18-A / CCP10 Control Computer. Pentium M CCP·sCCCP·sA· Control Computer, Pentium III (CCP10) RN33111EN20GLA0 RNC Architecture and Functionalities 89 89 © Nokia Siemens Networks RN33111EN20GLA1 GTPU: GPRS Tunnelling Protocol Unit (1/2) Function: • Facilitates RNC connections towards the SGSN by performing those RNC-specific Iu user plane functions which are related to GTP protocols – Routing based on GTP tunnel ID – UDP/IP (User Datagram Protocol / Internet Protocol) protocols termination – IP and GTP protocol processing This unit is no longer needed if Iu-PS interface is implemented using new network interface unit, NPS1(P) or NPGE(P) Type : Computer Unit with no sub unit Redundancy : SN+ Plug-in unit : CCP10, CCP18-A, CCP18-C GTPU The GTPU performs the RNC-related IU user plane functions towards the SGSN. The unit is SN+ redundant. The unit is responsible for the following tasks: Iu-PS transport level IP protocol processing and termination Gateway Tunnelling Protocol User Plane (GTP-U) protocol processing RN33111EN20GLA0 RNC Architecture and Functionalities 90 90 © Nokia Siemens Networks RN33111EN20GLA1 GTPU: GPRS Tunnelling Protocol Unit (2/2) CCP18-A CCP18-C CCP10 CCP18-A, CCP18-C The Control Computer with Pentium M 745 processor (CCP18-A and CCP18-C) acts as the central processing resource in the IPA2800 system computer units. The CCP18-A/-C incorporate an Intel Pentium M 745 Microprocessor with DDR200 SDRAM memory on board The CCP18-A and CCP18-C have ATM connections to other plug-in units. This is done by an interface to the ATM multiplexer (MXU). The CCP18-A and CCP18-C have an interface to the Hardware Management System (HMS). CCP18-A has two Hardware Management Nodes (HMN): the HMS Master Node (HMSM) and HMS Slave Node (HMSS-B). CCP18-C has only the HMS Slave Node (HMSS-B). The CCP18-A has a 16 bit wide Ultra3 SCSI bus. It is possible to connect up to 16 devices into the SCSI bus (including CCP18-A). The CCP18-A has two SCSI interfaces because the mass memory system is 2N redundant. Current Ultra2 SCSI is also supported. CCP18-C does not have a SCSI bus. The timing and synchronisation of the CCP18-A and CCP18-C is provided by the Timing and Synchronisation plug-in unit (TSS3). TSS3 provides 19.44 MHz clock signal for real time clock and UX2 FPGA. There are two V.24/V.28 based serial interfaces for service terminals to provide an interface for controlling and monitoring the CCP18-A and the CCP18-C. The CCP18-A and CCP18-C have two 10 Base-T /100 Base-TX /1000 Base-T Ethernet interfaces to connect to LAN. In addition to the interfaces described above, CCP18-A and CCP18-C RN33111EN20GLA0 RNC Architecture and Functionalities 91 91 © Nokia Siemens Networks RN33111EN20GLA1 DMCU: Data and Macro-Diversity Combining Unit Purpose: • WCDMA L1 functions, including macro-diversity combining (MDC) and outer loop power control. • RLC-U and RLC-C protocol processing • MAC-C and MAC-D protocol processing • PDCP (Packet Data Convergence Protocol) protocol processing • GTP termination • Encryption • HSDPA with CDSP-C Type : Signal processing unit with no sub unit Redundancy : SN+ Plug-in unit : CDSP-C, CDSP-DH Data and Macro Diversity Combining Unit (DMCU) The Data and Macro Diversity Combining Unit (DMCU) performs RNC-related user and control plane functions. Each of these units has several state-of-the-art digital signal processors (DSPs) and general purpose RISC processors. The signal processing tasks can be configured and altered dynamically for each DSP. The unit is SN+ redundant. The unit is responsible for the following tasks: UE and L2 related protocols Frame Protocol (FP) Radio Link Control (RLC) Medium Access Control (MAC) The following functions are within protocols: macro diversity combining and outer loop PC: FP ciphering: FP and RLC/MAC Packet Data Convergence Protocol (PDCP): header compression High-Speed Packet Access (HSPA) processing: MAC-shared (MAC-SH) and Enhanced Dedicated Transport Channel (EDCH) RN33111EN20GLA0 RNC Architecture and Functionalities 92 92 © Nokia Siemens Networks RN33111EN20GLA1 DMCU: Data and Macro-Diversity Combining Unit CDSP-C CDSP-DH CDSP, CDSP-B or CDSP-C The Configurable Dynamic Signal Processing Platform (CDSP, CDSP-B or CDSP-C plug-in unit) functions as a CDSP pool. Each CDSP (-B/-C) has 32 Digital Signal Processors (DSPs) on four daughter boards, either type D5510 (CDSP), CIP (CDSP- B), or CIP-A (CDSP-B version 4 and CDSP-C). The daughter boards are used for transcoding, echo cancelling and other applications which need digital signal processing. Four MPC 8260 processors control the DSPs. CDSP-DT, CDSP-DH and CDSP-D The configurable dynamic signal processing platform (CDSP-DT, CDSP-DH and CDSP-D plug-in units) function as CDSP pool. Each CDSP-D (C109045) plug-in unit has 16 multicore digital signal processors (DSP) and a total of 96 DSP cores. Each CDSP-DH (C110830) and CDSP-DT (C111195) has 8 DSPs. The DSP cores are used in transcoding and echo cancelling as well as other applications that need digital signal processing. The DSPs are controlled by four MPC 8280 processors. CDSP-D and CDSP-DT plug-in units are used in MGW and CDSP-DH in RNC. RN33111EN20GLA0 RNC Architecture and Functionalities 93 93 © Nokia Siemens Networks RN33111EN20GLA1 OMS: Operation & Maintenance Server Unit(1/2) Purpose: • RNC element management tasks and local user interface • Provides interface toward higher-level network management function, such as OSS • Provide graphic-based local interface • Processing fault and performance management data • Support for configuration management in RNC • O&M functions which are not handled by other computer units of the RNC • post-processing support for measurement and statistics • peripheral device control Type : Computer unit, with dedicated storage devices and the Ethernet Switch unit as sub-units Redundancy : None Plug-in unit : MCP18-B OMS The Operation and Maintenance Server OMS· is a computer unit which provides an open and standard computing platform for applications which do not have strict real time requirements The OMS provides functions related to external OsM interfaces For example Postprocessing of fault management data Postprocessing of performance data Software upgrade support These functions include both generic interfacing to the data communication network DCN· and application specific functions such as processing of fault and performance management data. implementation of the network element user interface and support for configuration management of the network element This way the OMS provides easy and flexible interfacing to the network element The OMS is implemented with the Red Hat Enterprise Linux · It contains its own disks devices. interfaces for keyboard. mouse and display for debugging purposes. and a LAN ·a·aa·aaa Mbit Ethernet· interface Communication between the OMS and the rest of the network element uses Ethernet The basic services of the OMS are MMI interface implemented as a telnet protocol through which the user can execute the existing MML commands Alarm transfer from network element to network management system NMS· Provides the statistical interface for NMS RN33111EN20GLA0 RNC Architecture and Functionalities 94 94 © Nokia Siemens Networks RN33111EN20GLA1 OMS: Operation & Maintenance Server Unit (2/2) MCP18-B MCP18-B The MCP18-B plug-in unit is used as the management computer unit in network elements. For OMS, MCP18-B B01 or later must be used. The MCP18-B is a Pentium®M based, PC compatible, single slot computer designed to interface to the internal standard PCI bus. The Pentium®M 745 central processing unit (CPU) comes in an Intel 479 ball micro-FCBGA form factor. The Intel Pentium®M chipset (E7501 MCH & P64H2) provides the PCI and PCI-X interfaces. Integrated PCI peripherals provide dual Ethernet, dual SCSI, SVGA and USB interfaces. Scalability RNC OMS is capable of handling capacity of RNC2600, 2 800 WCDMA BTSs and 4 800 cells. RNC OMS is capable of handling different types of mass management operations under the control of NetAct, so that there are management operations going on in parallel towards several elements. Mass operations are used when certain management operations need to be done to certain group of network elements. An example of this are configuration data and software downloads to new base stations. RN33111EN20GLA0 RNC Architecture and Functionalities 95 95 © Nokia Siemens Networks RN33111EN20GLA1 OMS’s Storage Device • New plug-in unit HDS-B, consist of two Hard Disk Drive (HDD): One for OMU and another for OMS • 73 GB formatted storage capacity/disk • Redundancy type : 2N HDS-B capacity and performance Hard disks 73 GB formatted storage capacity/disk Average seek time: read 4.5 ms/ write 5.0 ms Data transfer rate of disk drive: 132.4 MB/s SCSI buses Data transfer rate 160 MB/s (80 MHz) in synchronous mode SCSI bus is 16 bits wide Maximum 16 devices on bus SCSI bus can work in both LVD or SE mode HDS-B The HDS-B plug-in unit is used with the OMU and NEMU units. The computer units serve two 16-bit wide Ultra SCSI buses which connect to the HDS-B through external shielded back-cables. The HDS-B has two independent SCSI buses for two computer units. In the case of OMU the SCSI buses pass through the HDS-B and continue to the other unit of the duplicated pair (OMU only). In the case of NEMU the SCSI buses pass into the HDS-B and end there. It is possible to connect other SCSI devices on the same bus. The maximum number of installed SCSI devices, not counting computer units, is 14. The HDS-B plug-in unit is connected to the hardware management bus the via the bus interface of the HMSS. HDS-B has an interface to two HMS transmission lines via back connectors. RN33111EN20GLA0 RNC Architecture and Functionalities 96 96 © Nokia Siemens Networks RN33111EN20GLA1 Configuration and redundancy principles of OMS storage devices • OMS has two redundant disk with RAID0 configuration • SCSI connection is shown on the figure beside. (MCP18-B and HDS-B) HDS-B The HDS-B serves as a non-volatile memory for program code and data in the MGW and RNC. It connects via the SCSI bus to the OMU and NEMU units. Operating environment of HDS-B The HDS-B plug-in unit is used with the OMU and NEMU units. The computer units serve two 16-bit wide Ultra SCSI buses which connect to the HDS-B through external shielded back-cables. The HDS-B has two independent SCSI buses for two computer units. In the case of OMU the SCSI buses pass through the HDS-B and continue to the other unit of the duplicated pair (OMU only). In the case of NEMU the SCSI buses pass into the HDS-B and end there. It is possible to connect other SCSI devices on the same bus. The maximum number of installed SCSI devices, not counting computer units, is 14. The HDS-B plug-in unit is connected to the hardware management bus the via the bus interface of the HMSS. HDS-B has an interface to two HMS transmission lines via back connectors. The HDS-B has automatically functioning SCSI bus terminators. The HMSS has a separate 2N redundant power feed. The HDS-B gets also 48V DC supply and power feed from the HMSS through back connectors RN33111EN20GLA0 RNC Architecture and Functionalities 97 97 © Nokia Siemens Networks RN33111EN20GLA1 ESA: Ethernet Switch for ATM 24 Ports • Provides physical LAN/Ethernet interfaces for connections between OMS and the other units of the network element. • The ESA24 upgrade increases LAN switching capacity. • Redundant ESA24 is needed for AGPS feature Type: Sub unit to OMS Redundancy: None/2N Capacity/ Performance: 24 physical 10/100 Base-T Ethernet interfaces Ethernet Switch for ATM with 24 Ports (ESA24) The ESA24 plug-in unit provides the Ethernet switch functionality for OMS. 2N redundant ESA24 provides duplicated IP connections towards the A-GPS server. There are two Ethernet ports in the front panel. ESA24 The 10/100 Mbps LAN switch plug-in unit ESA24 functions as the LAN switch unit of the IPA2800 ATM platform. The ESA24 features: Complies with IEEE802.1d Spanning Tree protocol. Store and Forward operation Half and full duplex on all ports IEE802.3X Full Duplex flow control on all ports Back pressure in Half Duplex mode on all ports Priority queuing based on Port or 802.1p None blocking operation and VLAN per 802.1q Address table contains 8000 entries and Port Trunking Differences between ESA12 and ESA24 Increase in FLASH memory from 2 to 8 MB RAM memory 64 MB New operating system (BiNOS) Complies with IEEE802.1w Rapid Spanning Tree protocol Complies with IEEE802.1s Multiple Spanning Tree protocol RN33111EN20GLA0 RNC Architecture and Functionalities 98 98 © Nokia Siemens Networks RN33111EN20GLA1 Standalone OMS • 1RU high server that is mountable to a standard 19 inch rack • Concentrates operation and management traffic and performs operation and management activities towards the RNC and WCDMA Base Stations under control of NetAct • Local management interface towards RNC network elements with basic centralised alarm and performance management capabilities • Capable of handling capacity of RNC2600, 1 600 WCDMA BTSs and 4 800 cells • Capable of handling different types of mass management operations under the control of NetAct Operation and Maintenance Server (OMS) The Operation and Maintenance Server (OMS) unit is responsible for RNC element management tasks. It provides interface to the higher-level network management functions and to local user interface functions. These functions include both generic interfacing to the data communication network (DCN) and application-specific functions like processing of fault and performance management data, implementation of the RNC user interface and support for configuration management of the RNC. This way the OMS provides easy and flexible interfacing to the RNC. In previous releases, OMS is integrated in RNC2600. It is implemented with Intel- based industry standard PC core. It contains own disk devices, interfaces for keyboard and a display for debugging purposes, a serial interface, an USB interface, and a LAN (100 Mbit/s Ethernet) interface. In RN5.0, standalone OMS is introduced. It uses commercial HW: HP DL360 Proliant. This offers better scalability to OMS performance and always offers the latest and best HW technology available. This is the first evolution step towards new technologies - common OMS platform within different technologies. Same OMS applications and functions are available on both platforms. This does not bring any changes to existing OMS interfaces. HP ProLiant DL360 Generation 6: Quad core Nehalem Intel processors 12 GB memory (scalable up to 128 GB) 4 x Mirrored hard discs (4 x 146GB) Dual port network card SCSI card for external devices like data tapes and magneto-optical USB 2.0 ports Height 1U RN33111EN20GLA0 RNC Architecture and Functionalities 99 99 © Nokia Siemens Networks RN33111EN20GLA1 Standalone OMS Benefit: • State-of-the-art feature set • High quality, proven software platform • Scalable, efficient architecture • Accurate status of the network • Local operation interface • Secure software platform • Easy to place and install OMS HW: HP ProLiant DL360 G6 1U rack-mount server Redundancy: None Benefits of standalone RNC OMS The main benefits of Nokia Siemens Networks RNC OMS are outlined below. State-of-the-art feature set Nokia Siemens Networks’ long experience of radio access and mobile data networks management and input based on operator requirements ensure that RNC OMS functionality and feature set are well considered and provide maximum benefit to operators. High quality, proven software platform RNC OMS software is running on top of a carrier grade FlexiPlatform (SW platform). The FlexiPlatform design ensures high availability, reliability, scalability and high performance incorporating innovations from open standards such as Linux and J2EE. RNC OMS is based on the field-proven NEMU unit used in Nokia Siemens Networks 3G networks. Thus a high quality platform and increased benefits of economies of scale are ensured. Scalable, efficient architecture RNC OMS provides scalability of operability architecture via aggregating, parsing and intermediating the operation and management traffic flow between NetAct and access network elements. RNC OMS performs individual management operations to network elements under control of NetAct. RNC OMS is able to perform efficient parallel mass operations towards several network elements and handle different operation and management operations simultaneously to the same network element. These capabilities reduce both the processing and database access load in NetAct management system and overall management data transmission needs. RN33111EN20GLA0 RNC Architecture and Functionalities 100 100 © Nokia Siemens Networks RN33111EN20GLA1 Standalone OMS Interfaces • RNC OMS connects to RNC through Nokia Siemens Networks’ management interface EMT • All fault management, performance management, configuration and software management transactions to/from RNC OMS are transferred over the EMT interface • The NWI3 and EMT management interfaces used in Nokia Siemens Networks WCDMA systems provide sophisticated functional capabilities, reliability and efficiency Benefits of standalone RNC OMS (Cont) Accurate status of the network RNC OMS provides synchronized measurement data from the WCDMA Access Network elements and real-time WCDMA BTS and RNC state supervision and management, giving thus an accurate picture of network status. Reliable, correct information helps operators to make right daily operation and management decisions. It also gives good input to longer-term network planning, enabling operators to plan network investments in a cost efficient manner. Local operation interface RNC OMS offers a local operation interface towards RNC. The interface makes it possible to monitor access networks locally via RNC OMS during network roll-out, upgrade and expansion phases and during regular daily operation, when reasonable. Secure software platform RNC OMS runs on top of FlexiPlatform/Red Hat, gaining thus from the security benefits of Red Hat Linux Security Framework. Industry experts consider the security risk of Linux to be low, thus giving relief to platform software security concerns. Easy to place and install RNC OMS has a compact size and it fits to a standard 19-inch rack. RN33111EN20GLA0 RNC Architecture and Functionalities 101 101 © Nokia Siemens Networks RN33111EN20GLA1 Network Interface Unit PDH (NIP1) • Provides 16 physical electrical PDH (E1/T1/JT1) interface • Execute physical and ATM layer functionalities • Provides ATM header translation, OAM function and Traffic policing. • Provides an optional reference clock for timing and synchronisation • Support Inverse Multiplexing for ATM (IMA) • Redundancy: None • Plugin unit : NI16P1A NIP1 contains PDH E1/T1/JT1 interfaces with Inverse Multiplexing for ATM (IMA) function, which allows for flexible grouping of physical links to logical IMA groups. Normally, the PDH lines are used for connections between RNC and the BTSs. NI16P1A The NI16P1A plug-in unit implements sixteen PDH E1/T1/JT1 based ATM interfaces. The NI16P1A supports IMA, that is, several E1/T1/JT1 interfaces can be grouped into one group that seems like one interface to the upper protocol layers. The NI16P1A makes ATM layer processing related to the traffic management and Utopia address embedding. The NI16P1A also provides a reference clock (that is recovered from the incoming E1/T1/JT1 lines) for the TSS3 plug-in unit. RN33111EN20GLA0 RNC Architecture and Functionalities 102 102 © Nokia Siemens Networks RN33111EN20GLA1 Concept of IMA Tx direction: cells distributed across links in round robin sequence Rx direction: cells recombined into single ATM stream Physical Link #0 Single ATM Cell Stream from ATM Layer IMA Virtual Link IMA Group PHY PHY PHY Physical Link #1 Physical Link #2 IMA Group PHY PHY PHY Original ATM Cell Stream to ATM Layer • Low bit rate transmission lines can be combined into a group that seen as a single virtual link by ATM • IMA sublayer is part of the physical layer. • It is located between the traditional Transmission Convergence sublayer and the ATM layer. RN33111EN20GLA0 RNC Architecture and Functionalities 103 103 © Nokia Siemens Networks RN33111EN20GLA1 Network Interface Unit SDH (NIS1/NIS1P) • Provides STM-1/OC-3 external interface • Execute physical and ATM layer functionalities • Provides ATM header translation, OAM function and Traffic policing. • Provides an optional reference clock for timing and synchronisation, handles bit timing, line coding, and timing recovery • Support MSP1+1 • Redundancy: None/2N • Plugin unit : NI4S1-B NI4S1-B The main functions of the NI4S1-B plug-in unit are the following: implementing adaptation between SDH transport technology and ATM performing ATM layer functions implementing interface to ATM Switch Fabric. The NI4S1-B can also be used to implement four SONET OC-3 interfaces. Operating environment of NI4S1-B NI4S1-B has the following interfaces with its environment: four interfaces with physical medium interface with ATM Switch Fabric (SF10) interface with the Hardware Management System (HMS) interface with TSS3 or TBUF plug-in unit. RN33111EN20GLA0 RNC Architecture and Functionalities 104 104 © Nokia Siemens Networks RN33111EN20GLA1 Network Interface Unit NPS1(P) • Functions: – Provides 8 SDH STM-1/STM-4 interfaces and an RJ45 connector, and handles multiprotocol packet processing at wire speed and network connectivity – Maps ATM cells to/from transmission frame structure of SDH/Sonet. – Performs AAL2 minipacket switching. – Translates ATM header. – Performs UPC/NPC, traffic management, performance management and performance data collection. – Provides optional reference clock for timing and synchronisation. • It supports MSP1+1 / APS1+1 for SDH/Sonet • Redundancy type: NONE or 2N • Plugin unit type – NP8S1, NP8S1-A, NP8S1-B (two slots wide) NP8S1-B, NP8S1-A and NP8S1 The NP8S1-B, NP8S1-A and NP8S1 plug-in units are interface units for IPA2800 network elements that are specifically designed for the optimized use of the Internet Protocol (IP) and the packet environment. NP8S1-B, NP8S1-A and NP8S1 are targeted for the multiprotocol transport interfaces Iu-PS and Iu-CS. The primary transport methods used are Packet over SONET (POS) and IP over ATM (IPoA). NP8S1-B, NP8S1-A and NP8S1 provide multiprotocol packet processing at wire speed and network connectivity with eight optical synchronous digital hierarchy (SDH) STM-1 or synchronous optical network (SONET) OC-3 interfaces. The high processing power of the network processor and the unit computer enable the NP8S1-B, NP8S1-A and NP8S1 plug-in units to process protocol and data at the line interface unit (LIU) instead of the dedicated processing units. The unit NP8S1 also has capacity for two SDH STM-4 or SONET OC-12 interfaces, but they are not supported and cannot be used. NP8S1 and NP8S1-A are only used in MGW, NP8S1-B is only used in RNC. RN33111EN20GLA0 RNC Architecture and Functionalities 105 105 © Nokia Siemens Networks RN33111EN20GLA1 Network Interface Unit NPGE(P) • Functions: – Provides Ethernet interfaces and handles multiprotocol packet processing at wire speed. – Two 1000Base-LX/T (optical or electrical) Gigabit Ethernet interfaces and two 10/100 Base-T (electrical) Fast Ethernet interfaces – Maps IP packet to/from transmission frame structure of Ethernet. – Translates IP header. – Performs traffic management, performance management and performance data collection. – Terminates GTP protocol when used at Iu-PS. • Redundancy type: NONE or 2N • Plugin unit type – NP2GE, NP2GE-A, NP2GE-B NP2GE-B, NP2GE-A and NP2GE The NP2GE-B, NP2GE-A and NP2GE plug-in units are interface units that are specifically designed for the optimized use of the Internet Protocol (IP) and the packet environment. NP2GE-B, NP2GE-A and NP2GE are targeted for the multiprotocol transport interfaces Iu-PS and Iu-CS. The primary transport method type used is IP over Ethernet. NP2GE-B, NP2GE-A and NP2GE provide multiprotocol packet processing at wire speed and also offer the possibility of using both electrical (copper) and optical (fibre) based Ethernet. The high processing power of the network processor and the unit computer enable the NP2GE-B, NP2GE-A and NP2GE plug-in units to process protocol and data at the line interface unit (LIU) instead of the dedicated processing units. NP2GE and NP2GE-A are only used in MGW, NP2GE-B is only used in RNC. RN33111EN20GLA0 RNC Architecture and Functionalities 106 106 © Nokia Siemens Networks RN33111EN20GLA1 Power Distribution System (1/2) Functions: • Distributes the -48 V/-60 V power from the rectifiers or batteries to the equipment inside the RNC cabinets • Consists of: – Cabinet Power Distributor – Subrack Power Distributor • Subrack power distributor controls the cooling equipment of its own subrack on the basis of messages sent by the OMU Redundancy : 2N Units : CPD80/120-A PD20/30 RN33111EN20GLA0 RNC Architecture and Functionalities 107 107 © Nokia Siemens Networks RN33111EN20GLA1 Power Distribution System (2/2) PD20/30 PD20 The Power Distribution Unit 20 A (PD20 plug-in unit) is a subrack level power distribution unit in the IPA2800 network element power feed system. The PD20 provides filtering, power distribution and fan control functions. PD30 The Power Distribution Unit 30 (PD30 plug-in unit) is a subrack level power distribution unit in the Nokia IPA2800 Network Elements power feed system. The PD30 provides filtering, power distribution, and fan control functions. In addition, the PD30 also provides over-current and overvoltage protection, and power dropout stretching. The PD30 incorporates reverse battery voltage protection for accidental installation errors. It continues to operate after correct battery voltage polarity and voltage level have been applied to it. The use of the older fan tray models FTR1 and FTRA damages the equipment. Only use the fan trays FTRA-A and FTRA-B with PD30 RN33111EN20GLA0 RNC Architecture and Functionalities 108 108 © Nokia Siemens Networks RN33111EN20GLA1 Power distribution principle and redundancy To ensure 2N redundancy for the power distribution lines, the RNC cabinets are provided with two independent feeding input branches Each CPD120-A unit contains: • Connectors for one of the two mutually redundant supply lines from the batteries/rectifiers. In this way the two independent input branches are kept separate until the subrack level. • Connectors for four supply lines to the subracks. Each subrack is supplied by a line from both CPD120-As, giving 2N redundancy. • Circuit breakers for the outgoing supply lines, each with 30-A rating The CPD120-A allows for either grounding the 0V lead from the battery or for a use of a separate grounding cable to achieve floating battery voltage. From the CPD120- A unit, the voltage is fed through the subrack-specific PD30 power distribution plug-in units, which have individual 10-A fuses for each outgoing distribution line, to the other plug-in units in a likewise manner as to the cabinets, that is, through two mutually redundant supply lines. The two distribution lines are finally combined in the power converter blocks of individual plug-in units, which adapt the voltage so that it is appropriate for the plug-in unit components. RN33111EN20GLA0 RNC Architecture and Functionalities 109 109 © Nokia Siemens Networks RN33111EN20GLA1 Fuse Connection T B U F T B U F 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 38 FB1 FB2 FB3 FB4 FA1 FA2 FA3 FA4 FA5 and FB5 to fan tray FTRx RN33111EN20GLA0 RNC Architecture and Functionalities 110 110 © Nokia Siemens Networks RN33111EN20GLA1 Timing and Buffering Unit (1/2) Functions: • Responsible for the network element synchronization, timing signal distribution and message transfer functions in the hardware management system • Receives an input timing signal from upper network level, adjusts its local oscillator to long time mean value and delivers this synchronised timing signal as system timing to all plug-in units. • Operates in plesiochronous mode, if all synchronisation are lost • Collect alarms from the PIUs in the same subrack and transfer them to HMS master (OMU) • 3 synchronisation inputs from line interface card • 8 synchronisation outputs support maximum 8-cabinet configuration Redundancy: 2N Plug-in unit: TSS3/A and TBUF New clock plug-in unit variant TSS3-A is implemented in RN5.0 based RNC2600 deliveries. However, TSS3-A can be used with RN4.0 software if Bridge HMX1BNGX version inside the plug-in unit is newer than in RN4.0 release package Due to 2N redundancy a mixed configuration of TSS3 and TSS3-A is not allowed. The same variant must be used for both clock units in each RNC. TSS3/-As generate the clock signals necessary for synchronising the functions of RNC. Normally, TSS3/-A operates in a synchronous mode, that is, it receives an input timing reference signal from an upper level of the network and adjusts its local oscillator to the long time mean value by filtering jitter and wander from the timing signal. It transmits the reference to the plug-in units in the same subrack (all plug-in units are equipped with onboard PLL blocks), as well as to the TBUF units, which distribute the signals to units not directly fed by TSS3/-As. TSS3/-A has inputs for both synchronisation references from other network elements (via the network interfaces) and for those from external sources (options are 2048 kbit/s, 2048 kHz, 64+8 kHz, 1544 kHz, or 1544 kbit/s (TSS3-A)). TSS3-A input is 5 V tolerant. If all synchronisation references are lost, TSS3/-A can operate in plesiochronous mode, that is, by generating independently the synchronisation reference for the units in the network element. TSS3/-As are also involved in the functioning of the HMS bus. They convey HMS messages through the HMS bridge node to the HMS master node. Each OMU has one master node. TSS3-A is designed to conform ITU-T G813, G.703 and Bellcore GR-1244 recommendation. RN33111EN20GLA0 RNC Architecture and Functionalities 111 111 © Nokia Siemens Networks RN33111EN20GLA1 Timing and Buffering Unit (2/2) TSS TBUF TSS3 and TSS3-A The Timing and Synchronization, SDH, Stratum 3 (TSS3 plug-in unit) or the Timing and Synchronization, SDH, Stratum 3, Variant A (TSS3-A plug-in unit) and TBUF plug-in units provide the functionality of the Timing and Hardware Management Bus Unit (TBU) functional unit. This functional unit is responsible for synchronisation, timing signal distribution and message transfer in the Hardware Management System of a network element. The RNC and the MGW configurations have always one duplicated synchronization unit implemented as two TSS3 or TSS3-A plug-in units. The TSS3s or TSS3-As are located in either of the two half-size slots in subracks 1 and 2 of rack 1. The remaining half-size two slots in these subracks are equipped with TBUs, and so are all other such slots in other subracks of the network element. Both TSS3s or TSS3- As form a subsystem which is 2N redundant, so there are always two TSS3 or TSS3- A plug-in units working in active/cold standby fashion. TBUF The Timing Buffer (TBUF plug-in unit) and the TSS3 plug-in units provide the functionality of the Timing and Hardware Management Bus Unit (TBU) functional unit. This functional unit is responsible for synchronisation, timing signal distribution and message transfer in the Hardware Management System of a network element. The RNC and the MGW configurations have always one duplicated synchronization unit implemented as two TSS3 plug-in units. The TSS3s are located in either of the two half-size slots in subracks 1 and 2 of rack 1. The remaining half-size two slots in these subracks are equipped with TBUFs, and so are all other such slots in other subracks of the network element. The redundancy method is 2N. RN33111EN20GLA0 RNC Architecture and Functionalities 112 112 © Nokia Siemens Networks RN33111EN20GLA1 Network Timing and Synchronisation PRC MSC RNC MGW BS MSC PRC BS BS PRC PRC PRC PRC PRC = Primary Reference Clock Synchronization Usually the distribution of synchronization references for RAN NEs (BTS, RNC) is based on a master-slave architecture, where the transport network is used for carrying the synchronization references. In particular, this is the case for base stations. In a master-slave synchronization architecture, a synchronization reference traceable to the Primary Reference Clock (PRC) is carried via the transport network to RAN NEs. Traceability to the PRC means that the synchronization reference originates from a timing source of PRC quality. The characteristics of primary reference clocks are specified in ITU-T Recommendation G.811 [8]. The hierarchical master-slave principle is generally used in traditional TDM based synchronization, where a PRC traceable reference is carried through a synchronization distribution chain via intermediate nodes to RAN NEs. In RAN NEs (BTSs shown in the following figure) the timing reference is recovered from the incoming transport interface (e.g. E1, T1, STM-1). The recovered reference is frequency locked to the original PRC signal, but due to impairments in the transport network there is some jitter and wander in the recovered synchronization reference. RN33111EN20GLA0 RNC Architecture and Functionalities 113 113 © Nokia Siemens Networks RN33111EN20GLA1 RNC Timing and Synchronisation TSS3 NPS1(P) 2 NPS1(P) 3 NPS1(P) 4 CPSY-A CPSY-B TSS3 Timing signal to PIU Timing signal to PIU TBUF TBUF TBUF TBUF Timing Bus 1 Timing Bus 0 Timing Bus 0 Timing Ref. 1 Timing Ref. 2 Timing Ref. 3 ext. Sync Default timing reference in RNC450: Timing ref. 1: NIS1(P) 0 Timing ref. 2: NIS1(P) 1 Timing ref. 3: NIS1(P) 10 Default timing reference in RNC196 Timing ref. 1: NIS1(P) 0 Timing ref. 2: NIS1(P) 1 Timing ref. 3: NIP1 0 RN33111EN20GLA0 RNC Architecture and Functionalities 114 114 © Nokia Siemens Networks RN33111EN20GLA1 Connection principle and redundancy for the timing and synchronisation distribution bus RNC has two separate timing and synchronisation distribution buses to ensure 2N redundancy for the internal timing signal distribution. Each bus has its own system clock (a TSS3/-A plug-in unit), distribution cabling, and timing buffers (TBUF plug-in units). The two TSS3/-A units backing up each other are placed in different subracks (subracks 1 and 2), each of which is powered by a power supply plug-in unit of its own to ensure redundancy for the power supply. Each of these subracks is also equipped with a TBUF plug-in unit, which connects the equipment in the subrack to the other clock distribution bus. The RNAC subracks 3 and 4 and all RNBC subracks have two separate TBUF units, which connect to different clock distribution buses by means of cables of their own. In order to function correctly, the differential buses need terminations in the ends of the bus by means of a termination cable. Due to the expansion of the network element through the capacity steps, the end of the bus and similarly the termination point changes. When a new subrack is taken into use in a capacity step, the cabling must always be moved to the new subrack. Duplicated buses need two terminations, which means that four terminators altogether in each cabinet are required for the HMS and the timing and synchronisation distribution bus RN33111EN20GLA0 RNC Architecture and Functionalities 115 115 © Nokia Siemens Networks RN33111EN20GLA1 External Hardware Unit Functions: • Receive external alarms and send as alarm message to OMU via HMS bus • Drive the optional External Hardware Alarm panel (EXAU-A / EXAU), the cabinet integrated lamp, and possible other external equipment. Redundancy: No Plugin unit: EHAT EXAU EHAT The optional peripheral EXAU-A / EXAU provides a visual alarm of the fault indications of RNC. The EXAU-A / EXAU unit is located in the equipment room. The CAIND/-A is located on top of the RNAC cabinet and provides a visual alarm indicating the network element with a fault. RN33111EN20GLA0 RNC Architecture and Functionalities 116 116 © Nokia Siemens Networks RN33111EN20GLA1 RNC Units Summary Functional Unit (redundancy) Supported HW OMU (2N) CCP18-A WDU (2N) HDS-A or HDS-B, with WDW18, WDW36 or WDW73. FDU (2N) MDS-A OMS (No) MCP18-B (4GB memory) HDD (2N) HDS-A or HDS-B, with WDW73 or WDW147 RSMU (2N) CCP10, CCP18-A, CCP18-C ICSU (N+1) CCP10, CCP18-A, CCP18-C DMCU (SN+) CDSP-C (int. D), CDSP-DH GTPU (SN+) CCP10, CCP18-A, CCP18-C A2SU (SN+) AL2S-D NIU (No or 2N) NI16P1-A, NI4S1-B, NP8S1, NP8S1-A, NP8S1-B, NP2GE, NP2GE-A, NP2GE-B SFU (2N) SF10, SF10E, SF20H MXU (2N) MX622-B, MX622-C, MX622-D, MX1G6, MX1G6-A SWU (No) ESA24 TBU (2N) TSS3, TBUF EHU (No) EHAT PDU (2N) CPD80, CPD120, PD20, PD30 RN33111EN20GLA0 RNC Architecture and Functionalities 117 117 © Nokia Siemens Networks RN33111EN20GLA1 Hardware Management System • Lowest intelligent system • Running on HMS bus, comprises 3 node types: – Master Node, head of HMS – Bridge Node, divide HMS network into subsystem, which physically each subrack. – Slave Node, interface toward PIUs • Function of HMS – Collect equipment data from the equipped PIUs – Transfer of system initialisation data – Collect HW fault notification – Control and supervise external or auxiliary equipments The Hardware Management System (HMS) provides a duplicated serial bus between the master node (located in the OMU) and every plug-in unit in the system. The bus provides fault tolerant message transfer facility between plug-in units and the HMS master node. The HMS is used in supporting auto-configuration, collecting fault data from plug-in units and auxiliary equipment, collecting condition data external to network elements and setting hardware control signals, such as restart and state control in plug-in units. The hardware management system is robust. For example, it is independent of system timing and it can read hardware alarms from a plug-in unit without power. The HMS allows power alarms and remote power on/off switching function. The hardware management system forms a hierarchical network. The duplicated master network connects the master node with the bridge node of each sub-rack. The sub-rack level networks connect the bridge node with each plug-in unit in the sub-rack. RN33111EN20GLA0 RNC Architecture and Functionalities 118 118 © Nokia Siemens Networks RN33111EN20GLA1 Hardware Management System HMMN = Hardware Management Master Node HMSB = HMS Bridge HMSS = HMS Slave HMS Master Node (HMMN) Head of Hardware Management System, which has responsible for example selecting the transfer line and supervision of HMS bridge nodes. Reside on OMU HMS Bridge (HMSB) Divides Hardware Management System into subnetwork, which physically each subrack. Reside on TSS3 and TBUF HMS Slave (HMSS) Interfaces with for example PIU’s power and hardware alarms. Reside on all PIUs except ESA12/24 RN33111EN20GLA0 RNC Architecture and Functionalities 119 119 © Nokia Siemens Networks RN33111EN20GLA1 Change in RU20 Reference reading material: Nokia Siemens NetworksWCDMA RAN, rel. RU20,operating documentation DN70515054: Changes in RU20 DN70357656: Changes in configuration parameters for radio network, ATM transport plan, and IP transport plan Introduction to new SW in this release The RU20 release extends the existing features and introduces new features for capacity enhancement. Enhanced voice and extented data services are improving the end-user experience. In addition to improved end-user experience, new RU20 functionalities like optimized resource management, reduce total cost of ownership. Operators also benefit from the RNC2600 and Flexi WCDMA Multiradio design as well as from the simplicity of the implementation of new services with the ability to quickly deploy new revenue generating applications. Enhanced UltraSite baseband hardware extends the lifetime of installed UltraSite base stations. With RU20, operators have the possibility to enhance data rates inline with current handset development. This gives the operator the possibility to smoothly evolve his network and concentrate on the current actual and relevant features. With RU20 peak data rate enhancements, the operator has the possibility to offer a fixed broadband alternative. With features like decreased latency and higher average throughput applications originally designed for wired internet become more attractive. Features like CS over HSPA, Continuous Packet Connectivity and Flexible RLC improve the spectral efficiency and extend UE battery life. The call set-up time is also shorter. Longer UE availability leads to a higher usage resources, applications and consequently to higher user satisfaction. A set of new HSPA+ features like HSDPA 64QAM, DC-HSDPA, HSUPA 5.8 Mbps and MIMO2x2 feature provide further benefits for the customers. These lead to significant gains in peak rate and average throughput on network level. Also the network capacity in loaded network is increased with low other-cell interference capacity increase. RN33111EN20GLA0 RNC Architecture and Functionalities 120 120 © Nokia Siemens Networks RN33111EN20GLA1 RU20: New MML Programs Q9 DHCP Server Data Handling Use this command group to maintain the data on DHCP server.These commands cover a wide range of maneuvers related to DHCP server: configure and interrogate DHCP server options, configure, modify and interrogate pool basic information, bind and unbind pool with unit and network interface,delete IP pool and interrogate pool binding relationship, add and delete IP address ranges, manage and interrogate DHCP client IP address status, manage DHCP server status,manage and interrogate DHCP server log. UW Preload Handling Use the command to start system preloading,cancel system preloading and interrogating system preloading information The purpose of this document is to describe, on the RN5.0 release level, the MML commands that are used in the management interfaces (such as NetAct and local management interfaces) of Radio Network Controller. This document describes the changes that have been made to MML programs between releases RN4.0 and RN5.0. MMLs with only a few internal changes or guide text changes are not listed in this document. It is possible that command sequences must be modified due to the changes summarised in this document. This document may contain information which is irrelevant to the customer. The relevance of the information depends on the delivered software build. For example, some MML programs are optional and are not automatically included in the software build. For more detailed descriptions please see the corresponding command and operating descriptions. RN33111EN20GLA0 RNC Architecture and Functionalities 121 121 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : Modified MML Programs LJ Bundle and Endpoint Handling NE Signaling Network State Interrogation Q8 IP Qos Configuration Handling QM IP Interface Configuration Handling QR TCP/IP Stack Data Handling US Working State an Restart Handling W7 Licence and Feature Handling WP Signal Processing Service Handling WS Software Package and Status Handling YA EXCHANGE TERMINAL CONFIGURATION HANDLING YB IMA Group Handling YG BFD Supervision Handling YW SDH TRANSMISSION PROTECTION HANDLING RN33111EN20GLA0 RNC Architecture and Functionalities 122 122 © Nokia Siemens Networks RN33111EN20GLA1 Differences in the hardware implementation between RU10 (RN4.0) and RU20 (RN5.0) New plug-in units TSS3-A, Timing and Synchronization, SDH, Stratum 3,Variant A New mechanics Cable-supporting shelves have been changed from CS186-B to CS216-A in RNAC cabinet RNC OMS hardware changes Operation and Management Server (OMS) has been introduced as a standalone network element. HP Proliant DL360 Generation 6 hardware platform is used to support the standalone RNC OMS. For more information, see Standalone RNC OMS product description. Note that the new standalone OMS hardware solution is optional and that MCP18-B plug-in unit hardware is also supported by the RNC. When standalone OMS is introduced, the MCP18-B plug-in unit and the related two HDDs must be removed. The following connections also need to be removed from the RNC rack: •SCSI connections between OMS and the HDD •LAN connection between OMS and Ethernet Switch (ESA24). RN33111EN20GLA0 RNC Architecture and Functionalities 123 123 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC New Alarms RN33111EN20GLA0 RNC Architecture and Functionalities 124 124 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC Changed Alarms RN33111EN20GLA0 RNC Architecture and Functionalities 125 125 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC Changed Alarms RN33111EN20GLA0 RNC Architecture and Functionalities 126 126 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC Alarm system configuration changes RU20 : RNC Removed Alarms • There are no removed alarms in RN5.0 RN33111EN20GLA0 RNC Architecture and Functionalities 127 127 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC OMS Changed Alarms RN33111EN20GLA0 RNC Architecture and Functionalities 128 128 © Nokia Siemens Networks RN33111EN20GLA1 RU20 : RNC OMS New Alarms RU20 : RNC OMS Removed Alarms • There are no removed alarms
Copyright © 2024 DOKUMEN.SITE Inc.