M 1 HW

Nokia Siemens Networks MSC
Server, Product Description
DN00292692
Issue 8-0-1
Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of
its products and services. We would like to encourage you as our customers and users to join
us in working towards a cleaner, safer environment. Please recycle product packaging and
follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Siemens Networks for any additional information.
Nokia Siemens Networks MSC Server, Product Description
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2012/1/28. All rights reserved
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.
Id:0900d805808f9346
DN00292692
Issue 8-0-1
Table of Contents
This document has 68 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
DN00292692
Issue 8-0-1
1
1.1
1.2
1.2.1
1.2.2
1.2.3
MSC Server overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Benefits of the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
MSS product configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Nokia Siemens Networks MSC Server . . . . . . . . . . . . . . . . . . . . . . . . . 12
Nokia Siemens Networks Mobile VoIP Server (NVS) . . . . . . . . . . . . . . 13
Interconnect Border Control Functionality (I-BCF). . . . . . . . . . . . . . . . . 14
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
MSC Server functionalities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Subscriber data management in the MSC Server . . . . . . . . . . . . . . . . .
Control functions in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobility management in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Roaming and handover in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intelligent Network functionalities in the MSS . . . . . . . . . . . . . . . . . . . .
Charging and accounting in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . .
SIP in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSC Server interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.7.1
4.7.1.1
4.7.1.2
4.7.1.3
4.7.1.4
4.7.2
4.7.2.1
4.7.2.2
4.7.2.3
4.7.2.4
4.7.2.5
4.7.2.6
4.7.2.7
4.7.2.8
4.7.2.9
4.7.2.10
4.7.2.11
Services in MSC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supplementary services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IN services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messaging services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multimedia and circuit switched data call in the MSS . . . . . . . . . . . . . .
Unstructured Supplementary Service Data . . . . . . . . . . . . . . . . . . . . . .
Location services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features for cost optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fax support in all-IP networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Codec support in MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A interface over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CS over I-HSPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Value Added Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MultiSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
One Number Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMS over LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit Switched Fallback (CSFB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Voice over LTE (VoLTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMS Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SM traffic filtering and blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Presence and Message Waiting Indicator . . . . . . . . . . . . . . . . . . . . . . .
Calling Name Presentation (CNAP). . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIP IP PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MultiSIM Short Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Id:0900d805808f9346
16
16
16
19
19
20
20
21
21
25
25
26
27
28
28
29
29
29
29
30
32
33
34
34
35
35
36
37
38
40
40
40
41
42
4.7.3
4.7.3.1
4.7.3.2
4.7.3.3
4.7.3.4
4.7.3.5
4.7.3.6
Operability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
M3UA load balancer in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
IP Realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
SIM-based authentication in the NVS . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Multipoint A/Iu-CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Remote and automated SW management . . . . . . . . . . . . . . . . . . . . . . . 44
Real-time user plane monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.3.10
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.10.1
5.10.2
MSC Server hardware architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

MSS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Integrated MSS architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Functional units in MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Charging Unit (CHU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Central Memory and Marker (CMM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Cellular Management Unit (CMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Signaling Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
IP Directory Unit (IPDU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
General Purpose Linux Unit (GPLU). . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Operation and Maintenance Unit (OMU) . . . . . . . . . . . . . . . . . . . . . . . . 50
LAN Switching Unit (SWU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Statistical Unit (STU). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Visitor Location Register Unit (VLRU). . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Redundancy principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
MSS availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
MSS mechanical design and power supply . . . . . . . . . . . . . . . . . . . . . . 52
Capacity of first delivery MSS, upgraded MSS, and upgraded MSSu . . 59
Capacity of Integrated MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Upgrade paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
MSS site requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Exchange room layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Typical power consumption of MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

MMI system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuration management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Network Element Management Unit (NEMU) . . . . . . . . . . . . . . . . . . . . . 66
System maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Remote User Information Management . . . . . . . . . . . . . . . . . . . . . . . . . 68
Id:0900d805808f9346
DN00292692
Issue 8-0-1
List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
DN00292692
Issue 8-0-1
MSC Server access domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local switching in MSS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Positioning the MSS in mobile networks . . . . . . . . . . . . . . . . . . . . . . . .
Positioning the MSS/NVS in a VoIP architecture. . . . . . . . . . . . . . . . . .
I-BCF in the MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Control entities in MSS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A interface over IP with TC in MGW . . . . . . . . . . . . . . . . . . . . . . . . . . .
CS over I-HSPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMS over LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A voice over LTE architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SMS Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Real-time user plane monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Block diagram of MSS, NVS, and MSSu . . . . . . . . . . . . . . . . . . . . . . . .
Block diagram of Integrated MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSS cabinets and layout, M14 first delivery . . . . . . . . . . . . . . . . . . . . .
Cabinet types in upgraded MSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSSu cabinet types (part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MSSu cabinet types (part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cabinet types available in integrated models . . . . . . . . . . . . . . . . . . . .
Id:0900d805808f9346
10
11
13
14
15
17
33
34
36
38
39
45
48
49
54
55
56
57
58
List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Redundancy methods of functional units . . . . . . . . . . . . . . . . . . . . . . . . 51

Dimensions of MSS cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Weight of MSS cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Power consumption and heat dissipation in MSS cartridges and cabinets
62
Power consumption of cabinets in standalone models . . . . . . . . . . . . . 62
Power consumption of cabinets in the integrated models and in the MSSu
63
MML commands execution tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Id:0900d805808f9346
DN00292692
Issue 8-0-1
Summary of changes
Summary of changes
Changes made between issues 8-0-1 and 8-0-0
Section General Purpose Linux Unit (GPLU) has been added. Table Redundancy
methods of functional units has been updated with the GPLU.
References to LTE Fast Track have been replaced by IMS-based VoLTE throughout the
document.
The following new features have been introduced in M15.0 MSS:
Circuit-Switched Fallback (CSFB)

SIP IP PBX
MultiSIM Short Message

The whole document has been rewritten to reflect the changes due to the introduction
of the new Advanced Telecommunications Computing Architecture (ATCA) hardware
platform and the M16.0 software release.
Changes made between issues 5-0-0 and 4-0
The following sections have been modified:
DN00292692
Issue 8-0-1
Nokia Siemens Networks MSC Server overview

MSS Supplementary Services
Id:0900d805808f9430
MSC Server overview
1 MSC Server overview

Nokia Siemens Networks MSC Server (MSS) is a mobile softswitch product offering a
wide variety of services, including 3GPP defined teleservices, asynchronous and synchronous bearer and supplementary services. It provides Service Switching Function
(SSF) logic for supporting Customised Applications for Mobile Network Enhanced Logic
(CAMEL) and Core Intelligent Network Application Protocol (INAP) based Intelligent
Network (IN) procedures. The MSC Server also offers standalone Voice over IP (VoIP)
registrar and server functionality.
Nokia Siemens Networks MSC Server provides full support for GSM, WCDMA, and CS
over HSPA access networks. Nokia Siemens Networks MSS simultaneously supports
different functions in the same physical network element.
The MSS can have interfaces to LTE Evolved Packet Core (EPC) and can either
function as a circuit switched (CS) mobile softswitch in the 3GPP CS Fallback architecture, or to provide VoIP services for subscribers attached to the Evolved Packet System
(EPS) through IMS-based Voice over LTE (VoLTE) architectures.
The MSS can be seamlessly integrated into a 3GPP IP Multimedia Subsystem (IMS) allIP communication network as Media Gateway Control Function (MGCF) and, with the
Nokia Siemens Networks Mobile VoIP Server (NVS) functionality, as Telecommunications Application Server (TAS). With the NVS functionality, the MSS can also provide
VoIP services in a standalone mode.
The dynamic and static capacities of the MSS are fully shared between different functions. Therefore, it offers control plane interworking function (IWF) between different
network domains.
A complete MSS System also incorporates Nokia Siemens Networks Multimedia
Gateway (MGW) and Circuit Switched Data Server (CDS). The MGW supports GSM,
WCDMA, I-HSPA, FEMTO, CS over HSPA, and Evolved Packet System (EPS)
accesses. It implements CS-MGW and IM-MGW functionalities in a single product. It
also offers a full set of interfaces to CS core domains and all-IP IMS networks.
The Nokia Siemens Networks Circuit Switched Data Server is an integrated part of the
MSS System. It provides interworking function for mobile-originating and terminating
circuit switched data calls. It is logically part of the user plane, but it is a separate network
element that is connected to the MGW.
The MSS System provides native support for Internet Protocol (IP), Time-division Multiplexing (TDM), and Asynchronous Transfer Mode (ATM) based transmission of control
and user plane traffic. These factors make the MSS a safe and long term investment
both in technical and economic terms.
Where to find more information
For more information on the MSS System and its network elements, see MSS System
Overview in MSS System documentation.
For more information on CDS, see the Circuit Switched Data Server (CDS), Product
Description.
For more information on Nokia Siemens Networks NetAct, see NetAct System Principles in NetAct product documentation.
Id:0900d805808e1867
DN00292692
Issue 8-0-1
1.1
MSC Server overview
Benefits of the MSS

The MSS is based on the proven and durable Nokia Siemens Networks DX 200
hardware platform which, together with the distributed software platform, provides excellent scalability and reliability.
One system for GSM, WCDMA, CS over HSPA, and LTE access networks
The MSS System supports GSM, WCDMA, and CS over HSPA circuit switched access
technologies. It supports services for subscribers in the same network element on an
access agnostic way. This capability offers smooth roaming among different domains by
offering the same services for all subscribers independent of the used radio access
network. This One System concept enables a cost-efficient rollout of new access technologies, minimizing the number of network elements at all stages of the network evolution.
The MSS System supports SMS over LTE and CS Fallback functionalities as specified
by 3GPP, thus allowing seamless introduction of LTE for mobile broadband data access
along with SMS and CS voice support for subscribers camping on Evolved UTRAN (EUTRAN).
The NVS functionality of MSS provides 3GPP compliant VoIP services for subscribers
who are attached to various packet switched mobile or fixed access networks like
GPRS, HSPA, LTE, or xDSL. Circuit-switched mobile services of the MSS are also available for VoIP subscribers registered in the NVS. The resources of the same MSS are
shared dynamically among CS mobile and VoIP subscribers. Moreover, the same subscriber can be served on CS and VoIP accesses simultaneously. The MSS enables the
introduction of VoIP services in a network for subscribers in an evolutionary way, while
operating only one network element and one set of services for CS and VoIP accesses.
In this way, capital and operating expenditure can be kept low. The NVS functionality
also makes MSS investments protected for long term.
The MSS System can be integrated into any communications networks as it supports
IP, TDM, and ATM transport technologies. A safe integration is also ensured by supporting interfaces and signaling protocols like ISDN User Part (ISUP), Telephone User Part
(TUP), or Digital Subscriber Signaling System No. 1 (DSS1) towards legacy public
switched telephone networks (PSTNs). Figure 1 MSC Server access domains below
illustrates various access domains of the MSS.
DN00292692
Issue 8-0-1
Id:0900d805808e1867
MSC Server overview
Figure 1
MSC Server access domains
Operational cost savings

Local switching in a Multimedia Gateway saves transmission and interconnect costs.
MGWs can be located closer to subscribers and local calls can be switched locally
without a long MSS transmission loop. In addition, transmission bandwidth requirement
per voice call in the MSS network is approximately one third of the requirement for traditional TDM-based networks. This factor allows savings in transmission costs in long
distance calls as well.
Operators can save site costs and operation and maintenance (O&M) work because the
MSS System elements have the highest subscriber density out of all CS core solutions.
The distributed system architecture makes is possible to locate each function where it
is most economical and efficient. For example, MGWs can be located at remote
BSC/RNC/eNB sites where they are as close to the subscribers as possible. On the
other hand, the MSSs can be located freely where it is the easiest to arrange operation
and maintenance support. Thus the number of sites can be reduced to a minimum.
The MSS saves transmission costs due to local switching by MGWs. The distributed
architecture allows optimizing network interconnections and saving on site costs. The
logic of local switching is illustrated in Figure 2 Local switching in MSS System below.
10
Id:0900d805808e1867
DN00292692
Issue 8-0-1
Figure 2
MSC Server overview
Local switching in MSS System
Networks that use IP backbone with the MSS System do not need a Transit MSS layer.
This is due to the simple and efficient operation of the IP-based network and the shared
traffic interfaces in MGWs. An MGW has conventional Gigabit Ethernet or STM-1 interfaces that are shared by all traffic directions. Thus fluctuation in traffic amount and direction in the backbone can be accommodated in the interfaces without a need for
modifications in the hardware configuration. Routing is also taken care of by the IP protocols in the backbone.
The MSS System with IP transport is simpler to operate than a traditional MSS System
with TDM transport. This brings savings in O&M work as the Transit MSS layer is eliminated from large networks.
With native support of different fixed and mobile packet switched networks like xDSL, IHSPA, and LTE, and with the related VoIP server functionality, the MSS provides a cost
efficient solution for introducing VoIP service in CSP networks without the need for
deploying new network elements.
Long-term investment protection
On the radio access side, the MSS System primarily supports the GSM A interface and
3G Iu-CS interfaces. To reduce the total number of network elements and to enable
better usage of transport resources, Nokia Siemens Networks has also implemented the
GSM Ater interface between the Base Station Subsystem (BSS) and the MGW. Therefore, standalone transcoders are unnecessary in the BSS, and floor space and power
requirements can be reduced in all areas with Nokia Siemens Networks GSM radio
network.
The MSS System also supports A and Iu-CS interfaces over IP. These capabilities are
evidence of Nokia Siemens Networks continuous commitment to develop both GSM
and 3G networks and to provide IP-based connectivity on all supported interfaces.
Support for A and Iu-CS interfaces over IP also helps operators drive down operation,
transmission, and maintenance costs.
DN00292692
Issue 8-0-1
Id:0900d805808e1867
11
MSC Server overview
With native support of CS over HSPA access, Nokia Siemens Networks MSS System
helps communication service providers (CSPs) exploit the spectral efficiency that HSPA
provides for voice calls when both terminals and radio access networks support the
functionality. Comparing EFR codec usage in GSM and AMR codec usage with
12.2kbit/s transfer rate in HSPA, HSPA can serve up to 7 times more subscribers per
MHz compared to GSM. When compared to WCDMA, HSPA can serve almost 2 times
more subscribers per MHz. Apparently, CSPs can utilize the available radio resources
much better with using HSPA technology.
The MSS System also provides support for Nokia Siemens Networks Internet HSPA (IHSPA) architecture. In this architecture, voice services use direct connections between
I-HSPA base transceiver stations (I-BTSs) and MSSs. This allows removing RNCs from
the UTRAN subsystem, leading to a flat network architecture.
With the latest enhancements, the MSS System supports LTE access networks. Full
support for CS Fallback functionality is available in the MSS, and the NVS can provide
VoIP services for subscribers attached to an LTE system.
All these facts result in significant capital and operating expenditure savings for CSPs.
Support for multitude of radio access technologies in the Nokia Siemens Networks MSS
System secures investment in MSSs and MGWs, and ensures re-usability of the
existing platforms.
With the MSS System, operators can use a common packet switched transport network
for both fixed and mobile voice traffic on access and trunk interfaces. The MSS System
supports both TDM and IP-based A interface, as well as ATM and IP-based Iu-CS interface on radio access side. On the core network interfaces, it supports IP, TDM, and ATM
based transport for control and user plane traffic. The same MSS network element can
simultaneously function as mobile softswitch, MGCF, and NVS. The same MGW can
offer CS and IM user plane gateway roles. The available capacity of the MSS System is
shared dynamically among these roles on demand, enabling stepwise introduction of
new interfaces, services, and functions.
1.2
MSS product configurations

The original role of the MSC Server was to perform call control, messaging, and mobility
control functionalities of a mobile switching center in a 3GPP Bearer Independent Circuit
Switched Core Network architecture. Nokia Siemens Networks MSC Server has
evolved to a multi-purpose mobile and VoIP softswitch, which provides rich communication capabilities and registrar function while meeting the requirements of the latest
releases of 3GPP standards.
g
1.2.1
All the MSS functions and interfaces listed below can co-exist and operate in the same
physical network element simultaneously.
Nokia Siemens Networks MSC Server

Nokia Siemens Networks MSC Server implements the functionality of the 3GPP standardized MSC Server, Gateway MSC Server, and Media Gateway Control Function
(MGCF).
The MSS offers interworking among various user-network and network-network interfaces, as illustrated in Figure 3 Positioning the MSS in mobile networks below.
12
Id:0900d805808e1867
DN00292692
Issue 8-0-1
MSC Server overview
Femto
Gateway
LIMS
One-NDS
iGLMC SADM
NPS
NetAct
DX HLR
(FE)
CMD
NT-HLR
(FE)
I-BTS
Charge@once
EIR
SAAM
DX MSC
hiS 700
MSS
MSS
hiE
9200
SMSC
Traffica
hiQ
4200/4300
NEMU
Nelmon
DNS
RNC
MGW
TDM/ATM/IP
MGW
hiQ
1200/1600/
1800
BSC
DTG3000
CDS
PSTN
Figure 3
1.2.2
CISCO 7609(S) Juniper

CISCO 3750-E EX4200
CombiSGSN
Positioning the MSS in mobile networks
Nokia Siemens Networks Mobile VoIP Server (NVS)

The Nokia Siemens Networks Mobile VoIP Server (NVS) provides VoIP services to subscribers, for example:
supplementary services
network services
regulatory services
The NVS is based on the MSS software and hardware platform; thus it can be co-located
with an MSS in the same physical network node, and it can also provide the same
services as the MSS. The NVS is available as either a standalone VoIP server or as a
Telecommunications Application Server for the IMS. Figure 4 Positioning the MSS/NVS
in a VoIP architecture below illustrates a possible VoIP network architecture with NVS.
DN00292692
Issue 8-0-1
Id:0900d805808e1867
13
MSC Server overview
One-NDS
NPS
CMD
SADM
DX HLR
(FE)
Colibria
Presence Server
NT-HLR
(FE)
EIR
Charge@once
NetAct
Surpass hiQ
4200/4300
DX MSC
MSS
Multi
Access
Mereon
Media Server
6000
NVS
CFX-5000 BC/
PCS-5000
CFX-5000
ACME BG4250
MGW
TDM/ATM/IP
NEMU
NEMU
CISCO 7609(S) Juniper

CISCO 3750-E EX4200
Figure 4
1.2.3
LIMS
MGW
Surpass hiE
9200
Surpass hiG
1200/1600
/1800
DTG3000
Positioning the MSS/NVS in a VoIP architecture
Interconnect Border Control Functionality (I-BCF)

Parallel with the growing use of IP-based transmission both on control and user planes
in CSP networks, the number of IP-based interconnections increases in the home PLMN
and towards other networks. Session Initiation Protocol (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 MSS to be connected to many
different foreign IP networks that have various requirements for
14
flexible screening
traffic separation
security
Quality of Service (QoS)
Id:0900d805808e1867
DN00292692
Issue 8-0-1
MSC Server overview
Traditionally, Session Border Controllers (SBCs) have been used to provide these services. However, SBCs require extra investment from operators, including purchase of
hardware and software; and as extra network elements, SBCs also mean new operating
cost items.
To relieve operators of this expenditure, Nokia Siemens Networks MSS System can be
upgraded to serve as Interconnect Border Control Function (I-BCF) with MSS and Interconnect Border Gateway Function (I-BGF) with MGW.
The MSS/NVS acting as I-BCF controls network-network interface (NNI) interworking.
The I-BCF provides the following functionalities:
Application Layer Gateway (ALG), without firewall capabilities

SIP topology hiding with native B2B User Agent
flexible VLAN configuration
Service Level Agreement (SLA) monitoring
Implementing I-BCF in MSS/NVS provides reductions in capital and operating expenditure for operators, as it eliminates the need for separate SBCs. Operators can also
manage their own IP networks, including connections to external networks, more effectively. Figure 5 I-BCF in the MSS shows a basic architecture with I-BCF and I-BGF functionalities in MSS System elements.
Figure 5
I-BCF in the MSS
For more information on I-BCF in the MSS, see Feature 1903: MSC Server - IP Realm,
Feature Description.
DN00292692
Issue 8-0-1
Id:0900d805808e1867
15
MSC Server functionalities
2 MSC Server functionalities

The MSC Server (MSS) has a large set of functionalities which can be used in different
domains like GERAN, UTRAN, and E-UTRAN access networks, and in mobile and VoIP
service domains.
2.1
Subscriber data management in the MSC Server

Subscriber data is stored and managed by a Visitor Location Register (VLR) in an MSS.
Subscriber data is retrieved from the HLR over the 3GPP standard MAP interface with
standard procedures when a CS or SIP subscriber registers to the MSS or NVS. The
VLR supports mobility management, authentication, and participates, for example, in
the following call and non-call related events:
User Equipment (UE) originating and terminating calls

outgoing call barring
supplementary services (for example, call forwarding and call waiting)
mobile-originated or terminated SMS (SMS-MO or SMS-MT)
supplementary service (SS) management
CS Fallback
Mobility management functions supported by the VLR include location registration and
the management of Temporary Mobile Subscriber Identity (TMSI) and International
Mobile Subscriber Identity (IMSI).
The VLR requests authentication vectors from the Authentication Centre (AuC) over the
standard MAP-F interface, stores the received vectors, and executes the authentication
procedure. The VLR is also involved in other security functions, such as TMSI reallocation, starting of ciphering, IMEI checking, and tracing.
VoIP subscription related data, like uniform resource identifier (URI) and password for
HTTP Digest authentication, is stored in the Serving Profile Database (SPD) in the NVS.
VLR and SPD records are linked together for a subscriber, that is, SIP subscription
related data means additional information on top of the standard mobile subscription.
This allows introducing VoIP as a new service for mobile subscribers and provides the
same standard and operator specific services for both mobile and VoIP subscribers.
SIP subscriber data is downloaded from a dedicated database. The database can be
installed on a standalone network element exclusively integrated for this purpose. The
NVS can retrieve SIP subscriber data with Lightweight Directory Access Protocol
(LDAP) from the register. It means that the NVS requires an LDAP-based interface to
the database, and that data is stored in the format in accordance with the Nokia Siemens
Networks specific LDAP schema. Usage of the database is optional.
The MSS offers a possibility of sending subscriber data to an external network element
for further processing. This function is called VLR Data Feed, and it enables an operator
to provide more sophisticated services when the information is delivered, for example,
to the Gateway Mobile Location Center (GMLC) or Terminal Management Server.
2.2
Control functions in the MSS

In the MSS System, control and user planes are separated. Figure 6 Control entities in
MSS System shows the logical relationships between call control, user plane control,
and MGW control functions.
16
Id:0900d80580811cb8
DN00292692
Issue 8-0-1
Figure 6
Control entities in MSS System
Call control
Call control can be defined, in short, as an interaction between the parties of a call for
setting up and maintaining the connection. The primary aim of call control is the supervision of control plane routing. Control plane routing is a process executed during the
set-up phase of a call, and specifies the destination of the call. Control plane routing also
determines various call handling and call control protocol related parameters and
actions. Call control protocols can be, for example:
SIP
BICC
Integrated Services Digital User Part (ISUP)
Base Station System Application Part (BSSAP)
Radio Access Network Application Part (RANAP)
Call control starts connection set-up, handles calls in progress, and clears procedures.
Tasks related to ongoing calls include functionalities such as paging, handovers, supplementary services, and call re-establishment. Call control is responsible for a call all
through its duration. Call control has interfaces to O&M applications for traffic measurement, traffic observation, and charging purposes.
The MSS provides routing and switching analyses capability to increase efficiency and
flexibility. These analyses can be configured by operator, and they enable call and
routing control, and call differentiation based on a wide range of parameters. This flexibility enables seamless service integration of MSS into existing CSP networks. Control
plane routing also provides input parameters to user plane control, to enable differentiation in the user plane handling based on the control plane parameters and results.
Call control in the MSS is access agnostic, that is, the signaling interfaces and call
control logic are implemented as separate software entities, and they are connected to
DN00292692
Issue 8-0-1
Id:0900d80580811cb8
17
each other through a well defined internal interface. Therefore, call control, integrated
with IN Service Switching Point (SSP) functions, serves as a common routing, service
execution, and charging control functionality. Call control can be influenced by the
operator through various flexible analyses.
For more information on control functions in the MSS, see the following documents:
Basic Routing Functions, Functional Description

Control Plane Routing, Functional Description
Routing and Analyses, Operating Instructions
User plane control

User plane control in the MSS is responsible for:
selecting the MGWs to be used in the call

selecting the bearer characteristics (IP, ATM, TDM) for the user plane
creating user plane legs between different MGWs controlled by the same MSS
codec selection
User plane control has access to a topology database in the MSS, which database
contains the full network topology of MGWs controlled by the MSS and it is used for
creating connections within one topology.
In addition to knowing the topology of the individual network, user plane control knows
the User Plane Destinations (UPD) towards other network elements. For example, in
Figure 6 Control entities in MSS System, MSS1 knows in which of its own gateways are
the user plane connections controlled by MSS2.
User plane control applies user plane analysis in addition to topology information. This
analysis enables the operator to control, for example, the following characteristics:
bearer type
(if the network element should act as a call mediation node)
user plane destinations for originating and terminating sides
bearer setup mechanism
User plane analysis makes use of parameters such as:
call origin and destination

preceding and succeeding node related parameters
transmission medium requirements
call type
control plane analysis result parameters
For more information on user plane control, see User Plane Routing, Functional
Description and User Plane Routing, Operating Instructions.
Multimedia Gateway control
The MSS controls the MGWs using the H.248/MEGACO device control protocol. With
using H.248, the MSS can direct an MGW to perform various actions, for example:
18
reserve resources
provide tones
perform echo cancelling
give announcements
connect conferences
Id:0900d80580811cb8
DN00292692
Issue 8-0-1
handle call interception

control voice transcoding
handle handover-related connection topologies
During its start-up, the MGW performs registration and audit procedures and sends the
necessary configuration and status information about the user plane processing
resources to the MSS. The MSS uses a MGW database to store MGW-related information.
The MGW offers the following connections:
IP and TDM connections towards GERAN

IP and ATM-based connections towards UTRAN
IP, ATM, and TDM based connections towards backbone
The MSS can control a maximum of 100 MGWs. These MGWs can be physical or virtual
MGWs. One physical MGW can be divided into several virtual MGWs.
2.3
Mobility management in the MSS

Mobility management in the MSS takes care of the mobility of subscribers and participates in CS Fallback procedures. Mobility management handles transactions such as:
2.4
IMEI checking
2G/3G authentication and key agreement
IMSI attach and detach procedures
These procedures indicate whether the mobile station is
active and ready to receive a call or SMS, or
inactive when a call and SMS delivery attempt should not be made.
roaming and handover
normal or periodical location update
call re-establishment when radio connection is lost for a short period of time
Roaming and handover in the MSS

Nokia Siemens Networks' solution offers complete roaming and handover capability
between 2G and 3G networks. Operators can build a 3G radio coverage on top of an
existing 2G radio coverage. Therefore service continuity is ensured. Subscribers use 3G
services when they are under 3G coverage. When they move from 3G to 2G coverage,
the system performs a handover, and the services supported by the GSM radio access
network are available to them.
A handover maintains a call connection to a mobile even when the mobile phone moves
across cell boundaries. TheMSS supports the following handover scenarios:
intra-PLMN handover where a handover takes place within the operator's network
inter-PLMN handover where the mobile moves between operator boundaries
intra-system handover that takes place inside the 2G or the 3G system
inter-system handover that takes place between the 2G and the 3G system
This means that a handover is possible even in a case where the subscriber moves from
3G coverage of one operator to 2G coverage of another.
When the NVS plays TAS role in an IMS network, it supports IMS based Voice Call Continuity between 3GPP CS and non-3GPP PS access domains.
DN00292692
Issue 8-0-1
Id:0900d80580811cb8
19
Single Radio Voice Call Continuity (SRVCC) functionality is planned to be implemented

in the MSS/NVS to ensure seamless handover of calls between LTE and 2G/3G radio
access technologies. The implementation timeframe is synchronized with the expected
availability of terminals with LTE and 2G/3G access capabilities.
2.5
Intelligent Network functionalities in the MSS

For operation in the IN environment, the MSS incorporates the Service Switching Point
(SSP) function. The openness of the IN concept is ensured by implementing the SSP Service Control Point (SCP) interface using guidelines stated in Core INAP and CAMEL
standards. The use of ETSI-defined Basic Call State Models provides operators with an
efficient way of offering IN services for call-associated transactions.
The IN concept is also applied to the non-call related transactions. The State Models
defined for these transactions provide operation triggering points, where the control is
moved from the MSS to the SCP. Based on this, operator-specific services can be
executed by the SCP. These non-call related IN procedures are applied, for example, to:
location registration
mobility management procedures
supplementary service invocation
short message handling
The SSP implementation of the MSS supports the following protocols:
Nokia INAP CS-1 and CS-2

Siemens INAP 7m+
CAMEL phase 4 (and all previous CAMEL phases)
Due to the distributed HW and SW architecture of the MSS, the effect of IN services on
overall call handling capacity has been minimized. The MSS is able to provide 100% IN
service coverage for the target capacity of 3 500 000 Busy Hour Call Attempts (BHCA).
As NVS is implemented as a software function on top of the MSS platform, the very
same SSP functions are supported in the MSS and the NVS. It means that deployed
mobile IN services are available for VoIP subscribers without any need for business
logic or protocol modifications.
2.6
Charging and accounting in the MSS

Charging is a network function to create call information required for subscriber billing.
The MSS generates and stores call data, and makes it available for post-processing
computer systems.
Charging Data Records (CDRs) are generated for call cases an operator wishes to
charge for. The content of the different CDRs can be tailored to a particular operator's
need. The CDRs can be transferred to a Billing Center using an IP-based protocol, like
FTP, SFTP, and GTP; or they can be stored locally. The MSS is delivered with an integrated Blu-Ray media drive for backing up charging data locally.
Charging is also responsible for providing charging analysis for time charging information to determine parameters, for example, for accounting or the Advice of Charge (AoC)
supplementary service.
Accounting means collecting and analysing call data, to monitor the amount and
monetary value of call traffic. Typically, accounting data is the sum of all calls within a
20
Id:0900d80580811cb8
DN00292692
Issue 8-0-1
specific time period. Accounting data is used, for example, to verify the amount of call
traffic between different network operators.
Beside the above mentioned traditional circuit switched charging functions, the MSS in
NVS role provides offline charging over the Rf interface either in standalone VoIP Server
or TAS role in the IP Multimedia Subsystem (IMS). In the NVS, all other charging interfaces of the MSS are available.
2.7
SIP in the MSS

The Nokia Siemens Networks MSS has the longest history industry-wide history in supporting SIP for session and message management. For smooth introduction of SIPenabled services and for interconnecting SIP usage with legacy networks, the MSS
supports the following 3GPP SIP interfaces:
Mg/Mj, also known as MGCF interface

Nc
ISC
Gm/Mw
also known as SIP Access interface in Nokia Siemens Networks terminology
The support of Mg/Mj interfaces allows the MSS to act as an MGCF in the IMS architecture. Thus, together with the MGW they provide a control and user plane interworking
function between multimedia services domains and legacy CS networks.
The MSS also supports SIP-I protocol on the Nc interface, as specified by 3GPP.
With the Gm and Mw interface support, the NVS can take the role of a standalone VoIP
server and provide SIP registrar and back-to-back (B2B) User Agent functionalities.
Because of this, the NVS allows introducing VoIP services for mobile subscribers.
Through the ISC interface, the NVS can be integrated into the IMS as Telecommunications Application Server, and can provide 3GPP defined supplementary services and
IM-SSF functionality.
All these interfaces and functions are simultaneously supported by the same network
element, NVS, thus implementing a multi-purpose carrier-grade SIP server that can be
seamlessly integrated into next generation networks.
SIP requires the Domain Name System (DNS) to find out the IP address of the other
endpoint. The MSS first performs a number analysis, the result of which contains a
logical name representing the other endpoint of the signaling. The MSS then sends a
query to the DNS to find out the IP address that corresponds to the logical name. The
IP addresses that are retrieved from the DNS are stored in the cache of the MSS, so
there is no need to perform a DNS query for every call.
2.8
Statistics
Statistics provides operators with real-time data on the operation, capacity, and service
level of exchanges.
There are a large number of measurements, observations, and supervisions for monitoring exchange operation and call events. Operators can select and define the measurements, observations, and supervisions they want to use in the exchange.
The need to use statistical services varies depending on the operator and the exchange
involved. There are no common rules, which can uniformly be applied to all operators.
DN00292692
Issue 8-0-1
Id:0900d80580811cb8
21
There are, however, certain basic functions in the operation of the exchange, which
operators should measure and supervise. Certain statistical services can be listed and
they form the basis of the administration and observation of the exchange.
Measurements, observations, and supervisions are organized according to the following
division:
call traffic
IP traffic
signaling
mobility
security
load and availability
services
On the basis of observed and analyzed data, operators can receive information on the
following operational aspects of an exchange:
overloaded parts in the system

faulty parts in the system
traffic intensity
traffic categories
subscriber mobility
exchange status
capacity of the exchange for dimensioning purposes
The concepts of measurement, observation, and supervision in statistics can be

defined as follows:
22
Measurement
Measurement is a function where the system collects information about the traffic
and network events in the exchange, and then processes this information. The
system produces reports for the operator on the basis of the information. A measurement gives a result in an agreed unit, for example, in erlangs.
Observation
Observation is a function where the system either collects information about certain
events or directly produces information about single events in the system. It is
possible to set certain objects under observation, and to set conditions which must
be fulfilled before the system produces reports or alarms related to the events or
objects under observation.
Observations are typically used to locate the part of the network which causes problems, and to identify the nature of the problems that have occurred in the network.
Supervision
Supervision is a function where the system collects information about call traffic or
certain events in the exchange and then processes this information (same as the
concept of 'measurement'). In addition to this, it is possible to set conditions which
must be fulfilled before the system produces reports or alarms.
Supervisions are typically used as continuous functions to indicate if there are
problems in a telecommunication network. After getting indications of problems, it is
possible to identify the reason of the problem on a detailed level by using other functions of the network element.
Id:0900d80580811cb8
DN00292692
Issue 8-0-1
Statistical functionalities of the MSS can provide data in ASCII or XML format, depending on the operator's configuration. The reports can be transferred to a post-processing
system, for example, to Nokia Siemens Networks NetAct.
DN00292692
Issue 8-0-1
Id:0900d80580811cb8
23
MSC Server interfaces
3 MSC Server interfaces

Figure Positioning the MSS in mobile networks and Positioning the MSS/NVS in a VoIP
architecture in Section MSS product configurations illustrate the interfaces of the MSS
and NVS toward various network elements.
The physical interfaces of the MSS support Gigabit Ethernet or 10 Gigabit Ethernet,
depending on the application domain. The VLAN tagging functionality is supported on
all interfaces.
The MSS supports all-IP interfaces to every possible peer domains. As transport level
protocols, UDP, TCP, and SCTP are all supported. The applicability of the given transport layer protocol is up to the application it has to convey. For example, SIGTRAN
implementation for SS7 requires multihomed SCTP, while SIP can be transferred on any
of the protocols above.
H.248 signaling protocol is transferred over multihomed SCTP connections between the
MSS and the MGW.
For transporting SS7 signaling, MTP3 user adaptation layer (M3UA)-based SIGTRAN
protocol stack is used according to IETF guidelines. The M3UA protocol supports the
conveyance of all possible SS7 based protocols like BSSAP, RANAP, MAP, ISUP, TUP,
NUP, BICC, and so on. The MSS supports direct SIGTRAN signaling connections to
other peer nodes. Alternatively, the MGW can be used as Signaling Gateway (SGW). If
TDM or ATM-based signaling links are required by the peer network entity, the MGW
can act as an SGW between the MSS and the other network.
On PBX interfaces, the MSS supports IUA based SIGTRAN protocol stack. In this case,
the MGW can also act as an SGW, providing translation between 30B+D or 23B+D and
IUA protocol stacks.
On O&M and billing interfaces, the MSS supports Telnet, SSH, FTP, SFTP, and XML
over HTTP application level protocols.
To ensure secure connections on its interfaces, the MSS provides native support for
IPSec protocol suite with a rich set of symmetric ciphers, asymmetric IKE algorithms,
key lengths, and message digests.
24
Id:0900d80580811cb9
DN00292692
Issue 8-0-1
Services in MSC Server
4 Services in MSC Server

Beside voice calls, Nokia Siemens Networks MSC Server (MSS) offers an abundance
of services to operators, as discussed in this chapter.
4.1
Supplementary services
Nokia Siemens Networks is active in standardizing supplementary services (SS), and
the MSS implementation follows the latest standardized functionalities according to
customer needs.
The following supplementary services are supported in the MSS for mobile and VoIP
subscribers:
Call Deflection
Call Transfer
Both Non-attended and Attended Call Transfer procedures are supported for
VoIP subscribers
Missed Call Log (Nokia Siemens Networks proprietary)
Private Numbering Plan (Nokia Siemens Networks proprietary)
Closed User Group (both ETSI and enhanced Nokia Siemens Networks versions)
Call barring (both operator-determined and subscriber-determined)
Message Waiting
Line identification services
Calling Line Identity Presentation (CLIP)
Calling Line Identity Restriction (CLIR)
Connected Line Identity Presentation (COLP)
Connected Line Identity Restriction (COLR)
Call forwarding services
Call Forwarding Unconditional (CFU)
Call Forwarding on Mobile Subscriber Busy (CFB)
Call Forwarding Not Reachable (CFNRc)
Call Forwarding on No Reply (CFNRy)
Call waiting and call hold (with or without announcements)
For VoIP subscribers, call waiting is a terminal based service.
Multiparty
For VoIP subscribers, multiparty is a terminal based service.
Anonymous Call Rejection
Private Numbering Plan
The following services are supported only for mobile subscribers:
Calling Name Presentation

Advice Of Charging
Multicall (2 x 64 kbit/s)
enhanced Multi-Level Precedence and Pre-emption (eMLPP) service
Completion of Calls to Busy Subscriber (CCBS), even without HLR involvement
RAT Restriction
The following services are supported only for VoIP subscribers:
DN00292692
Issue 8-0-1
Presence
Id:0900d805808e1869
25
Malicious Call Identification
The MSS can to handle PLMN-specific SS codes when those are received from the HLR
over the MAP interface. With the flexible configuration options of the MSS, the operator
can trigger various services for subscribers based on received SS codes.
The MSS provides 3GPP 22.030 compliant Supplementary Service Control interface for
controlling mobile subscribers services.
VoIP subscribers can control and interrogate their supplementary service status in the
HLR and VLR via Facility Calls. The subscriber has to initiate a call by dialing MMI
control string in the format defined by 3GPP 22.030. Call related digit analyses have to
be set up in the Nokia Siemens Networks Mobile VoIP Server (NVS to recognize these
calls as facility calls. The result of these analyses identifies:
the exact supplementary service to be managed (CFU, CFB, CLIP, and so on)
the action to be performed (activation, deactivation, registration, interrogation, and
so on)
the in-band announcements to be given to the subscriber for the different outcomes
of the operation (success/failure)
The NVS maps the request to standard MAP operations towards the VLR or HLR. The
destination depends on the service and the action to be performed. Based on the
outcome of the operation (success/failure), the NVS plays the configured announcement to the subscriber.
The following supplementary services can be managed with a Facility Call:
call forwarding
call barring
line identification services
call waiting
Other supplementary services, for example, eMLPP, COLP, or COLR, cannot be

managed with Facility Calls currently.
The MSS and NVS will provide XCAP/Ut interface for subscriber service management
in the upcoming releases, as defined by 3GPP.
4.2
IN services
The MSS supports IN-SSP functionalities as described in Section Intelligent Network
functionality in the MSS. With IN capabilities, CSPs can provide SCP-controlled services
for call and non-call related items, for example:
Prepaid
Virtual Private Network (VPN)
Group Hunting
Home Zone Billing
Unstructured Supplementary Service Data (USSD) Callback
On top of supporting CAMEL and INAP standard procedures and functions, the MSS
can flexibly be configured to handle deviations from the standard functions and can be
tailored to given CSP needs.
The MSS includes internal GSM service control function (gsmSCF) to provide service
execution logic for services like:
26
Id:0900d805808e1869
DN00292692
Issue 8-0-1
4.3
Selective Ringback Tone (SRBT)

A-party SRBT (Ring to Me)
Group Hunting
Multimedia Ringback Tone (MRBT)
Collect Call
Missed Call Log
Messaging services
The MSS supports Short Message Service (SMS) as specified by 3GPP for CS mobile
domain.
The MSS can act as an mobile-originating (MO) or mobile-terminating (MT) visited MSC
(VMSC), SMS interworking MSC (SMS-IWMSC), and SMS gateway MSC (SMS
GMSC). It provides standard a MAP interface or Nokia Siemens Networks proprietary
SMRSE protocol based interface to the Short Message Service Center (SMSC). The
MSS can also act as an SMS Router, as defined by 3GPP.
Regarding LTE networks, the MSS provides SGs interface towards the Mobility Management Entity (MME) and related MO and MT-SM delivery procedures between LTE
devices and UEs roaming on E-UTRAN.
The NVS supports SMS MIME functionality, in accordance with 3GPP standards. The
NVS offers interworking between circuit switched SMS and SMS over IP. The NVS can
translate an MO/MT-SM to a SIP MESSAGE and vice versa. On SIP based interfaces,
the message is delivered in SIP MESSAGE payload. The message is either:
encoded as plain text with using GSM-7 or UCS2 Data Coding Scheme, or
it is encapsulated in the payload in binary format according to SMS MIME specifications.
Direct short message (SM) delivery allows that SMs are directly forwarded from the MOVMSC to the MT-VMSC without involving the SMSC. Since most of the SMs (roughly
60%) can be delivered at the first try (that is, direct delivery can be performed), this
solution provides a considerable decrease in the load of the SMSC and also the interface between the MSS and the SMSC. Direct SM delivery is also supported by the NVS
for SIP MESSAGE and for interworking cases.
Concatenated short messages, More-Messages-to-Send, and SMS queuing is supported on every interfaces. MO-SM load sharing is supported by a rotating method or by
SMSC link capacity. SMS barring analysis can be defined based on the SMSC or the Asubscribers address.
The MSS supports MAP-Gd interface, thus enabling SMS over GPRS delivery when it
acts as SMS-GMSC.
The MSS offers the possibility to route MO-SMs with providing a configurable short
message routing table, based on the following attributes:
Protocol Identifier
Service Application Prefix (SAP-B-number)
subscriber type
The MSS also provides mobile number portability solution for MO-SM charging.
For more information, see Feature 1641: B-IMSI Retrieval in MO Side for MNP, Feature
Description.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
27
4.4
Multimedia and circuit switched data call in the MSS

The MSS supports a wide variety of asynchronous and synchronous bearer and teleservices, like modem, fax, and 3G-H324M CS multimedia calls.
The MSS System supports T.38 as fax delivery mechanism on interfaces controlled by
SIP sessions, as specified by ITU-T. The MSS System provides native supports for
interworking between T.38 and T.30 fax delivery mechanisms, thus allowing end-to-end
fax service between CS mobile and VoIP service domains.
Nokia Siemens Networks Circuit Switched Data Server (CDS) is an integrated part of
the MSS System. It provides interworking function (IWF) for mobile originating and terminating circuit switched data calls.
In the MSS System, CDS is used to provide the IWF functionality for the MGW. It is logically part of the MGW user plane, but it is a separate network element that is connected
to the MGW using TDM lines.
Typical services requiring interworking functionality are as follows:
non-transparent asynchronous bearer services

transparent synchronous bearer services requiring rate adaptation
transparent facsimile group 3 teleservice
High Speed Circuit Switched Data (HSCSD) services
14.4 kbit/s data traffic channel
V.42bis data compression and compression on V.120
asymmetric data connection
H.324 multimedia modem calls
data call handovers between 3G and 2G
The CDS is not used with the following services:
32kbit/s transparent data service (rate adaptation in the MGW)

56/64 kbit/s transparent data services
3G H.324 M multimedia (video call)
The NVS supports the establishment of video sessions between VoIP subscribers.
Nokia Siemens Networks provides certified 3rd party video gateway in the MSS System
solution to enable video calls between CS and VoIP subscribers, thus enabling access
agnostic multimedia experience for end users.
The NVS also supports fax calls with image and T.38 media. As NVS is implemented as
an on top functionality of the MSS, it provides native support for interworking with CS
mobile side T.30 fax.
The CDS is not used in NVS video and T.38 sessions, as they are not circuit switched
services.
4.5
Unstructured Supplementary Service Data

Unstructured Supplementary Service Data (USSD) provides means to carry textual
information between a mobile subscriber and an application in the network. As with
SMS, USSD uses signaling channel as the bearer. However, instead of having the store
and forward functionality, it is session oriented. This means that when a user accesses
a service with USSD, a session is established and the radio connection stays open until
it is released by the user or an application, or it is timed out.
28
Id:0900d805808e1869
DN00292692
Issue 8-0-1
The MSS supports USSD-based management (activation, deactivation, and interrogation) of services like:
Call Completion to Busy Subscriber (CCBS)

Follow Me
Sequential Group Hunting
Parallel Group Hunting
The MSS also supports subsequent network-initiated USSD transactions.

The characters in a USSD string can be analyzed and take different action according to
the results of the analysis.
Mobile initiated USSD can be directly routed to the SCP (USSDC) via MAP protocol or
Siemens INAP.
4.6
Location services
The MSS supports location services (LCS) to locate a subscriber for GERAN and
UTRAN access networks, as specified by 3GPP. The MSS supports MO, MT and
Network Initiated (NI) Location Requests (LRs) to enable CSPs to provide subscriber
location information for various services like:
emergency calls (according to FCC E911 phase 2 and EU regulations)

surveillance of suspected criminals
home/office zone applications
network planning applications
electronic yellow pages
navigation
Location Services in the MSS are implemented according to radio access network
(RAN)-centric location services architecture. The MSS transfers positioning requests
towards the RAN, and retrieves location information towards the requesting entity, such
as the Gateway Mobile Location Centre (GMLC). The MSS can also identify events,
such as an emergency call set-up, which can trigger subscriber positioning.
Feature 1070: Support for Location Services (LCS) offers network operators a means
for providing value-added services to their subscribers.
4.7
Features
The MSS offers a wide and impressive variety of features and services to help CSPs
with providing innovative solutions to meet their customers' needs. On top of the wide
range of basic and supplementary services a mobile network provides, Nokia Siemens
Networks has also introduced value-added concepts and features which enhance
existing services and enables deploying new ones. The following sections give a brief
introduction to this rich set.
4.7.1
Features for cost optimization
4.7.1.1
Fax support in all-IP networks

Facsimile service plays an important role in CSPs portfolios. Thus it is important to
ensure seamless end user experience for subscribers even if a CSP uses IP backbone
DN00292692
Issue 8-0-1
Id:0900d805808e1869
29
in the core network. Nokia Siemens Networks MSS System supports fax and CS data
call detection, and T.38-based facsimile service as specified by ITU-T, to enable CSPs
to provide reliable facsimile services over IP.
When the MSS acts as interworking call routing function between legacy PSTN
networks and other network domains, like mobile networks, IMS or other PSTN networks, it is not always possible to determine from the call setup request whether the call
is a speech, fax, or modem call. Unless this differentiation is made, IP or ATM backbone
transmission resources cannot be optimized for speech calls without preventing fax and
modem data calls. If a compressed codec, for example, AMR-WB, was used in such
calls over IP or ATM backbone, fax and modem data calls would fail.
Feature 1630: Fax and CS Data Call Detection enables the MSS System to differentiate
between speech, fax, and modem data calls by monitoring the user plane and detecting
fax and modem negotiation related signals, as specified by the ITU-T. For calls either
coming from or going to the PSTN, Fax and CS Data Call Detection is an important
feature since IP or ATM backbone transmission resource usage can be optimized. This
means that compressed speech codecs can be selected during setup phase codec
negotiation, even when the exact type of the call (speech, fax, or modem) is unknown.
Without this feature, the MSS reserves user plane bearer with 64 Kbit/s bandwidth for
such calls. When a fax or modem signal is detected, the MSS performs codec modification from the compressed codec to a fax or modem capable codec to enable the fax or
modem data call.
With T.38 Fax over IP, it is possible to achieve significant savings, while being able to
create new sources of revenue. T.38 Fax over IP offers the following benefits:
enhanced quality and reliability for fax calls on IP based interfaces

savings in transmission capacity
better end user experience
savings in CAPEX
There is no need for 3rd party solutions for handling fax traffic over IP.
The T.38 protocol guarantees the reliability of facsimile transport in non-QoS-aware

environments such as IP networks, which are prone to jitter and Real-Time Transport
Protocol (RTP) packet loss.
Nokia Siemens Networks MSS System offers a native transcoding functionality between
T.30 and T.38 fax both on control and user plane levels. Because of this, the MSS
System ensures seamless interworking for fax calls where one side of the call is served
by legacy PSTN or CS mobile networks and the other side is an all-IP Next Generation
Network (NGN).
For more information, see Feature 1630: Fax and CS Data Call Detection in MSC Server
System, Feature Description.
4.7.1.2
Codec support in MSS

Nokia Siemens Networks MSS System supports a wide range of speech codecs.
Enhanced with the support of IP and ATM bearers on every interfaces, it enables transmission savings, as voice information can be conveyed in a compressed format over
various interfaces of the MSS System.
The following codecs are supported by Nokia Siemens Networks MSS System:
30
G.711 -law
Id:0900d805808e1869
DN00292692
Issue 8-0-1
G.711 A-law
GSM FR
GSM HR
GSM EFR
GSM FR AMR
GSM HR AMR
GSM FR AMR-WB
UMTS AMR
UMTS AMR 2
UMTS AMR-WB
G.723.1
G.723.1 ANN A
G.729 A
G.729 A ANN B
iLBC
As UMTS AMR-WB is a subset of G.722.2, Nokia Siemens Networks MSS System also
supports codec negotiation between network domains offering G.722.2 and UMTS-AMR
WB codecs.
Native support of UMTS AMR-WB and GSM FR AMR-WB codecs and the support of a
subset of possible G.722.2 configurations make Nokia Siemens Networks MSS System
ready for HD Voice services, irrespective of whether the participants of a call are served
by 2G, 3G, or fixed or mobile VoIP access.
For better interworking with the VoIP domain, Nokia Siemens Networks MSS System
has full support for G.723.1, G.729.A, and iLBC codecs.
For codecs that do not have native Discontinuous Transmission (DTX) capability, the
MSS provides Comfort Noise (CN) functionality. Currently, these codecs are iLBC and
G.711.
For dual-tone multifrequency (DTMF) transmission, the MSS System supports out-ofband, in-band, and telephone event based DTMF transfer:
In-band transfer is the classic method when DTMF characters are transferred as
in-band information, and the transferred signal is the mixture of two tones.
Out-of-band transfer can be used when BICC or SIP signaling is used on the
control plane for the call, and the in-band transmission of the DTMF signal over the
selected user plane codec would distort the signal, so it could not be recognized by
the receiving side.
For these cases, the MSS can transfer the received characters with BICC or SIP signaling procedures.
Telephone event is an alternative to SIP based out-of-band transmission, as specified by IETF. Support of telephone event can be negotiated with the well-known
SDP offer/answer procedure as a special RTP payload format and media type. If the
communicating peers support telephone event, DTMF characters are transferred as
a special RTP packet payload on the user plane.
The MSS System supports full interworking among the three DTMF transfer procedures
described above. That is, if a DTMF character has been received in-band, it can be forwarded with out-of-band or with telephone event method, and so on.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
31
Moreover, the support of Transcoder Free Operation (TrFO) in the MSS enables endto-end codec transparency with enhanced codec negotiation and codec modification
procedures. TrFO removes unnecessary voice sample transcodings, and enables
improved speech quality. Because of this, TrFO can function as a differentiator service
through increasing end-user satisfaction and saving transcoder resources in the core
network, thus lowering costs for CSPs.
Tandem Free Operation (TFO) can provide better speech quality with turning off
transcoders on interfaces where:
out-of-band codec negotiation is not possible due to the nature of the interface (for
example, ISUP or A over TDM), and
G.711 codec would be used from the MGW to the peer network element with
transcoders reserved in the MGW.
As for TFO, the transcoders in the MGW and the peer system can negotiate the common
codec in-band, which is then used to encode the speech samples in the slot reserved
for G.711 codec. On top of this standard functionality, Nokia Siemens Networks MSS
System provides payload optimization for TFO on IP or ATM backbone. This means that
only the compressed codec part of the G.711 slot is transferred over the IP/ATM backbone, thus decreasing the bandwidth need to a fourth of that needed for G.711 transmission.
For situations when using G.711 codec over an IP bearer cannot be avoided, the MSS
supports G.711 packetization periods of 5, 10, 20, and 30 ms. This means improved
interworking possibilities with network elements from different vendors. With the 30 ms
packetization period, tremendous bandwidth can be saved compared to the standard 5
ms period.
For more information on codec support and speech transmission, see Feature 1335:
Speech Transmission Optimization, Feature Description and Feature 1690: AMR-WB in
MSS, Feature Description.
4.7.1.3
A interface over IP
Nokia Siemens Networks MSS System supports A interface over IP (AoIP) towards the
BSS, compliant with 3GPP Rel-8 standards. Thus the MSS System proves its all-IP
capability by enabling smooth migration of a traditionally TDM-based interface to IP
technology.
The MSS System implements AoIP support with transcoder in MGW, as illustrated in
Figure 7 A interface over IP with TC in MGW. This solution decreases CSPs costs
through enabling the removal of additional transcoder boxes from the BSS. However,
the MSS System supports AoIP with transcoders still located in the BSS.
32
Id:0900d805808e1869
DN00292692
Issue 8-0-1
Figure 7
A interface over IP with TC in MGW
The A over IP feature has the following benefits:
4.7.1.4
IP technology, compared to Time Division Multiplexing (TDM), provides lower cost

networks due to easy configuration and maintenance.
In IP networks, bandwidth can be used efficiently by using compressed codecs and
Transcoder Free Operation (TrFO).
IP provides possibility for flexible user plane routing and network design, for
example, for Multipoint A.
IP provides possibility to use new features such as TrFO on the A interface to
achieve better speech quality and digital signal processor (DSP) capacity savings in
the MGW.
The same IP site and backbone can be used for different networks, like 2G, 3G, and
VoIP.
Removing 2G TCs from the BSS and using common TC resources in the core
network, that is, in the MGW reduce the number of NEs and overall need for TC
resources. Fewer TCs lead to significant cost savings as network architecture can
be simplified.
Speech quality can be optimized, and delay can be decreased, as TrFO is also supported for 2G calls.
CS over I-HSPA
Internet High-Speed Packet Access (I-HSPA) introduces a flat network architecture for
both RAN and packet core, as standardized by 3GPP in Release 7. By flattening the
architecture, I-HSPA removes the bottlenecks from the network, unleashing the whole
Air interface capability for growing packet-switched (PS) data traffic needs. Nokia
Siemens Networks is the only vendor at the moment offering fully flat 3GPP Rel-7 compliant architecture for I-HSPA.
Even though I-HSPA is a PS optimized solution, CSPs who have existing CS core
networks still want to utilize their investment for speech calls together with I-HSPA
DN00292692
Issue 8-0-1
Id:0900d805808e1869
33
access network, exploiting the spectral efficiency HSPA access can provide for CS
voice traffic.
In I-HSPA, I-BTSs are connected to the MSS System directly through standard Iu-CS
control and user plane interfaces, as shown in Figure 8 CS over I-HSPA. Nokia Siemens
Networks MSS System is able to handle up to 500 I-BTS connections in one MSS; therefore it can provide a cost efficient, flat network architecture for CS Voice traffic, too. The
support of CS over I-HSPA functionality can indirectly increase CSP incomes, as HSPA
access technology extends UE battery lifetime by more than 50%.
Figure 8
CS over I-HSPA
In near future, the MSS is going to support up to 4000 I-HSPA I-BTS connections, and
there are further plans to go even beyond that.
4.7.2
4.7.2.1
Value Added Services

MultiSIM
Mobile phone penetration keeps increasing continuously in the world. More and more
subscribers start using separate phones with different purposes, for example, one builtin car phone and another one kept in the pocket, or one for business usage and another
one for private purposes. A natural desire is that whichever phone is used by the subscriber, the same Mobile Subscriber International ISDN Number (MSISDN) is shown to
the opposite side as Calling Line Identity (CLI). Another use case can be to enable the
use of a common MSISDN for a small group of people, for example, for a family.
MultiSIM is a service that makes it possible to group several individual subscriptions
behind the same MSISDN.
The MultiSIM service comprises of the combination of features Same CLI for Multiple
Subscribers and Sequential and Parallel Alerting. This set of features enables the presentation of the same MSISDN to the outside world, while the members of the group can
be alerted sequentially or in parallel. Sequential alerting is applicable to voice and any
kind of data calls, while parallel alerting is possible for voice and video calls.
34
Id:0900d805808e1869
DN00292692
Issue 8-0-1
The MultiSIM feature can also provide the functionality to enable the same subscriber
to be reached in different access domains, for example, when a subscriber has both CS
mobile and VoIP subscriptions either on separate terminals or on the same multi-radio
capable terminal. MultiSIM enables smooth introduction of VOIP services while subscribers can be reached whatever access network they are is camped on.
The hunting group can be retrieved from the HLR if a Nokia Siemens Networks HLR is
in use, and the hunting logic can be executed by the internal IN service of MSS with
using the retrieved group information. Alternatively, the MSS can execute hunting,
acting as GSM service switching function (gsmSSF) based on instructions coming from
external gsmSCF over standard CAMEL or INAP-based interfaces.
Supplementary services can be synchronized among members, for example, execution
of call forwarding can be carried out on a group or on a member level, based on flexible
configuration options.
For more information on this topic, see Feature 1541: Same CLI for Multiple Subscribers, Feature Description and Feature 1545 and 1576: Sequential and Parallel Alerting,
4.7.2.2
One Number Service

The great success of MultiSIM service generated more requirements to improve this
functionality. One Number Service implements the following enhancements:
Hunting group information can be retrieved from the LDAP database, so the functionality does not require a Nokia Siemens Networks HLR in the CSP network.
Therefore, the MultiSIM repository becomes vendor independent, and introduction
of the service is faster and safe as subscription data does not have to be migrated
form a 3rd party HLR to a Nokia Siemens Networks HLR.
The possible number of members is increased from 5 to 15.
Enhanced support for multi-radio terminal users, for example, when the service is
used to reach the same subscriber camping on different access networks (for
example, 2G, 3G, and WLAN).
Enhanced support of embedding hunting groups into a hunting group. That is, a
member of a hunting group can be a hunting group, too.
For more information on this topic, see Feature 1907: One Number Service, Feature
Description.
4.7.2.3
SMS over LTE

As part of its evolution, the MSS can be integrated into Evolved Packet System (EPS)
through the SMS over LTE functionality. The MSS provides 3GPP-standard SGs interface towards the MME and all the procedures related to SMS handling over SGs interface, as shown in Figure 9 SMS over LTE. Therefore, SMS, as one of the most profitable
services, can be offered for LTE subscribers with reusing the existing SMS routing infrastructure, even if only data-centric LTE subscriptions are available in the first phase of
LTE deployments.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
35
Figure 9
SMS over LTE
Later, the functionality can be seamlessly applied for voice centric LTE subscribers as
well, because the SGs interface implementation in MSS disregards the subscriber type,
that is, if they are data centric or voice centric subscribers. The SM content is also transparent; For example, an SM with Over-The-Air configuration purpose and another,
generic SM are handled and delivered identically.
The MSS can handle the following SGs interface related procedures:
Location Update
Paging for MT-SM
Delivery of MO and MT-SM
Alert
Detach
MM Information Request
Reset
SGs interface implementation of the MSS is evolving to provide the full 3GPP standardized capability set, thus providing a complete CS Fallback functionality for calls, USSD
and Location Services.
4.7.2.4
Circuit Switched Fallback (CSFB)

3GPP defines the concept of Circuit Switched (CS) Fallback for the Evolved Packet
System (EPS). When voice, location, or USSD services (other than SMS) are initiated
or terminated to or from a UE attached to EPS, the network forces the UE to fall back to
the GERAN or UTRAN network where the CS procedures are carried out.
The CS Fallback functionality provides a seamless voice service for end users and
enables the reuse of existing CS core networks for voice services when the subscriber
is attached to E-UTRAN or EPS. This means that the LTE services can be introduced
to CSP networks with also providing CS voice services to LTE subscribers.
This feature provides the following benefits:
36
Id:0900d805808e1869
DN00292692
Issue 8-0-1
Seamless CS voice services

Reusing deployed circuit switched domain for LTE voice, location and USSD
services
Reusing MSS functionalities and investments
Reusing deployed, value added service and charging infrastructure
Parallel use with, or prior to the introduction of VoLTE VoIP Solution
The CS Fallback feature in MSS utilizes the same SGs interface that is used for the SMS
over LTE functionality.
For more information on the feature, see Feature 1914: CS Fallback in EPS for MSC
Server, Feature Description.
4.7.2.5
Voice over LTE (VoLTE)

Evolved Packet System has been standardized by 3GPP in Rel-8 within the LTE project
in order to define the next generation mobile packet switched data access network architecture. 3GPP selected new radio access technologies to improve spectral efficiency
and end user data rates for providing mobile data access service for subscribers that is
competitive with fixed rivals. 3GPP also targeted ensuring sustainable growth with
decreasing mobile CSPs costs even if the number of mobile data users and data service
volume grows continuously.
EPS is defined by 3GPP to be as service independent as possible. Consequently, it
does not provide native support for CS voice services, unlike HSPA. 3GPP defined VoIP
as voice solution when subscriber is camped on E-UTRAN. VoIP service is to be
provided by VoIP servers in the Services Domain. Nokia Siemens Networks Mobile
VoIP Server (NVS) can act as application server in this architecture and provide voice
and messaging services for LTE subscribers.
Nokia Siemens Networks Mobile VoIP Server (NVS) is a software functionality on top of
the MSS. VoIP can be enabled as additional service for existing mobile subscribers, or
can be defined as exclusive voice service for new and existing subscribers. The
resources of the MSS are dynamically shared among mobile and VoIP subscribers, calls
and messages. Moreover, the same services are seamlessly executed on an access
agnostic way. All these factors ensures that the introduction of VoIP services can
happen in an evolutionary way on a per subscriber basis, while end users have the same
experience with services.
To connect VoIP enabled LTE terminals in 3GPP and One Voice compliant manner to
the MSS System, a separate Proxy Call State Control Function (P-CSCF) entity is
needed between the EPS and the MSS System, as shown by Figure 10 A voice over
LTE architecture. This P-CSCF functionality is available in Nokia Siemens Networks
CFX-5000 Border Controller (BC), part of Nokia Siemens Networks IMS solution, in a
specific configuration suited for this purpose.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
37
Figure 10
A voice over LTE architecture
For the NVS, EPS is just another access network. This means that all functions and
features available for subscribers camping on, for example, 2G, 3G, GPRS, HSPA and
xDSL access networks can be executed when a subscriber uses EPS for accessing the
services domain.
4.7.2.6
SMS Router
When an MT-SM is delivered to an outbound roamer, the route of the SM may bypass
the home network of the target subscriber. In such cases, the home network operator of
the outbound subscriber loses control over these SMs. Moreover, the originating public
land mobile network (PLMN) may not have interworking agreement with the target
PLMN, in which case the delivery of the SM fails.
The MSS implements 3GPP-compliant SMS Router functionality to enable operators to
route MT-SMs to the HPLMN by force before delivering them to subscribers, as shown
in Figure 11 SMS Router. In addition to the MSS, Nokia Siemens Networks HLR
products also support this functionality, so Nokia Siemens Networks can provide a
complete solution with its product portfolio.
38
Id:0900d805808e1869
DN00292692
Issue 8-0-1
Figure 11
SMS Router
Successful SM delivery even if the target subscriber is roaming in a visited PLMN

which does not have SMS interworking agreement with the originating subscriber's
home PLMN
Successful SM delivery even in cases when Mobile Number Portability is used with
no SMS interworking agreement between the subscribed network of target subscriber and the home PLMN of originating subscriber
Enhanced user privacy and security (by hiding actual locations and IMSI of target
subscribers from the SMS-GMSC)
New and unique subscriber related number
The so-called correlation ID and the address of the SMS Router is sent to the SMSGMSC instead of the real IMSI number and VMSC/SGSN addresses after HLR
inquiry. If one of them is incorrect in the MT-SM which comes from the SMS-GMSC,
SMS Router handles this MT-SM as spam SM and blocks it.
Solution to fraud scenario when short messages are delivered from "fake" originating subscriber, and thus billed by a wrong PLMN
Possibility to control receiving of unsolicited short messages ("spam") when subscriber roams outside of their home PLMN.
Providing lawful interception when subscriber roams outside of her home PLMN.
Override the route indication of the SMS-GMSC (which can be MSC/SGSN) in the
case of an MT-SM
That is, not the foreign PLMN determines how the home PLMN us used.
For more information on this topic, see Feature 1906: SMS Router Functionality in MSS,
DN00292692
Issue 8-0-1
Id:0900d805808e1869
39
4.7.2.7
SM traffic filtering and blocking

Currently, mobile messaging abuse is growing, and the industry needs to have efficient
ways to tackle it in real time. There are CSP networks where 40% of the SM traffic is
caused by mobile viruses.
This feature provides a solution for SM traffic blocking, as it protects the core network
from fraud SMs coming from mobile subscribers. The MSS can analyze MO-SM traffic
at an early stage and block it. Therefore, unwanted core network traffic decreases.
The feature provides two analyses to identify fraud SMs:
Black list
The MSS analyzes the B-number (MO-SM), or the A-number (MT-SM).
Content filter
The MSS analyzes the user data of the MO-SM and the MT-SM.
For more information on this topic, see Feature 1927: SM Traffic Filtering and Blocking,
4.7.2.8
Presence and Message Waiting Indicator

The Nokia Siemens Networks Mobile VoIP Server (NVS) can act as an authentication
and authorization proxy for Presence and Message Waiting Indicator services of subscribers. It can authenticate and relay SUBSCRIBE, PUBLISH an NOTIFY requests
between the subscriber and the Presence Server or Voice Mail Server. Message
Waiting Indicator is supported both with solicited and non-solicited modes.
For more information on this topic, see Feature 1883: Presence and Message Summary
Services in NVS, Feature Description.
4.7.2.9
Calling Name Presentation (CNAP)

Calling Name Presentation (CNAP) is a supplementary service that provides the ability
to indicate the name information of the calling party to the called party at call set-up time
for incoming calls. However, 3GPP standardized this service as a called party service.
The MSS supports two solutions for CNAP services from subscription point of view.
In "A-party CNAP", which is also known as Calling Name Provision (CNPRO), the subscription is connected to the calling party, so name query is made in the originating MSS.
For mobile subscribers, the service can be activated by a PLMN-specific supplementary
service code. It it is also possible to trigger name query for any incoming call, such as
call from a public switched telephone network (PSTN) or private branch exchange
(PBX). CNAP name query can be performed from two different kinds of name database:
Internal database
The MSS includes an internal CNAP database, which has limited capacity, but it is
very useful to provide service without cost, installation, or maintenance of an
external DB element. This solution is typically useful to provide services, for
example, for banks, insurance, and telemarketing companies.
External database
The MSS can perform a CNAP name query through Lightweight Directory Access
Protocol (LDAP) from Nokia Siemens Networks Profile Server (NPS), which is a
subscriber data management and profile resolution system.
"B-party CNAP" is the 3GPP standardized service. As the service is connected to the
called party, a name query is performed from the terminated MSS based on a standard-
40
Id:0900d805808e1869
DN00292692
Issue 8-0-1
ized CNAP service code, or based on a PLMN specific supplementary service code.
This CNAP solution also supports the name query from an external NPS through LDAP.
As a third option, the MSS also supports query through ANSI specific Transaction Capabilities Application Part (TCAP) protocol.
For more information on this topic, see Feature 1603: Calling Name Presentation Alternatives, Feature Description.
4.7.2.10
SIP IP PBX
Enterprises with Internet Protocol Private Branch Exchange (IP PBX) solution, providing
telecommunication and supplementary services, will be crucial part of Next Generation
Networks (NGN) and form part of the all-IP evolution.
IP PBX is a business telephone system designed to deliver voice or video over a data
network and interoperate with PSTNs.
Nokia Siemens Networks MSS System already supports the interoperability of telecom
services between the Internet Protocol Multimedia Networks (IM CN) and the Circuit
Switched networks. Phase 1 of the IP PBX solution extends the services and functionalities previously available for PBXs to IP PBXs, to improve both subscriber experience
and the performance of operators' networks.
The MSS System provides a direct interface to IP PBXs, enabling direct peering
between existing CSP domains and SIP-enabled enterprise networks by using the basic
call-related capabilities of the MSS System.
With this feature, the MSS System provides support for IP PBX UNI call procedures and
supplementary functions like:
Dedicated number and charging analysis

Calling Line Identity Screening
Number Normalization
UNI CLIR Handling on terminating calls
Ring Back Tone Connection and Early Media
SIP "anonymous" mapping with ISUP presentation indicator
Call Hold and Retrieval
The IP PBX interface in the MSS can be virtualized by defining multiple access realms
for each IP PBX.
Using one single MSS for IP PBX users in different countries, bringing significant
OPEX savings.
Connecting several IP PBXs to the core network
Call control layer providing PBX-like connectivity, similar to ISDN-based DSS1 connections
Cost effectiveness and scalability, allowing operators to use the same MSS for both
mobile and fixed networks with IP connectivity
For more information on this topic, see Feature 1972: SIP IP PBX Support, Feature
Description.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
41
4.7.2.11
MultiSIM Short Message

The MultiSIM SM feature gives the possibility of delivering a SM or a SIP MESSAGE to
every group member of a ringing group depending on the used access type of the
member. Parallel and sequential hunting are both supported. When sequential hunting
is applied, group members are tried one at a time until the first successful delivery. For
parallel hunting, SMs or SIP MESSAGEs are sent to all group members at the same
time, and if at least one of the deliveries is successful, the delivery is considered as successful.
Group information can be stored either in the HLR or the LDAP database. Common
SMS Application is used if the SMS and NVS messaging solutions support both repository types. The NVS messaging solution is supported in both NVS standalone (SA) and
application server (AS) roles.
For more information on this topic, see Feature 1935: MultiSIM Enhancement for SMS
and NVS Messaging, Feature Description.
4.7.3
4.7.3.1
Operability
M3UA load balancer in the MSS
The MSS supports load balancer (LB) functionality for M3UA-based SIGTRAN traffic.
For M3UA based signaling, the dedicated M3UA LB signaling units serve as load
balancer units. Nokia Siemens Networks plans to support other interfaces such as SGs,
Diameter, and LDAP with load balancer architecture in the future.
For more information on this topic, see Feature 1949: M3UA Load Balancer, Feature
Description.
4.7.3.2
IP Realm
The integration of MSS into all-IP networks requires that an MSS is connected to many
different uncontrolled IP networks with various requirements for flexible screening, traffic
separation, security, and QoS.
Traditionally, Session Border Controllers (SBCs) have been used to provide these services. However, SBCs require extra investment from operators, including purchase of
hardware and software.
To save operators from such costs, Nokia Siemens Networks implements the IP Realm
functionality in the MSS System. With a single software upgrade, Nokia Siemens
Networks MSS provides Interconnect Border Control Function (I-BCF), and the MGW
can Interconnect Border Gateway Function (I-BGF).
An IP Realm is a logical identifier for one separate network segment of an IP network.
Traffic can be passed back and forth between IP realms and the home network through
multiple listening points. These listening points represent a communication route
through which communication between the MSS/NVS and IP realms takes place. With
the IP Realm feature, the MSS/NVS controls interworking between IP realms at SIP signaling level on Network-Network Interface (NNI).
IP Realms supports:
42
integrated SIP signaling ALG functionality between realms

Network Address Translation (NAT)
Id:0900d805808e1869
DN00292692
Issue 8-0-1
SIP topology hiding through Back-to-Back User Agents (B2BUA)

flexible VLAN configuration for each realm
By using the IP Realm feature, operators can remove 3 rd party SBC products from the
Network-Network Interface and save significant costs.
For more information on this topic, see Feature 1903: MSC Server - IP Realm, Feature
Description.
4.7.3.3
SIM-based authentication in the NVS

Subscribers can access mobile broadband packet-switched networks, like GPRS,
HSPA, and EPS, using PC Data cards or USB dongles equipped with a SIM reader, as
well as with their mobile phones. A VoIP application can register to a VoIP server over
this access interface. This requires re-using SIM-based authentication on service level.
It also means that a SIM/USIM is re-used as the binding element between subscribers
and operators. In this way, operators can convince end-users that provided VoIP service
is on the same level as CS mobile voice when it comes to trustworthiness. Therefore,
operators can strongly argue against using 3rd party VoIP providers.
Nokia Siemens Networks Mobile VoIP Server (NVS), as a software functionality in the
MSS, can download authentication vectors from the Authentication Center (AuC) over
standard MAP interface. The NVS uses those vectors to authenticate the subscriber
with Digest AKAv1 or AKAv2 algorithms, as specified by the IETF. Both algorithms can
be applied for 2G or 3G SIM/USIM cards.
IMS AKA algorithm is also under development for upcoming releases.
For more information on this topic, see Feature 1863: SIM-based Authentication for NVS
Convergence, Feature Description.
4.7.3.4
Multipoint A/Iu-CS
The MSS supports intra-domain connection of Radio Access Network (RAN) nodes to
multiple Core Network (CN) nodes both on A and Iu interfaces, as specified by 3GPP.
This feature is called Multipoint A and Multipoint Iu, respectively, in the Nokia
Siemens Networks feature portfolio.
The multipoint concept introduces a so-called pool area, which corresponds to one or
more RAN service areas. A pool area can be controlled by multiple MSSs. Subscribers
and traffic are shared among core network elements.
Using multiple MSSs within pool areas enlarges the service area of each MSS. There
are practically no inter-MSS node location updates nor handovers as each UE is
handled by the same MSS while it stays in the pool area. This has the further benefit of
reducing traffic to the HLR.
With overlapping pool areas, the overall traffic can be divided into separate areas. For
example, each pool area might cover a separate residential area and all pool areas the
same city center. Therefore, existing core network capacity can be used more efficiently.
Core network capacity can also be upgraded more easily through simply adding new
MSSs to the pool area.
In addition, network level resiliency is improved with this feature, as another MSS can
be called upon to serve a subscriber if an MSS fails in a pool area.
DN00292692
Issue 8-0-1
Id:0900d805808e1869
43
In the original concept, RAN nodes provide Non-Access Stratum (NAS) Node Selection
Function (NNSF) to route the NAS requests to different MSSs. Nokia Siemens Networks
MSS System implements an additional approach where MGWs support NNSF, that is,
Multipoint functionality can be introduced in networks where RAN does not support Multipoint related tasks. Beside making the concept independent from RAN implementation,
it further simplifies the configuration and maintenance efforts of networks with Multipoint
features.
4.7.3.5
Remote and automated SW management

Software Manager in Nokia Siemens Networks NetAct is enhanced to support the integrated and automated run of a Change Delivery (CD) Remote Macro. As a result, the
content of a new CD can be automatically downloaded and installed to the MSS.
Operator interaction is needed only at critical points, for example, in the case of a restart
or in erroneous situations.
4.7.3.6
Real-time user plane monitoring

When Nokia Siemens Networks MSS System is integrated into all-IP networks, it is a
natural requirement that the operator has adequate information on network characteristics and quality of voice that is being transmitted.
Traffica, the advanced real-time control plane monitoring tool of Nokia Siemens
Networks MSS System, is enhanced with user plane monitoring capabilities for this
purpose. The MGW provides real-time user plane monitoring data to an external server
application, NELMON, which collects data from several MGWs and forwards them to
Traffica, as shown in Figure 12 Real-time user plane monitoring.
44
Id:0900d805808e1869
DN00292692
Issue 8-0-1
Figure 12
Real-time user plane monitoring
Real-time control plane and user plane information are terminated in the same analyzer
tool. With correlation information from MSS and MGW, control plane and user plane
traffic of the same call can be analyzed simultaneously.
This feature provides real-time visibility of MGW monitoring data. The MGW data in
Traffica includes, for example, the following information:
jitter information in IP terminations

out of order IP packets
active speech level information
noise level
speech activity factor
double talk, MOS simulation
MGW data can be post-processed in both NELMON and Traffica. As the data is
analyzed externally with NELMON, MGW capacity is saved for other purposes.
NELMON is connected to the MGW over TCP/IP.
User plane measurements stored to the NELMON database includes the following information:
DN00292692
Issue 8-0-1
quantile jitter information for IP terminations

inter arrival jitter/peak to peak jitter/wander
IP packet loss ratio/out of order IP packets
frame erasure ratio
saturation clipping
active speech level information
Id:0900d805808e1869
45
noise level information

speech activity factor
double talk
echo path delay/echo return loss
MOS, speech quality (simulation)
Data can be searched offline in the NELMON database in order to:
46
evaluate behavior of traffic in the MGW

troubleshoot a specific traffic direction
troubleshoot a single call or connection (for example, based on customer complaint)
Id:0900d805808e1869
DN00292692
Issue 8-0-1
MSC Server hardware architecture
5 MSC Server hardware architecture

All MSS products are based on DX 200 hardware platform which uses Intel Pentium processors.
The Integrated MSS is a feature in the DX MSC. Thus the hardware configuration is
similar to that of the DX MSC as well. This ensures an easy and cost-efficient upgrade
for the existing DX MSC elements to the Integrated MSS that can be upgraded to MSSu
that has no TDM connections. The standalone MSS is based on the DX 200 Server Platform.
The DX 200 Server Platform is a new hardware configuration optimized for call control.
It is a pure server configuration that uses double computer cartridges. This minimizes
floorspace requirement and maximizes performance. However, all plug-in units are the
same as in the DX MSC, so it also offers full synergy with other DX 200 elements.
Exact specifications for the interfaces between the modules make it possible to add new
functions without changing the system architecture and enable the system to remain upto-date throughout its long operational life.
The possibility to build different network elements which provide different functionalities
is a good example of the versatility of hardware architecture.
5.1
MSS architecture
The MSS is a compact standalone server product that offers processing power that is
needed when one server controls several MGWs.
The MSS does not have a Group Switch (GSW) for switching 64 kbit/s TDM channels.
An optional small Group Switch can be included in the configuration if required for TDMbased SS7 and PBX signaling.
Figure 13 Block diagram of MSS, NVS, and MSSu shows the hardware architecture of
the MSS, NVS, and MSSu; and how the units are backed up to ensure reliability.
DN00292692
Issue 8-0-1
Id:0900d805808f93bc
47
IP for
O&M
LAN
X.25
VDU and LPT
CLS
OMU
CMM
CHU
optional
E1 or T1
ET
GSW
CCSU
MESSAGE BUS
Ext. Sync.
BDCU
SWU
STU
*SU
SWU
IPDU
GPLU
CMU
VLRU
dn0247335
IP for Control LAN
Optional in MSS
(not in MSSu)
* SU BBSU, SIGU, or SCPU

Figure 13
Block diagram of MSS, NVS, and MSSu
Similarly to the MSS, the MSSu is also a compact standalone server product that offers
processing power that is needed when one server controls several MGWs.
The MSSu is always upgraded from the operator's current DX MSC. The MSSu is a pure
standalone server that does not have any TDM interfaces.
Figure 13 Block diagram of MSS, NVS, and MSSu shows the hardware architecture of
the MSSu.
5.2
Integrated MSS architecture

As a regular DX MSC can be upgraded to an Integrated MSS, the block diagram of the
Integrated MSS includes all the functional units that are available in the regular DX MSC.
48
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
The GSW is included here since this network element can also handle user and control
plane traffic on TDM lines.
Figure 14
5.3
Block diagram of Integrated MSS
Functional units in MSS

The concept of functional unit allows versatile configuration of the MSS. Regarding the
hardware, a functional unit is a set of plug-in units that are inserted into one cartridge.
As for software, a functional unit performs a set of operations that can be seen as an
entity in network element configuration. This allows for flexible hardware configuration
that ensures optimal use of floor space.
MSS functional units are briefly described in the following sections.
5.3.1
Charging Unit (CHU)

The Charging Unit collects and stores charging data records (CDRs). CDRs are created
in the CHU memory, and based on operators decision. They can be handled in two
basic ways:
DN00292692
Issue 8-0-1
they can be stored on a local, redundant hard disk drive (HDD) first and periodically
transferred to the Billing Center, or
they can be directly sent to the Billing Center when they are created.
Id:0900d805808f93bc
49
In the latter case, the local HDD can serve as fallback storage when the connection to
Billing Center fails. For charging data backup, integrated Blu-Ray devices are provided.
5.3.2
Central Memory and Marker (CMM)

The Central Memory and Marker serves as a centralized unit for providing functions in
routing and configuration management that cannot be distributed. CMM stores the configuration files. Configuration changes are first written to CMM files, and then they are
distributed, for example, to signaling units.
The CMM acts as a virtual Marker in hunting for TDM resources, which are physically in
the MGW. In the case of BICC management, virtual call instance codes (CICs) are used
in the CMM.
5.3.3
Cellular Management Unit (CMU)

The Cellular Management Unit is responsible for managing cellular network related
functionalities in the MSS; for example, maintaining the location areas, BSCs, RNCs,
cells, and service areas under the MSS. The CMU also keeps track of the transactions
of individual subscribers. Thus it plays a role in supplementary services where it is interesting whether the subscriber has already another ongoing transaction, for example, call
waiting, or CFB.
5.3.4
Signaling Unit
The various signaling units (CCSU, SIGU, PAU, SCPU, BSU) host signaling interfaces
for protocols like ISUP, TUP, NUP, SIP, RANAP, BSSAP, BICC, H.248, and so on. They
provide call control functionality, SMS handling, and Media Gateway control. Basically,
signaling units host the main business logic functionalities of the MSS.
5.3.5
IP Directory Unit (IPDU)

The IP Directory Unit serves as a load balancer for SIP and H.248 signaling in the MSS.
5.3.6
General Purpose Linux Unit (GPLU)

The General Purpose Linux Unit (GPLU) is necessary in Web Server Interface (WSI)
MSSs. The MSS provides a WSI towards the Secure Telecom Asset Exposure Layer
(STAE layer). This is an optional interface that requires a dedicated GPLU to run the
web server, so a single GPLU is needed to be installed in each network. This unit serves
the requests from the STAE layer and collects all necessary information from the core
network.
The other task of the GPLU unit is to serve the XML Configuration Acess Protocol
(XCAP) function through the Ut interface.
5.3.7
Operation and Maintenance Unit (OMU)

The OMU is the central O&M unit in the MSS. It stores the uploaded SW packages on
redundant local HDDs. It incorporates the alarm system of the MSS, which is responsible for collecting alarms from the distributed units and sending them to external O&M
systems. The OMU is the central unit of recovery subsystem that supervises the functional unit states in the MSS.
50
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
5.3.8
LAN Switching Unit (SWU)

LAN Switching Units maintains Base Interface (BI) and Fabric Interface (FI) connections
among CPU blades and shelves in the MSS. The Base Interface is mainly used for
internal messaging, for example, EMB traffic, alarms, and control messages, among
functional units. The Fabric Interface is mainly used for external control, O&M, and
billing interfaces.
5.3.9
Statistical Unit (STU)

The Statistical Unit collects performance and measurement data from the network. It
also takes care of lawful interception (LI) reporting and related IP connections.
5.3.10
Visitor Location Register Unit (VLRU)

The Visitor Location Register Unit is responsible for subscriber management in the
MSS. It includes the local VLR database and the business logic related to the management of subscriber data.
5.4
Redundancy principles
To ensure reliability, different back-up techniques are used in the MSS depending on
the particular element. Furthermore, each backed-up element receives their power
supply from separate DC/DC converters or from the power source of each card.
The following back-up techniques are used:
2N providing duplication
The spare unit is in hot-standby mode, and when a failure occurs in an active unit,
the switchover to the spare unit is very fast.
N+1 replacement principle
One spare unit is designated to a group of functional units. One spare unit can
replace any unit in the group. In this case, the switchover is a bit slower because the
spare unit is synchronised as part of the switchover procedure (also called as
(warming)). The spare unit is in cold stand-by mode.
N+1/L loadsharing principle
A unit group has no allocated spare unit and the group acts as a resource pool. The
number of units in the pool is selected in a way that there is redundant capacity. If
some units of the pool are disabled because of faults, the whole group can still
perform its designated functions.
N principle
The network element has several functional units and several network connections,
but no replacement or loadsharing is provided.
Redundancy methods of different units are shown in the table below.

Unit
BDCU
None
BSU
N+1
CCMU
2N
Table 1
DN00292692
Issue 8-0-1
Redundancy
Redundancy methods of functional units
Id:0900d805808f93bc
51
Unit
CCSU
N+1
CHU
2N
CM
2N
CMM
2N
CMU
2N
EMB
2N
ET
INDU
2N
GPLU
N+1
MB
2N
OMU
2N
PAU
N+1
SCPU
N+1
SIGU
N+1
STU
2N
SWU
2N
VLRU
2N
Table 1
5.5
Redundancy
Redundancy methods of functional units (Cont.)
MSS availability
Availability of the MSS is predicted to be approximately 0.999 9976 and the mean down
time 1.3 minutes per year. The mean time between system failures is approximately 400
000 hours.
The repair time is assumed to be 1 hour.
The availability performance figures may change as reliability predictions are made in
different phases of the design process. The figures are based on the latest field data.
MSS HW and SW attributable unavailability (System Outage Performance)
Based on latest field data of MSS product quality, six months rolling sum of the total and
major software and hardware outages is under the Bellcore Telecom standard 2 Minutes/Network Element/Year. The six months rolling sum is calculated as a sum of the
latest six months period.
5.6
MSS mechanical design and power supply

Cabinet types in MSS
52
14AC and IPCF cabinet

This cabinet provides signaling capacity, statistical functions, O&M functions,
external interfaces, and controlling of the optional TDM signaling cabinet. The func-
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
tional units in the cabinet slightly differ depending on the configuration. For MSS
deployment, this cabinet also provides storage for visited subscriber information,
whereas for the GCS the storage capacity (VLRU) is replaced with control plane signaling capacity (SU).
14BC and IPCG cabinet
This cabinet provides control plane signaling functions, charging functions, and
external interfaces. It depends on the configuration whether the subscriber database
capacity is available, or whether the configuration provides more signaling handling
capacity.
14CC and optional TDM signaling cabinet
This cabinet is an optional cabinet in the MSS that provides connectivity to the TDMbased SS7 signaling network. It supports external connections. It also provides the
capability to handle Channel Associated Signaling (CAS) and PBX signaling.
Cabinet configuration of MSS

The base configuration of the MSS is one cabinet.
MSS cabinets and layout
DN00292692
Issue 8-0-1
Id:0900d805808f93bc
53
Figure 15
54
MSS cabinets and layout, M14 first delivery
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
Cabinet types in upgraded MSS
Figure 16
Cabinet types in upgraded MSS
Cabinet types in MSSu

Figure 17 MSSu cabinet types (part 1) and Figure 18 MSSu cabinet types (part 2) show
the cabinet types that are used in the MSSu. The MSSu is always an upgrade from an
existing Integrated MSS.
DN00292692
Issue 8-0-1
Id:0900d805808f93bc
55
Figure 17
56
MSSu cabinet types (part 1)
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
Figure 18
MSSu cabinet types (part 2)
Main Operation and Maintenance Cabinet (MOMC)

The MOMC provides the O&M functionality, statistic functions, and connections to
external devices such as the Nokia Siemens Networks NetAct, NEMU, Traffica, and
SMSC. The MOMC also contains the Central Memory and cellular management
functions.
Visitor Location Register Cabinet (VLRC)
The VLRC cabinet contains subscriber data and supports statistics, charging, and
signaling functionalities.
14BC
The 14BC cabinet supports signaling functionality.
Cabinet types in Integrated MSS

The following section introduces all the seven cabinet types that are available in the Integrated MSS. New deliveries are based on IC209-A cabinets. In Figure 19 Cabinet types
available in integrated models, the Fan Tray Units are marked with the unit name FTRB.
DN00292692
Issue 8-0-1
Id:0900d805808f93bc
57
Figure 19
58
Cabinet types available in integrated models
Main Operation and Maintenance Cabinet (MOMC)

The MOMC provides the O&M functionality, statistic functions, and connections to
external devices such as the Nokia Siemens Networks NetAct, NEMU, Traffica, and
SMSC. The MOMC also contains the Central Memory and cellular management
functions.
Visitor Location Register Cabinet (VLRC)
The VLRC cabinet contains subscriber data and supports the statistics, charging,
and signaling functionalities. The VLRC also provides Channel Associated Signaling
(CAS) and PBX signaling.
General Signaling Cabinet (GSC)
Primarily, the GSC provides signaling and charging capacity. It is used when GMSC
or GMSC Server functionality is needed.
The GSC can be used to connect external devices such as the SMSC and Traffica.
Interworking Cabinet (IWC)
The IWC provides analogue and digital modem pools needed in circuit-switched
data calls. The IWC is available only in the Integrated MSS. In the standalone MSS,
the interworking functionality is provided in the Circuit Switched Data Server (CDS),
connected to the MGW.
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
Group Switch Cabinet (GSWC)

The GSWC provides switching to external and internal TDM lines.
Exchange Terminal Cabinet (ETC)
External TDM lines are terminated in the ETC. Echo cancellation is also provided in
this cabinet.
Cartridges
In the design of cartridges special attention has been paid to durability even under
demanding conditions, along with dimensioning for optimal use of space. One cartridge
usually contains the equipment of one functional unit.
In MSS configurations the VLRU, BSU, and SIGU are housed in dual computer unit cartridges meaning that one cartridge contains two functional units thus enabling a very efficient use of floorspace.
Plug-in units
The printed circuit boards of the plug-in units are multilayered and covered with a protective coating for easy handling and protection against scratches. High quality Hardmetric and Euroconnectors are used. Both surface and hole-mounted components are
used.
5.7
Capacity of first delivery MSS, upgraded MSS, and

upgraded MSSu
With the minimum configuration of one cabinet it is possible to achieve a capacity of 380
000 subscribers and 380 000 Busy Hour Call Attempts (BHCAs).
The MSS supports capacity upgrade steps of 5 000 subscribers.
Ethernet-based message bus (EMB) enables the total capacity of:
4 500 000 subscribers

3 500 000 BHCAs
4 000 000 short messages/busy hour
The corresponding capacity is the same for MSSu as well.
5.8
Capacity of Integrated MSS

As the Integrated MSS also has user plane traffic through TDM connections, the
capacity figures given here are for combined traffic towards TDM network and towards
IP/ATM backbone.
The design capacity figures stated below are for a configuration with a CP710 processor
card and 32 Mbyte/s Message Bus (MBIF-B) with compression.
The maximum configuration supports the following capacity figures:
DN00292692
Issue 8-0-1
600 000 BHCAs

600 000 subscribers
16 700 Erlangs (for the traffic using TDM network)
416 SS7 links towards the PSTN/PLMN
The other side of the network element, the bearer independent core network, has
corresponding signaling capacity.
Id:0900d805808f93bc
59
480 SS7 links towards the GERAN

The other side of the network element, the bearer independent core network, has
corresponding signaling capacity.
The Integrated MSS can be upgraded with a 64 Mbytes/s Message Bus (MBIF-C). The
new Message Bus enables the introduction of another VLRC cabinet. The corresponding total capacity figures of the Integrated MSS are as follows:
1 100 000 BHCAs

1 100 000 subscribers
The cabinet layout for the Integrated MSS is the same as for the DX MSC.
5.9
Upgrade paths
Nokia Siemens Networks offers the possibility for its current customers to utilize their
existing equipment, by integrating MSS functionality into DX MSC.
Upgrading DX MSC to Integrated MSS
When an operator wishes to use IP or ATM transmission together with existing TDMbased PLMN, it is possible to integrate MSS functionality into an existing DX MSC. The
shift from using TDM-based transmission to using IP/ATM backbone takes place gradually. The operator has both the TDM network and the IP/ATM backbone network in use
at the same time. TDM connections and IP/ATM connections can share, for example, a
common synchronous digital hierarchy (SDH) network if the operator deploys the SDH
in the IP/ATM backbone. Alternatively, these networks can be totally separate.
The upgrade can be done in a live network with minimum effects on the ongoing traffic.
Upgrade possibility is provided for DX MSC network elements based on cartridge construction. Older equipment based on subrack construction cannot be upgraded to an
Integrated MSS. Upgrading Compact DX MSC to integrate MSS is not supported either.
Upgrading a DX MSC to Integrated MSS requires:
installing LAN switching units (SWUs) and LAN cabling

upgrading CPU and memory to provide redundant LAN connections
From the M11 deliveries onwards, the necessary LAN cabling is already available.
Therefore, only addition of LAN switches is required to support control LAN, if not
already deployed. If LAN switches have already been added to support control LAN
(SIGTRAN) in M11 or early M12 deliveries, these LAN switches may need to be
replaced with later ESB SWU variants, for example, ESB20-A, ESB24-A, or ESB24-D,
to support enhanced resilience provided by SCTP multihoming.
LAN connections
It is necessary to create separate LANs for control plane and O&M traffic by installing
LAN SWUs and arranging LAN cabling. The space occupied by LAN SWUs is small
enough to allow them to be inserted into the existing STU and CHU functional units. It
is not necessary to remove the existing hardware.
CPU cards
60
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
The MSS provides redundant LAN connections. Because of this, it is necessary to have
CPU cards with two LAN interfaces. All existing CP523 CPU cards with one LAN interface need to be upgraded to a C710 or a newer CPU card.
CP710 CPU cards are only for cabinets with forced ventilation. Newer CPU cards can
be used in all cabinet types.
Upgrading DX MSC to MSSu
When upgrading Nokia Siemens Networks DX MSC to an MSSu, keep to the following
upgrade order:
1. Upgrade the DX MSC to an Integrated MSS.
2. Upgrade the Integrated MSS to an MSSu.
This procedure ensures that there is no service break. During upgrade to MSSu, the
TDM based connections (GERAN, PSTN, PLMN and CS data services) are moved from
the Integrated MSS to the MGW.
When upgrading to MSSu, hardware configuration is changed in the following way:
5.10
Clock and Alarm system is reconfigured.

AS7 cards are removed from signaling units.
Group Switch, ET, and IWF-related hardware are removed.
MSS site requirements

Operators benefit from the small size of DX 200 exchanges, since it is often possible to
install them in small equipment rooms, and the installation does not impose special
requirements on ceiling, wall, or floor constructions.
5.10.1
Exchange room layout

Cabinets contain cartridges which contain the plug-in units, all of which can be installed
to suit specific configuration needs of a customer.
The cabinets are standard welded frames designed in accordance with IEC, EN, and
Telcordia recommendations. Cabinets are provided with advanced features in terms of
stability, durability, and safety protection against interference.
The DX 200 network element hardware is NEBS Level 3 compliant, covering GR-63CORE, 1995 and GR-1089-CORE, 1999, in Central Office or equivalent premises, as
applicable for Type 2 equipment, as specified in GR-1089-CORE, 1999, Appendix B.
Some cabinets are equipped with a cabling cabinet, which is an integral part of the
equipment cabinet and attached permanently to the right-hand end of the cabinet. The
Cable Conduit Cabinet (CCC) contains all the external interfaces for the computer-unit
row. These interfaces may include LAN interfaces, external alarm interfaces, external
balanced timing interfaces, and terminal and printer interfaces.
Dimensions and weight of MSS cabinets are shown in the tables below.
Cabinet type
Basic cabinet
Table 2
DN00292692
Issue 8-0-1
Height
2000 mm (6.6 ft.)
Width
900 mm (3.0 ft.)
Depth
600 mm (2.0 ft.)
Dimensions of MSS cabinets
Id:0900d805808f93bc
61
Cabinet type
With cabling
cabinet
Table 2
Height
2000 mm (6.6 ft.)
1200 mm (4.0 ft.)
Depth
600 mm (2.0 ft.)
Dimensions of MSS cabinets (Cont.)
Basic cabinet
Empty
Fully equipped
14AC and IPCF
370kg
appr. 450kg
14BC and IPCG
270kg
appr. 350kg
14CC and.IPCH
370kg
appr. 450kg
Table 3
5.10.2
Width
Weight of MSS cabinets
Typical power consumption of MSS

Easy installation, reliability, and maintainability of power supply system have been the
main goals in the power supply design of Nokia Siemens Networks MSS.
Power supply is distributed from the rectifier system and the batteries through the Power
Distribution Fuse Unit (PDFU) to the cartridges, through distribution cables. The PDFU
contains fuses for internal distribution cables of the cabinet and alarm circuits for the
incoming voltages, plus its own fuses. An alarm is generated if a power failure occurs.
For more information, see MSC Server (MSS and MSSu) Engineering Description.
Power consumption of MSS
Power consumption for fully equipped MSS cabinets is shown in the tables below.
Cabinet
14AC
1500 W
14BC 0
1400 W
14BC 1
1400 W
14BC 2
1400 W
14CC
1500 W
Table 4
Power consumption and heat dissipation in MSS cartridges and cabinets
Cabinet
Power consumption
IPCF
1000 W
IPCG
1200 W
IPCH
1300 W
Table 5
62
Estimated maximum operating

power consumption
Power consumption of cabinets in standalone models
Id:0900d805808f93bc
DN00292692
Issue 8-0-1
Cabinet
Power consumption
MOMC
850 W
VLRC
1000 W
GSC
1050 W
GSWC
1700 W
ETC
750 W
IWC
1100 W
Table 6
DN00292692
Issue 8-0-1
Power consumption of cabinets in the integrated models and in the MSSu
Id:0900d805808f93bc
63
Operation and maintenance
6 Operation and maintenance

6.1
MMI system
The MSS is operated by means of MML commands. MML commands are entered using
the keyboard of the MML terminal. Printouts and messages are displayed on the
terminal screen. Communication with the system takes place in an MML session.
The system has an online help with command menus and a parameter guide. MML
commands executed during a particular MML session are written to an MML command
log, which also contains other information on the MML session.
In addition to the MML commands, other tools are available for operating the MSS
System, as listed in the table below.
Tool
Description
Disk command file
Executing MML command sequences
MML macro
Executing complicated MML command

sequences
Command calendar
Executing an MML command or a disk command

file once or several times at a predetermined
moment
Command log
Storing information on the executed commands
Table 7
MML commands execution tool
The system can be managed by local and remote MML sessions. A local session directly
connects the user to the system. A remote session is opened by establishing a connection to the local system, and then to the system you want to use. The system can also
be operated remotely from a network management system (NMS) by opening remote
MML sessions from NetAct.
NetAct is a Nokia Siemens Networks operations support system (OSS), which can be
used to operate different core network elements. NetAct provides basic tools and applications, as well as enhanced optional solutions, products, and services. NetAct provides
an interface to manage network elements like the MSS by offering several management
functions, such as:
Fault Management (FM)

Performance Management (PM)
Configuration Management (CM)
User Management (UM)
Time Management (TM)
Hardware Management (HM)
Software Management (SM)
The NetAct - MSS interface is based on open standards, but has proprietary mechanisms as well. Some of the mechanisms are not even directly visible to the operator, only
through NetAct applications, and are offered by the NetAct northbound interface.
For more information, see NetAct product documentation in Nokia Siemens Networks
Product Information Center (PIC).
64
Id:0900d80580811cee
DN00292692
Issue 8-0-1
6.2
Configuration management
Nokia Siemens Networks provides a Man-Machine-Interface (MMI) for the configuration
management of the MSS. The MSS can be managed by MML commands locally on site
or remotely from Nokia Siemens Networks NetAct using, for example, Telnet or SSH
protocol.
NetAct also offers the NetAct Configurator tool for configuring radio access network in
MSS. For more information, see NetAct Configurator Principles in NetAct product documentation.
6.3
Fault management
Fault management in a network element can to detect, localize, and report faults. Fault
reporting is realized with alarms. The alarm system handles the fault and disturbance
observations that occur in the network element and in the remote objects controlled by
the network element.
The alarm system is part of the network element's maintenance system. Locally, the
alarms can be viewed by using a Visual Display Unit (VDU), or transferred to a printer.
Alarms can also be transferred to NetAct as notifications over the network or by using
the alarm upload mechanism.
In a notification transfer mechanism, alarms are carried to NetAct using Extensible
Markup Language (XML) over the Hypertext Transfer Protocol (HTTP). An alarm upload
takes place with File Transfer Protocol (FTP) or Secure FTP (SFTP).
More information about the system state can be gathered with MMI sessions and service
terminal sessions.
In NetAct, fault management tools are part of the base delivery.
6.4
Performance management
Performance management functions
Measurements are used for collecting data about predefined objects periodically, for
example, about traffic amount in a circuit group every hour. The measurements are seen
as tools for network planning, optimization, early fault detection, and troubleshooting.
Observations are used for getting detailed information about a predefined object when
a specific event occurs, for example, a report when a test mobile makes a location
update. Observations are mostly used for troubleshooting, testing, and equipment and
subscriber tracing.
The supervision function can be used to generate an alarm when a measured value
reaches a predefined threshold, for example, if the handover success rate is below a
limit in a cell. After receiving the alarm, the operator can use the measurements and
observations to locate the fault in the system.
Traffica provides excellent possibilities to extend these functionalities. For more information on Traffica, see Serve atOnce Traffica operating documentation in PIC.
Content of performance management
The MSS provides comprehensive information about every area of its operations,
including user traffic, signaling traffic, mobility, resource usage, network access, and
security, services, and so on. In the MSS System, user plane is handled by the MGW,
DN00292692
Issue 8-0-1
Id:0900d80580811cee
65
thus information from MGW PM functions is used together with MSS reports to provide
a complete picture of operations.
Performance management tools are part of the NetAct standard package. If more comprehensive performance management investigation is required, NetAct can provide an
optional enhanced reporting suite.
Access to performance management information
Statistic information can be accessed locally at the network element, or remotely from
Nokia Siemens Networks NetAct. Plain ASCII format reports can be printed locally on
Line Printer (LPT) or VDU by using MML commands.
Statistic reports (measurements and observations) can be transferred to the Nokia
Siemens Networks NetAct in the ASCII, XML file format. The Nokia Siemens Networks
NetAct is able to further process the XML formatted report files.
The Traffica tool can also be used to get detailed information about various activities in
the network element.
6.5
Network Element Management Unit (NEMU)

In addition to NetAct, Nokia Siemens Networks offers an optional Network Element
Management Unit (NEMU) that provides further enhancements for managing network
elements.
NEMU provides a standard computing platform for O&M applications, which do not have
strict real-time requirements. NEMU adds application-specific functions, such as processing fault management data and software management.
For more detailed information on NEMU functionalities, see Network Element Management Unit (NEMU), Product Description in NEMU product documentation.
Network Element Backup Server
The Network Element Backup Server (NEBS) is a functionality of NEMU, and can be
used to automate the daily routines of network switching subsystem (NSS) backup procedures.
The system can be configured to create a fallback build of network element, which is
transferred to a remote server. By doing so, it is possible to create backup copies in a
24-hour cycle, which are automatically taken to the remote end. This feature also
enables remote monitoring and activation of backups. Using NEBS considerably
decreases the manual work on sites, without compromising reliability of network elements. Additionally, operational costs of the network can be reduced, while the overall
efficiency of the network can be improved.
6.6
System maintenance
System maintenance handles fault situations and user-initiated configuration management tasks, and it controls availability performance on the network element level. The
tasks include preventive maintenance, fault control, and fault correction, and are performed automatically and autonomously.
System maintenance consists of the following functional groups:
66
Hardware and software fault detection
Id:0900d80580811cee
DN00292692
Issue 8-0-1
DN00292692
Issue 8-0-1
Hardware supervision
Hardware supervision is based on routine tests and supervisions performed as
a background process. Hardware supervision is divided into several subfunctions according to hardware type.
Software supervision
Software supervision detects fault conditions in which control over the software
is lost. Program block supervision is based on watchdog timers and special
supervision messages. The watchdog timer is set at regular intervals for every
control processor and preprocessor in the system. Otherwise, the hardware
restarts the processor.
Time supervision
Time supervision is performed in a hierarchical way, so that the network element
functioning as the main maintenance center in the O&M network controls the
time in the other systems of the network.
Supervision of semipermanent connections
Supervision of the semipermanent connections ensures that the connections
defined by the user commands are maintained in the switching network. If one
or some of the connections are missing, they are re-established. If the connection restoration fails, or the connection disappears again, an alarm is generated.
Alarm handling for fault information analysis
The alarm system collects various fault and disturbance observations, processes
them, and then informs the user by alarm printouts and alarm lamp panel controls.
The alarm system also stores the alarm events and activates the automatic recovery
functions when necessary.
The following types of alarm data is collected:
hardware alarms
fault observations produced by program blocks
fault observations produced by preprocessors
Recovery and elimination of fault effects
The recovery block controls the operating states of functional units. The recovery
functions are as follows:
elimination of fault effects
restart control
user interface
Fault localization
The fault localization function locates hardware faults in the system to an accuracy
of one plug-in unit in 70% of the cases, and to an accuracy of four plug-in units in
95% of the cases. The system complies with the ITU-T requirement for the average
active repair time of 30 minutes. Fault localization function is implemented in all the
functional units.
Fault localization can be divided into the following subfunctions:
fault localization for switching network
fault localization for processor units
fault localization for time-slot-based units
fault localization for preprocessors
fault localization for I/O devices
fault localization for message bus
fault localization for clock system
Id:0900d80580811cee
67
System maintenance management

All MML commands for system maintenance can be used both in the exchange
premises and remotely from Nokia Siemens Networks NetAct. NetAct also provides a
hardware inventory functionality for hardware management.
6.7
Remote User Information Management

Remote User Information Management (RUIM) in the MSS enables centralized user
account management and user role management. User accounts and roles are
managed with NetAct and the data is saved to the Lightweight Directory Access Protocol
(LDAP) directory. Network elements authenticate users from the LDAP directory. User
role data is retrieved from the LDAP directory to the network element after the particular
user is authenticated. Role data is saved in the local cache until the user ends the
session.
68
Id:0900d80580811cee
DN00292692
Issue 8-0-1

M 1 HW

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M 1 HW

Uploaded by

Copyright:

Available Formats

Nokia Siemens Networks MSC

Server, Product Description

Nokia Siemens Networks MSC Server, Product Description

Important Notice on Product Safety

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

Nokia Siemens Networks MSC Server, Product Description

MSC Server overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

MSC Server functionalities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSC Server interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Services in MSC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Nokia Siemens Networks MSC Server, Product Description

MSC Server hardware architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Operation and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Nokia Siemens Networks MSC Server, Product Description

MSC Server access domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Nokia Siemens Networks MSC Server, Product Description

Redundancy methods of functional units . . . . . . . . . . . . . . . . . . . . . . . . 51

Nokia Siemens Networks MSC Server, Product Description

Circuit-Switched Fallback (CSFB)

Changes made between issues 6-0-0 and 5-0-0

Nokia Siemens Networks MSC Server overview

MSC Server overview

Nokia Siemens Networks MSC Server, Product Description

1 MSC Server overview

Nokia Siemens Networks MSC Server, Product Description

MSC Server overview

Benefits of the MSS

MSC Server overview

Nokia Siemens Networks MSC Server, Product Description

MSC Server access domains

Operational cost savings

Nokia Siemens Networks MSC Server, Product Description

MSC Server overview

Local switching in MSS System

MSC Server overview

Nokia Siemens Networks MSC Server, Product Description

MSS product configurations

Nokia Siemens Networks MSC Server

Nokia Siemens Networks MSC Server, Product Description

MSC Server overview

CISCO 7609(S) Juniper

Positioning the MSS in mobile networks

Nokia Siemens Networks Mobile VoIP Server (NVS)

MSC Server overview

Nokia Siemens Networks MSC Server, Product Description

CISCO 7609(S) Juniper

Positioning the MSS/NVS in a VoIP architecture

Interconnect Border Control Functionality (I-BCF)

Nokia Siemens Networks MSC Server, Product Description

MSC Server overview

Application Layer Gateway (ALG), without firewall capabilities

I-BCF in the MSS

MSC Server functionalities

Nokia Siemens Networks MSC Server, Product Description

2 MSC Server functionalities

Subscriber data management in the MSC Server

User Equipment (UE) originating and terminating calls

Control functions in the MSS

Nokia Siemens Networks MSC Server, Product Description

MSC Server functionalities

Control entities in MSS System

MSC Server functionalities