Professional Documents
Culture Documents
02 CN34012EN50GLA0 Open MSS Architecture PDF
02 CN34012EN50GLA0 Open MSS Architecture PDF
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.
Module objectives
Open MSS Overview
Open MSS Hardware Architecture
Open MSS Functional Units
Open MSS Hardware Configuration
Module objectives
Open MSS Overview
Open MSS Hardware Architecture
Open MSS Functional Units
Open MSS Hardware Configuration
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)
Module objectives
Open MSS Overview
Open MSS Hardware Architecture
Open MSS Functional Units
Open MSS Hardware Configuration
AMC
module
Shelf
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.
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
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
27 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.
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.
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)
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.
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)
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
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.
CPRT4-B interfaces:
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.
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.
Open MSS Hardware Architecture
Interconnection of blade, RTM, and backplane
The hardware implementation of functional
units in ATCA HW Platform is based on
interconnection of blade,
blades, RTMs and AMCs. Their RTM, AMC and backplane
interconnection is presented in the figure
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
The two DC PEMs, located at the lower rear side of the 16-
slot 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.
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
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
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
Module objectives
Open MSS Overview
Open MSS Hardware Architecture
Open MSS Functional Units
Open MSS Hardware Configuration
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.
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 even-
numbered SWU.
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.
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 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.
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.
The VMU provides the possibility to use the operating system in a HW-
independent 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.
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.
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).
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:
Module objectives
Open MSS Overview
Open MSS Hardware Architecture
Open MSS Functional Units
Open MSS Hardware Configuration
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.
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).
OMU pair 1 1
CMM pair 1 1
CHU pair 5 3
GPLU 2 0
VMU 43 33