Open MSS Architecture
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Nokia Solutions and Networks Academy Legal notice Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can use the Nokia Solutions and 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 Solutions and Networks. The Nokia Solutions and Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior written agreement of Nokia Solutions and Networks.
2
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module contents Module objectives Open MSS Overview Open MSS Hardware Architecture Open MSS Functional Units
Open MSS Hardware Configuration
4
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module Objectives At the end of this module the participant can: List the benefits of the Open MSS List the MSS product configuration Describe the Open MSS Hardware platform Describe the Open MSS functional units and its corresponding HW configuration List the Open MSS Hardware configuration options
5
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module contents Module objectives Open MSS Overview Open MSS Hardware Architecture Open MSS Functional Units
Open MSS Hardware Configuration
6
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview The Open MSS is a mobile softswitch product offering a wide variety of services. The Open MSS is based on the open, telecommunications industry standard Common Off-The-Shelf (COTS) Advanced Telecommunications Computing Architecture (ATCA) HW platform which together with the distributed SW platform provide excellent scalability and reliability. The Open MSS has full support for GSM, WCDMA and CS over HSPA access networks. The Open MSS has interfaces to LTE-EPC to either function as CS Mobile Softswitch in 3GPP CS Fallback architecture or to provide VoIP service for subscribers attached to the EPS IMS-based Voice over LTE (VoLTE) architectures. The Open MSS simultaneously supports the different functions like CS Mobile Softswitch, MGCF, TAS and NVS in the same physical network element.
7
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview MSS Product Configuration The original role of the MSS was to perform the call control, messaging and mobility control functionalities of a mobile switching center in a 3GPP Bearer Independent Circuit Switched Core Network architecture. Since then Nokia Solutions and Networks MSS has evolved to a multi-purpose mobile and VoIP softswitch, providing rich communication capabilities and registrar function while implementing the requirements of the latest releases of 3GPP standards. MSS product configuration: NSN Open MSS (MSS) Interconnect Border Control Functionality (I-BCF) NSN Open Transit Routing Server (Open TRS)
8
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview Open MSS (MSS) The Open MSS is a product that implements the functionality of the 3GPP standardized MSC Server, Gateway MSC Server and MGCF.
9
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview Interconnect Border Control Functionality (I-BCF) The growing utilization of IP-based interconnection between networks requires the Open MSS to be connected to many different foreign IP. Traditionally, Session Border Controllers (SBCs) have been used to provide these services. However, SBCs require extra investment from the operator. To relieve operators of this expenditure, NSN MSS System can be upgraded to function as Interconnect Border Control Functionality (IBCF) with Open MSS and Interconnect Border Gateway Functionality (IBGF) with the MGW.
10
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview, cont. Parallel with the growing utilization of IP-based transmission both on control and user planes in CSP networks, the number of IP-based interconnections increases in the own PLMN and towards other networks, too. SIP has been standardized by 3GPP for the various network interfaces, and it serves as control plane protocol both on access interfaces (User-Network Interface - UNI), and Network-Network Interfaces (NNI). IP-based interconnection between networks requires the Open MSS to be connected to many different foreign IP networks that have various requirements for flexible screening, traffic separation, security and quality of service (QoS). Traditionally, Session Border Controllers (SBCs) have been used to provide these services. However, SBCs require extra investment from the operator, including the purchase of hardware and software. To relieve operators of this expenditure, NSN MSS System can be upgraded to function as Interconnect Border Control Functionality (IBCF) with Open MSS and Interconnect Border Gateway Functionality (IBGF) with the MGW. The Open MSS acting as I-BCF controls NNI interworking. It provides Application Layer Gateway (ALG) functionality (without firewall capabilities), SIP topology hiding with native B2B User Agent functionality, flexible VLAN configuration and Service Level Agreement (SLA) monitoring. This feature provides CAPEX and OPEX reductions for operators through the elimination of separate SBC network elements. Through the activation of this function in Open MSS, operators can manage their own IP networks, including connections to external networks, more effectively. 11
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview Open Transit Routing Server (Open TRS) The Open TRS is a high capacity transit switch that serves as smooth transition from the TDM-based transit layer to the all-IP Next Generation Networks. It serves as a gateway between the two networks, thus it minimizes the required number of connections between the networks, takes care of the hierarchical routing and addressing, translations and topology hiding.
12
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Overview, cont. The NSN Open Transit Routing Server (Open TRS) is a high capacity transit switch that serves as smooth transition from the TDM-based transit layer to the all-IP Next Generation Networks. This integrated CS voice and VoIP solution maximizes the reuse of the voice core investments since it allows the operator to run the voice business with one core network infrastructure. It also enables innovative solutions and features such as: • High Definition Voice • Web Services interface for Telco-to-Web applications • IP interconnect with Embedded Interconnect Border Control Functionality (I-BCF) The NSN Open TRS serves as a gateway between the two networks, thus it minimizes the required number of connections between the networks, takes care of the hierarchical routing and addressing, translations and topology hiding. Open TRS system is available for: • Transit layer in mobile networks • National transit networks (class 4) • International transit networks (IGW/ICS)
13
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module contents Module objectives Open MSS Overview Open MSS Hardware Architecture Open MSS Functional Units
Open MSS Hardware Configuration
14
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ATCA Introduction The NSN Open Mobile Softswitch (MSS) is a mobile and VoIP softswitch product built on top of the Advanced Telecommunications Computing Architecture (ATCA) hardware platform. ATCA is a series of industry standard specifications for the next generation of carrier grade communications equipment. These specifications are driven by over 100 companies with the PCI Industrial Computers Manufacturers Group (PICMG). The specifications mainly concentrate on three areas: mechanics of building blocks (shelf, blade, mezzanine, rear transition module) Interconnects
hardware management.
15
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ATCA Benefits
16
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. Benefits of ATCA The main strength of ATCA is in its versatility, its ability to support larger volumes, and its capacity to harmonize different platforms. In the long run, ATCA will allow faster time to market and lower costs in terms of both equipment and development, as it will be possible to employ a wide variety of building blocks with minimal modifications. • Modularity and configurability ATCA allows diverse applications to be created in one platform using multiple modules with various interfaces, including CPUs, DSPs, and storage media from different manufacturers. • Redundancy ATCA features many levels of redundancy throughout the system, achieving 99.999% availability (fivenines or carrier grade availability). The option to allow less demanding applications to utilize nonredundant configurations for lower cost is also possible. • Support for Ethernet switching fabric ATCA specifications support various serial-type switching fabrics, such as Ethernet and PCI Express. The NSN ATCA HW platform currently uses 10 Gigabit Ethernet technology. • Scalable capacity Scalability in ATCA is enabled by a centralized switching hub, interconnected to all shelf slots in a star configuration. This allows handling of full-duplex data rates up to 140 Gbit/s per 16-slot shelf when using a 10 Gbit/s switching fabric. With the 16-slot shelf, capacity can be scaled upwards by adding the necessary amount of blades, RTMs and AMC modules. On the cabinet level, more shelves or even cabinets can be added. • Regulatory requirements compliance ATCA adheres to operating requirements and environmental regulations set out by Network Equipment Building System (NEBS) and the European Telecommunications Standards Institute (ETSI). • Hot-swappable units Blades and other field replaceable units (FRUs) are hot-swappable. • Faster time to market Open architecture allows faster innovation and reduced engineering time. 17
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ATCA building blocks An Open MSS network element consists of a set of basic ATCA hardware building blocks: Cabinet: provides enclosure for shelves Cabinets can be interconnected to achieve more scalability. PDU: power feed from site power feed to shelf-level power modules Shelf: provides enclosure, cooling, power and HW management to blades and RTMs Blades (front boards): blades plug into the front side of the shelf. AMCs: advanced mezzanine cards plug into the AMC bay of a blade. RTMs (rear boards): rear transition modules plug into the rear of the shelf. RTMs are extension modules for blades.
18
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ATCA Hardware Cabinet
CPU blade
Hub blade
AMC (Advanced Mezzanine Card) • AMC carrier AMC carrier • AMC module AMC module
Shelf
Shelf interconnecting cables and transceiver modules
19
CN34012EN50GLA0
RTM (Rear Transition Module)
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ATCA Hardware
20
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Changes between M16.0 and Ma16.1 The following hardware items are newly used in Ma16.1: ASH16SET-B 16-slot shelf set ACPI4-B (CPU blade) New functional unit GPLU. CPU blade extensions on Ma16.1: M16.0 based network elements are extended with ACPI4-B CPU blade on Ma16.1 SW level. Shelf extension on Ma16.1: M16.0 based network elements are extended with ASH16SET-B 16-slot shelf set on Ma16.1 SW level. Also on Ma16.1 SW level it is possible to extend shelves up to 5. When adding fourth and/or fifth shelf the second cabinet is also required. The following rules are applied when a replacement of failed HW is required. ACH16-A shelf or ASH16SET-B shelf set are always replaced by ASH16SET-B shelf set. ACPI4-A is always replaced by ACPI4-A to minimize impacts on configuration data. ACPI4-B is always replaced by ACPI4-B. 21
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Changes between Ma16.1 and Ma16.2 The following hardware items are introduced in Ma16.2: CAB216SET-A ASH16SET-A ADPD2-A
22
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Cabinet CAB216SET-A Accommodate up to three shelves
Cabinet dimensions (HxWxD) : • 2000 x 800 x 600 mm (without doors) • 2000 x 800 x 700 mm (with doors)
Cabinet includes wheels for moving the cabinet during installation The cabinet can be installed: • on feet, • onto floor rails, and • directly onto concrete floor or raised floor
Weight of empty cabinets with doors, 132kg
23
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. The CAB216SET-A Equipment Cabinet is designed according to ETSI EN 300 119-4 standard. The cabinet set CAB216SET-A consists of the cabinet frame CAB216-A, two doors, two cable storage shelves, one topmost cable storage shelf, one PDU mounting holder, an installation frame, anti toppling brackets and 3 pairs of support brackets for supporting the shelves. The maximum outer height of the cabinet is 2254 mm. Width with side panels is 598 mm and depth without doors is 600 mm. The mounting width for a shelf inside the cabinet is 500 mm. The lockable doors of the cabinet add 80 mm to the depth dimension (40 mm per door).
24
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ASH16SET-A 16-slot shelf set The ASH16-A ATCA 16-slot shelf houses blades and rear transition modules (RTMs) and provides them power feed, cooling and hardware management functions according to the PICMG ATCA specifications. Up to three shelves can be equipped in one cabinet.
ATCA Shelf ASH16SET-A (front and rear view) There are two types of shelf in Ma16.1 release: - ASH16SET-B 16-slot shelf set - ACH16-A 16-slot shelf 25
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ASH16SET-A 16-slot shelf set The following lists the ASH16SET-A 16-slot shelf set components and related items: ASH16-A shelf, which includes the following components: enclosure with 16 slots for blades at the front and RTMs at the back ATCA compliant backplane a horizontal board and a riser board for power feed and communication between the shelf managers and the fan modules front cable tray rear cable tray three AFAMO-A ATCA fan modules two ADPE2-A ATCA DC power entry modules two ASMGR-A ATCA shelf managers SHALD-B shelf alarm display SHALP-A shelf alarm panel two SHCDM-B shelf data modules CHAF2-A Shelf Air Filter ASFF6-A ATCA slot filler blades and ASFR6-A ATCA RTM fillers 26
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. The ASMGR-A ATCA 16-slot shelf manager is responsible for managing all the field replaceable units (FRUs) in the shelf. The shelf manager ASMGR-A consists of a shelf management carrier containing power supply and interface circuitry and a shelf management module containing the shelf management controller (ShMC). The 16-slot shelf alarm panel (SHALP-A) provides a Telco alarm connector (DB15 male) for routing alarms from the shelf to external devices. The alarm panel is located at the lower rear side of the shelf, next to the power entry module. The shelf alarm panel is connected to the shelf managers through a master-only I2C bus. Only the active shelf manager has access to the alarm panel. The alarm panel is currently not in use. The SHALP-A becomes an optional item starting from the ACH16SET-A revision 08, ASH16SET-A revision 05, and ASH16SET-B revision 04. The 16-slot shelf alarm display (SHALD-B) is located on the front side of the ASH16-A shelf. It contains the following components: • three shelf alarm LEDs (minor, major, critical); these LEDs are not in use • three user definable LEDs; these LEDs are not in use • three fan tray alarm LEDs (left, center, right) • three fan tray OK LEDs (left, center, right) • alarm cutoff button • two serial console interfaces (RJ45) for shelf managers
27
The 16-slot shelf data module (SHCDM-B) is used in the ASH16-A shelf and it is a carrier for: • the FRU SEEPROM • three temperature sensors • air filter presence sensor The shelf data modules are located on the rear side of the shelf, behind the power entry modules. They are attached to the backplane with a connector and with an additional bracket fixed by a screw. The shelf CN34012EN50GLA0 ©2014 Nokia Solutions and Networks. All rights reserved. data modules are field replaceable but can only be accessed by removing the power entry modules.
Open MSS Hardware Architecture ASH16SET-A 16-slot shelf set Power to the shelf is provided by two power distribution units (PDUs). The PDUs are located at the top of the cabinet. Each PDU is able to receive three DC inputs from three dedicated site power supplies or one site power supply that is chained to feed all the three PDU inputs. One PDU provides six DC outputs to three power entry modules (PEMs) on the same side, that is, two outputs to one PEM in each shelf. The power supply system of the shelf, consisting of PDUs and PEMs, is fault tolerant. The shelf will continue operating even when one of the PDUs or PEMs fails. Two outputs of a single PDU and the PEM on the same side are capable of supplying all power required by a whole shelf.
28
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture ASH16SET-A 16-slot shelf set Based on PICMG 3.0 specification for 16 slot ATCA systems The ATCA shelf variant providing the highest amount of payload slots Internal buses • IPMI, HW management and alarms • FI, fabric interface for internal and ext. LAN • BI, base interface for EMB
Power feeding Integrated cooling Board slots • Blade slots • Rear transition module (RTM) slots • Advanced mezzanine card slots, housed in CPU or own carrier blade
Integrated cooling, power feeding, HW management and alarm system Backplane providing point-to-point connections between the boards • NSN ATCA uses dual star connection in backplane • Standard includes also full mesh backplane
29
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Field-replaceable units (FRUs) Field Replaceable units are hardware component that can be removed and replaced on-site separately from other resources FRU types in ATCA Specification are: Blades CPU blade
Hub blade AMC modules (not used in MSS) Rear transition modules (RTMs) RTM for CPU blade RTM for Hub blade
30
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture CPU Blade ACPI4-A The ACPI4-A ATCA CPU Blade is a central processing unit (CPU) in the AdvancedTCA system. The ACPI4-A is a single-width blade that can be equipped to any node slot in the ATCA shelf.
Features : 1 x quad core x86 processor 6 x 2 GB / 4 GB DIMM modules in 3 parallel memory channels. Maximum memory is 24 GB.
31
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture CPU Blade ACPI4-A Front panel interfaces: 1 x single-width AMC bay 1 x serial interface through RJ-45 connector 2 x 1GbE (10/100/1000Base-T) interfaces through RJ-45 connectors
Backplane interfaces: 2 x 10GbE (10GBase-4BX) to the fabric interface through Zone 2 connector 2 x 1GbE (1000Base-T) to the base interface through Zone 2 connector
Interfaces to zone 3: PCIe X8 2 x 1GbE interfaces to the RTM SFP connectors (optional)
32
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture CPU Blade ACPI4-B The ACPI4-B ATCA CPU Blade is a central processing unit (CPU) in the AdvancedTCA system. The ACPI4-B is a single-width blade that can be equipped to any node slot in the ATCA shelf.
Features : 1 x six-core x86 processor 6 x 2 GB / 4 GB / 8 GB DIMM modules in 3 parallel memory channels. Maximum memory is 48 GB.
33
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture CPU Blade ACPI4-B Front panel interfaces: 1 x single-width AMC bay 1 x serial interface through RJ-45 connector 2 x 1GbE (10/100/1000Base-T) interfaces through RJ-45 connectors
Backplane interfaces: 2 x 10GbE (10GBase-4BX) to the fabric interface through Zone 2 connector 2 x 1GbE (1000Base-T) to the base interface through Zone 2 connector
Interfaces to zone 3: PCIe X8 2 x 1GbE interfaces to the RTM SFP connectors (optional)
34
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture CPU Blade
Principle for a redundant SAS connection
Redundant Serial Attached SCSI (SAS) disk cross sharing Storage for the CPU blade is provided on an hard disk, equipped in the CPRT4-A rear transition module. The CPU links to the hard disk via a local I/O hub and a SAS controller on the CPRT4-A Storage redundancy can be provided with SAS disk cross-sharing, where two CPRT4-A RTMs are externally connected via SAS links, and can access each other’s hard disks
35
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Hub Blade AHUB3-A The ATCA hub blade AHUB3-A is the main switch used for internal traffic between nodes in a network element
The hub blade provides connections for two types of networks: Base interface (BI) switch for the network element’s internal traffic (for communication between computer nodes) Fabric interface (FI) switch for communicating with external networks as well as for the network element’s internal user data communication The hub blade is a single-slot wide blade equipped in the two hub slots (slots 8-9) in the 16-slot ATCA shelf. Two hub blades are always required in one shelf for redundancy. In addition, AHUB3-A provides management interfaces towards shelf manager through the base switch, and the hub can also be used for distributing a reference clock signal to other ATCA units (the signal can be either received from an external source or it can be generated locally). Hub blades on different shelves can be chained together through front panel base interface connectors. Larger configurations may require a separate, second-level Ethernet switch, depending on the network topology. 36
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture AHUB3-A
Hub Blade AHUB3-A Front panel interfaces: 4 x 1GbE base interface SFP ports, using optical or electrical transceivers for, respectively, LC or RJ-45 connectors 1 x 10GbE base interface XFP port, using optical transceiver for LC connector 3 x 10GbE fabric interface XFP ports, using optical transceivers for LC connectors 1 x serial (RS-232) RJ-45 management port to unit computer 1 x Fast Ethernet RJ-45 management port to unit computer Additional COM ports and USB port on the front panel are not in use
AHUB3-A Technical Data: Width : Single slot (6 HP) Weight : 1960 g Features • Integrated 1GbE base interface switch (24 ports) and 10GbE fabric interface switch (20 ports) • Master clock generator for distributing synchronized clock signals to other nodes in the network element. • PowerPC-based 833 MHz unit computer, using 1GB DDR SDRAM 37
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture AHUB3-A
Hub Blade AHUB3-A Backplane interfaces through base switch: 14 x 1GbE base interfaces through Zone 2 connector 2 x 1GbE base interfaces towards HBRT3-A via Zone 3 connector 1 x 1GbE base interface to redundant hub blade on the shelf 2 x Fast Ethernet management interfaces to shelf manager via Zone 2 connector Backplane interfaces through fabric switch: 14 x 10GbE (XAUI) fabric interfaces through Zone 2 connector
2 x 10GbE fabric (XAUI) interfaces towards HBRT3-A via Zone 3 connector Other backplane interfaces: 1 x update channel interface via Zone 2 connector IPMB interface and power feed through Zone 1 connector
38
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. Interfaces Front panel interfaces: • 4 x 1GbE base interface SFP ports, using optical or electrical transceivers for, respectively, LC or RJ-45 connectors • 1 x 10GbE base interface XFP port, using optical transceiver for LC connector • 3 x 10GbE fabric interface XFP ports, using optical transceivers for LC connectors • 1 x serial (RS-232) RJ-45 management port to unit computer • 1 x Fast Ethernet RJ-45 management port to unit computer Additional COM ports and USB port on the front panel are not in use. Backplane interfaces through base switch: • 14 x 1GbE base interfaces through Zone 2 connector • 2 x 1GbE base interfaces towards HBRT3-A via Zone 3 connector • 1 x 1GbE base interface to redundant hub blade on the shelf • 2 x Fast Ethernet management interfaces to shelf manager via Zone 2 connector Backplane interfaces through fabric switch: • 14 x 10GbE (XAUI) fabric interfaces through Zone 2 connector • 2 x 10GbE fabric (XAUI) interfaces towards HBRT3-A via Zone 3 connector Other backplane interfaces: • 2 x 8 kHz clock synchronization outputs/inputs to HBRT3-A via Zone 3 connector • 19.44 MHz and 8 kHz clock synchronization interfaces via Zone 2 connector • 1 x update channel interface via Zone 2 connector • IPMB interface and power feed through Zone 1 connector 39
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Hard Disk drive HDS30-A Hard Disk SAS - 300GB Storage for the CPU blade is provided on the hard disk, equipped in the CPRT4-A rear transition module 1 SAS Hard disk drive 300 GB (HDS30-A) provided for the units: • Operation and Maintenance Unit (OMU) and Charging Unit (CHU) Hard disk drive capacity: 300 GB
Hard disk drive interface: redundant SAS HDD storage connection, 3.0 Gbit/s
40
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Rear Transition Module CPRT4-A RTM for CPU blades The CPRT4-A rear transition module provides storage and additional connectivity for the CPU blades. The CPRT4-A is a single-width rear transition module which can be equipped into the corresponding RTM slot where the CPU blade is located in front The CPRT4-A can be used for: • SAS disk cross-sharing: redundant CPU blades can access each other's hard disks on the CPRT4-A • Providing Ethernet connections for the CPU blade, via two external SFP connectors • Providing a serial port and USB connection for the CPU blade
41
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
CPRT4-A
Open MSS Hardware Architecture, cont. CPRT4-A interfaces: Front panel interfaces: • 2 x 1GbE SFP ports using optical or electrical transceivers with, respectively, LC or RJ-45 connectors. • Serial port and 2 x USB ports • SAS interfaces via a single RJ48C connector Backplane interfaces (through zone 3 connectors area): • 2 X 1GbE (if the SFP ports are in use) • serial interface to the CPU blade • 2 X USB interfaces • PCI Express interface to the CPU blade If the Ethernet ports on the CPU blade front panel are configured to be in use, the dual GbE interface between the CPU blade and the RTM is disabled. Thus, the SFP ports would be also disabled on the CPRT4-A.
42
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Rear Transition Module CPRT4-B RTM for CPU blades The CPRT4-B rear transition module provides additional connectivity for the CPU blades. The CPRT4-B is a single-width rear transition module which can be equipped into the corresponding RTM slot where the CPU blade is located in front The CPRT4-B can be used for: • Providing Ethernet connections for the CPU blade, via two external SFP connectors • Providing a serial port and USB connection for the CPU blade
43
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
CPRT4-B
Open MSS Hardware Architecture, cont. CPRT4-B interfaces: Front panel interfaces: • 2 x 1GbE SFP ports using optical or electrical transceivers with, respectively, LC or RJ-45 connectors. • Serial port and 2 x USB ports
Backplane interfaces (through zone 3 connectors area): • 2 X 1GbE (if the SFP ports are in use) • serial interface to the CPU blade • 2 X USB interfaces • PCI Express interface to the CPU blade If the Ethernet ports on the CPU blade front panel are configured to be in use, the dual GbE interface between the CPU blade and the RTM is disabled. Thus, the SFP ports would be also disabled on the CPRT4-B.
44
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Rear Transition Module HBRT3-A RTM for Hub blades HBRT3-A RTM Blade (Ethernet connection) The HBRT3-A rear transition module provides external base and fabric connectivity as well as external synchronization connectivity for the AHUB3-A hub blades.
The HBRT3-A is a single-width rear transition module (RTM) which can be equipped into RTM slots where an AHUB3-A hub blade is located Front panel interfaces: • 2 x 1GbE SFP ports for base interface, using optical or electrical transceivers with, respectively, LC or RJ-45 connectors • 2 x 1GbE/10GbE SFP+ ports for fabric interface, using optical transceivers for LC connectors The two mid-most fabric ports on the front panel are not in use • 2 x SSU/BITS ports for 2.048 / 1.544 MHz external synchronization input/output, using RJ-48C (RJ-45) connectors Zone 3 connections: • 2 x 1GbE base interfaces towards AHUB3-A via Zone 3 connector • 2 x 10GbE fabric interfaces towards AHUB3-A via Zone 3 connector • 2 x 8 kHz clock synchronization outputs towards AHUB3-A via Zone 3 connector • 1 x 8 kHz or 2.048 / 1.544 Mbit/s clock synchronization input from AHUB3-A via Zone 3 connector • IPMB interface and power feed through a paddle board connector 45
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
HBRT3-A
Open MSS Hardware Architecture Interconnection of blade, RTM, and backplane The hardware implementation of functional units in ATCA HW Platform is based on blades, RTMs and AMCs. Their interconnection is presented in the figure
interconnection of blade, RTM, AMC and backplane
The blade is connected directly to the backplane • Zone 1 connectors are used for power connection, testing and hardware management • Zone 2 is reserved for the data transport through fabric and base interfaces. • Zone 3 provides I/O interconnection between blade and RTM The RTM is connected only to the blade (it has no direct connection to the backplane). Zone 3 RTM connector to the CPU blade: A rear transition module (RTM) is managed through its front blade. The RTM and the blade are connected by the RTM's zone 3 connector. The RTM receives its power from the front blade. The RTM Zone 1 connectors are used for power connection. 46
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Shelf Backplane
47
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Power Distribution Subsystem
Power distribution subsystem in a cabinet
The 16-slot shelf (ASH16-A used in ASH16SET-A) power feed subsystem consists of two PDUs (ADPD2-A) and two PEMs (ADPE2-A). For the ASH16-A shelf used in ASH16SET-A shelf set, the power distribution units (PDUs), ADPD2-A, at the top of the cabinet supply -48/-60 VDC power to the power entry modules (PEMs), ADPE2-A, in all shelves. When a cabinet is fully equipped with three shelves, the two ADPD2-A can serve up to six ADPE2-A. Each PDU provides three inputs for -48/-60 VDC battery feed cables and six outputs for 48/-60 VDC power feed cables to the PEM. The two DC PEMs, located at the lower rear side of the 16slot shelf (ASH16-A), supply -48/-60 VDC power to the whole shelf. The backplane is divided into four power branches, and each branch has a redundant power feed. Each ADPE2-A supplies power to the four branches through the backplane Zone 1 connector.
48
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. Power supply redundancy The power supply of the ATCA 16-slot shelf is fault tolerant. The shelf will continue operating even when one of the power entry modules fails. The redundancy is achieved by: • two PEMs, each of which is capable of supplying all power required by the whole shelf • two PDUs • dedicated battery feed cabling to each PDU • four power branches on the backplane • redundant hub blades, redundant shelf managers, and fan tray units are powered from different power rails • each blade and each fan module has access to two redundant power rails on the backplane
49
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture Power Distribution Subsystem Power distribution subsystem in a shelf
Power distribution to units Blades, fan modules and shelf managers receive their power from the PEMs via the shelf backplane. AMCs and RTMs receive their power via the blade to which they are connected to. Shelf managers generate a 3.3 V auxiliary supply voltage to the PEMs, fan modules, shelf alarm panel, shelf alarm display and shelf data modules. Each PEM consists of four power segments (feeds) that share common management, control and supervision functions. The backplane powerfeeds are divided into four segments.
50
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture HW Management Shelf Managers are implemented in the ATCA HW platform as separate field replaceable hardware modules which have their own slots in the shelf Shelf Manager controls all blades and other field replaceable units (FRUs) in the shelf through the intelligent platform management interface (IPMI) Each blade in the shelf has an IPM controller connected to the shelf manager’s shelf management controllers (ShMC) through a redundant intelligent platform management bus (IPMB) The fan modules and the power entry modules are connected to the shelf manager through a bus Shelf Manager has a serial port (RJ-45) (routed to shelf alarm display)
51
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont.
52
ATCA HW Blade internal management - The shelf manager controls all blades and other field replaceable units (FRUs) in the shelf through the intelligent platform management interface (IPMI). Each blade in the shelf has an IPM controller (IPMC) connected to the shelf manager’s shelf management controllers (ShMC) through a redundant intelligent platform management bus (IPMB-0). AMC modules and rear transition modules contain a module management controller (MMC), which interfaces with the IPMC in the controlling blade. The ShMCs, IPMCs and MMCs together form the intelligent platform management (IPM) subsystem. Fan modules and power entry modules are connected to the shelf manager through a master-only I2C bus. - IPMC subsystem overview Each blade contains an Intelligent Platform Management Controller (IPMC) subsystem which provides the ability to monitor, query, and log system management events on the blade. The functions of the IPMC subsystem include controlling the blade state, power supplies, and LEDs, monitoring voltages and temperatures, logging events, and maintaining information on the blade. The IPMC subsystem consists of the following components: • IPM Controller • EEPROM • Local voltage and temperature sensors • Serial interfaces • Power load control The IPMC subsystem communicates with the shelf manager through the Intelligent Platform Management Bus (IPMB). It also stores a Local System Event Log (SEL) and Sensor Data Records (SDR) which can be used for troubleshooting purposes. In addition, the EEPROM contains a Field Replaceable Unit (FRU) information storage. The user can access the information stored in the IPMC subsystem through the system manager. Note: The shelf manager also routes messages between the System Manager Interface and IPMB-0, provides interfaces to system repositories, and responds to event messages. The shelf manager can be partially or wholly deployed on the shelf management controller and/or system manager hardware. There are two shelf managers per shelf. CN34012EN50GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture HW Management ATCA HW is managed via the intelligent platform management interface (IPMI) • Each independent component has IPMI Controller which controls the component and enables connection to system level • ATCA Building blocks are called as Field Replaceable Unit (FRU) The ATCA shelf management system consists of redundant shelf managers in the ATCA shelf and their connections to the FRUs and the system manager software controlling the shelf managers The shelf managers are controlled by the system manager which is a higher level management application which consists of software running on a CPU blade
53
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. FRU information repository All field replaceable units (FRUs) that contain a hardware management controller contain an EEPROM for storing information about the unit itself. This information storage is commonly referred to as a FRU information repository. The repository contains information on the firmware versions, addressing, connectivity, and configuration of the unit. This information can be viewed through the system manager or with shelf manager clia commands. For the shelf alarm display, shelf alarm panel and shelf data module of the 16-slot shelf, only identification information is available, and it is included in the shelf FRU information. Cabinets, PDUs, and cables do not have electronically stored FRU information. Type of wired external alarms - TELCO alarm connector on the shelf alarm panel Telco alarm outputs critical, major and minor, as defined by PICMG 3.0, are supported by the ACH16-A shelf. However, the power alarm output and the reset inputs are not implemented. Using the Telco alarm is optional. The wire output provided by each shelf is a combination of the outputs from both shelf managers. The alarms can be cabled directly to each ACH16-A shelf. An open circuit denotes an active alarm state and a closed circuit denotes no alarm. A lamp panel and a buzzer can be acquired separately. Shelf alarm panel The shelf alarm panel (SHALP-A) provides a Telco alarm connector (DB15 male) for routing alarms from the shelf to external devices. The alarm panel is located at the lower rear side of the shelf, next to the power entry module. The shelf alarm panel is connected to the shelf managers through a master-only I2C bus. Only the active shelf manager has access to the shelf alarm panel. 54
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture IPMI Bus The following figure shows the shelf management system on a conceptual level
55
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture, cont. System manager The system manager is the central management application in the ATCA system, providing a user interface for accessing hardware-related information, such as configuration data and various logs and measurements. The system manager consists of software running on, for example, a redundant pair of CPU blades. The tasks of the system manager include: • handling FRU state transitions, such as hot swaps and resets • storing centralized information on events and alarms in the system • storing FRU information The system manager and the shelf manager are connected through the base interface, and communicate via IPMI commands. The system manager communicates with the shelf manager via IPMI commands encapsulated as remote management control protocol (RMCP) packets. As shelf manager is implemented with hardware platform interface (HPI) that is an abstract layer over RMCP and provides a platform-independent set of programmatic interfaces, the system manager can also communicate with the shelf manager via the commands developed by software platform. The communication between the system manager and the shelf manager can be based on: • remote management control protocol (RMCP) in case of OpenHPI daemon running on the system manager and RMCP server running on the shelf manager • remote procedure call (RPC) protocol in case of IntegralHPI enabled on the shelf manager If the simple network management protocol (SNMP) traps are enabled, the shelf manager sends events to the system manager. Otherwise, the system manager is not able to receive any event from the shelf manager directly. System manager is not part of the ATCA hardware platform. ATCA hardware platform offers only the hardware, the software platforms offer the software functionality. 56
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Architecture IPMB Addressing The Shelf IPMB addressing conventions are: Each of the 16 blades and the two shelf managers within each shelf have a unique IPMB address. For example, blade in the physical slot 4 has an IPMB address 92h and the left shelf manager an IPMB address 10h The two shelf managers have a unique IPMB address: left shelf manager 10h and right 12h. If a blade needs to communicate with either of the physical shelf managers they use these addresses. In that case they are not communicating with the shelf manager, but just a normal field replaceable unit. However, all communication from blades to the shelf manager entity is directed to address 20h, the address of the active shelf manager. Furthermore all field replaceable units controlled by blades (such as AMCs and RTMs) have the same IPMB address as the device controlling them. All such FRUs are identified in addition to the IPMB address of the controlling blade by a field replaceable unit identification number (FRU ID). For example, if the first physical slot in the shelf is occupied by a CPU blade where both AMC bays are occupied and an RTM is in use, the full address of the blade is IPMB 9eh, FRU ID 0, upper bay AMC IPMB 9eh, FRU ID 1, lower bay AMC IPMB 9eh, FRU ID 2, and RTM IPMB address 9eh, FRU ID 3. In a similar manner are addressed all field replaceable units controlled by an active shelf manager. Power entry modules, fan modules, shelf alarm panels, shelf data modules all have IPMB address 20h, but their FRU IDs differ. Use the CLIA fru 20 command to get the list of devices controlled by the active shelf manager and their FRU IDs. 57
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
IPMB Address Conversion Table
58
Physical slot
IPMB address (hexadecimal)
Slot type
1
9E
node blade
2
9A
node blade
3
96
node blade
4
92
node blade
5
8E
node blade
6
8A
node blade
7
86
node blade
8
82
hub blade
9
84
hub blade
10
88
node blade
11
8C
node blade
12
90
node blade
13
94
node blade
14
98
node blade
15
9C
node blade
16
A0
node blade
left shelf manager
10
shelf manager
right shelf manager
12
shelf manager
active shelf manager
20
shelf manager
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module contents Module objectives Open MSS Overview Open MSS Hardware Architecture Open MSS Functional Units
Open MSS Hardware Configuration
59
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Block Diagram
60
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units, cont. The COTS ATCA-based Open MSS is a compact server product, designed with a modular software and hardware architecture, which enables distributed computing and high availability. The functions of the MSS are spread among functional units, each running on top of a multi-processor system. The concept of functional unit allows very versatile configurations of the MSS. From the hardware point of view, a functional unit is a CPU blade which is deployed into a shelf. From the software point of view, a functional unit performs a set of operations that can be seen as an entity from the network element configuration point of view. This allows for flexible hardware configurations that ensure optimal use of power resources and floor space. The virtualization of functional units feature for the Open MSS provides the possibility to deploy MSS functionality on a HW independent way, as far as the virtualization host layer can handle the underlying physical HW. With virtualization it is possible to implement several logical functional units into the same physical functional unit (CPU blade). This feature provides improved performance and utilization of available HW resources. The GISU, VLRU, CMU and STU are virtualized on the VMU. The following figure shows the MSS architecture, where there are native functional units and virtualized functional units shown, which are located into physical host functional units, VMUs.
61
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Switching Unit (SWU) Purpose:
The Hub handles LAN switching for the base and fabric interfaces of the network element. The base interface is used for the internal signaling and management traffic between all the hardware nodes in a shelf. The fabric interface is used for user plane traffic.
Redundancy:
2N
FU content:
• Hub blades • Hub RTMs (only for Shelf 1 used for TDM signaling module)
The units are numbered separately like SWU 0,1,2,3… not as a 2N redundant pair normally like 0-0, 0-1. A pair consists of an odd-numbered and evennumbered SWU.
62
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Operation and Maintenance Unit (OMU) Purpose:
The OMU has dedicated storage devices, which serve as a storage for, for example, the entire system software of the network element as well as for the event buffer for intermediate storing of alarms. The software uploading and downloading is done by OMU.
Redundancy:
2N
FU content:
• CPU blades • Memory modules • CPU blade RTMs • RTMs housed hard disk drives • CSAS cables for hard disk cross-connecting
SW uploading/downloading is done via CPU USB port by using USB stick as a removable media.
63
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units, cont. Alarm outputs In the Open MSS, there are alarm outputs from the OMU in the network element. When the system detects a fault, an alarm is immediately printed out. The overall alarm situation of the network element is set in the alarm outputs in the OMU. The number for an alarm output, which is controlled on the basis of an individual alarm, is determined on the basis of the device type and urgency level of the alarm. Depending on the delivery involved, part of the alarm outputs can be reserved for other controls. Recovery block The role of the recovery block is to control the operating states of the functional units. The recovery functions are: • elimination of the effects of faults • restart control • user interface Faults are eliminated by using the hardware redundancy and restarts of the functional units. At functional unit level, processes and preprocessors can also be used. Recovery has real-time data on the states of functional units. By using this data, it controls the restarts of the system and functional units, so that restarts are carried out quickly and reliably in the correct order. Redundancies and working states of the functional units are hidden from the application program blocks by using logical addressing. When the state data on the functional units is updated in real time, the recovery system maintains a table on the basis of which the operating system is able to direct the logically addressed messages to the correct physical units. The recovery system consists of a centralized and a distributed part. The centralized part is situated in the OMU. Time supervision Time supervision is executed in a hierarchical manner so that the network element functioning as the main maintenance centre in the Operation and Maintenance (O&M) network supervises the time in the other systems of the network. OMU supervises the time in the units that the systems use. The supervision of the network element checks the time of the other systems belonging to the network at 15 minutes' intervals. In individual systems, the time of the units is also checked at 15 minutes' intervals. 64
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Central Memory and Marker (CMM) Purpose:
The central memory handles the routing functions of the MSS. It also contains all system configuration data and master copies of distributed files. In addition, it is responsible for the central functions of signaling. Also parts of statistical unit tasks are migrated into CMM.
Redundancy:
2N
FU content:
• CPU blades • Memory modules
The routing functions of CMM The destination of an incoming call is determined by analyzing the called number in the routing and charging analysis in the Central Memory (CM). There are different types of analyses: • Dialling preanalysis • Extended preanalysis • Priority analysis • Area service number analysis • Origin analysis • Digit analysis • Wildcard analysis • User plane analysis • EOS analysis 65
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Charging Unit (CHU) Purpose:
The Charging Unit collects and stores charging data. In Open MSS, one pair of CHUs is required even in the minimum configuration, five pairs in maximum configuration. IP interconnectivity to billing center is through first CHU pair.
Redundancy:
2N
FU content:
• CPU blades • Memory modules • CPU blade RTMs • RTMs housed hard disk drives • CSAS cables for hard disk cross-connecting
66
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units, cont. The charging functions of CHU The charging functions cover: • collecting and generating call data for billing purposes • collecting and generating call traffic sum data for accounting purposes • storing charging and accounting data in the exchanges • transferring charging and accounting data to post-processing computer systems. The charging functions and the operator's post-processing system are separate functions. The exchanges produce charging data and send it to the post-processing computers for analysis and generating the final subscriber bills. The post-processing system has to contain: • software to handle the structures and contents of the charging data records (CDRs) • capacity to store and process the charging data received from the exchanges • capacity to transfer charging data from the exchanges The charging data records (CDRs) inside CHU CDRs are the only possible way to store call-specific charging data. A CDR is a data package that contains the identification and charging information for one call or event. It consists of a number of defined data fields containing all the information required for the billing of a call, excluding the actual price information. CDRs are stored in blocks to the CHU memory. CDRs are formed in the RAM memory of the charging unit (CHU). CDRs for one call can be generated in more than one network element or exchange. The number of CDRs generated for a call in a network depends on the call case in question. 67
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units IP Directory Unit (IPDU) Purpose:
The IP directory unit is used as a load balancer and IP forwarder for signaling traffic.
Redundancy:
N+1
FU content:
• CPU blade
• Memory modules • CPU blade RTM The IPDU acts as a load balancer for SIP, H.248 and M3UA signaling traffic. The IPDU hides the internal structure of the cluster and balances the incoming load to the GISU units. There is no more need to have own externally visible service identifiers (IP addresses) for each GISU units. Instead the MSS and IPDU advertise only one service identifier per service. In case of GISU failures the load of the failed GISU unit is repartitioned among the working ones. In addition to the load balancing function IPDU is used as IP forwarder. The signaling traffic not balanced by IPDU unit (like LDAP and VLR backup) is IP forwarded to the cluster internal service nodes. In this case the internal service nodes like GISU and VLRU units need own externally visible service identifiers (IP addresses). And because there is no load balancing layer involved, the cluster internal configuration is visible to the external clients. 68
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units General Purpose Linux Unit (GPLU) Purpose:
The General Purpose Linux unit provides the WSI and Ut/XCAP interfaces.
Redundancy:
No redundancy
FU content:
• CPU blade
• Memory modules • CPU blade RTM (optional) GPLU unit is optional. It is based on LinDX and is connected to DX 200 services like messaging and high availability. The Web Service Interface provides a web protocol-based interface (HTTP / SOAP) for MSS and NVS. By using the WSI operators are able to integrate the existing MSS / NVS installation base with future applications. Via the WSI applications may e.g. retrieve mobile subscriber related data from MSS / NVS. The XML Configuration Access Protocol (XCAP) is a 3GPP standards-compliant protocol. This protocol is used by subscribers to manage their supplementary service configuration data.
69
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Virtualization Manager Unit (VMU) Purpose:
The Virtualization manager unit works as a host for virtualized units: CMU, STU, GISU and VLRU
Redundancy:
No redundancy
FU content:
• CPU blade • Memory modules • CPU blade RTMs (only for virtualized STU units)
The VMU provides the possibility to use the operating system in a HWindependent way, as far as the host can handle the underlying physical HW. With virtualization it is possible to implement several logical functional units into the same physical functional unit, VMU. In this way the memory is utilized in a more efficient way and the performance improved.
70
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Statistical Unit (STU) Purpose:
The STU collects performance and measurement data from the network. It also takes care of the lawful interception functionalities and IP connections related to it.
Redundancy:
2N
The statistics collected by the STU provide operators with real-time data on the operation, capacity, and service level of the exchange. There are a large number of measurements, observations, and supervisions for monitoring the exchange operation and call events. The operators can select and define the measurements, observations, and supervisions they want to use in the exchange.
71
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Cellular Management Unit (CMU) Purpose:
The CMU controls the cellular radio network. It also provides system support functions, such as PNP (private numbering plan) translations.
Redundancy:
2N
FU content:
• CPU blades • Memory modules
The main functions of the cellular radio network management are: • Handling location areas under the MSC/MSS (GSM and Universal Mobile Telecommunications System (UMTS)) • Handling BSCs • Handling the BTS cells (GSM), the service area (UMTS) and the auxiliary service area (UMTS) • Handling RNCs (UMTS) • Handling general RNW parameters • NRI and pool area configuration handling • Handling roaming areas (zone codes) (GSM and UMTS) • Handling the Gs-interface (an interface between the MSC and the Serving GPRS Support Node (SGSN)) definitions (GSM) 72
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Generic Signaling Unit (GISU) Purpose:
The GISU combined signaling unit type for Open MSS.
Redundancy:
N+X
FU content:
• CPU blades • Memory modules
The GISU unit is the heart of the Open MSS. It contains former SIGU, BSU, SCPU and PAU functionalities and handles e.g. following interfaces: • Mobile interface (BSC, RNC and I-BTS) • Interconnection interface (SIP, BICC and ISUP) • VoIP interface (NVS as SIP registrar and application server) • IP PBX (SIP) • MGCF (SIP) • Subscriber register interface (HLR and LDAP) • IN Service interface (Core INAP and Camel) • User plane connections to the MGW (H.248) • Primary Rate Access (DSS1) 73
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Visitor Location Register Unit (VLRU) Purpose:
The VLRU contains information about each subscriber who is currently being served by the Open MSS.
Redundancy:
2N
One VLRU pair is the minimum amount in MSS, if it is not used as the Gateway Control Server (GCS).
74
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units, cont. Location Registration (GSM and UMTS) The Location Registration function class includes the functions in the VLRU and the HLR, which are needed in the location update of a GSM or UMTS subscriber in the GSM or UMTS network. In order to be able to route incoming calls, the PLMN keeps track of the location of the mobile station. Location information is stored in functional units called location registers. There are two types of location registers: • the HLR, which contains permanent subscriber information and the address of the current VLRU of the subscriber if it is known • the VLRU, where subscriber data is stored as long as the MS is within the area controlled by that particular VLRU This description covers circuit-switched side location registration. Location Registration (LTE) The evolved packet system (MME) takes care about the LTE user authentication and access interface related tasks. But if the packet access is not suitable for voice calls, the network may be configured to perform a CS fall back. Thus during the subscriber registration procedure, the location of a LTE user is stored also to the MSS/VLRU. It means that HSS/HLR contains access information for PS and CS. These both are returned to application logic which makes the routing decision according to the subscriber services and PS network capabilities. Location update • When an MS changes its location area but remains under the control of the same VLRU, only the location information in the VLRU needs to be updated. • When an MS changes its location area so that it moves to the control area of another VLRU, the information in the HLR also needs to be updated. As soon as this is done, the HLR cancels the subscriber's data from the previous VLRU. • When the MS is turned on/off within the same location area, an IMSI attach/detach is performed. The mobile status (attached/detached) is then updated in the VLRU. 75
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units Redundancy principle The following table shows the redundancy model of each unit:
76
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Functional Units, cont. Redundancy of the functional units Different redundancy techniques are used for backing up the different types of functional units. The units participating in the switching functions or recording of statistical data are backed up according to the 2N redundancy principle, that is, by duplication according to the hot-standby or spare-device method. All signaling units are backed up according to the N+1 principle. 2N redundancy means that there is always one spare unit available to take over the tasks of a faulty unit. N+X means that one or more spare units are used for N number of units, N+1 means that one spare unit is used for N number of units. SN+ means load
sharing without spare redundant functional unit. Extra computer unit(s) can be reserved if needed so that the system can bear the failure of one unit by utilizing the remaining units. The redundancy principles of the already known DX 200 HW units are not changed, GISU unit is the successor of SIGU, BSU, and SCPU so it follows their redundancy model.
77
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Module contents Module objectives Open MSS Overview Open MSS Hardware Architecture Open MSS Functional Units
Open MSS Hardware Configuration
78
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration An Open MSS are expandable from a minimum of one shelf to a maximum of five shelves which are located in two or more different cabinets. The minimum configuration contains a single shelf, and the core units OMU pair and CMM pair are needed to run the network element. Despite of the size of the network element, the amount of these units remains always the same. Capacity can be increased by adding CHU, IPDU, GPLU, STU, CMU, GISU and VLRU units and additional shelves (maximum configurations). Note that the virtualized units STU, CMU, GISU and VLRU reside physically on the VMU unit. The Open MSS configurations are expandable in a way that a configuration can contain one rack with a single shelf up to three racks and 5 shelves. Currently, in M16.1 a maximum of 5 shelves in a double rack is supported, but also three racks are supported because of co-location requirements. 79
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration Minimum Configuration The minimum configuration fits in a single shelf, Shelf 1, which is equipped in the topmost position in the cabinet and consists of the following items: 1 SWU Hub pair 1 OMU pair 1 CMM pair 1 CHU pair
2 IPDU units 1 GPLU unit 4 VMU units
80
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration Maximum Configuration The maximum configuration consists of five shelves in two or more cabinets and includes the following items: 5 SWU Hub pairs 1 OMU pair 1 CMM pair 5 CHU pair
5+1 IPDU unit 2 GPLU unit 43 VMU units
81
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration, cont. CHU pair – The quantity in the element is always based on dimensioning. - Ma16.1: min 1, max 5 - M16.0: min 1, max 3 – Flexible equipping means that there can be shelves with or without CHU pair. Shelf can have more than 1 CHU pair. – Equipping position (slot) flexible can be equipped to next free position in the element. However, we recommend to equip to slot 5 and 6. IPDU unit – The quantity in the element is always based on dimensioning. - Ma16.1: min 1+1, max 8+1 - M16.0: min 1+1, max 2+1 – Flexible equipping means that there can be shelves with or without IPDU pair. Shelf can have more than 1 IPDU pair. – Equipping position (slot) flexible can be equipped to next free position in the element. However, we recommend to equip to slot 7 and 10. GPLU unit – The quantity in the element is always based on dimensioning. - Ma16.1: min 0, max 2+1 - M16.0: min 0, max 0 – Flexible equipping means that there can be shelves with or without GPLU pair. Shelf can have more than 1 GPLU pair. – Equipping position (slot) flexible can be equipped to next free position in the element. However, we recommend to equip to slot 7 and 10. 82
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration Maximum Configuration Table below summarizes unit quantities in maximum configurations for two releases (M16.1/M16.2 and M16.0). Unit
83
M16.1/ M16.2
M16.0
SWU Hub pair
5
3
OMU pair
1
1
CMM pair
1
1
CHU pair
5
3
IPDU
5+1
2+1
GPLU
2
0
VMU
43
33
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.
Open MSS Hardware Configuration Capacity and availability The main capacity figures for the Open MSS (double-rack configuration) in M16.2 are: 16 million VLR capacity 8 million 2G/3G/VoIP subscriber dynamic VLR capacity 6.5 million busy hour call attempts (BHCA) (NSN’ profile) 13 million BHCA (basic profile)
up to 300 000 simultaneous calls power consumption: 1000 BHCA / W The Open MSS delivers availability of 99.99976%.
84
CN34012EN50GLA0
©2014 Nokia Solutions and Networks. All rights reserved.